public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/88646] Optimizer failure on integer sum overflow cast to bool
[not found] <bug-88646-4@http.gcc.gnu.org/bugzilla/>
@ 2019-01-01 1:09 ` pinskia at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: pinskia at gcc dot gnu.org @ 2019-01-01 1:09 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 3986858 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88646
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Signed integer overflow is undefined.
In the case of short and signed char, the operations are promoted to int due to
the way C++ works.
>From gcc-bugs-return-627192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 01:16:22 2019
Return-Path: <gcc-bugs-return-627192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2173 invoked by alias); 1 Jan 2019 01:16: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 127301 invoked by uid 48); 1 Jan 2019 01:15:52 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88510] GCC generates inefficient U64x2/v2di scalar multiply for NEON32
Date: Tue, 01 Jan 2019 01:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin 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: short_desc
Message-ID: <bug-88510-4-9l8PAjwOPr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00001.txt.bz2
Content-length: 903
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88510
Devin Hussey <husseydevin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|GCC generates inefficient |GCC generates inefficient
|U64x2 scalar multiply for |U64x2/v2di scalar multiply
|NEON32 |for NEON32
--- Comment #1 from Devin Hussey <husseydevin at gmail dot com> ---
I noticed that the scalarization is performed in the veclower21 stage.
In making a patch for LLVM, I found that the x86 code could basically be
copy-pasted over, just adding truncates and replacing the SSE instructions with
NEON instructions. I would add it if someone told me where the SSE code is and
where to put the NEON code. That is what helped me with the LLVM patch.
>From gcc-bugs-return-627193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 06:46:51 2019
Return-Path: <gcc-bugs-return-627193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26170 invoked by alias); 1 Jan 2019 06:46:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26121 invoked by uid 48); 1 Jan 2019 06:46:47 -0000
From: "gianni at mariani dot ws" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88646] Optimizer failure on integer sum overflow cast to bool
Date: Tue, 01 Jan 2019 06:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gianni at mariani dot ws
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88646-4-lGwX453D4F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00002.txt.bz2
Content-length: 679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88646
gianni at mariani dot ws changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #2 from gianni at mariani dot ws ---
While it may be undefined, should the result at least be consistent? Either the
result is zero and the bool cast works as the code expected or the result is
non zero and the value printed is non zero.
Note the printed l_v=0.
Also note that casting the result to int doesn't work either.
>From gcc-bugs-return-627194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 08:27:45 2019
Return-Path: <gcc-bugs-return-627194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33903 invoked by alias); 1 Jan 2019 08:27: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 33860 invoked by uid 48); 1 Jan 2019 08:27:41 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88646] Optimizer failure on integer sum overflow cast to bool
Date: Tue, 01 Jan 2019 08:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-88646-4-vGY0SunM3E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00003.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88646
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
If you want signed integer overflow to be defined and be the same between
different variables then use -fwrapv .
Under defined behavior means gcc could produce this behavior.
If you want to detect this behavior at runtime you can use -fsantizer=undefined
option.
>From gcc-bugs-return-627195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 11:13:33 2019
Return-Path: <gcc-bugs-return-627195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115052 invoked by alias); 1 Jan 2019 11:13:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115017 invoked by uid 48); 1 Jan 2019 11:13:29 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88575] gcc got confused by different comparison operators
Date: Tue, 01 Jan 2019 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-88575-4-IPg0s3cdEL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00004.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88575
--- Comment #2 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
Code was compiled with -O3 -march=skylake.
I have tried to add -fno-signed-zeros and -fsigned-zeros, and got the same
output for both cases.
>From gcc-bugs-return-627196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 11:32:01 2019
Return-Path: <gcc-bugs-return-627196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130249 invoked by alias); 1 Jan 2019 11: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 130209 invoked by uid 48); 1 Jan 2019 11:31:56 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88575] gcc got confused by different comparison operators
Date: Tue, 01 Jan 2019 11:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-88575-4-P5kjrAYWrJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00005.txt.bz2
Content-length: 1253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88575
--- Comment #3 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
I have tried to compile with -O3 -march=skylake -ffast-math and got this:
[asm]
test(double, double):
vminsd xmm2, xmm0, xmm1
vcmplesd xmm0, xmm0, xmm1
vxorpd xmm1, xmm1, xmm1
vblendvpd xmm0, xmm1, xmm2, xmm0
ret
test2(double, double):
vminsd xmm2, xmm0, xmm1
vcmpltsd xmm0, xmm0, xmm1
vxorpd xmm1, xmm1, xmm1
vblendvpd xmm0, xmm1, xmm2, xmm0
ret
[/asm]
And this is for -O3 -march=skylake -funsafe-math-optimizations. As you can see,
one instruction was eliminated from test2(). For some reason it was not
eliminated from test() function. I checked that -ffinite-math-only present in
-ffast-math prevented elimination of this extra instruction.
[asm]
test(double, double):
vminsd xmm2, xmm0, xmm1
vcmplesd xmm0, xmm0, xmm1
vxorpd xmm1, xmm1, xmm1
vblendvpd xmm0, xmm1, xmm2, xmm0
ret
test2(double, double):
vcmpnltsd xmm1, xmm0, xmm1
vxorpd xmm2, xmm2, xmm2
vblendvpd xmm0, xmm0, xmm2, xmm1
ret
[/asm]
>From gcc-bugs-return-627197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 15:52:37 2019
Return-Path: <gcc-bugs-return-627197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113353 invoked by alias); 1 Jan 2019 15:52: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 113309 invoked by uid 48); 1 Jan 2019 15:52:32 -0000
From: "mcccs at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88645] Don't assume functions are always nonnull if there's __attribute__((weak_import)), similar to __attribute__((weak))
Date: Tue, 01 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mcccs at gmx dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88645-4-ZJ6ovxcToo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00006.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88645
MCCCS <mcccs at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from MCCCS <mcccs at gmx dot com> ---
*it works. This bug seemed to exit because of
a missing weak_import in Apple's headers.
>From gcc-bugs-return-627198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 15:53:51 2019
Return-Path: <gcc-bugs-return-627198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114936 invoked by alias); 1 Jan 2019 15:53:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114815 invoked by uid 48); 1 Jan 2019 15:53:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88640] ICE in mark_reachable_handlers, at tree-eh.c:3926
Date: Tue, 01 Jan 2019 15:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88640-4-hvpUzDQGUD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00007.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88640
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
With additional -mcpu=power8 already r200000 ICEs, GCC 4.8-RH ICEs too, don't
have anything powerpc64le-ish older than that.
>From gcc-bugs-return-627199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 16:28:44 2019
Return-Path: <gcc-bugs-return-627199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36542 invoked by alias); 1 Jan 2019 16:28:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36491 invoked by uid 48); 1 Jan 2019 16:28:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88635] [8 Regression] Assembler error when building with "-g -O2 -m32"
Date: Tue, 01 Jan 2019 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: assemble-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88635-4-KI1UvJ1Ohv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00008.txt.bz2
Content-length: 1132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88635
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-01
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |8.3
Summary|Assembler error when |[8 Regression] Assembler
|building with "-g -O2 -m32" |error when building with
| |"-g -O2 -m32"
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r256580. Got fixed or went latent with r265677 on the trunk.
Reduced testcase with -m32 -dA -g -O2 -fpie -fvisibility=hidden:
void
foo (char *b)
{
unsigned c = 0;
--c;
do
if (++*b++ == 0)
break;
while (--c);
if (c == 0)
while (*b++)
;
}
void
bar (void)
{
foo ("");
}
>From gcc-bugs-return-627200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 16:51:21 2019
Return-Path: <gcc-bugs-return-627200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93741 invoked by alias); 1 Jan 2019 16:51:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93586 invoked by uid 48); 1 Jan 2019 16:51:16 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88640] ICE in mark_reachable_handlers, at tree-eh.c:3926
Date: Tue, 01 Jan 2019 16:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88640-4-kRDWSMhpky@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00009.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88640
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
It looks like a generic problem to me, fwiw.
>From gcc-bugs-return-627201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 17:10:53 2019
Return-Path: <gcc-bugs-return-627201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129843 invoked by alias); 1 Jan 2019 17:10: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 129635 invoked by uid 48); 1 Jan 2019 17:10:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52491] FAIL: gcc.dg/torture/pr52402.c at -O2 and above
Date: Tue, 01 Jan 2019 17:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: wrong-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-52491-4-3HDWxBmfLE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52491-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52491-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00010.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52491
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this still present on ppc?
>From gcc-bugs-return-627202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 17:11:35 2019
Return-Path: <gcc-bugs-return-627202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130975 invoked by alias); 1 Jan 2019 17:11: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 130844 invoked by uid 48); 1 Jan 2019 17:11:31 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65342] [7/8/9 Regression] FAIL: gfortran.dg/intrinsic_(un)?pack_1.f90 -O1 execution test on powerpc-apple-darwin9 after r210201
Date: Tue, 01 Jan 2019 17:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65342-4-2iq2FEDx56@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00011.txt.bz2
Content-length: 158
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65342
--- Comment #22 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this still present on ppc?
>From gcc-bugs-return-627203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 17:52:06 2019
Return-Path: <gcc-bugs-return-627203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50073 invoked by alias); 1 Jan 2019 17:52: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 50028 invoked by uid 48); 1 Jan 2019 17:52:02 -0000
From: "johannespfau at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88041] gdc.test tests should include that prefix in test names
Date: Tue, 01 Jan 2019 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: johannespfau at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ro at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88041-4-F6begBeHBk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88041-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88041-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00012.txt.bz2
Content-length: 1699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88041
Johannes Pfau <johannespfau at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |johannespfau at gmail dot com
--- Comment #5 from Johannes Pfau <johannespfau at gmail dot com> ---
For reference, this makes running the testsuite on windows/msys2 hosts somewhat
more complicated:
On these systems, ln -s is implemented by copying SRC to DST instead of
creating proper links [1]. (I'm not sure whether the TCL file link command
actually calls ln on MSYS2, but it seems to do so, as the observed effect is
just this: a copy of the directory).
It is possible to configure MSYS2 to use proper NTFS symlinks instead [2], but
then running the testuite will always require administrator privileges on older
windows versions. On newer windows versions, mklink can now be used as normal
user iff the windows developer mode is enabled [3]. However, the ln shipped
with MSYS2 does not yet make use of this feature[4].
Not sure if this really is a problem or if there's a better solution. For now,
configuring ln to use windows symlinks and building gcc as admin should work.
An alternative is to just manually create that one symlink. The best solution
is probably to just use a cross-compiler for testing and build on linux ;-)
[1] https://sourceforge.net/p/msys2/tickets/41/
[2] https://www.joshkel.com/2018/01/18/symlinks-in-windows/
[3]
https://www.wintellect.com/non-admin-users-can-now-create-symlinks-windows-10/
[4] https://github.com/Alexpux/MSYS2-packages/issues/1219
>From gcc-bugs-return-627204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 19:13:34 2019
Return-Path: <gcc-bugs-return-627204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25049 invoked by alias); 1 Jan 2019 19:13:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24976 invoked by uid 48); 1 Jan 2019 19:13:30 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88647] New: Rejects valid program dereferencing pointer with incomplete reference type.
Date: Tue, 01 Jan 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00013.txt.bz2
Content-length: 1088
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88647
Bug ID: 88647
Summary: Rejects valid program dereferencing pointer with
incomplete reference type.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
struct S *p;
void f(void);
int main()
{
f();
*p;
}
struct S { int x; };
void f()
{
static struct S s = { 0 };
p = &s;
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
The following error message was outputed:
prog.c: In function 'main':
prog.c:10:5: error: dereferencing pointer to incomplete type 'struct S'
10 | *p;
| ^~
Expected behaviour:
No error message outputed.
I can't find anything in the standard that makes the this program invalid.
>From gcc-bugs-return-627205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 21:20:28 2019
Return-Path: <gcc-bugs-return-627205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83833 invoked by alias); 1 Jan 2019 21:20: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 83795 invoked by uid 55); 1 Jan 2019 21:20:25 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82743] uncaught character truncation in derived type initialization
Date: Tue, 01 Jan 2019 21:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82743-4-Fl4JfvDIuO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00014.txt.bz2
Content-length: 822
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82743
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Tue Jan 1 21:19:53 2019
New Revision: 267499
URL: https://gcc.gnu.org/viewcvs?rev=267499&root=gcc&view=rev
Log:
2019-01-01 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/82743
* primary.c (gfc_convert_to_structure_constructor): If a character
in a constructor is too long, add a warning with
-Wcharacter-truncation.
2019-01-01 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/82743
* gfortran.dg/structure_constructor_16.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/structure_constructor_16.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/primary.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 21:21:25 2019
Return-Path: <gcc-bugs-return-627206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85063 invoked by alias); 1 Jan 2019 21:21:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85013 invoked by uid 48); 1 Jan 2019 21:21:21 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82743] uncaught character truncation in derived type initialization
Date: Tue, 01 Jan 2019 21:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-82743-4-1NmuHrflSQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00015.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82743
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk, closing.
>From gcc-bugs-return-627207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 21:21:25 2019
Return-Path: <gcc-bugs-return-627207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85153 invoked by alias); 1 Jan 2019 21:21:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85030 invoked by uid 48); 1 Jan 2019 21:21:21 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19276] [meta-bug] CHARACTER related bugs in gfortran
Date: Tue, 01 Jan 2019 21:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.0.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-19276-4-os8OgJH5EB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-19276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-19276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00016.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19276
Bug 19276 depends on bug 82743, which changed state.
Bug 82743 Summary: uncaught character truncation in derived type initialization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82743
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-627208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 21:31:36 2019
Return-Path: <gcc-bugs-return-627208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94116 invoked by alias); 1 Jan 2019 21:31: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 94072 invoked by uid 48); 1 Jan 2019 21:31:33 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64
Date: Tue, 01 Jan 2019 21:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-65782-4-wId3YcUr6b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00017.txt.bz2
Content-length: 713
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782
Daniel Fruzynski <bugzilla@poradnik-webmastera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugzilla@poradnik-webmaster
| |a.com
--- Comment #3 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
Cygwin (x86_64-pc-cygwin) is also affected. I have encountered this bug on gcc
7.4.0.
Could you add new option which would remove XMM16+ registers from available
registers pool? It could be used as an easy to use workaround until you fix it
properly.
>From gcc-bugs-return-627209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 22:59:00 2019
Return-Path: <gcc-bugs-return-627209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23739 invoked by alias); 1 Jan 2019 22:59: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 23610 invoked by uid 48); 1 Jan 2019 22:58:56 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64
Date: Tue, 01 Jan 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-65782-4-DhHyfnfeLl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00018.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782
--- Comment #4 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
I have found that I can use -ffixed-reg option for this. It allows to eliminate
one register, so I have to use it 16 times to eliminate all xmm16..31
registers. It would be handy to have another option which would allow to
disable all registers from this group together.
>From gcc-bugs-return-627210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 23:20:00 2019
Return-Path: <gcc-bugs-return-627210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55000 invoked by alias); 1 Jan 2019 23:20: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 54950 invoked by uid 48); 1 Jan 2019 23:19:56 -0000
From: "stefan at agner dot ch" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88648] New: Force unified syntax for inline assembly not functional (-masm-syntax-unified)
Date: Tue, 01 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stefan at agner dot ch
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00019.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88648
Bug ID: 88648
Summary: Force unified syntax for inline assembly not
functional (-masm-syntax-unified)
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: stefan at agner dot ch
Target Milestone: ---
Forcing inline assembly to be unified syntax seems not to work properly
E.g. compiling a c file with the following inline assembly using
arm-none-eabi-gcc -marm -march=armv7-a -masm-syntax-unified test.c --save-temps
asm ( "nop" );
leads to:
.syntax divided
@ 5 "test.c" 1
nop
@ 0 "" 2
>From gcc-bugs-return-627211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 01 23:29:34 2019
Return-Path: <gcc-bugs-return-627211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67646 invoked by alias); 1 Jan 2019 23:29:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65920 invoked by uid 48); 1 Jan 2019 23:29:30 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65782] Assembly failure (invalid register for .seh_savexmm) with -O3 -mavx512f on mingw-w64
Date: Tue, 01 Jan 2019 23:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-65782-4-lNIH9WCcX8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00020.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65782
--- Comment #5 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
I got following link:
https://stackoverflow.com/questions/53733624/is-xmm8-register-value-preserved-across-calls/53733767#53733767
Quote from it: "Any additional registers for newer instruction sets are
volatile by default. This includes the upper parts of YMM0-15 and ZMM0-15 as
well as ?MM16-31 if present.".
So it looks that gcc should not generate .seh_savexmm for xmm16..31 at all.
>From gcc-bugs-return-627212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 03:53:31 2019
Return-Path: <gcc-bugs-return-627212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106403 invoked by alias); 2 Jan 2019 03:53:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106357 invoked by uid 48); 2 Jan 2019 03:53:28 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87729] Please include -Woverloaded-virtual in -Wall
Date: Wed, 02 Jan 2019 03:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87729-4-C1NHVgLaln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00021.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87729
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Daniel Fruzynski from comment #0)
> clang includes -Woverloaded-virtual in -Wall. Please do same for gcc.
I was looking for a testcase to check and tried g++.dg/warn/pr61945.C but clang
doesn't warn on that with -Wall. Do you have a better testcase to show how
clang warns but gcc doesn't?
>From gcc-bugs-return-627213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 03:56:19 2019
Return-Path: <gcc-bugs-return-627213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108890 invoked by alias); 2 Jan 2019 03:56:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108843 invoked by uid 48); 2 Jan 2019 03:56:15 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/79011] incorrect form of warning options listed in the manual
Date: Wed, 02 Jan 2019 03:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79011-4-4ExuFy7O17@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79011-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79011-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00022.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79011
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #0)
> Section 3.8 of the manual, Options to Request or Suppress Warnings, states
> that:
>
> "This manual lists only one of the two forms, whichever is not the
> default."
>
> The following is a list of options listed in that section that, according to
> the manual, are enabled by default (and thus should be listed in the
> -Wno-xxx form).
>
...
> -Wno-endif-labels
This one's already in -Wno-xxx form
>From gcc-bugs-return-627214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 07:38:11 2019
Return-Path: <gcc-bugs-return-627214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64703 invoked by alias); 2 Jan 2019 07:38:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64620 invoked by uid 48); 2 Jan 2019 07:38:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88649] New: runtime error: load of value 137971008, which is not a valid value for type 'gfc_intrinsic_op'
Date: Wed, 02 Jan 2019 07:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter blocked target_milestone
Message-ID: <bug-88649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00023.txt.bz2
Content-length: 1918
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88649
Bug ID: 88649
Summary: runtime error: load of value 137971008, which is not a
valid value for type 'gfc_intrinsic_op'
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Blocks: 63426
Target Milestone: ---
Using ubsan GCC compiler, one can see:
$ ./xgcc -B.
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/dec_bitwise_ops_1.f90
-O0 -fdec
../../gcc/fortran/resolve.c:4150:23: runtime error: load of value 137971008,
which is not a valid value for type 'gfc_intrinsic_op'
#0 0xb1362e in resolve_operator ../../gcc/fortran/resolve.c:4150
#1 0xb2ffce in gfc_resolve_expr(gfc_expr*) ../../gcc/fortran/resolve.c:6825
#2 0xb61cfa in gfc_resolve_code(gfc_code*, gfc_namespace*)
../../gcc/fortran/resolve.c:11269
#3 0xb9cb84 in resolve_codes ../../gcc/fortran/resolve.c:16715
#4 0xb9cd8b in gfc_resolve(gfc_namespace*)
../../gcc/fortran/resolve.c:16750
#5 0xad072e in resolve_all_program_units ../../gcc/fortran/parse.c:6067
#6 0xad1a20 in gfc_parse_file() ../../gcc/fortran/parse.c:6317
#7 0xc3694a in gfc_be_parse_file ../../gcc/fortran/f95-lang.c:204
#8 0x22fdf98 in compile_file ../../gcc/toplev.c:456
#9 0x2305493 in do_compile ../../gcc/toplev.c:2176
#10 0x2305ac1 in toplev::main(int, char**) ../../gcc/toplev.c:2311
#11 0x466210c in main ../../gcc/main.c:39
#12 0x7ffff608cfea in __libc_start_main ../csu/libc-start.c:308
#13 0x872bd9 in _start
(/home/marxin/Programming/gcc2/objdir/gcc/f951+0x872bd9)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
[Bug 63426] [meta-bug] Issues found with -fsanitize=undefined
>From gcc-bugs-return-627215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 07:45:48 2019
Return-Path: <gcc-bugs-return-627215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70714 invoked by alias); 2 Jan 2019 07:45:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69496 invoked by uid 48); 2 Jan 2019 07:45:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88650] New: [9 Regression] ICE in set_even_probabilities at gcc/predict.c:885 since r267485
Date: Wed, 02 Jan 2019 07:45: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00024.txt.bz2
Content-length: 2426
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88650
Bug ID: 88650
Summary: [9 Regression] ICE in set_even_probabilities at
gcc/predict.c:885 since r267485
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Caused by my commit:
$ gcc
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/transfer_simplify_1.f90
-fno-tree-fre -fno-tree-ccp -Og
during GIMPLE pass: profile_estimate
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/transfer_simplify_1.f90:15:0:
15 | call pr31427 ()
|
internal compiler error: Floating point exception
0xb3bd2f crash_signal
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/toplev.c:326
0x7ffff6bc310f ???
/usr/src/debug/glibc-2.27-6.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x96966a safe_scale_64bit(unsigned long, unsigned long, unsigned long, unsigned
long*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/profile-count.h:81
0x96966a profile_probability::apply_scale(long, long) const
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/profile-count.h:497
0x96966a profile_probability::apply_scale(long, long) const
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/profile-count.h:489
0xa955d4 set_even_probabilities
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/predict.c:885
0xa99f30 combine_predictions_for_bb
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/predict.c:1237
0xa9a2e9 tree_estimate_probability(bool)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/predict.c:3091
0xa9a677 execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/predict.c:4028
0xa9a677 execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-x86_64/build/gcc/predict.c:4011
>From gcc-bugs-return-627216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 07:46:08 2019
Return-Path: <gcc-bugs-return-627216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82141 invoked by alias); 2 Jan 2019 07:46: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 79035 invoked by uid 48); 2 Jan 2019 07:46:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88650] [9 Regression] ICE in set_even_probabilities at gcc/predict.c:885 since r267485
Date: Wed, 02 Jan 2019 07:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88650-4-h3KieuQQP4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00025.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88650
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-627217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 07:51:04 2019
Return-Path: <gcc-bugs-return-627217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28323 invoked by alias); 2 Jan 2019 07:51:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28231 invoked by uid 48); 2 Jan 2019 07:50:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88651] New: tree-data-ref.c:3764:26: runtime error: signed integer overflow: 9223372036854775802 - -6 cannot be represented in type 'long int'
Date: Wed, 02 Jan 2019 07:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc blocked target_milestone attachments.created
Message-ID: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00026.txt.bz2
Content-length: 3590
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88651
Bug ID: 88651
Summary: tree-data-ref.c:3764:26: runtime error: signed integer
overflow: 9223372036854775802 - -6 cannot be
represented in type 'long int'
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Blocks: 63426
Target Milestone: ---
Created attachment 45311
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45311&action=edit
test-case
UBSAN GCC compiler complains about:
$ ./xgcc -B. -c -O -ftree-loop-vectorize final.f90
final.f90:65:8:
65 | DO m= 1,zone(1)
| 1
Warning: Deleted feature: End expression in DO loop at (1) must be integer
../../gcc/tree-data-ref.c:3764:26: runtime error: signed integer overflow:
9223372036854775802 - -6 cannot be represented in type 'long int'
#0 0x457686a in analyze_subscript_affine_affine
../../gcc/tree-data-ref.c:3764
#1 0x4577d03 in analyze_siv_subscript ../../gcc/tree-data-ref.c:3915
#2 0x457935b in analyze_overlapping_iterations
../../gcc/tree-data-ref.c:4161
#3 0x457c7c1 in subscript_dependence_tester_1
../../gcc/tree-data-ref.c:4702
#4 0x457cb57 in subscript_dependence_tester ../../gcc/tree-data-ref.c:4752
#5 0x457cf8a in compute_affine_dependence(data_dependence_relation*, loop*)
../../gcc/tree-data-ref.c:4811
#6 0x457d4ef in compute_all_dependences(vec<data_reference*, va_heap,
vl_ptr>, vec<data_dependence_relation*, va_heap, vl_ptr>*, vec<loop*, va_heap,
vl_ptr>, bool) ../../gcc/tree-data-ref.c:4878
#7 0x45bb302 in vect_analyze_data_ref_dependences(_loop_vec_info*, unsigned
int*) ../../gcc/tree-vect-data-refs.c:541
#8 0x2b52e3c in vect_analyze_loop_2 ../../gcc/tree-vect-loop.c:1851
#9 0x2b574c6 in vect_analyze_loop(loop*, _loop_vec_info*, vec_info_shared*)
../../gcc/tree-vect-loop.c:2270
#10 0x2be22b4 in try_vectorize_loop_1 ../../gcc/tree-vectorizer.c:873
#11 0x2be31b8 in try_vectorize_loop ../../gcc/tree-vectorizer.c:1019
#12 0x2be34ea in vectorize_loops() ../../gcc/tree-vectorizer.c:1101
#13 0x2831799 in execute ../../gcc/tree-ssa-loop.c:414
#14 0x1ec9ffa in execute_one_pass(opt_pass*) ../../gcc/passes.c:2483
#15 0x1eca890 in execute_pass_list_1 ../../gcc/passes.c:2569
#16 0x1eca945 in execute_pass_list_1 ../../gcc/passes.c:2570
#17 0x1eca945 in execute_pass_list_1 ../../gcc/passes.c:2570
#18 0x1eca9e4 in execute_pass_list(function*, opt_pass*)
../../gcc/passes.c:2580
#19 0x1162338 in cgraph_node::expand() ../../gcc/cgraphunit.c:2196
#20 0x11638ff in expand_all_functions ../../gcc/cgraphunit.c:2334
#21 0x1165f6e in symbol_table::compile() ../../gcc/cgraphunit.c:2685
#22 0x11669d4 in symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.c:2863
#23 0x22fe0f7 in compile_file ../../gcc/toplev.c:481
#24 0x2305493 in do_compile ../../gcc/toplev.c:2176
#25 0x2305ac1 in toplev::main(int, char**) ../../gcc/toplev.c:2311
#26 0x466210c in main ../../gcc/main.c:39
#27 0x7ffff608cfea in __libc_start_main ../csu/libc-start.c:308
#28 0x872bd9 in _start
(/home/marxin/Programming/gcc2/objdir/gcc/f951+0x872bd9)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
[Bug 63426] [meta-bug] Issues found with -fsanitize=undefined
>From gcc-bugs-return-627218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 07:52:35 2019
Return-Path: <gcc-bugs-return-627218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30769 invoked by alias); 2 Jan 2019 07:52: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 30686 invoked by uid 48); 2 Jan 2019 07:52:30 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88652] New: sel-sched.c:1545:11: runtime error: index 2 out of bounds for type 'long unsigned int [2]'
Date: Wed, 02 Jan 2019 07:52: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter blocked target_milestone
Message-ID: <bug-88652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00027.txt.bz2
Content-length: 3488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88652
Bug ID: 88652
Summary: sel-sched.c:1545:11: runtime error: index 2 out of
bounds for type 'long unsigned int [2]'
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Blocks: 85099
Target Milestone: ---
UBSAN GCC complains about:
$ ./xgcc -B.
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr87759.c -c -O
-fschedule-insns -fselective-scheduling -fno-tree-dce
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr87759.c: In
function ‘rc’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr87759.c:20:39:
warning: initialization of ‘__int128 unsigned *’ from incompatible pointer type
‘int *’ [-Wincompatible-pointer-types]
20 | unsigned __int128 *ar = &cc;
| ^
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr87759.c:29:54:
warning: right shift count >= width of type [-Wshift-count-overflow]
29 | y5 = (cc + 1) == ((*ar /= *oi) << ((zp >>= 128) / cc));
| ^~~
../../gcc/sel-sched.c:1545:11: runtime error: index 2 out of bounds for type
'long unsigned int [2]'
#0 0x1ed74cb in verify_target_availability ../../gcc/sel-sched.c:1545
#1 0x1ed7faf in find_best_reg_for_expr ../../gcc/sel-sched.c:1679
#2 0x1ee4ef9 in fill_vec_av_set ../../gcc/sel-sched.c:3797
#3 0x1ee6629 in fill_ready_list ../../gcc/sel-sched.c:4027
#4 0x1ee88a5 in find_best_expr ../../gcc/sel-sched.c:4387
#5 0x1ef18bb in fill_insns ../../gcc/sel-sched.c:5548
#6 0x1ef9ffb in schedule_on_fences ../../gcc/sel-sched.c:7364
#7 0x1efafa2 in sel_sched_region_2 ../../gcc/sel-sched.c:7502
#8 0x1efb3f2 in sel_sched_region_1 ../../gcc/sel-sched.c:7544
#9 0x1efc11b in sel_sched_region(int) ../../gcc/sel-sched.c:7645
#10 0x1efc353 in run_selective_scheduling() ../../gcc/sel-sched.c:7731
#11 0x1e86883 in rest_of_handle_sched ../../gcc/sched-rgn.c:3717
#12 0x1e86bde in execute ../../gcc/sched-rgn.c:3827
#13 0x1ba25da in execute_one_pass(opt_pass*) ../../gcc/passes.c:2483
#14 0x1ba2e70 in execute_pass_list_1 ../../gcc/passes.c:2569
#15 0x1ba2f25 in execute_pass_list_1 ../../gcc/passes.c:2570
#16 0x1ba2fc4 in execute_pass_list(function*, opt_pass*)
../../gcc/passes.c:2580
#17 0xe3a3f6 in cgraph_node::expand() ../../gcc/cgraphunit.c:2196
#18 0xe3b9bd in expand_all_functions ../../gcc/cgraphunit.c:2334
#19 0xe3e02c in symbol_table::compile() ../../gcc/cgraphunit.c:2685
#20 0xe3ea92 in symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.c:2863
#21 0x1ffa639 in compile_file ../../gcc/toplev.c:481
#22 0x20019d5 in do_compile ../../gcc/toplev.c:2176
#23 0x2002003 in toplev::main(int, char**) ../../gcc/toplev.c:2311
#24 0x4333837 in main ../../gcc/main.c:39
#25 0x7ffff6246fea in __libc_start_main ../csu/libc-start.c:308
#26 0x85b559 in _start
(/home/marxin/Programming/gcc2/objdir/gcc/cc1+0x85b559)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85099
[Bug 85099] [meta-bug] selective scheduling issues
>From gcc-bugs-return-627219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 08:15:35 2019
Return-Path: <gcc-bugs-return-627219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49606 invoked by alias); 2 Jan 2019 08:15: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 49481 invoked by uid 48); 2 Jan 2019 08:15:27 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] New: Is this a compiler bug?
Date: Wed, 02 Jan 2019 08:15: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev 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 attachments.created
Message-ID: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00028.txt.bz2
Content-length: 871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Bug ID: 88653
Summary: Is this a compiler bug?
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: mtekeev at yandex dot ru
Target Milestone: ---
Created attachment 45312
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45312&action=edit
A list of files that failed to compile.
Hello!
When I tried to compile some of the NIST tests using gfortran, I got an
"internal compiler error"message.
Maybe I'm doing something wrong?
When compiling with the help of compilers from Intel and Absoft there were no
problems.
A list of files that failed to compile are in the attachment.
Sincerely, Murat Tekeev
>From gcc-bugs-return-627220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 08:49:45 2019
Return-Path: <gcc-bugs-return-627220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129626 invoked by alias); 2 Jan 2019 08:49: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 129568 invoked by uid 55); 2 Jan 2019 08:49:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 08:49: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: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85574-4-dymYfRpLTY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00029.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jan 2 08:49:07 2019
New Revision: 267506
URL: https://gcc.gnu.org/viewcvs?rev=267506&root=gcc&view=rev
Log:
2019-01-02 Richard Biener <rguenther@suse.de>
PR ipa/85574
* ipa-icf.h (sem_item_optimizer::sort_congruence_split): Declare.
* ipa-icf.c (sem_item_optimizer::sort_congruence_split): New
function.
(sem_item_optimizer::do_congruence_step_f): Sort the congruence
set after UIDs before splitting them.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-icf.c
trunk/gcc/ipa-icf.h
>From gcc-bugs-return-627221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 08:54:04 2019
Return-Path: <gcc-bugs-return-627221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8987 invoked by alias); 2 Jan 2019 08: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 8906 invoked by uid 48); 2 Jan 2019 08:53:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] New: Hangs in libphobos testsuite
Date: Wed, 02 Jan 2019 08:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 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: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00030.txt.bz2
Content-length: 6505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
Bug ID: 88654
Summary: Hangs in libphobos testsuite
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
I've reinstalled my workstation with Fedora 29 x86_64 recently, and since that
both my 32-bit bootstraps hanged in libphobos testing (while 64-bit ones were
ok).
In both cases, I saw a stuck process:
25678 pts/6 Sl+ 0:00
/home/jakub/src/gcc/obj37/i686-pc-linux-gnu/libphobos/src/.libs/lt-unittest
std.net.curl
25679 pts/6 Z+ 0:00 [cat] <defunct>
When I've tried to attach to it, one thread is waiting in pthread_join
#0 0xf7fc3049 in __kernel_vsyscall ()
#1 0xf2cf1aa6 in __pthread_timedjoin_ex () from /lib/libpthread.so.0
#2 0xf2cf1898 in pthread_join () from /lib/libpthread.so.0
#3 0xf2ea1004 in core.thread.Thread.join(bool) (rethrow=true, this=0xf29ef180)
at ../../../../libphobos/libdruntime/core/thread.d:776
#4 thread_joinAll () at ../../../../libphobos/libdruntime/core/thread.d:2369
#5 0xf2ebfa5c in rt_term () at
../../../../libphobos/libdruntime/rt/dmain2.d:215
#6 0xf2ebfac9 in runAll (this=0xffd5b97c) at
../../../../libphobos/libdruntime/rt/dmain2.d:490
#7 0xf2ebf6f1 in tryExec (this=0xffd5b97c, dg=...) at
../../../../libphobos/libdruntime/rt/dmain2.d:461
#8 0xf2ebf8ee in _d_run_main (argc=2, argv=0xffd5ba74, mainFunc=0x8049810 <D
main>) at ../../../../libphobos/libdruntime/rt/dmain2.d:494
#9 0x08049281 in main (argc=2, argv=0xffd5ba74) at
/home/jakub/src/gcc/libphobos/libdruntime/__entrypoint.di:44
#10 0xf2b34c09 in __libc_start_main () from /lib/libc.so.6
#11 0x08049326 in _start ()
while the other one is stuck in:
#0 0xf7fc3049 in __kernel_vsyscall ()
#1 0xf2cfaf11 in accept () from /lib/libpthread.so.0
#2 0xf7233398 in std.socket.Socket.accept() (this=0xf29f0010) at
../../../../libphobos/src/std/socket.d:2876
#3 0xf6b64e47 in std.net.curl.TestServer.loop(shared(std.socket.TcpSocket))
(listener=0xf29f0010) at ../../../../libphobos/src/std/net/curl.d:205
#4 0xf6b81daa in std.concurrency.exec (this=0xf29f0060) at
/home/jakub/src/gcc/libphobos/src/std/concurrency.d:506
#5 0xf2e9e547 in core.thread.Thread.run() (this=0xf29ef180) at
../../../../libphobos/libdruntime/core/thread.d:1469
#6 core.thread.Thread.run() (this=0xf29ef180) at
../../../../libphobos/libdruntime/core/thread.d:1461
#7 thread_entryPoint (arg=<optimized out>) at
../../../../libphobos/libdruntime/core/thread.d:400
#8 0xf2cf05de in start_thread () from /lib/libpthread.so.0
#9 0xf2c0697a in clone () from /lib/libc.so.6
When I try to run it by hand it showed a clue, but hanged anyway:
.libs/lt-unittest std.net.curl
****** FAIL release32 std.net.curl
std.net.curl.CurlException@../../../../libphobos/src/std/net/curl.d(4188):
Failed to load curl, tried "libcurl.so", "libcurl.so.4", "libcurl-gnutls.so.4",
"libcurl-nss.so.4", "libcurl.so.3".
----------------
/home/jakub/src/gcc/libphobos/src/std/exception.d:420 pure @safe void
std.exception.bailOut!(std.net.curl.CurlException).bailOut(immutable(char)[],
uint, const(char[])) [0xf6bb1f08]
/home/jakub/src/gcc/libphobos/src/std/exception.d:388 pure @safe bool
std.exception.enforce!(std.net.curl.CurlException, bool).enforce(bool, lazy
const(char)[], immutable(char)[], uint) [0xf6b737e5]
../../../../libphobos/src/std/net/curl.d:4188 void*
std.net.curl.CurlAPI.loadAPI() [0xf6b6bc40]
../../../../libphobos/src/std/net/curl.d:4135 __dgliteral1 [0xf6b6bab2]
/home/jakub/src/gcc/libphobos/src/std/concurrency.d:2422 __dgliteral2
[0xf6bdd299]
/home/jakub/src/gcc/libphobos/src/std/concurrency.d:2493 ref void*
std.concurrency.initOnce!(std.net.curl.CurlAPI._handle).initOnce(lazy void*,
core.sync.mutex.Mutex) [0xf6bdd212]
/home/jakub/src/gcc/libphobos/src/std/concurrency.d:2422 ref void*
std.concurrency.initOnce!(std.net.curl.CurlAPI._handle).initOnce(lazy void*)
[0xf6b73a1b]
../../../../libphobos/src/std/net/curl.d:4135 ref @property
std.net.curl.CurlAPI.API std.net.curl.CurlAPI.instance() [0xf6b6ba89]
../../../../libphobos/src/std/net/curl.d:4245 ref @property
std.net.curl.CurlAPI.API std.net.curl.Curl.curl() [0xf6b629d6]
../../../../libphobos/src/std/net/curl.d:4268 void
std.net.curl.Curl.initialize() [0xf6b64d95]
../../../../libphobos/src/std/net/curl.d:2547 void
std.net.curl.HTTP.initialize() [0xf6b6430f]
../../../../libphobos/src/std/net/curl.d:2520 std.net.curl.HTTP
std.net.curl.HTTP.opCall() [0xf6b5e8d2]
../../../../libphobos/src/std/net/curl.d:416 void
std.net.curl.download!(std.net.curl.AutoProtocol).download(const(char)[],
immutable(char)[], std.net.curl.AutoProtocol) [0xf6b6e764]
../../../../libphobos/src/std/net/curl.d:433 void
std.net.curl.__unittestL420_2() [0xf6b5e292]
/home/jakub/src/gcc/obj37/i686-pc-linux-gnu/libphobos/src/<no_file>:1 void
std.net.curl.__modtest() [0xf6b6d5d9]
../../../../libphobos/libdruntime/../testsuite/test_runner.d:58 void
test_runner.doTest(object.ModuleInfo*, ref bool) [0x80495eb]
../../../../libphobos/libdruntime/../testsuite/test_runner.d:30 bool
test_runner.testModules() [0x8049736]
../../../../libphobos/libdruntime/core/runtime.d:570 runModuleUnitTests
[0xf2e92b44]
../../../../libphobos/libdruntime/rt/dmain2.d:485 runAll [0xf2eb8aec]
../../../../libphobos/libdruntime/rt/dmain2.d:461 tryExec [0xf2eb86f0]
../../../../libphobos/libdruntime/rt/dmain2.d:494 _d_run_main [0xf2eb88ed]
/home/jakub/src/gcc/libphobos/libdruntime/__entrypoint.di:44 main [0x8049280]
??:? __libc_start_main [0xf2b2ec08]
??:? _start [0x8049325]
??:? ???[0xffffffff]
Indeed, I had just 64-bit libcurl.so.4 installed, not 32-bit libcurl.so.4 and
installing the latter makes the command run from the command line succeed.
The reason I'm filing this is that there are multiple issues:
1) what I'm worried about most is that the timeouts for tests don't work, it
happens that some test gets stuck, but it should be killed after 5 minutes or
for how long the default timeout is set and the set should FAIL in that case or
something similar
2) if Curl fails to initialize, the test shouldn't get stuck
3) and, if libcurl isn't available, I think it would be better to skip the test
as UNSUPPORTED, i.e. add some effective-target that tests if libcurl is
available and if it fails, don't even try to run the test
>From gcc-bugs-return-627222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:19:57 2019
Return-Path: <gcc-bugs-return-627222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74423 invoked by alias); 2 Jan 2019 09:19: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 74346 invoked by uid 48); 2 Jan 2019 09:19:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88575] gcc got confused by different comparison operators
Date: Wed, 02 Jan 2019 09:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88575-4-4maAT4rA06@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00031.txt.bz2
Content-length: 1257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88575
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. Even with -ffast-math on GIMPLE we fail to elide the MIN_EXPR in
both functions (test has a_2(D) < b_3(D)). When doing integer operations
VRP manages to elide those. Given we have no such thing as value-range
propagation for floats the closest we have is DOM/VN registering the
conditions and MIN_EXPR VN "failing" to lookup whether a<=b is known.
<bb 2> [local count: 1073741825]:
if (a_2(D) <= b_3(D))
goto <bb 3>; [34.00%]
else
goto <bb 4>; [66.00%]
<bb 3> [local count: 365072220]:
_4 = MIN_EXPR <a_2(D), b_3(D)>;
<bb 4> [local count: 1073741825]:
# _1 = PHI <_4(3), 0.0(2)>
return _1;
>From gcc-bugs-return-627223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:25:59 2019
Return-Path: <gcc-bugs-return-627223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86014 invoked by alias); 2 Jan 2019 09:25:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85961 invoked by uid 48); 2 Jan 2019 09:25:55 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88602] Consider adding ext_vector_type for better clang compatibility
Date: Wed, 02 Jan 2019 09:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88602-4-l9oCxjm0i6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88602-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88602-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00032.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88602
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
It turns out that ext_vector_type attribute is not only about declaring vector
variable but also affects semantics. Brief documentation is in
https://clang.llvm.org/docs/LanguageExtensions.html#vectors-and-extended-vectors
and see also discussion in
http://hubicka.blogspot.com/2018/12/even-more-fun-with-building-and.html
I can confirm that Skia code is somewhat more compact/ergonomic with the
extension though i still do not fully understand the design.
>From gcc-bugs-return-627224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:26:20 2019
Return-Path: <gcc-bugs-return-627224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87091 invoked by alias); 2 Jan 2019 09:26: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 87032 invoked by uid 48); 2 Jan 2019 09:26:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88576] -fno-math-errno causes GCC to consider that malloc does not set errno
Date: Wed, 02 Jan 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88576-4-ytTyrzhg5t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00033.txt.bz2
Content-length: 1223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88576
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #6)
> Has this got to do anything with errno? It seems to me that with
> -fno-math-errno, GCC assumes that malloc does not set *any* TLS variable.
> That doesn't look right to me.
GCC assumes that memory allocation does not affect global heap state.
That's correct unless you compile the memory allocator itself.
Note the original "alias" with -fno-math-errno was probably too lazy but
allocations being a barrier for any load/store of global memory is quite
bad for optimization in _fortran_ (which has no business with errno)
where we (unfortunately) also get everything passed by reference.
I'll introduce -f[no-]alloc-errno, defaulted to the -f[no-]math-errno
state and enabled at -Ofast (but not with -ffast-math).
>From gcc-bugs-return-627225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:26:34 2019
Return-Path: <gcc-bugs-return-627225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87943 invoked by alias); 2 Jan 2019 09:26: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 87848 invoked by uid 55); 2 Jan 2019 09:26:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88561] [8/9 Regression] PGO devirtualization miscompilation of firefox
Date: Wed, 02 Jan 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88561-4-Juqf8gzNGk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88561-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88561-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00034.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88561
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 2 09:25:59 2019
New Revision: 267507
URL: https://gcc.gnu.org/viewcvs?rev=267507&root=gcc&view=rev
Log:
PR ipa/88561
* g++.dg/tree-prof/devirt.C: Expect _ZThn16 only for lp64 and llp64
targets and expect _ZThn8 for ilp32 targets.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/tree-prof/devirt.C
>From gcc-bugs-return-627227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:46:47 2019
Return-Path: <gcc-bugs-return-627227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109355 invoked by alias); 2 Jan 2019 09:46:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109309 invoked by uid 48); 2 Jan 2019 09:46:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88440] size optimization of memcpy-like code
Date: Wed, 02 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88440-4-CCmvFAUy9Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88440-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88440-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00036.txt.bz2
Content-length: 673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88440
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45313
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45313&action=edit
patch
This enables distribution of patterns at -O[2s]+ and optimizes the testcase
at -Os by adjusting the guards in loop distribution.
Note that the interesting bits are compile-time, binary-size and performance
at mainly -O2, eventually size at -Os.
I suspect that at -O2 w/o profiling most loops would be optimize_loop_for_speed
anyways so changing the heuristics isn't so bad but of course enabling
distribution at -O2 might encour a penalty.
>From gcc-bugs-return-627226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:46:15 2019
Return-Path: <gcc-bugs-return-627226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108547 invoked by alias); 2 Jan 2019 09:46:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108515 invoked by uid 48); 2 Jan 2019 09:46:11 -0000
From: "dominique.pelle at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88655] New: Different overloaded function being called depending on which compiler is used
Date: Wed, 02 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominique.pelle 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-88655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00035.txt.bz2
Content-length: 2789
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88655
Bug ID: 88655
Summary: Different overloaded function being called depending
on which compiler is used
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dominique.pelle at gmail dot com
Target Milestone: ---
The following program behaves differently
between gcc and clang. Overloaded function
foo(...) gets resolved differently depending
on which compiler is used. It outputs
3 different kinds of outputs depending on
which compiler or compiler version is used:
$ cat foo.cpp
#include <cstdio>
#include <cstdint>
struct Foo
{
Foo(std::int64_t)
{
}
};
void foo(const char*)
{
std::puts("In foo(const char*)");
}
void foo(const Foo&)
{
std::puts("In foo(const Foo&)");
}
int main()
{
foo((int)0);
foo((unsigned)0);
foo((short)0);
foo((unsigned short)0);
foo((std::int64_t)0);
foo((std::uint64_t)0);
foo(0);
foo(NULL);
foo(nullptr);
}
With g++-8 (Ubuntu 8.1.0-5ubuntu1~16.04) 8.1.0
or g++-7 (Ubuntu 7.4.0-1ubuntu1~16.04~ppa1) 7.4.0
or g++-6 (Ubuntu 6.5.0-2ubuntu1~16.04) 6.5.0 20181026
$ g++-8 -std=c++11 foo.cpp
$ ./a.out
In foo(const Foo&)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
With g++-5 (Ubuntu 5.4.0-6ubuntu1~16.04.11) 5.4.0 20160609:
$ g++-5 -std=c++11 foo.cpp
$ ./a.out
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
Notice that the first call results in a different overload being called.
With clang version 7.0.0-svn338141-1~exp1+0~20180727181251.1677~1.gbpcccb1b
(trunk)
or clang version 6.0.1-svn334776-1~exp1~20181018153226.114
(branches/release_60)
or clang version 5.0.2 (tags/RELEASE_502/final)
or clang version 4.0.0-1ubuntu1~16.04.2 (tags/RELEASE_400/rc1)
or clang version 3.9.1-4ubuntu3~16.04.2 (tags/RELEASE_391/rc2)
$ clang++-7 -std=c++11 foo.cpp
$ ./a.out
In foo(const Foo&)
In foo(const Foo&)
In foo(const Foo&)
In foo(const Foo&)
In foo(const Foo&)
In foo(const Foo&)
In foo(const char*)
In foo(const char*)
In foo(const char*)
Notice that clang resolve overload completely differently
than any version of gcc!?
I initially reported this as a clang bug in
https://bugs.llvm.org/show_bug.cgi?id=40193
albeit with a different program, which I decided
to simplify here to avoid a boost dependency.
According to comments in the clang ticket, it's
a gcc bug. Hence this bug report.
>From gcc-bugs-return-627228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 09:55:07 2019
Return-Path: <gcc-bugs-return-627228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81290 invoked by alias); 2 Jan 2019 09:55:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80760 invoked by uid 48); 2 Jan 2019 09:55:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Wed, 02 Jan 2019 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88598-4-7zbVq4P0HH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00037.txt.bz2
Content-length: 1009
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
CC| |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue for bar() is that we do not have constant folding for
<bb 2> [local count: 894749062]:
vect__5.23_41 = MEM[(const float *)v_16(D)];
vect__6.24_42 = vect__5.23_41 * { 0.0, 1.0e+0, 0.0, 0.0 };
stmp_ret_17.26_45 = .REDUC_PLUS (vect__6.24_42); [tail call]
return stmp_ret_17.26_45;
fold-const-call.c would be the place to amend with the various IFNs
we accumulated.
>From gcc-bugs-return-627229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:05:35 2019
Return-Path: <gcc-bugs-return-627229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96511 invoked by alias); 2 Jan 2019 10:05:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95574 invoked by uid 48); 2 Jan 2019 10:05:31 -0000
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88656] New: [7/8/9 Regression] lr clobbered by thumb prologue before __builtin_return_address(0) reads from it
Date: Wed, 02 Jan 2019 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00038.txt.bz2
Content-length: 1606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88656
Bug ID: 88656
Summary: [7/8/9 Regression] lr clobbered by thumb prologue
before __builtin_return_address(0) reads from it
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: aoliva at gcc dot gnu.org
Target Milestone: ---
Target: arm-none-eabi
Alas, the fix for bug 77933 broke __builtin_return_address(0) in both leaf and
non-leaf functions on ARM -mthumb, because lr is now more likely to be used as
a scratch register to save other high registers, but then its value is used in
__builtin_return_address(0) as if it still held the return address.
This remains broken in GCC9 (I've just tried r267435).
Add "r4" to the clobber list, or compile the original testcase with
-fno-omit-frame-pointer, to get:
push {r[47], lr}
mov lr, r9
mov r[47], r8
push {r[47], lr}
[ add r7, sp, #0 ];; -fno-omit-frame-pointer only
mov r0, lr
Add a call to e.g. bar() between the asm and the return, and you'll also see lr
overwritten and then used as if it still held the return address:
push {r4, lr}
mov lr, r9
mov r4, r8
push {r4, lr}
mov r4, lr
bl bar
movs r0, r4
Before the patch for PR 77933, lr would not be overwritten before use in any of
these cases.
>From gcc-bugs-return-627230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:07:31 2019
Return-Path: <gcc-bugs-return-627230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100380 invoked by alias); 2 Jan 2019 10:07:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99659 invoked by uid 48); 2 Jan 2019 10:07:27 -0000
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/77933] Stack corruption on ARM when using high registers and __builtin_return_address
Date: Wed, 02 Jan 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: thomas.preudhomme at celest dot fr
X-Bugzilla-Target-Milestone: 5.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-77933-4-AZjKUtkM3y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00039.txt.bz2
Content-length: 447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77933
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
--- Comment #10 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
Bug 88656 is a regression introduced by the fix for this one.
>From gcc-bugs-return-627231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:13:46 2019
Return-Path: <gcc-bugs-return-627231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10042 invoked by alias); 2 Jan 2019 10:13: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 9999 invoked by uid 48); 2 Jan 2019 10:13:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88578] Static C++ objects with flexible array members overlap when initializes are non-const
Date: Wed, 02 Jan 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88578-4-4muIaeOxF2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88578-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88578-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00040.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88578
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
So that means DECL_SIZE is not properly updated by the FE?
>From gcc-bugs-return-627232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:16:24 2019
Return-Path: <gcc-bugs-return-627232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13990 invoked by alias); 2 Jan 2019 10:16: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 13929 invoked by uid 48); 2 Jan 2019 10:16:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88585] [9 Regression] ICE in fld_incomplete_type_of, at tree.c:5295
Date: Wed, 02 Jan 2019 10:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88585-4-sMNu0YTfDA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88585-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88585-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00041.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88585
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Target Milestone|--- |9.0
>From gcc-bugs-return-627233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:17:51 2019
Return-Path: <gcc-bugs-return-627233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15361 invoked by alias); 2 Jan 2019 10:17: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 15279 invoked by uid 48); 2 Jan 2019 10:17:47 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88655] Different overloaded function being called depending on which compiler is used
Date: Wed, 02 Jan 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88655-4-YiGL9oM8tu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00042.txt.bz2
Content-length: 926
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88655
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Using C++98 (on a LP64 target) and:
typedef unsigned long uint64_t;
typedef long int64_t;
struct Foo { Foo(int64_t) { } };
void foo(const char*)
{
std::puts("In foo(const char*)");
}
void foo(const Foo&)
{
std::puts("In foo(const Foo&)");
}
int main()
{
foo((int)0);
foo((unsigned)0);
foo((short)0);
foo((unsigned short)0);
foo((int64_t)0);
foo((uint64_t)0);
foo(0);
foo(NULL);
}
--- CUT ---
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
As you can see that is the "old" behavior.
With -std=c++11, I get:
In foo(const Foo&)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
In foo(const char*)
>From gcc-bugs-return-627234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:20:31 2019
Return-Path: <gcc-bugs-return-627234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18805 invoked by alias); 2 Jan 2019 10:20:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18732 invoked by uid 48); 2 Jan 2019 10:20:28 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88655] Different overloaded function being called depending on which compiler is used
Date: Wed, 02 Jan 2019 10:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: dependson
Message-ID: <bug-88655-4-em8KVyjEi2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00043.txt.bz2
Content-length: 596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88655
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |52145
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Most likely a dup of bug 52145 and related to PR 77712.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52145
[Bug 52145] [C++11] [DR 903] zero-valued integer constant expression should
prefer conversion to pointer
>From gcc-bugs-return-627235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:25:23 2019
Return-Path: <gcc-bugs-return-627235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50948 invoked by alias); 2 Jan 2019 10:25: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 50880 invoked by uid 48); 2 Jan 2019 10:25:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] cleanup_cfg may make cached dominance info stale
Date: Wed, 02 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88593-4-dcZHhiWTXC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00044.txt.bz2
Content-length: 1492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #4)
> It seems to avoid this sort of gotchas cleanup_cfg should
>
> gcc_checking_assert (!dom_info_available_p (CDI_DOMINATORS));
> gcc_checking_assert (!dom_info_available_p (CDI_POST_DOMINATORS));
>
> but maybe there's a deeper reason it's not done already — I cannot be sure.
It already does it in a not always executed path:
/* ??? We probably do this way too often. */
if (current_loops
&& (changed
|| (mode & CLEANUP_CFG_CHANGED)))
{
timevar_push (TV_REPAIR_LOOPS);
/* The above doesn't preserve dominance info if available. */
gcc_assert (!dom_info_available_p (CDI_DOMINATORS));
calculate_dominance_info (CDI_DOMINATORS);
hardening this contract might be a good idea but expect some fallout. I
think the correct mode-switching local fix is to do
diff --git a/gcc/mode-switching.c b/gcc/mode-switching.c
index ef6f6e1984c..2ff21a40081 100644
--- a/gcc/mode-switching.c
+++ b/gcc/mode-switching.c
@@ -856,7 +856,10 @@ optimize_mode_switching (void)
commit_edge_insertions ();
if (targetm.mode_switching.entry && targetm.mode_switching.exit)
- cleanup_cfg (CLEANUP_NO_INSN_DEL);
+ {
+ free_dominance_info (CDI_DOMINATORS);
+ cleanup_cfg (CLEANUP_NO_INSN_DEL);
+ }
else if (!need_commit && !emitted)
return 0;
>From gcc-bugs-return-627236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:25:41 2019
Return-Path: <gcc-bugs-return-627236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53615 invoked by alias); 2 Jan 2019 10:25: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 53560 invoked by uid 48); 2 Jan 2019 10:25:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Wed, 02 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority short_desc
Message-ID: <bug-88593-4-NmdhJPpJS2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00045.txt.bz2
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Summary|cleanup_cfg may make cached |[9 Regression] cleanup_cfg
|dominance info stale |may make cached dominance
| |info stale
>From gcc-bugs-return-627237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:26:13 2019
Return-Path: <gcc-bugs-return-627237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60077 invoked by alias); 2 Jan 2019 10:26:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60041 invoked by uid 48); 2 Jan 2019 10:26:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88594] [9 Regression] ICE in int_mode_for_mode, at stor-layout.c:403
Date: Wed, 02 Jan 2019 10:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88594-4-Ccx5ya0bs6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00046.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88594
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Target Milestone|--- |9.0
>From gcc-bugs-return-627238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:27:16 2019
Return-Path: <gcc-bugs-return-627238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66748 invoked by alias); 2 Jan 2019 10:27: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 65983 invoked by uid 48); 2 Jan 2019 10:27:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88596] [9 Regression] ICE: Maximum number of LRA assignment passes is achieved (30)
Date: Wed, 02 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: 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-88596-4-na3ftLgeXQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88596-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88596-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00047.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88596
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:30:53 2019
Return-Path: <gcc-bugs-return-627239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99278 invoked by alias); 2 Jan 2019 10:30: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 94039 invoked by uid 48); 2 Jan 2019 10:30:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88597] Compile time hog w/ -O1 -fpeel-loops
Date: Wed, 02 Jan 2019 10:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on version assigned_to everconfirmed
Message-ID: <bug-88597-4-fX47NQFKYa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88597-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88597-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00048.txt.bz2
Content-length: 938
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88597
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
Version|4.6.0 |9.0
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The interesting part is of couse that =26 is fast but =27 is slow... likely
because after completely peeling the inner loop the outer loop is starting to
be peeled and analysis on _that_ body is taking forever for some reason
(well, quadratic analysis in SCEV which isn't guarded "properly" everywhere).
Mine.
>From gcc-bugs-return-627241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:34:35 2019
Return-Path: <gcc-bugs-return-627241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8156 invoked by alias); 2 Jan 2019 10:34: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 8108 invoked by uid 48); 2 Jan 2019 10:34:31 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88602] Consider adding ext_vector_type for better clang compatibility
Date: Wed, 02 Jan 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version bug_severity
Message-ID: <bug-88602-4-0dorTeZkFH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88602-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88602-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00050.txt.bz2
Content-length: 354
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88602
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Severity|normal |enhancement
>From gcc-bugs-return-627240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:34:24 2019
Return-Path: <gcc-bugs-return-627240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7404 invoked by alias); 2 Jan 2019 10:34: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 7349 invoked by uid 48); 2 Jan 2019 10:34:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88601] We may consider adding __builtin_convertvector and __builtin_shufflevector for better compaitbility with Clang
Date: Wed, 02 Jan 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version bug_severity
Message-ID: <bug-88601-4-o3xy6sUNhp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88601-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88601-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00049.txt.bz2
Content-length: 354
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88601
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Severity|normal |enhancement
>From gcc-bugs-return-627242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:40:56 2019
Return-Path: <gcc-bugs-return-627242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12962 invoked by alias); 2 Jan 2019 10:40:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12932 invoked by uid 48); 2 Jan 2019 10:40:52 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88578] Static C++ objects with flexible array members overlap when initializes are non-const
Date: Wed, 02 Jan 2019 10:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88578-4-ClNNLDfvql@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88578-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88578-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00051.txt.bz2
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88578
--- Comment #3 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
(In reply to Richard Biener from comment #2)
> So that means DECL_SIZE is not properly updated by the FE?
that is generally not done, and I can't tell if it is right
or wrong, since sizeof(s) should not include the flexible array.
Normally varasm.c works around this because it sees the
additional CONSTRUCTOR elements and assembles them.
But in this case the FE strips the non-constant initializers
from the decl and generates code to initialize them.
Everything would work if at least the final element of the
flexible array is assembled as zero.
That can be seen in the example, when the flexible arrays
are initilialized with a constant as last element, the code works:
static Ax s = { 3, { i, j, k, 0 } };
>From gcc-bugs-return-627243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:42:00 2019
Return-Path: <gcc-bugs-return-627243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14019 invoked by alias); 2 Jan 2019 10:42: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 13980 invoked by uid 48); 2 Jan 2019 10:41:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88603] optimization missed for saturation arithmetic add
Date: Wed, 02 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc version everconfirmed
Message-ID: <bug-88603-4-n7d4HfWyL7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88603-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88603-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00052.txt.bz2
Content-length: 2464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88603
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
CC| |rguenth at gcc dot gnu.org
Version|unknown |8.2.1
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. GCC "optimized" the code to
<bb 2> [local count: 1073741825]:
_1 = (long unsigned int) a_4(D);
_2 = (long unsigned int) b_5(D);
tmp_6 = _1 + _2;
if (tmp_6 > 4294967295)
goto <bb 4>; [21.72%]
else
goto <bb 3>; [78.28%]
<bb 3> [local count: 840525100]:
_7 = a_4(D) + b_5(D);
<bb 4> [local count: 1073741825]:
# _3 = PHI <_7(3), 4294967295(2)>
return _3;
forwprop1 does this already by means of narrowing patterns in match.pd:
/* Narrowing of arithmetic and logical operations.
These are conceptually similar to the transformations performed for
the C/C++ front-ends by shorten_binary_op and shorten_compare. Long
term we want to move all that code out of the front-ends into here. */
/* If we have a narrowing conversion of an arithmetic operation where
both operands are widening conversions from the same type as the outer
narrowing conversion. Then convert the innermost operands to a suitable
unsigned type (to avoid introducing undefined behavior), perform the
operation and convert the result to the desired type. */
(for op (plus minus)
(simplify
(convert (op:s (convert@2 @0) (convert?@3 @1)))
...
(convert (op (convert:utype @0)
(convert:utype @1))))))))
here :s is not effective for your testcase since there's no extra
conversions in the end. Disabling this yields
<bb 2> [local count: 1073741825]:
_1 = (long unsigned int) a_4(D);
_2 = (long unsigned int) b_5(D);
tmp_6 = _1 + _2;
_10 = MIN_EXPR <tmp_6, 4294967295>;
_3 = (uint32_t) _10;
and not much better code in the end:
saturation_add:
.LFB4:
.cfi_startproc
movl %edi, %edi
movl %esi, %eax
movl $4294967295, %edx
addq %rdi, %rax
cmpq %rdx, %rax
cmova %rdx, %rax
ret
>From gcc-bugs-return-627244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:42:56 2019
Return-Path: <gcc-bugs-return-627244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15045 invoked by alias); 2 Jan 2019 10:42:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15007 invoked by uid 48); 2 Jan 2019 10:42:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88604] Initializing constexpr array consumes all memory
Date: Wed, 02 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88604-4-V2hsYyWMtp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88604-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88604-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00053.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88604
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |compile-time-hog,
| |memory-hog
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
IIRC things improved for GCC 9 (recently).
>From gcc-bugs-return-627245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:49:18 2019
Return-Path: <gcc-bugs-return-627245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73916 invoked by alias); 2 Jan 2019 10:49:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73842 invoked by uid 48); 2 Jan 2019 10:49:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88605] vector extensions: Widening or conversion generates inefficient or scalar code.
Date: Wed, 02 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88605-4-SziLRZwzjC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88605-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88605-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00054.txt.bz2
Content-length: 1691
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88605
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I agree we should try to optimize this patterns. Note we have proper tree
codes for this but they are currently only emitted by the vectorizer because
expansion only works when target support is available.
Patterns to detect are a bit awkward thus our kitchen-sink forwprop pass
is the place to implement this pattern matching:
vconvert_u64_u32 (U32x2 v)
{
unsigned int _1;
long long unsigned int _2;
unsigned int _3;
long long unsigned int _4;
U64x2 _6;
<bb 2> [local count: 1073741825]:
_1 = BIT_FIELD_REF <v_7(D), 32, 0>;
_2 = (long long unsigned int) _1;
_3 = BIT_FIELD_REF <v_7(D), 32, 32>;
_4 = (long long unsigned int) _3;
_6 = {_2, _4};
return _6;
so the keying should be on the CONSTRUCTORs (watch out for constants
eventually propagated...). See simplify_vector_constructor which
currently tries to detect a permutation only. Enhancing that to handle
an intermediate conversion shouldn't be too difficult (it already seems
to handle a few cases but not widening/shortening ones).
There might be duplicates of this bug...
>From gcc-bugs-return-627246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:49:51 2019
Return-Path: <gcc-bugs-return-627246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74777 invoked by alias); 2 Jan 2019 10:49: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 74716 invoked by uid 48); 2 Jan 2019 10:49:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88606] ICE: verify_type failed (error: type variant differs by TYPE_TRANSPARENT_AGGR)
Date: Wed, 02 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka 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-88606-4-VF1zoyK7Ov@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00055.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88606
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Honza?
>From gcc-bugs-return-627247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:51:20 2019
Return-Path: <gcc-bugs-return-627247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76485 invoked by alias); 2 Jan 2019 10:51:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76425 invoked by uid 48); 2 Jan 2019 10:51:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Wed, 02 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-88611-4-UUcc7HAJ3o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00056.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|2018-12-27 00:00:00 |2019-01-02
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-627248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:52:07 2019
Return-Path: <gcc-bugs-return-627248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77571 invoked by alias); 2 Jan 2019 10:52:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77482 invoked by uid 48); 2 Jan 2019 10:52:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88613] [9 Regression] ICE in size_binop_loc at fold-const.c:1900 since r267272
Date: Wed, 02 Jan 2019 10:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88613-4-tH1n38J0hc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00057.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88613
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Target Milestone|--- |9.0
>From gcc-bugs-return-627251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:53:52 2019
Return-Path: <gcc-bugs-return-627251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86829 invoked by alias); 2 Jan 2019 10:53: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 86703 invoked by uid 48); 2 Jan 2019 10:53:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88620] [7/8/9 Regression] ICE in assign_stack_temp_for_type, at function.c:837
Date: Wed, 02 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88620-4-YhgVIQMDkE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00060.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
>From gcc-bugs-return-627249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:53:00 2019
Return-Path: <gcc-bugs-return-627249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84750 invoked by alias); 2 Jan 2019 10:53:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84676 invoked by uid 48); 2 Jan 2019 10:52:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88616] [9 Regression] ICE in gimplify_expr at gcc/gimplify.c:13363
Date: Wed, 02 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88616-4-IFSiz96Ybf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00058.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88616
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:53:41 2019
Return-Path: <gcc-bugs-return-627250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86004 invoked by alias); 2 Jan 2019 10:53:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85910 invoked by uid 48); 2 Jan 2019 10:53:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88619] [9 Regression] ICE in asan_emit_stack_protection, at asan.c:1574 since r266664
Date: Wed, 02 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88619-4-ycGqDYYxme@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00059.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88619
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 10:59:12 2019
Return-Path: <gcc-bugs-return-627252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91240 invoked by alias); 2 Jan 2019 10:59: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 91153 invoked by uid 48); 2 Jan 2019 10:59:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88621] [9 Regression] wrong code at -O1 and above on x86_64-linux-gnu in 64-bit mode (not in 32-bit mode)
Date: Wed, 02 Jan 2019 10:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status version assigned_to
Message-ID: <bug-88621-4-6db1ydx39k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88621-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88621-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00061.txt.bz2
Content-length: 614
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88621
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|NEW |ASSIGNED
Version|unknown |9.0
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
Oops. And more cut&paste errors in the change...
>From gcc-bugs-return-627253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:04:56 2019
Return-Path: <gcc-bugs-return-627253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100249 invoked by alias); 2 Jan 2019 11:04: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 100165 invoked by uid 48); 2 Jan 2019 11:04:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87545] [9 Regression] -mtune=intel regressions
Date: Wed, 02 Jan 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: 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-87545-4-W2rWjHPaVD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87545-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87545-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00062.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87545
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:05:20 2019
Return-Path: <gcc-bugs-return-627254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101275 invoked by alias); 2 Jan 2019 11:05:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101212 invoked by uid 55); 2 Jan 2019 11:05:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87545] [9 Regression] -mtune=intel regressions
Date: Wed, 02 Jan 2019 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87545-4-h5ZEYYV4Wm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87545-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87545-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00063.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87545
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jan 2 11:04:45 2019
New Revision: 267509
URL: https://gcc.gnu.org/viewcvs?rev=267509&root=gcc&view=rev
Log:
2019-01-02 Richard Biener <rguenther@suse.de>
PR target/87545
* config/i386/x86-tune-costs.h (intel_cost): Adjust
cost of cheap SSE instruction.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/x86-tune-costs.h
>From gcc-bugs-return-627255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:05:46 2019
Return-Path: <gcc-bugs-return-627255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102162 invoked by alias); 2 Jan 2019 11:05: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 102110 invoked by uid 48); 2 Jan 2019 11:05:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/88657] New: Come up with filter column 'untouched' for GCC bugs
Date: Wed, 02 Jan 2019 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00064.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88657
Bug ID: 88657
Summary: Come up with filter column 'untouched' for GCC bugs
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
As requested in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86315#c17, I'm
creating a separate bug for it.
>From gcc-bugs-return-627256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:07:04 2019
Return-Path: <gcc-bugs-return-627256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109322 invoked by alias); 2 Jan 2019 11:07:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105523 invoked by uid 48); 2 Jan 2019 11:07:00 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/88657] Come up with filter column 'untouched' for GCC bugs
Date: Wed, 02 Jan 2019 11:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: LpSolit at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on see_also assigned_to everconfirmed
Message-ID: <bug-88657-4-Pk9vaYE4mf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00065.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88657
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
See Also| |https://bugzilla.mozilla.or
| |g/show_bug.cgi?id=743883
Assignee|unassigned at gcc dot gnu.org |LpSolit at gmail dot com
Ever confirmed|0 |1
>From gcc-bugs-return-627257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:09:58 2019
Return-Path: <gcc-bugs-return-627257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122694 invoked by alias); 2 Jan 2019 11:09: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 122638 invoked by uid 48); 2 Jan 2019 11:09:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88623] gcc build uses CXX_FOR_BUILD but files have .c extension
Date: Wed, 02 Jan 2019 11:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88623-4-oWuID06PFp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88623-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88623-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00066.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88623
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
why would a C++ compiler ever compile sth as C?
>From gcc-bugs-return-627258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:12:31 2019
Return-Path: <gcc-bugs-return-627258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125889 invoked by alias); 2 Jan 2019 11:12:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125689 invoked by uid 48); 2 Jan 2019 11:12:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88626] __builtin_constant_p should be as cheap as dead code for inlining purposes
Date: Wed, 02 Jan 2019 11:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88626-4-e06KNttYOL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00067.txt.bz2
Content-length: 751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88626
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
The __builtin_constant_p call itself is "free" but whether guarded code is
"free" isn't easy to determine. I guess what you want is the computation
of "b" which is only used when it is constant is considered "free"?
Confirmed for that. Not sure how easy to implement though.
>From gcc-bugs-return-627259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:17:06 2019
Return-Path: <gcc-bugs-return-627259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2716 invoked by alias); 2 Jan 2019 11:17:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2658 invoked by uid 48); 2 Jan 2019 11:17:02 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Wed, 02 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.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-88653-4-Ud3zzwrrA7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00068.txt.bz2
Content-length: 705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-02
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I guess that the files are coming from
http://mysite.verizon.net/serveall/NISTtest.tar.gz.
All the tests succeed for me (except a small glitch for FM308.f, I'll report
elsewhere). What is the output of 'gfortran -v'?
>From gcc-bugs-return-627260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:22:44 2019
Return-Path: <gcc-bugs-return-627260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10771 invoked by alias); 2 Jan 2019 11:22:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10727 invoked by uid 48); 2 Jan 2019 11:22:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/58770] GCC very slow compiling with #pragma once
Date: Wed, 02 Jan 2019 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords: easyhack
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
Message-ID: <bug-58770-4-pbJBwfq7Oq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00069.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58770
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |easyhack
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Tom Tromey from comment #3)
> One possible fix might be to use a hash table rather than a
> linked list for finding potential duplicates.
I'm adding the "easyhack" keyword, because Tom's suggestion above seems
sensible and probably isn't too hard to do.
>From gcc-bugs-return-627261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:28:33 2019
Return-Path: <gcc-bugs-return-627261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28498 invoked by alias); 2 Jan 2019 11:28: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 28389 invoked by uid 48); 2 Jan 2019 11:28:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88631] CTAD cannot deduce from () value initialization
Date: Wed, 02 Jan 2019 11:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88631-4-GXHupVQQQH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00070.txt.bz2
Content-length: 212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88631
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think this is a dup of PR 81486, please check if your patch fixes the
examples there too.
>From gcc-bugs-return-627262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:35:42 2019
Return-Path: <gcc-bugs-return-627262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90266 invoked by alias); 2 Jan 2019 11:35:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90222 invoked by uid 48); 2 Jan 2019 11:35:38 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88658] New: [9 Regression] Intrinsic MAX1 returns a REAL result, should be INTEGER.
Date: Wed, 02 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00071.txt.bz2
Content-length: 782
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88658
Bug ID: 88658
Summary: [9 Regression] Intrinsic MAX1 returns a REAL result,
should be INTEGER.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: tkoenig at gcc dot gnu.org
Target Milestone: ---
PR14377 "Intrinsic MAX1 returns a REAL result, should be INTEGER" resurfaced
between r265571 and r265728, likely r265649.
real :: RVCOMP
RVCOMP = MAX1(2.3, 3.1, 4.4) / 5
print *, RVCOMP
end
gives now
0.879999995
instead of
0.00000000
>From gcc-bugs-return-627263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:37:16 2019
Return-Path: <gcc-bugs-return-627263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93094 invoked by alias); 2 Jan 2019 11:37: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 93028 invoked by uid 48); 2 Jan 2019 11:37:12 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88626] __builtin_constant_p should be as cheap as dead code for inlining purposes
Date: Wed, 02 Jan 2019 11:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88626-4-3T02XVROey@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00072.txt.bz2
Content-length: 688
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88626
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Implementation should not be very hard - one would need to add pass propagating
liveness that will mark all statements that are needed only for
builtin_constant_p and call that from ipa_fnsummary.c:analyze_function_body.
Then it would be easy to ignore those statements for code size/time
calculations
>From gcc-bugs-return-627264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:38:43 2019
Return-Path: <gcc-bugs-return-627264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94904 invoked by alias); 2 Jan 2019 11:38: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 94806 invoked by uid 48); 2 Jan 2019 11:38:38 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88635] [8 Regression] Assembler error when building with "-g -O2 -m32"
Date: Wed, 02 Jan 2019 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: assemble-failure, wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc component
Message-ID: <bug-88635-4-KmxO8mxXX5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00073.txt.bz2
Content-length: 1210
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88635
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-debug
CC| |rguenth at gcc dot gnu.org
Component|c |middle-end
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
must really be latent before/after the revs. I see
.value 0xf # Location expression size
.byte 0x3 # DW_OP_addr
.long .LC0
.byte 0x72 # DW_OP_breg2
.sleb128 0
.byte 0x1c # DW_OP_minus
.byte 0x3 # DW_OP_addr
.long -2-.LC0@gotoff
.byte 0x22 # DW_OP_plus
.byte 0x9f # DW_OP_stack_value
in debug_loc. To me looks like a missed expression simplification and
failure to reject this "constant". Note that
.long .LC0@gotoff+2
works, so doing that and DW_OP_negate (if exists) might work. Of course
the @gotoff looks odd to me given the non-@gotoff reference to .LC0 above.
>From gcc-bugs-return-627265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:39:24 2019
Return-Path: <gcc-bugs-return-627265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96274 invoked by alias); 2 Jan 2019 11:39: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 96205 invoked by uid 48); 2 Jan 2019 11:39:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Wed, 02 Jan 2019 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 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: version target_milestone
Message-ID: <bug-88638-4-FlW230XRSi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00074.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Target Milestone|--- |9.0
>From gcc-bugs-return-627267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:42:36 2019
Return-Path: <gcc-bugs-return-627267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101438 invoked by alias); 2 Jan 2019 11:42:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101392 invoked by uid 48); 2 Jan 2019 11:42:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88659] [9 Regression] ICE in maybe_warn_nonstring_arg at gcc/calls.c:1688 since r267503
Date: Wed, 02 Jan 2019 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cf_known_to_work cf_known_to_fail
Message-ID: <bug-88659-4-SHzYX2zENx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00076.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88659
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Known to work| |8.2.0
Known to fail| |9.0
>From gcc-bugs-return-627266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:42:26 2019
Return-Path: <gcc-bugs-return-627266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100714 invoked by alias); 2 Jan 2019 11:42:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100666 invoked by uid 48); 2 Jan 2019 11:42:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88659] New: [9 Regression] ICE in maybe_warn_nonstring_arg at gcc/calls.c:1688 since r267503
Date: Wed, 02 Jan 2019 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00075.txt.bz2
Content-length: 2832
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88659
Bug ID: 88659
Summary: [9 Regression] ICE in maybe_warn_nonstring_arg at
gcc/calls.c:1688 since r267503
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: law at gcc dot gnu.org
Target Milestone: ---
Following is causing ICE:
$ cat /tmp/warn.i
const char a[][5] = {"", "", "1234"};
enum { b } c() { int d = __builtin_strnlen(&a[2][d], b); }
$ ./xgcc -B. /tmp/warn.i
during RTL pass: expand
/tmp/warn.i: In function ‘c’:
/tmp/warn.i:2:26: internal compiler error: Segmentation fault
2 | enum { b } c() { int d = __builtin_strnlen(&a[2][d], b); }
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0x1166940 crash_signal
../../gcc/toplev.c:326
0x7ffff6bc310f ???
/usr/src/debug/glibc-2.27-6.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x862461 contains_struct_check(tree_node const*, tree_node_structure_enum, char
const*, int, char const*)
../../gcc/tree.h:3545
0x8993ad wi::extended_tree<192>::extended_tree(tree_node const*)
../../gcc/tree.h:5615
0x89816f generic_wide_int<wi::extended_tree<192> >::generic_wide_int<tree_node
const*>(tree_node const* const&)
../../gcc/wide-int.h:780
0x897d72 wi::to_widest(tree_node const*)
../../gcc/tree.h:5542
0x897da4 tree_int_cst_lt(tree_node const*, tree_node const*)
../../gcc/tree.h:5795
0xa3a138 maybe_warn_nonstring_arg(tree_node*, tree_node*)
../../gcc/calls.c:1688
0xa3c6ea initialize_argument_information
../../gcc/calls.c:2221
0xa411a7 expand_call(tree_node*, rtx_def*, int)
../../gcc/calls.c:3601
0xa1fd31 expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int)
../../gcc/builtins.c:8337
0xc2f6e6 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../gcc/expr.c:10989
0xc21aee expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**, bool)
../../gcc/expr.c:8234
0xc16e22 store_expr(tree_node*, rtx_def*, int, bool, bool)
../../gcc/expr.c:5633
0xc1544c expand_assignment(tree_node*, tree_node*, bool)
../../gcc/expr.c:5416
0xa61513 expand_call_stmt
../../gcc/cfgexpand.c:2720
0xa64ec9 expand_gimple_stmt_1
../../gcc/cfgexpand.c:3685
0xa65557 expand_gimple_stmt
../../gcc/cfgexpand.c:3844
0xa6dda4 expand_gimple_basic_block
../../gcc/cfgexpand.c:5880
0xa6f8aa execute
../../gcc/cfgexpand.c:6502
>From gcc-bugs-return-627269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:43:47 2019
Return-Path: <gcc-bugs-return-627269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111946 invoked by alias); 2 Jan 2019 11:43:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109646 invoked by uid 48); 2 Jan 2019 11:43:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88635] [8 Regression] Assembler error when building with "-g -O2 -m32"
Date: Wed, 02 Jan 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: assemble-failure, wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88635-4-eK6xcJBStj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00078.txt.bz2
Content-length: 1070
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88635
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Of course it is latent before/after.
In const_ok_for_output_1 we have
/* FIXME: Refer to PR60655. It is possible for simplification
of rtl expressions in var tracking to produce such expressions.
We should really identify / validate expressions
enclosed in CONST that can be handled by assemblers on various
targets and only handle legitimate cases here. */
switch (GET_CODE (rtl))
{
case SYMBOL_REF:
break;
case NOT:
case NEG:
return false;
default:
return true;
}
that catches some problematic cases, but in this case the simplification
created (const (minus (const_int -2) (unspec ...)))
and that makes the unspec negated too. So, we could e.g. add a case to the
above switch that case MINUS: if there are any UNSPECs in subexpressions of the
second operand, punt. Of course, if we want to try harder, we could try to
negate the expression and see if it is valid that way etc.
>From gcc-bugs-return-627268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:43:28 2019
Return-Path: <gcc-bugs-return-627268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103026 invoked by alias); 2 Jan 2019 11:43: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 102789 invoked by uid 48); 2 Jan 2019 11:43:24 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88626] __builtin_constant_p should be as cheap as dead code for inlining purposes
Date: Wed, 02 Jan 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88626-4-MFFozj3r3e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00077.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88626
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Also note that builtin_constant_p is handled conservatively.
If you have
if (builtin_constant_p (x))
constant code;
else
nonconstant code;
inliner will know that nonconstant code will be optimized out if x is constant,
but it will not know that constant code will be optimized out if x is variable
(because it never knows that info, only later optimizations will decide) and it
does not know that it is always the case that one of the branches will be
optimized out.
The last problem I think is most serious about our BCP handling. It may be
possible to compute size/time vectors of the two variants and then produce
final one that will take constant variant when x is constant and longer of the
two variants when x is not, but it will need some work.
Honza
>From gcc-bugs-return-627271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:45:40 2019
Return-Path: <gcc-bugs-return-627271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117856 invoked by alias); 2 Jan 2019 11:45:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117559 invoked by uid 48); 2 Jan 2019 11:45:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64372] [DR1560] Gratuitous lvalue-to-rvalue conversion in conditional-expression with throw-expression operand
Date: Wed, 02 Jan 2019 11:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: diagnostic, rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-64372-4-vk8lkNAP0J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64372-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64372-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00080.txt.bz2
Content-length: 1133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64372
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2016-11-23 00:00:00 |2019-1-2
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #10)
> Author: jason
> Date: Tue May 15 21:56:29 2018
> New Revision: 260272
>
> URL: https://gcc.gnu.org/viewcvs?rev=260272&root=gcc&view=rev
> Log:
> PR c++/64372 - CWG 1560, gratuitous lvalue-rvalue conversion in ?:
>
> * call.c (build_conditional_expr_1): Don't force_rvalue when one arm
> is a throw-expression.
>
> Added:
> trunk/gcc/testsuite/g++.dg/cpp1y/dr1560.C
> Modified:
> trunk/gcc/cp/ChangeLog
> trunk/gcc/cp/call.c
Jason, you added known to work = 9.0 but neither comment 0 nor comment 8 is
fixed by this patch.
Comment 11 might be a different issue, or might be the same and has a
misleading diagnostic (there's no & operator in the code), but either way it
also isn't fixed.
>From gcc-bugs-return-627270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:45:36 2019
Return-Path: <gcc-bugs-return-627270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117684 invoked by alias); 2 Jan 2019 11:45:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117257 invoked by uid 48); 2 Jan 2019 11:45:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88643] -Wl,--wrap not supported with LTO
Date: Wed, 02 Jan 2019 11:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-88643-4-SMKUF7L026@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00079.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88643
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |lto
CC| |ccoutant at gmail dot com
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
There isn't support for this kind of replacement. I guess the resolution
output could be enhanced to handle this.
>From gcc-bugs-return-627272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:48:35 2019
Return-Path: <gcc-bugs-return-627272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123577 invoked by alias); 2 Jan 2019 11:48:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123277 invoked by uid 48); 2 Jan 2019 11:48:16 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81239] std::__cxx11::string& visible in gcc warning output
Date: Wed, 02 Jan 2019 11:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81239-4-kLRAfRXuFY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00081.txt.bz2
Content-length: 342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's the ABI that meets the requirements of the C++11 standard, but that
doesn't mean it's enabled by the -std=c++11 flag. The -std flags never change
ABI, irrespective of the names used for attributes and namespaces.
>From gcc-bugs-return-627273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:50:29 2019
Return-Path: <gcc-bugs-return-627273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127042 invoked by alias); 2 Jan 2019 11:50:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126908 invoked by uid 48); 2 Jan 2019 11:50:24 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88626] __builtin_constant_p should be as cheap as dead code for inlining purposes
Date: Wed, 02 Jan 2019 11:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88626-4-tf4FPB5D78@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00082.txt.bz2
Content-length: 1543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88626
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> The __builtin_constant_p call itself is "free" but whether guarded code is
> "free" isn't easy to determine. I guess what you want is the computation
> of "b" which is only used when it is constant is considered "free"?
Yes. The computation of b should be free, and also the estimated size of the
function should be at most the max of the 2 branches, not the sum, since only
one will remain.
One possible pessimistic definition (I am not saying we should do it, just
trying to define some goal) would be, for the purpose of estimating the size:
replace all __builtin_constant_p with false, simplify/DCE, and look at the size
of the result. Of course we would actually inline the original function with
__builtin_constant_p, the reduced one is only to get an upper bound on the
size, with the assumption that when __builtin_constant_p returns true, things
are always better (smaller & faster).
> Confirmed for that. Not sure how easy to implement though.
Running some modified DCE pass may not be too hard, although doing that just to
improve the size estimation with __builtin_constant_p for inlining might be
overkill...
Maybe a heuristic that gives a "bonus" for inlining a function that contains
__builtin_constant_p (only if the argument looks like it depends on the
function parameters?) would be easier? I don't know if we have something like
that yet.
>From gcc-bugs-return-627274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:51:31 2019
Return-Path: <gcc-bugs-return-627274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129927 invoked by alias); 2 Jan 2019 11:51:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129888 invoked by uid 48); 2 Jan 2019 11:51:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88650] [9 Regression] ICE in set_even_probabilities at gcc/predict.c:885 since r267485
Date: Wed, 02 Jan 2019 11:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88650-4-Yae1T8394W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00083.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88650
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:53:58 2019
Return-Path: <gcc-bugs-return-627275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1952 invoked by alias); 2 Jan 2019 11:53: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 1906 invoked by uid 48); 2 Jan 2019 11:53:55 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88658] [9 Regression] Intrinsic MAX1 returns a REAL result, should be INTEGER.
Date: Wed, 02 Jan 2019 11:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
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_known_to_work keywords cf_reconfirmed_on everconfirmed target_milestone cf_known_to_fail
Message-ID: <bug-88658-4-6ZSqBNP0hE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00084.txt.bz2
Content-length: 682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88658
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Known to work| |8.2.0
Keywords| |wrong-code
Last reconfirmed| |2019-01-02
Ever confirmed|0 |1
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-627276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:54:16 2019
Return-Path: <gcc-bugs-return-627276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3033 invoked by alias); 2 Jan 2019 11:54: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 2768 invoked by uid 55); 2 Jan 2019 11:54:13 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88626] __builtin_constant_p should be as cheap as dead code for inlining purposes
Date: Wed, 02 Jan 2019 11:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88626-4-S2OuZgSNmI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88626-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00085.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88626
--- Comment #6 from Jan Hubicka <hubicka at ucw dot cz> ---
> Maybe a heuristic that gives a "bonus" for inlining a function that contains
> __builtin_constant_p (only if the argument looks like it depends on the
> function parameters?) would be easier? I don't know if we have something like
> that yet.
Yes, we have inline bonuses (called inline_hint) and I guess adding
bonus for builtin_constant_p calls which depends on function parameter
should be doable and indeed makes sense to me.
Still for serious builtin_constant_p performance I think we need to do
something about the double accounting problem I explained above that is
bit harder to fix (the time/size vector themselves do not have any
if-then-else semantics and predicates have no NOT operation, but merging
the outcomes is possible, just bit hard to implement)
Honza
>From gcc-bugs-return-627277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:55:14 2019
Return-Path: <gcc-bugs-return-627277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15920 invoked by alias); 2 Jan 2019 11:55:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15809 invoked by uid 48); 2 Jan 2019 11:55:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88651] tree-data-ref.c:3764:26: runtime error: signed integer overflow: 9223372036854775802 - -6 cannot be represented in type 'long int'
Date: Wed, 02 Jan 2019 11:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88651-4-O1LBhGpONr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00086.txt.bz2
Content-length: 659
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88651
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
looks like latent wrong-code to me.
>From gcc-bugs-return-627278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:56:48 2019
Return-Path: <gcc-bugs-return-627278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17822 invoked by alias); 2 Jan 2019 11:56:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17680 invoked by uid 48); 2 Jan 2019 11:56:44 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Wed, 02 Jan 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.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:
Message-ID: <bug-88653-4-jvPrmwae9Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00087.txt.bz2
Content-length: 207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Note that I run the tests with the '-w -fno-sign-zero -std=legacy' options.
>From gcc-bugs-return-627279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 11:58:51 2019
Return-Path: <gcc-bugs-return-627279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20393 invoked by alias); 2 Jan 2019 11:58: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 20309 invoked by uid 48); 2 Jan 2019 11:58:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65994] auto deduces object instead of initializer_list
Date: Wed, 02 Jan 2019 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-65994-4-euko36i6X5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00088.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65994
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Jason, should this be closed, because our current behaviour is as intended?
>From gcc-bugs-return-627280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:00:25 2019
Return-Path: <gcc-bugs-return-627280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23727 invoked by alias); 2 Jan 2019 12:00: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 23059 invoked by uid 48); 2 Jan 2019 12:00:01 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81259] Class template deduction cannot work on Constructor without parameters in some cases
Date: Wed, 02 Jan 2019 12:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-81259-4-T6nchflZ7x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81259-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81259-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00089.txt.bz2
Content-length: 540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81259
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think this is another dup of PR 88631 (and PR 81486).
*** This bug has been marked as a duplicate of bug 88631 ***
>From gcc-bugs-return-627281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:00:25 2019
Return-Path: <gcc-bugs-return-627281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23796 invoked by alias); 2 Jan 2019 12:00:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23116 invoked by uid 48); 2 Jan 2019 12:00:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88631] CTAD cannot deduce from () value initialization
Date: Wed, 02 Jan 2019 12:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88631-4-ANkMjuFBHJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00090.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88631
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kmp53 at sina dot com
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 81259 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:12:53 2019
Return-Path: <gcc-bugs-return-627282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37265 invoked by alias); 2 Jan 2019 12:12: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 37210 invoked by uid 48); 2 Jan 2019 12:12:49 -0000
From: "alexander.hirsch at gin dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88660] New: Invalid report of "set but used variable" with -O
Date: Wed, 02 Jan 2019 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: alexander.hirsch at gin dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88660-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00091.txt.bz2
Content-length: 874
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88660
Bug ID: 88660
Summary: Invalid report of "set but used variable" with -O
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: alexander.hirsch at gin dot de
Target Milestone: ---
Created attachment 45314
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45314&action=edit
testcase triggering the warning
Compiling the attached testcase with -O -Wunused-but-set-variable on gcc >= 8.1
erroneously generates a warning that i is unused.
Removing either the -O flag, the const-modifier or replacing the
switch-statement by e.g. an if leads to no warning being reported.
The warning also does not appear in gcc 7.4.
>From gcc-bugs-return-627283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:15:47 2019
Return-Path: <gcc-bugs-return-627283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39716 invoked by alias); 2 Jan 2019 12:15:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39668 invoked by uid 48); 2 Jan 2019 12:15:42 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88649] runtime error: load of value 137971008, which is not a valid value for type 'gfc_intrinsic_op'
Date: Wed, 02 Jan 2019 12:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.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 everconfirmed
Message-ID: <bug-88649-4-CBLoPmpJ6H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88649-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00092.txt.bz2
Content-length: 667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88649
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I get
../../work/gcc/fortran/resolve.c:4151:23: runtime error: load of value 21200,
which is not a valid value for type 'gfc_intrinsic_op'
with r267421, not no error with r259553.
>From gcc-bugs-return-627285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:19:57 2019
Return-Path: <gcc-bugs-return-627285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71293 invoked by alias); 2 Jan 2019 12:19: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 69452 invoked by uid 48); 2 Jan 2019 12:19:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88621] [9 Regression] wrong code at -O1 and above on x86_64-linux-gnu in 64-bit mode (not in 32-bit mode)
Date: Wed, 02 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
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-88621-4-QlM9U9V9CS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88621-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88621-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00094.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88621
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:19:46 2019
Return-Path: <gcc-bugs-return-627284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67995 invoked by alias); 2 Jan 2019 12:19:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66011 invoked by uid 55); 2 Jan 2019 12:19:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88621] [9 Regression] wrong code at -O1 and above on x86_64-linux-gnu in 64-bit mode (not in 32-bit mode)
Date: Wed, 02 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88621-4-ojOZTYWffZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88621-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88621-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00093.txt.bz2
Content-length: 666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88621
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jan 2 12:19:10 2019
New Revision: 267510
URL: https://gcc.gnu.org/viewcvs?rev=267510&root=gcc&view=rev
Log:
2019-01-02 Richard Biener <rguenther@suse.de>
PR tree-optimization/88621
* tree-ssa-loop-im.c (gather_mem_refs_stmt): Fix pastos, avoid
bitfields when canoncalizing.
* gcc.dg/torture/pr88621.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr88621.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-loop-im.c
>From gcc-bugs-return-627286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:21:58 2019
Return-Path: <gcc-bugs-return-627286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105019 invoked by alias); 2 Jan 2019 12:21: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 102906 invoked by uid 48); 2 Jan 2019 12:21:55 -0000
From: "dinuxbg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88609] [avr] ice: insn does not satisfy its constraints while building libgcc
Date: Wed, 02 Jan 2019 12:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dinuxbg at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88609-4-gwm6CrpfXa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88609-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88609-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00095.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88609
--- Comment #1 from Dimitar Dimitrov <dinuxbg at gmail dot com> ---
Note that this build error depends on the host compiler used to build the avr
toolchain.
I can build successfully with host: gcc (Debian 6.3.0-18+deb9u1) 6.3.0 20170516
Build fails with host top-of-tree build: gcc (GCC) 9.0.0 20181215
(experimental)
>From gcc-bugs-return-627287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:22:11 2019
Return-Path: <gcc-bugs-return-627287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108764 invoked by alias); 2 Jan 2019 12: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 106985 invoked by uid 48); 2 Jan 2019 12:22:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] Hangs in libphobos testsuite
Date: Wed, 02 Jan 2019 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 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: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88654-4-bXESiYFi9r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00096.txt.bz2
Content-length: 542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think I saw a duplicate somewhere - this is using real-time threads pinned to
a single CPU but yield()ing in a spinning loop expecting to make progress.
>From gcc-bugs-return-627288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:23:52 2019
Return-Path: <gcc-bugs-return-627288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36562 invoked by alias); 2 Jan 2019 12:23:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34322 invoked by uid 48); 2 Jan 2019 12:23:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88659] [9 Regression] ICE in maybe_warn_nonstring_arg at gcc/calls.c:1688 since r267503
Date: Wed, 02 Jan 2019 12:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88659-4-ClJCysSOFC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00097.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88659
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:24:37 2019
Return-Path: <gcc-bugs-return-627289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56592 invoked by alias); 2 Jan 2019 12:24: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 41829 invoked by uid 55); 2 Jan 2019 12:24:03 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88041] gdc.test tests should include that prefix in test names
Date: Wed, 02 Jan 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ro at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88041-4-gXMsNXVLA7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88041-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88041-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00098.txt.bz2
Content-length: 536
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88041
--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from Johannes Pfau <johannespfau at gmail dot com> ---
> For reference, this makes running the testsuite on windows/msys2 hosts somewhat
> more complicated:
I'm sorry for that. I don't use Windows myself in any way, but before
making that change, I've checked file(1t) which didn't indicate that
there might be problems with file link on Windows.
Rainer
>From gcc-bugs-return-627291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:24:44 2019
Return-Path: <gcc-bugs-return-627291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57474 invoked by alias); 2 Jan 2019 12:24:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56896 invoked by uid 48); 2 Jan 2019 12:24:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88656] [7/8/9 Regression] lr clobbered by thumb prologue before __builtin_return_address(0) reads from it
Date: Wed, 02 Jan 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords version target_milestone
Message-ID: <bug-88656-4-Itbi0fL0HV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00100.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88656
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Version|unknown |9.0
Target Milestone|--- |7.5
>From gcc-bugs-return-627290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:24:44 2019
Return-Path: <gcc-bugs-return-627290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57377 invoked by alias); 2 Jan 2019 12:24:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56760 invoked by uid 48); 2 Jan 2019 12:24:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88646] Optimizer failure on integer sum overflow cast to bool
Date: Wed, 02 Jan 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88646-4-NpTHAb6SKe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00099.txt.bz2
Content-length: 266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88646
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to gianni from comment #2)
> While it may be undefined, should the result at least be consistent?
No, that's not what undefined means.
>From gcc-bugs-return-627292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:47:07 2019
Return-Path: <gcc-bugs-return-627292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118856 invoked by alias); 2 Jan 2019 12:47:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118790 invoked by uid 48); 2 Jan 2019 12:47:03 -0000
From: "igor.chorazewicz at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88661] New: No brace ellision performed when aggregate is initialized inside of struct
Date: Wed, 02 Jan 2019 12:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: igor.chorazewicz at intel dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00101.txt.bz2
Content-length: 654
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88661
Bug ID: 88661
Summary: No brace ellision performed when aggregate is
initialized inside of struct
Product: gcc
Version: 5.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: igor.chorazewicz at intel dot com
Target Milestone: ---
The following code produces "error: array must be initialized with a
brace-enclosed initializer":
struct array {
int data[3];
};
struct X {
array a = {1,2,3};
};
>From gcc-bugs-return-627293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 12:52:04 2019
Return-Path: <gcc-bugs-return-627293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127255 invoked by alias); 2 Jan 2019 12:52: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 127147 invoked by uid 48); 2 Jan 2019 12:51:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Wed, 02 Jan 2019 12:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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 cc component assigned_to
Message-ID: <bug-88611-4-faczJHu5Bn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00102.txt.bz2
Content-length: 4725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
CC| |burnus at gcc dot gnu.org
Component|tree-optimization |fortran
Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, so this is
<var_decl 0x7ffff7fefab0 p
type <pointer_type 0x7ffff6896000
type <void_type 0x7ffff688ff18 void VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff688ff18
pointer_to_this <pointer_type 0x7ffff6896000>>
public unsigned DI
size <integer_cst 0x7ffff687ab70 constant 64>
unit-size <integer_cst 0x7ffff687ab88 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set 4 canonical-type
0x7ffff6896000
pointer_to_this <pointer_type 0x7ffff689b738>>
readonly used static unsigned DI t.f90:8:0 size <integer_cst 0x7ffff687ab70
64> unit-size <integer_cst 0x7ffff687ab88 8>
align:64 warn_if_not_align:0 context <function_decl 0x7ffff6a44c00
pr82869_8> initial <integer_cst 0x7ffff689a210 0> chain <var_decl
0x7ffff7fefb40 s>>
where the DECL_INITIAL is
<integer_cst 0x7ffff689a210 type <integer_type 0x7ffff688f738 integer(kind=8)>
constant 0>
so a frontend type mismatch we do not "expect" ...
type(c_ptr) :: p = c_null_ptr
My change uncovers this. The inital value is set here:
tree
gfc_get_symbol_decl (gfc_symbol * sym)
{
...
/* Add static initializer. For procedures, it is only needed if
SAVE is specified otherwise they need to be reinitialized
every time the procedure is entered. The TREE_STATIC is
in this case due to -fmax-stack-var-size=. */
DECL_INITIAL (decl) = gfc_conv_initializer (sym->value, &sym->ts,
TREE_TYPE (decl), sym->attr.dimension
|| (sym->attr.codimension
&& sym->attr.allocatable),
sym->attr.pointer || sym->attr.allocatable
|| sym->ts.type == BT_CLASS,
sym->attr.proc_pointer);
and there
/* Check if we have ISOCBINDING_NULL_PTR or ISOCBINDING_NULL_FUNPTR
(these are the only two iso_c_binding derived types that can be
used as initialization expressions). If so, we need to modify
the 'expr' to be that for a (void *). */
if (expr != NULL && expr->ts.type == BT_DERIVED
&& expr->ts.is_iso_c && expr->ts.u.derived)
{
gfc_symbol *derived = expr->ts.u.derived;
/* The derived symbol has already been converted to a (void *). Use
its kind. */
if (derived->ts.kind == 0)
derived->ts.kind = gfc_default_integer_kind;
expr = gfc_get_int_expr (derived->ts.kind, NULL, 0);
expr->ts.f90_type = derived->ts.f90_type;
gfc_init_se (&se, NULL);
gfc_conv_constant (&se, expr);
gcc_assert (TREE_CODE (se.expr) != CONSTRUCTOR);
return se.expr;
but it looks like gfc_conv_constant doesn't do the pointer conversion
required. It also looks overly complicated to me where at the same
time it doesn't try to distinguish between (void *) and void (*)()
or whatever type ISOCBINDING_NULL_FUNPTR is supposed to map to...
Well. The following "fixes" this for me. Fortran folks?
diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c
index 27eb2d2ee38..798952c2336 100644
--- a/gcc/fortran/trans-expr.c
+++ b/gcc/fortran/trans-expr.c
@@ -7085,21 +7085,7 @@ gfc_conv_initializer (gfc_expr * expr, gfc_typespec *
ts, tree type,
the 'expr' to be that for a (void *). */
if (expr != NULL && expr->ts.type == BT_DERIVED
&& expr->ts.is_iso_c && expr->ts.u.derived)
- {
- gfc_symbol *derived = expr->ts.u.derived;
-
- /* The derived symbol has already been converted to a (void *). Use
- its kind. */
- if (derived->ts.kind == 0)
- derived->ts.kind = gfc_default_integer_kind;
- expr = gfc_get_int_expr (derived->ts.kind, NULL, 0);
- expr->ts.f90_type = derived->ts.f90_type;
-
- gfc_init_se (&se, NULL);
- gfc_conv_constant (&se, expr);
- gcc_assert (TREE_CODE (se.expr) != CONSTRUCTOR);
- return se.expr;
- }
+ return build_int_cst (ptr_type_node, 0);
if (array && !procptr)
{
>From gcc-bugs-return-627294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:09:18 2019
Return-Path: <gcc-bugs-return-627294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7875 invoked by alias); 2 Jan 2019 13:09: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 7826 invoked by uid 48); 2 Jan 2019 13:09:13 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88147] [9 Regression] ICE in linemap_line_start, at libcpp/line-map.c:781 starting from r265875
Date: Wed, 02 Jan 2019 13:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88147-4-KkCQC9w0Ol@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00103.txt.bz2
Content-length: 239
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88147
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
David can you please help us with that? Would it be possible to write a
sanitization patch will catch an overflow?
>From gcc-bugs-return-627295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:15:16 2019
Return-Path: <gcc-bugs-return-627295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15212 invoked by alias); 2 Jan 2019 13:15: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 14763 invoked by uid 48); 2 Jan 2019 13:15:01 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87304] [9 regression] gcc.dg/vect/bb-slp-over-widen-1.c fails starting with r262371
Date: Wed, 02 Jan 2019 13:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-87304-4-UikHlqzWHZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87304-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87304-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00104.txt.bz2
Content-length: 421
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87304
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Jakub: will you apply the patch?
>From gcc-bugs-return-627296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:16:25 2019
Return-Path: <gcc-bugs-return-627296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18092 invoked by alias); 2 Jan 2019 13:16:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17991 invoked by uid 48); 2 Jan 2019 13:16:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86979] [9 Regression] ICE: in maybe_record_trace_start, at dwarf2cfi.c:2348 with -m32 on darwin
Date: Wed, 02 Jan 2019 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: abel at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc blocked
Message-ID: <bug-86979-4-jjtJ99GNyU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86979-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86979-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00105.txt.bz2
Content-length: 624
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86979
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
Blocks| |85099
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Is it really P1 as it's related to selective-scheduling?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85099
[Bug 85099] [meta-bug] selective scheduling issues
>From gcc-bugs-return-627297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:17:25 2019
Return-Path: <gcc-bugs-return-627297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20752 invoked by alias); 2 Jan 2019 13:17: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 20683 invoked by uid 48); 2 Jan 2019 13:17:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86865] [9 Regression] Wrong code w/ -O2 -floop-parallelize-all -fstack-reuse=none -fwrapv -fno-tree-ch -fno-tree-dce -fno-tree-dominator-opts -fno-tree-loop-ivcanon
Date: Wed, 02 Jan 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86865-4-tQZrjuMO5e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00106.txt.bz2
Content-length: 160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86865
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Really P1 as it's Graphite-related?
>From gcc-bugs-return-627298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:41:14 2019
Return-Path: <gcc-bugs-return-627298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27436 invoked by alias); 2 Jan 2019 13:41: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 23110 invoked by uid 48); 2 Jan 2019 13:41:10 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88436] [9 regression] r265421 causes gcc.target/powerpc/pr54240.c to fail
Date: Wed, 02 Jan 2019 13:41: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: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88436-4-hpvJHDIycJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00107.txt.bz2
Content-length: 554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88436
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |marxin at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Let me adjust the test.
>From gcc-bugs-return-627299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:42:58 2019
Return-Path: <gcc-bugs-return-627299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29126 invoked by alias); 2 Jan 2019 13:42:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29069 invoked by uid 55); 2 Jan 2019 13:42:52 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o
Date: Wed, 02 Jan 2019 13:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
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-88535-4-fabschbgcC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88535-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88535-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00108.txt.bz2
Content-length: 987
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535
--- Comment #15 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
>> --- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
>>> I wonder if the configure or make process should defend against the
>>> possibility that the host compiler and the compiler that we are building
>>> today have differing defaults for -m32 vs -m64.
>>
>> The problem is that we don't correctly detect the cross configuration here.
>
> That's because, as I suspected, config.guess doesn't distinguish sparc
> and sparcv9 configurations of Solaris, unlike the i386/x86_64 case.
I've now submitted a patch to do just that:
http://lists.gnu.org/archive/html/config-patches/2019-01/msg00000.html
Once it has been accepted, I'll import config.guess and config.sub into
the gcc and binutils-gdb repos.
>From gcc-bugs-return-627300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:45:58 2019
Return-Path: <gcc-bugs-return-627300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31926 invoked by alias); 2 Jan 2019 13:45:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31868 invoked by uid 48); 2 Jan 2019 13:45:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88576] -fno-math-errno causes GCC to consider that malloc does not set errno
Date: Wed, 02 Jan 2019 13:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88576-4-ekgF46w5Q3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00109.txt.bz2
Content-length: 741
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88576
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45315
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45315&action=edit
patch
What I have sofar - this doesn't work for Fortran behaving differently by
default. I think a proper fix would be to refactor the existing
_set_by_frontend stuff triggered via SetByCombined into a frontend specific
default_options_table (lang_hooks.default_options_table I guess) which
gets merged with the global default_options_table, overriding any settings
there.
Note there's a related bug complaining about -fno-math-errno not doing what
is documented. That probably changed because of fortran as well.
>From gcc-bugs-return-627301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:47:10 2019
Return-Path: <gcc-bugs-return-627301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34895 invoked by alias); 2 Jan 2019 13:47: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 34847 invoked by uid 48); 2 Jan 2019 13:47:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86865] [9 Regression] Wrong code w/ -O2 -floop-parallelize-all -fstack-reuse=none -fwrapv -fno-tree-ch -fno-tree-dce -fno-tree-dominator-opts -fno-tree-loop-ivcanon
Date: Wed, 02 Jan 2019 13:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86865-4-BTgzn4MmCJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00110.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86865
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #4)
> Really P1 as it's Graphite-related?
it's wrong-code, so yes for now.
>From gcc-bugs-return-627302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:51:48 2019
Return-Path: <gcc-bugs-return-627302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44505 invoked by alias); 2 Jan 2019 13:51: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 44448 invoked by uid 48); 2 Jan 2019 13:51:44 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] New: Document trap representations of _Bool
Date: Wed, 02 Jan 2019 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 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-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00111.txt.bz2
Content-length: 1024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
Bug ID: 88662
Summary: Document trap representations of _Bool
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: gonzalobg88 at gmail dot com
Target Milestone: ---
Compiling
unsigned int foo(unsigned int x, _Bool b) {
return x - (unsigned int)b;
}
only produces correct results if the value of `_Bool` is either `0` or `1` [0],
see https://gcc.godbolt.org/z/l0DPjc:
foo:
movzx esi, sil
mov eax, edi
sub eax, esi
ret
This probably means that all other representations of `_Bool` are trap
representations, but this does not appear to be documented anywhere.
>From my reading of the C standard, the role that padding bits play for `_Bool`
is unclear.
[0] one can construct such a _Bool by writing to it via a char* .
>From gcc-bugs-return-627303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 13:52:39 2019
Return-Path: <gcc-bugs-return-627303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46488 invoked by alias); 2 Jan 2019 13:52:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46410 invoked by uid 55); 2 Jan 2019 13:52:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88651] tree-data-ref.c:3764:26: runtime error: signed integer overflow: 9223372036854775802 - -6 cannot be represented in type 'long int'
Date: Wed, 02 Jan 2019 13:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88651-4-iJgIFDAyLz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00112.txt.bz2
Content-length: 533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88651
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Wed Jan 2 13:52:03 2019
New Revision: 267512
URL: https://gcc.gnu.org/viewcvs?rev=267512&root=gcc&view=rev
Log:
2019-01-02 Richard Biener <rguenther@suse.de>
PR middle-end/88651
* tree-data-ref.c (analyze_subscript_affine_affine): Use
widest_ints when mangling max_stmt_execution results.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-data-ref.c
>From gcc-bugs-return-627306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:04:41 2019
Return-Path: <gcc-bugs-return-627306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73110 invoked by alias); 2 Jan 2019 14:04:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73037 invoked by uid 48); 2 Jan 2019 14:04:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88651] tree-data-ref.c:3764:26: runtime error: signed integer overflow: 9223372036854775802 - -6 cannot be represented in type 'long int'
Date: Wed, 02 Jan 2019 14: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88651-4-0Bwl7KkfOC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00115.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88651
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:04:29 2019
Return-Path: <gcc-bugs-return-627304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72395 invoked by alias); 2 Jan 2019 14:04:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72372 invoked by uid 55); 2 Jan 2019 14:04:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88650] [9 Regression] ICE in set_even_probabilities at gcc/predict.c:885 since r267485
Date: Wed, 02 Jan 2019 14: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88650-4-HztypUYsws@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00113.txt.bz2
Content-length: 806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88650
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Wed Jan 2 14:03:53 2019
New Revision: 267513
URL: https://gcc.gnu.org/viewcvs?rev=267513&root=gcc&view=rev
Log:
Calculate prediction remainder at proper place (PR tree-optimization/88650).
2019-01-02 Martin Liska <mliska@suse.cz>
PR tree-optimization/88650
* predict.c (set_even_probabilities): Calculate probability
remainer only when really used.
2019-01-02 Martin Liska <mliska@suse.cz>
PR tree-optimization/88650
* gfortran.dg/predict-3.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/predict-3.f90
Modified:
trunk/gcc/ChangeLog
trunk/gcc/predict.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:04:41 2019
Return-Path: <gcc-bugs-return-627305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73108 invoked by alias); 2 Jan 2019 14:04:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73052 invoked by uid 48); 2 Jan 2019 14:04:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63426] [meta-bug] Issues found with -fsanitize=undefined
Date: Wed, 02 Jan 2019 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-63426-4-1l68Lnf96X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00114.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 88651, which changed state.
Bug 88651 Summary: tree-data-ref.c:3764:26: runtime error: signed integer overflow: 9223372036854775802 - -6 cannot be represented in type 'long int'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88651
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-627307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:06:27 2019
Return-Path: <gcc-bugs-return-627307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129186 invoked by alias); 2 Jan 2019 14:06:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126920 invoked by uid 48); 2 Jan 2019 14:06:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88650] [9 Regression] ICE in set_even_probabilities at gcc/predict.c:885 since r267485
Date: Wed, 02 Jan 2019 14:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88650-4-VWyKz3uV4u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00116.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88650
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:12:20 2019
Return-Path: <gcc-bugs-return-627308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8800 invoked by alias); 2 Jan 2019 14:12:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8740 invoked by uid 48); 2 Jan 2019 14:12:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Wed, 02 Jan 2019 14:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88662-4-mJllugz91S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00117.txt.bz2
Content-length: 1049
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to gnzlbg from comment #0)
> Compiling
>
> unsigned int foo(unsigned int x, _Bool b) {
> return x - (unsigned int)b;
> }
>
> only produces correct results if the value of `_Bool` is either `0` or `1`
Because (unsigned int)b is undefined otherwise.
> [0], see https://gcc.godbolt.org/z/l0DPjc:
>
> foo:
> movzx esi, sil
> mov eax, edi
> sub eax, esi
> ret
>
> This probably means that all other representations of `_Bool` are trap
> representations, but this does not appear to be documented anywhere.
The representation of _Bool is unspecified, not implementation-defined, so
doesn't need to be documented.
>From gcc-bugs-return-627309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:15:51 2019
Return-Path: <gcc-bugs-return-627309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11847 invoked by alias); 2 Jan 2019 14:15:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11707 invoked by uid 48); 2 Jan 2019 14:15:39 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Wed, 02 Jan 2019 14:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-MYmgMcqwqI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00118.txt.bz2
Content-length: 241
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #2 from gnzlbg <gonzalobg88 at gmail dot com> ---
> Because (unsigned int)b is undefined otherwise.
AFAICT this is only undefined behavior iff `b` has a trap representation.
>From gcc-bugs-return-627310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:17:09 2019
Return-Path: <gcc-bugs-return-627310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13318 invoked by alias); 2 Jan 2019 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 13239 invoked by uid 48); 2 Jan 2019 14:17:05 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88661] No brace ellision performed when aggregate is initialized inside of struct
Date: Wed, 02 Jan 2019 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-88661-4-BkDM5k8cLb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00119.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88661
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
You're using an old, unsupported version of GCC. This was fixed years ago.
*** This bug has been marked as a duplicate of bug 65815 ***
>From gcc-bugs-return-627311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:17:09 2019
Return-Path: <gcc-bugs-return-627311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13338 invoked by alias); 2 Jan 2019 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 13251 invoked by uid 48); 2 Jan 2019 14:17:05 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65815] brace elision doesn't work in NSDMI
Date: Wed, 02 Jan 2019 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-65815-4-e7Y8KTOsLh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00120.txt.bz2
Content-length: 453
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65815
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |igor.chorazewicz at intel dot com
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 88661 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:21:15 2019
Return-Path: <gcc-bugs-return-627312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17817 invoked by alias); 2 Jan 2019 14:21:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17777 invoked by uid 48); 2 Jan 2019 14:21:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Wed, 02 Jan 2019 14:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-GTcIBe73oS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00121.txt.bz2
Content-length: 230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, and an implementation is not required to document which object
representations are trap representations.
>From gcc-bugs-return-627313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:23:18 2019
Return-Path: <gcc-bugs-return-627313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25713 invoked by alias); 2 Jan 2019 14:23: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 25669 invoked by uid 48); 2 Jan 2019 14:23:14 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Wed, 02 Jan 2019 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-hH3zT0OakI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00122.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #4 from gnzlbg <gonzalobg88 at gmail dot com> ---
Without that information, how does one know which values can a valid program
write to a `_Bool` via a `char*`?
AFAIK the C standard guarantees that 0x0 must be a valid representation of
_Bool, but there are no guarantees about the bit-pattern of true beyond that
such a value must exist.
>From gcc-bugs-return-627315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:25:27 2019
Return-Path: <gcc-bugs-return-627315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28240 invoked by alias); 2 Jan 2019 14:25:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28085 invoked by uid 48); 2 Jan 2019 14:25:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88634] [c++17] Error message when deducing templated types for a constructor with more than one argument when using `new`
Date: Wed, 02 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88634-4-TwsIarfWkP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88634-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88634-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00124.txt.bz2
Content-length: 508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88634
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Already fixed on trunk.
*** This bug has been marked as a duplicate of bug 85883 ***
>From gcc-bugs-return-627314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:25:27 2019
Return-Path: <gcc-bugs-return-627314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28224 invoked by alias); 2 Jan 2019 14:25:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28111 invoked by uid 48); 2 Jan 2019 14:25:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85883] class template argument deduction fails in new-expression
Date: Wed, 02 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85883-4-Ls1KeZlWnH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85883-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00123.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85883
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jacksonmcneillnospam@gmail.
| |com
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 88634 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:28:28 2019
Return-Path: <gcc-bugs-return-627316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33504 invoked by alias); 2 Jan 2019 14:28:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33442 invoked by uid 48); 2 Jan 2019 14:28:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Wed, 02 Jan 2019 14:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-SgDwOPz0xT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00125.txt.bz2
Content-length: 281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
You can copy the bit-pattern from any _Bool with true value, e.g. one
initialized with 'true' or an expression like '0==0'.
Why do you need more than that?
>From gcc-bugs-return-627317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:31:12 2019
Return-Path: <gcc-bugs-return-627317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37027 invoked by alias); 2 Jan 2019 14:31:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36847 invoked by uid 48); 2 Jan 2019 14:30:53 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] New: [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Wed, 02 Jan 2019 14:31: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: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00126.txt.bz2
Content-length: 2694
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
Bug ID: 88663
Summary: [9 Regression] internal compiler error: in check, at
tree-vrp.c:188
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: law at redhat dot com
Target Milestone: ---
On x86-64, r267503 caused:
Executing on host: /export/project/git/gcc-bisect/master/267503/bld/gcc/xgcc
-B/export/project/git/gcc-bisect/master/267503/bld/gcc/
/export/project/git/gcc-bisect/gcc/gcc/testsuite/gcc.dg/torture/pr42667.c -m32
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O1 -w -S -o pr42667.s (timeout = 300)
spawn -ignore SIGHUP /export/project/git/gcc-bisect/master/267503/bld/gcc/xgcc
-B/export/project/git/gcc-bisect/master/267503/bld/gcc/
/export/project/git/gcc-bisect/gcc/gcc/testsuite/gcc.dg/torture/pr42667.c -m32
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O1 -w -S -o pr42667.s^M
during GIMPLE pass: dom^M
/export/project/git/gcc-bisect/gcc/gcc/testsuite/gcc.dg/torture/pr42667.c: In
function 'OnDisplay':^M
/export/project/git/gcc-bisect/gcc/gcc/testsuite/gcc.dg/torture/pr42667.c:7:6:
internal compiler error: in check, at tree-vrp.c:188^M
0x152ccee value_range_base::check()^M
../../../../gcc/gcc/tree-vrp.c:188^M
0x152c797 value_range_base::set(value_range_kind, tree_node*, tree_node*)^M
../../../../gcc/gcc/tree-vrp.c:83^M
0x1487429 get_range_info(tree_node const*, value_range_base&)^M
../../../../gcc/gcc/tree-ssanames.c:450^M
0x15f5267 vr_values::update_value_range(tree_node const*, value_range*)^M
../../../../gcc/gcc/vr-values.c:176^M
0x1e580f0 evrp_range_analyzer::record_ranges_from_stmt(gimple*, bool)^M
../../../../gcc/gcc/gimple-ssa-evrp-analyze.c:316^M
0x130d87f dom_opt_dom_walker::before_dom_children(basic_block_def*)^M
../../../../gcc/gcc/tree-ssa-dom.c:1467^M
0x1e0bbe3 dom_walker::walk(basic_block_def*)^M
../../../../gcc/gcc/domwalk.c:353^M
0x130b8e9 execute^M
../../../../gcc/gcc/tree-ssa-dom.c:706^M
Please submit a full bug report,^M
with preprocessed source if appropriate.^M
Please include the complete backtrace with any bug report.^M
See <https://gcc.gnu.org/bugs/> for instructions.^M
compiler exited with status 1
FAIL: gcc.dg/torture/pr42667.c -O1 (internal compiler error)
FAIL: gcc.dg/torture/pr42667.c -O1 (test for excess errors)
>From gcc-bugs-return-627318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:39:36 2019
Return-Path: <gcc-bugs-return-627318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63086 invoked by alias); 2 Jan 2019 14:39:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63037 invoked by uid 48); 2 Jan 2019 14:39:32 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88599] ICE in make_decl_rtl, at varasm.c:1337
Date: Wed, 02 Jan 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88599-4-9FNp7XGJtf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00127.txt.bz2
Content-length: 287
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88599
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
I cannot reproduce this. Either you need more flags, a more specific target,
some specific libc version (etc.), and/or some non-default configure arguments.
>From gcc-bugs-return-627319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 14:40:00 2019
Return-Path: <gcc-bugs-return-627319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63946 invoked by alias); 2 Jan 2019 14:40: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 63869 invoked by uid 48); 2 Jan 2019 14:39:54 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Wed, 02 Jan 2019 14:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-RNgqX3LymT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00128.txt.bz2
Content-length: 742
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #6 from gnzlbg <gonzalobg88 at gmail dot com> ---
> Why do you need more than that?
I'm reading raw data from a file which supposedly contains _Bool's and I'd like
to validate it (the _Bools could have been written to the file by a program
compiled with a different C toolchain).
> You can copy the bit-pattern from any _Bool with true value,
The standard does not guarantee that only one such bit-pattern exists AFAICT,
i.e., there might be multiple bit-patterns representing true and false, e.g.,
if only the first bit is used to represent true and false, and all other bits
are ignored (e.g., as opposed to just being zero, like the SysV AMD64 ABI
requires).
>From gcc-bugs-return-627320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:03:14 2019
Return-Path: <gcc-bugs-return-627320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98411 invoked by alias); 2 Jan 2019 15: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 98132 invoked by uid 48); 2 Jan 2019 15:03:10 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Wed, 02 Jan 2019 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88611-4-mvono9zOuT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00129.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Well. The following "fixes" this for me. Fortran folks?
Looks reasonable to me.
>From gcc-bugs-return-627321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:05:03 2019
Return-Path: <gcc-bugs-return-627321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106637 invoked by alias); 2 Jan 2019 15:05:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106317 invoked by uid 48); 2 Jan 2019 15:04:59 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34816] Missed optimisation in ANY and ALL with different kinds
Date: Wed, 02 Jan 2019 15:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-34816-4-Yyp8XS8RqJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00130.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34816
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Actually, I think a "simple" call to an inlined
function won't work.
I have now come to the conclusion that this is not worth it.
Let's resolve this one as WONTFIX (after more than 10 years).
>From gcc-bugs-return-627322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:07:06 2019
Return-Path: <gcc-bugs-return-627322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114300 invoked by alias); 2 Jan 2019 15:07:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114035 invoked by uid 48); 2 Jan 2019 15:07:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Wed, 02 Jan 2019 15:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88663-4-lgM5lcV8gK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00131.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Target Milestone|--- |9.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
So bogus range-info set...
>From gcc-bugs-return-627323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:18:50 2019
Return-Path: <gcc-bugs-return-627323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55065 invoked by alias); 2 Jan 2019 15:18:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55021 invoked by uid 48); 2 Jan 2019 15:18:46 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] New: False positive -Waddress-of-packed-member
Date: Wed, 02 Jan 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00132.txt.bz2
Content-length: 1298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
Bug ID: 88664
Summary: False positive -Waddress-of-packed-member
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nathan at gcc dot gnu.org
Target Milestone: ---
Created attachment 45316
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45316&action=edit
extracted from code using epoll_event structure
nathans@devvm2452:29>./cc1plus -Waddress-of-packed-member ../../../packed.cc
-quiet
../../../packed.cc: In function 'void foo(epoll_event*)':
../../../packed.cc:10:49: warning: taking address of packed member of
'epoll_event' may result in an unaligned pointer value
[-Waddress-of-packed-member]
10 | int *actionable = static_cast <int *> (event->ptr);
| ~~~~~~~^~~
But we're not taking the address of the packed field, we're converting the
value the field holds to a different pointer.
epoll_event is packed, and I imagine more code than mine squirrels away data
pointers in its data field. I suppose the FE could internally be taking a
reference to preserve lvalueness ...
>From gcc-bugs-return-627324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:23:50 2019
Return-Path: <gcc-bugs-return-627324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62275 invoked by alias); 2 Jan 2019 15:23:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62237 invoked by uid 48); 2 Jan 2019 15:23:46 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Wed, 02 Jan 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88663-4-WXH1m7I7SG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00133.txt.bz2
Content-length: 604
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
Assignee|unassigned at gcc dot gnu.org |law at redhat dot com
Ever confirmed|0 |1
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
A couple of my tester targets tripped this overnight. Mine.
>From gcc-bugs-return-627325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:24:03 2019
Return-Path: <gcc-bugs-return-627325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63374 invoked by alias); 2 Jan 2019 15:24:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63221 invoked by uid 55); 2 Jan 2019 15:23:59 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88130] [9 Regression] ICE in copy_function_or_variable, at lto-streamer-out.c:2315 since r260963
Date: Wed, 02 Jan 2019 15:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88130-4-PdTqgHFPRV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00134.txt.bz2
Content-length: 607
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88130
--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Wed Jan 2 15:23:27 2019
New Revision: 267515
URL: https://gcc.gnu.org/viewcvs?rev=267515&root=gcc&view=rev
Log:
PR lto/88130
* varpool.c (varpool_node::ctor_useable_for_folding_p): Also return
false at WPA time when body was removed.
* g++.dg/torture/pr88130.C: New testcase.
Added:
trunk/gcc/testsuite/g++.dg/torture/pr88130.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/varpool.c
>From gcc-bugs-return-627326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:24:39 2019
Return-Path: <gcc-bugs-return-627326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77569 invoked by alias); 2 Jan 2019 15:24:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76152 invoked by uid 55); 2 Jan 2019 15:24:34 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] False positive -Waddress-of-packed-member
Date: Wed, 02 Jan 2019 15:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88664-4-24P0vWdPuL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00135.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
--- Comment #1 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Author: nathan
Date: Wed Jan 2 15:23:56 2019
New Revision: 267516
URL: https://gcc.gnu.org/viewcvs?rev=267516&root=gcc&view=rev
Log:
gcc/cp/
* cxx-mapper.cc (server): Workaround PR c++/88664.
Modified:
branches/c++-modules/ChangeLog.modules
branches/c++-modules/gcc/cp/cxx-mapper.cc
>From gcc-bugs-return-627327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:25:41 2019
Return-Path: <gcc-bugs-return-627327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82698 invoked by alias); 2 Jan 2019 15:25:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82653 invoked by uid 48); 2 Jan 2019 15:25:37 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88130] [9 Regression] ICE in copy_function_or_variable, at lto-streamer-out.c:2315 since r260963
Date: Wed, 02 Jan 2019 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88130-4-gIEBZ1BKaB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00136.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88130
--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
This is fixed on mainline, but we should backport to gcc 7 and 8.
>From gcc-bugs-return-627328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:26:31 2019
Return-Path: <gcc-bugs-return-627328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102193 invoked by alias); 2 Jan 2019 15:26:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102074 invoked by uid 55); 2 Jan 2019 15:26:18 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48543] Collapse identical strings
Date: Wed, 02 Jan 2019 15: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: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-48543-4-IkellYJSty@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00137.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Wed Jan 2 15:25:47 2019
New Revision: 267517
URL: https://gcc.gnu.org/viewcvs?rev=267517&root=gcc&view=rev
Log:
2019-01-02 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/48543
* gfortran.dg/const_chararacter_merge.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/const_chararacter_merge.f90
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:27:34 2019
Return-Path: <gcc-bugs-return-627329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103877 invoked by alias); 2 Jan 2019 15:27: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 103790 invoked by uid 48); 2 Jan 2019 15:27:31 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88631] CTAD cannot deduce from () value initialization
Date: Wed, 02 Jan 2019 15:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88631-4-7kJTZdOszi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00138.txt.bz2
Content-length: 221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88631
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Yup, my patch fixes all the examples in PR 81486 as well. I think the
testcases are worth adding.
>From gcc-bugs-return-627330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:28:43 2019
Return-Path: <gcc-bugs-return-627330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106168 invoked by alias); 2 Jan 2019 15:28:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106057 invoked by uid 48); 2 Jan 2019 15:28:40 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81486] Class template argument deduction fails with (), succeeds with {}
Date: Wed, 02 Jan 2019 15:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-81486-4-oqmN5Twy20@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81486-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81486-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00139.txt.bz2
Content-length: 755
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81486
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
The examples now compile with my patch for PR 88631. I'll add them to the
testsuite. Thanks for reporting them.
>From gcc-bugs-return-627331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:31:07 2019
Return-Path: <gcc-bugs-return-627331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108589 invoked by alias); 2 Jan 2019 15:31: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 108534 invoked by uid 48); 2 Jan 2019 15:31:03 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48543] Collapse identical strings
Date: Wed, 02 Jan 2019 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-48543-4-ynWxxD4cs7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00140.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed (by whoever did this, thanks!) and test case committed, closing.
>From gcc-bugs-return-627332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:32:54 2019
Return-Path: <gcc-bugs-return-627332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111923 invoked by alias); 2 Jan 2019 15:32: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 111871 invoked by uid 48); 2 Jan 2019 15:32:50 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88658] [9 Regression] Intrinsic MAX1 returns a REAL result, should be INTEGER.
Date: Wed, 02 Jan 2019 15: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88658-4-7C9Yg7wSgt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00141.txt.bz2
Content-length: 382
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88658
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
>From gcc-bugs-return-627333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:37:52 2019
Return-Path: <gcc-bugs-return-627333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118046 invoked by alias); 2 Jan 2019 15:37: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 117990 invoked by uid 48); 2 Jan 2019 15:37:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 15:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85574-4-M8cd46Wx18@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00142.txt.bz2
Content-length: 1155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #18 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, so it looks like uncprop causes a lot of differences (minor dump
differences
appear from profile-estimate and printf-return-value2 as well).
--- prev-gcc/cc1.ltrans99.196t.uncprop1 2019-01-02 16:06:25.701672034 +0100
+++ gcc/cc1.ltrans99.196t.uncprop1 2019-01-02 16:19:03.713847999 +0100
@@ -20478,7 +20478,7 @@
<bb 230> [local count: 28992085]:
# reject_602 = PHI <reject_971(229), reject_600(656), reject_600(657),
reject_600(659), reject_600(655), reject_600(658), reject_951(873)>
# this_alternative_850 = PHI <this_alternative_686(229),
this_alternative_686(656), this_alternative_686(657),
this_alternative_686(659), this_alternative_686(655),
this_alternative_686(658), this_alternative_685(873)>
- # _44 = PHI <_2222(229), _2222(656), _2222(657), _2222(659), 1(655),
_2222(658), 1(873)>
+ # _44 = PHI <_2222(229), _2222(656), _2222(657), _2222(659), _2222(655),
_2222(658), 1(873)>
# DEBUG reject => reject_602
# DEBUG BEGIN_STMT
# DEBUG this_alternative_offmemok => offmemok_671
>From gcc-bugs-return-627334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:39:34 2019
Return-Path: <gcc-bugs-return-627334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120004 invoked by alias); 2 Jan 2019 15:39: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 119970 invoked by uid 48); 2 Jan 2019 15:39:30 -0000
From: "andrew at ishiboo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88623] gcc build uses CXX_FOR_BUILD but files have .c extension
Date: Wed, 02 Jan 2019 15:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew at ishiboo 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-88623-4-nOJtdvuZr9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88623-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88623-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00143.txt.bz2
Content-length: 269
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88623
--- Comment #3 from Andrew Paprocki <andrew at ishiboo dot com> ---
Sorry, I said 'libgcc', but I meant the 'gcc/' sub-directory. It is always
using the C++ compiler for the build and relying on the fact that `g++`
>From gcc-bugs-return-627335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:41:14 2019
Return-Path: <gcc-bugs-return-627335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122578 invoked by alias); 2 Jan 2019 15:41: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 122538 invoked by uid 48); 2 Jan 2019 15:41:10 -0000
From: "andrew at ishiboo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88623] gcc build uses CXX_FOR_BUILD but files have .c extension
Date: Wed, 02 Jan 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew at ishiboo 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-88623-4-5cd7bU2VDQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88623-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88623-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00144.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88623
--- Comment #4 from Andrew Paprocki <andrew at ishiboo dot com> ---
... relying on the fact that `g++` will compile the `.c` files as C.
>From gcc-bugs-return-627336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:42:47 2019
Return-Path: <gcc-bugs-return-627336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125065 invoked by alias); 2 Jan 2019 15:42:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124980 invoked by uid 48); 2 Jan 2019 15:42:43 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/87089] [9 regression] tree check: expected class 'type', have 'declaration' (namespace_decl) in type_with_linkage_p, at ipa-utils.h
Date: Wed, 02 Jan 2019 15: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87089-4-OJbzpjxXzK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00145.txt.bz2
Content-length: 2270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87089
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at redhat dot com
--- Comment #9 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
This is caused by:
_ZN4itpp1cILNS_1aE0EED2Ev/1 (itpp::c<<anonymous> >::~c() [with itpp::a
<anonymous> = itpp::b]) @0x7ffff70e9438
Type: function definition analyzed
Visibility: forced_by_abi public weak comdat_group:_ZN4itpp1cILNS_1aE0EED5Ev
one_only
Same comdat group as: _ZN4itpp1cILNS_1aE0EED1Ev/2
Address is taken.
Aux: @0x7ffff70e95a0
References: _ZTVN4itpp1cILNS_1aE0EEE/4 (addr)__gxx_personality_v0/8 (addr)
Referring: _ZN4itpp1cILNS_1aE0EED1Ev/2 (alias)
Function flags: body
Called by:
Calls: itpp::CFix::~CFix()/7
this is a destructor which is pointed to from virutal table, but it has no
DECL_VIRTUAL_P flag set. This makes free_lang_data to modify its context and
point to outer namespace rather than the containing polymorphic type.
Why we do not set VIRTUAL_P here?
>From gcc-bugs-return-627337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:45:32 2019
Return-Path: <gcc-bugs-return-627337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128332 invoked by alias); 2 Jan 2019 15:45:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128068 invoked by uid 48); 2 Jan 2019 15:45:21 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88140] [9 Regression] ICE: verify_gimple failed since r266325
Date: Wed, 02 Jan 2019 15:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88140-4-hGHxay91n5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00146.txt.bz2
Content-length: 469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88140
--- Comment #12 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I have committed the workaround as:
r267398 | hubicka | 2018-12-24 12:21:25 +0100 (Mon, 24 Dec 2018) | 6 lines
* tree.c (fld_simplified_type): Temporarily disable array
simplification.
* gcc.c-torture/pr88140.c: New testcase.
forgot to cut&past the PR specifier into the commit log.
Shall we retarget this to GCC 10 now?
>From gcc-bugs-return-627338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 15:54:49 2019
Return-Path: <gcc-bugs-return-627338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15146 invoked by alias); 2 Jan 2019 15:54: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 15109 invoked by uid 48); 2 Jan 2019 15:54:44 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88585] [9 Regression] ICE in fld_incomplete_type_of, at tree.c:5295
Date: Wed, 02 Jan 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-88585-4-K6XVehdcx9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88585-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88585-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00147.txt.bz2
Content-length: 4787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88585
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|ipa |lto
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Changing component to LTO.
This fails on the sanity check:
5295 gcc_assert (TYPE_CANONICAL (t2) != t2
5296 && TYPE_CANONICAL (t2) == TYPE_CANONICAL
(TREE_TYPE (t)));
which is supposed to check that TYPE_CANONICAL of newly created pointer to t2
points to right place.
In this case t2 is:
<record_type 0x7ffff7234930 S atomic packed type_0 VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff7234348 context <translation_unit_decl 0x7ffff70f4ca8 t.c>
pointer_to_this <pointer_type 0x7ffff72349d8>>
which is incomplete version of its TYPE_CANONICAL:
(gdb) p debug_tree (t2->type_common.canonical)
<record_type 0x7ffff7234348 S atomic packed type_0 SI
size <integer_cst 0x7ffff70e7ed0 type <integer_type 0x7ffff71000a8
bitsizetype> constant 32>
unit-size <integer_cst 0x7ffff70e7ee8 type <integer_type 0x7ffff7100000
sizetype> constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff7234348
fields <field_decl 0x7ffff710f2f8 x
type <integer_type 0x7ffff71005e8 int sizes-gimplified public SI size
<integer_cst 0x7ffff70e7ed0 32> unit-size <integer_cst 0x7ffff70e7ee8 4>
align:32 warn_if_not_align:0 symtab:0 alias-set 2 canonical-type
0x7ffff71005e8 precision:32 min <integer_cst 0x7ffff70e7e88 -2147483648> max
<integer_cst 0x7ffff70e7ea0 2147483647>
pointer_to_this <pointer_type 0x7ffff71089d8>>
packed SI t.c:1:16 size <integer_cst 0x7ffff70e7ed0 32> unit-size
<integer_cst 0x7ffff70e7ee8 4>
align:8 warn_if_not_align:0 offset_align 128
offset <integer_cst 0x7ffff70e7cc0 constant 0>
bit-offset <integer_cst 0x7ffff70e7d08 constant 0> context <record_type
0x7ffff720fd20 S>> context <translation_unit_decl 0x7ffff70f4ca8 t.c>
pointer_to_this <pointer_type 0x7ffff72343f0>>
TREE_TYPE (t) is:
(gdb) p debug_tree (t->typed.type)
<record_type 0x7ffff720fdc8 S atomic packed type_0 SI
size <integer_cst 0x7ffff70e7ed0 type <integer_type 0x7ffff71000a8
bitsizetype> constant 32>
unit-size <integer_cst 0x7ffff70e7ee8 type <integer_type 0x7ffff7100000
sizetype> constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff720fdc8
fields <field_decl 0x7ffff710f2f8 x
type <integer_type 0x7ffff71005e8 int sizes-gimplified public SI size
<integer_cst 0x7ffff70e7ed0 32> unit-size <integer_cst 0x7ffff70e7ee8 4>
align:32 warn_if_not_align:0 symtab:0 alias-set 2 canonical-type
0x7ffff71005e8 precision:32 min <integer_cst 0x7ffff70e7e88 -2147483648> max
<integer_cst 0x7ffff70e7ea0 2147483647>
pointer_to_this <pointer_type 0x7ffff71089d8>>
packed SI t.c:1:16 size <integer_cst 0x7ffff70e7ed0 32> unit-size
<integer_cst 0x7ffff70e7ee8 4>
align:8 warn_if_not_align:0 offset_align 128
offset <integer_cst 0x7ffff70e7cc0 constant 0>
bit-offset <integer_cst 0x7ffff70e7d08 constant 0> context <record_type
0x7ffff720fd20 S>> context <translation_unit_decl 0x7ffff70f4ca8 t.c>
pointer_to_this <pointer_type 0x7ffff7234000>>
and TYPE_CANONICAL (TREE_TYPE (t)) is:
<record_type 0x7ffff720fdc8 S atomic packed type_0 SI
size <integer_cst 0x7ffff70e7ed0 type <integer_type 0x7ffff71000a8
bitsizetype> constant 32>
unit-size <integer_cst 0x7ffff70e7ee8 type <integer_type 0x7ffff7100000
sizetype> constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff720fdc8
fields <field_decl 0x7ffff710f2f8 x
type <integer_type 0x7ffff71005e8 int sizes-gimplified public SI size
<integer_cst 0x7ffff70e7ed0 32> unit-size <integer_cst 0x7ffff70e7ee8 4>
align:32 warn_if_not_align:0 symtab:0 alias-set 2 canonical-type
0x7ffff71005e8 precision:32 min <integer_cst 0x7ffff70e7e88 -2147483648> max
<integer_cst 0x7ffff70e7ea0 2147483647>
pointer_to_this <pointer_type 0x7ffff71089d8>>
packed SI t.c:1:16 size <integer_cst 0x7ffff70e7ed0 32> unit-size
<integer_cst 0x7ffff70e7ee8 4>
align:8 warn_if_not_align:0 offset_align 128
offset <integer_cst 0x7ffff70e7cc0 constant 0>
bit-offset <integer_cst 0x7ffff70e7d08 constant 0> context <record_type
0x7ffff720fd20 S>> context <translation_unit_decl 0x7ffff70f4ca8 t.c>
pointer_to_this <pointer_type 0x7ffff7234000>>
So we have two versions of the packed structure, I am not sure why?
>From gcc-bugs-return-627339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 16:00:02 2019
Return-Path: <gcc-bugs-return-627339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28499 invoked by alias); 2 Jan 2019 16:00: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 25908 invoked by uid 48); 2 Jan 2019 15:59:58 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86875] [8/9 Regression] ICE in tsubst_copy, at cp/pt.c:15478
Date: Wed, 02 Jan 2019 16:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-86875-4-yQmTTkDj17@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00148.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86875
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed it's fixed now. Reducing & adding the testcase then.
>From gcc-bugs-return-627340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 16:10:23 2019
Return-Path: <gcc-bugs-return-627340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101659 invoked by alias); 2 Jan 2019 16: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 99061 invoked by uid 48); 2 Jan 2019 16:10:18 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81239] std::__cxx11::string& visible in gcc warning output
Date: Wed, 02 Jan 2019 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81239-4-kicflBxbzI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00149.txt.bz2
Content-length: 297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81239
--- Comment #10 from Jonny Grant <jg at jguk dot org> ---
Would you agree "abi11" would not have suffered the "cxx11" ambiguity?
Hope this can be avoided next time another ABI needs to be added to accommodate
a change in language behaviour.
>From gcc-bugs-return-627341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 16:12:58 2019
Return-Path: <gcc-bugs-return-627341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116460 invoked by alias); 2 Jan 2019 16:12: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 116414 invoked by uid 48); 2 Jan 2019 16:12:54 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Wed, 02 Jan 2019 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88663-4-sxChr1pPcR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00150.txt.bz2
Content-length: 320
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
--- Comment #3 from Jeffrey A. Law <law at redhat dot com> ---
I guess I should have kept going last night, this is fixed by the next patch in
the series. I thought I had all the dependencies between them resolved, but
clearly not. I'll have this fixed shortly.
>From gcc-bugs-return-627342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 16:25:16 2019
Return-Path: <gcc-bugs-return-627342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60555 invoked by alias); 2 Jan 2019 16:25:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57417 invoked by uid 48); 2 Jan 2019 16:25:09 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 16:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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:
Message-ID: <bug-85574-4-5rzmcTnJyk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00151.txt.bz2
Content-length: 2637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #19 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
gcc 5 has:
inline bool
val_ssa_equiv_hash_traits::equal_keys (tree value1, tree value2)
{
return operand_equal_p (value1, value2, 0);
}
/* Free an instance of equiv_hash_elt. */
template<typename T>
inline void
val_ssa_equiv_hash_traits::remove (T &elt)
{
elt.m_value.release ();
}
while in mainline we seem to compare addresses... Looks like wrong update to
hash_map.
>From gcc-bugs-return-627343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 16:27:35 2019
Return-Path: <gcc-bugs-return-627343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44040 invoked by alias); 2 Jan 2019 16:27: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 39293 invoked by uid 55); 2 Jan 2019 16:27:31 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88647] Rejects valid program dereferencing pointer with incomplete reference type.
Date: Wed, 02 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88647-4-YyKQci89HN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00152.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88647
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
6.3.2.1#2 (conversion of lvalues to rvalues): "If the lvalue has an
incomplete type and does not have array type, the behavior is undefined.".
Cf. bug 36941 (noting how DR#106 confuses things by allowing dereferences
of pointers to qualified void).
>From gcc-bugs-return-627344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 16:37:36 2019
Return-Path: <gcc-bugs-return-627344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56246 invoked by alias); 2 Jan 2019 16:37:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51186 invoked by uid 48); 2 Jan 2019 16:37:31 -0000
From: "nsl at fireeye dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88539] A memory leak issue was discovered in cplus-dem.c
Date: Wed, 02 Jan 2019 16:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nsl at fireeye 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-88539-4-5EwBboQjRw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88539-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88539-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00153.txt.bz2
Content-length: 372
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88539
nsl at fireeye dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nsl at fireeye dot com
--- Comment #2 from nsl at fireeye dot com ---
This looks to be CVE-2018-20657.
>From gcc-bugs-return-627345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:03:24 2019
Return-Path: <gcc-bugs-return-627345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25003 invoked by alias); 2 Jan 2019 17:03:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24936 invoked by uid 55); 2 Jan 2019 17:03:18 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 17:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
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-85574-4-T6js23BMwI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00154.txt.bz2
Content-length: 3001
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #20 from rguenther at suse dot de <rguenther at suse dot de> ---
On January 2, 2019 5:25:09 PM GMT+01:00, "hubicka at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
>
>--- Comment #19 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
>gcc 5 has:
>inline bool
>
>val_ssa_equiv_hash_traits::equal_keys (tree value1, tree value2)
>
>{
>
>return operand_equal_p (value1, value2, 0);
>
>}
>
>
>/* Free an instance of equiv_hash_elt. */
>
>
>template<typename T>
>
>inline void
>
>val_ssa_equiv_hash_traits::remove (T &elt)
>
>{
>
>elt.m_value.release ();
>
>}
>
>
>while in mainline we seem to compare addresses... Looks like wrong
>update to
>hash_map.
But still it doesn't explain differences in tree sharing between stage2 and
three.
But yes, I'll go track things down a bit more.
>From gcc-bugs-return-627346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:07:38 2019
Return-Path: <gcc-bugs-return-627346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64041 invoked by alias); 2 Jan 2019 17:07: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 63968 invoked by uid 55); 2 Jan 2019 17:07:33 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86875] [8/9 Regression] ICE in tsubst_copy, at cp/pt.c:15478
Date: Wed, 02 Jan 2019 17:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86875-4-L17H9PJE85@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00155.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86875
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Jan 2 17:07:02 2019
New Revision: 267519
URL: https://gcc.gnu.org/viewcvs?rev=267519&root=gcc&view=rev
Log:
PR c++/86875
* g++.dg/cpp1y/lambda-generic-86875.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp1y/lambda-generic-86875.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:09:15 2019
Return-Path: <gcc-bugs-return-627347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69606 invoked by alias); 2 Jan 2019 17:09:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69528 invoked by uid 48); 2 Jan 2019 17:09:11 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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:
Message-ID: <bug-85574-4-JDQLrJYrFv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00156.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #21 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Looks like last minute change in this patch
https://gcc.gnu.org/ml/gcc-cvs/2014-06/msg00838.html
https://gcc.gnu.org/ml/gcc-patches/2014-06/msg01600.html
>From gcc-bugs-return-627348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:12:33 2019
Return-Path: <gcc-bugs-return-627348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58401 invoked by alias); 2 Jan 2019 17:12: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 53803 invoked by uid 48); 2 Jan 2019 17:12:30 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 17:12: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: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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: attachments.created
Message-ID: <bug-85574-4-FggERKOGoR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00157.txt.bz2
Content-length: 266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #22 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 45318
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45318&action=edit
patch for operand_equal_p in tree-ssa-uncprop
>From gcc-bugs-return-627349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:26:45 2019
Return-Path: <gcc-bugs-return-627349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4420 invoked by alias); 2 Jan 2019 17:26:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4264 invoked by uid 48); 2 Jan 2019 17:26:41 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86875] [8/9 Regression] ICE in tsubst_copy, at cp/pt.c:15478
Date: Wed, 02 Jan 2019 17:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86875-4-LMJ78fYPwE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00158.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86875
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Done.
>From gcc-bugs-return-627350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:42:05 2019
Return-Path: <gcc-bugs-return-627350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120709 invoked by alias); 2 Jan 2019 17:42: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 120571 invoked by uid 48); 2 Jan 2019 17:42:00 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88605] vector extensions: Widening or conversion generates inefficient or scalar code.
Date: Wed, 02 Jan 2019 17:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin 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-88605-4-xPxhB0MGsl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88605-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88605-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00159.txt.bz2
Content-length: 629
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88605
--- Comment #4 from Devin Hussey <husseydevin at gmail dot com> ---
I also want to note that LLVM is probably a good place to look. They have been
pushing to remove as many intrinsic builtins as they can in favor of idiomatic
code.
This has multiple advantages:
1. You can open up <emmintrin.h> and see what x intrinsic really does (many
SIMD instructions have inadequate documentation)
2. Platform independent intrinsic headers
3. More useful vector extensions
Should we make a metabug for this?
Such as "Improve vector extension pattern recognition" or something?
>From gcc-bugs-return-627351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:53:37 2019
Return-Path: <gcc-bugs-return-627351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2446 invoked by alias); 2 Jan 2019 17:53: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 2382 invoked by uid 48); 2 Jan 2019 17:53:32 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88600] GCC rejects attributes on type aliases, while clang accepts them
Date: Wed, 02 Jan 2019 17:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88600-4-JIlH1FA4pt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88600-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88600-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00160.txt.bz2
Content-length: 1367
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88600
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
The grammar implies the original form of the alias-declaration should be
accepted with standard C++ attributes so I think it would make sense to accept
it with GNU attributes as well:
alias-declaration:
using identifier attribute-specifier-seq opt = defining-type-id;
defining-type-id:
defining-type-specifier-seq abstract-declarator opt
defining-type-specifier-seq:
defining-type-specifier attribute-specifier-seq opt
defining-type-specifier defining-type-specifier-seq
With that, I would expect the following two declarations to be equivalent:
template <class T>
using U = __attribute__ ((__vector_size__ (8))) T;
template <class T>
using V = [[gnu::vector_size (8)]] T;
Here GCC rejects both forms while Clang accepts the GNU form but (ironically)
rejects the standard form.
>From gcc-bugs-return-627352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 17:56:58 2019
Return-Path: <gcc-bugs-return-627352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4924 invoked by alias); 2 Jan 2019 17:56:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4878 invoked by uid 48); 2 Jan 2019 17:56:54 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87729] Please include -Woverloaded-virtual in -Wall
Date: Wed, 02 Jan 2019 17:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-87729-4-qK5Xw1U2ng@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00161.txt.bz2
Content-length: 272
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87729
--- Comment #2 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
Here you are:
[code]
class Foo
{
public:
virtual void f(int);
};
class Bar : public Foo
{
public:
virtual void f(short);
};
[/code]
>From gcc-bugs-return-627353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 18:03:27 2019
Return-Path: <gcc-bugs-return-627353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15625 invoked by alias); 2 Jan 2019 18:03:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15569 invoked by uid 48); 2 Jan 2019 18:03:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Wed, 02 Jan 2019 18:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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-85052-4-4kfoJasDjN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00162.txt.bz2
Content-length: 688
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45319
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45319&action=edit
gcc9-pr85052.patch
Untested implementation. Some further work is needed to improve code
generation for the narrowing or widening conversions.
>From gcc-bugs-return-627354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 18:26:13 2019
Return-Path: <gcc-bugs-return-627354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43884 invoked by alias); 2 Jan 2019 18:26:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43834 invoked by uid 48); 2 Jan 2019 18:26:09 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88642] Accepts ill-formed program with invalid scalar initialization syntax.
Date: Wed, 02 Jan 2019 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88642-4-xUtUXiZ32D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88642-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88642-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00163.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88642
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. Clang rejects the code with
$ clang -S --pedantic-errors pr88642.c
pr88642.c:4:15: error: too many braces around scalar initializer
[-Werror,-Wmany-braces-around-scalar-init]
int x = { { 0 } };
^~~~~
1 error generated.
>From gcc-bugs-return-627355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 18:31:28 2019
Return-Path: <gcc-bugs-return-627355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54420 invoked by alias); 2 Jan 2019 18:31:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54388 invoked by uid 55); 2 Jan 2019 18:31:22 -0000
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Wed, 02 Jan 2019 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88663-4-Nl1qcrEgwf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00164.txt.bz2
Content-length: 1119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
--- Comment #4 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Wed Jan 2 18:30:50 2019
New Revision: 267520
URL: https://gcc.gnu.org/viewcvs?rev=267520&root=gcc&view=rev
Log:
PR middle-end/88663
* gimple-fold.c (get_range_strlen): Update prototype to no longer
need the flexp argument.
(get_range_strlen_tree): Drop flexp argument. Drop flexp argument
from calls to get_range_strlen. Update comments. Just update
VAL for an unterminated const char array and let the reset of the
code handle it normally. No longer try to set *flexp. Adjust
return value.
(get_range_strlen): Update for the new get_range_strlen API.
(get_maxval_strlen): Similarly.
(gimple_fold_builtin_strlen): Handle update meaning of return value
from get_range_strlen.
* gimple-ssa-sprintf.c (get_string_length): Update for the new
get_range_strlen API.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimple-fold.c
trunk/gcc/gimple-ssa-sprintf.c
>From gcc-bugs-return-627356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:00:25 2019
Return-Path: <gcc-bugs-return-627356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39892 invoked by alias); 2 Jan 2019 19:00:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39334 invoked by uid 48); 2 Jan 2019 19:00:03 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 19:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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:
Message-ID: <bug-85574-4-4203gHqHzp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00165.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #23 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Patch needs ">>>" to be repaced by "> > >" to bootstrap, but then I get 756
mismatches building firefox, while previously it was 1300 and before the
rebuild_type_inheritance_graph 6273, so we are improving. I will look into the
remaining cases.
Can't the type sharing difference come from GTY((cache)) use in tree.h?
>From gcc-bugs-return-627357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:15:59 2019
Return-Path: <gcc-bugs-return-627357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11193 invoked by alias); 2 Jan 2019 19:15:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11111 invoked by uid 48); 2 Jan 2019 19:15:52 -0000
From: "geir at cray dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88666] New: GCC 8.2.- gets Internal Compiler Error: seg fault; GCC 8.1.0 works fine
Date: Wed, 02 Jan 2019 19:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: geir at cray 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-88666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00166.txt.bz2
Content-length: 5545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
Bug ID: 88666
Summary: GCC 8.2.- gets Internal Compiler Error: seg fault;
GCC 8.1.0 works fine
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: geir at cray dot com
Target Milestone: ---
Simple reproducer code causes a seg fault during compile with gcc 8.2.0. The
reproducer does not seg fault for gcc 8.1.0
$ cat repro.c
#include <string.h>
#include <stdlib.h>
#include <stdio.h>
#include <stdint.h>
int64_t foo (int64_t max, FILE *in)
{
int64_t count = 0;
const int64_t MAXLINE = 1024;
char buff[MAXLINE];
while (!feof(in) && count < max) {
if (fgets(buff, sizeof(buff), in) != NULL) {
// gcc 8.2 segfaults !!
if (strncmp (&buff[0], "QUIT", 4) == 0)
break;
// this is OK:
if (strncmp (buff, "QUIT", 4) == 0)
break;
}
}
return count;
}
$ gcc --version
gcc (GCC) 8.1.0 20180502 (Cray Inc.)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gcc -c repro.c
$ module swap gcc/8.1.0 gcc/8.2.0
$ gcc --version
gcc (GCC) 8.2.0 20180726 (Cray Inc.)
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
$ gcc -c repro.c
during RTL pass: expand
repro.c: In function 'foo':
repro.c:17:11: internal compiler error: Segmentation fault
if (strncmp (&buff[0], "QUIT", 4) == 0)
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0xa8de4f crash_signal
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/toplev.c:325
0x6eeb25 wi::extended_tree<192>::get_len() const
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/tree.h:5572
0x6eeb25 wi::int_traits<generic_wide_int<wi::extended_tree<192> >
>::decompose(long*, unsigned int, generic_wide_int<wi::extended_tree<192> >
const&)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/wide-int.h:934
0x6eeb25 wide_int_ref_storage<true,
false>::wide_int_ref_storage<generic_wide_int<wi::extended_tree<192> >
>(generic_wide_int<wi::extended_tree<192> > const&, unsigned int)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/wide-int.h:983
0x6eeb25 generic_wide_int<wide_int_ref_storage<true, false>
>::generic_wide_int<generic_wide_int<wi::extended_tree<192> >
>(generic_wide_int<wi::extended_tree<192> > const&, unsigned int)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/wide-int.h:758
0x6eeb25 bool wi::lts_p<generic_wide_int<wi::extended_tree<192> >,
generic_wide_int<wi::extended_tree<192> >
>(generic_wide_int<wi::extended_tree<192> > const&,
generic_wide_int<wi::extended_tree<192> > const&)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/wide-int.h:1849
0x6eeb25 wi::binary_traits<generic_wide_int<wi::extended_tree<192> >,
generic_wide_int<wi::extended_tree<192> >,
wi::int_traits<generic_wide_int<wi::extended_tree<192> > >::precision_type,
wi::int_traits<generic_wide_int<wi::extended_tree<192> >
>::precision_type>::signed_predicate_result operator<
<generic_wide_int<wi::extended_tree<192> >,
generic_wide_int<wi::extended_tree<192> >
>(generic_wide_int<wi::extended_tree<192> > const&,
generic_wide_int<wi::extended_tree<192> > const&)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/wide-int.h:3170
0x6eeb25 tree_int_cst_lt(tree_node const*, tree_node const*)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/tree.h:5728
0x6eeb25 maybe_warn_nonstring_arg(tree_node*, tree_node*)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/calls.c:1716
0x6f053a maybe_warn_nonstring_arg(tree_node*, tree_node*)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/calls.c:1627
0x6f053a initialize_argument_information
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/calls.c:2321
0x6f053a expand_call(tree_node*, rtx_def*, int)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/calls.c:3713
0x6e4286 expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/builtins.c:6656
0x7f1679 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/expr.c:11005
0x7fa35b store_expr_with_bounds(tree_node*, rtx_def*, int, bool, bool,
tree_node*)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/expr.c:5635
0x7fb5b3 expand_assignment(tree_node*, tree_node*, bool)
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/expr.c:5403
0x7015d8 expand_call_stmt
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/cfgexpand.c:2688
0x7015d8 expand_gimple_stmt_1
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/cfgexpand.c:3624
0x7015d8 expand_gimple_stmt
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/cfgexpand.c:3790
0x70287f expand_gimple_basic_block
../../cray-gcc-8.2.0-201808172015.9a091ef8ec76a/gcc/cfgexpand.c:5819
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$
>From gcc-bugs-return-627358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:16:34 2019
Return-Path: <gcc-bugs-return-627358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12150 invoked by alias); 2 Jan 2019 19:16: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 12107 invoked by uid 48); 2 Jan 2019 19:16:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7/8/9 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Wed, 02 Jan 2019 19:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88644-4-IOJVuTCRqK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00167.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
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 45320
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45320&action=edit
gcc9-pr88644.patch
Untested fix.
>From gcc-bugs-return-627360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:27:18 2019
Return-Path: <gcc-bugs-return-627360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23243 invoked by alias); 2 Jan 2019 19:27:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23204 invoked by uid 48); 2 Jan 2019 19:27:14 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Wed, 02 Jan 2019 19:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88638-4-tvHzFCqmN4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00169.txt.bz2
Content-length: 379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
>From gcc-bugs-return-627359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:27:02 2019
Return-Path: <gcc-bugs-return-627359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22503 invoked by alias); 2 Jan 2019 19:27: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 22428 invoked by uid 48); 2 Jan 2019 19:26:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Wed, 02 Jan 2019 19:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88638-4-nvBFsV0RMU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00168.txt.bz2
Content-length: 743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
At a minimum, the warning on line 15 is not intended. The change in r266195
needs to also take Objective C strings into account analogously to how they are
being handled by valid_stringptr_type_p() in c-format.c.
>From gcc-bugs-return-627361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:35:55 2019
Return-Path: <gcc-bugs-return-627361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30965 invoked by alias); 2 Jan 2019 19:35: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 30892 invoked by uid 55); 2 Jan 2019 19:35:51 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 19:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
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-85574-4-xpbRcoEgLp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00170.txt.bz2
Content-length: 554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #24 from Jan Hubicka <hubicka at ucw dot cz> ---
> Patch needs ">>>" to be repaced by "> > >" to bootstrap, but then I get 756
> mismatches building firefox, while previously it was 1300 and before the
> rebuild_type_inheritance_graph 6273, so we are improving. I will look into the
> remaining cases.
Actually I was wrong - grepped wrong file. Still 1300 warnings. I am
looking into that - perhaps these are same problems.
Still I think the patch for uncprop makes sense.
Honza
>From gcc-bugs-return-627362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:43:32 2019
Return-Path: <gcc-bugs-return-627362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48138 invoked by alias); 2 Jan 2019 19:43:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45118 invoked by uid 55); 2 Jan 2019 19:43:27 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88605] vector extensions: Widening or conversion generates inefficient or scalar code.
Date: Wed, 02 Jan 2019 19:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88605-4-k2OUr1Bb1I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88605-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88605-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00171.txt.bz2
Content-length: 973
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88605
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On January 2, 2019 6:42:00 PM GMT+01:00, husseydevin at gmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88605
>
>--- Comment #4 from Devin Hussey <husseydevin at gmail dot com> ---
>I also want to note that LLVM is probably a good place to look. They
>have been
>pushing to remove as many intrinsic builtins as they can in favor of
>idiomatic
>code.
>
>This has multiple advantages:
>1. You can open up <emmintrin.h> and see what x intrinsic really does
>(many
>SIMD instructions have inadequate documentation)
> 2. Platform independent intrinsic headers
> 3. More useful vector extensions
>
>Should we make a metabug for this?
>Such as "Improve vector extension pattern recognition" or something?
I think we have one for the generic vector extension where this would fit. If
kit create one.
>From gcc-bugs-return-627363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:45:50 2019
Return-Path: <gcc-bugs-return-627363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64683 invoked by alias); 2 Jan 2019 19:45:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64588 invoked by uid 48); 2 Jan 2019 19:45:46 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88659] [9 Regression] ICE in maybe_warn_nonstring_arg at gcc/calls.c:1688 since r267503
Date: Wed, 02 Jan 2019 19:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-88659-4-oyjiTdNhjP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00172.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88659
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-02
CC| |msebor at gcc dot gnu.org
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> ---
Confirmed. Let me handle it.
>From gcc-bugs-return-627364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 19:50:54 2019
Return-Path: <gcc-bugs-return-627364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70073 invoked by alias); 2 Jan 2019 19:50: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 69937 invoked by uid 55); 2 Jan 2019 19:50:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87304] [9 regression] gcc.dg/vect/bb-slp-over-widen-1.c fails starting with r262371
Date: Wed, 02 Jan 2019 19:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-87304-4-JbbwwjkY9w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87304-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87304-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00173.txt.bz2
Content-length: 515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87304
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 2 19:50:13 2019
New Revision: 267528
URL: https://gcc.gnu.org/viewcvs?rev=267528&root=gcc&view=rev
Log:
PR testsuite/87304
* gcc.dg/vect/bb-slp-over-widen-1.c: Expect basic block vectorized
messages only on vect_hw_misalign targets.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/vect/bb-slp-over-widen-1.c
>From gcc-bugs-return-627365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:02:19 2019
Return-Path: <gcc-bugs-return-627365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122676 invoked by alias); 2 Jan 2019 20:02:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122592 invoked by uid 48); 2 Jan 2019 20:02:14 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7/8/9 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Wed, 02 Jan 2019 20:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88644-4-TJNBTJhdaA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00174.txt.bz2
Content-length: 2730
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
works for me with following addition to correct the length of the (now correct)
subtypes sections.
-----
diff --git a/gcc/testsuite/gcc.dg/pubtypes-2.c
b/gcc/testsuite/gcc.dg/pubtypes-2.c
index 3ac3a38..6669f3d 100644
--- a/gcc/testsuite/gcc.dg/pubtypes-2.c
+++ b/gcc/testsuite/gcc.dg/pubtypes-2.c
@@ -2,7 +2,7 @@
/* { dg-options "-O0 -gdwarf-2 -dA" } */
/* { dg-skip-if "Unmatchable assembly" { mmix-*-* } } */
/* { dg-final { scan-assembler "__debug_pubtypes" } } */
-/* { dg-final { scan-assembler "long+\[ \t\]+0x13b+\[ \t\]+\[#;]+\[ \t\]+Pub
Info Length" } } */
+/* { dg-final { scan-assembler "long+\[ \t\]+0x12e+\[ \t\]+\[#;]+\[ \t\]+Pub
Info Length" } } */
/* { dg-final { scan-assembler "used_struct\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
/* { dg-final { scan-assembler-not "unused_struct\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
diff --git a/gcc/testsuite/gcc.dg/pubtypes-3.c
b/gcc/testsuite/gcc.dg/pubtypes-3.c
index 6fa1940..345e4ed 100644
--- a/gcc/testsuite/gcc.dg/pubtypes-3.c
+++ b/gcc/testsuite/gcc.dg/pubtypes-3.c
@@ -2,7 +2,7 @@
/* { dg-options "-O0 -gdwarf-2 -dA" } */
/* { dg-skip-if "Unmatchable assembly" { mmix-*-* } } */
/* { dg-final { scan-assembler "__debug_pubtypes" } } */
-/* { dg-final { scan-assembler "long+\[ \t\]+0x13b+\[ \t\]+\[#;]+\[ \t\]+Pub
Info Length" } } */
+/* { dg-final { scan-assembler "long+\[ \t\]+0x12e+\[ \t\]+\[#;]+\[ \t\]+Pub
Info Length" } } */
/* { dg-final { scan-assembler "used_struct\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
/* { dg-final { scan-assembler-not "unused_struct\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
/* { dg-final { scan-assembler-not "\"list_name_type\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
diff --git a/gcc/testsuite/gcc.dg/pubtypes-4.c
b/gcc/testsuite/gcc.dg/pubtypes-4.c
index b2f520d..da2f9b0 100644
--- a/gcc/testsuite/gcc.dg/pubtypes-4.c
+++ b/gcc/testsuite/gcc.dg/pubtypes-4.c
@@ -2,7 +2,7 @@
/* { dg-options "-O0 -gdwarf-2 -dA" } */
/* { dg-skip-if "Unmatchable assembly" { mmix-*-* } } */
/* { dg-final { scan-assembler "__debug_pubtypes" } } */
-/* { dg-final { scan-assembler "long+\[ \t\]+0x172+\[ \t\]+\[#;]+\[ \t\]+Pub
Info Length" } } */
+/* { dg-final { scan-assembler "long+\[ \t\]+0x165+\[ \t\]+\[#;]+\[ \t\]+Pub
Info Length" } } */
/* { dg-final { scan-assembler "used_struct\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
/* { dg-final { scan-assembler-not "unused_struct\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
/* { dg-final { scan-assembler "\"list_name_type\\\\0\"+\[ \t\]+\[#;]+\[
\t\]+external name" } } */
>From gcc-bugs-return-627366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:09:03 2019
Return-Path: <gcc-bugs-return-627366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130894 invoked by alias); 2 Jan 2019 20:09: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 130816 invoked by uid 48); 2 Jan 2019 20:08:59 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88647] Rejects valid program dereferencing pointer with incomplete reference type.
Date: Wed, 02 Jan 2019 20:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88647-4-bCau76vgn9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00175.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88647
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Thanks. That explains it.
>From gcc-bugs-return-627367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:10:29 2019
Return-Path: <gcc-bugs-return-627367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2454 invoked by alias); 2 Jan 2019 20:10: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 1907 invoked by uid 48); 2 Jan 2019 20:10:23 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84478] [8 Regression] pdftex miscompilation on i386
Date: Wed, 02 Jan 2019 20:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-84478-4-lX8BqQu0uA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00176.txt.bz2
Content-length: 1183
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |ro at gcc dot gnu.org
Resolution|FIXED |---
--- Comment #5 from Rainer Orth <ro at gcc dot gnu.org> ---
The new testcase FAILs e.g. on i386-pc-solaris2.11 and sparc-sun-solaris2.11
(32-bit only) at -O1 and above:
+FAIL: gcc.c-torture/execute/pr84478.c -O1 execution test
+FAIL: gcc.c-torture/execute/pr84478.c -O2 execution test
+FAIL: gcc.c-torture/execute/pr84478.c -O2 -flto execution test
+FAIL: gcc.c-torture/execute/pr84478.c -O2 -flto -flto-partition=none
execution test
+FAIL: gcc.c-torture/execute/pr84478.c -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
+FAIL: gcc.c-torture/execute/pr84478.c -O3 -g execution test
According to gcc-testresult postings, the same happens on a couple of other
targets, including i686-pc-linux-gnu.
>From gcc-bugs-return-627368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:13:38 2019
Return-Path: <gcc-bugs-return-627368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6135 invoked by alias); 2 Jan 2019 20:13:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6074 invoked by uid 48); 2 Jan 2019 20:13:33 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88582] GCC does not unqualify return types in the case of _Atomic qualified return type.
Date: Wed, 02 Jan 2019 20:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-88582-4-GHEtBoM0cf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00177.txt.bz2
Content-length: 412
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88582
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |INVALID
--- Comment #5 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Thanks for the explanation.
>From gcc-bugs-return-627369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:14:49 2019
Return-Path: <gcc-bugs-return-627369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7761 invoked by alias); 2 Jan 2019 20:14: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 7681 invoked by uid 48); 2 Jan 2019 20:14:45 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7/8/9 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Wed, 02 Jan 2019 20:14: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: iains 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88644-4-wO4kAJS4QI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00178.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #4 from Iain Sandoe <iains at gcc dot gnu.org> ---
will do a complete test suite run now, to catch any other changed lengths.
>From gcc-bugs-return-627370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:21:25 2019
Return-Path: <gcc-bugs-return-627370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20213 invoked by alias); 2 Jan 2019 20:21:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20117 invoked by uid 48); 2 Jan 2019 20:21:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84478] [8 Regression] pdftex miscompilation on i386
Date: Wed, 02 Jan 2019 20:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84478-4-TLFGF5BzHh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00179.txt.bz2
Content-length: 252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
If this is a new regression please open a new bug for it. It's probably a
fallout from r267503 or one of the other related changes.
>From gcc-bugs-return-627371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:33:52 2019
Return-Path: <gcc-bugs-return-627371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44402 invoked by alias); 2 Jan 2019 20:33:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44330 invoked by uid 48); 2 Jan 2019 20:33:46 -0000
From: "gary_mills at fastmail dot fm" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Wed, 02 Jan 2019 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary_mills at fastmail dot fm
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-YDqDKS7g5x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00180.txt.bz2
Content-length: 639
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #21 from Gary Mills <gary_mills at fastmail dot fm> ---
Most of the words in the title are wrong now. I'm attempting to build gcc-7
now. The ICE occurs on both SPARC and x86 systems. It only happens with the
native assembler. The result is a structure that contains many NULL pointers,
which cause a segmentation violation when xgcc dereferences one of the NULL
pointers.
I've been attempting to find the origin of this structure by examining the
source, without success. Can someone show me a debugging technique that will
reveal the origin of this structure?
>From gcc-bugs-return-627372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:49:22 2019
Return-Path: <gcc-bugs-return-627372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65648 invoked by alias); 2 Jan 2019 20:49: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 65565 invoked by uid 48); 2 Jan 2019 20:49:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88635] [8 Regression] Assembler error when building with "-g -O2 -m32"
Date: Wed, 02 Jan 2019 20:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: assemble-failure, 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.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88635-4-ekdZpySTIe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00181.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88635
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45321
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45321&action=edit
gcc9-pr88635.patch
Untested fix.
>From gcc-bugs-return-627373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 20:54:50 2019
Return-Path: <gcc-bugs-return-627373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81347 invoked by alias); 2 Jan 2019 20:54:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81307 invoked by uid 48); 2 Jan 2019 20:54:46 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88647] Rejects valid program dereferencing pointer with incomplete reference type.
Date: Wed, 02 Jan 2019 20:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88647-4-F19oNRbqKi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00182.txt.bz2
Content-length: 861
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88647
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #3 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
What about this modified test case?
struct S *p;
void f(void);
int main()
{
f();
&*p;
}
struct S { int x; };
void f()
{
static struct S s = { 0 };
p = &s;
}
It gives the same error message (using the same compilation command line), and
there is no lvalue to rvalue conversion of *p in this case, because of the
operator & .
Clang accept that test case without any errors.
>From gcc-bugs-return-627374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:06:02 2019
Return-Path: <gcc-bugs-return-627374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91396 invoked by alias); 2 Jan 2019 21:06: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 91259 invoked by uid 55); 2 Jan 2019 21:05:56 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Wed, 02 Jan 2019 21:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.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-87836-4-1BigoCQXfC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00183.txt.bz2
Content-length: 1339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #22 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #21 from Gary Mills <gary_mills at fastmail dot fm> ---
> Most of the words in the title are wrong now. I'm attempting to build gcc-7
> now. The ICE occurs on both SPARC and x86 systems. It only happens with the
Which version of /bin/as are you using on Solaris/x86?
And before trying to debug this further, could you please try a
bootstrap with the bare minimum of configure options and no local
patches: from what I see in your Comment #11, that would be
CC=/usr/gcc/4.9/bin/gcc these are a 32-bit-default compilers, I assume?
CXX=/usr/gcc/4.9/bin/g++
--enable-languages=c,c++
--without-gnu-ld --with-ld=/usr/bin/ld
--without-gnu-as --with-as=/usr/bin/as
Certainly omit --with-initfini-array: if the configure test doesn't
detect it, there may be a problem (e.g. in ld) here.
Can you bootstrap a previous unmodified version of GCC (e.g. 4.9.x) in a
similar way and use that instead of the bundled one? Maybe there's
already a problem with your bootstrap compiler.
If 4.9.x bootstraps fine and 4.9.x -> 7.x doesn't, try the last releases
from each branch (5.x, 6.x) in turn, starting with 4.9.x -> 5.x; then
5.x -> 6.x; then 6.x -> 7.x.
>From gcc-bugs-return-627375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:08:48 2019
Return-Path: <gcc-bugs-return-627375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95790 invoked by alias); 2 Jan 2019 21:08: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 95720 invoked by uid 48); 2 Jan 2019 21:08:45 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
Date: Wed, 02 Jan 2019 21:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60563-4-UPZ1PJ0Kvg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00184.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60563
--- Comment #16 from Iain Sandoe <iains at gcc dot gnu.org> ---
well.. given the amount of time that's passed - perhaps we'll only get a fix
for ld64 if we do it ourselves...
What about xfail-run-if - to reduce test noise, and then when (if?) ld64 gets
fixed it will "xpass" alerting us to the change?
>From gcc-bugs-return-627376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:17:34 2019
Return-Path: <gcc-bugs-return-627376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96723 invoked by alias); 2 Jan 2019 21:17:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91903 invoked by uid 48); 2 Jan 2019 21:17:30 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Wed, 02 Jan 2019 21:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88663-4-6twLkUlw7l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00185.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jeffrey A. Law <law at redhat dot com> ---
Should be fixed on the trunk now.
>From gcc-bugs-return-627377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:23:13 2019
Return-Path: <gcc-bugs-return-627377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86352 invoked by alias); 2 Jan 2019 21:23: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 86256 invoked by uid 48); 2 Jan 2019 21:23:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87304] [9 regression] gcc.dg/vect/bb-slp-over-widen-1.c fails starting with r262371
Date: Wed, 02 Jan 2019 21:23: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: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87304-4-rKwkFgAh2z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87304-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87304-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00186.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87304
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Applied.
>From gcc-bugs-return-627378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:26:01 2019
Return-Path: <gcc-bugs-return-627378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91594 invoked by alias); 2 Jan 2019 21:26:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91379 invoked by uid 48); 2 Jan 2019 21:25:57 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/448] <stdint.h>-related issues (C99 issues)
Date: Wed, 02 Jan 2019 21:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 2.96
X-Bugzilla-Keywords:
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: cf_gcctarget cc
Message-ID: <bug-448-4-16hSGn2xJa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-448-4@http.gcc.gnu.org/bugzilla/>
References: <bug-448-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00187.txt.bz2
Content-length: 1447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=448
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|i686-pc-linux-gnu |netbsd, VxWorks, SymbianOS,
| |LynxOS, QNX, TPF
CC| |hainque at adacore dot com,
| |kristerw at netbsd dot org,
| |thorpej at gcc dot gnu.org
--- Comment #39 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to joseph@codesourcery.com from comment #38)
> I think the correct state is NEW. There is a well-defined set of target
> OSes that lack the target macro definitions describing those targets'
> stdint.h types, each of which should be straightforward to fix for someone
> with access to the target OS in question to examine its headers and run
> tests.
That's still these ones, right?
(In reply to joseph@codesourcery.com from comment #31)
> The following targets still appear to be missing this type information in
> GCC: some NetBSD targets (netbsd-stdint.h only used for x86 / x86_64),
> VxWorks, SymbianOS, LynxOS, QNX, TPF. Others have either been fixed, or
> obsoleted and removed.
cc-ing maintainers of those ports
>From gcc-bugs-return-627379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:35:59 2019
Return-Path: <gcc-bugs-return-627379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16683 invoked by alias); 2 Jan 2019 21:35: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 16415 invoked by uid 48); 2 Jan 2019 21:35:55 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88665] Arduino: 1.8.8 (Windows Store 1.8.19.0) (Windows 10), Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"
Date: Wed, 02 Jan 2019 21:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status version component cc resolution product
Message-ID: <bug-88665-4-Zj7A0sw3X7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88665-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88665-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00188.txt.bz2
Content-length: 797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88665
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Version|unspecified |5.1.0
Component|classpath |lto
CC| |marxin at gcc dot gnu.org
Resolution|--- |DUPLICATE
Product|classpath |gcc
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 87695. NOTE you filed this bug under classpath which is wrong.
*** This bug has been marked as a duplicate of bug 87695 ***
>From gcc-bugs-return-627381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:36:28 2019
Return-Path: <gcc-bugs-return-627381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18149 invoked by alias); 2 Jan 2019 21:36: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 18093 invoked by uid 48); 2 Jan 2019 21:36:23 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49743] -g enables var_tracking on -O0 - causes long compilations
Date: Wed, 02 Jan 2019 21:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49743-4-kNCn2mKThC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00190.txt.bz2
Content-length: 1245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Gary Funck from comment #3)
> Recently, I've been reviewing changes that we made on the GUPC branch (see
> comment #2) that are candidates for the trunk revision (or in this case,
> possibly the 4.7 branch).
>
> Index: gcc/config/darwin.c
> ===================================================================
> --- gcc/config/darwin.c (.../trunk) (revision 190707)
> +++ gcc/config/darwin.c (.../branches/gupc) (revision 190718)
> @@ -3039,6 +3039,7 @@ darwin_override_options (void)
> }
>
> if (flag_var_tracking
> + && optimize >= 1
> && generating_for_darwin_version >= 9
> && (flag_gtoggle ? (debug_info_level == DINFO_LEVEL_NONE)
> : (debug_info_level >= DINFO_LEVEL_NORMAL))
>
> Reading the problem description, unless the option scanning logic has
> changed for Darwin, it looks as if this change might still be necessary to
> suppress var tracking at -O0?
Any plans to resubmit the GUPC branch again?
>From gcc-bugs-return-627380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:36:00 2019
Return-Path: <gcc-bugs-return-627380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16775 invoked by alias); 2 Jan 2019 21:36:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16469 invoked by uid 48); 2 Jan 2019 21:35:56 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/87695] Arduino: ICE with avr and LTO
Date: Wed, 02 Jan 2019 21:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87695-4-aZRoPEpE6t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00189.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87695
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |WOLFCREEK1 at COX dot NET
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 88665 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:38:09 2019
Return-Path: <gcc-bugs-return-627382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22102 invoked by alias); 2 Jan 2019 21:38:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22050 invoked by uid 48); 2 Jan 2019 21:38:05 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc++/58783] Fast enumeration is not supported for Objective-C++
Date: Wed, 02 Jan 2019 21:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: objc++
X-Bugzilla-Version: 4.8.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58783-4-FmpnXlMmMb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00191.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58783
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #8)
> I recently ran into this with the Cocoa interface for DeSmuME, which also
> tries to use fast enumeration from Objective-C++. So maybe this should be
> re-titled to reflect the fact that it's a more general issue with fast
> enumeration in Objective-C++, and not anything Qt5-specific.
Thanks to FX for doing the retitling
>From gcc-bugs-return-627383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:42:42 2019
Return-Path: <gcc-bugs-return-627383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35207 invoked by alias); 2 Jan 2019 21:42: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 35123 invoked by uid 48); 2 Jan 2019 21:42:38 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88147] [9 Regression] ICE in linemap_line_start, at libcpp/line-map.c:781 starting from r265875
Date: Wed, 02 Jan 2019 21:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88147-4-pHOMgBLaFc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00192.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88147
--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I've been trying to reproduce this, but failing - I tried with today's trunk,
and with a build from 2018-11-16.
Do you have a revision that is known to trigger the ICE?
>From gcc-bugs-return-627384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:43:04 2019
Return-Path: <gcc-bugs-return-627384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36441 invoked by alias); 2 Jan 2019 21:43:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36182 invoked by uid 48); 2 Jan 2019 21:43:00 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug classpath/29304] autoconf should be used in libjava to check for fabs, fabsf and scalbn
Date: Wed, 02 Jan 2019 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: classpath
X-Bugzilla-Component: classpath
X-Bugzilla-Version: 0.15
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-29304-4-6zXBSmo5dM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29304-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29304-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00193.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29304
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew John Hughes from comment #3)
> No, this is a Classpath bug. Nothing to do with GCJ.
Does it make sense for Classpath and GCC to continue to share a bugzilla these
days? This is far from the only time I've been confused by it... would it be
possible to split them into 2 separate bug databases?
>From gcc-bugs-return-627385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:44:17 2019
Return-Path: <gcc-bugs-return-627385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39337 invoked by alias); 2 Jan 2019 21:44:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39259 invoked by uid 48); 2 Jan 2019 21:44:13 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/29838] -fstack-protector shouldn't use TLS in freestanding mode
Date: Wed, 02 Jan 2019 21:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-29838-4-Y7IEpoxA6y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00194.txt.bz2
Content-length: 232
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29838
--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #12)
> See also PR78875.
That's been closed since you commented.
>From gcc-bugs-return-627386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:48:40 2019
Return-Path: <gcc-bugs-return-627386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46254 invoked by alias); 2 Jan 2019 21:48:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45648 invoked by uid 48); 2 Jan 2019 21:48:28 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/80042] gcc thinks sin/cos don't set errno
Date: Wed, 02 Jan 2019 21:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: easyhack
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-80042-4-4HWMBNEW6W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80042-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80042-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00195.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80042
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |easyhack
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> DEF_LIB_BUILTIN (BUILT_IN_SIN, "sin", BT_FN_DOUBLE_DOUBLE,
> ATTR_MATHFN_FPROUNDING)
>
> so it doesn't set errno according to GCC.
So all that needs to be done is to change ATTR_MATHFN_FPROUNDING to
ATTR_MATHFN_FPROUNDING_ERRNO on the relevant lines in builtins.def, right?
>From gcc-bugs-return-627387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:48:59 2019
Return-Path: <gcc-bugs-return-627387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47573 invoked by alias); 2 Jan 2019 21:48:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47328 invoked by uid 48); 2 Jan 2019 21:48:55 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug classpath/29304] autoconf should be used in libjava to check for fabs, fabsf and scalbn
Date: Wed, 02 Jan 2019 21:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: classpath
X-Bugzilla-Component: classpath
X-Bugzilla-Version: 0.15
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-29304-4-Kkin333Wsw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29304-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29304-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00196.txt.bz2
Content-length: 835
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29304
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> (In reply to Andrew John Hughes from comment #3)
> > No, this is a Classpath bug. Nothing to do with GCJ.
>
> Does it make sense for Classpath and GCC to continue to share a bugzilla
> these days? This is far from the only time I've been confused by it... would
> it be possible to split them into 2 separate bug databases?
I am less confused by the sharing because I know the history (I was one of the
folks who prompted the sharing). I don't think it hurts having the classpath
in GCC's bugzilla and I normally monitor classpath's bug list for accidental
usage there (there was one today but it only happens once every two months so
it is low traffic).
>From gcc-bugs-return-627388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:49:19 2019
Return-Path: <gcc-bugs-return-627388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48377 invoked by alias); 2 Jan 2019 21:49:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48331 invoked by uid 48); 2 Jan 2019 21:49:15 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/80023] missing diagnostic on aligned_alloc with invalid alignment
Date: Wed, 02 Jan 2019 21:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80023-4-ZjVzx8qMfz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80023-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80023-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00197.txt.bz2
Content-length: 203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80023
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #2)
> Confirmed per comment #1.
Thanks.
>From gcc-bugs-return-627389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:50:31 2019
Return-Path: <gcc-bugs-return-627389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51806 invoked by alias); 2 Jan 2019 21:50:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51713 invoked by uid 48); 2 Jan 2019 21:50:27 -0000
From: "mathieu.malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88273] [8/9 Regression] warning: 'memcpy' offset [-527, -529] is out of the bounds [0, 16] of object 'vrsave' with type 'union <anonymous>' [-Warray-bounds]
Date: Wed, 02 Jan 2019 21:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mathieu.malaterre at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88273-4-kH9KPZYDtj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00198.txt.bz2
Content-length: 953
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
--- Comment #7 from Mathieu Malaterre <mathieu.malaterre at gmail dot com> ---
Here is the new creduced test case:
$ cat bug.c
#include <string.h>
typedef struct {
int b[4]
} c;
void* d;
unsigned e;
inline int h(void *i, int p2, int j) {
if (j < 0 || e < j) {
int copy = ({
typeof(e) k = j - e;
k;
});
i += e - p2;
memcpy(d, i, copy);
e = copy;
}
}
void a() {
int g = h(&g, 0, sizeof(c));
union {
c f;
} vrsave;
h(&vrsave, 33 * sizeof(c), -1);
}
Compilation:
$ powerpc-linux-gnu-gcc -Warray-bounds -mcpu=powerpc -O2 -c bug.c
Using creduce with:
#!/bin/bash
powerpc-linux-gnu-gcc -Warray-bounds -mcpu=powerpc -O2 -c ptrace2.i >&
output.txt
grep error output.txt && exit 1
grep -F "warning: 'memcpy' offset [-527, -529] is out of the bounds [0, 16] of
object 'vrsave' with type 'union <anonymous>'" output.txt >/dev/null 2>&1
>From gcc-bugs-return-627390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:52:24 2019
Return-Path: <gcc-bugs-return-627390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56295 invoked by alias); 2 Jan 2019 21:52: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 56221 invoked by uid 48); 2 Jan 2019 21:52:20 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88667] New: Accepts program with invalid abstract-declarator grammar.
Date: Wed, 02 Jan 2019 21: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: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88667-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00199.txt.bz2
Content-length: 832
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88667
Bug ID: 88667
Summary: Accepts program with invalid abstract-declarator
grammar.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
void f(int [const *]);
int main() {}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
No error messages outputed.
Expected behaviour:
An error message outputed.
[const *] is an invalid abstract-declarator according to the grammar in
6.7.7/1
(no type qualifiers allowed in [*]).
>From gcc-bugs-return-627391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:54:02 2019
Return-Path: <gcc-bugs-return-627391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57708 invoked by alias); 2 Jan 2019 21:54: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 57519 invoked by uid 48); 2 Jan 2019 21:53:49 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87729] Please include -Woverloaded-virtual in -Wall
Date: Wed, 02 Jan 2019 21:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-87729-4-0QuaubyWiu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00200.txt.bz2
Content-length: 1114
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87729
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-02
Ever confirmed|0 |1
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Daniel Fruzynski from comment #2)
> Here you are:
>
> [code]
> class Foo
> {
> public:
> virtual void f(int);
> };
>
> class Bar : public Foo
> {
> public:
> virtual void f(short);
> };
> [/code]
Thanks, confirmed.
$ /usr/local/bin/g++ -c -Wall 87729.cc
$ clang++ -c -Wall 87729.cc
87729.cc:10:16: warning: 'Bar::f' hides overloaded virtual function
[-Woverloaded-virtual]
virtual void f(short);
^
87729.cc:4:16: note: hidden overloaded virtual function 'Foo::f' declared here:
type mismatch at 1st parameter ('int' vs 'short')
virtual void f(int);
^
1 warning generated.
$
>From gcc-bugs-return-627392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:54:19 2019
Return-Path: <gcc-bugs-return-627392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58547 invoked by alias); 2 Jan 2019 21:54:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58478 invoked by uid 48); 2 Jan 2019 21:54:16 -0000
From: "gary at intrepid dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/49743] -g enables var_tracking on -O0 - causes long compilations
Date: Wed, 02 Jan 2019 21:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary at intrepid 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-49743-4-xVhOJpJY1L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00201.txt.bz2
Content-length: 244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49743
--- Comment #5 from Gary Funck <gary at intrepid dot com> ---
(In reply to Eric Gallager from comment #4)
> Any plans to resubmit the GUPC branch again?
Eric, no not at this time. Thanks.
>From gcc-bugs-return-627393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:54:58 2019
Return-Path: <gcc-bugs-return-627393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59515 invoked by alias); 2 Jan 2019 21:54:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59459 invoked by uid 48); 2 Jan 2019 21:54:53 -0000
From: "mathieu.malaterre at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88273] [8/9 Regression] warning: 'memcpy' offset [-527, -529] is out of the bounds [0, 16] of object 'vrsave' with type 'union <anonymous>' [-Warray-bounds]
Date: Wed, 02 Jan 2019 21:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mathieu.malaterre at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88273-4-O3PT9KAdgA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00202.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
--- Comment #8 from Mathieu Malaterre <mathieu.malaterre at gmail dot com> ---
For reference:
$ cat ptrace2.c
#include <linux/regset.h>
#define CREATE_TRACE_POINTS
#include <trace/events/syscalls.h>
void a(int b, int c, void *d) {
void *e = 0;
int g = user_regset_copyout(&b, &c, d, e, g, 0, sizeof(vector128));
union {
elf_vrreg_t f
} vrsave;
user_regset_copyout(&b, &c, d, e, &vrsave, 33 * sizeof(vector128), -1);
}
>From gcc-bugs-return-627394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:11:49 2019
Return-Path: <gcc-bugs-return-627394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86618 invoked by alias); 2 Jan 2019 22:11: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 86495 invoked by uid 48); 2 Jan 2019 22:11:45 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/44263] missing diagnostic on questionable array sizes with -pedantic
Date: Wed, 02 Jan 2019 22:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-44263-4-gYLbiVpE2z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00203.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44263
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org,
| |nathan at gcc dot gnu.org
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing c++ FE maintainers
>From gcc-bugs-return-627395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:15:03 2019
Return-Path: <gcc-bugs-return-627395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47110 invoked by alias); 2 Jan 2019 22:15: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 44433 invoked by uid 55); 2 Jan 2019 22:14:58 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84478] [8 Regression] pdftex miscompilation on i386
Date: Wed, 02 Jan 2019 22:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84478-4-YIPFw09wUc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00204.txt.bz2
Content-length: 967
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
--- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
> If this is a new regression please open a new bug for it. It's probably a
How would I determine that? The testcase fails on a considerable number
of targets the moment it is introduced.
> fallout from r267503 or one of the other related changes.
And what would be the point anyway: either the testcase doesn't always
test what it claims to or the patch doesn't always fix what it should.
In either case, the author is on the hook to investigate and fix the
issue, both well within the scope of this PR.
Only if it turns out that this is a completely different issue that
needs to be fixed without modifying either the new testcase or the rest
of the patch can a new PR be opened. Everything else only leads to a
needless explosion of PRs.
>From gcc-bugs-return-627396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:16:22 2019
Return-Path: <gcc-bugs-return-627396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86827 invoked by alias); 2 Jan 2019 22:16: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 86781 invoked by uid 55); 2 Jan 2019 22:16:18 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88612] [9 Regression] Internal compiler error: Error reporting routines re-entered.
Date: Wed, 02 Jan 2019 22:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88612-4-UDURyuSTsO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88612-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88612-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00205.txt.bz2
Content-length: 719
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88612
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Jan 2 22:15:46 2019
New Revision: 267532
URL: https://gcc.gnu.org/viewcvs?rev=267532&root=gcc&view=rev
Log:
PR c++/88612 - ICE with -Waddress-of-packed-member.
* call.c (convert_for_arg_passing): Only give warnings with tf_warning.
* typeck.c (convert_for_assignment): Likewise.
* g++.dg/warn/Waddress-of-packed-member1.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/warn/Waddress-of-packed-member1.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/cp/typeck.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:17:45 2019
Return-Path: <gcc-bugs-return-627397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88706 invoked by alias); 2 Jan 2019 22:17: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 88597 invoked by uid 48); 2 Jan 2019 22:17:41 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88612] [9 Regression] Internal compiler error: Error reporting routines re-entered.
Date: Wed, 02 Jan 2019 22:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88612-4-CFLbKTO7rq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88612-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88612-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00206.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88612
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:20:30 2019
Return-Path: <gcc-bugs-return-627398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91139 invoked by alias); 2 Jan 2019 22:20: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 91084 invoked by uid 48); 2 Jan 2019 22:20:26 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Wed, 02 Jan 2019 22:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88343-4-fdudSzUgzP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00207.txt.bz2
Content-length: 901
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #11 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
This change results in miscompilation of glibc for 32-bit soft-float powerpc
(symptoms: many libm tests as run by "make regen-ulps" either segfault, or
produce spurious errors that don't occur with compilers without this change, or
in the case of tests for float fail the "Value outside of 100 +/- 1ulp."
internal sanity check).
Specifically, on GCC 7 branch r267476 works OK but the tip of the branch, which
has no subsequent changes other than this patch and changes to DATESTAMP,
miscompiles glibc. On GCC 8 branch r267386 (the revision before this change)
works and tip of the branch miscompiles glibc (but I haven't bisected there to
confirm it is indeed this change that's responsible). Trunk also miscompiles
glibc (I haven't tried previous revisions there).
>From gcc-bugs-return-627399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:21:20 2019
Return-Path: <gcc-bugs-return-627399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92614 invoked by alias); 2 Jan 2019 22:21:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92582 invoked by uid 55); 2 Jan 2019 22:21:16 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88631] CTAD cannot deduce from () value initialization
Date: Wed, 02 Jan 2019 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88631-4-YTbWgBz207@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00208.txt.bz2
Content-length: 681
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88631
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Jan 2 22:20:45 2019
New Revision: 267533
URL: https://gcc.gnu.org/viewcvs?rev=267533&root=gcc&view=rev
Log:
PR c++/88631 - CTAD failing for value-initialization.
* typeck2.c (build_functional_cast): Try deducing the template
arguments even if there are no arguments to deduce from.
* g++.dg/cpp1z/class-deduction59.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp1z/class-deduction59.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:25:15 2019
Return-Path: <gcc-bugs-return-627400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18107 invoked by alias); 2 Jan 2019 22:25:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9261 invoked by uid 48); 2 Jan 2019 22:25:02 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88631] CTAD cannot deduce from () value initialization
Date: Wed, 02 Jan 2019 22:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88631-4-Z9Hbae2Z08@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88631-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00209.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88631
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:33:11 2019
Return-Path: <gcc-bugs-return-627401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24483 invoked by alias); 2 Jan 2019 22:33:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24399 invoked by uid 55); 2 Jan 2019 22:33:08 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/448] <stdint.h>-related issues (C99 issues)
Date: Wed, 02 Jan 2019 22:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 2.96
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: joseph at codesourcery 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-448-4-C5PlYbw8Os@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-448-4@http.gcc.gnu.org/bugzilla/>
References: <bug-448-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00210.txt.bz2
Content-length: 202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=448
--- Comment #40 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
The definitions have been added for VxWorks at some point.
>From gcc-bugs-return-627402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:36:11 2019
Return-Path: <gcc-bugs-return-627402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28118 invoked by alias); 2 Jan 2019 22:36:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28057 invoked by uid 55); 2 Jan 2019 22:36:07 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88667] Accepts program with invalid abstract-declarator grammar.
Date: Wed, 02 Jan 2019 22:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88667-4-xyihzIvrpM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88667-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88667-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00211.txt.bz2
Content-length: 282
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88667
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
This is a known defect in the syntax in the standard, as discussed on the
WG14 reflector on 22 Sep 2017 (see reflector message 14798).
>From gcc-bugs-return-627403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:39:52 2019
Return-Path: <gcc-bugs-return-627403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33684 invoked by alias); 2 Jan 2019 22:39:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33623 invoked by uid 55); 2 Jan 2019 22:39:48 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81486] Class template argument deduction fails with (), succeeds with {}
Date: Wed, 02 Jan 2019 22:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81486-4-3XKf1duLKq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81486-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81486-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00212.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81486
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Jan 2 22:39:16 2019
New Revision: 267535
URL: https://gcc.gnu.org/viewcvs?rev=267535&root=gcc&view=rev
Log:
PR c++/81486 - CTAD failing with ().
* g++.dg/cpp1z/class-deduction60.C: New test.
* g++.dg/cpp1z/class-deduction61.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp1z/class-deduction60.C
trunk/gcc/testsuite/g++.dg/cpp1z/class-deduction61.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:40:19 2019
Return-Path: <gcc-bugs-return-627404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34807 invoked by alias); 2 Jan 2019 22:40:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34725 invoked by uid 48); 2 Jan 2019 22:40:15 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81486] Class template argument deduction fails with (), succeeds with {}
Date: Wed, 02 Jan 2019 22:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-81486-4-JLunbmziSy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81486-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81486-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00213.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81486
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Done.
>From gcc-bugs-return-627405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:46:36 2019
Return-Path: <gcc-bugs-return-627405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71134 invoked by alias); 2 Jan 2019 22:46:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71033 invoked by uid 48); 2 Jan 2019 22:46:30 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Wed, 02 Jan 2019 22:46: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: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka 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:
Message-ID: <bug-85574-4-XIx74Z0BrL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00214.txt.bz2
Content-length: 369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #25 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I have tracked down the firefox issue to be -fno-lifetime-dse=1 being used in
with -fprofile-use but not with -fprofile-generate. I am down to 36 mismatches
now and those seems real sourcecode changes (will analyze them after another
rebuild)
>From gcc-bugs-return-627406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 22:58:07 2019
Return-Path: <gcc-bugs-return-627406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8176 invoked by alias); 2 Jan 2019 22:58: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 8076 invoked by uid 48); 2 Jan 2019 22:58:01 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88667] Accepts program with invalid abstract-declarator grammar.
Date: Wed, 02 Jan 2019 22: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88667-4-ZkR3RZ7JtZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88667-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88667-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00215.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88667
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Thanks for the explanation.
>From gcc-bugs-return-627407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 23:12:47 2019
Return-Path: <gcc-bugs-return-627407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32621 invoked by alias); 2 Jan 2019 23:12:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32539 invoked by uid 48); 2 Jan 2019 23:12:43 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45424] [F08] Add IS_CONTIGUOUS intrinsic
Date: Wed, 02 Jan 2019 23:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx 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: attachments.isobsolete attachments.created
Message-ID: <bug-45424-4-wf2Cej7upa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00216.txt.bz2
Content-length: 1509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45292|0 |1
is obsolete| |
--- Comment #7 from Harald Anlauf <anlauf at gmx dot de> ---
Created attachment 45322
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45322&action=edit
Extended Update of Tobias' patch to 9-trunk (except for ChangeLog)
I've updated Tobias' patch, adding a runtime library function to handle
assumed rank arrays (not sure if this is the right way). This now works
for the following testcase:
program is_contiguous_2
implicit none
real, allocatable :: b(:,:)
allocate(b(10,10))
if (fail (b, .true.) ) stop 1
if (fail (b(::1,::1), .true.) ) stop 2
if (fail (b(::2,::1), .false.)) stop 3
if (fail (b(::1,::2), .false.)) stop 4
if (fail (b(:10,:10), .true. )) stop 5
if (fail (b(: 9,:10), .false.)) stop 6
contains
pure logical function fail (x, expect)
! type(*), dimension(..), intent(in) :: x ! This should work, too
real, dimension(..), intent(in) :: x
logical, intent(in) :: expect
fail = is_contiguous (x) .neqv. expect
end function fail
end program
I don't know how to handle assumed type; I need help by somebody else
who is interested in pursuing this.
Thanks to whoever will pick this up.
>From gcc-bugs-return-627408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 23:51:04 2019
Return-Path: <gcc-bugs-return-627408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129309 invoked by alias); 2 Jan 2019 23:51:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129106 invoked by uid 48); 2 Jan 2019 23:50:57 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84478] [8 Regression] pdftex miscompilation on i386
Date: Wed, 02 Jan 2019 23:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-84478-4-pe90TlFInx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00217.txt.bz2
Content-length: 1661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
The test started failing only today:
https://gcc.gnu.org/ml/gcc-regression/2019-01/msg00039.html
so the failures are a regression in GCC 9 but not in GCC 8 as the bug summary
indicates. Since GCC 8 is not affected, neither is the patch referenced in
comment #3, and so tracking any new failures in this area under a separate bug
would be appropriate.
r267503 is also part of a bigger patch kit with at least one change after it
(r267531) so it's possible that the regression was only transient. As Jeff
mentions in his post to gcc-patches below, he is aware of a few outstanding
issues on a few 32-bit targets as a result of some of the patches in this
series and is in the process of validating the full kit:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00064.html
I have just built the top of trunk and verified the test passes in both 32-bit
and 64-bit modes (with a 64-bit host GCC) so unless the original bug was also
specific to an ILP32 host compiler the new failures are, making the root cause
also likely different. In any case, if the failures do persist on any targets
let's open a new bug and make both the host and target clear. As the author of
the changes behind both regressions I prefer it that way.
>From gcc-bugs-return-627409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 00:10:36 2019
Return-Path: <gcc-bugs-return-627409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48132 invoked by alias); 3 Jan 2019 00:10:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48033 invoked by uid 48); 3 Jan 2019 00:10:31 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84478] [8 Regression] pdftex miscompilation on i386
Date: Thu, 03 Jan 2019 00:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget cf_gcchost
Message-ID: <bug-84478-4-gDLYSwKncE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00218.txt.bz2
Content-length: 720
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Target| |i386-*-linux
Host| |x86_64-*-linux
--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
With the patch in comment #3 reverted the test case in comment #0 fails with a
64-bit host GCC 8 compiling for an i386 target (i.e., with -m32). The new
failures reported for GCC 9 appear to be specific to ILP32 host compilers.
>From gcc-bugs-return-627410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 00:41:36 2019
Return-Path: <gcc-bugs-return-627410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75647 invoked by alias); 3 Jan 2019 00:41: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 75578 invoked by uid 48); 3 Jan 2019 00:41:31 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] Hangs in libphobos testsuite
Date: Thu, 03 Jan 2019 00:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88654-4-bGfpVVTNxF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00219.txt.bz2
Content-length: 708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Richard Biener from comment #1)
> I think I saw a duplicate somewhere - this is using real-time threads pinned
> to a single CPU but yield()ing in a spinning loop expecting to make progress.
I checked the multilib issue, and couldn't see it.
Had a look on D's bugtracker, and found this related issue:
https://issues.dlang.org/show_bug.cgi?id=18519
Raised a pull request against upstream phobos that fixes the test itself:
https://github.com/dlang/phobos/pull/6824
Though I haven't yet checked running in dejagnu that the desirable behaviour
transfers over well.
>From gcc-bugs-return-627411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 00:42:19 2019
Return-Path: <gcc-bugs-return-627411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76653 invoked by alias); 3 Jan 2019 00:42:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76619 invoked by uid 48); 3 Jan 2019 00:42:14 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88666] GCC 8.2.- gets Internal Compiler Error: seg fault; GCC 8.1.0 works fine
Date: Thu, 03 Jan 2019 00:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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-88666-4-MnQUe3lQJl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00220.txt.bz2
Content-length: 973
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-03
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
This looks similar to bug 88659 but I'm not able to reproduce it on x86_64 with
either the top of the gcc-8-branch or trunk (GCC 9). Either it's been fixed or
it's target-specific. Please mention your Host and Target triplets and either
provide a preprocessing translation unit for the test case or reduce it to one
that doesn't include any headers.
>From gcc-bugs-return-627412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 03:45:58 2019
Return-Path: <gcc-bugs-return-627412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124840 invoked by alias); 3 Jan 2019 03:45:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124765 invoked by uid 55); 3 Jan 2019 03:45:53 -0000
From: "WOLFCREEK1 at COX dot NET" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88665] Arduino: 1.8.8 (Windows Store 1.8.19.0) (Windows 10), Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"
Date: Thu, 03 Jan 2019 03:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: WOLFCREEK1 at COX dot NET
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88665-4-Q1MTZcm977@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88665-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88665-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00221.txt.bz2
Content-length: 1258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88665
--- Comment #2 from ALLEN WYMER <WOLFCREEK1 at COX dot NET> ---
I HAD NO IDEA WHAT I WAS DOING IY JUST SAID REPORT BUG SO I TRIED
Sent from Mail for Windows 10
From: pinskia at gcc dot gnu.org
Sent: Wednesday, January 2, 2019 3:36 PM
To: WOLFCREEK1@COX.NET
Subject: [Bug lto/88665] Arduino: 1.8.8 (Windows Store 1.8.19.0) (Windows10),
Board: "Arduino/Genuino Mega or Mega 2560, ATmega2560 (Mega 2560)"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88665
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Version|unspecified |5.1.0
Component|classpath |lto
CC| |marxin at gcc dot gnu.org
Resolution|--- |DUPLICATE
Product|classpath |gcc
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 87695. NOTE you filed this bug under classpath which is wrong.
*** This bug has been marked as a duplicate of bug 87695 ***
>From gcc-bugs-return-627413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 04:21:23 2019
Return-Path: <gcc-bugs-return-627413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24017 invoked by alias); 3 Jan 2019 04:21: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 23939 invoked by uid 48); 3 Jan 2019 04:21:20 -0000
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/80362] [5 Regression] gcc miscompiles arithmetic with signed char
Date: Thu, 03 Jan 2019 04:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80362-4-vQz5DAUxJq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80362-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00222.txt.bz2
Content-length: 798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80362
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
--- Comment #9 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
I see the same issue of using arg vs op is present in the reciprocal tests
right below the patched ones. AFAICT it is not possible to trigger the problem
in a way that affects the outcome, but... is there any good reason to keep
them different and have people puzzle over the difference? I think it was not
the first time that difference caught my attention and got me distracted trying
to reason it out.
>From gcc-bugs-return-627414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 05:55:12 2019
Return-Path: <gcc-bugs-return-627414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108274 invoked by alias); 3 Jan 2019 05:55: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 108165 invoked by uid 48); 3 Jan 2019 05:55:07 -0000
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84748] wrong code with u128 at aarch64 at -O and and above
Date: Thu, 03 Jan 2019 05:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: aoliva at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: ktkachov at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84748-4-qHgtc8OpLu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00223.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84748
Alexandre Oliva <aoliva at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org
--- Comment #8 from Alexandre Oliva <aoliva at gcc dot gnu.org> ---
Shouldn't the *compare_condjump<mode> insn_and_split be similarly marked with a
CC clobber? (and perhaps an additional clobber for the scratch register while
at that?)
>From gcc-bugs-return-627415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 06:38:24 2019
Return-Path: <gcc-bugs-return-627415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75469 invoked by alias); 3 Jan 2019 06:38: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 75436 invoked by uid 48); 3 Jan 2019 06:38:20 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88668] New: Code generated was different for PowerPC on Windows W.R.T Linux.
Date: Thu, 03 Jan 2019 06:38: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: umesh.kalappa0 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-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00224.txt.bz2
Content-length: 1635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
Bug ID: 88668
Summary: Code generated was different for PowerPC on Windows
W.R.T Linux.
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: umesh.kalappa0 at gmail dot com
Target Milestone: ---
Hi All ,
Lets consider the below code
int foo()
{
printf("Hello World");
}
On linux with configure like :
--target=powerpc-linux-gnu --prefix=/usr/local/wind/tmp/compilers
--with-pkgversion=' GCC 8.1.0.0 - 2018.10.29' --disable-nls
--enable-languages=c,c++ --enable-targets=all --disable-multilib
--enable-threads --enable-tls --enable-__cxa_atexit --enable-secureplt
code generated like
addis 3,2,.LC0@toc@ha
addi 3,3,.LC0@toc@l
where offset signed 32 bit used relatively to toc base on linux as expected
for the medium code model . and the relocation entry will be generated by gas
:
R_PPC64_TOC16_HA and R_PPC64_TOC16_LO
On windows with configure like :
--host i686-w64-mingw32 --target=powerpc-linux-gnu
--prefix=/usr/local/wind/tmp/compilers --with-pkgversion='GCC 8.1.0.0 -
2018.10.25' --disable-nls --enable-languages=c,c++ --enable-targets=all
--disable-multilib --enable-threads --enable-tls --enable-__cxa_atexit
--enable-secureplt
code generated like :
la 3,.LC0@toc(2)
where offset used is signed 16 bit used relatively to toc base and the
relocation entry will be :
R_PPC64_TOC16 (signed 16 bit offset ).
>From gcc-bugs-return-627416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 06:42:17 2019
Return-Path: <gcc-bugs-return-627416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80791 invoked by alias); 3 Jan 2019 06:42:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79932 invoked by uid 48); 3 Jan 2019 06:42:13 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88668] Code generated was different for PowerPC on Windows W.R.T Linux.
Date: Thu, 03 Jan 2019 06: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: umesh.kalappa0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88668-4-pokgmOQ01d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00225.txt.bz2
Content-length: 1230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
--- Comment #1 from Umesh Kalappa <umesh.kalappa0 at gmail dot com> ---
after our investigation we found that the below change ,makes code to be
generated like identical to linux host .
--- a/gcc/configure
+++ b/gcc/configure
@@ -11795,15 +11795,16 @@ else
CXX="${CXX_FOR_BUILD}" CXXFLAGS="${CXXFLAGS_FOR_BUILD}" \
LD="${LD_FOR_BUILD}" LDFLAGS="${LDFLAGS_FOR_BUILD}" \
GMPINC="" CPPFLAGS="${CPPFLAGS} -DGENERATOR_FILE" \
+ gcc_cv_as=../as gcc_cv_ld=../collect-ld enable_targets=$enable_targets\
${realsrcdir}/configure \
--enable-languages=${enable_languages-all} \
--target=$target_alias --host=$build_alias --build=$build_alias
This change would affect the value of macros defined in auto-build.h which is
used when building the toolchain for Windows, the different value of macros
result the different code in generated file insn-conditions.md, insn-recog.c
etc which eventually makes a different compiler is built for Windows.
Before we conclude with our changes ,we would like to hear from the experts
here on the difference behaviour(b/w hosts) and the fix .
>From gcc-bugs-return-627417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 06:56:53 2019
Return-Path: <gcc-bugs-return-627417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105806 invoked by alias); 3 Jan 2019 06:56: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 105745 invoked by uid 48); 3 Jan 2019 06:56:47 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host
Date: Thu, 03 Jan 2019 06:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on component cf_gcchost short_desc everconfirmed cf_gccbuild
Message-ID: <bug-88668-4-RSjG4kn5FW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00226.txt.bz2
Content-length: 1787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
Component|c |bootstrap
Host|windows |!=build
Summary|Code generated was |Code generated was
|different for PowerPC on |different for PowerPC when
|Windows W.R.T Linux. |build!=host compared to
| |build=host
Ever confirmed|0 |1
Build| |!=target
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> On windows with configure like
> --host i686-w64-mingw32
But build is then guessed using config.guess.
Then you have a build!=host case.
Now AS="${AS_FOR_BUILD}" should be passed too and that is missing there.
This is the patch which should fix that (NOTE you will need to regenerate
configure):
diff --git a/gcc/configure.ac b/gcc/configure.ac
index 974a1723843..ac7fe138548 100644
--- a/gcc/configure.ac
+++ b/gcc/configure.ac
@@ -1708,6 +1708,7 @@ else
CC="${CC_FOR_BUILD}" CFLAGS="${CFLAGS_FOR_BUILD}" \
CXX="${CXX_FOR_BUILD}" CXXFLAGS="${CXXFLAGS_FOR_BUILD}" \
LD="${LD_FOR_BUILD}" LDFLAGS="${LDFLAGS_FOR_BUILD}" \
+ AS=${AS_FOR_BUILD}" \
GMPINC="" CPPFLAGS="${CPPFLAGS} -DGENERATOR_FILE" \
${realsrcdir}/configure \
--enable-languages=${enable_languages-all} \
>From gcc-bugs-return-627418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 07:00:34 2019
Return-Path: <gcc-bugs-return-627418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21161 invoked by alias); 3 Jan 2019 07:00: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 20830 invoked by uid 48); 3 Jan 2019 07:00:14 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host
Date: Thu, 03 Jan 2019 07:00: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88668-4-tci935KtzG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00227.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> > On windows with configure like
> > --host i686-w64-mingw32
>
> But build is then guessed using config.guess.
> Then you have a build!=host case.
I should say you have the build!=host case on accident. Really this one case
you should have them being the same.
>From gcc-bugs-return-627419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 07:54:13 2019
Return-Path: <gcc-bugs-return-627419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113857 invoked by alias); 3 Jan 2019 07:54:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113802 invoked by uid 55); 3 Jan 2019 07:54:09 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88436] [9 regression] r265421 causes gcc.target/powerpc/pr54240.c to fail
Date: Thu, 03 Jan 2019 07:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88436-4-BXZbRTWwdS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00228.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88436
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Thu Jan 3 07:53:37 2019
New Revision: 267541
URL: https://gcc.gnu.org/viewcvs?rev=267541&root=gcc&view=rev
Log:
Adjust a dump file in a test-case (PR testsuite/88436).
2019-01-03 Martin Liska <mliska@suse.cz>
PR testsuite/88436
* gcc.target/powerpc/pr54240.c: Scan phiopt2.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/powerpc/pr54240.c
>From gcc-bugs-return-627420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 07:55:19 2019
Return-Path: <gcc-bugs-return-627420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115409 invoked by alias); 3 Jan 2019 07:55: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 115307 invoked by uid 48); 3 Jan 2019 07:55:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88436] [9 regression] r265421 causes gcc.target/powerpc/pr54240.c to fail
Date: Thu, 03 Jan 2019 07: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: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88436-4-aWognCY1sY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00229.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88436
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 07:59:21 2019
Return-Path: <gcc-bugs-return-627421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120044 invoked by alias); 3 Jan 2019 07:59:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119968 invoked by uid 48); 3 Jan 2019 07:59:17 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Thu, 03 Jan 2019 07:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85052-4-Q7nGrRWf0S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00230.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #5 from Matthias Kretz <kretz at kde dot org> ---
Thank you Jakub! Here's a tested x86 library implementation for all conversions
and different ISA extension support for reference:
https://github.com/mattkretz/gcc/blob/mkretz/simd/libstdc%2B%2B-v3/include/experimental/bits/simd_x86_conversions.h
(I have not looked at the patch yet to see whether I understand enough of the
implementation to optimize conversions myself.)
>From gcc-bugs-return-627422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:07:07 2019
Return-Path: <gcc-bugs-return-627422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15935 invoked by alias); 3 Jan 2019 08:07: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 15861 invoked by uid 48); 3 Jan 2019 08:07:01 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 08:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88343-4-3SDOtMm9Ga@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00231.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #12 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Please revert this on 7 and 8 for now, and we'll fix this on trunk? Or revert
it on trunk as well, if it is in the way. Thanks!
>From gcc-bugs-return-627423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:14:39 2019
Return-Path: <gcc-bugs-return-627423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31298 invoked by alias); 3 Jan 2019 08:14:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31243 invoked by uid 48); 3 Jan 2019 08:14:35 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88343-4-atKR2eIzJl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00232.txt.bz2
Content-length: 1252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Joseph S. Myers from comment #11)
> This change results in miscompilation of glibc for 32-bit soft-float powerpc
> (symptoms: many libm tests as run by "make regen-ulps" either segfault, or
> produce spurious errors that don't occur with compilers without this change,
> or in the case of tests for float fail the "Value outside of 100 +/- 1ulp."
> internal sanity check).
>
> Specifically, on GCC 7 branch r267476 works OK but the tip of the branch,
> which has no subsequent changes other than this patch and changes to
> DATESTAMP, miscompiles glibc. On GCC 8 branch r267386 (the revision before
> this change) works and tip of the branch miscompiles glibc (but I haven't
> bisected there to confirm it is indeed this change that's responsible).
> Trunk also miscompiles glibc (I haven't tried previous revisions there).
Unfortunately, there doesn't appear to be anything in the GCC test suite that
catches this (all languages reg-strap was clean, on gcc110). Does it show for
a 32b multilib on a 64b host, or only with a 32b host?
(if you have a specific reproducer that would be most welcome).
>From gcc-bugs-return-627424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:24:55 2019
Return-Path: <gcc-bugs-return-627424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64671 invoked by alias); 3 Jan 2019 08:24:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64540 invoked by uid 48); 3 Jan 2019 08:24:46 -0000
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88669] New: Contiguous attribute wrongly rejected
Date: Thu, 03 Jan 2019 08:24: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mscfd at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00233.txt.bz2
Content-length: 995
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
Bug ID: 88669
Summary: Contiguous attribute wrongly rejected
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: mscfd at gmx dot net
Target Milestone: ---
The code below gives the following error
contiguous_pointer.f90:7:51:
class(t), dimension(:), contiguous, pointer :: x
1
Error: Component ‘x’ at (1) has the CONTIGUOUS attribute but is not an array
pointer
With type(t) instead of class(t) , the error does not occur.
program contiguous_pointer
type t
end type t
type s
class(t), dimension(:), contiguous, pointer :: x
end type s
end program contiguous_pointer
>From gcc-bugs-return-627425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:33:27 2019
Return-Path: <gcc-bugs-return-627425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78081 invoked by alias); 3 Jan 2019 08:33: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 78014 invoked by uid 48); 3 Jan 2019 08:33:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88599] ICE in make_decl_rtl, at varasm.c:1337
Date: Thu, 03 Jan 2019 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: 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-88599-4-PlHKg3ThCR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00234.txt.bz2
Content-length: 883
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88599
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-03
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
I also can't reproduce that with x86_64-linux-gnu cross compiler configured
with:
Configured with: ../configure --enable-languages=c,c++ --disable-multilib
--prefix=/home/marxin/bin/gcc2 --disable-bootstrap --disable-libsanitizer
--target=powerpc-linux-gnu --with-as=/usr/bin/powerpc-suse-linux-as
$ ./xgcc -B. ~/Programming/testcases/pr88599.c -c -msoft-float -mcpu=e300c3
All is fine.
>From gcc-bugs-return-627426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:35:19 2019
Return-Path: <gcc-bugs-return-627426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82160 invoked by alias); 3 Jan 2019 08:35: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 82080 invoked by uid 55); 3 Jan 2019 08:35:14 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 08:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88343-4-62cKF5x601@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00235.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #14 from Iain Sandoe <iains at gcc dot gnu.org> ---
Author: iains
Date: Thu Jan 3 08:34:41 2019
New Revision: 267542
URL: https://gcc.gnu.org/viewcvs?rev=267542&root=gcc&view=rev
Log:
revert fix for pr88343
causes problems with soft-fp in GLIBC, see pr comment 11
2019-01-03 Iain Sandoe <iain@sandoe.co.uk>
revert:
2018-12-30 Iain Sandoe <iain@sandoe.co.uk>
backport from mainline.
2018-12-12 Segher Boessenkool <segher@kernel.crashing.org>
Iain Sandoe <iain@sandoe.co.uk>
PR target/88343
* config/rs6000/rs6000.c (save_reg_p): Do not save the picbase reg
unless it has been used.
(first_reg_to_save): Remove dead code.
Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/config/rs6000/rs6000.c
>From gcc-bugs-return-627427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:36:23 2019
Return-Path: <gcc-bugs-return-627427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83350 invoked by alias); 3 Jan 2019 08:36: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 83299 invoked by uid 48); 3 Jan 2019 08:36:19 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88147] [9 Regression] ICE in linemap_line_start, at libcpp/line-map.c:781 starting from r265875
Date: Thu, 03 Jan 2019 08:36: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88147-4-A21HNz1eFT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00236.txt.bz2
Content-length: 542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88147
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #7)
> I've been trying to reproduce this, but failing - I tried with today's
> trunk, and with a build from 2018-11-16.
>
> Do you have a revision that is known to trigger the ICE?
Started with r265875 and is gone with r266395 where Honza removed sorting of
ODR types during LTO streaming in. Maybe one can't use expand_location before
all stuff is read in LTO stream in?
>From gcc-bugs-return-627428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:40:07 2019
Return-Path: <gcc-bugs-return-627428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88235 invoked by alias); 3 Jan 2019 08:40: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 88128 invoked by uid 48); 3 Jan 2019 08:40:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/80362] [5 Regression] gcc miscompiles arithmetic with signed char
Date: Thu, 03 Jan 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80362-4-GOwWdidVHM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80362-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00237.txt.bz2
Content-length: 617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80362
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Alexandre Oliva from comment #9)
> I see the same issue of using arg vs op is present in the reciprocal tests
> right below the patched ones. AFAICT it is not possible to trigger the
> problem in a way that affects the outcome, but... is there any good reason
> to keep them different and have people puzzle over the difference? I think
> it was not the first time that difference caught my attention and got me
> distracted trying to reason it out.
Feel free to patch it.
>From gcc-bugs-return-627430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:46:15 2019
Return-Path: <gcc-bugs-return-627430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99431 invoked by alias); 3 Jan 2019 08:46:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99356 invoked by uid 55); 3 Jan 2019 08:46:11 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88343-4-p2sBQ4o5a1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00239.txt.bz2
Content-length: 897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> ---
Author: iains
Date: Thu Jan 3 08:45:35 2019
New Revision: 267543
URL: https://gcc.gnu.org/viewcvs?rev=267543&root=gcc&view=rev
Log:
revert fix for pr88343
This causes problems for soft-f on GLIBC, see pr comment 11.
2019-01-03 Iain Sandoe <iain@sandoe.co.uk>
revert:
2018-12-23 Iain Sandoe <iain@sandoe.co.uk>
backport from mainline.
2018-12-12 Segher Boessenkool <segher@kernel.crashing.org>
Iain Sandoe <iain@sandoe.co.uk>
PR target/88343
* config/rs6000/rs6000.c (save_reg_p): Do not save the picbase reg
unless it has been used.
(first_reg_to_save): Remove dead code.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/rs6000/rs6000.c
>From gcc-bugs-return-627431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:46:27 2019
Return-Path: <gcc-bugs-return-627431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100206 invoked by alias); 3 Jan 2019 08:46:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100108 invoked by uid 48); 3 Jan 2019 08:46:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Thu, 03 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-88568-4-xsVm22NhC6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00240.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Target Milestone|--- |8.3
>From gcc-bugs-return-627429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:46:05 2019
Return-Path: <gcc-bugs-return-627429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98679 invoked by alias); 3 Jan 2019 08:46: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 98531 invoked by uid 48); 3 Jan 2019 08:45:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88666] GCC 8.2.- gets Internal Compiler Error: seg fault; GCC 8.1.0 works fine
Date: Thu, 03 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc cf_known_to_work version cf_known_to_fail
Message-ID: <bug-88666-4-NDnwpyOsQi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00238.txt.bz2
Content-length: 792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
CC| |marxin at gcc dot gnu.org
Known to work| |8.1.0, 8.2.1
Version|unknown |8.2.0
Known to fail| |8.2.0
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed with GCC 8.2.0, I can't reproduce it on the branch head so I assume
it was fixed (and there was likely a duplicate report). Martin, can you bisect
the fix?
>From gcc-bugs-return-627432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:47:15 2019
Return-Path: <gcc-bugs-return-627432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102808 invoked by alias); 3 Jan 2019 08:47:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102698 invoked by uid 48); 3 Jan 2019 08:47:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88570] Missing or ineffective vectorization of scatter load
Date: Thu, 03 Jan 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: blocked
Message-ID: <bug-88570-4-brHDYMywAY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88570-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88570-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00241.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88570
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |53947
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's probbaly a dependence issue again.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
>From gcc-bugs-return-627433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 08:49:40 2019
Return-Path: <gcc-bugs-return-627433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107599 invoked by alias); 3 Jan 2019 08:49:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107519 invoked by uid 55); 3 Jan 2019 08:49:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88561] [8/9 Regression] PGO devirtualization miscompilation of firefox
Date: Thu, 03 Jan 2019 08:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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-88561-4-S6WsDofSP0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88561-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88561-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00242.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88561
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Thu Jan 3 08:49:04 2019
New Revision: 267546
URL: https://gcc.gnu.org/viewcvs?rev=267546&root=gcc&view=rev
Log:
Backport r267507
2019-01-03 Martin Liska <mliska@suse.cz>
Backport from mainline
2019-01-02 Jakub Jelinek <jakub@redhat.com>
PR ipa/88561
* g++.dg/tree-prof/devirt.C: Expect _ZThn16 only for lp64 and llp64
targets and expect _ZThn8 for ilp32 targets.
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/testsuite/g++.dg/tree-prof/devirt.C
>From gcc-bugs-return-627434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:10:28 2019
Return-Path: <gcc-bugs-return-627434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63389 invoked by alias); 3 Jan 2019 09:10:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60814 invoked by uid 48); 3 Jan 2019 09:10:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88273] [8/9 Regression] warning: 'memcpy' offset [-527, -529] is out of the bounds [0, 16] of object 'vrsave' with type 'union <anonymous>' [-Warray-bounds]
Date: Thu, 03 Jan 2019 09:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status keywords cf_reconfirmed_on cc cf_gcchost everconfirmed cf_known_to_fail
Message-ID: <bug-88273-4-80YzqMzHKw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00243.txt.bz2
Content-length: 5933
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |powerpc-*-linux-gnu
Status|UNCONFIRMED |NEW
Keywords| |needs-bisection
Last reconfirmed| |2019-01-03
CC| |marxin at gcc dot gnu.org
Host| |x86_64-pc-linux-gnu
Ever confirmed|0 |1
Known to fail| |9.0
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
Slightly cleaned up test-case:
$ cat /home/marxin/Programming/testcases/pr88273-2.c
typedef struct {
int b[4];
} c;
void* d;
unsigned e;
inline int h(void *i, int p2, int j) {
if (j < 0 || e < j) {
int copy = j - e;
i += e - p2;
__builtin_memcpy(d, i, copy);
e = copy;
}
}
void a() {
int g = h(&g, 0, sizeof(c));
c vrsave;
h(&vrsave, 33 * sizeof(c), -1);
}
So the warning is triggered for the cross compiler from here:
$ Breakpoint 5, warning_at (location=location@entry=2147483704,
opt=opt@entry=171, gmsgid=gmsgid@entry=0x15a3448 "%G%qD offset %s is out of the
bounds [0, %wu] of object %qD with type %qT") at ../../gcc/diagnostic.c:1289
1289 {
(gdb) bt
#0 warning_at (location=location@entry=2147483704, opt=opt@entry=171,
gmsgid=gmsgid@entry=0x15a3448 "%G%qD offset %s is out of the bounds [0, %wu] of
object %qD with type %qT") at ../../gcc/diagnostic.c:1289
#1 0x0000000000a39dc3 in (anonymous namespace)::maybe_diag_offset_bounds
(loc=2147483704, call=<gimple_call 0x7ffff6b411c8>, func=<function_decl
0x7ffff6a23500 __builtin_memcpy>, strict=<optimized out>, expr=<optimized out>,
ref=...) at ../../gcc/wide-int.h:831
#2 0x0000000000a3a9d9 in (anonymous namespace)::maybe_diag_offset_bounds
(ref=..., expr=<ssa_name 0x7ffff6b3dbd0>, strict=0, func=<optimized out>,
call=<gimple_call 0x7ffff6b411c8>, loc=2147483704) at
../../gcc/gimple-ssa-warn-restrict.c:1586
#3 check_bounds_or_overlap (call=<gimple_call 0x7ffff6b411c8>, dst=<ssa_name
0x7ffff6b3da68>, src=<ssa_name 0x7ffff6b3dbd0>, dstsize=<optimized out>,
srcsize=<optimized out>, bounds_only=<optimized out>) at
../../gcc/gimple-ssa-warn-restrict.c:1851
#4 0x0000000000a3c718 in (anonymous
namespace)::wrestrict_dom_walker::check_call (this=<optimized out>,
call=<gimple_call 0x7ffff6b411c8>) at ../../gcc/gimple-ssa-warn-restrict.c:1814
#5 (anonymous namespace)::wrestrict_dom_walker::before_dom_children
(this=<optimized out>, bb=<optimized out>) at
../../gcc/gimple-ssa-warn-restrict.c:105
#6 0x00000000013256d8 in dom_walker::walk (this=this@entry=0x7fffffffd720,
bb=<basic_block 0x7ffff6b0ab60 (4)>) at ../../gcc/domwalk.c:373
#7 0x0000000000a31c38 in (anonymous namespace)::pass_wrestrict::execute
(this=<optimized out>, fun=0x7ffff6b360b0) at
../../gcc/gimple-ssa-warn-restrict.c:119
#8 0x0000000000be2885 in execute_one_pass (pass=<opt_pass* 0x1d49510
"wrestrict"(188)>) at ../../gcc/passes.c:2483
#9 0x0000000000be3008 in execute_pass_list_1 (pass=<opt_pass* 0x1d49510
"wrestrict"(188)>) at ../../gcc/passes.c:2569
#10 0x0000000000be301a in execute_pass_list_1 (pass=<opt_pass* 0x1d47020
"*all_optimizations"(-1)>) at ../../gcc/passes.c:2570
#11 0x0000000000be3059 in execute_pass_list (fn=0x7ffff6b360b0, pass=<optimized
out>) at ../../gcc/passes.c:2580
#12 0x00000000008cd5cb in cgraph_node::expand (this=<cgraph_node * const
0x7ffff698f5a0 "a"/3>) at ../../gcc/context.h:48
#13 0x00000000008ce5a4 in expand_all_functions () at
../../gcc/cgraphunit.c:2334
#14 symbol_table::compile (this=0x7ffff6991000) at ../../gcc/cgraphunit.c:2685
#15 0x00000000008d0bed in symbol_table::compile (this=0x7ffff6991000) at
../../gcc/cgraphunit.c:2863
#16 symbol_table::finalize_compilation_unit (this=0x7ffff6991000) at
../../gcc/cgraphunit.c:2863
#17 0x0000000000cb9b4b in compile_file () at ../../gcc/toplev.c:481
#18 0x00000000007522c4 in do_compile () at ../../gcc/toplev.c:2176
#19 toplev::main (this=this@entry=0x7fffffffd93e, argc=<optimized out>,
argc@entry=23, argv=<optimized out>, argv@entry=0x7fffffffda38) at
../../gcc/toplev.c:2311
#20 0x00000000007545db in main (argc=23, argv=0x7fffffffda38) at
../../gcc/main.c:39
For the following gimple IL:
$ (gdb) p debug_gimple_stmt(call)
No symbol "call" in current context.
(gdb) p debug_function(cfun->decl,0)
a ()
{
void * i;
void * i;
int D.2622;
struct c vrsave;
int g;
unsigned int e.0_5;
void * pretmp_10;
unsigned int _12;
unsigned int prephitmp_13;
void * pretmp_14;
void * prephitmp_17;
unsigned int _19;
unsigned int _21;
<bb 2> [local count: 1073741824]:
e.0_5 = e;
pretmp_10 = d;
if (e.0_5 <= 15)
goto <bb 3>; [50.00%]
else
goto <bb 4>; [50.00%]
<bb 3> [local count: 536870913]:
_12 = 16 - e.0_5;
i_15 = &g + e.0_5;
__builtin_memcpy (pretmp_10, i_15, _12);
e = _12;
pretmp_14 = d;
<bb 4> [local count: 1073741824]:
# prephitmp_13 = PHI <_12(3), e.0_5(2)>
# prephitmp_17 = PHI <pretmp_14(3), pretmp_10(2)>
_19 = ~prephitmp_13;
_21 = prephitmp_13 + 4294966768;
i_22 = &vrsave + _21;
__builtin_memcpy (prephitmp_17, i_22, _19);
e = _19;
g ={v} {CLOBBER};
vrsave ={v} {CLOBBER};
return;
}
I can confirm the warning is false, because the problematic __builtin_memcpy
for which we trigger the warning:
__builtin_memcpy (prephitmp_17, i_22, _19);
and complains about i_22, but this one should be fine (with a reasonable
initial value of global variable 'e').
Martin: can you please take a look?
>From gcc-bugs-return-627435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:22:52 2019
Return-Path: <gcc-bugs-return-627435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89521 invoked by alias); 3 Jan 2019 09: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 89448 invoked by uid 48); 3 Jan 2019 09:22:48 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7/8/9 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Thu, 03 Jan 2019 09:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88644-4-gz21mwubxJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00244.txt.bz2
Content-length: 276
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #4)
> will do a complete test suite run now, to catch any other changed lengths.
I don't see any other related changes.
>From gcc-bugs-return-627436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:24:34 2019
Return-Path: <gcc-bugs-return-627436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91116 invoked by alias); 3 Jan 2019 09:24: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 90865 invoked by uid 48); 3 Jan 2019 09:24:14 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88666] GCC 8.2.- gets Internal Compiler Error: seg fault; GCC 8.1.0 works fine
Date: Thu, 03 Jan 2019 09:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: 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-88666-4-bxbWnrcZz6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00245.txt.bz2
Content-length: 357
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> Confirmed with GCC 8.2.0, I can't reproduce it on the branch head so I
> assume it was fixed (and there was likely a duplicate report). Martin, can
> you bisect the fix?
Doing that.
>From gcc-bugs-return-627438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:42:21 2019
Return-Path: <gcc-bugs-return-627438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12990 invoked by alias); 3 Jan 2019 09:42: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 12820 invoked by uid 48); 3 Jan 2019 09:42:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87099] [8 Regression] internal compiler error: segmentation fault
Date: Thu, 03 Jan 2019 09:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87099-4-GsARbllsN2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87099-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87099-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00247.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87099
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |geir at cray dot com
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
*** Bug 88666 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:42:21 2019
Return-Path: <gcc-bugs-return-627437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12893 invoked by alias); 3 Jan 2019 09:42: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 12797 invoked by uid 48); 3 Jan 2019 09:42:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88666] GCC 8.2.- gets Internal Compiler Error: seg fault; GCC 8.1.0 works fine
Date: Thu, 03 Jan 2019 09:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: 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-88666-4-17TtywsuLS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00246.txt.bz2
Content-length: 497
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88666
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Dup.
*** This bug has been marked as a duplicate of bug 87099 ***
>From gcc-bugs-return-627439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:51:56 2019
Return-Path: <gcc-bugs-return-627439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36502 invoked by alias); 3 Jan 2019 09:51:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36380 invoked by uid 48); 3 Jan 2019 09:51:51 -0000
From: "rainer@emrich-ebersheim.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88331] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Thu, 03 Jan 2019 09:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rainer@emrich-ebersheim.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88331-4-nQoenXAqRG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00248.txt.bz2
Content-length: 3838
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
Rainer Emrich <rainer@emrich-ebersheim.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rainer@emrich-ebersheim.de
--- Comment #6 from Rainer Emrich <rainer@emrich-ebersheim.de> ---
The issue is now shown during bootstrap while building libfortran.
libtool: compile:
/opt/devel/SCRATCH/tmp.Q1UXSYzwJg/gcc-9.0.0/gcc-9.0.0/./gcc/xgcc
-B/opt/devel/SCRATCH/tmp.Q1UXSYzwJg/gcc-9.0.0/gcc-9.0.0/./gcc/
-L/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/x86_64-w64-mingw32/lib
-L/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/mingw/lib
-isystem
/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/x86_64-w64-mingw32/include
-isystem
/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/mingw/include
-B/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/x86_64-w64-mingw32/bin/
-B/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/x86_64-w64-mingw32/lib/
-isystem
/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/x86_64-w64-mingw32/include
-isystem
/opt/devel/gnu/gcc/MINGW_NT/x86_64-w64-mingw32/mingw-w64-runtime-trunk-svn/gcc-9.0.0/x86_64-w64-mingw32/sys-include
-fchecking=1 -DHAVE_CONFIG_H -I.
-I../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran
-iquote../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/io
-I../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/../gcc
-I../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/../gcc/config
-I../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/../libquadmath
-I../.././gcc
-I../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/../libgcc
-I../libgcc
-I../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/../libbacktrace
-I../libbacktrace -I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes
-Wmissing-prototypes -Wold-style-definition -Wextra -Wwrite-strings
-Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules
-ffunction-sections -fdata-sections -ffast-math -ftree-vectorize -funroll-loops
--param max-unroll-times=4 -g -O2 -MT matmul_i4.lo -MD -MP -MF
.deps/matmul_i4.Tpo -c
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/matmul_i4.c
-DDLL_EXPORT -DPIC -o .libs/matmul_i4.o
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/matmul_i4.c:
In function 'matmul_i4_avx2':
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/matmul_i4.c:1210:1:
error: insn outside basic block
1210 | }
| ^
(insn 10248 8120 10249 (parallel [
(set (reg:DI 5750)
(plus:DI (reg/f:DI 19 frame)
(const_int -1200 [0xfffffffffffffb50])))
(clobber (reg:CC 17 flags))
]) 191 {*adddi_1}
(nil))
during RTL pass: reload
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/matmul_i4.c:1210:1:
internal compiler error: in rtl_verify_bb_layout, at cfgrtl.c:2987
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[3]: *** [Makefile:4194: matmul_i4.lo] Error 1
make[3]: Leaving directory
'/opt/devel/SCRATCH/tmp.Q1UXSYzwJg/gcc-9.0.0/gcc-9.0.0/x86_64-w64-mingw32/libgfortran'
>From gcc-bugs-return-627440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:53:17 2019
Return-Path: <gcc-bugs-return-627440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39195 invoked by alias); 3 Jan 2019 09:53:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39153 invoked by uid 48); 3 Jan 2019 09:53:13 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88592] Passing of packed structures on sparc64 different than in clang
Date: Thu, 03 Jan 2019 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88592-4-8N3eFe6p9f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00249.txt.bz2
Content-length: 753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88592
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
CC| |ebotcazou at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Here's the historical comment in the GCC codebase:
/* The ABI obviously doesn't specify how packed structures are passed.
These are passed in integer regs if possible, otherwise memory. */
>From gcc-bugs-return-627441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:53:59 2019
Return-Path: <gcc-bugs-return-627441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40092 invoked by alias); 3 Jan 2019 09:53: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 40052 invoked by uid 48); 3 Jan 2019 09:53:55 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88592] Passing of packed structures on sparc64 different than in clang
Date: Thu, 03 Jan 2019 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: SUSPENDED
X-Bugzilla-Resolution:
X-Bugzilla-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-88592-4-Pw3RP8va5c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00250.txt.bz2
Content-length: 390
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88592
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |SUSPENDED
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
No action required.
>From gcc-bugs-return-627442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:54:12 2019
Return-Path: <gcc-bugs-return-627442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40833 invoked by alias); 3 Jan 2019 09:54: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 40764 invoked by uid 48); 3 Jan 2019 09:54:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88563] [7/8/9 Regression] wrong code with -O2 -fno-code-hoisting -fno-tree-ccp -fno-tree-dominator-opts -fno-tree-forwprop -fno-tree-fre -fno-tree-pre -fno-tree-vrp
Date: Thu, 03 Jan 2019 09:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88563-4-GNr8dV2GsI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00251.txt.bz2
Content-length: 464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88563
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
Jakub: Is it fixed on trunk? Can you please adjust title and known-to-fail?
>From gcc-bugs-return-627443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 09:57:21 2019
Return-Path: <gcc-bugs-return-627443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43311 invoked by alias); 3 Jan 2019 09:57:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43216 invoked by uid 48); 3 Jan 2019 09:57:16 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/87554] [8/9 Regression] internal compiler error: in record_reference, at cgraphbuild.c:64
Date: Thu, 03 Jan 2019 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-87554-4-6avJoAUMiZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00252.txt.bz2
Content-length: 3606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87554
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
With first bad revision the constructor looks as follows:
$ (gdb) p print_generic_expr(stderr, decl->decl_common.initial, 0)
instance = b<k>::create ()$1 = void
(gdb) p debug_tree(decl->decl_common.initial)
<init_expr 0x7ffff6cc0a50
type <reference_type 0x7ffff6cbe540
type <record_type 0x7ffff6cb5f18 k type_5 type_6 SI
size <integer_cst 0x7ffff6b730c0 constant 32>
unit-size <integer_cst 0x7ffff6b730d8 constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff6cb5f18 fields <function_decl 0x7ffff6cc8700 __ct > context
<translation_unit_decl 0x7ffff6b60168
/home/marxin/Programming/testcases/pr87554.ii>
full-name "struct k"
X() X(constX&) this=(X&) n_parents=0 use_template=0
interface-unknown
pointer_to_this <pointer_type 0x7ffff6cbe9d8> reference_to_this
<reference_type 0x7ffff6cbe540> chain <type_decl 0x7ffff6c7bda8 k>>
unsigned DI
size <integer_cst 0x7ffff6b53e70 constant 64>
unit-size <integer_cst 0x7ffff6b53e88 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff6cbe540>
side-effects
arg:0 <var_decl 0x7ffff6cbd2d0 instance type <reference_type
0x7ffff6cbe540>
readonly used public static tree_1 tree_3 unsigned external nonlocal
read decl_3 decl_5 DI /home/marxin/Programming/testcases/pr87554.ii:11:25 size
<integer_cst 0x7ffff6b53e70 64> unit-size <integer_cst 0x7ffff6b53e88 8>
align:64 warn_if_not_align:0 context <record_type 0x7ffff6cbe348 b>
initial <init_expr 0x7ffff6cc0a50>
template-info 0x7ffff6ca6f20
chain <type_decl 0x7ffff6cbf1c8 b type <record_type 0x7ffff6cbe3f0 b>
external nonlocal suppress-debug decl_4 VOID
/home/marxin/Programming/testcases/pr87554.ii:1:30
align:8 warn_if_not_align:0 context <record_type 0x7ffff6cbe348 b>
result <record_type 0x7ffff6cbe348 b>
>>
arg:1 <call_expr 0x7ffff6cca090 type <reference_type 0x7ffff6cbe540>
side-effects
fn <addr_expr 0x7ffff6cc2e40 type <pointer_type 0x7ffff6cc47e0>
constant arg:0 <function_decl 0x7ffff6cc1000 create>>
/home/marxin/Programming/testcases/pr87554.ii:11:50 start:
/home/marxin/Programming/testcases/pr87554.ii:11:44 finish:
/home/marxin/Programming/testcases/pr87554.ii:11:51>>
before that C++ FE reported following error:
$ ./xgcc -B. ~/Programming/testcases/pr87554.ii -c -O2
/home/marxin/Programming/testcases/pr87554.ii: In instantiation of ‘k&
b<k>::instance’:
/home/marxin/Programming/testcases/pr87554.ii:3:26: required from ‘static a&
b<a>::create() [with a = k]’
/home/marxin/Programming/testcases/pr87554.ii:8:24: required from ‘static a
b<a>::d() [with a = k]’
/home/marxin/Programming/testcases/pr87554.ii:26:55: required from ‘void p(m,
a) [with m = e*; a = int]’
/home/marxin/Programming/testcases/pr87554.ii:16:39: required from ‘void
f::h(a) [with a = int]’
/home/marxin/Programming/testcases/pr87554.ii:15:31: required from here
/home/marxin/Programming/testcases/pr87554.ii:11:50: error: call to
non-‘constexpr’ function ‘static a& b<a>::create() [with a = k]’
template < class a > a &b< a >::instance = create();
~~~~~~^~
Jason can you please take a look?
>From gcc-bugs-return-627444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:00:15 2019
Return-Path: <gcc-bugs-return-627444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46506 invoked by alias); 3 Jan 2019 10:00: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 46101 invoked by uid 48); 3 Jan 2019 09:59:59 -0000
From: "rainer@emrich-ebersheim.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88331] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Thu, 03 Jan 2019 10:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rainer@emrich-ebersheim.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88331-4-y5P1ZMVqdA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00253.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #7 from Rainer Emrich <rainer@emrich-ebersheim.de> ---
If I call make within the libgfortran directory I get a slightly different
error message:
during RTL pass: postreload
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/matmul_i4.c:
In function 'matmul_i4_avx2':
../../../../../../../../opt/devel/gnu/src/gcc-mingw-w64/gcc-9.0.0/libgfortran/generated/matmul_i4.c:1210:1:
internal compiler error: in reload_combine_note_use, at postreload.c:1547
1210 | }
| ^
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
>From gcc-bugs-return-627445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:03:43 2019
Return-Path: <gcc-bugs-return-627445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49301 invoked by alias); 3 Jan 2019 10: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 49262 invoked by uid 48); 3 Jan 2019 10:03:39 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/88610] ICE with new ACATS test c452003
Date: Thu, 03 Jan 2019 10:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88610-4-7Ls2UBZ8bB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88610-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88610-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00254.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88610
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
CC| |ebotcazou at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
There is probably little value in filling PRs against new ACATS tests though.
>From gcc-bugs-return-627446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:09:01 2019
Return-Path: <gcc-bugs-return-627446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55916 invoked by alias); 3 Jan 2019 10:09:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55864 invoked by uid 48); 3 Jan 2019 10:08:57 -0000
From: "rainer@emrich-ebersheim.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88331] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Thu, 03 Jan 2019 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rainer@emrich-ebersheim.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88331-4-LMyD5dJzmx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00255.txt.bz2
Content-length: 278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #8 from Rainer Emrich <rainer@emrich-ebersheim.de> ---
Created attachment 45323
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45323&action=edit
preprocessed source
I attached the preprocessed source.
>From gcc-bugs-return-627447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:12:15 2019
Return-Path: <gcc-bugs-return-627447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60425 invoked by alias); 3 Jan 2019 10:12:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60369 invoked by uid 55); 3 Jan 2019 10:12:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88636] [9 Regression] ICE: Segmentation fault (in c_tree_chain_next)
Date: Thu, 03 Jan 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88636-4-ok5cMiBa3K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00256.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88636
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 3 10:11:40 2019
New Revision: 267548
URL: https://gcc.gnu.org/viewcvs?rev=267548&root=gcc&view=rev
Log:
PR c++/88636
* decl.c (builtin_function_1): Return result of pushdecl_top_level
or pushdecl rather than decl.
* g++.target/i386/pr88636.C: New test.
Added:
trunk/gcc/testsuite/g++.target/i386/pr88636.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:16:55 2019
Return-Path: <gcc-bugs-return-627448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77304 invoked by alias); 3 Jan 2019 10:16: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 77112 invoked by uid 48); 3 Jan 2019 10:16:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83651] [7/8/9 regression] 20% slowdown of linux kernel AES cipher
Date: Thu, 03 Jan 2019 10:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83651-4-3Kqvj1NLEm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00257.txt.bz2
Content-length: 3542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
--- Comment #18 from Martin Liška <marxin at gcc dot gnu.org> ---
This is what I see on my model name : Intel(R) Core(TM) i7-4770 CPU @
3.40GHz:
gcc-bisect.py bisect 'gcc -O2 aes_generic.c && /usr/bin/time -f '%E' ./a.out'
-o
Releases
4.8.0 (e9c762ec4671d77e)(22 Mar 2013 10:05): [took: 6.368s] result: OK
0:03.28
4.8.1 (caa62b4636bfed71)(31 May 2013 09:02): [took: 5.318s] result: OK
0:03.40
4.8.2 (9bcca88e24e64d4e)(16 Oct 2013 07:20): [took: 5.344s] result: OK
0:03.43
4.8.3 (6bbf0dec66c0e719)(22 May 2014 09:10): [took: 5.352s] result: OK
0:03.40
4.8.4 (1a97fa0bb3fa5669)(19 Dec 2014 11:43): [took: 5.283s] result: OK
0:03.39
4.8.5 (cf82a597b0d18985)(23 Jun 2015 07:54): [took: 5.431s] result: OK
0:03.45
4.9.0 (a7aa383874520cd5)(22 Apr 2014 09:43): [took: 5.469s] result: OK
0:03.39
4.9.1 (c6fa1b4126635939)(16 Jul 2014 10:04): [took: 5.500s] result: OK
0:03.39
4.9.2 (c1283af40b65f1ad)(30 Oct 2014 08:27): [took: 5.536s] result: OK
0:03.45
4.9.3 (876d41ed80ce13e0)(26 Jun 2015 17:57): [took: 5.499s] result: OK
0:03.39
4.9.4 (d3191480f376c780)(03 Aug 2016 05:07): [took: 5.444s] result: OK
0:03.38
5.1.0 (d5ad84b309d0d97d)(22 Apr 2015 08:43): [took: 5.770s] result: OK
0:03.37
5.2.0 (7b26e3896e268cd4)(16 Jul 2015 09:13): [took: 5.798s] result: OK
0:03.38
5.3.0 (2bc376d60753a58b)(04 Dec 2015 10:45): [took: 5.789s] result: OK
0:03.37
5.4.0 (9d0507742960aa9f)(03 Jun 2016 08:41): [took: 5.795s] result: OK
0:03.38
5.5.0 (ba9cddfdab8b539b)(10 Oct 2017 08:11): [took: 5.824s] result: OK
0:03.39
6.1.0 (c441d9e8e0438dcf)(27 Apr 2016 08:20): [took: 5.673s] result: OK
0:03.18
6.2.0 (6ac74a62ba725829)(22 Aug 2016 08:01): [took: 5.660s] result: OK
0:03.18
6.3.0 (4b5e15daff8b5444)(21 Dec 2016 07:51): [took: 5.665s] result: OK
0:03.18
6.4.0 (45dd06cef49fe00a)(04 Jul 2017 07:22): [took: 5.832s] result: OK
0:03.18
6.5.0 (e4c9bd2bb2324c32)(26 Oct 2018 09:54): [took: 5.724s] result: OK
0:03.18
7.1.0 (f9105a38249fb57f)(02 May 2017 12:42): [took: 6.186s] result: OK
0:03.34
7.2.0 (1bd23ca8c30f4827)(14 Aug 2017 07:59): [took: 6.149s] result: OK
0:03.33
7.3.0 (87fb575328cc5d95)(25 Jan 2018 08:17): [took: 6.350s] result: OK
0:03.53
8.1.0 (af8bbdf198a7cd61)(02 May 2018 08:13): [took: 6.293s] result: OK
0:03.26
8.2.0 (9fb89fa845c1b2e0)(26 Jul 2018 09:47): [took: 6.165s] result: OK
0:03.26
known-to-work: 4.8.5, 4.9.4, 5.5.0, 6.5.0, 7.3.0, 8.2.0
known-to-fail:
Active branches
6 (f2b648ddec0a9552)(07 Nov 2018 20:52): [took: 5.662s] result: OK
0:03.19
7 (2d21868dbe6a8be0)(02 Jan 2019 00:16): [took: 6.220s] result: OK
0:03.50
8 (687f6e70d3fd0eac)(02 Jan 2019 00:16): [took: 6.226s] result: OK
0:03.26
Active branch bases
4.8-base (daf81a9011692e3e)(16 Mar 2013 02:48): [took: 5.279s] result: OK
0:03.42
4.9-base (ec86f0be138e2f97)(11 Apr 2014 12:47): [took: 5.383s] result: OK
0:03.38
5-base (905be4e64f0f9136)(12 Apr 2015 19:30): [took: 5.669s] result: OK
0:03.37
6-base (a050099a416f013b)(15 Apr 2016 14:51): [took: 5.671s] result: OK
0:03.19
7-base (7369309777f6d6e6)(20 Apr 2017 09:44): [took: 6.165s] result: OK
0:03.33
8-base (941fafa56b52ee23)(25 Apr 2018 07:10): [took: 6.299s] result: OK
0:03.26
Bisecting latest revisions
553d41a8a57496a6(02 Jan 2019 16:30): [took: 6.285s] result: OK
0:03.24
acafca510c97652f(09 Oct 2014 07:40): [took: 5.520s] result: OK
0:03.38
As mentioned in the previous comment, Richi: can we adjust title and
known-to-work as
you're installed patch a year ago?
>From gcc-bugs-return-627449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:25:20 2019
Return-Path: <gcc-bugs-return-627449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12882 invoked by alias); 3 Jan 2019 10:25: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 12810 invoked by uid 48); 3 Jan 2019 10:25:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88636] [9 Regression] ICE: Segmentation fault (in c_tree_chain_next)
Date: Thu, 03 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88636-4-lFuQUlKnN2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00258.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88636
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:38:43 2019
Return-Path: <gcc-bugs-return-627450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13517 invoked by alias); 3 Jan 2019 10:38: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 13448 invoked by uid 48); 3 Jan 2019 10:38:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88273] [8/9 Regression] warning: 'memcpy' offset [-527, -529] is out of the bounds [0, 16] of object 'vrsave' with type 'union <anonymous>' [-Warray-bounds]
Date: Thu, 03 Jan 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_known_to_fail
Message-ID: <bug-88273-4-L61R5Z4tmp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88273-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00259.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88273
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
Known to fail| |8.2.0
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r255755.
>From gcc-bugs-return-627451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:48:38 2019
Return-Path: <gcc-bugs-return-627451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52444 invoked by alias); 3 Jan 2019 10:48: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 51844 invoked by uid 48); 3 Jan 2019 10:48:33 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/87880] [9 regression] All macOS asan execution tests FAIL
Date: Thu, 03 Jan 2019 10:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87880-4-BzQ51bFYRY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00260.txt.bz2
Content-length: 2129
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87880
--- Comment #9 from Iain Sandoe <iains at gcc dot gnu.org> ---
So.. this is somewhat puzzling.
Essentially, it seems that on macOS and Linux (at least) currently
ASAN_INTERCEPT___CXA_RETHROW_PRIMARY_EXCEPTION is set unconditionally to "on"
(for any target that has ASAN_HAS_EXCEPTIONS).
libsupc++'s implementation doesn't include this, so ..
.. the mystery is not so much why it's failing sometimes on macOS - so much as
why it's not failing always, when the c++ library is libstdc++ (and also on
Linux).
Hypothesis, could be that since the search is being carried out in the flat
namespace, any library that happens to pull in libc++ (as a dependent) will
cause the libc++abi version of __cxa_rethrow_primary_exception to become
visible in that flat namespace.
using the following hack the results go from wholesale fail on C to a handfull
of fails and on c++ similarly.
I guess this could be a dyld bug too - if the lookup is supposed to be a weak
reference (not checked).
.. obviously, this is incomplete .. it just jams the hook off (not looked at
the configuration stuff yet, or whether there's a weak symbol problem).
[this appears distinct from failure mode on Darwin10 and also distinct from
some fails caused by missing symbolization (atos) on m64 / darwin14]
diff --git a/libsanitizer/asan/asan_interceptors.h
b/libsanitizer/asan/asan_interceptors.h
index b599ebb..10b6d2c 100644
--- a/libsanitizer/asan/asan_interceptors.h
+++ b/libsanitizer/asan/asan_interceptors.h
@@ -79,7 +79,11 @@ void InitializePlatformInterceptors();
#if ASAN_HAS_EXCEPTIONS && !SANITIZER_WINDOWS && !SANITIZER_SOLARIS && \
!SANITIZER_NETBSD
# define ASAN_INTERCEPT___CXA_THROW 1
-# define ASAN_INTERCEPT___CXA_RETHROW_PRIMARY_EXCEPTION 1
+# if ASAN_HAS_CXA_RETHROW_PRIMARY_EXCEPTION
+# define ASAN_INTERCEPT___CXA_RETHROW_PRIMARY_EXCEPTION 1
+#else
+# define ASAN_INTERCEPT___CXA_RETHROW_PRIMARY_EXCEPTION 0
+# endif
# if defined(_GLIBCXX_SJLJ_EXCEPTIONS) || (SANITIZER_IOS && defined(__arm__))
# define ASAN_INTERCEPT__UNWIND_SJLJ_RAISEEXCEPTION 1
# else
>From gcc-bugs-return-627452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 10:50:01 2019
Return-Path: <gcc-bugs-return-627452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55249 invoked by alias); 3 Jan 2019 10:50: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 55185 invoked by uid 48); 3 Jan 2019 10:49:58 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48543] Collapse identical strings
Date: Thu, 03 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-48543-4-ncaIlikvpT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00261.txt.bz2
Content-length: 571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tnfchris at gcc dot gnu.org
--- Comment #5 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hi,
The testcase seems to fail on
aarch64-none-linux-gnu and arm-none-linux-gnueabihf.
with
gfortran.dg/const_chararacter_merge.f90 -O : Supercalifragilis found 2 times
>From gcc-bugs-return-627453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:06:07 2019
Return-Path: <gcc-bugs-return-627453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88742 invoked by alias); 3 Jan 2019 11:06: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 88671 invoked by uid 55); 3 Jan 2019 11:06:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7/8/9 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Thu, 03 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88644-4-y3TJeMnJMd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00262.txt.bz2
Content-length: 1040
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 3 11:05:24 2019
New Revision: 267550
URL: https://gcc.gnu.org/viewcvs?rev=267550&root=gcc&view=rev
Log:
PR debug/88644
* dwarf2out.c (modified_type_die): If type is equal to sizetype,
change it to qualified_type.
* gcc.dg/debug/dwarf2/pr88644.c: New test.
* gcc.dg/debug/dwarf2/pr80263.c: Remove darwin hack.
2019-01-03 Iain Sandoe <iain@sandoe.co.uk>
* gcc.dg/pubtypes-2.c: Adjust expected pubtypes length.
* gcc.dg/pubtypes-3.c: Likewise.
* gcc.dg/pubtypes-4.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/debug/dwarf2/pr88644.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/dwarf2out.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/debug/dwarf2/pr80263.c
trunk/gcc/testsuite/gcc.dg/pubtypes-2.c
trunk/gcc/testsuite/gcc.dg/pubtypes-3.c
trunk/gcc/testsuite/gcc.dg/pubtypes-4.c
>From gcc-bugs-return-627454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:20:53 2019
Return-Path: <gcc-bugs-return-627454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116123 invoked by alias); 3 Jan 2019 11:20:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116099 invoked by uid 48); 3 Jan 2019 11:20:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88669] Contiguous attribute wrongly rejected
Date: Thu, 03 Jan 2019 11:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88669-4-TPTGb0RZ71@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00263.txt.bz2
Content-length: 530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from at least 4.8 up to trunk (9.0).
>From gcc-bugs-return-627455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:29:04 2019
Return-Path: <gcc-bugs-return-627455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2399 invoked by alias); 3 Jan 2019 11:29:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2265 invoked by uid 55); 3 Jan 2019 11:28:58 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88535] sparcv9 gcc 7 causes comparison failure in sparc gcc 8 dwarf2out.o
Date: Thu, 03 Jan 2019 11: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro 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-88535-4-wdyZgHiH8l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88535-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88535-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00264.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88535
--- Comment #16 from Rainer Orth <ro at gcc dot gnu.org> ---
Author: ro
Date: Thu Jan 3 11:28:27 2019
New Revision: 267551
URL: https://gcc.gnu.org/viewcvs?rev=267551&root=gcc&view=rev
Log:
Update config.guess, config.sub (PR target/88535)
PR target/88535
* config.guess: Import upstream version 2019-01-03.
* config.sub: Import upstream version 2019-01-01.
Modified:
trunk/ChangeLog
trunk/config.guess (contents, props changed)
trunk/config.sub (contents, props changed)
>From gcc-bugs-return-627456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:30:27 2019
Return-Path: <gcc-bugs-return-627456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6983 invoked by alias); 3 Jan 2019 11:30:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5484 invoked by uid 48); 3 Jan 2019 11:30:00 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48543] Collapse identical strings
Date: Thu, 03 Jan 2019 11:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-48543-4-53gkNjA1vq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00265.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
See https://gcc.gnu.org/ml/fortran/2019-01/msg00010.html.
>From gcc-bugs-return-627457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:32:02 2019
Return-Path: <gcc-bugs-return-627457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9602 invoked by alias); 3 Jan 2019 11:32: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 9510 invoked by uid 48); 3 Jan 2019 11:31:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83651] [7/8/9 regression] 20% slowdown of linux kernel AES cipher
Date: Thu, 03 Jan 2019 11:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83651-4-gTpfEMNXs7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00266.txt.bz2
Content-length: 315
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
Not sure what you are talking about - your numbers confirm the regression is
still present? Or do you mean that GCC 7.1.0 is also bad and only 6.x was OK
(which didn't have code hoisting?)
>From gcc-bugs-return-627458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:34:28 2019
Return-Path: <gcc-bugs-return-627458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11761 invoked by alias); 3 Jan 2019 11:34: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 11721 invoked by uid 48); 3 Jan 2019 11:34:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88670] New: [meta-bug] generic vector extension issues
Date: Thu, 03 Jan 2019 11:34: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: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00267.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug ID: 88670
Summary: [meta-bug] generic vector extension issues
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
>From gcc-bugs-return-627460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:35:50 2019
Return-Path: <gcc-bugs-return-627460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13792 invoked by alias); 3 Jan 2019 11:35:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13727 invoked by uid 48); 3 Jan 2019 11:35:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/83651] [7/8/9 regression] 20% slowdown of linux kernel AES cipher
Date: Thu, 03 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83651-4-E4fQ3dZb9F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00269.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83651
--- Comment #20 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #19)
> Not sure what you are talking about - your numbers confirm the regression is
> still present? Or do you mean that GCC 7.1.0 is also bad and only 6.x was OK
> (which didn't have code hoisting?)
My numbers show that I can't see any regression/improvement on my machine.
And I'm talking about r251376.
>From gcc-bugs-return-627459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 11:35:39 2019
Return-Path: <gcc-bugs-return-627459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13040 invoked by alias); 3 Jan 2019 11:35:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13001 invoked by uid 48); 3 Jan 2019 11:35:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88670] [meta-bug] generic vector extension issues
Date: Thu, 03 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
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-88670-4-Z2bnfSJ65Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00268.txt.bz2
Content-length: 554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
For both user-facing interface and optimization issues when using the
extension.
>From gcc-bugs-return-627461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:07:11 2019
Return-Path: <gcc-bugs-return-627461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57665 invoked by alias); 3 Jan 2019 12:07:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57616 invoked by uid 48); 3 Jan 2019 12:07:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54939] Very poor vectorization of loops with complex arithmetic
Date: Thu, 03 Jan 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-54939-4-1T26BoJHRf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00270.txt.bz2
Content-length: 3383
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org,
| |uros at gcc dot gnu.org
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
On trunk we get with -Ofast -msse4.2
.L3:
movupd (%rdx,%rax), %xmm0
movupd (%rdx,%rax), %xmm1
movupd (%rcx,%rax), %xmm4
mulpd %xmm3, %xmm1
palignr $8, %xmm0, %xmm0
mulpd %xmm2, %xmm0
addsubpd %xmm0, %xmm1
addpd %xmm4, %xmm1
movups %xmm1, (%rcx,%rax)
addq $16, %rax
cmpq %rsi, %rax
jne .L3
ICC unrolls the body once more. With -mavx2 we get
.L4:
vmovupd (%rdx,%rsi), %xmm6
vinsertf128 $0x1, 16(%rdx,%rsi), %ymm6, %ymm1
vmovupd (%rcx,%rsi), %xmm7
vmulpd %ymm5, %ymm1, %ymm2
vpermpd $177, %ymm1, %ymm1
vmulpd %ymm4, %ymm1, %ymm1
vaddsubpd %ymm1, %ymm2, %ymm1
vinsertf128 $0x1, 16(%rcx,%rsi), %ymm7, %ymm2
vaddpd %ymm2, %ymm1, %ymm1
vmovups %xmm1, (%rcx,%rsi)
vextractf128 $0x1, %ymm1, 16(%rcx,%rsi)
addq $32, %rsi
cmpq %rsi, %rdi
jne .L4
if I add -mfma for example via -march=core-avx2 I get again
.L4:
vpermpd $177, (%rdx,%rsi), %ymm2
vmovapd %ymm4, %ymm1
vmulpd %ymm5, %ymm2, %ymm2
vfmsub132pd (%rdx,%rsi), %ymm2, %ymm1
vfmadd231pd (%rdx,%rsi), %ymm4, %ymm2
vshufpd $10, %ymm2, %ymm1, %ymm1
vaddpd (%rcx,%rsi), %ymm1, %ymm1
vmovupd %ymm1, (%rcx,%rsi)
addq $32, %rsi
cmpq %rsi, %rdi
jne .L4
showing that we lack vfmaddsub patterns or those present do not work
properly. combine sees
37: r109:V4DF={r127:V4DF*r105:V4DF+-r108:V4DF}
38: r110:V4DF={r127:V4DF*r105:V4DF+r108:V4DF}
REG_DEAD r127:V4DF
REG_DEAD r108:V4DF
39: r129:V4DF=vec_select(vec_concat(r109:V4DF,r110:V4DF),parallel)
REG_DEAD r110:V4DF
REG_DEAD r109:V4DF
unfortunately the fmaddsub patterns all use UNSPECs with the comment
;; It would be possible to represent these without the UNSPEC as
;;
;; (vec_merge
;; (fma op1 op2 op3)
;; (fma op1 op2 (neg op3))
;; (merge-const))
;;
;; But this doesn't seem useful in practice.
the AVX512 ones do not seem to suffer from this but using AVX512 via
-march=knl also only results in
.L4:
vmovupd (%rdx,%rax), %zmm1
vpermpd $177, %zmm1, %zmm2
vmovapd %zmm1, %zmm0
vmulpd %zmm4, %zmm2, %zmm2
vfmsub132pd %zmm3, %zmm2, %zmm0
vfmadd132pd %zmm3, %zmm2, %zmm1
vshufpd $170, %zmm1, %zmm0, %zmm0
vaddpd (%rcx,%rax), %zmm0, %zmm0
vmovupd %zmm0, (%rcx,%rax)
leaq 64(%rax), %rax
cmpq %rax, %rsi
jne .L4
but maybe KNL doesn't have fmaddsub. Ah, with AVX512 we end up with
vec_merge (like with SSE2) but above AVX256 shows concat/select
(avx_shufpd256_1).
Maybe combine itself can try both variants in case there's a duality
between (vec_merge ...) and (vec_select (vec_concat ...))?
>From gcc-bugs-return-627462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:19:43 2019
Return-Path: <gcc-bugs-return-627462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67125 invoked by alias); 3 Jan 2019 12:19: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 67090 invoked by uid 48); 3 Jan 2019 12:19:38 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/88063] Libbacktrace leak on dwarf read failure
Date: Thu, 03 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: vries at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone
Message-ID: <bug-88063-4-qHDtLzR6Wq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88063-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88063-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00271.txt.bz2
Content-length: 700
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88063
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |vries at gcc dot gnu.org
Target Milestone|--- |9.0
--- Comment #15 from Tom de Vries <vries at gcc dot gnu.org> ---
Patch fixing the problem mentioned in the description committed to trunk.
Other problems mentioned fixed as well in trunk.
Marking resolved-fixed.
>From gcc-bugs-return-627463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:24:20 2019
Return-Path: <gcc-bugs-return-627463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73043 invoked by alias); 3 Jan 2019 12:24: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 72766 invoked by uid 55); 3 Jan 2019 12:23:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Thu, 03 Jan 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85574-4-y8zR99QEBD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00272.txt.bz2
Content-length: 618
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #26 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Jan 3 12:23:27 2019
New Revision: 267552
URL: https://gcc.gnu.org/viewcvs?rev=267552&root=gcc&view=rev
Log:
2019-01-03 Jan Hubicka <hubicka@ucw.cz>
PR tree-optimization/85574
* tree-ssa-uncprop.c (struct equiv_hash_elt): Remove unused
structure.
(struct ssa_equip_hash_traits): Declare.
(val_ssa_equiv): Use custom hash traits using operand_equal_p.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-ssa-uncprop.c
>From gcc-bugs-return-627464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:33:10 2019
Return-Path: <gcc-bugs-return-627464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92589 invoked by alias); 3 Jan 2019 12:33: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 92543 invoked by uid 55); 3 Jan 2019 12:33:06 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48543] Collapse identical strings
Date: Thu, 03 Jan 2019 12: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: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-48543-4-A1QO5YrjaC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00273.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Thu Jan 3 12:32:34 2019
New Revision: 267553
URL: https://gcc.gnu.org/viewcvs?rev=267553&root=gcc&view=rev
Log:
2019-01-02 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/48543
* gfortran.dg/const_chararacter_merge.f90: Remove.
Removed:
trunk/gcc/testsuite/gfortran.dg/merge_char_const.f90
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:40:25 2019
Return-Path: <gcc-bugs-return-627465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103060 invoked by alias); 3 Jan 2019 12:40: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 103000 invoked by uid 48); 3 Jan 2019 12:40:20 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54939] Very poor vectorization of loops with complex arithmetic
Date: Thu, 03 Jan 2019 12:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54939-4-KVmloMoedc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00274.txt.bz2
Content-length: 335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #9 from Segher Boessenkool <segher at gcc dot gnu.org> ---
I think we should declare one of the forms canonical, and make simplify
use that one, if possible. If we really want one form in some cases and
another in other cases something like change_zero_ext will work.
>From gcc-bugs-return-627466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:41:51 2019
Return-Path: <gcc-bugs-return-627466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104315 invoked by alias); 3 Jan 2019 12:41:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104277 invoked by uid 48); 3 Jan 2019 12:41:46 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host
Date: Thu, 03 Jan 2019 12:41: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: umesh.kalappa0 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-88668-4-rHIeLbJ3P4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00275.txt.bz2
Content-length: 207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
--- Comment #4 from Umesh Kalappa <umesh.kalappa0 at gmail dot com> ---
Thank you Andrew for the suggestions and let us try the same and update here .
>From gcc-bugs-return-627467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 12:51:22 2019
Return-Path: <gcc-bugs-return-627467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113005 invoked by alias); 3 Jan 2019 12:51:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112952 invoked by uid 55); 3 Jan 2019 12:51:18 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54939] Very poor vectorization of loops with complex arithmetic
Date: Thu, 03 Jan 2019 12:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54939-4-lbhjQWeyRb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00276.txt.bz2
Content-length: 1532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 3 Jan 2019, segher at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
>
> --- Comment #9 from Segher Boessenkool <segher at gcc dot gnu.org> ---
> I think we should declare one of the forms canonical, and make simplify
> use that one, if possible. If we really want one form in some cases and
> another in other cases something like change_zero_ext will work.
Yeah, the main issue is that targets have existing patterns prefering
either form. vec_merge avoids the need of wider intermediate modes
but with vec_select it's easier to allow constrained operands...
So IMHO RTL shouldn't have both but it would be convenient to
not need that wider mode... it might ask for a
vec_concat_and_select (aka vec_shuffle2). Another issue with
vec_merge is the limit of the bitmask operand
(CONST_INT) which limits us to 64 vector elements.
That said, kill vec_merge and allow
(vec_select:V4DF (vec_concat:V8DF (reg:V4DF...) (reg:V4DF...))
(parallel [ (const_int 0) ....])))
to be written as
(vec_shuffle:V4DF (reg:V4DF...) (reg:V4DF...)
(parallel [ (const_int 0) ....])))
note vec_concat operands are not constrained in any way but
vec_shuffle would be?
That is, in practice targets can probably get rid of vec_merge
by using vec_select/vec_concat "easily" even if that means
introducing of "fake" larger vector modes.
>From gcc-bugs-return-627469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:03:28 2019
Return-Path: <gcc-bugs-return-627469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47640 invoked by alias); 3 Jan 2019 13: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 46907 invoked by uid 48); 3 Jan 2019 13:03:18 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88669] Contiguous attribute wrongly rejected
Date: Thu, 03 Jan 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88669-4-9JMHi1vfs8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00278.txt.bz2
Content-length: 5362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Strange.
The code looks like it does the right thing, but the attributes
apparently have not been set correctly. In resolve.c:
│13778 /* F2008, C448. */
│
│13779 if (c->attr.contiguous && (!c->attr.dimension ||
!c->attr.pointer))
│
│13780 {
│
>│13781 gfc_error ("Component %qs at %L has the CONTIGUOUS attribute
but "
│
│13782 "is not an array pointer", c->name, &c->loc);
│
│13783 return false;
│
│13784 }
│
but
(gdb) p c
$2 = (gfc_component *) 0x2689980
(gdb) p c->attr.dimension
$3 = 0
(gdb) p c->attr.pointer
$4 = 0
>From gcc-bugs-return-627468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:03:19 2019
Return-Path: <gcc-bugs-return-627468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46922 invoked by alias); 3 Jan 2019 13:03:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46138 invoked by uid 48); 3 Jan 2019 13:03:14 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54939] Very poor vectorization of loops with complex arithmetic
Date: Thu, 03 Jan 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54939-4-GdTYK3JcNO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00277.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #11 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #10)
> even if that means introducing of "fake" larger vector modes.
That would be a good reason to not do this, except many targets already
do need double-length modes to describe their permute instructions?
>From gcc-bugs-return-627470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:05:56 2019
Return-Path: <gcc-bugs-return-627470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50800 invoked by alias); 3 Jan 2019 13:05: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 50736 invoked by uid 48); 3 Jan 2019 13:05:51 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54939] Very poor vectorization of loops with complex arithmetic
Date: Thu, 03 Jan 2019 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54939-4-FjqlAGbYln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00279.txt.bz2
Content-length: 640
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #12 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Richard Biener from comment #8)
> Maybe combine itself can try both variants in case there's a duality
> between (vec_merge ...) and (vec_select (vec_concat ...))?
Please note that combine splitters are used to help combine create addsub
pattern. Please also see addsub_vm_operator predicate that handles vec_merge
form and addsub_vs_operator that handles vec_select/vec_concat combo. Please
see PR66560.
Probably these predicates and similar splitters can be used to handle fmaddsub
instructions.
>From gcc-bugs-return-627471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:17:31 2019
Return-Path: <gcc-bugs-return-627471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61858 invoked by alias); 3 Jan 2019 13:17:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61830 invoked by uid 48); 3 Jan 2019 13:17:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88671] New: generic vector passed in MMX regs
Date: Thu, 03 Jan 2019 13:17: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: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00280.txt.bz2
Content-length: 884
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
Bug ID: 88671
Summary: generic vector passed in MMX regs
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
typedef unsigned int U32;
typedef U32 U32x2 __attribute__((vector_size(8)));
typedef U32 U32x4 __attribute__((vector_size(16)));
void bar2(U32x2);
void foo2(U32x2 *p)
{
bar2(*p);
}
void bar4(U32x4);
void foo4(U32x4 *p)
{
bar4(*p);
}
shows bar2/foo2 passing U32x2 in MMX regs on i?86-linux with -msse2
(on the stack when using -mno-mmx). On x86_64-linux args are passed in
SSE regs.
clang passes U32x2 values on the stack on i?86-linux independent of
-m[no-]mmx.
>From gcc-bugs-return-627472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:18:47 2019
Return-Path: <gcc-bugs-return-627472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64684 invoked by alias); 3 Jan 2019 13:18:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64650 invoked by uid 48); 3 Jan 2019 13:18:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88671] generic vector passed in MMX regs
Date: Thu, 03 Jan 2019 13:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget
Message-ID: <bug-88671-4-DvyJzBkrkV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00281.txt.bz2
Content-length: 780
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ABI
Target| |i?86-*-*
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
And -m32 -msse2 -mno-mmx of course warns:
t.c: In function ‘foo2’:
t.c:8:3: warning: MMX vector argument without MMX enabled changes the ABI
[-Wpsabi]
bar2(*p);
^~~~~~~~
so it seems to work as designed. Still it might be unfortunate to the
occasional user of generic vectors with MMX size that MMX is used
when not using intrinsics...
>From gcc-bugs-return-627474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:22:43 2019
Return-Path: <gcc-bugs-return-627474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73864 invoked by alias); 3 Jan 2019 13:22: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 73811 invoked by uid 55); 3 Jan 2019 13:22:39 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/54939] Very poor vectorization of loops with complex arithmetic
Date: Thu, 03 Jan 2019 13:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-54939-4-OFmQstj0gO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54939-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00283.txt.bz2
Content-length: 719
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 3 Jan 2019, segher at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54939
>
> --- Comment #11 from Segher Boessenkool <segher at gcc dot gnu.org> ---
> (In reply to rguenther@suse.de from comment #10)
> > even if that means introducing of "fake" larger vector modes.
>
> That would be a good reason to not do this, except many targets already
> do need double-length modes to describe their permute instructions?
Yes. I think there's no good need for vec_merge for those targets.
vec_shuffle would of course remove the need of the larger modes.
>From gcc-bugs-return-627473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:22:32 2019
Return-Path: <gcc-bugs-return-627473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73097 invoked by alias); 3 Jan 2019 13:22: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 73055 invoked by uid 48); 3 Jan 2019 13:22:27 -0000
From: "damian.jarek93 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88672] New: friend class template declaration in a class template is ignored
Date: Thu, 03 Jan 2019 13:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: damian.jarek93 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-88672-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00282.txt.bz2
Content-length: 728
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
Bug ID: 88672
Summary: friend class template declaration in a class template
is ignored
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: damian.jarek93 at gmail dot com
Target Milestone: ---
Friend class template declaration in a class template is ignored, reproduces on
gcc 4.9 and above (didn't check earlier versions)
Example: https://godbolt.org/z/FdmEHE
Note that if S is not a class template, it works correctly:
https://godbolt.org/z/dnp6uT
>From gcc-bugs-return-627475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:25:24 2019
Return-Path: <gcc-bugs-return-627475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76480 invoked by alias); 3 Jan 2019 13:25:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76320 invoked by uid 48); 3 Jan 2019 13:25:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88619] [9 Regression] ICE in asan_emit_stack_protection, at asan.c:1574 since r266664
Date: Thu, 03 Jan 2019 13:25: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88619-4-z18P63997F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00284.txt.bz2
Content-length: 691
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88619
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45324
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45324&action=edit
gcc9-pr88619.patch
Untested fix. make check-gcc check-c++-all
RUNTESTFLAGS='--target_board=unix\{-m32,-m64\} asan.exp' passes with this, but
haven't checked anything beyond that. The variables are sorted primarily on
large vs. small alignment (not relevant to x86), then on size and only
afterwards on alignment, so if there is e.g. a big variable and after it a
smaller one with much bigger alignment, we could have triggered this already in
earlier releases.
>From gcc-bugs-return-627476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:31:58 2019
Return-Path: <gcc-bugs-return-627476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84010 invoked by alias); 3 Jan 2019 13:31: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 83960 invoked by uid 48); 3 Jan 2019 13:31:52 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88671] generic vector passed in MMX regs
Date: Thu, 03 Jan 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88671-4-mRIzPMTMwA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00285.txt.bz2
Content-length: 366
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
This is required by ABI, please see section 2.3.3 of i386 PSABI, where:
The exceptions to parameters passed on stack are as follows:
• The first three parameters of type __m64 are passed in %mm0, %mm1, and %mm2.
So, clang is wrong.
>From gcc-bugs-return-627477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:35:40 2019
Return-Path: <gcc-bugs-return-627477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94895 invoked by alias); 3 Jan 2019 13:35:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94861 invoked by uid 48); 3 Jan 2019 13:35:34 -0000
From: "venkateshprabu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88673] New: Overflowed array index read error
Date: Thu, 03 Jan 2019 13:35: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: 6.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: venkateshprabu 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-88673-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00286.txt.bz2
Content-length: 2188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88673
Bug ID: 88673
Summary: Overflowed array index read error
Product: gcc
Version: 6.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: venkateshprabu at gmail dot com
Target Milestone: ---
https://github.com/gcc-mirror/gcc/blob/gcc-6_2_0-release/libstdc++-v3/include/bits/random.tcc#L399
Coverity report:
399 _M_gen_rand(void)
400 {
401 const _UIntType __upper_mask = (~_UIntType()) << __r;
402 const _UIntType __lower_mask = ~__upper_mask;
403
1. Condition __k < 227UL /* 624UL - 397UL */, taking true branch.
4. Condition __k < 227UL /* 624UL - 397UL */, taking true branch.
7. Condition __k < 227UL /* 624UL - 397UL */, taking false branch.
404 for (size_t __k = 0; __k < (__n - __m); ++__k)
405 {
406 _UIntType __y = ((_M_x[__k] & __upper_mask)
407 | (_M_x[__k + 1] & __lower_mask));
2. Condition __y & 1, taking true branch.
5. Condition __y & 1, taking true branch.
408 _M_x[__k] = (_M_x[__k + __m] ^ (__y >> 1)
409 ^ ((__y & 0x01) ? __a : 0));
3. Jumping back to the beginning of the loop.
6. Jumping back to the beginning of the loop.
410 }
411
8. Condition __k < 623UL /* 624UL - 1 */, taking true branch.
412 for (size_t __k = (__n - __m); __k < (__n - 1); ++__k)
413 {
414 _UIntType __y = ((_M_x[__k] & __upper_mask)
415 | (_M_x[__k + 1] & __lower_mask));
9. overflow: Add operation overflows on operands __k and
18446744073709551389UL.
CID 4797118 (#1-2 of 2): Overflowed array index read (INTEGER_OVERFLOW)
10. overflow_sink: Overflowed or truncated value (or a value computed from an
overflowed or truncated value) __k + 18446744073709551389UL used as array
index.
416 _M_x[__k] = (_M_x[__k + (__m - __n)] ^ (__y >> 1)
417 ^ ((__y & 0x01) ? __a : 0));
418 }
>From gcc-bugs-return-627478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 13:38:03 2019
Return-Path: <gcc-bugs-return-627478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97691 invoked by alias); 3 Jan 2019 13: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 97618 invoked by uid 48); 3 Jan 2019 13:37:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88671] generic vector passed in MMX regs
Date: Thu, 03 Jan 2019 13:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88671-4-Bo9LzsXfju@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00287.txt.bz2
Content-length: 655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, so the question would be whether unsinged int
__attribute__((vector_size(8)))
is of type __m64 (I guess x87 psABI terms are not C language lawyer terms).
But yes, even when naming the type __m64 clang doesn't pass in mmx regs.
>From gcc-bugs-return-627479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:04:28 2019
Return-Path: <gcc-bugs-return-627479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58342 invoked by alias); 3 Jan 2019 14:04:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58287 invoked by uid 48); 3 Jan 2019 14:04:23 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88674] New: GCC thinks that register is a qualifier in function declaration with no parameters.
Date: Thu, 03 Jan 2019 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00288.txt.bz2
Content-length: 1038
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88674
Bug ID: 88674
Summary: GCC thinks that register is a qualifier in function
declaration with no parameters.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
void f(register void);
int main()
{
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
The following error message was outputed:
prog.c:1:8: error: 'void' as only parameter may not be qualified
1 | void f(register void);
| ^~~~~~~~~~~~~
Expected behaviour:
No error message outputed.
The program is valid. register is not a type qualifier.
Note:
Clang accepts the program without outputing any error message.
>From gcc-bugs-return-627480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:08:09 2019
Return-Path: <gcc-bugs-return-627480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62235 invoked by alias); 3 Jan 2019 14:08: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 62166 invoked by uid 48); 3 Jan 2019 14:08:02 -0000
From: "huili80 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88675] New: std::make_integer_sequence not working for enums
Date: Thu, 03 Jan 2019 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: huili80 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-88675-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00289.txt.bz2
Content-length: 1467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88675
Bug ID: 88675
Summary: std::make_integer_sequence not working for enums
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: huili80 at gmail dot com
Target Milestone: ---
The following code doesn't compile with --std=c++17:
#include <utility>
enum Number
{
Zero,
One,
Two,
Three
};
int main()
{
std::make_integer_sequence<Number,Three> s;
}
The error read:
/usr/include/c++/8/utility: In substitution of 'template<class _Tp, _Tp _Num>
using make_integer_sequence = std::integer_sequence<_Tp,
__integer_pack(_Num)...> [with _Tp = Number; _Tp _Num = (Number)3]':
t.cpp:13:43: required from here
/usr/include/c++/8/utility:329:55: error: invalid conversion from 'sizetype' to
'Number' [-fpermissive]
= integer_sequence<_Tp, __integer_pack(_Num)...>;
^
/usr/include/c++/8/utility:329:55: error: invalid conversion from 'sizetype' to
'Number' [-fpermissive]
/usr/include/c++/8/utility:329:55: error: invalid conversion from 'sizetype' to
'Number' [-fpermissive]
I suspect that this would be an easy fix by changing
/usr/include/c++/8/utility:329 to
= integer_sequence<_Tp, _Tp(__integer_pack(_Num))...>;
>From gcc-bugs-return-627481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:21:10 2019
Return-Path: <gcc-bugs-return-627481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83565 invoked by alias); 3 Jan 2019 14:21:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82855 invoked by uid 48); 3 Jan 2019 14:21:02 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] Hangs in libphobos testsuite
Date: Thu, 03 Jan 2019 14:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88654-4-33mGNuSyDz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00290.txt.bz2
Content-length: 1278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #3 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Jakub Jelinek from comment #0)
> The reason I'm filing this is that there are multiple issues:
>
> 1) what I'm worried about most is that the timeouts for tests don't work, it
> happens that some test gets stuck, but it should be killed after 5 minutes
> or for how long the default timeout is set and the set should FAIL in that
> case or something similar
>
I couldn't reproduce, maybe I'm running the 32bit testsuite differently though?
Running ../../../../../libphobos/testsuite/libphobos.unittests/unittests.exp
...
WARNING: program timed out.
FAIL: libphobos.unittests/phobos/static/std.net.curl
WARNING: program timed out.
FAIL: libphobos.unittests/phobos/shared/std.net.curl
> 2) if Curl fails to initialize, the test shouldn't get stuck
>
Patch I've sent upstream fixes this.
> 3) and, if libcurl isn't available, I think it would be better to skip the
> test as UNSUPPORTED, i.e. add some effective-target that tests if libcurl is
> available and if it fails, don't even try to run the test
This would be a proc local to libphobos I guess? There's nothing using this
module outside of the libphobos testsuite.
>From gcc-bugs-return-627482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:25:04 2019
Return-Path: <gcc-bugs-return-627482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87084 invoked by alias); 3 Jan 2019 14:25:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86749 invoked by uid 48); 3 Jan 2019 14:24:30 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Thu, 03 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88598-4-7VR3xnn0Cr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00291.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-627483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:25:23 2019
Return-Path: <gcc-bugs-return-627483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88193 invoked by alias); 3 Jan 2019 14:25: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 87340 invoked by uid 48); 3 Jan 2019 14:25:03 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88671] generic vector passed in MMX regs
Date: Thu, 03 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88671-4-qj9CZUE4be@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00292.txt.bz2
Content-length: 811
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88671
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Uroš Bizjak from comment #2)
> This is required by ABI, please see section 2.3.3 of i386 PSABI, where:
>
> The exceptions to parameters passed on stack are as follows:
> • The first three parameters of type __m64 are passed in %mm0, %mm1, and
> %mm2.
>
> So, clang is wrong.
clang is never good at conforming to psABIs:
https://bugs.llvm.org/show_bug.cgi?id=39501
There are other psABI bugs in clang.
>From gcc-bugs-return-627484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:27:03 2019
Return-Path: <gcc-bugs-return-627484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89655 invoked by alias); 3 Jan 2019 14:27: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 89586 invoked by uid 48); 3 Jan 2019 14:26:59 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88676] New: missed opportunity is integer conditional
Date: Thu, 03 Jan 2019 14:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz 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-88676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00293.txt.bz2
Content-length: 1243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
Bug ID: 88676
Summary: missed opportunity is integer conditional
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: drepper.fsp+rhbz at gmail dot com
Target Milestone: ---
Take the following code:
int f(unsigned b)
{
int r;
if (b >= 2)
__builtin_unreachable();
switch (b) {
case 0:
r = 1;
break;
case 1:
r = 2;
break;
default:
r = 0;
break;
}
return r;
}
Compiled using the current trunk gcc and gcc 8.2.1 with -O3 on x86_64 the
following code is produced:
0000000000000000 <f>:
0: 31 c0 xor %eax,%eax
2: 83 ff 01 cmp $0x1,%edi
5: 0f 94 c0 sete %al
8: ff c0 inc %eax
a: c3 retq
This is quite good but it should be something like
leal 1(%edi),%eax
ret
The first three instructions test for 0 or 1 and load into %eax the values 0 or
1 respectively. This should be just a move.
>From gcc-bugs-return-627485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:30:24 2019
Return-Path: <gcc-bugs-return-627485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96017 invoked by alias); 3 Jan 2019 14:30: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 95534 invoked by uid 48); 3 Jan 2019 14:30:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] Hangs in libphobos testsuite
Date: Thu, 03 Jan 2019 14:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
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: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88654-4-5iwwegD5dK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00294.txt.bz2
Content-length: 3052
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Iain Buclaw from comment #3)
> (In reply to Jakub Jelinek from comment #0)
> > The reason I'm filing this is that there are multiple issues:
> >
> > 1) what I'm worried about most is that the timeouts for tests don't work, it
> > happens that some test gets stuck, but it should be killed after 5 minutes
> > or for how long the default timeout is set and the set should FAIL in that
> > case or something similar
> >
>
> I couldn't reproduce, maybe I'm running the 32bit testsuite differently
> though?
>
> Running ../../../../../libphobos/testsuite/libphobos.unittests/unittests.exp
> ...
> WARNING: program timed out.
> FAIL: libphobos.unittests/phobos/static/std.net.curl
> WARNING: program timed out.
> FAIL: libphobos.unittests/phobos/shared/std.net.curl
My i686-linux bootstraps are done through a couple of executable scripts in
~/hbin directory on x86_64-linux:
for i in ~/hbin/*; do echo ===$i===; cat $i; done
===/home/jakub/hbin/as===
#!/bin/sh
exec /usr/bin/as --32 "$@"
===/home/jakub/hbin/g++===
#!/bin/sh
exec /usr/bin/g++ -m32 "$@"
===/home/jakub/hbin/gcc===
#!/bin/sh
exec /usr/bin/gcc -m32 "$@"
===/home/jakub/hbin/ld===
#!/bin/sh
case "$*" in
--version) cat <<\EOF
GNU ld version 2.20.52.0.1-10.fc17 20100131
Copyright 2012 Free Software Foundation, Inc.
This program is free software; you may redistribute it under the terms of
the GNU General Public License version 3 or (at your option) a later version.
This program has absolutely no warranty.
EOF
exit 0;;
esac
exec /usr/bin/ld -m elf_i386 -L /usr/lib/ "$@"
and then
PATH=~/hbin:$PATH i386 ../configure
--enable-languages=default,obj-c++,lto,go,brig,d
--enable-checking=yes,rtl,extra \
&& PATH=~/hbin:$PATH i386 make -j32 bootstrap > LOG 2>&1 \
&& PATH=~/hbin:$PATH i386 make -j32 -k check > LOGC 2>&1; \
../contrib/test_summary > LOGT 2>&1
and that got stuck forever if libcurl.i?86 wasn't installed (only
libcurl.x86_64 and libcurl-devel.x86_64), but works
fine now that I also have libcurl.i?86 installed.
> > 3) and, if libcurl isn't available, I think it would be better to skip the
> > test as UNSUPPORTED, i.e. add some effective-target that tests if libcurl is
> > available and if it fails, don't even try to run the test
>
> This would be a proc local to libphobos I guess? There's nothing using this
> module outside of the libphobos testsuite.
If the test doesn't fail if it fails to load libcurl (and doesn't get stuck),
it is fine too.
If it fails if it is missing, yeah, something like a tcl procedure somewhere in
libphobos/testsuite/lib/*.exp would do.
As libphobos itself doesn't need libcurl-devel, it is just dlopen, so I think
you want to test that
#include <dlfcn.h>
int
main ()
{
void *h = dlopen ("libcurl.so.4"); // etc., whatever the library will try to
dlopen
...
}
will succeed dlopening it.
>From gcc-bugs-return-627486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:31:47 2019
Return-Path: <gcc-bugs-return-627486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100677 invoked by alias); 3 Jan 2019 14:31:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100557 invoked by uid 48); 3 Jan 2019 14:31:40 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/84478] [8 Regression] pdftex miscompilation on i386
Date: Thu, 03 Jan 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84478-4-ZHcTO3NA51@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84478-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00295.txt.bz2
Content-length: 934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84478
--- Comment #10 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Rainer Orth from comment #5)
> The new testcase FAILs e.g. on i386-pc-solaris2.11 and sparc-sun-solaris2.11
> (32-bit only) at -O1 and above:
>
> +FAIL: gcc.c-torture/execute/pr84478.c -O1 execution test
> +FAIL: gcc.c-torture/execute/pr84478.c -O2 execution test
> +FAIL: gcc.c-torture/execute/pr84478.c -O2 -flto execution test
> +FAIL: gcc.c-torture/execute/pr84478.c -O2 -flto -flto-partition=none
> execution test
> +FAIL: gcc.c-torture/execute/pr84478.c -O3 -fomit-frame-pointer
> -funroll-loops -fpeel-loops -ftracer -finline-functions execution test
> +FAIL: gcc.c-torture/execute/pr84478.c -O3 -g execution test
>
> According to gcc-testresult postings, the same happens on a couple of other
> targets, including i686-pc-linux-gnu.
Please try r267520 or newer.
>From gcc-bugs-return-627487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:38:23 2019
Return-Path: <gcc-bugs-return-627487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8384 invoked by alias); 3 Jan 2019 14:38:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8294 invoked by uid 48); 3 Jan 2019 14:38:17 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Thu, 03 Jan 2019 14:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88598-4-cRt29vX1YU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00296.txt.bz2
Content-length: 350
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
I think a general fix for this would involve tracking the set of
nonzero vector elements and adding a match.pd rule that uses that
to replace REDUC functions in which only one element of the
argument is nonzero.
>From gcc-bugs-return-627488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:38:54 2019
Return-Path: <gcc-bugs-return-627488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25561 invoked by alias); 3 Jan 2019 14: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 20050 invoked by uid 48); 3 Jan 2019 14:38:48 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88669] Contiguous attribute wrongly rejected
Date: Thu, 03 Jan 2019 14:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88669-4-nDC89ZVAPu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88669-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00297.txt.bz2
Content-length: 217
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88669
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Works when class(t) is replaced by type(t), so the attributes
were not correctly set somewhere.
>From gcc-bugs-return-627489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:41:52 2019
Return-Path: <gcc-bugs-return-627489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50704 invoked by alias); 3 Jan 2019 14:41:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41266 invoked by uid 55); 3 Jan 2019 14:41:47 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Thu, 03 Jan 2019 14:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88598-4-vRWff4Lbzp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00298.txt.bz2
Content-length: 760
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 3 Jan 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
>
> --- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> I think a general fix for this would involve tracking the set of
> nonzero vector elements and adding a match.pd rule that uses that
> to replace REDUC functions in which only one element of the
> argument is nonzero.
Yes. Or even replacing REDUC_PLUS <constants, single-non-constant>
with a partial reduction over the constants plus the single non-constant
element.
But variable-length stuff is a bit awkward in match.pd.
>From gcc-bugs-return-627490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:53:20 2019
Return-Path: <gcc-bugs-return-627490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35493 invoked by alias); 3 Jan 2019 14:53: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 32799 invoked by uid 48); 3 Jan 2019 14:53:15 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] New: Divergence in -O2 and -O2 -flto early opts
Date: Thu, 03 Jan 2019 14:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00299.txt.bz2
Content-length: 1006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Bug ID: 88677
Summary: Divergence in -O2 and -O2 -flto early opts
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
Created attachment 45325
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45325&action=edit
testcase
This causes profile data loss for Firefox.
There is one PHI different in function obj_seal in fre1 dump when built with:
g++ test2.ii -O3 -fomit-frame-pointer -funwind-tables -fno-strict-aliasing
-fno-rtti -fno-exceptions -fno-math-errno test2.ii -fdump-tree-fre1 -flto
and
g++ test2.ii -O3 -fomit-frame-pointer -funwind-tables -fno-strict-aliasing
-fno-rtti -fno-exceptions -fno-math-errno test2.ii -fdump-tree-fre1
>From gcc-bugs-return-627491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:53:52 2019
Return-Path: <gcc-bugs-return-627491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52599 invoked by alias); 3 Jan 2019 14:53: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 49990 invoked by uid 48); 3 Jan 2019 14:53:48 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] Divergence in -O2 and -O2 -flto early opts
Date: Thu, 03 Jan 2019 14:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88677-4-Ceii8fC9DN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00300.txt.bz2
Content-length: 236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 45326
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45326&action=edit
dump with no lto
>From gcc-bugs-return-627492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 14:54:25 2019
Return-Path: <gcc-bugs-return-627492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84458 invoked by alias); 3 Jan 2019 14:54: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 79565 invoked by uid 48); 3 Jan 2019 14:54:20 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] Divergence in -O2 and -O2 -flto early opts
Date: Thu, 03 Jan 2019 14:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88677-4-SWlpxpJYYK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00301.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 45327
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45327&action=edit
dump with lto
>From gcc-bugs-return-627493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 15:01:59 2019
Return-Path: <gcc-bugs-return-627493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51240 invoked by alias); 3 Jan 2019 15:01:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51103 invoked by uid 48); 3 Jan 2019 15:01:49 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Thu, 03 Jan 2019 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-e5h3u9JhY3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00302.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Yes, the extension should be zero-extend, not sign extend. The plus operation
is correct, however, since decrementing the first operand could lead to
underflow if it was zero. So the correct rtl would be
(compare ((zero_x(a)) (plus (zero_x(b) (ltu(cc, 0)))))
(minus (...))
>From gcc-bugs-return-627494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 15:03:15 2019
Return-Path: <gcc-bugs-return-627494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63246 invoked by alias); 3 Jan 2019 15: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 63189 invoked by uid 48); 3 Jan 2019 15:03:07 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] New: [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Thu, 03 Jan 2019 15:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.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-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00303.txt.bz2
Content-length: 5937
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
Bug ID: 88678
Summary: [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test
cases fail starting with r267465
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
There are a bunch of the gfortran.dg/ieee/ieee_X.f90 test cases that began
failing with r267465:
FAIL: gfortran.dg/ieee/ieee_10.f90 -O0 execution test
FAIL: gfortran.dg/ieee/ieee_10.f90 -O1 execution test
FAIL: gfortran.dg/ieee/ieee_10.f90 -O2 execution test
FAIL: gfortran.dg/ieee/ieee_10.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/ieee/ieee_10.f90 -O3 -g execution test
FAIL: gfortran.dg/ieee/ieee_10.f90 -Os execution test
FAIL: gfortran.dg/ieee/ieee_2.f90 -O0 execution test
FAIL: gfortran.dg/ieee/ieee_2.f90 -O1 execution test
FAIL: gfortran.dg/ieee/ieee_2.f90 -O2 execution test
FAIL: gfortran.dg/ieee/ieee_2.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/ieee/ieee_2.f90 -O3 -g execution test
FAIL: gfortran.dg/ieee/ieee_2.f90 -Os execution test
FAIL: gfortran.dg/ieee/ieee_3.f90 -O0 execution test
FAIL: gfortran.dg/ieee/ieee_3.f90 -O1 execution test
FAIL: gfortran.dg/ieee/ieee_3.f90 -O2 execution test
FAIL: gfortran.dg/ieee/ieee_3.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/ieee/ieee_3.f90 -O3 -g execution test
FAIL: gfortran.dg/ieee/ieee_3.f90 -Os execution test
FAIL: gfortran.dg/ieee/ieee_4.f90 -O0 execution test
FAIL: gfortran.dg/ieee/ieee_4.f90 -O1 execution test
FAIL: gfortran.dg/ieee/ieee_4.f90 -O2 execution test
FAIL: gfortran.dg/ieee/ieee_4.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/ieee/ieee_4.f90 -O3 -g execution test
FAIL: gfortran.dg/ieee/ieee_4.f90 -Os execution test
FAIL: gfortran.dg/ieee/large_1.f90 -O0 execution test
FAIL: gfortran.dg/ieee/large_1.f90 -O1 execution test
FAIL: gfortran.dg/ieee/large_1.f90 -O2 execution test
FAIL: gfortran.dg/ieee/large_1.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/ieee/large_1.f90 -O3 -g execution test
FAIL: gfortran.dg/ieee/large_1.f90 -Os execution test
The failures all look like this one:
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test2/gcc/testsuite/gfortran/../../gfortran
-B/home/seurer/gcc/build/gcc-test2/gcc/testsuite/gfortran/../../
-B/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/ieee/ieee_10.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O0 -ffpe-trap=overflow,invalid
-B/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs
-L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs
-L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs
-L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libatomic/.libs
-B/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs
-L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs
-L/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs
-lm -o ./ieee_10.exe
PASS: gfortran.dg/ieee/ieee_10.f90 -O0 (test for excess errors)
Setting LD_LIBRARY_PATH to
.:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libatomic/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs:/home/seurer/gcc/build/gcc-test2/gcc:.:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libgfortran/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libatomic/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs:/home/seurer/gcc/build/gcc-test2/powerpc64le-unknown-linux-gnu/./libquadmath/.libs:/home/seurer/gcc/build/gcc-test2/gcc:/home/seurer/gcc/build/gcc-test2/./gmp/.libs:/home/seurer/gcc/build/gcc-test2/./prev-gmp/.libs:/home/seurer/gcc/build/gcc-test2/./mpfr/src/.libs:/home/seurer/gcc/build/gcc-test2/./prev-mpfr/src/.libs:/home/seurer/gcc/build/gcc-test2/./mpc/src/.libs:/home/seurer/gcc/build/gcc-test2/./prev-mpc/src/.libs:/home/seurer/gcc/build/gcc-test2/./isl/.libs:/home/seurer/gcc/build/gcc-test2/./prev-isl/.libs:/home/seurer/gcc/install/gcc-7.2.0/lib64
Execution timeout is: 300
spawn [open ...]
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic
operation.
Backtrace for this error:
#0 0x3fffb00304d7 in ???
#1 0x3fffafd17068 in ???
FAIL: gfortran.dg/ieee/ieee_10.f90 -O0 execution test
r267465 | kargl | 2018-12-29 12:10:57 -0600 (Sat, 29 Dec 2018) | 11 lines
2018-12-29 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/88342
* ieee/ieee_arithmetic.F90: Prevent exceptions in IEEE_VALUE if
-ffpe-trap=invalid or -ffpe-trap=overflow is used.
2018-12-29 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/88342
* gfortran.dg/ieee/ieee_10.f90: New test.
>From gcc-bugs-return-627495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 15:22:21 2019
Return-Path: <gcc-bugs-return-627495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106185 invoked by alias); 3 Jan 2019 15:22:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106124 invoked by uid 48); 3 Jan 2019 15:22:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Thu, 03 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-88677-4-DiBKj8qHPi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00304.txt.bz2
Content-length: 812
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
Known to work| |8.2.0
Summary|Divergence in -O2 and -O2 |[9 Regression] Divergence
|-flto early opts |in -O2 and -O2 -flto early
| |opts
Ever confirmed|0 |1
Known to fail| |9.0
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r265841.
>From gcc-bugs-return-627496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 15:26:29 2019
Return-Path: <gcc-bugs-return-627496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111328 invoked by alias); 3 Jan 2019 15:26: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 111245 invoked by uid 48); 3 Jan 2019 15:26:23 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Thu, 03 Jan 2019 15: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: 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:
Message-ID: <bug-88678-4-R47Rr13RJI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00305.txt.bz2
Content-length: 1058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to seurer from comment #0)
> Program received signal SIGFPE: Floating-point exception - erroneous
> arithmetic operation.
>
> Backtrace for this error:
> #0 0x3fffb00304d7 in ???
What is this?
> #1 0x3fffafd17068 in ???
and this?
> FAIL: gfortran.dg/ieee/ieee_10.f90 -O0 execution test
>
>
> r267465 | kargl | 2018-12-29 12:10:57 -0600 (Sat, 29 Dec 2018) | 11 lines
>
> 2018-12-29 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/88342
> * ieee/ieee_arithmetic.F90: Prevent exceptions in IEEE_VALUE if
> -ffpe-trap=invalid or -ffpe-trap=overflow is used.
>
> 2018-12-29 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/88342
> * gfortran.dg/ieee/ieee_10.f90: New test.
The change in question queries the system if it supports IEEE
arithmetic. If powerpc64 does not support IEEE arithmetic or
the OS prevents a user from manipulating the FPU, then you need
to XFAIL the tests.
>From gcc-bugs-return-627497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 15:26:49 2019
Return-Path: <gcc-bugs-return-627497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112243 invoked by alias); 3 Jan 2019 15:26:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112165 invoked by uid 55); 3 Jan 2019 15:26:44 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Thu, 03 Jan 2019 15:26: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88677-4-92Dr3eVVzX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00306.txt.bz2
Content-length: 660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #4 from Jan Hubicka <hubicka at ucw dot cz> ---
This drops TYPE_NEEDS_CONSTRUCTING. I checked the uses
jan@skylake:~/trunk/gcc> grep TYPE_NEEDS_CONSTRU *.c
gimplify.c: || TYPE_NEEDS_CONSTRUCTING (TREE_TYPE (decl))))
print-tree.c: if (TYPE_NEEDS_CONSTRUCTING (node))
tree.c: TYPE_NEEDS_CONSTRUCTING (type) = 0;
tree.c: verify_variant_match (TYPE_NEEDS_CONSTRUCTING);
tree-inline.c: if (TYPE_NEEDS_CONSTRUCTING (TREE_TYPE (p)))
I convinced myself that gimply and tree-inline uses are there only for
inlining/gimplifying within frontend. Perhaps they can also be dropped?
Honza
>From gcc-bugs-return-627498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 15:58:59 2019
Return-Path: <gcc-bugs-return-627498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24729 invoked by alias); 3 Jan 2019 15: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 23470 invoked by uid 48); 3 Jan 2019 15:58:53 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Thu, 03 Jan 2019 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88677-4-Y8weXSqlaj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00307.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-reduction
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm reducing that test-case..
>From gcc-bugs-return-627499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 16:09:02 2019
Return-Path: <gcc-bugs-return-627499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47668 invoked by alias); 3 Jan 2019 16:09: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 47156 invoked by uid 48); 3 Jan 2019 16:08:57 -0000
From: "acsawdey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88027] PowerPC generates slightly weird code for memset
Date: Thu, 03 Jan 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: acsawdey at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: acsawdey 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-88027-4-acqa5Ukcbl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88027-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88027-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00308.txt.bz2
Content-length: 591
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88027
acsawdey at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-03
Assignee|unassigned at gcc dot gnu.org |acsawdey at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #5 from acsawdey at gcc dot gnu.org ---
This is fixed in trunk but I should backport to 8 now too.
>From gcc-bugs-return-627500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 16:54:41 2019
Return-Path: <gcc-bugs-return-627500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68009 invoked by alias); 3 Jan 2019 16:54:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67900 invoked by uid 48); 3 Jan 2019 16:54:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88675] std::make_integer_sequence not working for enums
Date: Thu, 03 Jan 2019 16:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
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-88675-4-Itq8skkr6H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88675-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88675-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00309.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88675
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The C++ standard requires that the first template argument for
std::integer_sequence is an integer type, so your code is undefined.
>From gcc-bugs-return-627501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:05:07 2019
Return-Path: <gcc-bugs-return-627501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58690 invoked by alias); 3 Jan 2019 17:05: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 58554 invoked by uid 48); 3 Jan 2019 17:04:58 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88679] New: SSE2 intrinsics are available by default on x86
Date: Thu, 03 Jan 2019 17: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-88679-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00310.txt.bz2
Content-length: 780
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
Bug ID: 88679
Summary: SSE2 intrinsics are available by default on x86
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: bugzilla@poradnik-webmastera.com
Target Milestone: ---
SSE2 intrinsics are available by default when compiling code for 32-bit x86.
Code below compiles fine with options -m32 -O3. I had to add -mno-sse2 to get
an error.
Fortunately __SSE2__ is not defined by default, so code can rely on it.
[code]
#include <immintrin.h>
void test(__m128i const* m)
{
__m128i v = _mm_load_si128(m);
}
[/code]
>From gcc-bugs-return-627502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:21:35 2019
Return-Path: <gcc-bugs-return-627502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24498 invoked by alias); 3 Jan 2019 17:21: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 24422 invoked by uid 55); 3 Jan 2019 17:21:30 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 17:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88343-4-lddIgY07Xt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00311.txt.bz2
Content-length: 1835
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #16 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Thu, 3 Jan 2019, iains at gcc dot gnu.org wrote:
> Unfortunately, there doesn't appear to be anything in the GCC test suite that
> catches this (all languages reg-strap was clean, on gcc110). Does it show for
> a 32b multilib on a 64b host, or only with a 32b host?
All my testing has been for x86_64-linux-gnu host, powerpc-linux-gnu
target, --disable-multilib --with-float=soft.
The issue appears when a test built with a compiler without the problem
patch is run with glibc built with a compiler with the patch, so it looks
like something miscompiled in glibc - but it also seems sensitive to e.g.
the exact compilation options used for compiling the test with the
non-buggy compiler (as would be expected if e.g. the buggy compiler is
generating code that's using uninitialized or overwritten data in some way
and so details that should be irrelevant end up mattering). I'll look for
a specific object file in glibc that shows the issue if built with the
buggy compiler and inserted in glibc otherwise built with the non-buggy
compiler. The current cut-down version of the glibc test I have (built
with -lm -O2 -fno-builtin with GCC 8 branch just before the change) is:
float nextafterf (float, float);
int printf (const char *, ...);
static void
check_ulp (void)
{
float ulps, value;
value = nextafterf (10, 20);
/* Should print 0x1.400002p+3. */
printf ("%a\n", value);
for (int i = 1; i < 100; i++)
value = nextafterf (value, 20);
ulps = __builtin_fabsf (value - 10);
/* Should print 0x1.9p-14; buggy case hangs before this. */
printf ("%a\n", ulps);
}
int
main (void)
{
check_ulp ();
}
>From gcc-bugs-return-627503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:32:24 2019
Return-Path: <gcc-bugs-return-627503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86650 invoked by alias); 3 Jan 2019 17:32: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 86593 invoked by uid 48); 3 Jan 2019 17:32:19 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88679] SSE2 intrinsics are available by default on x86
Date: Thu, 03 Jan 2019 17:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools 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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88679-4-FpB8BDxr3k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00312.txt.bz2
Content-length: 517
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-03
Ever confirmed|0 |1
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
Please show output of
$ gcc -v
$ gcc -v -m32 .... -S
>From gcc-bugs-return-627504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:37:52 2019
Return-Path: <gcc-bugs-return-627504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93299 invoked by alias); 3 Jan 2019 17:37: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 92268 invoked by uid 48); 3 Jan 2019 17:37:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88673] Overflowed array index read error
Date: Thu, 03 Jan 2019 17:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88673-4-ZL6SgvSX65@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88673-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88673-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00313.txt.bz2
Content-length: 2723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88673
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-03
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
GCC 6.x is no longer supported, and 6.2.0 is not even the latest release from
the 6.x branch, so it's not very useful to report bugs against that version.
(In reply to Venkatesh Prabhu from comment #0)
> https://github.com/gcc-mirror/gcc/blob/gcc-6_2_0-release/libstdc++-v3/
> include/bits/random.tcc#L399
>
>
> Coverity report:
>
> 399 _M_gen_rand(void)
> 400 {
> 401 const _UIntType __upper_mask = (~_UIntType()) << __r;
> 402 const _UIntType __lower_mask = ~__upper_mask;
> 403
> 1. Condition __k < 227UL /* 624UL - 397UL */, taking true branch.
> 4. Condition __k < 227UL /* 624UL - 397UL */, taking true branch.
> 7. Condition __k < 227UL /* 624UL - 397UL */, taking false branch.
> 404 for (size_t __k = 0; __k < (__n - __m); ++__k)
> 405 {
> 406 _UIntType __y = ((_M_x[__k] & __upper_mask)
> 407 | (_M_x[__k + 1] & __lower_mask));
> 2. Condition __y & 1, taking true branch.
> 5. Condition __y & 1, taking true branch.
> 408 _M_x[__k] = (_M_x[__k + __m] ^ (__y >> 1)
> 409 ^ ((__y & 0x01) ? __a : 0));
> 3. Jumping back to the beginning of the loop.
> 6. Jumping back to the beginning of the loop.
> 410 }
> 411
> 8. Condition __k < 623UL /* 624UL - 1 */, taking true branch.
> 412 for (size_t __k = (__n - __m); __k < (__n - 1); ++__k)
> 413 {
> 414 _UIntType __y = ((_M_x[__k] & __upper_mask)
> 415 | (_M_x[__k + 1] & __lower_mask));
> 9. overflow: Add operation overflows on operands __k and
> 18446744073709551389UL.
The operands are unsigned, so cannot overflow.
>
> CID 4797118 (#1-2 of 2): Overflowed array index read (INTEGER_OVERFLOW)
> 10. overflow_sink: Overflowed or truncated value (or a value computed from
> an overflowed or truncated value) __k + 18446744073709551389UL used as array
> index.
> 416 _M_x[__k] = (_M_x[__k + (__m - __n)] ^ (__y >> 1)
The range of values of __k is [n-m, n-1) so the range of indices is
[n-m+m-n, n-1) i.e. [0,n-1) which does not go out of range.
This seems like a Coverity bug.
> 417 ^ ((__y & 0x01) ? __a : 0));
> 418 }
>From gcc-bugs-return-627505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:39:04 2019
Return-Path: <gcc-bugs-return-627505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102583 invoked by alias); 3 Jan 2019 17:39: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 97747 invoked by uid 48); 3 Jan 2019 17:38:59 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88510] GCC generates inefficient U64x2/v2di scalar multiply for NEON32
Date: Thu, 03 Jan 2019 17:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88510-4-9pt2akNCnG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00314.txt.bz2
Content-length: 322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88510
--- Comment #2 from Devin Hussey <husseydevin at gmail dot com> ---
Update: I did the calculations, and twomul has the same cycle count as
goodmul_sse. vmul.i32 with 128-bit operands takes 4 cycles (I assumed it was
two), so just like goodmul_sse, it takes 11 cycles.
>From gcc-bugs-return-627507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:40:48 2019
Return-Path: <gcc-bugs-return-627507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108364 invoked by alias); 3 Jan 2019 17:40: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 108303 invoked by uid 48); 3 Jan 2019 17:40:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88672] friend class template declaration in a class template is ignored
Date: Thu, 03 Jan 2019 17:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88672-4-215fhLFm9Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00316.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Also, https://gcc.gnu.org/bugs very clearly says we need the testcase in
bugzilla, and not just a URL to some other site.
>From gcc-bugs-return-627506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:40:14 2019
Return-Path: <gcc-bugs-return-627506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107355 invoked by alias); 3 Jan 2019 17:40:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107258 invoked by uid 48); 3 Jan 2019 17:40:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88672] friend class template declaration in a class template is ignored
Date: Thu, 03 Jan 2019 17:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88672-4-egB9nthm4E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00315.txt.bz2
Content-length: 201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Please check if this is a duplicate of one of the bugs that PR 59002 depends
on.
>From gcc-bugs-return-627508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 17:52:07 2019
Return-Path: <gcc-bugs-return-627508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34715 invoked by alias); 3 Jan 2019 17:52: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 31269 invoked by uid 55); 3 Jan 2019 17:52:01 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88674] GCC thinks that register is a qualifier in function declaration with no parameters.
Date: Thu, 03 Jan 2019 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88674-4-1UbKf5i7r6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00317.txt.bz2
Content-length: 606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88674
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
"qualified" is used in the informal sense of "any additional specifiers
along with void", not in the sense of "type qualifiers present". The
program is not valid. J.2 explicitly lists "A storage-class specifier or
type qualifier modifies the keyword void as a function parameter type list
(6.7.6.3)." as undefined behavior. (I think this is a case of
undefined-for-lack-of-semantics rather than
normative-text-directly-says-is-undefined.)
>From gcc-bugs-return-627509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:02:21 2019
Return-Path: <gcc-bugs-return-627509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11247 invoked by alias); 3 Jan 2019 18:02: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 11154 invoked by uid 48); 3 Jan 2019 18:02:13 -0000
From: "bugzilla@poradnik-webmastera.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88679] SSE2 intrinsics are available by default on x86
Date: Thu, 03 Jan 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bugzilla@poradnik-webmastera.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-88679-4-mnKy6zKxck@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00318.txt.bz2
Content-length: 10989
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
--- Comment #2 from Daniel Fruzynski <bugzilla@poradnik-webmastera.com> ---
I used compiler at https://godbolt.org/. Here are outputs for both commands:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/opt/compiler-explorer/gcc-snapshot/bin/g++
Target: x86_64-linux-gnu
Configured with: ../gcc-trunk-20190103/configure
--prefix=/opt/compiler-explorer/gcc-build/staging --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu --disable-bootstrap
--enable-multiarch --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --enable-clocale=gnu --enable-languages=c,c++,fortran
--enable-ld=yes --enable-gold=yes --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-linker-build-id --enable-lto
--enable-plugins --enable-threads=posix --with-pkgversion=GCC-Explorer-Build
Thread model: posix
gcc version 9.0.0 20190102 (experimental) (GCC-Explorer-Build)
COLLECT_GCC_OPTIONS='-fdiagnostics-color=always' '-g' '-o'
'/tmp/compiler-explorer-compiler11903-60-1nshruf.qczq/output.s' '-masm=intel'
'-S' '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/x86_64-linux-gnu/9.0.0/cc1plus
-quiet -v -imultiarch x86_64-linux-gnu -iprefix
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/
-D_GNU_SOURCE <source> -quiet -dumpbase example.cpp -masm=intel -mtune=generic
-march=x86-64 -auxbase-strip
/tmp/compiler-explorer-compiler11903-60-1nshruf.qczq/output.s -g -version
-fdiagnostics-color=always -o
/tmp/compiler-explorer-compiler11903-60-1nshruf.qczq/output.s
GNU C++14 (GCC-Explorer-Build) version 9.0.0 20190102 (experimental)
(x86_64-linux-gnu)
compiled by GNU C version 7.3.0, GMP version 6.1.0, MPFR version 3.1.4,
MPC version 1.0.3, isl version isl-0.18-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/include"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/x86_64-linux-gnu"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/backward"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/include"
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/include-fixed"
ignoring nonexistent directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/x86_64-linux-gnu
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/backward
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/include
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/include-fixed
/usr/local/include
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../include
/usr/include/x86_64-linux-gnu
/usr/include
End of search list.
GNU C++14 (GCC-Explorer-Build) version 9.0.0 20190102 (experimental)
(x86_64-linux-gnu)
compiled by GNU C version 7.3.0, GMP version 6.1.0, MPFR version 3.1.4,
MPC version 1.0.3, isl version isl-0.18-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: f724e483fb841047a948ffa41ca3218a
COMPILER_PATH=/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/x86_64-linux-gnu/9.0.0/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/x86_64-linux-gnu/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/bin/
LIBRARY_PATH=/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../lib64/:/lib/x86_64-linux-gnu/:/lib/../lib64/:/usr/lib/x86_64-linux-gnu/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/lib/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-fdiagnostics-color=always' '-g' '-o'
'/tmp/compiler-explorer-compiler11903-60-1nshruf.qczq/output.s' '-masm=intel'
'-S' '-v' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
Compiler returned: 0
-------------------------------------------
$ gcc -v -m32 .... -S
Using built-in specs.
COLLECT_GCC=/opt/compiler-explorer/gcc-snapshot/bin/g++
Target: x86_64-linux-gnu
Configured with: ../gcc-trunk-20190103/configure
--prefix=/opt/compiler-explorer/gcc-build/staging --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu --disable-bootstrap
--enable-multiarch --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --enable-clocale=gnu --enable-languages=c,c++,fortran
--enable-ld=yes --enable-gold=yes --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-linker-build-id --enable-lto
--enable-plugins --enable-threads=posix --with-pkgversion=GCC-Explorer-Build
Thread model: posix
gcc version 9.0.0 20190102 (experimental) (GCC-Explorer-Build)
COLLECT_GCC_OPTIONS='-fdiagnostics-color=always' '-g' '-o'
'/tmp/compiler-explorer-compiler11903-60-7jj20d.uacxt/output.s' '-masm=intel'
'-S' '-v' '-m32' '-S' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/x86_64-linux-gnu/9.0.0/cc1plus
-quiet -v -imultilib 32 -imultiarch i386-linux-gnu -iprefix
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/
-D_GNU_SOURCE <source> -quiet -dumpbase example.cpp -masm=intel -m32
-mtune=generic -march=x86-64 -auxbase-strip
/tmp/compiler-explorer-compiler11903-60-7jj20d.uacxt/output.s -g -version
-fdiagnostics-color=always -o
/tmp/compiler-explorer-compiler11903-60-7jj20d.uacxt/output.s
GNU C++14 (GCC-Explorer-Build) version 9.0.0 20190102 (experimental)
(x86_64-linux-gnu)
compiled by GNU C version 7.3.0, GMP version 6.1.0, MPFR version 3.1.4,
MPC version 1.0.3, isl version isl-0.18-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
ignoring nonexistent directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/include"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/x86_64-linux-gnu/32"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/backward"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/include"
ignoring nonexistent directory "/usr/local/include/i386-linux-gnu"
ignoring duplicate directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/include-fixed"
ignoring nonexistent directory
"/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/include"
ignoring nonexistent directory "/usr/include/i386-linux-gnu"
#include "..." search starts here:
#include <...> search starts here:
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/x86_64-linux-gnu/32
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../include/c++/9.0.0/backward
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/include
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/include-fixed
/usr/local/include
/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/../../include
/usr/include
End of search list.
GNU C++14 (GCC-Explorer-Build) version 9.0.0 20190102 (experimental)
(x86_64-linux-gnu)
compiled by GNU C version 7.3.0, GMP version 6.1.0, MPFR version 3.1.4,
MPC version 1.0.3, isl version isl-0.18-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: f724e483fb841047a948ffa41ca3218a
COMPILER_PATH=/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/x86_64-linux-gnu/9.0.0/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../libexec/gcc/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/bin/
LIBRARY_PATH=/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/32/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../lib32/:/lib/i386-linux-gnu/:/lib/../lib32/:/usr/lib/i386-linux-gnu/:/usr/lib/../lib32/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../../x86_64-linux-gnu/lib/:/opt/compiler-explorer/gcc-trunk-20190103/bin/../lib/gcc/x86_64-linux-gnu/9.0.0/../../../:/lib/i386-linux-gnu/:/lib/:/usr/lib/i386-linux-gnu/:/usr/lib/
COLLECT_GCC_OPTIONS='-fdiagnostics-color=always' '-g' '-o'
'/tmp/compiler-explorer-compiler11903-60-7jj20d.uacxt/output.s' '-masm=intel'
'-S' '-v' '-m32' '-S' '-shared-libgcc' '-mtune=generic' '-march=x86-64'
Compiler returned: 0
>From gcc-bugs-return-627510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:07:09 2019
Return-Path: <gcc-bugs-return-627510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65430 invoked by alias); 3 Jan 2019 18:07:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62312 invoked by uid 48); 3 Jan 2019 18:07:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88680] New: [9 Regression] bogus -Wtype-limits for constant expressions after r267272
Date: Thu, 03 Jan 2019 18:07: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: 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-88680-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00319.txt.bz2
Content-length: 2050
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88680
Bug ID: 88680
Summary: [9 Regression] bogus -Wtype-limits for constant
expressions after r267272
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
-Wtype-limits is documented to
Warn if a comparison is always true or always false due to the limited
range of the data type, but do not warn for constant expressions.
According to the documentation the following test case should be accepted with
no warning, but since r267272 triggers one (Clang does not warn):
$ cat t.C && gcc -S -Wtype-limits t.C
const unsigned n = 8;
static_assert (n >= 0 && n % 2 == 0, "");
t.C:3:18: warning: comparison of unsigned expression >= 0 is always true
[-Wtype-limits]
3 | static_assert (n >= 0 && n % 2 == 0, "");
| ~~^~~~
This change apparently causes a large number of new warnings in Firefox builds.
According to my breakdown of Honza's build here at the following link, there
are over 20 thousand such warnings:
https://hg.mozilla.org/try/rev/e1e0472c3f68e47b9741d7814ef4417759cde24c
Diagnostic Count Unique Files
-Wtype-limits 20882 10441 604
-Wmultistatement-macros 1552 5 2
-Wcoverage-mismatch 793 225 141
-Wclass-memaccess 346 72 46
-Wsign-compare 292 127 55
-Wnarrowing 272 2 1
-Wmissing-profile 245 212 207
-Wattributes 212 1 1
-Wint-in-bool-context 140 3 2
-Wdeprecated-copy 104 22 10
-Wmaybe-uninitialized 103 67 54
>From gcc-bugs-return-627511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:10:08 2019
Return-Path: <gcc-bugs-return-627511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63696 invoked by alias); 3 Jan 2019 18:10:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63628 invoked by uid 48); 3 Jan 2019 18:10:03 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88679] SSE2 intrinsics are available by default on x86
Date: Thu, 03 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools 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-88679-4-9UZ6lalACx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00320.txt.bz2
Content-length: 303
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
Your GCC is configured -m32 ISA to x86-64 ISA by default. To default -m32 ISA
to i686 ISA, please configure your GCC with --with-arch_32=i686. Or you can
use
"-march=i686 -m32".
>From gcc-bugs-return-627512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:21:54 2019
Return-Path: <gcc-bugs-return-627512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113296 invoked by alias); 3 Jan 2019 18:21: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 113203 invoked by uid 48); 3 Jan 2019 18:21:49 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88343-4-1pauDnKFqi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00321.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #17 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Created attachment 45328
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45328&action=edit
Preprocessed source
Replacing s_nextafterf.os built with trunk with that patch reverted, by the
same file as built with trunk without the reversion, is sufficient to produce a
glibc binary showing the problem. Preprocessed sources attached. Given the
--with-float=soft compiler, compile with: -std=gnu11 -fgnu89-inline -g -O2
-fmerge-all-constants -frounding-math -fno-stack-protector -fno-math-errno
-mlong-double-128 -fpic s_nextafterf.i.
>From gcc-bugs-return-627513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:22:29 2019
Return-Path: <gcc-bugs-return-627513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117346 invoked by alias); 3 Jan 2019 18:22:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114507 invoked by uid 48); 3 Jan 2019 18:22:24 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 18:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88343-4-4FMrVXNXlQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00322.txt.bz2
Content-length: 266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #18 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Created attachment 45329
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45329&action=edit
Good assembly (with the GCC patch reverted)
>From gcc-bugs-return-627514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:23:21 2019
Return-Path: <gcc-bugs-return-627514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121720 invoked by alias); 3 Jan 2019 18:23: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 121638 invoked by uid 48); 3 Jan 2019 18:23:16 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 18:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88343-4-z6fzm1cdNO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00323.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #19 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Created attachment 45330
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45330&action=edit
Bad assembly (from trunk r267560 with the patch still present)
>From gcc-bugs-return-627515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:25:55 2019
Return-Path: <gcc-bugs-return-627515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17133 invoked by alias); 3 Jan 2019 18:25: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 17083 invoked by uid 48); 3 Jan 2019 18:25:50 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88679] SSE2 intrinsics are available by default on x86
Date: Thu, 03 Jan 2019 18:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88679-4-KZsVFAWfPc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88679-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00324.txt.bz2
Content-length: 348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88679
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-627517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:29:54 2019
Return-Path: <gcc-bugs-return-627517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21551 invoked by alias); 3 Jan 2019 18:29: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 20868 invoked by uid 48); 3 Jan 2019 18:29:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88620] [7/8/9 Regression] ICE in assign_stack_temp_for_type, at function.c:837
Date: Thu, 03 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88620-4-UltDqGuXce@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00326.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
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 #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45331
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45331&action=edit
gcc9-pr88620.patch
Untested fix.
>From gcc-bugs-return-627516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:29:46 2019
Return-Path: <gcc-bugs-return-627516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20833 invoked by alias); 3 Jan 2019 18:29:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20782 invoked by uid 48); 3 Jan 2019 18:29:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88681] New: Missing symbol exports in libstdc++.so
Date: Thu, 03 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00325.txt.bz2
Content-length: 2558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
Bug ID: 88681
Summary: Missing symbol exports in libstdc++.so
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
The following fails to link:
#define _GLIBCXX_USE_CXX11_ABI 0
#include <locale>
#include <sstream>
#include <string>
template<typename C>
void test_time_get()
{
using namespace std;
locale loc_c = locale::classic();
basic_istringstream<C> iss;
iss.imbue(loc_c);
const time_get<C>& tget = use_facet<time_get<C>>(iss.getloc());
typedef istreambuf_iterator<C> iter;
const iter end;
tm time;
ios_base::iostate err = ios_base::badbit;
tget.get(iter(iss), end, iss, err, &time, 'Y');
}
std::string s = "C";
template<typename C>
struct facet : std::collate_byname<C>
{
facet() : std::collate_byname<C>(s) { }
};
template<typename C>
void
test_collate_byname()
{
facet<C> c;
}
int main()
{
test_time_get<char>();
test_time_get<wchar_t>();
test_collate_byname<char>();
test_collate_byname<wchar_t>();
}
The errors are:
/usr/bin/ld: /tmp/ccHErRY2.o: in function `void test_time_get<char>()':
/tmp/missing.cc:22: undefined reference to `std::time_get<char,
std::istreambuf_iterator<char, std::char_traits<char> >
>::get(std::istreambuf_iterator<char, std::char_traits<char> >,
std::istreambuf_iterator<char, std::char_traits<char> >, std::ios_base&,
std::_Ios_Iostate&, tm*, char, char) const'
/usr/bin/ld: /tmp/ccHErRY2.o: in function `void test_time_get<wchar_t>()':
/tmp/missing.cc:22: undefined reference to `std::time_get<wchar_t,
std::istreambuf_iterator<wchar_t, std::char_traits<wchar_t> >
>::get(std::istreambuf_iterator<wchar_t, std::char_traits<wchar_t> >,
std::istreambuf_iterator<wchar_t, std::char_traits<wchar_t> >, std::ios_base&,
std::_Ios_Iostate&, tm*, char, char) const'
/usr/bin/ld: /tmp/ccHErRY2.o: in function `facet<char>::facet()':
/tmp/missing.cc:30: undefined reference to
`std::collate_byname<char>::collate_byname(std::string const&, unsigned long)'
/usr/bin/ld: /tmp/ccHErRY2.o: in function `facet<wchar_t>::facet()':
/tmp/missing.cc:30: undefined reference to
`std::collate_byname<wchar_t>::collate_byname(std::string const&, unsigned
long)'
collect2: error: ld returned 1 exit status
The exports have been missing since these symbols were added for GCC 5.1
>From gcc-bugs-return-627518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:30:34 2019
Return-Path: <gcc-bugs-return-627518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22925 invoked by alias); 3 Jan 2019 18:30: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 22362 invoked by uid 48); 3 Jan 2019 18:30:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88681] Missing symbol exports in libstdc++.so
Date: Thu, 03 Jan 2019 18: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88681-4-1wGYKAgdLD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00327.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-03
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-627519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:31:11 2019
Return-Path: <gcc-bugs-return-627519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99854 invoked by alias); 3 Jan 2019 18:31:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60524 invoked by uid 48); 3 Jan 2019 18:30:54 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88681] Missing symbol exports in libstdc++.so
Date: Thu, 03 Jan 2019 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88681-4-fQAVqfQ19w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00328.txt.bz2
Content-length: 211
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
N.B. When optimization is enabled the functions are inlined, so the exports
aren't needed.
>From gcc-bugs-return-627520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:39:10 2019
Return-Path: <gcc-bugs-return-627520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34035 invoked by alias); 3 Jan 2019 18:39:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33955 invoked by uid 48); 3 Jan 2019 18:39:05 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Thu, 03 Jan 2019 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
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:
Message-ID: <bug-88678-4-4k5GXTUCPQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00329.txt.bz2
Content-length: 894
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #2 from seurer at gcc dot gnu.org ---
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic
operation.
Backtrace for this error:
#0 0x3fffb17f0477 in ???
#1 0x3fffb14f1694 in feenableexcept
at ../sysdeps/powerpc/fpu/feenablxcpt.c:44
#2 0x3fffb1765e73 in __ieee_exceptions_MOD_ieee_support_halting
at /home/seurer/gcc/gcc-test2/libgfortran/ieee/ieee_exceptions.F90:193
#3 0x3fffb176590f in __ieee_arithmetic_MOD_ieee_value_4
at /home/seurer/gcc/gcc-test2/libgfortran/ieee/ieee_arithmetic.F90:972
#4 0x10000aa7 in foo
at
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/ieee/ieee_10.f90:12
#5 0x10000aa7 in main
at
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/ieee/ieee_10.f90:5
FAIL: gfortran.dg/ieee/ieee_10.f90 -O3 -g execution test
>From gcc-bugs-return-627521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 18:46:00 2019
Return-Path: <gcc-bugs-return-627521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130350 invoked by alias); 3 Jan 2019 18:46:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130231 invoked by uid 48); 3 Jan 2019 18:45:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88616] [9 Regression] ICE in gimplify_expr at gcc/gimplify.c:13363
Date: Thu, 03 Jan 2019 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88616-4-XgGQurOKQW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00330.txt.bz2
Content-length: 699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88616
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aoliva at gcc dot gnu.org,
| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01750.html patch doesn't
solve this, and neither does
https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01749.html, nevertheless it looks
related to the arm weirdness of returning this from cdtors.
>From gcc-bugs-return-627522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 19:26:28 2019
Return-Path: <gcc-bugs-return-627522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31337 invoked by alias); 3 Jan 2019 19:26: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 30955 invoked by uid 48); 3 Jan 2019 19:26:23 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88343] [7/8 Regression] R31 is unconditionally saved/restored on powerpc-darwin even when it's not necessary.
Date: Thu, 03 Jan 2019 19: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: iains at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88343-4-8ik1437wxi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00331.txt.bz2
Content-length: 593
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88343
--- Comment #20 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Joseph S. Myers from comment #19)
> Created attachment 45330 [details]
> Bad assembly (from trunk r267560 with the patch still present)
Thanks, Joseph, that's very helpful.
.. so the code plainly uses pic base reg /_GLOBAL_OFFSET_TABLE_
and thus fails when it's not saved...
.. the question to be addressed then is why crtl->uses_pic_offset_table not set
in this case?
(a question which perhaps has wider implications than this missed
optimisation).
>From gcc-bugs-return-627523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 19:29:06 2019
Return-Path: <gcc-bugs-return-627523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87447 invoked by alias); 3 Jan 2019 19:29:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87277 invoked by uid 48); 3 Jan 2019 19:29:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88594] [9 Regression] ICE in int_mode_for_mode, at stor-layout.c:403
Date: Thu, 03 Jan 2019 19:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component assigned_to everconfirmed
Message-ID: <bug-88594-4-KU6gDiqzFb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00332.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88594
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-03
CC| |jakub at gcc dot gnu.org
Component|tree-optimization |target
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-627524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 19:34:03 2019
Return-Path: <gcc-bugs-return-627524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94319 invoked by alias); 3 Jan 2019 19:34: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 94163 invoked by uid 48); 3 Jan 2019 19:33:57 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Thu, 03 Jan 2019 19:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-cwvrI3Fi9o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00333.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #5 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #4)
> Yes, the extension should be zero-extend, not sign extend. The plus
> operation is correct, however, since decrementing the first operand could
> lead to underflow if it was zero. So the correct rtl would be
>
> (compare ((zero_x(a)) (plus (zero_x(b) (ltu(cc, 0)))))
> (minus (...))
Agreed. The issue is more widespread though, signed underflow doesn't work
either,
and subv<mode>4 simply uses gen_sub<mode>3_compare1 which does do a normal
compare, so the RTL does not compute the overflow flag eventhough the actual
compare does.
It seems like a bug when it does constant fold this RTL given it should have
been folded before expand. Using UNSPEC for these complex flag uses may be best
to be safe.
>From gcc-bugs-return-627525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 19:43:03 2019
Return-Path: <gcc-bugs-return-627525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102893 invoked by alias); 3 Jan 2019 19:43: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 102757 invoked by uid 55); 3 Jan 2019 19:42:58 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Thu, 03 Jan 2019 19:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88678-4-WgO17mQUTK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00334.txt.bz2
Content-length: 1903
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Jan 03, 2019 at 06:39:05PM +0000, seurer at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
>
> --- Comment #2 from seurer at gcc dot gnu.org ---
> Program received signal SIGFPE: Floating-point exception - erroneous arithmetic
> operation.
>
> Backtrace for this error:
> #0 0x3fffb17f0477 in ???
> #1 0x3fffb14f1694 in feenableexcept
> at ../sysdeps/powerpc/fpu/feenablxcpt.c:44
> #2 0x3fffb1765e73 in __ieee_exceptions_MOD_ieee_support_halting
> at /home/seurer/gcc/gcc-test2/libgfortran/ieee/ieee_exceptions.F90:193
> #3 0x3fffb176590f in __ieee_arithmetic_MOD_ieee_value_4
> at /home/seurer/gcc/gcc-test2/libgfortran/ieee/ieee_arithmetic.F90:972
> #4 0x10000aa7 in foo
> at
> /home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/ieee/ieee_10.f90:12
> #5 0x10000aa7 in main
> at
> /home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/ieee/ieee_10.f90:5
> FAIL: gfortran.dg/ieee/ieee_10.f90 -O3 -g execution test
>
Thanks for the backtrace. Frame #1 suggests that this is a
glibc issue. gfortran will translate ieee_support_halting into
_gfortrani_support_fpu_trap.
% nm ieee_exceptions.o | grep _trap
U _gfortrani_get_fpu_trap_exceptions
U _gfortrani_set_fpu_trap_exceptions
U _gfortrani_support_fpu_trap
% nm fpu.o | grep _trap
0000000000000000 T _gfortrani_get_fpu_trap_exceptions
0000000000000000 T _gfortrani_set_fpu_trap_exceptions
0000000000000000 T _gfortrani_support_fpu_trap
The code in libgfortran/runtime/fpu.c appears to pull in architecture
dependent code via
/* We include the platform-dependent code. */
#include "fpu-target.h"
I don't know where or how powerpc64 sets up fpu-target.h.
>From gcc-bugs-return-627526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:16:08 2019
Return-Path: <gcc-bugs-return-627526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5769 invoked by alias); 3 Jan 2019 20:16: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 5666 invoked by uid 48); 3 Jan 2019 20:16:00 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88682] New: new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Thu, 03 Jan 2019 20:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00335.txt.bz2
Content-length: 1016
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
Bug ID: 88682
Summary: new test case c-c++-common/pr51628-10.c fails starting
with its introduction in r267313
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: ---
make -k check-gcc RUNTESTFLAGS=dg.exp=c-c++-common/pr51628-10.c
FAIL: c-c++-common/pr51628-10.c -Wc++-compat execution test
FAIL: c-c++-common/pr51628-10.c -std=gnu++98 execution test
FAIL: c-c++-common/pr51628-10.c -std=gnu++14 execution test
FAIL: c-c++-common/pr51628-10.c -std=gnu++17 execution test
# of expected passes 1
# of expected passes 3
# of unexpected failures 1
# of unexpected failures 3
The test case is exiting with a non-zero return code when it fails.
>From gcc-bugs-return-627527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:21:56 2019
Return-Path: <gcc-bugs-return-627527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12523 invoked by alias); 3 Jan 2019 20:21:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12435 invoked by uid 48); 3 Jan 2019 20:21:52 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Thu, 03 Jan 2019 20: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: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88682-4-PNER1I7VDC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00336.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
It looks like that powerpc64 failed to properly handle packed __int128_t.
>From gcc-bugs-return-627528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:26:04 2019
Return-Path: <gcc-bugs-return-627528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18976 invoked by alias); 3 Jan 2019 20:26: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 18831 invoked by uid 48); 3 Jan 2019 20:25:55 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Thu, 03 Jan 2019 20: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc component
Message-ID: <bug-88682-4-nNototNIMf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00337.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
Component|testsuite |target
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
aarch64 may have the same issue.
>From gcc-bugs-return-627529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:34:52 2019
Return-Path: <gcc-bugs-return-627529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39505 invoked by alias); 3 Jan 2019 20:34: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 39431 invoked by uid 48); 3 Jan 2019 20:34:46 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88674] GCC thinks that register is a qualifier in function declaration with no parameters.
Date: Thu, 03 Jan 2019 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88674-4-yOJCwgiY4X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88674-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88674-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00338.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88674
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Thanks for the explanation.
>From gcc-bugs-return-627531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:38:48 2019
Return-Path: <gcc-bugs-return-627531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47447 invoked by alias); 3 Jan 2019 20:38:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47020 invoked by uid 55); 3 Jan 2019 20:38:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88607] forward_list.h contains utf-8 charactor
Date: Thu, 03 Jan 2019 20:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88607-4-CXtzJZRqjd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00340.txt.bz2
Content-length: 1834
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88607
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Jan 3 20:38:11 2019
New Revision: 267564
URL: https://gcc.gnu.org/viewcvs?rev=267564&root=gcc&view=rev
Log:
PR libstdc++/88607 replace or remove unnecessary UTF-8 characters
There are a number of UTF-8 characters in comments which add no value
and can be replaced with ASCII equivalents, or removed entirely for the
section sign (U+00A7).
PR libstdc++/88607
* include/bits/forward_list.h: Replace UTF-8 "ligature fi" character.
* include/debug/forward_list: Likewise.
* include/experimental/bits/shared_ptr.h: Remove UTF-8 "section sign"
character.
* include/experimental/chrono: Likewise.
* include/experimental/functional: Likewise.
* include/experimental/ratio: Likewise.
* include/experimental/system_error: Likewise.
* include/experimental/tuple: Likewise.
* include/experimental/type_traits: Likewise.
* include/parallel/workstealing.h: Replace UTF-8 "en dash" character.
* include/parallel/multiseq_selection.h: Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/forward_list.h
trunk/libstdc++-v3/include/debug/forward_list
trunk/libstdc++-v3/include/experimental/bits/shared_ptr.h
trunk/libstdc++-v3/include/experimental/chrono
trunk/libstdc++-v3/include/experimental/functional
trunk/libstdc++-v3/include/experimental/ratio
trunk/libstdc++-v3/include/experimental/system_error
trunk/libstdc++-v3/include/experimental/tuple
trunk/libstdc++-v3/include/experimental/type_traits
trunk/libstdc++-v3/include/parallel/multiseq_selection.h
trunk/libstdc++-v3/include/parallel/workstealing.h
>From gcc-bugs-return-627530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:38:44 2019
Return-Path: <gcc-bugs-return-627530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47082 invoked by alias); 3 Jan 2019 20:38:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46917 invoked by uid 55); 3 Jan 2019 20:38:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88681] Missing symbol exports in libstdc++.so
Date: Thu, 03 Jan 2019 20:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88681-4-Mz2O8IZhZu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00339.txt.bz2
Content-length: 1034
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Jan 3 20:38:04 2019
New Revision: 267563
URL: https://gcc.gnu.org/viewcvs?rev=267563&root=gcc&view=rev
Log:
PR libstdc++/88681 export missing symbols
These new facet functions were added to GCC 5.1 but the versions for the
old std::string ABI were never exported from the shared library.
PR libstdc++/88681
* config/abi/pre/gnu.ver: Add missing exports.
* testsuite/22_locale/collate_byname/88681.cc: New test.
* testsuite/22_locale/time_get/get/char/88681.cc: New test.
* testsuite/22_locale/time_get/get/wchar_t/88681.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/22_locale/collate_byname/88681.cc
trunk/libstdc++-v3/testsuite/22_locale/time_get/get/char/88681.cc
trunk/libstdc++-v3/testsuite/22_locale/time_get/get/wchar_t/88681.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/config/abi/pre/gnu.ver
>From gcc-bugs-return-627532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:39:09 2019
Return-Path: <gcc-bugs-return-627532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49814 invoked by alias); 3 Jan 2019 20:39:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49158 invoked by uid 48); 3 Jan 2019 20:39:03 -0000
From: "damian.jarek93 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88672] friend class template declaration in a class template is ignored
Date: Thu, 03 Jan 2019 20:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: damian.jarek93 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 resolution
Message-ID: <bug-88672-4-CBGzTKNiNC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00341.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
Damian Jarek <damian.jarek93 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Damian Jarek <damian.jarek93 at gmail dot com> ---
Looks like it's a duplicate of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82613
*** This bug has been marked as a duplicate of bug 82613 ***
>From gcc-bugs-return-627533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:39:10 2019
Return-Path: <gcc-bugs-return-627533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50025 invoked by alias); 3 Jan 2019 20:39:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49296 invoked by uid 48); 3 Jan 2019 20:39:04 -0000
From: "damian.jarek93 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82613] Cannot access private definitions in base clause of friend class template
Date: Thu, 03 Jan 2019 20:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: damian.jarek93 at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82613-4-JiViPs5bYf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00342.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82613
Damian Jarek <damian.jarek93 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |damian.jarek93 at gmail dot com
--- Comment #2 from Damian Jarek <damian.jarek93 at gmail dot com> ---
*** Bug 88672 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:44:13 2019
Return-Path: <gcc-bugs-return-627534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103390 invoked by alias); 3 Jan 2019 20:44:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103336 invoked by uid 48); 3 Jan 2019 20:44:09 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88680] [9 Regression] bogus -Wtype-limits for constant expressions after r267272
Date: Thu, 03 Jan 2019 20:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88680-4-PHQOpXCymH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88680-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88680-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00343.txt.bz2
Content-length: 602
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88680
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-03
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks. Confirmed; am investigating.
>From gcc-bugs-return-627535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 20:49:38 2019
Return-Path: <gcc-bugs-return-627535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107995 invoked by alias); 3 Jan 2019 20:49: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 107929 invoked by uid 48); 3 Jan 2019 20:49:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88607] forward_list.h contains utf-8 charactor
Date: Thu, 03 Jan 2019 20:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88607-4-8Z69GpwZzk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00344.txt.bz2
Content-length: 678
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88607
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
Ever confirmed|0 |1
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Partially fixed. I should have looked at Jakub's patch first, as I missed a
few. I'll address that shortly.
I'm not sure about replacing the accented characters in Hervé Brönnimann's name
though.
>From gcc-bugs-return-627536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 21:19:22 2019
Return-Path: <gcc-bugs-return-627536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28687 invoked by alias); 3 Jan 2019 21:19: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 28559 invoked by uid 48); 3 Jan 2019 21:19:18 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Thu, 03 Jan 2019 21:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget
Message-ID: <bug-88682-4-T1na0VWgkO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00345.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64*-unknown-linux-gn |powerpc64*-unknown-linux-gn
|u |u aarch64
--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Indeed, the test also fails on aarch64-linux-gnu
>From gcc-bugs-return-627537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 21:20:45 2019
Return-Path: <gcc-bugs-return-627537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36446 invoked by alias); 3 Jan 2019 21:20: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 36336 invoked by uid 48); 3 Jan 2019 21:20:41 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45424] [F08] Add IS_CONTIGUOUS intrinsic
Date: Thu, 03 Jan 2019 21:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx 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: attachments.isobsolete attachments.created
Message-ID: <bug-45424-4-fjdeekw84Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00346.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45322|0 |1
is obsolete| |
--- Comment #8 from Harald Anlauf <anlauf at gmx dot de> ---
Created attachment 45332
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45332&action=edit
Corrected update of Tobias' patch to 9-trunk (except for ChangeLog)
This version corrects the previous attempt which broke the original patch.
It comes with an additional testcase that checks assumed rank/assumed type.
>From gcc-bugs-return-627538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 21:53:53 2019
Return-Path: <gcc-bugs-return-627538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68228 invoked by alias); 3 Jan 2019 21:53: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 68185 invoked by uid 48); 3 Jan 2019 21:53:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88672] friend class template declaration in a class template is ignored
Date: Thu, 03 Jan 2019 21:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88672-4-7vZgWr4081@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88672-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00347.txt.bz2
Content-length: 128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88672
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Thanks!
>From gcc-bugs-return-627539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:00:52 2019
Return-Path: <gcc-bugs-return-627539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116488 invoked by alias); 3 Jan 2019 22:00: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 116453 invoked by uid 48); 3 Jan 2019 22:00:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88681] Missing symbol exports in libstdc++.so
Date: Thu, 03 Jan 2019 22:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 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: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-88681-4-ft0HzSPxL5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88681-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00348.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88681
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-627540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:08:31 2019
Return-Path: <gcc-bugs-return-627540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42115 invoked by alias); 3 Jan 2019 22:08:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41996 invoked by uid 55); 3 Jan 2019 22:08:25 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88607] forward_list.h contains utf-8 charactor
Date: Thu, 03 Jan 2019 22:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88607-4-guhqU8aCS8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00349.txt.bz2
Content-length: 712
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88607
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Jan 3 22:07:52 2019
New Revision: 267565
URL: https://gcc.gnu.org/viewcvs?rev=267565&root=gcc&view=rev
Log:
PR libstdc++/88607 replace some more UTF-8 characters
2019-01-03 Jonathan Wakely <jwakely@redhat.com>
Jakub Jelinek <jakub@redhat.com>
PR libstdc++/88607
* include/experimental/memory: Replace UTF-8 quote characters.
* include/std/future: Replace UTF-8 "em dash" characters.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/experimental/memory
trunk/libstdc++-v3/include/std/future
>From gcc-bugs-return-627541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:15:54 2019
Return-Path: <gcc-bugs-return-627541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54958 invoked by alias); 3 Jan 2019 22:15:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54641 invoked by uid 48); 3 Jan 2019 22:15:34 -0000
From: "mjansche at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88683] New: nan <= inf not accepted as constant expression
Date: Thu, 03 Jan 2019 22: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mjansche at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00350.txt.bz2
Content-length: 2707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88683
Bug ID: 88683
Summary: nan <= inf not accepted as constant expression
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mjansche at google dot com
Target Milestone: ---
I am observing a regression between g++-7.4.0 and g++-8.2.0 when compiling the
following code:
#include <iostream>
#include <limits>
int main() {
constexpr double nan = std::numeric_limits<double>::quiet_NaN();
constexpr double inf = std::numeric_limits<double>::infinity();
constexpr bool inf_ge_nan = inf >= nan; // accepted
std::cout << inf_ge_nan << std::endl;
constexpr bool nan_le_inf = nan <= inf; // rejected: not a constant
expression
std::cout << nan_le_inf << std::endl;
return 0;
}
I have read section 5.19 [expr.const] of the C++11 standard a few times and
don't see why the expression (nan <= inf) wouldn't be a constant expression in
the above code.
This is especially puzzling as (inf >= nan) is considered a constant expression
yet (nan <= inf) is not. At a minimum I would expect (inf >= nan) to be a
constant expression iff (nan <= inf) is.
I wouldn't make too much of the observation that this is a regression between
7.4.0 and 8.2.0: I've seen similar issues in g++-7.3.0, but haven't been able
to reproduce them in isolation.
Details:
$ /usr/local/stow/gcc-7.4.0/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/usr/local/stow/gcc-7.4.0/bin/g++
COLLECT_LTO_WRAPPER=/usr/local/stow/gcc-7.4.0/libexec/gcc/x86_64-pc-linux-gnu/7.4.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-7.4.0/configure --prefix=/usr/local/stow/gcc-7.4.0
Thread model: posix
gcc version 7.4.0 (GCC)
$ /usr/local/stow/gcc-8.2.0/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/usr/local/stow/gcc-8.2.0/bin/g++
COLLECT_LTO_WRAPPER=/usr/local/stow/gcc-8.2.0/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-8.2.0/configure --prefix=/usr/local/stow/gcc-8.2.0
Thread model: posix
gcc version 8.2.0 (GCC)
$ /usr/local/stow/gcc-7.4.0/bin/g++ -std=c++11 -Wall -Wextra nan_le_inf.cc
$ /usr/local/stow/gcc-8.2.0/bin/g++ -std=c++11 -Wall -Wextra nan_le_inf.cc
nan_le_inf.cc: In function ‘int main()’:
nan_le_inf.cc:8:35: error: ‘(+QNaN <= +Inf)’ is not a constant expression
constexpr bool nan_le_inf = nan <= inf; // rejected: not a constant
expression
~~~~^~~~~~
>From gcc-bugs-return-627542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:44:01 2019
Return-Path: <gcc-bugs-return-627542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1757 invoked by alias); 3 Jan 2019 22:44: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 130454 invoked by uid 48); 3 Jan 2019 22:43:56 -0000
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] New: Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Thu, 03 Jan 2019 22:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rafael at espindo dot la
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00351.txt.bz2
Content-length: 1587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Bug ID: 88684
Summary: Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime
flag (or always true)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: rafael at espindo dot la
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Even on ABIs that normally unique typeinfo names, it is easy to end up in
situations where that fails.
Consider a shared library implemented with
lib.hh:
struct foo {
virtual ~foo(){}
};
struct bar : public foo {
virtual void zed();
};
lib.cc:
#include "lib.hh"
void bar::zed() {}
and being used by the program (could be another library):
test.cc:
#include "lib.hh"
int main(int argc, char** argv) { bar t; }
if the program is compiled with -fvisibility=hidden, it will have a hidden
_ZTI3foo which isDerivedFromAtOffset will think doesn't match the _ZTI3foo in
the library.
The above test is a reduction of
#include <boost/test/unit_test.hpp>
int main(int argc, char **argv) {
return 0;
}
compiled with -fvisibility=hidden, which complains that
/usr/include/boost/test/unit_test_log.hpp:112:23: runtime error: member call on
address 0x000006583060 which does not point to an object of type
'test_observer'
>From gcc-bugs-return-627543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:52:44 2019
Return-Path: <gcc-bugs-return-627543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127431 invoked by alias); 3 Jan 2019 22:52:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126761 invoked by uid 48); 3 Jan 2019 22:52:39 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88683] nan <= inf not accepted as constant expression
Date: Thu, 03 Jan 2019 22:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.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-88683-4-ocadao6rW5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00352.txt.bz2
Content-length: 135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88683
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
DUP of PR 88173?
>From gcc-bugs-return-627544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:53:18 2019
Return-Path: <gcc-bugs-return-627544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129039 invoked by alias); 3 Jan 2019 22:53:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128968 invoked by uid 48); 3 Jan 2019 22:53:12 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88170] [9 Regression] pretty printer FAILs
Date: Thu, 03 Jan 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88170-4-io2eoTq9MZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88170-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88170-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00353.txt.bz2
Content-length: 671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88170
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wjwray at gmail dot com
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This was caused by the patch for PR 87364 (r265077 and r265078). Presumably GDB
can no longer recognise the RTTI for shared_ptr because the demangled name no
longer looks like (__gnu_cxx::_Lock_policy)2.
The patch breaks existing functionality. Looks like it was not sufficiently
tested.
>From gcc-bugs-return-627545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:53:44 2019
Return-Path: <gcc-bugs-return-627545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 511 invoked by alias); 3 Jan 2019 22:53:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 436 invoked by uid 48); 3 Jan 2019 22:53:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87364] Pretty print of enumerator never prints the id, always falls back to C-style cast output
Date: Thu, 03 Jan 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87364-4-PPP04P3raS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00354.txt.bz2
Content-length: 142
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87364
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This caused PR 88170
>From gcc-bugs-return-627546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:56:50 2019
Return-Path: <gcc-bugs-return-627546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5381 invoked by alias); 3 Jan 2019 22:56: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 5304 invoked by uid 48); 3 Jan 2019 22:56:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88170] [9 Regression] pretty printer FAILs
Date: Thu, 03 Jan 2019 22:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88170-4-s5paN8pp2g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88170-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88170-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00355.txt.bz2
Content-length: 232
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88170
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Looks like these warnings were mentioned in PR 87634 comment 4, but nobody
noticed the resulting test failures.
>From gcc-bugs-return-627547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 22:58:20 2019
Return-Path: <gcc-bugs-return-627547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7009 invoked by alias); 3 Jan 2019 22:58:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6911 invoked by uid 48); 3 Jan 2019 22:58:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87364] Pretty print of enumerator never prints the id, always falls back to C-style cast output
Date: Thu, 03 Jan 2019 22: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.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87364-4-W0Cm0lz0Zk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00356.txt.bz2
Content-length: 878
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87364
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Will Wray from comment #4)
> Thanks Martin,
>
> I investigated enum template args with GCC bug 81932 test code,
> repeating its GDB Python-debug-print test case for enum args.
>
> Conclusion:
> This change to enum printing does not cause GDB to fail to look up
> non-type template specializations for enum type arguments;
> the lookup succeeds and there's no missing-type Python Exception.
>
> However, GDB still produces a warning for an RTTI lookup failure.
> The warning is not serious; the type must be found some other way.
But it does cause test failures, which should have been addressed as part of
the patch.
It doesn't just affect our testsuite, since the pretty printers for
std::shared_ptr now print these noisy warnings.
>From gcc-bugs-return-627548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 23:27:25 2019
Return-Path: <gcc-bugs-return-627548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112936 invoked by alias); 3 Jan 2019 23:27: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 106655 invoked by uid 48); 3 Jan 2019 23:27:20 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87364] Pretty print of enumerator never prints the id, always falls back to C-style cast output
Date: Thu, 03 Jan 2019 23:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87364-4-q2jOUHWp3i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00357.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87364
--- Comment #12 from Will Wray <wjwray at gmail dot com> ---
I can take a look at the weekend or early next week -
reproduce the test fails and diagnose some more.
I'll try to find answers to the questions I raised in comment #4
(about name mangling of enum types) and see how Clang deals with it.
>From gcc-bugs-return-627549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 23:54:01 2019
Return-Path: <gcc-bugs-return-627549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42453 invoked by alias); 3 Jan 2019 23:54: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 42357 invoked by uid 48); 3 Jan 2019 23:53:56 -0000
From: "antony at cosmologist dot info" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88685] New: 8/9 regression] pointer class array argument indexing
Date: Thu, 03 Jan 2019 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antony at cosmologist dot info
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00358.txt.bz2
Content-length: 1567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
Bug ID: 88685
Summary: 8/9 regression] pointer class array argument indexing
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: antony at cosmologist dot info
Target Milestone: ---
Created attachment 45333
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45333&action=edit
Test case
This code works in 7.3.1, but gives wrong answers in 8.3.1 and trunk (outputs
should all be the same, but are not):
program tester
implicit none
Type TArr
integer, allocatable :: CL(:)
end Type TArr
type(TArr), allocatable, target :: arr(:,:)
class(TArr), pointer:: Cls(:,:)
integer i
allocate(arr(1,1))
allocate(arr(1,1)%CL(3))
arr(1,1)%CL=-1
cls => arr
call doit(cls)
contains
subroutine doit(cls)
class(TArr), pointer :: Cls(:,:)
cls(1,1)%CL(:) = 1
print *, 'CL = ', Cls(1,1)%CL
print *, 'CL(i)= ', Cls(1,1)%CL(1),Cls(1,1)%CL(2),Cls(1,1)%CL(3)
end subroutine doit
end program tester
A longer variation is attached that's closer to real case where I found it. It
can give rise to very hard-to-trace bugs, in my full real-world code it showed
up as a mysterious seg fault in random places.
Looks similar to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87336, but is not
fixed in nightly build.
>From gcc-bugs-return-627550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 03 23:59:17 2019
Return-Path: <gcc-bugs-return-627550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46181 invoked by alias); 3 Jan 2019 23:59: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 46130 invoked by uid 48); 3 Jan 2019 23:59:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82521] [7/8/9 Regression] No -Wtype-limits warning when using templates
Date: Thu, 03 Jan 2019 23: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: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-82521-4-yH28B1pEMV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00359.txt.bz2
Content-length: 2599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82521
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-03
CC| |manu at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
Summary|No -Wtype-limits warning |[7/8/9 Regression] No
|when using templates |-Wtype-limits warning when
| |using templates
Ever confirmed|0 |1
Known to fail| |5.4.0, 6.3.0, 7.3.0, 8.2.0,
| |9.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
[Please include the full test case and GCC output in bug reports.]
Confirmed as a GCC 4.8 regression. GCC 4.7 issues -Wtype-limits for templates.
Bisection points to a revision in the range 124827 and 124899. I don't have
GCC binaries for all the revisions in the range but the likely culprit seems to
be r124856. I CC Manu for his thoughts.
2007-05-19 Manuel Lopez-Ibanez <manu@gcc.gnu.org>
* doc/invoke.texi (Warning Options): Add -Wconversion-sign.
(Wconversion): Update description.
(Wconversion-sign): New.
* c.opt (Wconversion-sign): New.
* c-opts.c (c_common_post_options): Uninitialized Wconversion-sign
means disabled for C++. Otherwise, take the status of Wconversion.
* c-common.c (conversion_warning): Warn with either Wconversion or
Wconversion-sign.
(warnings_for_convert_and_check): Conditions are already checked by
conversion_warning.
(convert_and_check): Don't check warnings if the conversion failed.
cp/
* cvt.c (cp_convert_and_check): Don't check warnings if the
conversion failed.
A simple test case and GCC output at r124825:
$ cat t.C && /opt/notnfs/gcc-bisect/obj/gcc/cc1plus.124825 -quiet -Wall -Werror
-o/dev/null t.C
template <typename T>
const char* f (T value)
{
return value == 12345U ? "-1" : "no";
}
const char *s = f<unsigned char>(0);
cc1plus.124825: warnings being treated as errors
t.C: In function ‘const char* f(T) [with T = unsigned char]’:
t.C:7: instantiated from here
t.C:4: error: comparison is always false due to limited range of data type
>From gcc-bugs-return-627551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:00:51 2019
Return-Path: <gcc-bugs-return-627551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48188 invoked by alias); 4 Jan 2019 00:00:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47976 invoked by uid 48); 4 Jan 2019 00:00:39 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82924] gcc gives no warning for comparing unsigned integer < 0 even with -Wextra enabled
Date: Fri, 04 Jan 2019 00:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: 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-82924-4-hq8hGJuzGB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82924-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82924-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00360.txt.bz2
Content-length: 581
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82924
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |msebor at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Duplicate of bug 82521.
*** This bug has been marked as a duplicate of bug 82521 ***
>From gcc-bugs-return-627552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:01:24 2019
Return-Path: <gcc-bugs-return-627552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48662 invoked by alias); 4 Jan 2019 00:01:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48187 invoked by uid 48); 4 Jan 2019 00:00:50 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82521] [7/8/9 Regression] No -Wtype-limits warning when using templates
Date: Fri, 04 Jan 2019 00:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82521-4-vZIqkCa2mt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00361.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82521
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jure.slak at ijs dot si
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
*** Bug 82924 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:20:57 2019
Return-Path: <gcc-bugs-return-627553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76928 invoked by alias); 4 Jan 2019 00:20:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76832 invoked by uid 48); 4 Jan 2019 00:20:52 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51712] -Wtype-limits should not trigger for types of implementation-defined signedness
Date: Fri, 04 Jan 2019 00:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-51712-4-jSCAtDklju@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00362.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51712
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #16 from Martin Sebor <msebor at gcc dot gnu.org> ---
This was fixed (or at least papered over) by the patch referenced in comment #8
and GCC no longer issues a warning for the test case in comment #0. Is the
reason the bug is open that the implementation can be improved or are there
other similar test cases where GCC still warns but shouldn't?
>From gcc-bugs-return-627554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:42:09 2019
Return-Path: <gcc-bugs-return-627554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96047 invoked by alias); 4 Jan 2019 00:42: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 95947 invoked by uid 48); 4 Jan 2019 00:42:04 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88685] [8/9 regression] pointer class array argument indexing
Date: Fri, 04 Jan 2019 00:42: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: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc cf_known_to_work everconfirmed cf_known_to_fail
Message-ID: <bug-88685-4-3GP9xrmFVs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00363.txt.bz2
Content-length: 1633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
CC| |kargl at gcc dot gnu.org
Known to work| |7.4.1
Ever confirmed|0 |1
Known to fail| |8.2.1, 9.0
--- Comment #1 from kargl at gcc dot gnu.org ---
Interesting bug. Changing doit() to
subroutine doit(cls)
class(tarr), pointer :: cls(:,:)
cls(1,1)%cl = 1
print *, 'cl = ', cls(1,1)%cl
print *, 'cl(i)= ', cls(1,1)%cl(1:3)
print *, 'cl(i)= ', cls(1,1)%cl(1:1),cls(1,1)%cl(2:2),cls(1,1)%cl(3:3)
print *, 'cl(i)= ', cls(1,1)%cl(1),cls(1,1)%cl(2),cls(1,1)%cl(3)
end subroutine doit
shows that the issue involves the reference individual elements. With
gfortran 7.4.1, get
% gfc7 -o z a.f90 && ./z
cl = 1 1 1
cl(i)= 1 1 1
cl(i)= 1 1 1
cl(i)= 1 1 1
with 8.2.1 and 9.0 I get
% gfc8 -o z a.f90 && ./z
cl = 1 1 1
cl(i)= 1 1 1
cl(i)= 1 1 1
cl(i)= 1 -1 -1
>From gcc-bugs-return-627555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:47:30 2019
Return-Path: <gcc-bugs-return-627555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100224 invoked by alias); 4 Jan 2019 00:47:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100190 invoked by uid 48); 4 Jan 2019 00:47:25 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88686] New: gcc generates wrong debug information at -O1
Date: Fri, 04 Jan 2019 00:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00364.txt.bz2
Content-length: 1982
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686
Bug ID: 88686
Summary: gcc generates wrong debug information at -O1
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: qrzhang at gatech dot edu
Target Milestone: ---
I have reported this bug at gdb
bugzilla(https://sourceware.org/bugzilla/show_bug.cgi?id=24032). However, it
appears to be a gcc bug. I can reproduce the bug with "gcc version 9.0.0
20190103 (experimental) [trunk revision 267553] (GCC)". The gdb version does
not matter. I can reproduce it with gdb 7.7.
Below is my original report:
=====8<=========
$ gdb-trunk --version
GNU gdb (GDB) 8.2.50.20181223-git
*It correctly prints the value without optimization*
$ gcc-trunk -g abc.c outer.c
$ gdb-trunk -x cmds -batch a.out
Breakpoint 1 at 0x400485: file abc.c, line 8.
Breakpoint 1, main () at abc.c:8
8 optimize_me_not();
9 c = 0;
$1 = 0
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 2315) killed]
*It incorrectly prints "j=1" at -O1*
$ gcc-trunk -g -O1 abc.c outer.c
$ gdb-trunk -x cmds -batch a.out
Breakpoint 1 at 0x400491: file abc.c, line 8.
Breakpoint 1, main () at abc.c:8
8 optimize_me_not();
10 for (; c < 6; c++)
$1 = 1
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 2331) killed]
*Files used to reproduce*
$ cat abc.c
volatile int a, b;
int c;
int main() {
int j;
for (; b < 10; b++) {
j = 0;
for (; j < 2; j++) {
optimize_me_not();
c = 0;
for (; c < 6; c++)
a = b + c;
}
}
}
$ cat outer.c
optimize_me_not() {}
$ cat cmds
b 8
r
n
p j
k
q
=====8<=========
>From gcc-bugs-return-627556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:49:01 2019
Return-Path: <gcc-bugs-return-627556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101827 invoked by alias); 4 Jan 2019 00:49:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101611 invoked by uid 48); 4 Jan 2019 00:48:40 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88686] gcc generates wrong debug information at -O1
Date: Fri, 04 Jan 2019 00:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88686-4-duwLW9PcJO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00365.txt.bz2
Content-length: 195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686
--- Comment #1 from Qirun Zhang <qrzhang at gatech dot edu> ---
The output should be "j=0". However, it incorrectly prints "j=1" at -O1.
>From gcc-bugs-return-627557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 00:57:41 2019
Return-Path: <gcc-bugs-return-627557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70850 invoked by alias); 4 Jan 2019 00:57: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 70602 invoked by uid 48); 4 Jan 2019 00:57:36 -0000
From: "jrnieder at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51712] -Wtype-limits should not trigger for types of implementation-defined signedness
Date: Fri, 04 Jan 2019 00:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jrnieder at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-51712-4-O8sYrrCN0J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00366.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51712
Jonathan Nieder <jrnieder at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #17 from Jonathan Nieder <jrnieder at gmail dot com> ---
Both tests pass with
$ gcc --version
gcc (Debian 7.3.0-5) 7.3.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>From gcc-bugs-return-627558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 01:59:43 2019
Return-Path: <gcc-bugs-return-627558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130128 invoked by alias); 4 Jan 2019 01:59:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128907 invoked by uid 48); 4 Jan 2019 01:59:38 -0000
From: "mjansche at google dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88683] nan <= inf not accepted as constant expression
Date: Fri, 04 Jan 2019 01:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mjansche at google dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88683-4-4p4AniWjgP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00367.txt.bz2
Content-length: 1000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88683
--- Comment #2 from Martin Jansche <mjansche at google dot com> ---
Yeah, looks definitely related. Details may depend on the ultimate diagnosis.
Similar observation here that it matters whether NaN appears on the left-hand
side vs. right-hand side of a comparison (cf.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88173#c5).
Additional notes:
* When/whether this surfaces depends to some extent on the version of gcc. I
first thought it was a simple regression between gcc-7 and gcc-8, but it's more
complex than that.
* The title of Bug 88173 could be interpreted to leave open the possibility
that this might be a library issue, i.e. std::numeric_limits<>::quiet_NaN() not
being declared constexpr. But it's definitely not a library issue.
Anyway, I agree with the recommended disposition as DUP. But I'm new around
here and don't know who gets to close this as DUP. Happy to do it myself, just
don't want to jump the gun.
>From gcc-bugs-return-627559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:06:40 2019
Return-Path: <gcc-bugs-return-627559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34948 invoked by alias); 4 Jan 2019 02:06: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 34283 invoked by uid 48); 4 Jan 2019 02:06:33 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/64525] Duplicate instructions in both paths in conditional code
Date: Fri, 04 Jan 2019 02: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: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-64525-4-YgGeIozZKh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64525-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64525-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00368.txt.bz2
Content-length: 615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64525
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|kugan at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Maxim Kuvyrkov from comment #2)
> > Kugan's work-in-progress patches may fix this one.
>
> Are they still work-in-progress?
Guess not; removing assignee
>From gcc-bugs-return-627560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:16:27 2019
Return-Path: <gcc-bugs-return-627560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109643 invoked by alias); 4 Jan 2019 02:16: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 107369 invoked by uid 48); 4 Jan 2019 02:15:36 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/15896] Strange behaviour for inline assembler input constraint
Date: Fri, 04 Jan 2019 02:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 3.4.0
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: P2
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-15896-4-p2py77Zyvx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-15896-4@http.gcc.gnu.org/bugzilla/>
References: <bug-15896-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00369.txt.bz2
Content-length: 1533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=15896
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #3)
> (In reply to Eric Gallager from comment #2)
> > (In reply to Andrew Pinski from comment #1)
> > > I don't know Ada that well (in terms of promotions and types) but the
> > > following C code produces the
> > > same ICE so I might assume the issue is that My_Type+constant is being
> > > promoted to unsigned long
> > > long or something along that line:
> > > int f()
> > > {
> > > unsigned long long cu32 = 1;
> > > asm("%0"::"a"(cu32));
> > > }
> >
> > Does this still happen with newer versions of GCC? I can't reproduce with
> > gcc 7, but I'm assuming that's due to target differences; I get different
> > messages depending on 32-bit or 64-bit, but neither of them are an ICE:
> >
> > $ gcc -c -m32 15896.c
> > 15896.c: In function 'f':
> > 15896.c:4:3: error: inconsistent operand constraints in an 'asm'
> > asm("%0"::"a"(cu32));
> > ^~~
> > $ gcc -c -m64 15896.c
> > 15896.c:4:Junk character 37 (%).
> > 15896.c:4:Rest of line ignored. 1st junk character valued 114 (r).
> > $
>
> WAITING on a reply
No reply; closing.
>From gcc-bugs-return-627561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:18:44 2019
Return-Path: <gcc-bugs-return-627561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5295 invoked by alias); 4 Jan 2019 02:18:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3556 invoked by uid 48); 4 Jan 2019 02:18:35 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/85716] No easy way for end-user to tell what GCC is doing when compilation is slow
Date: Fri, 04 Jan 2019 02:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85716-4-1DE5Qp3h7i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85716-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85716-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00370.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85716
--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to sandra from comment #9)
> Just to clarify, I didn't have anything to do with proposing a "progress
> bar"; I just needed to know whether the split1 pass had run yet. And I
> ended up solving that problem by using a property instead of a dynamic pass
> numbering thing.
Oh, maybe I was thinking of some other thread on the lists then?
>From gcc-bugs-return-627562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:20:12 2019
Return-Path: <gcc-bugs-return-627562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13882 invoked by alias); 4 Jan 2019 02:20:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13751 invoked by uid 48); 4 Jan 2019 02:20:07 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/38629] target-specific parameters for inline heuristics not defined for AVR
Date: Fri, 04 Jan 2019 02:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.3.3
X-Bugzilla-Keywords:
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: assigned_to
Message-ID: <bug-38629-4-H4NQu1392F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38629-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00371.txt.bz2
Content-length: 3509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38629
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|hubicka at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #10 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #9)
> (In reply to Jan Hubicka from comment #6)
> > OK, at -Os the issue is that function is called once so inlining is a win.
> > Making multiple copies of it leads to GCC making clone:
> > delay_wait_us_ms.constprop.0:
> > .LFB3:
> > movl $136, %edi
> > jmp delay_wait_us
> > .LFE3:
> > and then calling it
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > call delay_wait_us_ms.constprop.0
> > at -Os,that is
> >
> > With -O2 it is different story, we end up inlining everything. We get:
> > Analyzing function body size: delay_wait_us
> > freq: 1000 size: 1 time: 1 __asm__ __volatile__("wdr");
> > freq: 1000 size: 1 time: 1 MEM[(volatile unsigned char *)82B] ={v}
> > timeout_2(D);
> > freq: 1000 size: 1 time: 1 D.2719_5 ={v} MEM[(volatile unsigned char
> > *)88B];
> > freq: 1000 size: 1 time: 1 D.2720_6 = D.2719_5 | 1;
> > freq: 1000 size: 1 time: 1 MEM[(volatile unsigned char *)88B] ={v}
> > D.2720_6;
> > freq: 11111 size: 1 time: 1 D.2721_8 ={v} MEM[(volatile unsigned char
> > *)88B];
> > freq: 11111 size: 0 time: 0 D.2722_9 = (int) D.2721_8;
> > freq: 11111 size: 1 time: 1 D.2723_10 = D.2722_9 & 1;
> > freq: 11111 size: 2 time: 2 if (D.2723_10 == 0)
> > freq: 1000 size: 1 time: 2 return;
> > Likely eliminated
> > Overall function body time: 51-2 size: 10-1
> > With function call overhead time: 51-13 size: 10-3
> >
> > that fits in early-inlining-insns. With --param early-inlining-insns=0 we
> > get it right. GCC inliner is guessing here that inlining such a small leaf
> > function will result in enough optimization so it pays back. I am not sure
> > what we can do here, early-inlining-insns is being pushed up by C++ code...
> >
> > It is not terribly bad tradeoff even at -O2. I will try to get some data how
> > much early inlining insns cost us at -O2 and if it is too much, I will
> > disable the allowed growth for functions not declared inline.
>
> Are you still working on this?
No reply, unassigning
>From gcc-bugs-return-627563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:25:55 2019
Return-Path: <gcc-bugs-return-627563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28540 invoked by alias); 4 Jan 2019 02:25: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 28408 invoked by uid 48); 4 Jan 2019 02:25:50 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69215] Improve diagnostic for 'for(i : v)'
Date: Fri, 04 Jan 2019 02:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-69215-4-GgKQdULPWh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69215-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00372.txt.bz2
Content-length: 593
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69215
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ville.voutilainen at gmail dot com
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to TC from comment #0)
>
> Perhaps the code implementing N3994, removed by r229632, can be repurposed
> instead to produce a better error message?
Ville did that commit; cc-ing them
>From gcc-bugs-return-627564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:27:52 2019
Return-Path: <gcc-bugs-return-627564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31110 invoked by alias); 4 Jan 2019 02:27: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 31051 invoked by uid 48); 4 Jan 2019 02:27:48 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/70968] Missed case for -Wmisleading-indentation
Date: Fri, 04 Jan 2019 02:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-70968-4-Pa4OfC8nzD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70968-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70968-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00373.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70968
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dodji at gcc dot gnu.org
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #1)
> Confirmed; cc-ing author of the warning
cc-ing other diagnostics maintainer, too
>From gcc-bugs-return-627565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:32:21 2019
Return-Path: <gcc-bugs-return-627565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35413 invoked by alias); 4 Jan 2019 02:32: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 35054 invoked by uid 48); 4 Jan 2019 02:31:54 -0000
From: "gary_mills at fastmail dot fm" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Fri, 04 Jan 2019 02:32: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.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary_mills at fastmail dot fm
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-nIPLnoXDu1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00374.txt.bz2
Content-length: 4641
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #23 from Gary Mills <gary_mills at fastmail dot fm> ---
It's not Solaris, first of all. Solaris is a closed system once again. It's
illumos, which is derived from Opensolaris. These are the two assemblers:
This is on SPARC hardware:
<mills@t2000:725>$ as -V
as: Sun Compiler Common 12 SunOS_sparc snv_121 08/03/2009
<mills@t2000:726>$ uname -a
SunOS t2000 5.11 master-0-g5093b3b sun4v sparc SUNW,Sun-Fire-T200
This is on x86 hardware:
<mills@tyan:545>$ as -V
as: Sun Compiler Common 12 SunOS_i386 snv_121 08/03/2009
Usage: as [-V] [-Q{y,n}] [-s]
[-S[aAbBcClL]] [-K {pic,PIC}] [-o objfile] [-L] [-T]
[-P [[-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
[-m [-Ym,path]] [-n] [-xF] [-F] [-b] [-i] file.s ...
<mills@tyan:546>$ uname -a
SunOS tyan 5.11 illumos-8dfe5547fb i86pc i386 i86pc
They seem to be the same. illumos does not have source for the assembler, only
the binaries. They can't be changed. illumos does have source for the
linkers.
Yes, /usr/gcc/4.9/bin/gcc and /usr/gcc/4.9/bin/g++ are the 32-bit-default
compilers. They will produce 64-bit binaries with the -m64 option. They are
actually 4.9.4. I built the compilers myself, using gcc-4.4.4.
I just tried a build of gcc-7 (gcc-7.3.0) with a minimal configuration. This
is what appears in the oldest config.log:
$
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
CC=/usr/gcc/4.9/bin/gcc CXX=/usr/gcc/4.9/bin/g++ F77=/usr/gcc/4.9/bin/gfortran
FC=/usr/gcc/4.9/bin/gfortran CFLAGS= -O3 -mno-app-regs CXXFLAGS= FFLAGS=
FCFLAGS= LDFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib/pkgconfig --prefix=/usr/gcc/7
--mandir=/usr/gcc/7/share/man --bindir=/usr/gcc/7/bin --libdir=/usr/gcc/7/lib
--sbindir=/usr/gcc/7/sbin --sbindir=/usr/gcc/7/bin --libdir=/usr/gcc/7/lib
--libexecdir=/usr/gcc/7/lib --host sparc-sun-solaris2.11 --build
sparc-sun-solaris2.11 --target sparc-sun-solaris2.11 --without-gnu-ld
--with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
LDFLAGS=-R/usr/gcc/7/lib
I also removed all of the patches except for one that modifies
libgcc/config.host to create crtbeginS.o and crtendS.o. The build stopped
quite early with this error:
/usr/gcc/4.9/bin/g++ -std=gnu++98 -g -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-format -Wmissing-format-attribute -Woverloaded-virtual
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -fno-PIE -static-libstdc++
-static-libgcc -R/usr/gcc/7/lib -o build/genmddeps \
build/genmddeps.o build/read-md.o build/errors.o
../build-sparc-sun-solaris2.11/libiberty/libiberty.a
build/genmddeps
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/common.md
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/config/sparc/sparc.md
> tmp-mddeps
/bin/bash: line 1: 28485 Bus Error (core dumped) build/genmddeps
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/common.md
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/config/sparc/sparc.md
> tmp-mddeps
Makefile:2240: recipe for target 's-mddeps' failed
make[4]: *** [s-mddeps] Error 138
make[4]: Leaving directory
'/dpool/export/home/mills/Downloads/code/oi-userland-apr/components/developer/gcc-7/build/sparcv7/gcc'
This is what gdb said about the core file:
(gdb) bt
#0 0x0001f7bc in __gnu_cxx::__mutex::__mutex (
this=0x5007c <(anonymous namespace)::emergency_mutex>)
at
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc49/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/ext/concurrence.h:132
#1 __static_initialization_and_destruction_0 (__priority=65535,
__initialize_p=1)
at
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc49/gcc-4.9.4/libstdc++-v3/libsupc++/eh_alloc.cc:96
#2 _GLOBAL__sub_I_eh_alloc.cc(void) ()
at
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc49/gcc-4.9.4/libstdc++-v3/libsupc++/eh_alloc.cc:211
#3 0x0002f19c in __do_global_ctors_aux ()
#4 0x0002f1d4 in _init ()
#5 0x000165f0 in _start ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
(gdb) quit
The build didn't dump core at this point before. Something in the
configuration must have changed its behavior.
>From gcc-bugs-return-627566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:32:21 2019
Return-Path: <gcc-bugs-return-627566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35423 invoked by alias); 4 Jan 2019 02:32: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 35314 invoked by uid 48); 4 Jan 2019 02:32:16 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/64679] Spurious redefinition error when parsing not-quite-most-vexing-parse declarations
Date: Fri, 04 Jan 2019 02:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-64679-4-nrjGFujZpq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64679-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64679-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00375.txt.bz2
Content-length: 589
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64679
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=25814
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
Even though it's not QUITE the most-vexing-parse I'd say it's still related
enough to bug 25814 for it to go under "See Also"
>From gcc-bugs-return-627567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 02:34:44 2019
Return-Path: <gcc-bugs-return-627567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39443 invoked by alias); 4 Jan 2019 02:34: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 39383 invoked by uid 48); 4 Jan 2019 02:34:32 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/67276] duplicated missing terminating character diagnostic
Date: Fri, 04 Jan 2019 02:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-67276-4-za5DII9oTd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00376.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67276
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org,
| |dodji at gcc dot gnu.org
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing diagnostics maintainers
>From gcc-bugs-return-627568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 03:14:13 2019
Return-Path: <gcc-bugs-return-627568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22500 invoked by alias); 4 Jan 2019 03:14: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 15512 invoked by uid 55); 4 Jan 2019 03:14:07 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88659] [9 Regression] ICE in maybe_warn_nonstring_arg at gcc/calls.c:1688 since r267503
Date: Fri, 04 Jan 2019 03:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88659-4-IbA5XWwJCF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00377.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88659
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Fri Jan 4 03:13:33 2019
New Revision: 267569
URL: https://gcc.gnu.org/viewcvs?rev=267569&root=gcc&view=rev
Log:
PR tree-optimization/88659 - ICE in maybe_warn_nonstring_arg
gcc/ChangeLog:
* calls.c (maybe_warn_nonstring_arg): Avoid assuming maxlen is set.
gcc/testsuite/ChangeLog:
* gcc.dg/Wstringop-truncation-6.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/Wstringop-truncation-6.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/calls.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 03:22:41 2019
Return-Path: <gcc-bugs-return-627569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17382 invoked by alias); 4 Jan 2019 03:22: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 14724 invoked by uid 48); 4 Jan 2019 03:22:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88659] [9 Regression] ICE in maybe_warn_nonstring_arg at gcc/calls.c:1688 since r267503
Date: Fri, 04 Jan 2019 03:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88659-4-5odMUPC4fc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00378.txt.bz2
Content-length: 434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88659
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed in r267569.
>From gcc-bugs-return-627570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 03:52:56 2019
Return-Path: <gcc-bugs-return-627570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66653 invoked by alias); 4 Jan 2019 03:52:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66622 invoked by uid 48); 4 Jan 2019 03:52:51 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88687] New: redundant -Wbuiltin-declaration-mismatch after -Wimplicit-function-declaration
Date: Fri, 04 Jan 2019 03: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: 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-88687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00379.txt.bz2
Content-length: 1555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88687
Bug ID: 88687
Summary: redundant -Wbuiltin-declaration-mismatch after
-Wimplicit-function-declaration
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The -Wbuiltin-declaration-mismatch warning below should probably only be issued
if -Wimplicit-function-declaration is disabled, otherwise it's mostly redundant
(although only one instance of the latter warning is issued for each implicit
declaration regardless of the number of calls).
In addition, the <built-in>: note after the -Wbuiltin-declaration-mismatch
warning is meaningless.
$ cat t.c && gcc -O2 -S -Wall -Wextra t.c
int f (const char *s)
{
return memcmp (s, "1234", 4);
}
t.c: In function ‘f’:
t.c:3:10: warning: implicit declaration of function ‘memcmp’
[-Wimplicit-function-declaration]
3 | return memcmp (s, "1234", 4);
| ^~~~~~
t.c:3:29: warning: ‘memcmp’ argument 3 type is ‘int’ where ‘long unsigned int’
is expected in a call to built-in function declared without prototype
[-Wbuiltin-declaration-mismatch]
3 | return memcmp (s, "1234", 4);
| ^
<built-in>: note: built-in ‘memcmp’ declared here
>From gcc-bugs-return-627571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 03:53:15 2019
Return-Path: <gcc-bugs-return-627571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67383 invoked by alias); 4 Jan 2019 03:53:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67362 invoked by uid 48); 4 Jan 2019 03:53:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88687] redundant -Wbuiltin-declaration-mismatch after -Wimplicit-function-declaration
Date: Fri, 04 Jan 2019 03:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: minor
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_severity
Message-ID: <bug-88687-4-olb2kfaazZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00380.txt.bz2
Content-length: 352
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88687
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Severity|normal |minor
>From gcc-bugs-return-627572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 05:27:08 2019
Return-Path: <gcc-bugs-return-627572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34204 invoked by alias); 4 Jan 2019 05: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 31396 invoked by uid 48); 4 Jan 2019 05:27:03 -0000
From: "thfanning at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88688] New: Incorrect association in SELECT TYPE
Date: Fri, 04 Jan 2019 05:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thfanning 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-88688-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00381.txt.bz2
Content-length: 1653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88688
Bug ID: 88688
Summary: Incorrect association in SELECT TYPE
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: thfanning at gmail dot com
Target Milestone: ---
Created attachment 45334
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45334&action=edit
Test case demonstrating issue.
SELECT TYPE constructs may not correctly associate the local name with the
polymorphic selector. For example, consider the following snippet:
call tp%setref(i)
select type (ap => tp%ptr)
class default
call tp%setref(j)
lp => ap
call set7(lp)
end select
where 'setref' associates the pointer component 'ptr' to the actual argument.
In this case, should the name 'lp' associate with the original value of the
selector 'tp%ptr' (which is associated with 'i'), or with the updated value of
tp%ptr (which is newly associated with 'j')?
When compiled with fortran 8.2, the attached program produces the following:
$ gfortran debug2.f90
$ ./a.out
I: 3
J: 7
When compiled with Intel Fortran, the attached program produces the following:
$ ifort debug2.f90
$ ./a.out
I: 7
J: 4
It's not clear what the correct behavior should be. Does 'ap' associate with
the pointer or the pointee? In other words, is 'ap' just a syntactic
simplification, or does it "bind" with the polymorphic entity at the point of
definition? It should be the latter, which means there is a bug in gfortran.
>From gcc-bugs-return-627573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 05:46:03 2019
Return-Path: <gcc-bugs-return-627573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14669 invoked by alias); 4 Jan 2019 05:46:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14278 invoked by uid 48); 4 Jan 2019 05:45:46 -0000
From: "venkateshprabu at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88689] New: Resource leak.. Leaked storage
Date: Fri, 04 Jan 2019 05:46: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: venkateshprabu 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-88689-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00382.txt.bz2
Content-length: 1344
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88689
Bug ID: 88689
Summary: Resource leak.. Leaked storage
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: venkateshprabu at gmail dot com
Target Milestone: ---
https://github.com/gcc-mirror/gcc/blob/gcc-8_2_0-release/libstdc++-v3/include/bits/stl_list.h#L1900
Is this false positive by coverity ?
Coverity report:
1766 template<typename... _Args>
1767 void
1768 _M_insert(iterator __position, _Args&&... __args)
1769 {
1. alloc_fn: Storage is returned from allocation function
_M_create_node. [show details]
2. var_assign: Assigning: __tmp = storage returned from
this->_M_create_node(std::forward(__args)).
1770 _Node* __tmp = _M_create_node(std::forward<_Args>(__args)...);
3. noescape: Resource __tmp is not freed or pointed-to in unimplemented
function _M_hook.
1771 __tmp->_M_hook(__position._M_node);
1772 this->_M_inc_size(1);
CID 5519463 (#79-1 of 79): Resource leak (RESOURCE_LEAK)
4. leaked_storage: Variable __tmp going out of scope leaks the storage it
points to.
1773 }
1774#endif
>From gcc-bugs-return-627574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 06:09:05 2019
Return-Path: <gcc-bugs-return-627574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73085 invoked by alias); 4 Jan 2019 06:09: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 73026 invoked by uid 48); 4 Jan 2019 06:09:01 -0000
From: "jrnieder at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51712] -Wtype-limits should not trigger for types of implementation-defined signedness
Date: Fri, 04 Jan 2019 06:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jrnieder at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51712-4-pIzUmqRhUT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00383.txt.bz2
Content-length: 298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51712
--- Comment #18 from Jonathan Nieder <jrnieder at gmail dot com> ---
That said, as mentioned in comment#15, the use of -fno-short-enums in the test
is not right. I'll try removing that and see if the test still passes tomorrow
(it should).
>From gcc-bugs-return-627575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 06:36:17 2019
Return-Path: <gcc-bugs-return-627575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43605 invoked by alias); 4 Jan 2019 06:36:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43545 invoked by uid 48); 4 Jan 2019 06:36:12 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host
Date: Fri, 04 Jan 2019 06:36: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: umesh.kalappa0 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-88668-4-BUyx6r9ext@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00384.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
--- Comment #5 from Umesh Kalappa <umesh.kalappa0 at gmail dot com> ---
Andrew unfortunately your suggestion didn't worked for us and there was
mis-lead in our fix and the actual change was like
--- a/gcc/configure
+++ b/gcc/configure
@@ -11795,15 +11795,16 @@ else
CXX="${CXX_FOR_BUILD}" CXXFLAGS="${CXXFLAGS_FOR_BUILD}" \
LD="${LD_FOR_BUILD}" LDFLAGS="${LDFLAGS_FOR_BUILD}" \
GMPINC="" CPPFLAGS="${CPPFLAGS} -DGENERATOR_FILE" \
+ enable_targets=$enable_targets\
${realsrcdir}/configure \
--enable-languages=${enable_languages-all} \
--target=$target_alias --host=$build_alias --build=$build_alias
and my bad for miscommunication here .
>From gcc-bugs-return-627576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 06:40:52 2019
Return-Path: <gcc-bugs-return-627576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47631 invoked by alias); 4 Jan 2019 06:40: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 47587 invoked by uid 48); 4 Jan 2019 06:40:47 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88668] Code generated was different for PowerPC when build!=host compared to build=host
Date: Fri, 04 Jan 2019 06:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88668-4-tXlKPtmqyk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00385.txt.bz2
Content-length: 229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88668
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So the correct fix is to add --enable-targets=$enable_targets to
${realsrcdir}/configure command instead.
>From gcc-bugs-return-627578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 07:28:42 2019
Return-Path: <gcc-bugs-return-627578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 375 invoked by alias); 4 Jan 2019 07:28: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 130813 invoked by uid 48); 4 Jan 2019 07:28:38 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88653-4-Jt4dde44uH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00387.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #4 from Murat <mtekeev at yandex dot ru> ---
Created attachment 45336
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45336&action=edit
error message
>From gcc-bugs-return-627577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 07:28:10 2019
Return-Path: <gcc-bugs-return-627577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127626 invoked by alias); 4 Jan 2019 07:28:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127570 invoked by uid 48); 4 Jan 2019 07:28:06 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88653-4-6Zjp2KK0ef@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00386.txt.bz2
Content-length: 227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #3 from Murat <mtekeev at yandex dot ru> ---
Created attachment 45335
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45335&action=edit
gfortran verson
>From gcc-bugs-return-627579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 07:29:24 2019
Return-Path: <gcc-bugs-return-627579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1441 invoked by alias); 4 Jan 2019 07:29: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 1381 invoked by uid 48); 4 Jan 2019 07:29:20 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 07:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88653-4-YFYBPfFwWX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00388.txt.bz2
Content-length: 226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #5 from Murat <mtekeev at yandex dot ru> ---
Created attachment 45337
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45337&action=edit
files of tests
>From gcc-bugs-return-627580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 07:33:10 2019
Return-Path: <gcc-bugs-return-627580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5535 invoked by alias); 4 Jan 2019 07:33: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 5464 invoked by uid 48); 4 Jan 2019 07:33:04 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 07: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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-88653-4-gIbzFxxHoh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00389.txt.bz2
Content-length: 571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #6 from Murat <mtekeev at yandex dot ru> ---
Hello Dominique!
I took the test file from here:
http://www.fortran-2000.com/ArnaudRecipes/fcvs21_f95.html (file
fcvs21_f95.tar.bz2, modified version that conforms to Fortran 95).
I tried to compile with the options you write about, but the result is the
same.
I use gfortran v. 7.4 on Cygwin. When I had a gfortran v. 7.3, there were no
such problems, all tests were compiled successfully.
Maybe I'm doing something wrong?
Sincerely yours, Murat Tekeev
>From gcc-bugs-return-627581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 08:01:10 2019
Return-Path: <gcc-bugs-return-627581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116653 invoked by alias); 4 Jan 2019 08:01: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 116382 invoked by uid 48); 4 Jan 2019 08:00:56 -0000
From: "eugene at hutorny dot in.ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] New: internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 08: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: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eugene at hutorny dot in.ua
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00390.txt.bz2
Content-length: 1301
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
Bug ID: 88690
Summary: internal compiler error: in
output_constructor_regular_field, at varasm.c:5031
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: eugene at hutorny dot in.ua
Target Milestone: ---
GCC version: gcc version 7.3.1 20180622 (release) [ARM/embedded-7-branch
revision 261907] (GNU Tools for Arm Embedded Processors 7-2018-q2-update)
OS Name: Microsoft Windows 7 Ultimate
OS Version: 6.1.7601 Service Pack 1 Build 7601
Command line:
arm-none-eabi-g++ -mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16
-O3 -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -Wall
-Wshadow -Wlogical-op -Wfloat-equal -DDEBUG -I"E:\Projects\nrf52832-mdk\config"
-I"E:\Projects\ags\src" -fabi-version=9 -fno-exceptions -fno-rtti
-fno-use-cxa-atexit -fno-threadsafe-statics -std=c++17 -O5 -Wabi
-Wctor-dtor-privacy -Wnoexcept -Weffc++ @../gcc.opt --save-temps -MMD -MP
-MF"src/services.d" -MT"src/services.o" -c -o "src/services.o"
"../src/services.cpp"
>From gcc-bugs-return-627582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 08:02:52 2019
Return-Path: <gcc-bugs-return-627582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118598 invoked by alias); 4 Jan 2019 08:02:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118558 invoked by uid 48); 4 Jan 2019 08:02:48 -0000
From: "eugene at hutorny dot in.ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 08: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: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eugene at hutorny dot in.ua
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88690-4-D9dbNniica@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00391.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
--- Comment #1 from Eugene <eugene at hutorny dot in.ua> ---
Created attachment 45338
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45338&action=edit
Zipped prepocessed file causing internal error
>From gcc-bugs-return-627583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 08:04:05 2019
Return-Path: <gcc-bugs-return-627583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120348 invoked by alias); 4 Jan 2019 08:04: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 120256 invoked by uid 48); 4 Jan 2019 08:04:00 -0000
From: "eugene at hutorny dot in.ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 08:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eugene at hutorny dot in.ua
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88690-4-5xM3333ymi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00392.txt.bz2
Content-length: 250
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
--- Comment #2 from Eugene <eugene at hutorny dot in.ua> ---
Created attachment 45339
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45339&action=edit
Output of arm-none-eabi-gcc.exe -v
>From gcc-bugs-return-627584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 08:15:00 2019
Return-Path: <gcc-bugs-return-627584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16900 invoked by alias); 4 Jan 2019 08:14: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 16839 invoked by uid 48); 4 Jan 2019 08:14:55 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Fri, 04 Jan 2019 08:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88677-4-2ZS6CKcusp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00393.txt.bz2
Content-length: 1557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-reduction |
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:
$ cat test2.ii
template <typename> class c;
template <typename b> class D : public c<b> {
public:
static D d() { return D(0, e, f); }
enum g { e };
enum h { f };
D(b *, g, h) : i() {}
b i;
};
struct j {
int k;
};
template <> class c<j> {
public:
void l();
};
extern const D<j> m;
class n {
unsigned o;
public:
D<j> p() { return o ? D<j>::d() : m; }
};
void fn1() {
n a;
a.p().l();
a.p();
}
Minimal options: -O2
Difference for -fdump-tree-fre1:
$ diff -u 2 1
--- 2 2019-01-04 09:13:20.637935502 +0100
+++ 1 2019-01-04 09:13:17.961848506 +0100
@@ -57,7 +57,7 @@
n::p (struct n * const this)
{
int SR.3;
- struct D D.2531;
+ struct D D.2527;
struct D D.2507;
unsigned int _1;
@@ -108,9 +108,9 @@
int SR.8;
int SR.7;
unsigned int a;
- struct D D.2547;
- struct D D.2545;
- struct D D.2544;
+ struct D D.2543;
+ struct D D.2541;
+ struct D D.2540;
struct n a;
struct D D.2498;
struct D D.2497;
@@ -140,7 +140,8 @@
SR.9_27 = MEM[(struct D *)&m];
<bb 7> :
- MEM[(struct D *)&D.2498] = SR.8_11;
+ # SR.9_12 = PHI <0(5), SR.9_27(6)>
+ MEM[(struct D *)&D.2498] = SR.9_12;
return;
<bb 8> :
>From gcc-bugs-return-627585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 08:47:14 2019
Return-Path: <gcc-bugs-return-627585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57478 invoked by alias); 4 Jan 2019 08:47: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 44054 invoked by uid 48); 4 Jan 2019 08:47:09 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: needs-bisection, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget bug_status cf_reconfirmed_on cc cf_gcchost everconfirmed
Message-ID: <bug-88690-4-CqGRrPewyM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00394.txt.bz2
Content-length: 916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection,
| |needs-reduction
Target| |arm-linux-gnueabihf
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
CC| |marxin at gcc dot gnu.org
Host| |x86_64-pc-linux-gnu
Ever confirmed|0 |1
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed with cross-compiler on current trunk, bit similar to PR87861.
I'm reducing that now.
>From gcc-bugs-return-627586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 08:55:29 2019
Return-Path: <gcc-bugs-return-627586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36917 invoked by alias); 4 Jan 2019 08:55: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 30641 invoked by uid 48); 4 Jan 2019 08:55:25 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Fri, 04 Jan 2019 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc bug_severity
Message-ID: <bug-84010-4-B6II4J1r5s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00395.txt.bz2
Content-length: 642
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
Summary|[sparc64] Problematic TLS |problematic TLS code
|code generation |generation on 64-bit SPARC
Severity|normal |major
--- Comment #8 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
We definitely need to fix this. James, can you submit your patch on the ML?
>From gcc-bugs-return-627587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:01:21 2019
Return-Path: <gcc-bugs-return-627587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127970 invoked by alias); 4 Jan 2019 09:01: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 127875 invoked by uid 55); 4 Jan 2019 09:01:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88594] [9 Regression] ICE in int_mode_for_mode, at stor-layout.c:403
Date: Fri, 04 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88594-4-n81oczKcax@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00396.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88594
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 4 09:00:05 2019
New Revision: 267571
URL: https://gcc.gnu.org/viewcvs?rev=267571&root=gcc&view=rev
Log:
PR target/88594
* config/i386/i386.c (ix86_expand_divmod_libfunc): Use mode instead
of GET_MODE (opN) as modes of the libcall arguments.
* gcc.dg/pr88594.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/pr88594.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:07:10 2019
Return-Path: <gcc-bugs-return-627588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28032 invoked by alias); 4 Jan 2019 09:07: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 24945 invoked by uid 48); 4 Jan 2019 09:07:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 09:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: needs-bisection, needs-reduction
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-88690-4-MNLdr9j9RE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00397.txt.bz2
Content-length: 1674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:
$ cat services.ii
typedef char a;
using b = int;
class c {
b f{5};
};
class d {
int e{};
};
class C {
C() = delete;
};
class i : public d, public C {};
template <int, typename, int, class> using g = i;
enum { h };
using code = int;
struct : c {
enum k : a;
g<h, k, h, code> j;
} ags{};
$ /home/marxin/Programming/gcc2/objdir/gcc/xgcc
-B/home/marxin/Programming/gcc2/objdir/gcc/ -std=c++17 services.ii -c
services.ii:19:8: internal compiler error: in output_constructor_regular_field,
at varasm.c:5202
19 | } ags{};
| ^
0x7c4774 output_constructor_regular_field
../../gcc/varasm.c:5202
0x7c4774 output_constructor
../../gcc/varasm.c:5512
0x126aac3 output_constant
../../gcc/varasm.c:5241
0x126aac3 output_constructor_regular_field
../../gcc/varasm.c:5241
0x126aac3 output_constructor
../../gcc/varasm.c:5512
0x126c152 output_constant
../../gcc/varasm.c:4880
0x126c152 assemble_variable_contents
../../gcc/varasm.c:2144
0x12719d6 assemble_variable(tree_node*, int, int, int)
../../gcc/varasm.c:2323
0x12768e9 varpool_node::assemble_decl()
../../gcc/varpool.c:586
0x12768e9 varpool_node::assemble_decl()
../../gcc/varpool.c:554
0xb6fb5b output_in_order
../../gcc/cgraphunit.c:2444
0xb6fb5b symbol_table::compile()
../../gcc/cgraphunit.c:2684
0xb6fb5b symbol_table::compile()
../../gcc/cgraphunit.c:2595
0xb71cf5 symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.c:2863
>From gcc-bugs-return-627589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:08:36 2019
Return-Path: <gcc-bugs-return-627589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92232 invoked by alias); 4 Jan 2019 09:08:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92182 invoked by uid 48); 4 Jan 2019 09:08:32 -0000
From: "eugene at hutorny dot in.ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 09:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: needs-bisection, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eugene at hutorny dot in.ua
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88690-4-z0sY7yjXvP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00398.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
--- Comment #5 from Eugene <eugene at hutorny dot in.ua> ---
Meanwhile I have found exact line that causing this issue:
services.ii@35563:
characteristic_inst(const characteristic_inst&) = delete;
When commented out, compilation pass.
>From gcc-bugs-return-627590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:20:20 2019
Return-Path: <gcc-bugs-return-627590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110311 invoked by alias); 4 Jan 2019 09:20:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110227 invoked by uid 48); 4 Jan 2019 09:20:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88690-4-HaV3t4QgvH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00399.txt.bz2
Content-length: 434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
It's probably as old as -std=c++17. GCC 7 branch base r247015 fails.
>From gcc-bugs-return-627591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:33:21 2019
Return-Path: <gcc-bugs-return-627591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7029 invoked by alias); 4 Jan 2019 09:33: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 6627 invoked by uid 48); 4 Jan 2019 09:33:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] [7/8/9 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88690-4-ztPRyGsblB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00400.txt.bz2
Content-length: 750
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
Summary|internal compiler error: in |[7/8/9 Regression] internal
|output_constructor_regular_ |compiler error: in
|field, at varasm.c:5031 |output_constructor_regular_
| |field, at varasm.c:5031
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started to ICE with r241187 when P0017R1 has been implemented, before that it
has been rejected.
>From gcc-bugs-return-627592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:40:56 2019
Return-Path: <gcc-bugs-return-627592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25733 invoked by alias); 4 Jan 2019 09:40:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25676 invoked by uid 48); 4 Jan 2019 09:40:52 -0000
From: "antony at cosmologist dot info" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88685] [8/9 regression] pointer class array argument indexing
Date: Fri, 04 Jan 2019 09: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antony at cosmologist dot info
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88685-4-R1YLyPpsdH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00401.txt.bz2
Content-length: 396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
--- Comment #2 from Antony Lewis <antony at cosmologist dot info> ---
I think the individual elements are correct, it's the array indexing operations
that are wrong (this is clearer in the longer example; looks a like wrong
stride). E.g. printing this in the main program after calling doit
print *, arr(1,1)%CL
also gives 1, -1, -1.
>From gcc-bugs-return-627593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:41:00 2019
Return-Path: <gcc-bugs-return-627593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26191 invoked by alias); 4 Jan 2019 09:40: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 25695 invoked by uid 48); 4 Jan 2019 09:40:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88594] [9 Regression] ICE in int_mode_for_mode, at stor-layout.c:403
Date: Fri, 04 Jan 2019 09:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88594-4-0z9qNUNI2C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00402.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88594
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk, will backport to release branches (where the issue is
latent) later.
>From gcc-bugs-return-627594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:49:06 2019
Return-Path: <gcc-bugs-return-627594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40631 invoked by alias); 4 Jan 2019 09:49: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 40482 invoked by uid 48); 4 Jan 2019 09:49:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] [7/8/9 Regression] internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88690-4-Y883RuzuJy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00403.txt.bz2
Content-length: 297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Further reduced (-std=c++17):
struct A { int a = 1; };
struct B { int b = 0; };
struct C { C () = delete; };
struct D : public B, public C {};
struct E : A { D f; } g{};
>From gcc-bugs-return-627595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:53:00 2019
Return-Path: <gcc-bugs-return-627595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44000 invoked by alias); 4 Jan 2019 09:53:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43905 invoked by uid 48); 4 Jan 2019 09:52:56 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88686] gcc generates wrong debug information at -O1
Date: Fri, 04 Jan 2019 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88686-4-WNPDkgVnHk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00404.txt.bz2
Content-length: 854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
CC| |aoliva at gcc dot gnu.org,
| |jakub at gcc dot gnu.org,
| |marxin at gcc dot gnu.org,
| |vries at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, happens for all releases I have (4.8.0). However -Og works fine.
>From gcc-bugs-return-627596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 09:59:20 2019
Return-Path: <gcc-bugs-return-627596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49944 invoked by alias); 4 Jan 2019 09:59: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 49874 invoked by uid 48); 4 Jan 2019 09:59:14 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88691] New: Add support for -fuse-ld=lld (https://lld.llvm.org/)
Date: Fri, 04 Jan 2019 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88691-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00405.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88691
Bug ID: 88691
Summary: Add support for -fuse-ld=lld (https://lld.llvm.org/)
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: dilyan.palauzov at aegee dot org
Target Milestone: ---
>From gcc-bugs-return-627597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 10:14:08 2019
Return-Path: <gcc-bugs-return-627597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54641 invoked by alias); 4 Jan 2019 10:14: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 54548 invoked by uid 48); 4 Jan 2019 10:14:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] [7/8/9 Regression] c++17 internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget cc cf_gcchost short_desc
Message-ID: <bug-88690-4-u0HmIA1Tmj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00406.txt.bz2
Content-length: 1652
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|arm-linux-gnueabihf |
CC| |jason at gcc dot gnu.org
Host|x86_64-pc-linux-gnu |
Summary|[7/8/9 Regression] internal |[7/8/9 Regression] c++17
|compiler error: in |internal compiler error: in
|output_constructor_regular_ |output_constructor_regular_
|field, at varasm.c:5031 |field, at varasm.c:5031
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And it ICEs everywhere.
The CONSTRUCTOR with D type is:
{.D.2084={.b=0}, .D.2085={}}
D.2084 FIELD_DECL has field offset 0 and size 4 bytes, D.4405 FIELD_DECL has
field offset also 0 and size 0. If that is correct, then the CONTRUCTOR should
be ordered {.D.2085={}, .D.2084={.b=0}}.
.D.2084 is created by build_base_field_1 with t D and base_type B and .D.2085
is created by build_base_field_1 with t D and base_type C.
The latter is created with:
if (cxx_dialect >= cxx17 && !BINFO_VIRTUAL_P (binfo))
{
tree decl = build_base_field_1 (t, basetype, next_field);
DECL_FIELD_OFFSET (decl) = BINFO_OFFSET (binfo);
DECL_FIELD_BIT_OFFSET (decl) = bitsize_zero_node;
SET_DECL_OFFSET_ALIGN (decl, BITS_PER_UNIT);
}
Shall we sort somewhere the FIELD_DECLs by ascending offsets, something else?
>From gcc-bugs-return-627598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 10:22:27 2019
Return-Path: <gcc-bugs-return-627598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61708 invoked by alias); 4 Jan 2019 10:22: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 61676 invoked by uid 48); 4 Jan 2019 10:22:23 -0000
From: "d25fe0be at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] New: Spurious "redundant move in return statement"
Date: Fri, 04 Jan 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: d25fe0be at outlook 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-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00407.txt.bz2
Content-length: 908
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
Bug ID: 88692
Summary: Spurious "redundant move in return statement"
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: d25fe0be at outlook dot com
Target Milestone: ---
From https://en.cppreference.com/w/cpp/language/member_functions:
> Note: unlike cv-qualification, ref-qualification does not change the properties of the this pointer: within a rvalue ref-qualified function, *this remains an lvalue expression.
But GCC reports "redundant move" when compiling the following snippet:
```
#include <utility>
struct X {
X f() && {
return std::move(*this);
}
};
```
Live example: https://wandbox.org/permlink/9sD1NnyoDWnKE92C
>From gcc-bugs-return-627599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 10:29:22 2019
Return-Path: <gcc-bugs-return-627599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78421 invoked by alias); 4 Jan 2019 10:29: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 78352 invoked by uid 48); 4 Jan 2019 10:29:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88676] missed opportunity is integer conditional
Date: Fri, 04 Jan 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: cc
Message-ID: <bug-88676-4-GdP1FMdpVv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00408.txt.bz2
Content-length: 936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We have:
# RANGE [0, 1] NONZERO 1
unsigned int b_2(D) = b;
int r;
<bb 2> [local count: 1073741824]:
if (b_2(D) == 1)
goto <bb 3>; [21.72%]
else
goto <bb 4>; [78.28%]
<bb 3> [local count: 233216728]:
<bb 4> [local count: 1073741824]:
# RANGE [1, 2] NONZERO 3
# r_1 = PHI <1(2), 2(3)>
So, we'd need in some suitable pass (phiopt) figure out that a) the SSA_NAME in
the comparison has a value range of 2 values only, compared against one of them
b) that the PHI values can be expressed by cheap arithmetics from that.
>From gcc-bugs-return-627600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 10:33:15 2019
Return-Path: <gcc-bugs-return-627600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105914 invoked by alias); 4 Jan 2019 10:33: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 105843 invoked by uid 48); 4 Jan 2019 10:33:10 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88685] [8/9 regression] pointer class array argument indexing
Date: Fri, 04 Jan 2019 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: wrong-code
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-88685-4-BhbUw16zNb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00409.txt.bz2
Content-length: 511
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
CC| |pault at gcc dot gnu.org
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Likely caused by r251949 (r251946 is OK, r251980 is not).
>From gcc-bugs-return-627601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 10:43:40 2019
Return-Path: <gcc-bugs-return-627601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33226 invoked by alias); 4 Jan 2019 10:43:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29817 invoked by uid 55); 4 Jan 2019 10:42:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48543] Collapse identical strings
Date: Fri, 04 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-48543-4-C8262NB1ub@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48543-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00410.txt.bz2
Content-length: 630
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48543
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Fri Jan 4 10:42:12 2019
New Revision: 267572
URL: https://gcc.gnu.org/viewcvs?rev=267572&root=gcc&view=rev
Log:
2019-01-04 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/48543
* gfortran.dg/const_chararacter_merge.f90: Actually remove.
* gfortran.dg/merge_char_const.f90: Restore.
Added:
trunk/gcc/testsuite/gfortran.dg/merge_char_const.f90
Removed:
trunk/gcc/testsuite/gfortran.dg/const_chararacter_merge.f90
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:04:08 2019
Return-Path: <gcc-bugs-return-627602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24656 invoked by alias); 4 Jan 2019 11:02:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121167 invoked by uid 48); 4 Jan 2019 10:59:55 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65342] [7/8/9 Regression] FAIL: gfortran.dg/intrinsic_(un)?pack_1.f90 -O1 execution test on powerpc-apple-darwin9 after r210201
Date: Fri, 04 Jan 2019 11:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65342-4-uCj3krglFg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65342-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65342-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00411.txt.bz2
Content-length: 209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65342
--- Comment #23 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Still present, see
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00318.html.
>From gcc-bugs-return-627603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:04:34 2019
Return-Path: <gcc-bugs-return-627603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32521 invoked by alias); 4 Jan 2019 11:04:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27793 invoked by uid 48); 4 Jan 2019 11:03:16 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60732] FAIL: g++.dg/ext/altivec-7.C -std=* scan-assembler _Z3fooDv*
Date: Fri, 04 Jan 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.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: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-60732-4-ThOzRR9gqu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00412.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60732
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Not present in https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00318.html,
closing as FIXED.
>From gcc-bugs-return-627604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:06:49 2019
Return-Path: <gcc-bugs-return-627604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40911 invoked by alias); 4 Jan 2019 11:06: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 40848 invoked by uid 48); 4 Jan 2019 11:06:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget
Message-ID: <bug-88653-4-woMsCr9J8u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00413.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86-64-pc-cygwin
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I also don't see the problem with 7.4.1 on Linux. Maybe something
operating system or distribution specific.
I'll see if I can run a test on Cygwin next.
>From gcc-bugs-return-627605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:08:15 2019
Return-Path: <gcc-bugs-return-627605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45344 invoked by alias); 4 Jan 2019 11:08:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45245 invoked by uid 48); 4 Jan 2019 11:08:10 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/52491] FAIL: gcc.dg/torture/pr52402.c at -O2 and above
Date: Fri, 04 Jan 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-52491-4-iMMLMQmWx4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52491-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52491-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00414.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52491
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Not present in https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00318.html,
closing as FIXED.
>From gcc-bugs-return-627606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:18:42 2019
Return-Path: <gcc-bugs-return-627606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23163 invoked by alias); 4 Jan 2019 11: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 23110 invoked by uid 48); 4 Jan 2019 11:18:39 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88567] [9 Regression] ICE in get_initial_defs_for_reduction when building 521.wrf_r on AArch64 SVE
Date: Fri, 04 Jan 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-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: attachments.created
Message-ID: <bug-88567-4-Aw18j4f06e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00415.txt.bz2
Content-length: 337
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
--- Comment #2 from ktkachov at gcc dot gnu.org ---
Created attachment 45340
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45340&action=edit
minimal reproducer
I've reduced the file as much as I could.
ICEs for aarch64 with -Ofast -march=armv8.2-a+sve -mtune=generic
>From gcc-bugs-return-627607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:19:16 2019
Return-Path: <gcc-bugs-return-627607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24588 invoked by alias); 4 Jan 2019 11:19: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 24320 invoked by uid 48); 4 Jan 2019 11:19:12 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88331] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Fri, 04 Jan 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88331-4-Ar2RlNw4da@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00416.txt.bz2
Content-length: 1481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #9 from Uroš Bizjak <ubizjak at gmail dot com> ---
Created attachment 45341
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45341&action=edit
Somehow reduced testcase
The testcase can be compiled with a cross to --target=x86_64-w64-mingw32:
cc1 -O3 -march=core-avx2
ttt.c: In function ‘matmul_i4_avx2’:
ttt.c:139:1: error: insn outside basic block
139 | }
| ^
(insn 998 851 999 (parallel [
(set (reg:DI 764)
(plus:DI (reg/f:DI 19 frame)
(const_int -224 [0xffffffffffffff20])))
(clobber (reg:CC 17 flags))
]) 191 {*adddi_1}
(nil))
during RTL pass: reload
ttt.c:139:1: internal compiler error: in rtl_verify_bb_layout, at cfgrtl.c:2987
0x6635b6 _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
../../git/gcc/gcc/rtl-error.c:108
0x8e3621 rtl_verify_bb_layout
../../git/gcc/gcc/cfgrtl.c:2987
0x8e3621 rtl_verify_flow_info
../../git/gcc/gcc/cfgrtl.c:3033
0x8c784d verify_flow_info()
../../git/gcc/gcc/cfghooks.c:263
0x14945c9 checking_verify_flow_info
../../git/gcc/gcc/cfghooks.h:198
0x14945c9 try_optimize_cfg
../../git/gcc/gcc/cfgcleanup.c:2994
0x14945c9 cleanup_cfg(int)
../../git/gcc/gcc/cfgcleanup.c:3159
0xb26ed9 do_reload
../../git/gcc/gcc/ira.c:5524
0xb26ed9 execute
../../git/gcc/gcc/ira.c:5659
>From gcc-bugs-return-627608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:24:41 2019
Return-Path: <gcc-bugs-return-627608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18580 invoked by alias); 4 Jan 2019 11:24:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85041 invoked by uid 48); 4 Jan 2019 11:24:03 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88331] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Fri, 04 Jan 2019 11:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88331-4-dsylfNnz4X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00417.txt.bz2
Content-length: 1984
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #10 from Uroš Bizjak <ubizjak at gmail dot com> ---
As mentioned in comment #5, this is due to r266345 (AKA fix for PR84877). It
looks that the change now emits RTL sequence outside of BB.
This is what can be seen at the end of .reload dump:
...
(code_label 567 566 568 66 8 (nil) [6 uses])
(note 568 567 571 66 [bb 66] NOTE_INSN_BASIC_BLOCK)
(insn 571 568 572 66 (clobber (reg/i:SI 0 ax)) "ttt.c":139:1 -1
(nil))
(insn 572 571 573 66 (clobber (reg:SI 0 ax [orig:419 <retval> ] [419]))
"ttt.c":139:1 -1
(nil))
(insn 573 572 851 66 (use (reg/i:SI 0 ax)) "ttt.c":139:1 -1
(nil))
;; succ: EXIT [always] count:1311748 (estimated locally) (FALLTHRU)
;; lr out 0 [ax] 6 [bp] 7 [sp] 16 [argp] 19 [frame]
(note 851 573 998 NOTE_INSN_DELETED)
;; Insn is not within a basic block
(insn 998 851 999 (parallel [
(set (reg:DI 764)
(plus:DI (reg/f:DI 19 frame)
(const_int -224 [0xffffffffffffff20])))
(clobber (reg:CC 17 flags))
]) 191 {*adddi_1}
(nil))
;; Insn is not within a basic block
(insn 999 998 1000 (parallel [
(set (reg:DI 763)
(plus:DI (reg:DI 764)
(const_int 31 [0x1f])))
(clobber (reg:CC 17 flags))
]) 191 {*adddi_1}
(nil))
;; Insn is not within a basic block
(insn 1000 999 1001 (parallel [
(set (reg:DI 765)
(lshiftrt:DI (reg:DI 763)
(const_int 5 [0x5])))
(clobber (reg:CC 17 flags))
]) 564 {*lshrdi3_1}
(expr_list:REG_EQUAL (udiv:DI (reg:DI 763)
(const_int 32 [0x20]))
(nil)))
;; Insn is not within a basic block
(insn 1001 1000 0 (parallel [
(set (reg/f:DI 766)
(ashift:DI (reg:DI 765)
(const_int 5 [0x5])))
(clobber (reg:CC 17 flags))
]) 518 {*ashldi3_1}
(nil))
>From gcc-bugs-return-627609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 11:28:49 2019
Return-Path: <gcc-bugs-return-627609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65689 invoked by alias); 4 Jan 2019 11:28: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 65562 invoked by uid 48); 4 Jan 2019 11:28:45 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88331] [9 Regression] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Fri, 04 Jan 2019 11:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component target_milestone short_desc everconfirmed
Message-ID: <bug-88331-4-8Wjprif9Py@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00418.txt.bz2
Content-length: 991
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
CC| |law at gcc dot gnu.org,
| |renlin at gcc dot gnu.org
Component|target |rtl-optimization
Target Milestone|--- |9.0
Summary|ICE in |[9 Regression] ICE in
|rtl_verify_bb_layout, at |rtl_verify_bb_layout, at
|cfgrtl.c:2987 |cfgrtl.c:2987
Ever confirmed|0 |1
--- Comment #11 from Uroš Bizjak <ubizjak at gmail dot com> ---
Confirmed as gcc-9 Regression, CCs added.
>From gcc-bugs-return-627610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 12:14:05 2019
Return-Path: <gcc-bugs-return-627610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57709 invoked by alias); 4 Jan 2019 12:14: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 57588 invoked by uid 48); 4 Jan 2019 12:13:59 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88691] Add support for -fuse-ld=lld (https://lld.llvm.org/)
Date: Fri, 04 Jan 2019 12:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-88691-4-fRtIzNmJxz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88691-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88691-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00419.txt.bz2
Content-length: 299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88691
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-627611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 12:26:40 2019
Return-Path: <gcc-bugs-return-627611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82889 invoked by alias); 4 Jan 2019 12:26:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82823 invoked by uid 48); 4 Jan 2019 12:26:36 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Fri, 04 Jan 2019 12:26: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: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ubizjak 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-XcybHhqNc3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00420.txt.bz2
Content-length: 141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #12 from Uroš Bizjak <ubizjak at gmail dot com> ---
See also PR88331.
>From gcc-bugs-return-627612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 12:29:01 2019
Return-Path: <gcc-bugs-return-627612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85113 invoked by alias); 4 Jan 2019 12:29: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 85018 invoked by uid 48); 4 Jan 2019 12:28:56 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88522] Error: operand size mismatch for `vpgatherqq'
Date: Fri, 04 Jan 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: 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-88522-4-j0hFfaUyys@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88522-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88522-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00421.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88522
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #8 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 9.
>From gcc-bugs-return-627613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 12:37:18 2019
Return-Path: <gcc-bugs-return-627613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98176 invoked by alias); 4 Jan 2019 12:37:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98071 invoked by uid 48); 4 Jan 2019 12:37:13 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88689] Resource leak.. Leaked storage
Date: Fri, 04 Jan 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-88689-4-4Vl4TsF4pD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88689-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88689-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00422.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88689
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> ---
Yes. _M_hook attaches the new node into the linked list.
>From gcc-bugs-return-627615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:08:37 2019
Return-Path: <gcc-bugs-return-627615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75446 invoked by alias); 4 Jan 2019 13:08:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75392 invoked by uid 48); 4 Jan 2019 13:08:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88693] [9 Regression] Wrong code since r263511
Date: Fri, 04 Jan 2019 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cf_reconfirmed_on cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-88693-4-A6r40wwq1o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00424.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88693
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Last reconfirmed| |2019-1-4
Known to work| |8.2.0
Target Milestone|--- |9.0
Summary|Wrong code since r263511 |[9 Regression] Wrong code
| |since r263511
Known to fail| |9.0
>From gcc-bugs-return-627614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:08:11 2019
Return-Path: <gcc-bugs-return-627614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74592 invoked by alias); 4 Jan 2019 13:08: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 74542 invoked by uid 48); 4 Jan 2019 13:08:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88693] New: Wrong code since r263511
Date: Fri, 04 Jan 2019 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00423.txt.bz2
Content-length: 1129
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88693
Bug ID: 88693
Summary: Wrong code since r263511
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: msebor at gcc dot gnu.org
Target Milestone: ---
Following test-case (isolated from icu package) is miscompiled with -O2:
$ cat isolate.c
void
foo (char *p)
{
unsigned l = __builtin_strlen (p);
unsigned expected = 9;
__builtin_printf ("expected: %d, got: %d\n", expected, l);
if (l != expected)
__builtin_abort ();
}
int main()
{
static unsigned char
utf8[]={
0xe4, 0xb8, 0x80, 0xe3, 0x82, 0xa1, 0xef, 0xbd, 0xa1
};
char srcBuffer[100];
__builtin_memcpy(srcBuffer, utf8, sizeof(utf8));
srcBuffer[sizeof(utf8)]=0;
foo (srcBuffer);
return 0;
}
$ gcc isolate.c -O2 && ./a.out
expected: 9, got: 11
Aborted (core dumped)
>From gcc-bugs-return-627616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:23:59 2019
Return-Path: <gcc-bugs-return-627616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12028 invoked by alias); 4 Jan 2019 13:23: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 11966 invoked by uid 48); 4 Jan 2019 13:23:53 -0000
From: "amosbird at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88694] New: constexpr isn't captured correctly in lambda
Date: Fri, 04 Jan 2019 13:23: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amosbird 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-88694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00425.txt.bz2
Content-length: 7321
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88694
Bug ID: 88694
Summary: constexpr isn't captured correctly in lambda
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: amosbird at gmail dot com
Target Milestone: ---
Created attachment 45342
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45342&action=edit
source code
This might be related to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86594
and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82643
Tested with:
g++ -MMD -MP -DCC_PLAYGROUND -std=c++1z -O2 -v -save-temps
-I/home/amos/git/ccutils/ -I/usr/include -I/usr/local/include -c snippet.cpp -o
snippet.rel.o
Using built-in specs.
COLLECT_GCC=g++
Target: x86_64-pc-linux-gnu
Configured with: ../configure --disable-multilib --with-system-zlib
--enable-languages=c,c++ --enable-gold
Thread model: posix
gcc version 8.2.0 (GCC)
COLLECT_GCC_OPTIONS='-MMD' '-MP' '-D' 'CC_PLAYGROUND' '-std=c++17' '-O2' '-v'
'-save-temps' '-I' '/home/amos/git/ccutils/' '-I' '/usr/include' '-I'
'/usr/local/include' '-c' '-o' 'snippet.rel.o' '-shared-libgcc'
'-mtune=generic' '-march=x86-64'
/usr/local/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/cc1plus -E -quiet -v -I
/home/amos/git/ccutils/ -I /usr/include -I /usr/local/include -MMD
snippet.rel.d -MP -MQ snippet.rel.o -D_GNU_SOURCE -D CC_PLAYGROUND snippet.cpp
-mtune=generic -march=x86-64 -std=c++17 -O2 -fpch-preprocess -o snippet.ii
ignoring nonexistent directory
"/usr/local/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../x86_64-pc-linux-gnu/include"
ignoring duplicate directory "/usr/include"
as it is a non-system directory that duplicates a system directory
ignoring duplicate directory "/usr/local/include"
as it is a non-system directory that duplicates a system directory
#include "..." search starts here:
#include <...> search starts here:
/home/amos/git/ccutils/
/usr/local/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0
/usr/local/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/x86_64-pc-linux-gnu
/usr/local/lib/gcc/x86_64-pc-linux-gnu/8.2.0/../../../../include/c++/8.2.0/backward
/usr/local/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include
/usr/local/include
/usr/local/lib/gcc/x86_64-pc-linux-gnu/8.2.0/include-fixed
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-MMD' '-MP' '-D' 'CC_PLAYGROUND' '-std=c++17' '-O2' '-v'
'-save-temps' '-I' '/home/amos/git/ccutils/' '-I' '/usr/include' '-I'
'/usr/local/include' '-c' '-o' 'snippet.rel.o' '-shared-libgcc'
'-mtune=generic' '-march=x86-64'
/usr/local/libexec/gcc/x86_64-pc-linux-gnu/8.2.0/cc1plus -fpreprocessed
snippet.ii -quiet -dumpbase snippet.cpp -mtune=generic -march=x86-64
-auxbase-strip snippet.rel.o -O2 -std=c++17 -version -o snippet.s
GNU C++17 (GCC) version 8.2.0 (x86_64-pc-linux-gnu)
compiled by GNU C version 8.2.0, GMP version 6.1.0, MPFR version 3.1.4,
MPC version 1.0.3, isl version isl-0.18-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C++17 (GCC) version 8.2.0 (x86_64-pc-linux-gnu)
compiled by GNU C version 8.2.0, GMP version 6.1.0, MPFR version 3.1.4,
MPC version 1.0.3, isl version isl-0.18-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 4e924b3bd09bf840dfb30b5ba0fbc5b8
snippet.cpp: In instantiation of ‘main()::<lambda(auto:1)> [with auto:1 =
std::integral_constant<int, 0>]’:
snippet.cpp:8:7: required from ‘constexpr void static_for_impl(Func&&,
std::integer_sequence<T, Is ...>) [with T = int; T Begin = 0; Func =
main()::<lambda(auto:1)>; T ...Is = {0, 1, 2}]’
snippet.cpp:12:30: required from ‘constexpr void static_for(Func&&) [with T =
int; T Begin = 0; T End = 3; Func = main()::<lambda(auto:1)>]’
snippet.cpp:21:26: required from here
snippet.cpp:21:49: error: no matching function for call to ‘Foo::print<i>()’
static_for<int, 0, 3>([&](auto i) { [&]() { foo.print<i>(); }(); });
^~~
snippet.cpp:16:27: note: candidate: ‘template<int x> void Foo::print()’
template <int x> void print() { std::cout << x << std::endl; }
^~~~~
snippet.cpp:16:27: note: template argument deduction/substitution failed:
snippet.cpp:21:49: error: ‘this’ is not a constant expression
static_for<int, 0, 3>([&](auto i) { [&]() { foo.print<i>(); }(); });
^~~
snippet.cpp:21:49: note: in template argument for type ‘int’
snippet.cpp: In instantiation of ‘main()::<lambda(auto:1)> [with auto:1 =
std::integral_constant<int, 1>]’:
snippet.cpp:8:7: required from ‘constexpr void static_for_impl(Func&&,
std::integer_sequence<T, Is ...>) [with T = int; T Begin = 0; Func =
main()::<lambda(auto:1)>; T ...Is = {0, 1, 2}]’
snippet.cpp:12:30: required from ‘constexpr void static_for(Func&&) [with T =
int; T Begin = 0; T End = 3; Func = main()::<lambda(auto:1)>]’
snippet.cpp:21:26: required from here
snippet.cpp:21:49: error: no matching function for call to ‘Foo::print<i>()’
snippet.cpp:16:27: note: candidate: ‘template<int x> void Foo::print()’
template <int x> void print() { std::cout << x << std::endl; }
^~~~~
snippet.cpp:16:27: note: template argument deduction/substitution failed:
snippet.cpp:21:49: error: ‘this’ is not a constant expression
static_for<int, 0, 3>([&](auto i) { [&]() { foo.print<i>(); }(); });
^~~
snippet.cpp:21:49: note: in template argument for type ‘int’
snippet.cpp: In instantiation of ‘main()::<lambda(auto:1)> [with auto:1 =
std::integral_constant<int, 2>]’:
snippet.cpp:8:7: required from ‘constexpr void static_for_impl(Func&&,
std::integer_sequence<T, Is ...>) [with T = int; T Begin = 0; Func =
main()::<lambda(auto:1)>; T ...Is = {0, 1, 2}]’
snippet.cpp:12:30: required from ‘constexpr void static_for(Func&&) [with T =
int; T Begin = 0; T End = 3; Func = main()::<lambda(auto:1)>]’
snippet.cpp:21:26: required from here
snippet.cpp:21:49: error: no matching function for call to ‘Foo::print<i>()’
snippet.cpp:16:27: note: candidate: ‘template<int x> void Foo::print()’
template <int x> void print() { std::cout << x << std::endl; }
^~~~~
snippet.cpp:16:27: note: template argument deduction/substitution failed:
snippet.cpp:21:49: error: ‘this’ is not a constant expression
static_for<int, 0, 3>([&](auto i) { [&]() { foo.print<i>(); }(); });
^~~
snippet.cpp:21:49: note: in template argument for type ‘int’
make: *** [snippet.rel.o] Error 1
>From gcc-bugs-return-627617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:25:03 2019
Return-Path: <gcc-bugs-return-627617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13618 invoked by alias); 4 Jan 2019 13:25: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 13130 invoked by uid 48); 4 Jan 2019 13:24:41 -0000
From: "amosbird at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88694] constexpr isn't captured correctly in lambda
Date: Fri, 04 Jan 2019 13: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amosbird at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88694-4-wfkM54slnB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00426.txt.bz2
Content-length: 228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88694
--- Comment #1 from Amos Bird <amosbird at gmail dot com> ---
Created attachment 45343
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45343&action=edit
the ii file
>From gcc-bugs-return-627618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:29:38 2019
Return-Path: <gcc-bugs-return-627618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28075 invoked by alias); 4 Jan 2019 13:29:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28024 invoked by uid 48); 4 Jan 2019 13:29:33 -0000
From: "amosbird at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88694] constexpr isn't captured correctly in lambda
Date: Fri, 04 Jan 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amosbird at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88694-4-fwby81X2Ub@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00427.txt.bz2
Content-length: 918
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88694
--- Comment #2 from Amos Bird <amosbird at gmail dot com> ---
Currently by introducing a `auto local_i = decltype(i)();` can workaround this.
#include <iostream>
#include <tuple>
#include <utility>
template <typename T, T Begin, class Func, T... Is>
constexpr void static_for_impl(Func&& f, std::integer_sequence<T, Is...>) {
(f(std::integral_constant<T, Begin + Is>{}), ...);
}
template <typename T, T Begin, T End, class Func> constexpr void
static_for(Func&& f) {
static_for_impl<T, Begin>(std::forward<Func>(f),
std::make_integer_sequence<T, End - Begin>{});
}
struct Foo {
template <int x> void print() { std::cout << x << std::endl; }
};
int main() {
Foo foo;
static_for<int, 0, 3>([&](auto i) {
[&]() {
auto local_i = decltype(i)();
foo.print<local_i>();
}();
});
return 0;
}
>From gcc-bugs-return-627619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:33:16 2019
Return-Path: <gcc-bugs-return-627619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58927 invoked by alias); 4 Jan 2019 13:33: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 58872 invoked by uid 48); 4 Jan 2019 13:33:10 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87276] [9 Regression] Buggy tree-ssa optimization introduced in revision 263875
Date: Fri, 04 Jan 2019 13:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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-87276-4-vEnw9falLm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00428.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87276
--- Comment #6 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
Note concerning the tests: in Debian, as of gcc-snapshot 1:20181209-1, MPFR is
no longer affected (and I've checked that the failure is still reproducible
with gcc-snapshot 1:20181127-1). But the testcase in Comment 1 still fails.
>From gcc-bugs-return-627620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:37:23 2019
Return-Path: <gcc-bugs-return-627620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62053 invoked by alias); 4 Jan 2019 13:37:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61985 invoked by uid 48); 4 Jan 2019 13:37:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88676] missed opportunity in integer conditional
Date: Fri, 04 Jan 2019 13:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-88676-4-z4Kvnwsypd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00429.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-04
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> ---
Created attachment 45344
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45344&action=edit
gcc9-pr88676.patch
Untested fix.
>From gcc-bugs-return-627621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:39:36 2019
Return-Path: <gcc-bugs-return-627621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64808 invoked by alias); 4 Jan 2019 13:39:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64481 invoked by uid 55); 4 Jan 2019 13:39:26 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Fri, 04 Jan 2019 13:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.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-87836-4-kMXe5iBqv0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00430.txt.bz2
Content-length: 6743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #24 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #23 from Gary Mills <gary_mills at fastmail dot fm> ---
> It's not Solaris, first of all. Solaris is a closed system once again. It's
> illumos, which is derived from Opensolaris. These are the two assemblers:
>
> This is on SPARC hardware:
> <mills@t2000:725>$ as -V
> as: Sun Compiler Common 12 SunOS_sparc snv_121 08/03/2009
> <mills@t2000:726>$ uname -a
> SunOS t2000 5.11 master-0-g5093b3b sun4v sparc SUNW,Sun-Fire-T200
>
> This is on x86 hardware:
> <mills@tyan:545>$ as -V
> as: Sun Compiler Common 12 SunOS_i386 snv_121 08/03/2009
> Usage: as [-V] [-Q{y,n}] [-s]
> [-S[aAbBcClL]] [-K {pic,PIC}] [-o objfile] [-L] [-T]
> [-P [[-Ipath] [-Dname] [-Dname=def] [-Uname]]...]
> [-m [-Ym,path]] [-n] [-xF] [-F] [-b] [-i] file.s ...
> <mills@tyan:546>$ uname -a
> SunOS tyan 5.11 illumos-8dfe5547fb i86pc i386 i86pc
as it happens, I still have copies of both assemblers from OpenSolaris
snv_147 BEs I still have around. Both are almost 10 years old by now,
way older than the oldest versions of as I test with:
ro@s10-sparc 11 > /usr/ccs/bin/as -V
/usr/ccs/bin/as: Studio 12.5 Compiler Common 12.5 SunOS_sparc Patch 05/02/2016
ro@s10-sparc 12 > /bin/uname -a
SunOS s10-sparc.gcc 5.10 Generic_150400-59 sun4v sparc sun4v
ro@zebrano 1 > /usr/ccs/bin/as -V
as: Studio 12.5 Compiler Common 12.5 SunOS_i386 Patch 03/07/2016
[...]
ro@zebrano 2 > /bin/uname -a
SunOS zebrano 5.10 Generic_150401-59 i86pc i386 i86pc
And with the removal of Solaris 10 support in GCC 10, even those soon
won't be tested any longer, Solaris 11.3 being the oldest version I'm
testing here.
> They seem to be the same. illumos does not have source for the assembler, only
They are not: sparc and x86 as are completely different code bases.
They are integrated into Solaris once in a while from the studio
consolidation, usually at the same time. Thus they get the same build
number (snv_121) at that time.
> the binaries. They can't be changed. illumos does have source for the
> linkers.
Overall, I wonder if pursuing this PR isn't a waste of all our time.
Both assemblers are almost 10 years old, and Solaris as has had its host
of problems. I've gotten some of them fixed over the years. It may be
more effective to just go for a recent gas instead.
> Yes, /usr/gcc/4.9/bin/gcc and /usr/gcc/4.9/bin/g++ are the 32-bit-default
> compilers. They will produce 64-bit binaries with the -m64 option. They are
> actually 4.9.4. I built the compilers myself, using gcc-4.4.4.
Good. I'm only asking since because we just had a problem with a
64-bit-default gcc used as a bootstrap compiler.
> I just tried a build of gcc-7 (gcc-7.3.0) with a minimal configuration. This
> is what appears in the oldest config.log:
>
> $
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
> CC=/usr/gcc/4.9/bin/gcc CXX=/usr/gcc/4.9/bin/g++ F77=/usr/gcc/4.9/bin/gfortran
> FC=/usr/gcc/4.9/bin/gfortran CFLAGS= -O3 -mno-app-regs CXXFLAGS= FFLAGS=
> FCFLAGS= LDFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib/pkgconfig --prefix=/usr/gcc/7
> --mandir=/usr/gcc/7/share/man --bindir=/usr/gcc/7/bin --libdir=/usr/gcc/7/lib
> --sbindir=/usr/gcc/7/sbin --sbindir=/usr/gcc/7/bin --libdir=/usr/gcc/7/lib
> --libexecdir=/usr/gcc/7/lib --host sparc-sun-solaris2.11 --build
> sparc-sun-solaris2.11 --target sparc-sun-solaris2.11 --without-gnu-ld
> --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
> LDFLAGS=-R/usr/gcc/7/lib
Could you please for simplicity's sake omit almost everything above?
Just CC, CXX, --without-gnu-{as,ld} --with-{as,ld}=/usr/bin/{as,ld}
> I also removed all of the patches except for one that modifies
> libgcc/config.host to create crtbeginS.o and crtendS.o. The build stopped
> quite early with this error:
>
> /usr/gcc/4.9/bin/g++ -std=gnu++98 -g -DIN_GCC -fno-exceptions -fno-rtti
> -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
> -Wcast-qual -Wno-format -Wmissing-format-attribute -Woverloaded-virtual
> -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
> -fno-common -DHAVE_CONFIG_H -DGENERATOR_FILE -fno-PIE -static-libstdc++
> -static-libgcc -R/usr/gcc/7/lib -o build/genmddeps \
> build/genmddeps.o build/read-md.o build/errors.o
> ../build-sparc-sun-solaris2.11/libiberty/libiberty.a
> build/genmddeps
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/common.md
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/config/sparc/sparc.md
>> tmp-mddeps
> /bin/bash: line 1: 28485 Bus Error (core dumped) build/genmddeps
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/common.md
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/gcc/config/sparc/sparc.md
>> tmp-mddeps
> Makefile:2240: recipe for target 's-mddeps' failed
> make[4]: *** [s-mddeps] Error 138
> make[4]: Leaving directory
> '/dpool/export/home/mills/Downloads/code/oi-userland-apr/components/developer/gcc-7/build/sparcv7/gcc'
>
> This is what gdb said about the core file:
>
> (gdb) bt
> #0 0x0001f7bc in __gnu_cxx::__mutex::__mutex (
> this=0x5007c <(anonymous namespace)::emergency_mutex>)
> at
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc49/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/ext/concurrence.h:132
> #1 __static_initialization_and_destruction_0 (__priority=65535,
> __initialize_p=1)
> at
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc49/gcc-4.9.4/libstdc++-v3/libsupc++/eh_alloc.cc:96
> #2 _GLOBAL__sub_I_eh_alloc.cc(void) ()
> at
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc49/gcc-4.9.4/libstdc++-v3/libsupc++/eh_alloc.cc:211
> #3 0x0002f19c in __do_global_ctors_aux ()
> #4 0x0002f1d4 in _init ()
> #5 0x000165f0 in _start ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb) quit
>
> The build didn't dump core at this point before. Something in the
> configuration must have changed its behavior.
But that's code generated by the bootstrap compiler, which is why I
asked to start with a vanilla build of gcc 4.9.
I may try a build on Solaris 10 with the snv_121 assembler myself.
The sparc machine is busy until tomorrow night; I may try a Solaris
10/x86 build instead since you say you're seeing the same error there.
>From gcc-bugs-return-627622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:41:25 2019
Return-Path: <gcc-bugs-return-627622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68393 invoked by alias); 4 Jan 2019 13:41:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68324 invoked by uid 48); 4 Jan 2019 13:41:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Fri, 04 Jan 2019 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88593-4-FJ11pTYWl6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00431.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Is anyone going to test the #c5 patch and submit if it passes?
>From gcc-bugs-return-627623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 13:44:55 2019
Return-Path: <gcc-bugs-return-627623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77263 invoked by alias); 4 Jan 2019 13: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 76941 invoked by uid 48); 4 Jan 2019 13:44:43 -0000
From: "eugene at hutorny dot in.ua" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] [7/8/9 Regression] c++17 internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Fri, 04 Jan 2019 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eugene at hutorny dot in.ua
X-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.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88690-4-fEiWNPRM4w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00432.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
--- Comment #10 from Eugene <eugene at hutorny dot in.ua> ---
(In reply to Jakub Jelinek from comment #8)
> Further reduced (-std=c++17):
> struct A { int a = 1; };
> struct B { int b = 0; };
> struct C { C () = delete; };
> struct D : public B, public C {};
> struct E : A { D f; } g{};
I think this particular example should be rejected by the compiler because
there is no means for constructing C;
The one below should compile indeed:
struct A { int a = 1; };
struct B { int b = 0; };
struct C { C() = default; C (const C&) = delete; };
struct D : public B, public C {};
struct E : A { D f; } g{};
>From gcc-bugs-return-627624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:11:04 2019
Return-Path: <gcc-bugs-return-627624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41352 invoked by alias); 4 Jan 2019 14:11:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41214 invoked by uid 48); 4 Jan 2019 14:10:59 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Fri, 04 Jan 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-84010-4-FeD7l4A2U1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00433.txt.bz2
Content-length: 386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot gnu.org
>From gcc-bugs-return-627625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:32:35 2019
Return-Path: <gcc-bugs-return-627625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20276 invoked by alias); 4 Jan 2019 14:32: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 20202 invoked by uid 48); 4 Jan 2019 14:32:31 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Fri, 04 Jan 2019 14:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88593-4-n0bQDDmIeU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00434.txt.bz2
Content-length: 326
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #6)
> Is anyone going to test the #c5 patch and submit if it passes?
We won't test it. We no longer use LCM to insert vxorps since LCM generates
vxorps inside the loop.
>From gcc-bugs-return-627626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:34:34 2019
Return-Path: <gcc-bugs-return-627626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22071 invoked by alias); 4 Jan 2019 14:34: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 21990 invoked by uid 48); 4 Jan 2019 14:34:28 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Fri, 04 Jan 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88593-4-FDiKVAP1f3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00435.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
--- Comment #8 from Jeffrey A. Law <law at redhat dot com> ---
That's an indication you've likely done something wrong with your local
properties HJ. LCM inherently also does LICM since LICM is just a special case
of PRE.
>From gcc-bugs-return-627627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:40:34 2019
Return-Path: <gcc-bugs-return-627627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34752 invoked by alias); 4 Jan 2019 14:40:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34689 invoked by uid 48); 4 Jan 2019 14:40:30 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Fri, 04 Jan 2019 14:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88593-4-SeNTwTyvDg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00436.txt.bz2
Content-length: 929
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
--- Comment #9 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jeffrey A. Law from comment #8)
> That's an indication you've likely done something wrong with your local
> properties HJ. LCM inherently also does LICM since LICM is just a special
> case of PRE.
The LCM algorithm isn't appropriate here since it may place a vxorps
inside the loop. Simple testcase show this:
$ cat badcase.c
extern float f;
extern double d;
extern int i;
void
foo (int n, int k)
{
for (int j = 0; j != n; j++)
if (j < k)
d = f;
}
It generates
...
loop:
if(j < k)
vxorps %xmm0, %xmm0, %xmm0
vcvtss2sd %xmm1, %xmm0, %xmm0
...
loopend
...
This is because LCM only works when there is a certain benifit. But for
conditional branch, LCM wouldn't move
vxorps %xmm0, %xmm0, %xmm0
out of loop. It's suboptimal.
>From gcc-bugs-return-627628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:44:11 2019
Return-Path: <gcc-bugs-return-627628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51236 invoked by alias); 4 Jan 2019 14:44:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51151 invoked by uid 48); 4 Jan 2019 14:44:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Fri, 04 Jan 2019 14:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88593-4-yVUoEMasZt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00437.txt.bz2
Content-length: 204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, is this actually a regression? I.e. is there a testcase that fails with
trunk?
>From gcc-bugs-return-627629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:46:30 2019
Return-Path: <gcc-bugs-return-627629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56614 invoked by alias); 4 Jan 2019 14:46: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 56451 invoked by uid 48); 4 Jan 2019 14:46:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Fri, 04 Jan 2019 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-88568-4-pH6hMUNyPN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00438.txt.bz2
Content-length: 2848
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |jsm28 at gcc dot gnu.org,
| |jyong at gcc dot gnu.org
Summary|[8/9 Regression] |[7/8/9 Regression]
|'dllimport' no longer |'dllimport' no longer
|implies 'extern' in C |implies 'extern' in C
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Guess it regressed with the PR24293 change then.
I think the problem is that handle_dll_attribute has for dllimport on
VAR_DECLs:
/* `extern' needn't be specified with dllimport.
Specify `extern' now and hope for the best. Sigh. */
DECL_EXTERNAL (node) = 1;
/* Also, implicitly give dllimport'd variables declared within
a function global scope, unless declared static. */
if (current_function_decl != NULL_TREE && !TREE_STATIC (node))
TREE_PUBLIC (node) = 1;
The problem is that the decl is previously TREE_STATIC and TREE_PUBLIC and
setting it also DECL_EXTERNAL results in an unusual combination of flags.
So, either we can tweak the code reporting the issues and hope TREE_STATIC &&
DECL_EXTERNAL means something reasonable elsewhere:
--- gcc/c/c-decl.c.jj 2019-01-01 12:37:48.628458597 +0100
+++ gcc/c/c-decl.c 2019-01-04 15:13:03.281213304 +0100
@@ -5100,7 +5100,8 @@ finish_decl (tree decl, location_t init_
if ((RECORD_OR_UNION_TYPE_P (TREE_TYPE (decl))
|| TREE_CODE (TREE_TYPE (decl)) == ENUMERAL_TYPE)
&& DECL_SIZE (decl) == NULL_TREE
- && TREE_STATIC (decl))
+ && TREE_STATIC (decl)
+ && !DECL_EXTERNAL (decl))
incomplete_record_decls.safe_push (decl);
if (is_global_var (decl) && DECL_SIZE (decl) != NULL_TREE)
or we should change handle_dll_attribute to:
--- gcc/attribs.c 2019-01-01 12:37:18.066960036 +0100
+++ gcc/attribs.c 2019-01-04 15:41:55.949812827 +0100
@@ -1691,6 +1691,7 @@ handle_dll_attribute (tree * pnode, tree
a function global scope, unless declared static. */
if (current_function_decl != NULL_TREE && !TREE_STATIC (node))
TREE_PUBLIC (node) = 1;
+ TREE_STATIC (node) = 0;
}
if (*no_add_attrs == false)
Joseph, is there any meaning for DECL_EXTERNAL & TREE_STATIC, or is that
invalid flag combination? If the latter, we should go with the latter patch,
but I'm afraid I have no access to Windows and no way to test.
>From gcc-bugs-return-627630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:47:55 2019
Return-Path: <gcc-bugs-return-627630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58922 invoked by alias); 4 Jan 2019 14:47: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 58835 invoked by uid 48); 4 Jan 2019 14:47:49 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88567] [9 Regression] ICE in get_initial_defs_for_reduction when building 521.wrf_r on AArch64 SVE
Date: Fri, 04 Jan 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88567-4-QjMluy7ALH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00439.txt.bz2
Content-length: 612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-04
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
I'll take a look.
>From gcc-bugs-return-627631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 14:53:12 2019
Return-Path: <gcc-bugs-return-627631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96557 invoked by alias); 4 Jan 2019 14:53:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96498 invoked by uid 48); 4 Jan 2019 14:53:08 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88593] [9 Regression] cleanup_cfg may make cached dominance info stale
Date: Fri, 04 Jan 2019 14:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88593-4-t0pdqIbpj8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00440.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88593
--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #10)
> So, is this actually a regression? I.e. is there a testcase that fails with
> trunk?
I believe this issue is latent on trunk.
>From gcc-bugs-return-627632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:06:48 2019
Return-Path: <gcc-bugs-return-627632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114432 invoked by alias); 4 Jan 2019 15:06: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 114373 invoked by uid 48); 4 Jan 2019 15:06:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88693] [9 Regression] Wrong code since r263018
Date: Fri, 04 Jan 2019 15:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to short_desc everconfirmed
Message-ID: <bug-88693-4-g2i77L1Xug@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00441.txt.bz2
Content-length: 1075
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88693
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Summary|[9 Regression] Wrong code |[9 Regression] Wrong code
|since r263511 |since r263018
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The actual bug is earlier, it is not a FE bug, but tree-ssa-strlen.c bug,
caused by r263018 change.
__attribute__((noipa)) void
foo (char *p)
{
if (__builtin_strlen (p) != 9)
__builtin_abort ();
}
int
main ()
{
static unsigned char u[9] = "abcdefghi";
char b[100];
__builtin_memcpy (b, u, sizeof (u));
b[sizeof (u)] = 0;
foo (b);
return 0;
}
>From gcc-bugs-return-627633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:19:48 2019
Return-Path: <gcc-bugs-return-627633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107969 invoked by alias); 4 Jan 2019 15:19: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 104365 invoked by uid 48); 4 Jan 2019 15:19:44 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88567] [9 Regression] ICE in get_initial_defs_for_reduction when building 521.wrf_r on AArch64 SVE
Date: Fri, 04 Jan 2019 15:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88567-4-Ly5WtoiL5Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00442.txt.bz2
Content-length: 259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
--- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
BTW, turns out that this is the same ICE as gcc.dg/vect/pr63379.c,
which was on my list of things to look at in stage 4.
>From gcc-bugs-return-627634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:22:09 2019
Return-Path: <gcc-bugs-return-627634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123647 invoked by alias); 4 Jan 2019 15:22:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123592 invoked by uid 48); 4 Jan 2019 15:22:05 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] New: Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00443.txt.bz2
Content-length: 1686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
Bug ID: 88695
Summary: Accepts invalid program with incompatible function
types.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
void f()
{
}
int main()
{
void (*g)(int) = 0;
&f == g;
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
No error messages outputed.
Expected behaviour:
An error message outputed.
The program is invalid due to the following paragraphs of the standard:
6.5.9/2:
"One of the following shall hold:
— both operands have arithmetic type;
— both operands are pointers to qualified or unqualified versions of
compatible types;
— one operand is a pointer to an object type and the other is a pointer to
a
qualified or unqualified version of void; or
— one operand is a pointer and the other is a null pointer constant."
6.7.3/15:
"... If one type has a parameter type list and the other type is specified by
a function definition that contains a (possibly empty) identifier list, both
shall agree in the number of parameters, and the type of each prototype
parameter shall be compatible with the type that results from the
application
of the default argument promotions to the type of the corresponding
identifier. ..."
>From gcc-bugs-return-627635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:26:09 2019
Return-Path: <gcc-bugs-return-627635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40558 invoked by alias); 4 Jan 2019 15:26:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40504 invoked by uid 55); 4 Jan 2019 15:26:04 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88685] [8/9 regression] pointer class array argument indexing
Date: Fri, 04 Jan 2019 15:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88685-4-865rerHCve@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00444.txt.bz2
Content-length: 639
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Fri, Jan 04, 2019 at 09:40:52AM +0000, antony at cosmologist dot info wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
>
> --- Comment #2 from Antony Lewis <antony at cosmologist dot info> ---
> I think the individual elements are correct, it's the array indexing operations
> that are wrong (this is clearer in the longer example; looks a like wrong
> stride). E.g. printing this in the main program after calling doit
>
Ah, yeah, that is what my small change to doit() shows.
>From gcc-bugs-return-627636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:27:07 2019
Return-Path: <gcc-bugs-return-627636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44134 invoked by alias); 4 Jan 2019 15: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 44088 invoked by uid 48); 4 Jan 2019 15:27:03 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 15:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88695-4-OqDAdgJZSV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00445.txt.bz2
Content-length: 213
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
--- Comment #1 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Correction:
The second standard reference should be 6.7.6.3/15 and not 6.7.3/15.
>From gcc-bugs-return-627637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:31:56 2019
Return-Path: <gcc-bugs-return-627637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68803 invoked by alias); 4 Jan 2019 15:31: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 68729 invoked by uid 48); 4 Jan 2019 15:31:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88695-4-B223rRn1Gb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00446.txt.bz2
Content-length: 145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
See PR 64526 and DR 317.
>From gcc-bugs-return-627639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:36:00 2019
Return-Path: <gcc-bugs-return-627639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107846 invoked by alias); 4 Jan 2019 15:35: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 107689 invoked by uid 48); 4 Jan 2019 15:35:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/83243] -fuse-ld=lld
Date: Fri, 04 Jan 2019 15:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-83243-4-SRVD95GT9m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83243-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83243-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00448.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83243
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dilyan.palauzov at aegee dot org
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
*** Bug 88691 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:35:59 2019
Return-Path: <gcc-bugs-return-627638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107715 invoked by alias); 4 Jan 2019 15:35:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107643 invoked by uid 48); 4 Jan 2019 15:35:54 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88691] Add support for -fuse-ld=lld (https://lld.llvm.org/)
Date: Fri, 04 Jan 2019 15:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-88691-4-awObFD5iZW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88691-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88691-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00447.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88691
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
This has already been done. Dup of bug 83243.
*** This bug has been marked as a duplicate of bug 83243 ***
>From gcc-bugs-return-627640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:36:21 2019
Return-Path: <gcc-bugs-return-627640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109482 invoked by alias); 4 Jan 2019 15:36:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109192 invoked by uid 48); 4 Jan 2019 15:36:16 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64526] No warning on function call with excessive arguments
Date: Fri, 04 Jan 2019 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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 resolution everconfirmed bug_severity
Message-ID: <bug-64526-4-VLbB1bDV6h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64526-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64526-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00449.txt.bz2
Content-length: 681
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64526
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|RESOLVED |NEW
Last reconfirmed| |2019-01-04
Resolution|INVALID |---
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Reopening as a request for a warning.
>From gcc-bugs-return-627641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:37:06 2019
Return-Path: <gcc-bugs-return-627641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110845 invoked by alias); 4 Jan 2019 15:37: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 110587 invoked by uid 48); 4 Jan 2019 15:37:02 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Fri, 04 Jan 2019 15:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-qMrdlf0vpt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00450.txt.bz2
Content-length: 166
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #9 from ktkachov at gcc dot gnu.org ---
For context, this is the hot loop in 557.xz_r from SPEC2017
>From gcc-bugs-return-627642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:43:31 2019
Return-Path: <gcc-bugs-return-627642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121688 invoked by alias); 4 Jan 2019 15:43:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121048 invoked by uid 48); 4 Jan 2019 15:43:25 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88567] [9 Regression] ICE in get_initial_defs_for_reduction when building 521.wrf_r on AArch64 SVE
Date: Fri, 04 Jan 2019 15:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88567-4-NvPUSSFppI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00451.txt.bz2
Content-length: 335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
--- Comment #5 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Created attachment 45345
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45345&action=edit
Candidate patch
I'll test the attached over the weekend. Seems to pass initial spot-testing.
>From gcc-bugs-return-627643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 15:46:39 2019
Return-Path: <gcc-bugs-return-627643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8312 invoked by alias); 4 Jan 2019 15:46:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8265 invoked by uid 48); 4 Jan 2019 15:46:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88693] [9 Regression] Wrong code since r263018
Date: Fri, 04 Jan 2019 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88693-4-bKLQntmEIA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00452.txt.bz2
Content-length: 253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88693
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45346
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45346&action=edit
gcc9-pr88693.patch
Untested fix.
>From gcc-bugs-return-627644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:17:46 2019
Return-Path: <gcc-bugs-return-627644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82336 invoked by alias); 4 Jan 2019 16:17: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 82141 invoked by uid 48); 4 Jan 2019 16:17:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Fri, 04 Jan 2019 16: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-6J70Y9LvKo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00453.txt.bz2
Content-length: 1616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If the compiler knew say from PGO that pos is usually a multiple of certain
power of two and that the loop usually iterates many times (I guess the latter
can be determined from comparing the bb count of the loop itself and its
header), it could emit something like:
static int func2(int max, int pos, unsigned char *cur)
{
unsigned char *p = cur + pos;
int len = 0;
if (max > 32 && (pos & 7) == 0)
{
int l = ((1 - ((uintptr_t) cur)) & 7) + 1;
while (++len != l)
if (p[len] != cur[len])
goto end;
unsigned long long __attribute__((may_alias)) *p2 = (unsigned long long
*) &p[len];
unsigned long long __attribute__((may_alias)) *cur2 = (unsigned long long
*) &cur[len];
while (len + 8 < max)
{
if (*p2++ != *cur2++)
break;
len += 8;
}
--len;
}
while (++len != max)
if (p[len] != cur[len])
break;
end:
return cur[len];
}
or so (untested). Of course, it could be done using SIMD too if there is a way
to terminate the loop if any of the elts is different and could be done in that
case at 16 or 32 or 64 characters at a time etc.
But, without knowing that pos is typically some power of two this would just
waste code size, dealing with the unaligned cases would be more complicated
(one can't read the next elt until proving that the current one is all equal),
so it would need to involve some rotations (or permutes for SIMD).
>From gcc-bugs-return-627645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:27:16 2019
Return-Path: <gcc-bugs-return-627645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37673 invoked by alias); 4 Jan 2019 16:27: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 37567 invoked by uid 55); 4 Jan 2019 16:27:11 -0000
From: "samtebbs at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9 Regression] aarch64 target testcases fail after r265398
Date: Fri, 04 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samtebbs at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-6ZYKtt0NqU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00454.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
--- Comment #10 from Sam Tebbs <samtebbs at gcc dot gnu.org> ---
Author: samtebbs
Date: Fri Jan 4 16:26:38 2019
New Revision: 267579
URL: https://gcc.gnu.org/viewcvs?rev=267579&root=gcc&view=rev
Log:
[PATCH][GCC][Aarch64] Change expected bfxil count in
gcc.target/aarch64/combine_bfxil.c to 18 (PR/87763)
gcc/testsuite/Changelog:
2019-01-04 Sam Tebbs <sam.tebbs@arm.com>
PR gcc/87763
* gcc.target/aarch64/combine_bfxil.c: Change scan-assembler-times bfxil
count to 18.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/gcc.target/aarch64/combine_bfxil.c
>From gcc-bugs-return-627646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:39:15 2019
Return-Path: <gcc-bugs-return-627646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103160 invoked by alias); 4 Jan 2019 16:39: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 103084 invoked by uid 48); 4 Jan 2019 16:39:11 -0000
From: "acsawdey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88027] PowerPC generates slightly weird code for memset
Date: Fri, 04 Jan 2019 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: acsawdey at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: acsawdey at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88027-4-uncYKLxVwq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88027-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88027-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00455.txt.bz2
Content-length: 447
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88027
acsawdey at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from acsawdey at gcc dot gnu.org ---
Backport to 8 tested ok and is now checked in as 267580.
>From gcc-bugs-return-627647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:40:11 2019
Return-Path: <gcc-bugs-return-627647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105714 invoked by alias); 4 Jan 2019 16:40: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 105519 invoked by uid 48); 4 Jan 2019 16:40:06 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Fri, 04 Jan 2019 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-GYUY5tWzAA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00456.txt.bz2
Content-length: 847
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> There are similar problems for other TLS models which can be relaxed, but
> even worse than this, local dynamic uses a sethi/xor for the offset from the
> defining module's block to load a signed 32-bit value, but since it's marked
> as SI I assume a spill/reload will truncate the top 32 bits and thus lose
> any sign extension if it's negative, breaking it even with linker relaxation
> disabled.
It turns out that this sethi/xor pair cannot generate a negative value
according to the calculation formulas of R_SPARC_TLS_LDO_HIX22 &
R_SPARC_TLS_LDO_LOX10 available at
https://docs.oracle.com/cd/E37838_01/html/E36783/man-tlsam.html
So, if the above formulas are incorrect, relaxation is required in all cases.
>From gcc-bugs-return-627648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:41:53 2019
Return-Path: <gcc-bugs-return-627648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109438 invoked by alias); 4 Jan 2019 16:41: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 109282 invoked by uid 48); 4 Jan 2019 16:41:48 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Fri, 04 Jan 2019 16:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-heo0au9oac@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00457.txt.bz2
Content-length: 2078
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #11 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #10)
> If the compiler knew say from PGO that pos is usually a multiple of certain
> power of two and that the loop usually iterates many times (I guess the
> latter can be determined from comparing the bb count of the loop itself and
> its header), it could emit something like:
> static int func2(int max, int pos, unsigned char *cur)
> {
> unsigned char *p = cur + pos;
> int len = 0;
> if (max > 32 && (pos & 7) == 0)
> {
> int l = ((1 - ((uintptr_t) cur)) & 7) + 1;
> while (++len != l)
> if (p[len] != cur[len])
> goto end;
> unsigned long long __attribute__((may_alias)) *p2 = (unsigned long
> long *) &p[len];
> unsigned long long __attribute__((may_alias)) *cur2 = (unsigned long
> long *) &cur[len];
> while (len + 8 < max)
> {
> if (*p2++ != *cur2++)
> break;
> len += 8;
> }
> --len;
> }
> while (++len != max)
> if (p[len] != cur[len])
> break;
> end:
> return cur[len];
> }
>
> or so (untested). Of course, it could be done using SIMD too if there is a
> way to terminate the loop if any of the elts is different and could be done
> in that case at 16 or 32 or 64 characters at a time etc.
> But, without knowing that pos is typically some power of two this would just
> waste code size, dealing with the unaligned cases would be more complicated
> (one can't read the next elt until proving that the current one is all
> equal), so it would need to involve some rotations (or permutes for SIMD).
Given it is compressing data both pointers will typically be misaligned. Pos
would be fairly random and len does not usually start from zero either. And
it's highly unlikely it will iterate more than a few bytes. Compression matches
are typically just a few bytes long. So unrolling is the only useful
optimization for this kind of code.
>From gcc-bugs-return-627649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:54:59 2019
Return-Path: <gcc-bugs-return-627649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33016 invoked by alias); 4 Jan 2019 16:54: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 32625 invoked by uid 48); 4 Jan 2019 16:54:55 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Fri, 04 Jan 2019 16:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-979lCQB49T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00458.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> So, if the above formulas are incorrect, relaxation is required in all cases.
...are correct...
>From gcc-bugs-return-627650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 16:56:43 2019
Return-Path: <gcc-bugs-return-627650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37955 invoked by alias); 4 Jan 2019 16:56:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37875 invoked by uid 48); 4 Jan 2019 16:56:37 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88363] [9 Regression] alloc_align attribute doesn't accept enumerated arguments
Date: Fri, 04 Jan 2019 16:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88363-4-R6V49N0l5C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00459.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88363
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-12/msg00740.html
>From gcc-bugs-return-627651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:02:19 2019
Return-Path: <gcc-bugs-return-627651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50142 invoked by alias); 4 Jan 2019 17:02:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50090 invoked by uid 48); 4 Jan 2019 17:02:14 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87964] c-attribs.c:3965: possible cut'n'paste error ?
Date: Fri, 04 Jan 2019 17:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status version resolution
Message-ID: <bug-87964-4-wG3ilm49bg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87964-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00460.txt.bz2
Content-length: 543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87964
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Version|8.0 |9.0
Resolution|--- |FIXED
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The typo was introduced in r265980 (GCC 9) and has been fixed in r266335.
>From gcc-bugs-return-627652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:15:59 2019
Return-Path: <gcc-bugs-return-627652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73962 invoked by alias); 4 Jan 2019 17:15:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68488 invoked by uid 48); 4 Jan 2019 17:15:34 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 17:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88695-4-wfRw8JSn9h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00461.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
--- Comment #3 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Yes, the type of f does have a prototype.
That fact is however not relevant here.
Note that I'm not making any calls to f here. I am only using f in a way
that requires its type to be compatible with void (int) .
The prototype mentioned in 6.7.3/15 refers to the prototype of the type void
(int) in this case.
>From gcc-bugs-return-627653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:17:16 2019
Return-Path: <gcc-bugs-return-627653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75384 invoked by alias); 4 Jan 2019 17:17: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 75320 invoked by uid 48); 4 Jan 2019 17:17:06 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 17:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88695-4-cbzRCnZ06L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00462.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
--- Comment #4 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
(In reply to Jonathan Wakely from comment #2)
> See PR 64526 and DR 317.
(Forgot to reply instead of adding an additional comment)
Yes, the type of f does have a prototype.
That fact is however not relevant here.
Note that I'm not making any calls to f here. I am only using f in a way
that requires its type to be compatible with void (int) .
The prototype mentioned in 6.7.3/15 refers to the prototype of the type void
(int) in this case.
>From gcc-bugs-return-627654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:19:36 2019
Return-Path: <gcc-bugs-return-627654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77190 invoked by alias); 4 Jan 2019 17:19:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77156 invoked by uid 48); 4 Jan 2019 17:19:30 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88647] Rejects valid program dereferencing pointer with incomplete reference type.
Date: Fri, 04 Jan 2019 17:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88647-4-3rdwzwrPdp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00463.txt.bz2
Content-length: 942
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88647
--- Comment #4 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #1)
> 6.3.2.1#2 (conversion of lvalues to rvalues): "If the lvalue has an
> incomplete type and does not have array type, the behavior is undefined.".
> Cf. bug 36941 (noting how DR#106 confuses things by allowing dereferences
> of pointers to qualified void).
(Incorrectly added an additional comment instead of replying)
What about this modified test case?
struct S *p;
void f(void);
int main()
{
f();
&*p;
}
struct S { int x; };
void f()
{
static struct S s = { 0 };
p = &s;
}
It gives the same error message (using the same compilation command line), and
there is no lvalue to rvalue conversion of *p in this case, because of the
operator & .
Clang accept that test case without any errors.
>From gcc-bugs-return-627655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:23:09 2019
Return-Path: <gcc-bugs-return-627655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79744 invoked by alias); 4 Jan 2019 17:23:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79671 invoked by uid 48); 4 Jan 2019 17:23:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88694] constexpr isn't captured correctly in lambda
Date: Fri, 04 Jan 2019 17:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88694-4-MgiVoS1IBE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00464.txt.bz2
Content-length: 1558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88694
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org,
| |redi at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase with no headers, clang++ -std=c++17 accepts this.
template <typename T, T U> struct A {
static constexpr T e = U;
constexpr operator int () { return e; }
};
template <typename T, T...> struct B {};
template <typename T, T U>
using C
#ifdef __clang__
= __make_integer_seq<B, T, U>;
#else
= B<T, __integer_pack(U)...>;
#endif
template <typename T, int, class U, int... M>
void foo (U f, B<int, M...>) { (f (A<T, M>{}), ...); }
template <typename T, T P, T O, class U>
void bar (U f) { foo<T, P> (f, C<T, O>{}); }
struct D { template <int> void print (); };
int
main ()
{
D d;
bar<int, 0, 3> ([&](auto i) { auto x = [&] { d.print<i>(); }; });
}
Older versions of g++ reject it with
‘__closure’ is not a constant expression
instead and before r248384 it is rejected because __integer_pack hasn't been
implemented.
>From gcc-bugs-return-627656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:25:09 2019
Return-Path: <gcc-bugs-return-627656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82069 invoked by alias); 4 Jan 2019 17: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 81920 invoked by uid 55); 4 Jan 2019 17:25:03 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Fri, 04 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery 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:
Message-ID: <bug-88568-4-EMlzy1CVeE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00465.txt.bz2
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Fri, 4 Jan 2019, jakub at gcc dot gnu.org wrote:
> Joseph, is there any meaning for DECL_EXTERNAL & TREE_STATIC, or is that
> invalid flag combination? If the latter, we should go with the latter patch,
> but I'm afraid I have no access to Windows and no way to test.
I think a gnu_inline function definition is both DECL_EXTERNAL and
TREE_STATIC.
>From gcc-bugs-return-627657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:32:36 2019
Return-Path: <gcc-bugs-return-627657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95031 invoked by alias); 4 Jan 2019 17:32: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 94957 invoked by uid 48); 4 Jan 2019 17:32:30 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] Hangs in libphobos testsuite
Date: Fri, 04 Jan 2019 17:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88654-4-sAbDUGR2Am@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00466.txt.bz2
Content-length: 1188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #5 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Jakub Jelinek from comment #4)
>
> If the test doesn't fail if it fails to load libcurl (and doesn't get
> stuck), it is fine too.
> If it fails if it is missing, yeah, something like a tcl procedure somewhere
> in libphobos/testsuite/lib/*.exp would do.
> As libphobos itself doesn't need libcurl-devel, it is just dlopen, so I
> think you want to test that
> #include <dlfcn.h>
>
> int
> main ()
> {
> void *h = dlopen ("libcurl.so.4"); // etc., whatever the library will try
> to dlopen
> ...
> }
> will succeed dlopening it.
The names it will try before giving up:
---
version (OSX)
static immutable names = ["libcurl.4.dylib"];
else version (Posix)
{
static immutable names = ["libcurl.so", "libcurl.so.4",
"libcurl-gnutls.so.4", "libcurl-nss.so.4", "libcurl.so.3"];
}
else version (Windows)
static immutable names = ["libcurl.dll", "curl.dll"];
---
I think a link test would be good enough, as iff curl exists, but it has a
different name to any of the above, then the std.net.curl module needs fixing.
>From gcc-bugs-return-627658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:36:11 2019
Return-Path: <gcc-bugs-return-627658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97618 invoked by alias); 4 Jan 2019 17:36: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 97570 invoked by uid 55); 4 Jan 2019 17:36:06 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88695-4-zSC7js6xkR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00467.txt.bz2
Content-length: 379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
It's DR#316 that's relevant here (where the committee agreed with my
interpretation that implies this example is valid, and reiterated their
intent not to fix issues with unprototyped functions in the standard), not
DR#317.
>From gcc-bugs-return-627659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:53:48 2019
Return-Path: <gcc-bugs-return-627659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4715 invoked by alias); 4 Jan 2019 17:53: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 858 invoked by uid 55); 4 Jan 2019 17:53:41 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Fri, 04 Jan 2019 17: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.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-87836-4-FBBNmA6tI6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00468.txt.bz2
Content-length: 793
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #25 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #24 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
[...]
> I may try a build on Solaris 10 with the snv_121 assembler myself.
> The sparc machine is busy until tomorrow night; I may try a Solaris
> 10/x86 build instead since you say you're seeing the same error there.
I've now completed c,c++-only bootstraps of gcc 7.4.0 with the snv_121
as on Solaris 10/SPARC and x86 without issues, using a self-compiled gcc
4.9.0 as bootstrap compiler.
Which brings me back to a previous suggestion: please try bootstrapping
a vanilla gcc 4.9.x yourself and use the result to build gcc
7.3.0/7.4.0.
>From gcc-bugs-return-627660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 17:54:26 2019
Return-Path: <gcc-bugs-return-627660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7383 invoked by alias); 4 Jan 2019 17:54: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 7292 invoked by uid 48); 4 Jan 2019 17:54:19 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Fri, 04 Jan 2019 17:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: jrtc27 at jrtc27 dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-4vWTq5ROes@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00469.txt.bz2
Content-length: 1700
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #11 from James Clarke <jrtc27 at jrtc27 dot com> ---
(In reply to Eric Botcazou from comment #9)
> > There are similar problems for other TLS models which can be relaxed, but
> > even worse than this, local dynamic uses a sethi/xor for the offset from the
> > defining module's block to load a signed 32-bit value, but since it's marked
> > as SI I assume a spill/reload will truncate the top 32 bits and thus lose
> > any sign extension if it's negative, breaking it even with linker relaxation
> > disabled.
>
> It turns out that this sethi/xor pair cannot generate a negative value
> according to the calculation formulas of R_SPARC_TLS_LDO_HIX22 &
> R_SPARC_TLS_LDO_LOX10 available at
> https://docs.oracle.com/cd/E37838_01/html/E36783/man-tlsam.html
>
> So, if the above formulas are [correct], relaxation is required in all cases.
Yes, for Local Dynamic itself, the offset will always be positive, since it's
the offset from the start of that module's TLS block. However, *all* TLS
models, including Local Dynamic, can currently be relaxed to Local Exec on
SPARC, which always generates negative offsets (Variant II, so static TLS
blocks come just before TP).
So, as far as I see it, we have two choices:
1. Disable all X -> LE relaxations in the linker. Works, but then gives
suboptimal performance if some code linked into an executable is built with
-fPIC rather than -fPIE (or nothing).
2. Apply this patch to GCC (assuming it still applies cleanly...).
I'm struggling to understand what you meant by "relaxation is required in all
cases"; did you mean *forbidden* in all cases (i.e. my point 1)?
>From gcc-bugs-return-627661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 18:02:48 2019
Return-Path: <gcc-bugs-return-627661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19169 invoked by alias); 4 Jan 2019 18:02:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19090 invoked by uid 48); 4 Jan 2019 18:02:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Fri, 04 Jan 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87431-4-ap6zrXxNhV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00470.txt.bz2
Content-length: 2470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Maybe like this:
--- a/libstdc++-v3/include/std/variant
+++ b/libstdc++-v3/include/std/variant
@@ -439,7 +439,7 @@ namespace __variant
constexpr bool
_M_valid() const noexcept
{
- if constexpr ((is_scalar_v<_Types> && ...))
+ if constexpr ((is_trivially_copyable_v<_Types> && ...))
return true;
return this->_M_index != __index_type(variant_npos);
}
@@ -1185,6 +1185,23 @@ namespace __variant
{
static_assert(_Np < sizeof...(_Types),
"The index should be in [0, number of alternatives)");
+
+ using type = variant_alternative_t<_Np, variant>;
+ // If constructing the value can throw but move assigning it can't,
+ // construct in a temporary and then move assign from it. This gives
+ // the strong exception safety guarantee, ensuring we never become
+ // valueless.
+ if constexpr (is_trivially_copyable_v<type>
+ && !is_nothrow_constructible_v<type, _Args...>)
+ {
+ // If move assignment cannot throw then we can provide the
+ // strong exception safety guarantee, and never become valueless.
+ variant __tmp(in_place_index<_Np>,
+ std::forward<_Args>(__args)...);
+ *this = std::move(__tmp);
+ return std::get<_Np>(*this);
+ }
+
this->~variant();
__try
{
@@ -1208,6 +1225,20 @@ namespace __variant
{
static_assert(_Np < sizeof...(_Types),
"The index should be in [0, number of alternatives)");
+
+ using type = variant_alternative_t<_Np, variant>;
+ if constexpr (is_trivially_copyable_v<type>
+ && !is_nothrow_constructible_v<type, initializer_list<_Up>,
+ _Args...>)
+ {
+ // If move assignment cannot throw then we can provide the
+ // strong exception safety guarantee, and never become valueless.
+ variant __tmp(in_place_index<_Np>, __il,
+ std::forward<_Args>(__args)...);
+ *this = std::move(__tmp);
+ return std::get<_Np>(*this);
+ }
+
this->~variant();
__try
{
>From gcc-bugs-return-627662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 18:12:51 2019
Return-Path: <gcc-bugs-return-627662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84415 invoked by alias); 4 Jan 2019 18:12: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 84357 invoked by uid 48); 4 Jan 2019 18:12:46 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Fri, 04 Jan 2019 18:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-qXENYTsysn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00471.txt.bz2
Content-length: 807
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #12 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
(> So, as far as I see it, we have two choices:
>
> 1. Disable all X -> LE relaxations in the linker. Works, but then gives
> suboptimal performance if some code linked into an executable is built with
> -fPIC rather than -fPIE (or nothing).
At least we could implement the possibility, even if not enabled by default.
See PR binutils/22740.
> 2. Apply this patch to GCC (assuming it still applies cleanly...).
Don't worry, the SPARC back-end doesn't move that fast. ;-)
> I'm struggling to understand what you meant by "relaxation is required in
> all cases"; did you mean *forbidden* in all cases (i.e. my point 1)?
Required in all cases to have a bug in the final code.
>From gcc-bugs-return-627663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 18:21:06 2019
Return-Path: <gcc-bugs-return-627663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91178 invoked by alias); 4 Jan 2019 18:21: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 91114 invoked by uid 48); 4 Jan 2019 18:21:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85517] std::variant exception safety problems
Date: Fri, 04 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ville.voutilainen at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85517-4-CwxKemR8mV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00472.txt.bz2
Content-length: 777
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85517
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Xiaoyi Zhang from comment #0)
> 2. Conversion assignment operator=(T&&)
> According to [variant.assign] 23.7.3.3 (11.3): if
> is_nothrow_constructible<Tj, T> == false &&
> is_nothrow_move_constructible<Tj> == true, equivalent to
> operator=(variant(std::forward<T>(t))).
>
> Failure case: If Tj has a nothrow move constructor, the standard requires
> strong guarantee (that a temporary variant be created first and move it into
> *this). The current implementation always invokes emplace(), which has only
> basic guarantee.
My patch on PR 87431 comment 10 fixes this, by giving emplace the strong
guarantee for such types.
>From gcc-bugs-return-627664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 18:25:47 2019
Return-Path: <gcc-bugs-return-627664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108826 invoked by alias); 4 Jan 2019 18:25:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108750 invoked by uid 48); 4 Jan 2019 18:25:42 -0000
From: "cand at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88696] New: Power VSX builtins missing vmuluwm / vector int vec_mul (vector int, vector int);
Date: Fri, 04 Jan 2019 18:25: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cand at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00473.txt.bz2
Content-length: 874
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88696
Bug ID: 88696
Summary: Power VSX builtins missing vmuluwm / vector int
vec_mul (vector int, vector int);
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: cand at gmx dot com
Target Milestone: ---
Target: ppc64le
Seems gcc is currently missing the VSX built-in that multiplies int vectors.
The vmuluwm instruction seems otherwise supported by gcc codegen.
vector int vec_mul (vector int, vector int);
vector unsigned int vec_mul (vector unsigned int, vector unsigned int);
It was added in ISA 2.07 aka POWER8. Apologies if the "target" component is not
the right place for this.
>From gcc-bugs-return-627665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 19:19:24 2019
Return-Path: <gcc-bugs-return-627665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99220 invoked by alias); 4 Jan 2019 19:19:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99113 invoked by uid 48); 4 Jan 2019 19:19:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88640] ICE in mark_reachable_handlers, at tree-eh.c:3926
Date: Fri, 04 Jan 2019 19:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
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-88640-4-DBUg8ncZPP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00474.txt.bz2
Content-length: 922
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88640
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
-Ofast -fsignaling-nans is a really weirdo combination of options, it says that
NaNs aren't honored, but sNaNs are, so in this case it folds a _7 = 1.0 * _2
that is marked that could throw into just _7 = _2; which can't throw (because
HONOR_SNANS is false due to HONOR_NANS being false).
Anyway, the ICE is because recip does:
gimple_stmt_iterator gsi = gsi_for_stmt (stmt);
gimple_assign_set_rhs_code (stmt, MULT_EXPR);
fold_stmt_inplace (&gsi);
update_stmt (stmt);
and fold_stmt_inplace doesn't do maybe_clean_eh_stmt and the caller
(tree-ssa-math-opts.c has many similar spots) don't do either. Or during
analysis phase of these optimizations we should just punt if any relevant stmts
can throw.
>From gcc-bugs-return-627666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 19:21:03 2019
Return-Path: <gcc-bugs-return-627666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101223 invoked by alias); 4 Jan 2019 19:21: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 101116 invoked by uid 48); 4 Jan 2019 19:20:55 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 19:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88653-4-OEI3tRaR11@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00475.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I have my eye on this one folks.
>From gcc-bugs-return-627667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 19:43:15 2019
Return-Path: <gcc-bugs-return-627667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27447 invoked by alias); 4 Jan 2019 19:43:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27377 invoked by uid 48); 4 Jan 2019 19:43:10 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88697] New: New test case gcc.target/powerpc/pr88457.c in r267307 fails because of glibc requirement
Date: Fri, 04 Jan 2019 19:43: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-88697-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00476.txt.bz2
Content-length: 1846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88697
Bug ID: 88697
Summary: New test case gcc.target/powerpc/pr88457.c in r267307
fails because of glibc requirement
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: ---
It is failing because it requires GLIBC 2.23 and newer and some (most) of our
test machines don't have that.
This sort of thing has come up before and I don't think anyone has ever come up
with a clean solution for it.
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.target/powerpc/pr88457.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -m32 -mcpu=power7 -O1 -fexpensive-optimizations
--param ira-max-conflict-table-size=0 --param max-cse-insns=3 -c -mcpu=e300c3
-S -o pr88457.s
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.target/powerpc/pr88457.c:6:6:
error: target_clones attribute needs GLIBC (2.23 and newer) that exports
hardware capability bits
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.target/powerpc/pr88457.c:6:6:
error: default 'target_clones' attribute was not set
compiler exited with status 1
FAIL: gcc.target/powerpc/pr88457.c (test for excess errors)
Excess errors:
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.target/powerpc/pr88457.c:6:6:
error: target_clones attribute needs GLIBC (2.23 and newer) that exports
hardware capability bits
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.target/powerpc/pr88457.c:6:6:
error: default 'target_clones' attribute was not set
>From gcc-bugs-return-627668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 19:47:03 2019
Return-Path: <gcc-bugs-return-627668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32547 invoked by alias); 4 Jan 2019 19:47:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32445 invoked by uid 48); 4 Jan 2019 19:46:59 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88695] Accepts invalid program with incompatible function types.
Date: Fri, 04 Jan 2019 19:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88695-4-PgKhsJ1XYt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88695-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00477.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88695
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #6 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Thanks for the explanation.
>From gcc-bugs-return-627669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 19:49:51 2019
Return-Path: <gcc-bugs-return-627669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35380 invoked by alias); 4 Jan 2019 19:49: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 35310 invoked by uid 48); 4 Jan 2019 19:49:46 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] New: Relax generic vector conversions
Date: Fri, 04 Jan 2019 19:49: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: husseydevin 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-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00478.txt.bz2
Content-length: 1227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
Bug ID: 88698
Summary: Relax generic vector conversions
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: husseydevin at gmail dot com
Target Milestone: ---
GCC is far too strict about vector conversions.
Currently, mixing generic vector extensions and platform-specific intrinsics
almost always requires either a cast or -flax-vector-extensions, which is
annoying and breaks a lot of things Clang happily accepts.
Here is my proposal:
* x86's __mNi should implicitly convert between any N-bit vector. This matches
the void pointer-like behavior of SSE's vectors.
* Any vector with equivalent lane types and number of lanes should convert
without an issue. For example, uint32_t vector_size(16) and NEON's uint32x4_t
have no reason not to be compatible.
* Signed <-> unsigned should act like other implicit signed <-> unsigned
conversions, -Wextra in C and warning in C++.
* Implicit conversions between different vectors of the same size should emit
an error.
>From gcc-bugs-return-627670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:02:54 2019
Return-Path: <gcc-bugs-return-627670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61307 invoked by alias); 4 Jan 2019 20:02: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 61159 invoked by uid 48); 4 Jan 2019 20:02:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87364] Pretty print of enumerator never prints the id, always falls back to C-style cast output
Date: Fri, 04 Jan 2019 20:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87364-4-jDAdnnL1Rk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87364-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00479.txt.bz2
Content-length: 1915
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87364
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Will Wray from comment #4)
> I reckon that demangling is the cause of the spurious warning.
> It seems that demangle continues to output enums with C-style cast:
>
> template type TreeVector<int, E::a>::Tree
> demangles as TreeVector<int, (E)0>::Tree
>
> Is this demangle angle a red-herring?
> Is the C-style cast mandated by Itanium CXXABI for enum output?
The ABI doesn't mandate how exactly it is demangled, but there is nothing in
the mangled name that would allow it to be demangled as E::a or a.
E.g. with
enum E { a = 0, b = 1 };
template <E e>
const char *foo (void) { return __PRETTY_FUNCTION__; }
void bar (void) { foo <a> (); foo <b> (); }
the mangled names are _Z3fooIL1E0EEPKcv and _Z3fooIL1E1EEPKcv and that is what
the ABI says; there is no way to recover that 0 is a and 1 is b.
__PRETTY_FUNCTION__ is const char* foo() [with E e = a] etc. (previously this
was [with E e = (E)0] ). Similarly, in .debug_info, DW_AT_name for the
functions used to be foo<(E)0> and now is foo<a>.
> Is demangler code even able to look up enumerators?
No.
> (I mean, does it have access to sufficient type information).
Demangler works just on a string, it doesn't have access to debuginfo etc.
I'd say we should revert to what we used to do when emitting stuff for RTTI or
debug info and do what your patch does only for compiler diagnostics.
Unlike the enumerator ids, the casts with exact constants are much easier to
handle for tools that don't have always full context.
>From gcc-bugs-return-627671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:09:07 2019
Return-Path: <gcc-bugs-return-627671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74233 invoked by alias); 4 Jan 2019 20:09:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74134 invoked by uid 48); 4 Jan 2019 20:09:01 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Fri, 04 Jan 2019 20:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-88698-4-pwTQGngbWr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00480.txt.bz2
Content-length: 302
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
It would help if you could write some (very short) functions illustrating the
behavior you are requesting. "convert", "compatible" all depend about the
context in which they appear.
>From gcc-bugs-return-627672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:36:47 2019
Return-Path: <gcc-bugs-return-627672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113839 invoked by alias); 4 Jan 2019 20:36: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 113745 invoked by uid 48); 4 Jan 2019 20:36:40 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] New: tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 04 Jan 2019 20:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00481.txt.bz2
Content-length: 1446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
Bug ID: 88699
Summary: tree check fail: expected function_decl, have
using_decl in add_method, at cp/class.c:1137
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Created attachment 45347
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45347&action=edit
gzipped C++ source code
For the attached C++ code, with recent gcc trunk, I get this:
$ ~/gcc/results/bin/gcc -c -w bug492.cc
bug492.cc:145738:16: internal compiler error: tree check: expected
function_decl, have using_decl in add_method, at cp/class.c:1137
145738 | class Mat<eT>::fixed : public Mat<eT>
| ^~~~~
0x7bbfe5 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
../../trunk/gcc/tree.c:9811
0x5e5f3d tree_check(tree_node*, char const*, int, char const*, tree_code)
../../trunk/gcc/tree.h:3176
0x5e5f3d add_method(tree_node*, tree_node*, bool)
../../trunk/gcc/cp/class.c:1137
0x8a4ac1 finish_struct(tree_node*, tree_node*)
../../trunk/gcc/cp/class.c:7149
I'll have my usual go at reducing the code and providing a range
of revisions where I think gcc trunk has gone wrong.
>From gcc-bugs-return-627673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:37:49 2019
Return-Path: <gcc-bugs-return-627673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116323 invoked by alias); 4 Jan 2019 20:37:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116281 invoked by uid 48); 4 Jan 2019 20:37:44 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 04 Jan 2019 20:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88699-4-fJykqyJvoW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00482.txt.bz2
Content-length: 187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
Bug seems to start someplace between revision 266950 and 267100.
>From gcc-bugs-return-627674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:39:37 2019
Return-Path: <gcc-bugs-return-627674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118147 invoked by alias); 4 Jan 2019 20:39: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 118064 invoked by uid 48); 4 Jan 2019 20:39:33 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/48200] Implement function attribute for symbol versioning (.symver)
Date: Fri, 04 Jan 2019 20:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-48200-4-eXmHRZvftl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48200-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48200-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00483.txt.bz2
Content-length: 601
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48200
--- Comment #28 from Florian Weimer <fw at gcc dot gnu.org> ---
It seems that using symbol aliases (via .symver) in conjunction with LTO and a
version script which has a local: * clause causes the LTO plugin to assume that
the aliased function definitions are not (externally) referenced, so GCC will
elide them. The workaround for now appears to be to put __attribute__
((externally_visible)) on the aliased functions, so that GCC assumes that there
is a reference to them that it cannot see.
-flto-partition=none may also be needed.
>From gcc-bugs-return-627675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:44:55 2019
Return-Path: <gcc-bugs-return-627675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74828 invoked by alias); 4 Jan 2019 20: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 74776 invoked by uid 48); 4 Jan 2019 20:44:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88188] ICE in print_operand, at config/rs6000/rs6000.c
Date: Fri, 04 Jan 2019 20:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88188-4-tUsSU1NwlJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88188-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88188-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00484.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88188
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Not worth backporting IMHO.
>From gcc-bugs-return-627676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:45:08 2019
Return-Path: <gcc-bugs-return-627676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79320 invoked by alias); 4 Jan 2019 20:45: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 75490 invoked by uid 48); 4 Jan 2019 20:45:00 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 04 Jan 2019 20:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
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-88699-4-XM5Kt99AYx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00485.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Most likely started with r267096.
>From gcc-bugs-return-627677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:46:25 2019
Return-Path: <gcc-bugs-return-627677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80772 invoked by alias); 4 Jan 2019 20:46: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 80271 invoked by uid 48); 4 Jan 2019 20:45:30 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] [9 Regression] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 04 Jan 2019 20:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88699-4-O7xj4v1EuT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00486.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
Summary|tree check fail: expected |[9 Regression] tree check
|function_decl, have |fail: expected
|using_decl in add_method, |function_decl, have
|at cp/class.c:1137 |using_decl in add_method,
| |at cp/class.c:1137
>From gcc-bugs-return-627678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 20:49:07 2019
Return-Path: <gcc-bugs-return-627678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84193 invoked by alias); 4 Jan 2019 20:49: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 83979 invoked by uid 48); 4 Jan 2019 20:48:58 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88654] Hangs in libphobos testsuite
Date: Fri, 04 Jan 2019 20:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88654-4-P3G6moUFbb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00487.txt.bz2
Content-length: 1957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88654
--- Comment #6 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
(In reply to Jakub Jelinek from comment #4)
>
> My i686-linux bootstraps are done through a couple of executable scripts in
> ~/hbin directory on x86_64-linux:
> for i in ~/hbin/*; do echo ===$i===; cat $i; done
> ===/home/jakub/hbin/as===
> #!/bin/sh
> exec /usr/bin/as --32 "$@"
> ===/home/jakub/hbin/g++===
> #!/bin/sh
> exec /usr/bin/g++ -m32 "$@"
> ===/home/jakub/hbin/gcc===
> #!/bin/sh
> exec /usr/bin/gcc -m32 "$@"
> ===/home/jakub/hbin/ld===
> #!/bin/sh
> case "$*" in
> --version) cat <<\EOF
> GNU ld version 2.20.52.0.1-10.fc17 20100131
> Copyright 2012 Free Software Foundation, Inc.
> This program is free software; you may redistribute it under the terms of
> the GNU General Public License version 3 or (at your option) a later version.
> This program has absolutely no warranty.
> EOF
> exit 0;;
> esac
> exec /usr/bin/ld -m elf_i386 -L /usr/lib/ "$@"
>
> and then
> PATH=~/hbin:$PATH i386 ../configure
> --enable-languages=default,obj-c++,lto,go,brig,d
> --enable-checking=yes,rtl,extra \
> && PATH=~/hbin:$PATH i386 make -j32 bootstrap > LOG 2>&1 \
> && PATH=~/hbin:$PATH i386 make -j32 -k check > LOGC 2>&1; \
> ../contrib/test_summary > LOGT 2>&1
> and that got stuck forever if libcurl.i?86 wasn't installed (only
> libcurl.x86_64 and libcurl-devel.x86_64), but works
> fine now that I also have libcurl.i?86 installed.
>
I can't say I followed this to the letter, but I could not reproduce.
RUNTESTFLAGS="unittests.exp" LIBRARY_PATH=/usr/lib32 PATH=~/hbin:$PATH \
i386 make check -j8; \
../contrib/test_summary
Naturally, the libphobos testsuite took over 660 seconds to finish. But still
it eventually ended.
Going to deal with [2] and [3] anyway to prevent hitting the timeout in the
first place anyway.
>From gcc-bugs-return-627679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 22:05:40 2019
Return-Path: <gcc-bugs-return-627679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121078 invoked by alias); 4 Jan 2019 22:05: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 121023 invoked by uid 48); 4 Jan 2019 22:05:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Fri, 04 Jan 2019 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88638-4-Ropr5MEZfF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00488.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
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> ---
I submitted the patch below for review. Dominique, if you have an opportunity
to test it on Darwin and let me know if there are any outstanding problems that
would be great.
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00181.html
>From gcc-bugs-return-627680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 22:29:27 2019
Return-Path: <gcc-bugs-return-627680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48433 invoked by alias); 4 Jan 2019 22:29: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 48359 invoked by uid 48); 4 Jan 2019 22:29:21 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88700] New: C11 Annex K builtins
Date: Fri, 04 Jan 2019 22:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00489.txt.bz2
Content-length: 1184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88700
Bug ID: 88700
Summary: C11 Annex K builtins
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jg at jguk dot org
Target Milestone: ---
Would GCC consider adding C11 Annex K safe functions as builtins?
I feel they would be very useful. Currently only we use them on MSCV builds.
Clang is thinking of adding these bultins - this is where the thread began
http://lists.llvm.org/pipermail/cfe-dev/2016-February/047149.html
As JF explains, they can just wrap regular builtins
(memcpy_s, memmove_s, strcpy_s, strncpy_s, strcat_s, strncat_s, strtok_s,
memset_s, strerror_s, strerrorlen_s, strnlen_s)
Saw this list of current GCC builtins
https://gcc.gnu.org/onlinedocs/gcc/Other-Builtins.html
glibc "stdint.h" would need this adding as well - should I open a glibc ticket
for that proposed change?
My code below:
#ifdef (__STDC_WANT_LIB_EXT1__)
#if __STDC_WANT_LIB_EXT1__ >= 1
#define RSIZE_MAX (SIZE_MAX >> 1)
#endif
#endif
>From gcc-bugs-return-627681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 22:31:30 2019
Return-Path: <gcc-bugs-return-627681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51820 invoked by alias); 4 Jan 2019 22:31: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 51786 invoked by uid 48); 4 Jan 2019 22:31:26 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88700] C11 Annex K builtins
Date: Fri, 04 Jan 2019 22:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88700-4-CZTOhglK5U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00490.txt.bz2
Content-length: 188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88700
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think this should be implemented in glibc rather than GCC first.
>From gcc-bugs-return-627683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 22:49:33 2019
Return-Path: <gcc-bugs-return-627683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79971 invoked by alias); 4 Jan 2019 22:49:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79656 invoked by uid 48); 4 Jan 2019 22:49:19 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88363] [9 Regression] alloc_align attribute doesn't accept enumerated arguments
Date: Fri, 04 Jan 2019 22:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88363-4-49pkt7yFFk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00492.txt.bz2
Content-length: 434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88363
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed in r267583.
>From gcc-bugs-return-627684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 22:49:38 2019
Return-Path: <gcc-bugs-return-627684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80546 invoked by alias); 4 Jan 2019 22:49:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79981 invoked by uid 55); 4 Jan 2019 22:49:32 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88363] [9 Regression] alloc_align attribute doesn't accept enumerated arguments
Date: Fri, 04 Jan 2019 22:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88363-4-xNxieJMXNn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00493.txt.bz2
Content-length: 880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88363
--- Comment #8 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Fri Jan 4 22:48:45 2019
New Revision: 267583
URL: https://gcc.gnu.org/viewcvs?rev=267583&root=gcc&view=rev
Log:
PR c/88363 - alloc_align attribute doesn't accept enumerated arguments
gcc/c-family/ChangeLog:
PR c/88363
* c-attribs.c (positional_argument): Also accept enumerated types.
gcc/testsuite/ChangeLog:
PR c/88363
* c-c++-common/attributes-4.c: New test.
gcc/ChangeLog:
PR c/88363
* doc/extend.texi (attribute alloc_align, alloc_size): Update.
Added:
trunk/gcc/testsuite/c-c++-common/attributes-4.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-attribs.c
trunk/gcc/doc/extend.texi
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 22:49:11 2019
Return-Path: <gcc-bugs-return-627682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78827 invoked by alias); 4 Jan 2019 22:49: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 78444 invoked by uid 48); 4 Jan 2019 22:48:45 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] New: Internal compiler error for valid program using compound literal with variably modified type.
Date: Fri, 04 Jan 2019 22:49: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: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00491.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
Bug ID: 88701
Summary: Internal compiler error for valid program using
compound literal with variably modified type.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
void f(int [(int (*)[*]) { 0 } == 0]);
int main()
{
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
Internal compiler error.
>From gcc-bugs-return-627685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:03:49 2019
Return-Path: <gcc-bugs-return-627685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99780 invoked by alias); 4 Jan 2019 23:03:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95966 invoked by uid 48); 4 Jan 2019 23:03:40 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] Internal compiler error for valid program using compound literal with variably modified type.
Date: Fri, 04 Jan 2019 23:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88701-4-r41G828Gl7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00494.txt.bz2
Content-length: 304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
--- Comment #1 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Another test case that also gives internal compiler error with the same
compilation command line:
void f(int n, int [(int (*)[n]) { 0 } == 0]);
int main()
{
}
>From gcc-bugs-return-627686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:20:51 2019
Return-Path: <gcc-bugs-return-627686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125155 invoked by alias); 4 Jan 2019 23:20:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125096 invoked by uid 55); 4 Jan 2019 23:20:45 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88700] C11 Annex K builtins
Date: Fri, 04 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88700-4-yaRCjH6AJZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00495.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88700
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Consensus in glibc is that Annex K is badly designed and should not be
supported at all. See
<http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1969.htm> proposing
obsoletion or removal.
>From gcc-bugs-return-627687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:29:34 2019
Return-Path: <gcc-bugs-return-627687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98001 invoked by alias); 4 Jan 2019 23:29:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97964 invoked by uid 48); 4 Jan 2019 23:29:29 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Fri, 04 Jan 2019 23:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on target_milestone short_desc everconfirmed
Message-ID: <bug-88701-4-vF9cUfjFt8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00496.txt.bz2
Content-length: 2202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-04
Target Milestone|--- |9.0
Summary|Internal compiler error for |[9 Regression] Internal
|valid program using |compiler error for valid
|compound literal with |program using compound
|variably modified type. |literal with variably
| |modified type.
Ever confirmed|0 |1
--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Does not appear with GCC 8 branch, so a regression, can someone bisect to find
what commit introduced this ICE?
internal compiler error: in get_parm_info, at c/c-decl.c:7517
0x5992b3 get_parm_info(bool, tree_node*)
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-decl.c:7517
0x7e92e7 c_parser_parms_list_declarator
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:4024
0x7e9403 c_parser_parms_declarator
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:3939
0x7e2ae9 c_parser_direct_declarator_inner
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:3868
0x7f8ead c_parser_declaration_or_fndef
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:1999
0x800bef c_parser_external_declaration
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:1653
0x801611 c_parser_translation_unit
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:1534
0x801611 c_parse_file()
/scratch/jmyers/fsf/gcc-mainline/gcc/c/c-parser.c:19807
0x853afb c_common_parse_file()
/scratch/jmyers/fsf/gcc-mainline/gcc/c-family/c-opts.c:1151
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-627688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:31:46 2019
Return-Path: <gcc-bugs-return-627688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100425 invoked by alias); 4 Jan 2019 23:31:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100309 invoked by uid 48); 4 Jan 2019 23:31:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] [9 Regression] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 04 Jan 2019 23:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-88699-4-mYrhQvbDwX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00497.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
CC| |jakub at gcc dot gnu.org,
| |nathan at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed, started with r267096.
>From gcc-bugs-return-627689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:32:40 2019
Return-Path: <gcc-bugs-return-627689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101654 invoked by alias); 4 Jan 2019 23:32: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 101597 invoked by uid 48); 4 Jan 2019 23:32:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88700] C11 Annex K builtins
Date: Fri, 04 Jan 2019 23:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.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: cc
Message-ID: <bug-88700-4-rtFNtFAfLk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00498.txt.bz2
Content-length: 899
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88700
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
A similar sentiment is also shared within WG14. See item 12 in section 6.1 of
the last meeting minutes for the two options under consideration (remove or
fix): http://www.open-std.org/jtc1/sc22/wg14/www/docs/n2307.pdf. Since there
is no proposal for fixing the problems it's unclear how it might impact the
APIs. Until that's resolved, implementing support for the current API would be
risky.
In the meantime, the C++ proposal for contracts has gained strong support and
might provide a superior alternative.
>From gcc-bugs-return-627690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:36:49 2019
Return-Path: <gcc-bugs-return-627690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104783 invoked by alias); 4 Jan 2019 23:36:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104709 invoked by uid 48); 4 Jan 2019 23:36:45 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Fri, 04 Jan 2019 23:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88701-4-apUxgfIGVP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00499.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r259641.
>From gcc-bugs-return-627691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:38:33 2019
Return-Path: <gcc-bugs-return-627691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107461 invoked by alias); 4 Jan 2019 23:38: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 107365 invoked by uid 48); 4 Jan 2019 23:38:29 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Fri, 04 Jan 2019 23:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88701-4-C7Xke9l8Oe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00500.txt.bz2
Content-length: 154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
--- Comment #4 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Thanks for the bisect.
>From gcc-bugs-return-627692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:44:38 2019
Return-Path: <gcc-bugs-return-627692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112227 invoked by alias); 4 Jan 2019 23:44: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 112173 invoked by uid 48); 4 Jan 2019 23:44:33 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] New: [6/7/8 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Fri, 04 Jan 2019 23:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00501.txt.bz2
Content-length: 1993
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
Bug ID: 88702
Summary: [6/7/8 regression] We do terrible job optimizing
IsHTMLWhitespace from Firefox
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
compiling:
int IsHTMLWhitespace(int aChar) {
return aChar == 0x0009 || aChar == 0x000A ||
aChar == 0x000C || aChar == 0x000D ||
aChar == 0x0020;
}
q(int a,int b, int c)
{
return IsHTMLWhitespace (a) && IsHTMLWhitespace (b) && IsHTMLWhitespace (c);
}
we do quite funny things by ipa-splitting IsHTMLWhitespace:
IsHTMLWhitespace (int aChar)
{
unsigned int aChar.1_1;
unsigned int _2;
_Bool _3;
_Bool _4;
_Bool _5;
int iftmp.0_6;
int iftmp.0_8;
<bb 2> [100.00%]:
aChar.1_1 = (unsigned int) aChar_7(D);
_2 = aChar.1_1 + 4294967287;
_3 = _2 <= 1;
_4 = aChar_7(D) == 12;
_5 = _3 | _4;
if (_5 != 0)
goto <bb 4>; [46.00%]
else
goto <bb 3>; [54.00%]
<bb 3> [54.00%]:
iftmp.0_8 = IsHTMLWhitespace.part.0 (aChar_7(D));
<bb 4> [100.00%]:
# iftmp.0_6 = PHI <1(2), iftmp.0_8(3)>
return iftmp.0_6;
}
this is partly caused by the fact that we are not able to optimize early the
sequence of compares to shift. In Firefox later we fail to inline the functions
and produce some terrible code which slows down rerf-reftest/dep-check-1.html
Firefox benchmark
>From gcc-bugs-return-627693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:50:20 2019
Return-Path: <gcc-bugs-return-627693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117680 invoked by alias); 4 Jan 2019 23:50: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 117531 invoked by uid 48); 4 Jan 2019 23:50:14 -0000
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88616] [9 Regression] ICE in gimplify_expr at gcc/gimplify.c:13363
Date: Fri, 04 Jan 2019 23:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: raj.khem 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88616-4-8lmOW8SAwp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00502.txt.bz2
Content-length: 328
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88616
--- Comment #4 from Khem Raj <raj.khem at gmail dot com> ---
I am seeing similar ICE when compiling QT 5.12 on armhf, I have a un-reduced
case but I think its same problem. Since the reduced case fails with my built
gcc as well, I can test it out once a fix is available.
>From gcc-bugs-return-627694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:53:49 2019
Return-Path: <gcc-bugs-return-627694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120820 invoked by alias); 4 Jan 2019 23:53:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120759 invoked by uid 48); 4 Jan 2019 23:53:44 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Fri, 04 Jan 2019 23:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-88653-4-TcN6X5E2Sb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00503.txt.bz2
Content-length: 1781
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I am getting a fail on FM308.f:
54 PASS
55 PASS
56 PASS
57 PASS
58 PASS
59 PASS
60 PASS
61 PASS
62 PASS
63 FAIL 0.88000E+00 0.00000E+00
----------------------------------------------
END OF PROGRAM FM308
1 TESTS FAILED
31 TESTS PASSED
0 TESTS DELETED
This is with my original test files and test script. So I do think something is
wrong. Test 63 is:
C **** FCVS PROGRAM 308 - TEST 063 ****
08640308
C
08650308
C TEST 063 ATTEMPTS TO OVERRIDE THE TYPING OF INTEGER FOR THE
08660308
C INTRINSIC FUNCTION MAX1 WITH TYPE-STATEMENT TYPING OF REAL.
08670308
C
08680308
Didn't someone just do some work on MAX1?
>From gcc-bugs-return-627695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 04 23:55:34 2019
Return-Path: <gcc-bugs-return-627695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122828 invoked by alias); 4 Jan 2019 23:55:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122778 invoked by uid 48); 4 Jan 2019 23:55:29 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88190] compile_options.allow_std does not allow to distinguish between GFC_STD_GNU and GFC_STD_LEGACY
Date: Fri, 04 Jan 2019 23:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88190-4-wP6HySYiOq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88190-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88190-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00504.txt.bz2
Content-length: 154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88190
--- Comment #10 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Any further thoughts on this?
>From gcc-bugs-return-627696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:15:58 2019
Return-Path: <gcc-bugs-return-627696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18975 invoked by alias); 5 Jan 2019 00:15: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 18422 invoked by uid 48); 5 Jan 2019 00:15:07 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Sat, 05 Jan 2019 00:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-qXP2I3B5pC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00505.txt.bz2
Content-length: 1727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #2 from emsr at gcc dot gnu.org ---
I have this in another tree which solves the inf issue:
namespace __detail
{
// Avoid including all of <algorithm>
template<typename _Tp>
constexpr _Tp
__fmax3(_Tp __x, _Tp __y, _Tp __z)
{ return std::fmax(std::fmax(__x, __y), std::fmax(__y, __z)); }
template<typename _Tp>
constexpr _Tp
__hypot3(_Tp __x, _Tp __y, _Tp __z)
{
if (std::isnan(__x)
|| std::isnan(__y)
|| std::isnan(__z))
return std::numeric_limits<_Tp>::quiet_NaN();
else
{
__x = std::abs(__x);
__y = std::abs(__y);
__z = std::abs(__z);
const auto __amax = __fmax3(__x, __y, __z);
if (__amax == _Tp{0})
return _Tp{0};
else if (std::__detail::__isinf(__amax))
return std::numeric_limits<_Tp>::infinity();
else
{
__x /= __amax;
__y /= __amax;
__z /= __amax;
return __amax * std::sqrt(__x * __x + __y * __y + __z * __z);
}
}
}
}
I get your point about scaling and adding smallest first. I have access to
std::fma().
For me I think this means:
/*
const auto __amax = max(max(__x, __y), __z);
const auto __l0 = min(__z, max(__x, __y));
const auto __l1 = min(__y, __x);
const auto __scale = 1 / __amax;
__l0 *= __scale;
__l1 *= __scale;
// Add the two smaller values first.
const auto __lo = __l0 * __l0 + __l1 * __l1;
const auto __r = __amax * sqrt(fma(__h1, __h1, __lo));
*/
>From gcc-bugs-return-627697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:26:10 2019
Return-Path: <gcc-bugs-return-627697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34781 invoked by alias); 5 Jan 2019 00:26:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34253 invoked by uid 48); 5 Jan 2019 00:26:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] [9 Regression] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Sat, 05 Jan 2019 00:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-88699-4-AccIMYGu6y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00506.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|ice-on-invalid-code |
Priority|P3 |P1
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase:
template <typename>
struct A {
void operator= (int);
template <int> class B;
};
template <typename C>
template <int>
struct A<C>::B : A {
using A::operator=;
void operator= (B);
};
>From gcc-bugs-return-627698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:29:10 2019
Return-Path: <gcc-bugs-return-627698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39450 invoked by alias); 5 Jan 2019 00: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 39389 invoked by uid 48); 5 Jan 2019 00:29:06 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/69101] [F03] IEEE_SELECTED_REAL_KIND is not generic
Date: Sat, 05 Jan 2019 00: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc assigned_to
Message-ID: <bug-69101-4-RNHIeG1TLr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00507.txt.bz2
Content-length: 575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69101
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |kargl at gcc dot gnu.org
Assignee|fxcoudert at gcc dot gnu.org |kargl at gcc dot gnu.org
--- Comment #11 from kargl at gcc dot gnu.org ---
I have a part 1 patch that addresses IEEE_SELECTED_REAL_KIND
in an initialization expression.
>From gcc-bugs-return-627699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:35:54 2019
Return-Path: <gcc-bugs-return-627699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44902 invoked by alias); 5 Jan 2019 00:35:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44857 invoked by uid 48); 5 Jan 2019 00:35:48 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 00:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88698-4-RrWR7LL9Io@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00508.txt.bz2
Content-length: 2964
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #2 from Devin Hussey <husseydevin at gmail dot com> ---
What I am saying is that I think -flax-vector-conversions should be default, or
we should only have minimal warnings instead of errors.
That will make generic vectors much easier to use.
It is to be noted that Clang has -Wvector-conversion, which is the equivalent
of -fno-lax-vector-conversions, however, it is a warning that only occurs with
-Weverything. Not even -Wall -Wextra -Wpedantic in C++ mode will enable it.
If Clang thinks this is such a minor issue that it won't even warn with -Wall
-Wextra -Wpedantic, why does GCC consider it an error?
However, if you want examples, here:
Example 1 (SSE2)
Here, we are trying to use an intrinsic which accepts and returns an __m128i
(defined as "long long __attribute__((vector_size(16)))") with a u32x4 (defined
as "uint32_t __attribute__((vector_size(16)))")
#include <emmintrin.h>
#include <stdint.h>
typedef uint32_t u32x4 __attribute__((vector_size(16)));
u32x4 shift(u32x4 val)
{
return _mm_srli_epi32(val, 15);
}
On Clang, it will happily accept that, only complaining on -Wvector-conversion.
GCC will fail to compile.
There are three ways around that:
1. Typedef u32x4 to __m128i. This is unreasonable, because that causes the
operator overloads and constructors to operate on 64-bit integers instead of
32-bit.
2. Add -flax-vector-conversions. Requiring someone to add a warning suppression
flag to compile your code is often seen as code smell.
3. Cast. Good lord, if you thought intrinsics were ugly, this will change your
mind:
return (u32x4)_mm_srli_epi32((__m128i)val, 15);
or C++-style:
return static_cast<u32x4>(_mm_srli_epi32(static_cast<__m128i>(val), 15));
Example 2 (ARMv7-a + NEON):
#include <arm_neon.h>
_Static_assert(sizeof(unsigned long) == sizeof(unsigned int), "use 32-bit
please");
typedef unsigned long u32x4 __attribute__((vector_size(16)));
u32x4 shift(u32x4 val)
{
return vshrq_n_u32(val, 15);
}
This is the second issue: unsigned long and unsigned int are the same size and
should have no issues converting between each other.
This often comes from a situation where uint32_t is set to unsigned long.
Example 3 (Generic):
typedef unsigned u32x4 __attribute__((vector_size(16)));
typedef unsigned long long u64x2 __attribute__((vector_size(16)));
u64x2 cast(u32x4 val)
{
return val;
}
This should emit a warning without a cast. I would recommend an error, but
Clang without -Wvector-conversion accepts this without any complaining.
Example 4 (Generic):
typedef unsigned u32x2 __attribute__((vector_size(8)));
typedef unsigned long long u64x2 __attribute__((vector_size(16)));
u64x2 cast(u32x2 val)
{
return val;
}
This is clearly an error. There should be __builtin_convertvector which is
being tracked in a different bug, but that is not the point.
>From gcc-bugs-return-627700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:37:51 2019
Return-Path: <gcc-bugs-return-627700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46583 invoked by alias); 5 Jan 2019 00:37: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 46502 invoked by uid 48); 5 Jan 2019 00:37:47 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sat, 05 Jan 2019 00:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-88653-4-RVIgHOWjgW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00509.txt.bz2
Content-length: 243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #10 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Didn't someone just do some work on MAX1?
pr88658, fix at https://gcc.gnu.org/ml/fortran/2019-01/msg00006.html.
>From gcc-bugs-return-627701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:40:55 2019
Return-Path: <gcc-bugs-return-627701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57703 invoked by alias); 5 Jan 2019 00:40: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 57161 invoked by uid 48); 5 Jan 2019 00:40:49 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 00:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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-88698-4-w2m55elir8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00510.txt.bz2
Content-length: 571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
At one point -flax-vector-conversions was default and did the option did not
exist.
https://gcc.gnu.org/ml/gcc/2006-10/msg00682.html
See also:
https://gcc.gnu.org/ml/gcc/2006-11/msg00051.html
NOTE having this option on is required to be complaint with both the Altivec
and SPU PEMs. I remember when this discussion was happening since I was
working on PowerPC and I even voted against having an option to allowing the
lax conversion part.
>From gcc-bugs-return-627702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:49:06 2019
Return-Path: <gcc-bugs-return-627702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66694 invoked by alias); 5 Jan 2019 00:49: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 66463 invoked by uid 48); 5 Jan 2019 00:48:58 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 00:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88698-4-JetuVZZjVN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00511.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Devin Hussey from comment #2)
> It is to be noted that Clang has -Wvector-conversion, which is the
> equivalent of -fno-lax-vector-conversions, however, it is a warning that
> only occurs with -Weverything. Not even -Wall -Wextra -Wpedantic in C++ mode
> will enable it.
Sounds like clang decided to emulate GCC 3.4.x behavior and follow newer GCC's
behavior.
>From gcc-bugs-return-627703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:52:45 2019
Return-Path: <gcc-bugs-return-627703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74981 invoked by alias); 5 Jan 2019 00:52: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 74775 invoked by uid 48); 5 Jan 2019 00:52:40 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88703] New: oacc_validate_dims allows invalid dimensions
Date: Sat, 05 Jan 2019 00:52: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88703-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00512.txt.bz2
Content-length: 5860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88703
Bug ID: 88703
Summary: oacc_validate_dims allows invalid dimensions
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider oacc_validate_dims on trunk:
...
oacc_validate_dims (tree fn, tree attrs, int *dims, int level, unsigned used)
{
tree purpose[GOMP_DIM_MAX];
unsigned ix;
tree pos = TREE_VALUE (attrs);
/* Make sure the attribute creator attached the dimension
information. */
gcc_assert (pos);
for (ix = 0; ix != GOMP_DIM_MAX; ix++)
{
purpose[ix] = TREE_PURPOSE (pos);
tree val = TREE_VALUE (pos);
dims[ix] = val ? TREE_INT_CST_LOW (val) : -1;
pos = TREE_CHAIN (pos);
}
bool changed = targetm.goacc.validate_dims (fn, dims, level);
/* Default anything left to 1 or a partitioned default. */
for (ix = 0; ix != GOMP_DIM_MAX; ix++)
if (dims[ix] < 0)
{
/* The OpenACC spec says 'If the [num_gangs] clause is not
specified, an implementation-defined default will be used;
the default may depend on the code within the construct.'
(2.5.6). Thus an implementation is free to choose
non-unity default for a parallel region that doesn't have
any gang-partitioned loops. However, it appears that there
is a sufficient body of user code that expects non-gang
partitioned regions to not execute in gang-redundant mode.
So we (a) don't warn about the non-portability and (b) pick
the minimum permissible dimension size when there is no
partitioned execution. Otherwise we pick the global
default for the dimension, which the user can control. The
same wording and logic applies to num_workers and
vector_length, however the worker- or vector- single
execution doesn't have the same impact as gang-redundant
execution. (If the minimum gang-level partioning is not 1,
the target is probably too confusing.) */
dims[ix] = (used & GOMP_DIM_MASK (ix)
? oacc_default_dims[ix] : oacc_min_dims[ix]);
changed = true;
}
if (changed)
{
/* Replace the attribute with new values. */
pos = NULL_TREE;
for (ix = GOMP_DIM_MAX; ix--;)
pos = tree_cons (purpose[ix],
build_int_cst (integer_type_node, dims[ix]), pos);
oacc_replace_fn_attrib (fn, pos);
}
}
...
It does the following:
- read the dimensions set in the attributes
- call targetm.goacc.validate_dims on those dimensions
- apply oacc_default_dims[ix] or oacc_min_dims[ix] to set remaining unset
dimensions
- update the dimensions in the attributes
However, it's possible that the resulting dimensions are in fact invalid.
Consider this test-case on og8 branch:
...
$ cat libgomp/testsuite/libgomp.oacc-c-c++-common/test.c
/* { dg-do run { target openacc_nvidia_accel_selected } } */
/* { dg-additional-options "-fopenacc-dim=:32
-foffload=-mlong-vector-in-workers" } */
#include <stdlib.h>
#define N 2048
unsigned int a[N];
unsigned int b[N];
unsigned int c[N];
unsigned int n = N;
int
main (void)
{
#pragma acc parallel vector_length (128) copyin (a,b) copyout (c)
{
#pragma acc loop worker
for (unsigned int i = 0; i < n; i++)
#pragma acc loop vector
for (unsigned int j = 0; j < n; j++)
;
}
return 0;
}
...
This generates these dimensions in the .s file:
...
//:FUNC_MAP "main$_omp_fn$0", 0x1, 0x20, 0x80
...
so, num_workers * vector_length == 0x20 * 0x80 == 32 * 128 == 4096 (while the
maximum allowed is 1024 == maximum CTA size).
This causes a runtime error:
...
libgomp: The Nvidia accelerator has insufficient resources to launch
'main$_omp_fn$0' with num_workers = 32 and vector_length = 128; recompile the
program with 'num_workers = x and vector_length = y' on that offloaded region
or '-fopenacc-dim=-:x:y' where x * y <= 1024.
...
An easy way to detect this problem at compile time is by adding an assert here:
...
diff --git a/gcc/omp-offload.c b/gcc/omp-offload.c
index aac0aa8b27a..7e3efa1032e 100644
--- a/gcc/omp-offload.c
+++ b/gcc/omp-offload.c
@@ -700,6 +700,7 @@ oacc_validate_dims
? oacc_default_dims[ix] : oacc_min_dims[ix]);
changed = true;
}
+ gcc_assert (!targetm.goacc.validate_dims (fn, dims, level));
if (changed)
{
...
For the test-case, the compiler will enter the second call to
targetm.goacc.validate_dims with dims {1, 32, 128}, which will be updated to
{1, 32, 32}, which will cause targetm.goacc.validate_dims to return true, which
will trigger the assert.
AFAIU, this is a generic problem with the targetm.goacc.validate_dims hook on
both trunk and og8, and not specific to nvptx.
>From gcc-bugs-return-627705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:58:40 2019
Return-Path: <gcc-bugs-return-627705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38008 invoked by alias); 5 Jan 2019 00:58: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 37890 invoked by uid 48); 5 Jan 2019 00:58:33 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88546] Copy attribute unusable for weakrefs
Date: Sat, 05 Jan 2019 00:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88546-4-b4IFbPpGNK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88546-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88546-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00514.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88546
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed via r267591.
>From gcc-bugs-return-627704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 00:58:08 2019
Return-Path: <gcc-bugs-return-627704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37039 invoked by alias); 5 Jan 2019 00:58: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 36954 invoked by uid 55); 5 Jan 2019 00:58:02 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88546] Copy attribute unusable for weakrefs
Date: Sat, 05 Jan 2019 00:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88546-4-eIdU9eYjNx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88546-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88546-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00513.txt.bz2
Content-length: 1336
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88546
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Sat Jan 5 00:57:30 2019
New Revision: 267591
URL: https://gcc.gnu.org/viewcvs?rev=267591&root=gcc&view=rev
Log:
PR c/88546 - Copy attribute unusable for weakrefs
gcc/c-family/ChangeLog:
PR c/88546
* c-attribs.c (handle_copy_attribute): Avoid copying attribute leaf.
Handle C++ empty throw specification and C11 _Noreturn.
(has_attribute): Also handle C11 _Noreturn.
gcc/ChangeLog:
PR c/88546
* attribs.c (decls_mismatched_attributes): Avoid warning for attribute
leaf.
gcc/testsuite/ChangeLog:
PR c/88546
* g++.dg/ext/attr-copy.C: New test.
* gcc.dg/attr-copy-4.c: Disable macro expansion tracking.
* gcc.dg/attr-copy-6.c: New test.
* gcc.dg/attr-copy-7.c: New test.
Added:
trunk/gcc/testsuite/g++.dg/ext/attr-copy.C
trunk/gcc/testsuite/gcc.dg/attr-copy-6.c
trunk/gcc/testsuite/gcc.dg/attr-copy-7.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/attribs.c
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-attribs.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/attr-copy-4.c
trunk/libgcc/gthr-posix.h
trunk/libgfortran/libgfortran.h
>From gcc-bugs-return-627706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 01:03:16 2019
Return-Path: <gcc-bugs-return-627706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43942 invoked by alias); 5 Jan 2019 01:03:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43872 invoked by uid 48); 5 Jan 2019 01:03:10 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 01:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88698-4-5lNkm84Nlg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00515.txt.bz2
Content-length: 936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #5 from Devin Hussey <husseydevin at gmail dot com> ---
Well, if we are aiming for strict compliance, might as well throw out every GCC
extension in existence (including vector extensions), those aren't strictly
compliant to the C/C++ standard. /s
The whole point of extensions are to be an extension that violates the
standard.
#include <arm_neon.h>
uint64x2_t mult(uint64x2_t top, uint64x2_t bot)
{
return top * bot;
}
I am breaking two rules here:
1. Using operator overloads, which are not part of the standard.
2. Implying a nonexistent instruction, as there is no vmul.i64. (it is
scalarized at the moment, but I explained in bug 88510 that there are better
options)
Clang even allows this:
#include <arm_neon.h>
uint32x4_t mult(uint16x8_t top, uint32x4_t bot)
{
return top * bot;
}
In which it will reinterpret all to the widest lane type.
>From gcc-bugs-return-627707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 01:04:51 2019
Return-Path: <gcc-bugs-return-627707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45700 invoked by alias); 5 Jan 2019 01:04: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 45635 invoked by uid 48); 5 Jan 2019 01:04:47 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88430] -Wmissing-attributes warnings when including libquadmath headers
Date: Sat, 05 Jan 2019 01: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: 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-88430-4-QGVySOuDTj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88430-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88430-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00516.txt.bz2
Content-length: 1428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88430
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
With the patch referenced in comment #5 and with bug 88546 fixed there are no
-Wmissing-attributes warnings in GCC builds.
For reference, the following is the warning breakdown from my bootstrap on
x86_64-linux with the patch for pr88546 applied:
Diagnostic Count Unique Files
-Wmisleading-indentation 43 27 27
-Wimplicit-function-declaration 20 5 3
-Wimplicit-fallthrough= 12 1 1
-Wmaybe-uninitialized 10 5 4
-Wcast-function-type 7 4 3
-Waddress-of-packed-member 7 7 1
-Wpragmas 6 1 1
-Wstringop-truncation 5 1 1
-Wformat-truncation= 5 3 1
-Wincompatible-pointer-types 4 2 1
-Walloca-larger-than= 4 2 1
-Wsign-compare 2 1 1
>From gcc-bugs-return-627708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 01:16:43 2019
Return-Path: <gcc-bugs-return-627708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56565 invoked by alias); 5 Jan 2019 01: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 56493 invoked by uid 48); 5 Jan 2019 01:16:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [6/7/8 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Sat, 05 Jan 2019 01:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88702-4-CFqb6LshtK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00517.txt.bz2
Content-length: 543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
With what options? I'm getting 3 bit tests both with -O2 and -O3, both when
using C and C++. And get that also if I rewrite the function to use a switch
instead.
>From gcc-bugs-return-627709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 01:18:46 2019
Return-Path: <gcc-bugs-return-627709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58586 invoked by alias); 5 Jan 2019 01:18: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 58556 invoked by uid 48); 5 Jan 2019 01:18:42 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88704] New: Accepts invalid program with [*] outside function prototype scope.
Date: Sat, 05 Jan 2019 01:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00518.txt.bz2
Content-length: 851
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88704
Bug ID: 88704
Summary: Accepts invalid program with [*] outside function
prototype scope.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
void f(a)
int a[*];
{
}
int main()
{
}
Compilation command line:
gcc prog.c -std=c11 -pedantic-errors
Observed behaviour:
No error message outputed.
Expected behaviour:
An error message outputed.
The program is invalid because [*] occurs outside function prototype scope.
Note:
Clang gives the expected error message.
>From gcc-bugs-return-627710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 01:25:20 2019
Return-Path: <gcc-bugs-return-627710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62731 invoked by alias); 5 Jan 2019 01:25: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 62253 invoked by uid 55); 5 Jan 2019 01:24:36 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [6/7/8 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Sat, 05 Jan 2019 01:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
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-88702-4-mQBTJZfcHp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00519.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
--- Comment #2 from Jan Hubicka <hubicka at ucw dot cz> ---
> With what options? I'm getting 3 bit tests both with -O2 and -O3, both when
> using C and C++. And get that also if I rewrite the function to use a switch
> instead.
-O2 -flto and then look into release_ssa dump.
In Firefox we then fail to inline things back together. I am debugging
that but already producing that at firstplace is bad.
>From gcc-bugs-return-627711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 01:49:18 2019
Return-Path: <gcc-bugs-return-627711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87525 invoked by alias); 5 Jan 2019 01:49: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 87236 invoked by uid 48); 5 Jan 2019 01:48:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [6/7/8 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Sat, 05 Jan 2019 01:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88702-4-7LZaIUhQns@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00520.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The only pass that can do about this (at least right now) is reassoc (both 1
and 2), which is too late for inlining. So, either teach fnsplit not to
separate multiple if comparisons of the same variable against constants, or
schedule reasoc or just the maybe_optimize_range_tests part thereof in some
early pass.
>From gcc-bugs-return-627712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:03:06 2019
Return-Path: <gcc-bugs-return-627712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45765 invoked by alias); 5 Jan 2019 03: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 45666 invoked by uid 48); 5 Jan 2019 03:02:57 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] New: [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 03:03: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: husseydevin 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-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00521.txt.bz2
Content-length: 2827
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
Bug ID: 88705
Summary: [ARM][Generic Vector Extensions] float32x4/float64x2
vector operator overloads scalarize on NEON
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: husseydevin at gmail dot com
Target Milestone: ---
For some reason, GCC scalarizes float32x4_t and float64x2_t on ARM32 NEON when
using vector extensions.
typedef float f32x4 __attribute__((vector_size(16)));
typedef double f64x2 __attribute__((vector_size(16)));
f32x4 fmul (f32x4 v1, f32x4 v2)
{
return v1 * v2;
}
f64x2 dmul (f64x2 v1, f64x2 v2)
{
return v1 * v2;
}
Expected output:
arm-none-eabi-gcc (git commit 640647d4, not the latest) -O3 -S -march=armv7-a
-mfloat-abi=hard -mfpu=neon
fmul:
vmul.f32 q0, q0, q1
bx lr
dmul:
vmul.f64 d1, d1, d3
vmul.f64 d0, d0, d2
bx lr
Actual output:
fmul:
vmov.32 r3, d0[0]
sub sp, sp, #16
vmov s12, r3
vmov.32 r3, d2[0]
vmov s9, r3
vmov.32 r3, d0[1]
vmul.f32 s12, s12, s9
vstr.32 s12, [sp]
vmov s13, r3
vmov.32 r3, d2[1]
vmov s10, r3
vmov.32 r3, d1[0]
vmul.f32 s13, s13, s10
vstr.32 s13, [sp, #4]
vmov s14, r3
vmov.32 r3, d1[1]
vmov s15, r3
vmov.32 r3, d3[0]
vmov s11, r3
vmov.32 r3, d3[1]
vmul.f32 s14, s14, s11
vstr.32 s14, [sp, #8]
vmov s0, r3
vmul.f32 s0, s15, s0
vstr.32 s0, [sp, #12]
vld1.64 {d0-d1}, [sp:64]
add sp, sp, #16
bx lr
dmul:
push {r4, r5, r6, r7}
sub sp, sp, #96
vstr d0, [sp, #64]
vstr d1, [sp, #72]
vstr d2, [sp, #48]
vstr d3, [sp, #56]
vldr.64 d17, [sp, #64]
vldr.64 d19, [sp, #48]
vldr.64 d16, [sp, #72]
vldr.64 d18, [sp, #56]
vmul.f64 d17, d17, d19
vmul.f64 d16, d16, d18
vstr.64 d17, [sp, #32]
ldrd r0, [sp, #32]
mov r4, r0
mov r5, r1
strd r4, [sp]
vstr.64 d16, [sp, #40]
ldr r2, [sp, #40]
ldr ip, [sp, #44]
str r2, [sp, #8]
str ip, [sp, #12]
vld1.64 {d0-d1}, [sp:64]
add sp, sp, #96
pop {r4, r5, r6, r7}
bx lr
The same thing happens for other operators.
Oddly, according to Godbolt, GCC 4.5 actually did 32-bit float vectors
properly, but regressed more and more each release starting in 4.6.
>From gcc-bugs-return-627714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:08:33 2019
Return-Path: <gcc-bugs-return-627714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49485 invoked by alias); 5 Jan 2019 03:08: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 49388 invoked by uid 48); 5 Jan 2019 03:08:29 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88670] [meta-bug] generic vector extension issues
Date: Sat, 05 Jan 2019 03:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88670-4-CdlmfQtI8o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00523.txt.bz2
Content-length: 526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug 88670 depends on bug 88705, which changed state.
Bug 88705 Summary: [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-627713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:08:33 2019
Return-Path: <gcc-bugs-return-627713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49435 invoked by alias); 5 Jan 2019 03:08: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 49376 invoked by uid 48); 5 Jan 2019 03:08:28 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 03:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88705-4-NdyUI8H1yd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00522.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is expected.
See PR43703 for details on why.
Basically arm32 neon does not handle denormals at all.
It is a bug in clang (or rather their choice) to use them and not get valid
IEEE results.
>From gcc-bugs-return-627715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:12:55 2019
Return-Path: <gcc-bugs-return-627715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52685 invoked by alias); 5 Jan 2019 03:12: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 52646 invoked by uid 48); 5 Jan 2019 03:12:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 03:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88705-4-5zn1KpvS17@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00524.txt.bz2
Content-length: 325
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> This is expected.
For reference the patch which changed the behavior between 4.5.0 and 4.6.0:
https://gcc.gnu.org/ml/gcc-patches/2010-06/msg02102.html
>From gcc-bugs-return-627716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:20:18 2019
Return-Path: <gcc-bugs-return-627716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57545 invoked by alias); 5 Jan 2019 03:20: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 57469 invoked by uid 48); 5 Jan 2019 03:20:13 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/61367] Annoying rtx cost information in middle end dumps on arm/aarch64 targets
Date: Sat, 05 Jan 2019 03:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-61367-4-QGFaE8l7g0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61367-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61367-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00525.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61367
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |7.0
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Fixed a long time ago by:
+2016-11-16 Andrew PInski <apinski@cavium.com>
+
+ * config/aarch64/aarch64.opt (mverbose-cost-dump): New option.
+ * config/aarch64/aarch64.c (aarch64_rtx_costs): Use
+ flag_aarch64_verbose_cost instead of checking for details dump.
+ (aarch64_rtx_costs_wrapper): Likewise.
>From gcc-bugs-return-627717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:22:36 2019
Return-Path: <gcc-bugs-return-627717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59660 invoked by alias); 5 Jan 2019 03:22: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 59509 invoked by uid 48); 5 Jan 2019 03:22:30 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 03:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin 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_status resolution
Message-ID: <bug-88705-4-1F7VwN1Enk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00526.txt.bz2
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
Devin Hussey <husseydevin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
--- Comment #3 from Devin Hussey <husseydevin at gmail dot com> ---
Well, it is still not as efficient as it should be.
This would be the code that only uses VFP:
fmul:
vadd.f32 s0, s0, s4
vadd.f32 s1, s1, s5
vadd.f32 s2, s2, s6
vadd.f32 s3, s3, s7
bx lr
dmul:
vadd.f64 d0, d0, d2
vadd.f64 d1, d1, d3
bx lr
There is no need to keep swapping in and out of NEON registers.
>From gcc-bugs-return-627718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:22:36 2019
Return-Path: <gcc-bugs-return-627718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59670 invoked by alias); 5 Jan 2019 03:22:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59520 invoked by uid 48); 5 Jan 2019 03:22:31 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88670] [meta-bug] generic vector extension issues
Date: Sat, 05 Jan 2019 03:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88670-4-a1yEKEgp5w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00527.txt.bz2
Content-length: 525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug 88670 depends on bug 88705, which changed state.
Bug 88705 Summary: [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|INVALID |---
>From gcc-bugs-return-627719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:25:03 2019
Return-Path: <gcc-bugs-return-627719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87049 invoked by alias); 5 Jan 2019 03:25:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72797 invoked by uid 48); 5 Jan 2019 03:24:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 03:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88705-4-bzjQ5dLRFN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00528.txt.bz2
Content-length: 608
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Devin Hussey from comment #3)
> Well, it is still not as efficient as it should be.
>
> This would be the code that only uses VFP:
That I agree with. But arm32 is not where most of the work is being put into
...
>From gcc-bugs-return-627720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:52:51 2019
Return-Path: <gcc-bugs-return-627720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29966 invoked by alias); 5 Jan 2019 03: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 29898 invoked by uid 48); 5 Jan 2019 03:52:46 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sat, 05 Jan 2019 03:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88653-4-fRywPXQp5r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00529.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #11 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
OK, I had one other test fail which is one that requires inspection that my
testsuite compares the output to a reference file. This required only updating
my reference file to accomodate the fix where we took the spaces out inside the
parens for complex number output.
So with the discussed fixes NIST tests also pass for me.
>From gcc-bugs-return-627721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 03:58:24 2019
Return-Path: <gcc-bugs-return-627721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33650 invoked by alias); 5 Jan 2019 03:58: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 33603 invoked by uid 48); 5 Jan 2019 03:58:19 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 03:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88705-4-0uZVSIc5VN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00530.txt.bz2
Content-length: 1275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-05
Ever confirmed|0 |1
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
_5 = BIT_FIELD_REF <v1_1(D), 32, 0>;
_6 = BIT_FIELD_REF <v2_2(D), 32, 0>;
_7 = _5 * _6;
Here is a shorter testcase for one of the issues:
typedef float f32x4 __attribute__((vector_size(16)));
typedef double f64x2 __attribute__((vector_size(16)));
float f(f32x4 v1, f32x4 v2)
{
return v1[0] * v2[0];
}
double d(f64x2 v1, f64x2 v2)
{
return v1[0] * v2[0];
}
----- CUT ----
This is the extraction issue.
There is a generation issue too:
typedef float f32x4 __attribute__((vector_size(16)));
typedef double f64x2 __attribute__((vector_size(16)));
f32x4 f1(float a, float b, float c, float d)
{
return (f32x4){a,b,c,d};
}
f64x2 d1(float a, float b)
{
return (f64x2){a,b};
}
---- CUT ----
I think they both should be filed seperately too and make this depdent on those
two issues.
>From gcc-bugs-return-627722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 05:48:00 2019
Return-Path: <gcc-bugs-return-627722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128883 invoked by alias); 5 Jan 2019 05:48:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128856 invoked by uid 48); 5 Jan 2019 05:47:55 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88705] [ARM][Generic Vector Extensions] float32x4/float64x2 vector operator overloads scalarize on NEON
Date: Sat, 05 Jan 2019 05:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88705-4-DZXj8LMNs1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88705-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00531.txt.bz2
Content-length: 1439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88705
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
for the v4sf issue (v2sf has a similar issue too):
(define_insn "vec_extract<mode>"
[(set (match_operand:<V_elem> 0 "nonimmediate_operand" "=Um,r")
(vec_select:<V_elem>
(match_operand:VQ2 1 "s_register_operand" "w,w")
(parallel [(match_operand:SI 2 "immediate_operand" "i,i")])))]
That does not allow w (neon/vfp register) constraint as a dst so everything
needs to go through GPRs.
There is no vec_extract for V2DF which causes it to go through memory.
For the init part, the biggest issue is neon_expand_vector_init falls back to
doing everything in memory instead of doing "insertations" if there are a small
number of elements (<= 4, though you could do some gpr logical operations to
get to that number if needed):
/* Construct the vector in memory one field at a time
and load the whole vector. */
mem = assign_stack_temp (mode, GET_MODE_SIZE (mode));
for (i = 0; i < n_elts; i++)
emit_move_insn (adjust_address_nv (mem, inner_mode,
i * GET_MODE_SIZE (inner_mode)),
XVECEXP (vals, 0, i));
emit_move_insn (target, mem);
----- CUT ----
Note aarch64_expand_vector_init has some interesting ideas that could be
repeated here (and more due to the overlapping of lower d, q, and s registers).
>From gcc-bugs-return-627723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 05:49:35 2019
Return-Path: <gcc-bugs-return-627723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130309 invoked by alias); 5 Jan 2019 05:49: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 130251 invoked by uid 48); 5 Jan 2019 05:49:31 -0000
From: "marco_atzeri at yahoo dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47030] !GCC$ Attributes do not work for COMMON variables in procedures and BLOCK DATA
Date: Sat, 05 Jan 2019 05:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marco_atzeri at yahoo dot it
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-47030-4-86UTXU8EYS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47030-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00532.txt.bz2
Content-length: 779
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47030
marco atzeri <marco_atzeri at yahoo dot it> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #44949|0 |1
is obsolete| |
--- Comment #10 from marco atzeri <marco_atzeri at yahoo dot it> ---
Created attachment 45348
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45348&action=edit
updated patch for 7.3.0 - validated for style
refreshed patch that passes the
check_GNU_style.sh control.
Only formatting and removal of not needed comments versus previous one.
Previous one was applied on 7.4 for cygwin binary package without any build
problem
>From gcc-bugs-return-627724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 08:29:50 2019
Return-Path: <gcc-bugs-return-627724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15190 invoked by alias); 5 Jan 2019 08:29:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15114 invoked by uid 48); 5 Jan 2019 08:29:44 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 08:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-88698-4-sfKommVzxt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00533.txt.bz2
Content-length: 1394
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #6 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
My recommendation is to use a union like below; this allows writing code using
both generic vectors and intrinsics without casts, and having each operation
show exactly what lane types it operates on:
typedef unsigned char u8v __attribute__((vector_size(16)));
typedef unsigned short u16v __attribute__((vector_size(16)));
typedef unsigned int u32v __attribute__((vector_size(16)));
typedef union {
u8v u8;
u16v u16;
u32v u32;
__m128i m;
} uv;
Example use:
uv x, t, lo_nib, hi_nib;
memcpy(&x, ptr, sizeof x);
t.u32 = x.u32 >> 4;
lo_nib.u8 = x.u8 & 15;
hi_nib.u8 = t.u8 & 15;
lo_nib.m = _mm_shuffle_epi8(lut.m, lo_nib.m);
hi_nib.m = _mm_shuffle_epi8(lut.m, hi_nib.m);
This also allows writing 256-bit and 128-bit versions together when appropriate
(with help of extra macros for using the right intrinsic function).
Would you like to see the documentation mention this pattern?
>From gcc-bugs-return-627725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 08:59:35 2019
Return-Path: <gcc-bugs-return-627725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47675 invoked by alias); 5 Jan 2019 08:59:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47616 invoked by uid 55); 5 Jan 2019 08:59:30 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [6/7/8 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Sat, 05 Jan 2019 08:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
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-88702-4-8xrf2x2pvi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00534.txt.bz2
Content-length: 859
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
--- Comment #4 from Jan Hubicka <hubicka at ucw dot cz> ---
> The only pass that can do about this (at least right now) is reassoc (both 1
> and 2), which is too late for inlining. So, either teach fnsplit not to
> separate multiple if comparisons of the same variable against constants, or
> schedule reasoc or just the maybe_optimize_range_tests part thereof in some
> early pass.
Yep, I also found out about reassoc.
Teaching fnsplit to pattern match this is just a partial solution - we
would still miscalculate size of function body for functions like this
(which indeed look quite common). I will experiment with early reassoc.
I kind of debugged what happens later. Because code is compiled with -O2
and growth gets positive for both inlines and functions are not inline,
we won't inline.
>From gcc-bugs-return-627726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 09:38:19 2019
Return-Path: <gcc-bugs-return-627726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79369 invoked by alias); 5 Jan 2019 09:38:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79328 invoked by uid 48); 5 Jan 2019 09:38:13 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 09:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88698-4-KyEnsIMY0n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00535.txt.bz2
Content-length: 818
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #7 from Devin Hussey <husseydevin at gmail dot com> ---
I mean, sure, but how about this?
What about meeting in the middle?
-fno-lax-vector-conversions generates errors like it does now.
-flax-vector-conversions shuts GCC up.
No flag causes warnings on -Wpedantic or -Wvector-conversion.
If we really want to enforce the standard, we should also add a pedantic
warning for when we use overloads on intrinsic types without -std=gnu*.
-Wgnu-vector-extensions or something:
warning:
{
arithmetic operators |
logical operators |
array subscripts |
initializer lists
}
on vector types are a GNU extension
I feel that the weird promotion rules Clang uses should be an error, and
assignment to different types should warn without a cast.
>From gcc-bugs-return-627727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 09:57:49 2019
Return-Path: <gcc-bugs-return-627727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93424 invoked by alias); 5 Jan 2019 09:57: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 93355 invoked by uid 48); 5 Jan 2019 09:57:43 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88698-4-ZJX6a0ipnX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00536.txt.bz2
Content-length: 1440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Devin Hussey from comment #7)
> I mean, sure, but how about this?
>
> What about meeting in the middle?
The problem is how do you implement the rules that are required by both the
Altivec and Neon programming manuals? Do you treat those types differently?
And then what about the generic vector types to/from the Altivec/Neon types?
How do you want to have those handled?
Basically GCC was trying to follow what the Altivec (VMX) PEM says with respect
to the types and their casting.
For reference of the Altivec PEM:
https://www.nxp.com/docs/en/reference-manual/ALTIVECPEM.pdf
Have you read the Altivec PEM? GCC vector extension is/was modeled mostly
after the Altivec PEM with a few additions aftwards (like operators and
condtionals).
Here is the patch which added vector_size:
https://gcc.gnu.org/ml/gcc-patches/2001-12/msg00379.html
Here is the patch that made it in which added the operators:
https://gcc.gnu.org/ml/gcc/2002-05/msg02234.html
Notice that this patch has the following test:
+ v4si a, b;
..
+ uv4si f;
...
+ f = a; /* { dg-error "incompatible types in assignment" } */
As mentioned in the thread which added -flax-vector-conversions, that was an
accident that some versions of GCC accepted the assignment without the cast.
Somehow the testcase got lost.
>From gcc-bugs-return-627728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 10:14:01 2019
Return-Path: <gcc-bugs-return-627728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116881 invoked by alias); 5 Jan 2019 10:14:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116796 invoked by uid 48); 5 Jan 2019 10:13:55 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Sat, 05 Jan 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88638-4-C0SVndPQnp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00537.txt.bz2
Content-length: 2540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I submitted the patch below for review. Dominique, if you have
> an opportunity to test it on Darwin and let me know if there are
> any outstanding problems that would be great.
> https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00181.html
The patch for c-family/c-attribs.c no longer applies due to revision r267591: I
used
--- ../_clean/gcc/c-family/c-attribs.c 2019-01-05 05:45:01.000000000 +0100
+++ gcc/c-family/c-attribs.c 2019-01-05 06:04:49.000000000 +0100
@@ -632,16 +632,12 @@ positional_argument (const_tree fntype,
}
bool type_match;
- if (code == STRING_CST && POINTER_TYPE_P (argtype))
- {
- /* Where the expected code is STRING_CST accept any pointer
- to a narrow character type, qualified or otherwise. */
- tree type = TREE_TYPE (argtype);
- type = TYPE_MAIN_VARIANT (type);
- type_match = (type == char_type_node
- || type == signed_char_type_node
- || type == unsigned_char_type_node);
- }
+ if (code == STRING_CST)
+ /* Where the expected code is STRING_CST accept any pointer
+ expected by attribute format (this includes possibly qualified
+ char pointers and, for targets like Darwin, also pointers to
+ struct CFString). */
+ type_match = valid_format_string_type_p (argtype);
else if (code == INTEGER_TYPE)
/* For integers, accept enums, wide characters and other types
that match INTEGRAL_TYPE_P except for bool. */
@@ -652,6 +648,21 @@ positional_argument (const_tree fntype,
if (!type_match)
{
+ if (code == STRING_CST)
+ {
+ /* Reject invalid format strings with an error. */
+ if (argno < 1)
+ error ("%qE attribute argument value %qE refers to "
+ "parameter type %qT",
+ atname, pos, argtype);
+ else
+ error ("%qE attribute argument %i value %qE refers to "
+ "parameter type %qT",
+ atname, argno, pos, argtype);
+
+ return NULL_TREE;
+ }
+
if (argno < 1)
warning (OPT_Wattributes,
"%qE attribute argument value %qE refers to "
A quick tests showed that it fixed the reported failures.
>From gcc-bugs-return-627729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:09:50 2019
Return-Path: <gcc-bugs-return-627729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37844 invoked by alias); 5 Jan 2019 11:09: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 37763 invoked by uid 55); 5 Jan 2019 11:09:45 -0000
From: "dominiq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
Date: Sat, 05 Jan 2019 11:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60563-4-gvdWZ510cE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00538.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60563
--- Comment #17 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sat Jan 5 11:09:11 2019
New Revision: 267593
URL: https://gcc.gnu.org/viewcvs?rev=267593&root=gcc&view=rev
Log:
2019-01-05 Dominique d'Humieres <dominiq@gcc.gnu.org>
PR target/60563
Missing PR entry in the previous commit.
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:12:52 2019
Return-Path: <gcc-bugs-return-627730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45488 invoked by alias); 5 Jan 2019 11:12: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 45422 invoked by uid 48); 5 Jan 2019 11:12:46 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 11:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-88698-4-Vv477F8h7A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00539.txt.bz2
Content-length: 2251
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Devin Hussey from comment #2)
> What I am saying is that I think -flax-vector-conversions should be default,
> or we should only have minimal warnings instead of errors.
>
> That will make generic vectors much easier to use.
And more confusing / error-prone, there is a compromise.
> typedef uint32_t u32x4 __attribute__((vector_size(16)));
>
> u32x4 shift(u32x4 val)
> {
> return _mm_srli_epi32(val, 15);
> }
Indeed, when calling an intrinsic, it could make sense to allow other vector
types of the same size. Or would you expect the same behavior if you were
calling your own function instead of _mm_srli_epi32?
> 3. Cast. Good lord, if you thought intrinsics were ugly, this will change
> your mind:
>
> return (u32x4)_mm_srli_epi32((__m128i)val, 15);
It isn't that bad. First, if you only use intrinsics, you shouldn't define
u32x4, then you only have __m128i, __m128 and __m128d, fewer conversions are
needed. Then, if you do define u32x4, you can rewrite that as
return val >> 15;
> This is the second issue: unsigned long and unsigned int are the same size
> and should have no issues converting between each other.
We could special case this. But note that in C/C++, we don't consider int and
long as the same type just because they have the same size, and reinterpreting
int* as long* violates strict aliasing.
> typedef unsigned u32x4 __attribute__((vector_size(16)));
> typedef unsigned long long u64x2 __attribute__((vector_size(16)));
>
> u64x2 cast(u32x4 val)
> {
> return val;
> }
>
>
> This should emit a warning without a cast. I would recommend an error, but
> Clang without -Wvector-conversion accepts this without any complaining.
At some point it isn't easy to have a different behavior for an implicit
conversion in different contexts. Should the intrinsics be marked with some
magic flag that asks to be lax about their arguments?
(In reply to Devin Hussey from comment #5)
> Clang even allows this:
>
> #include <arm_neon.h>
>
> uint32x4_t mult(uint16x8_t top, uint32x4_t bot)
> {
> return top * bot;
> }
We clearly don't want that...
>From gcc-bugs-return-627731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:13:14 2019
Return-Path: <gcc-bugs-return-627731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46314 invoked by alias); 5 Jan 2019 11:13: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 46233 invoked by uid 55); 5 Jan 2019 11:13:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88635] [8 Regression] Assembler error when building with "-g -O2 -m32"
Date: Sat, 05 Jan 2019 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: assemble-failure, 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.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88635-4-MpkQJoc4ye@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00540.txt.bz2
Content-length: 1000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88635
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jan 5 11:12:35 2019
New Revision: 267594
URL: https://gcc.gnu.org/viewcvs?rev=267594&root=gcc&view=rev
Log:
PR debug/88635
* dwarf2out.c (const_ok_for_output_1): Reject MINUS that contains
SYMBOL_REF, CODE_LABEL or UNSPEC in subexpressions of second argument.
Reject PLUS that contains SYMBOL_REF, CODE_LABEL or UNSPEC in
subexpressions of both operands.
(mem_loc_descriptor): Handle UNSPEC if target hook acks it and all the
subrtxes are CONSTANT_P.
* config/i386/i386.c (ix86_const_not_ok_for_debug_p): Revert
2018-11-09 changes.
* gcc.dg/debug/dwarf2/pr88635.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/debug/dwarf2/pr88635.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/dwarf2out.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:14:55 2019
Return-Path: <gcc-bugs-return-627733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49507 invoked by alias); 5 Jan 2019 11:14:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49230 invoked by uid 55); 5 Jan 2019 11:14:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88620] [7/8/9 Regression] ICE in assign_stack_temp_for_type, at function.c:837
Date: Sat, 05 Jan 2019 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88620-4-Jr3FPjOrC4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00542.txt.bz2
Content-length: 749
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jan 5 11:14:12 2019
New Revision: 267595
URL: https://gcc.gnu.org/viewcvs?rev=267595&root=gcc&view=rev
Log:
PR middle-end/82564
PR target/88620
* expr.c (expand_assignment): For calls returning VLA structures
if to_rtx is not a MEM, force it into a stack temporary.
* gcc.dg/nested-func-12.c: New test.
* gcc.c-torture/compile/pr82564.c: New test.
Added:
trunk/gcc/testsuite/gcc.c-torture/compile/pr82564.c
trunk/gcc/testsuite/gcc.dg/nested-func-12.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/expr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:14:55 2019
Return-Path: <gcc-bugs-return-627732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49462 invoked by alias); 5 Jan 2019 11:14:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49218 invoked by uid 55); 5 Jan 2019 11:14:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82564] ICE at -O1 and above: in assign_stack_temp_for_type, at function.c:783
Date: Sat, 05 Jan 2019 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82564-4-BwcBHP5ieq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82564-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82564-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00541.txt.bz2
Content-length: 749
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82564
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jan 5 11:14:12 2019
New Revision: 267595
URL: https://gcc.gnu.org/viewcvs?rev=267595&root=gcc&view=rev
Log:
PR middle-end/82564
PR target/88620
* expr.c (expand_assignment): For calls returning VLA structures
if to_rtx is not a MEM, force it into a stack temporary.
* gcc.dg/nested-func-12.c: New test.
* gcc.c-torture/compile/pr82564.c: New test.
Added:
trunk/gcc/testsuite/gcc.c-torture/compile/pr82564.c
trunk/gcc/testsuite/gcc.dg/nested-func-12.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/expr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:17:14 2019
Return-Path: <gcc-bugs-return-627734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52889 invoked by alias); 5 Jan 2019 11:17: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 52792 invoked by uid 48); 5 Jan 2019 11:17:08 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88706] New: [og8, nvptx, openacc] Inconsistencies when vector length set using vector_length clause or fopenacc-dim
Date: Sat, 05 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88706-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00543.txt.bz2
Content-length: 5322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88706
Bug ID: 88706
Summary: [og8, nvptx, openacc] Inconsistencies when vector
length set using vector_length clause or fopenacc-dim
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider libgomp testcase vred2d-128.c (posted partially here):
...
gentest (test1, "acc parallel loop gang vector_length (128)",
"acc loop vector reduction(+:t1) reduction(-:t2)")
gentest (test2, "acc parallel loop gang vector_length (128)",
"acc loop worker vector reduction(+:t1) reduction(-:t2)")
gentest (test3, "acc parallel loop gang worker vector_length (128)",
"acc loop vector reduction(+:t1) reduction(-:t2)")
gentest (test4, "acc parallel loop",
"acc loop reduction(+:t1) reduction(-:t2)")
...
The resulting front-end attributes are:
...
$ grep -A1 __attribute__ vred2d-128.c.088t.fixup_cfg4
__attribute__((oacc function (, , 128), omp target entrypoint))
test1._omp_fn.0 (long int * t2, long int * t1, int[10000] * a2, int[10000] *
a1)
--
__attribute__((oacc function (, , 128), omp target entrypoint))
test2._omp_fn.1 (long int * t2, long int * t1, int[10000] * a2, int[10000] *
a1)
--
__attribute__((oacc function (, , 128), omp target entrypoint))
test3._omp_fn.2 (long int * t2, long int * t1, int[10000] * a2, int[10000] *
a1)
--
__attribute__((oacc function (, , ), omp target entrypoint))
test4._omp_fn.3 (long int * t2, long int * t1, int[10000] * a2, int[10000] *
a1)
...
When we compile at -O2 and grep for the resulting dimensions, we have:
...
$ grep FUNC_MAP vred2d-128.s
//:FUNC_MAP "test1$_omp_fn$0", 0, 0x1, 0x80
//:FUNC_MAP "test2$_omp_fn$1", 0, 0x1, 0x80
//:FUNC_MAP "test3$_omp_fn$2", 0, 0, 0x20
//:FUNC_MAP "test4$_omp_fn$3", 0, 0, 0x20
...
Note that the vector length for test3 has been downgraded by the
-mno-long-vector-in-workers workaround.
Now if we remove the hardcoded vector-length (128) from test1, test2 and test3,
and we add -fopenacc-dim=::128 we have instead:
...
//:FUNC_MAP "test1$_omp_fn$0", 0, 0x1, 0x80
//:FUNC_MAP "test2$_omp_fn$1", 0, 0, 0x80
//:FUNC_MAP "test3$_omp_fn$2", 0, 0, 0x80
//:FUNC_MAP "test4$_omp_fn$3", 0, 0, 0x80
...
The change on test4 is expected.
But the change on test3 is unexpected. It should not matter whether we set the
vector length on the parallel directive, or using -fopenacc-dim, the effect of
-mno-long-vector-in-workers should be the same.
The cause for this can be seen by adding this print statement:
...
diff --git a/gcc/config/nvptx/nvptx.c b/gcc/config/nvptx/nvptx.c
index 110dbffe0d0..5aab6db169f 100644
--- a/gcc/config/nvptx/nvptx.c
+++ b/gcc/config/nvptx/nvptx.c
@@ -5688,6 +5688,7 @@ nvptx_adjust_parallelism (unsigned inner_mask, unsigned
outer_mask)
offload_attrs oa;
populate_offload_attrs (&oa);
+ fprintf (stderr, "oa.vector_length in nvptx_adjust_parallelism: %d\n",
oa.vector_length);
if (oa.vector_length == PTX_WARP_SIZE)
return inner_mask;
...
If we have the first case (vector_length set on parallel directive, no
-fopenacc-dim=), we have:
...
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
...
But in the second case (no vector_length set on parallel directive, using
-fopenacc-dim=), we have:
...
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
...
I think the same problem exists for the other work around in
nvptx_adjust_parallelism, this one:
...
/* FIXME: This is overly conservative; worker and vector loop will
eventually be combined. */
if (wv)
return inner_mask & ~GOMP_DIM_MASK (GOMP_DIM_WORKER);
...
It's just harded to spot because the workaround doesn't affect vector length.
>From gcc-bugs-return-627735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 11:18:18 2019
Return-Path: <gcc-bugs-return-627735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57188 invoked by alias); 5 Jan 2019 11:18:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57111 invoked by uid 55); 5 Jan 2019 11:18:14 -0000
From: "dominiq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
Date: Sat, 05 Jan 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60563-4-UMdnV0AlhZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00544.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60563
--- Comment #18 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sat Jan 5 11:17:40 2019
New Revision: 267596
URL: https://gcc.gnu.org/viewcvs?rev=267596&root=gcc&view=rev
Log:
2019-01-05 Dominique d'Humieres <dominiq@gcc.gnu.org>
PR target/60563
* g++.dg/ext/sync-4.C: Add dg-xfail-run-if for darwin.
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/testsuite/g++.dg/ext/sync-4.C
>From gcc-bugs-return-627736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:02:22 2019
Return-Path: <gcc-bugs-return-627736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9911 invoked by alias); 5 Jan 2019 12:02: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 9849 invoked by uid 48); 5 Jan 2019 12:02:17 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sat, 05 Jan 2019 12:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.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:
Message-ID: <bug-88653-4-VG3JHAdXsu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00545.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #12 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
It seems that the problem comes from your installation.
Did you build gfortran yourself or did you get it from some binary
distribution? If the later, from where? Did you report the problem to them?
Is this the first time you use gfortran? If no, what was the last working
version?
> A list of files that failed to compile.
Does this mean that the other files compile and run?
>From gcc-bugs-return-627737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:19:22 2019
Return-Path: <gcc-bugs-return-627737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102537 invoked by alias); 5 Jan 2019 12:19: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 102452 invoked by uid 48); 5 Jan 2019 12:19:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88620] [7/8 Regression] ICE in assign_stack_temp_for_type, at function.c:837
Date: Sat, 05 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88620-4-u3bhc6gHeM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00546.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8/9 Regression] ICE in |[7/8 Regression] ICE in
|assign_stack_temp_for_type, |assign_stack_temp_for_type,
|at function.c:837 |at function.c:837
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-627738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:20:16 2019
Return-Path: <gcc-bugs-return-627738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103604 invoked by alias); 5 Jan 2019 12:20:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103522 invoked by uid 48); 5 Jan 2019 12:20:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82564] ICE at -O1 and above: in assign_stack_temp_for_type, at function.c:783
Date: Sat, 05 Jan 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-82564-4-B26bgFtC64@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82564-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82564-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00547.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82564
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk.
>From gcc-bugs-return-627739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:33:08 2019
Return-Path: <gcc-bugs-return-627739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125809 invoked by alias); 5 Jan 2019 12:33: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 125749 invoked by uid 48); 5 Jan 2019 12:33:03 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/88707] New: Random failures of libgomp.c++/task-reduction-(8|10).C on x86_64-apple-darwin18
Date: Sat, 05 Jan 2019 12:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88707-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00548.txt.bz2
Content-length: 1064
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88707
Bug ID: 88707
Summary: Random failures of libgomp.c++/task-reduction-(8|10).C
on x86_64-apple-darwin18
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgomp
Assignee: unassigned at gcc dot gnu.org
Reporter: dominiq at lps dot ens.fr
CC: iains at gcc dot gnu.org, jakub at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-apple-darwin18
Target: x86_64-apple-darwin18
Build: x86_64-apple-darwin18
On x86_64-apple-darwin18 I see
WARNING: program timed out.
FAIL: libgomp.c++/task-reduction-10.C execution test
WARNING: program timed out.
FAIL: libgomp.c++/task-reduction-8.C execution test
since they were introduced at revision r265930.
Not only the tests are randomly timed out for -m32 or -m64, but I have to to
kill the executable manually. I don't see the problem on darwin 10.
>From gcc-bugs-return-627740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:44:50 2019
Return-Path: <gcc-bugs-return-627740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6261 invoked by alias); 5 Jan 2019 12:44:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6200 invoked by uid 55); 5 Jan 2019 12:44:45 -0000
From: "dominiq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
Date: Sat, 05 Jan 2019 12:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60563-4-p77PBJVY1P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00549.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60563
--- Comment #19 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sat Jan 5 12:44:12 2019
New Revision: 267597
URL: https://gcc.gnu.org/viewcvs?rev=267597&root=gcc&view=rev
Log:
2019-01-05 Dominique d'Humieres <dominiq@gcc.gnu.org>
PR target/60563
* g++.dg/ext/sync-4.C: Add dg-xfail-run-if for darwin.
Modified:
branches/gcc-7-branch/gcc/testsuite/ChangeLog
branches/gcc-7-branch/gcc/testsuite/g++.dg/ext/sync-4.C
>From gcc-bugs-return-627741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:46:09 2019
Return-Path: <gcc-bugs-return-627741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7744 invoked by alias); 5 Jan 2019 12:46: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 7572 invoked by uid 48); 5 Jan 2019 12:45:48 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/88707] Random failures of libgomp.c++/task-reduction-(8|10).C on x86_64-apple-darwin18
Date: Sat, 05 Jan 2019 12:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88707-4-WWRjdFyRMY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88707-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88707-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00550.txt.bz2
Content-length: 621
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88707
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-05
Ever confirmed|0 |1
--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
looking through my last set of results, the first occurrence I see is for
Darwin16 (OSX 10.12), but since this is a random fail - that might be
inconclusive.
>From gcc-bugs-return-627742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:48:58 2019
Return-Path: <gcc-bugs-return-627742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9691 invoked by alias); 5 Jan 2019 12:48:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9576 invoked by uid 48); 5 Jan 2019 12:48:45 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60563] FAIL: g++.dg/ext/sync-4.C on *-apple-darwin*
Date: Sat, 05 Jan 2019 12:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.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: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status resolution
Message-ID: <bug-60563-4-M7zzxqP4O5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00551.txt.bz2
Content-length: 634
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60563
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #20 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Silenced on trunk and release branches, closing.
The test will XPASS when the ld problem will be fixed and the darwin hack could
then be removed.
>From gcc-bugs-return-627743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 12:58:25 2019
Return-Path: <gcc-bugs-return-627743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73533 invoked by alias); 5 Jan 2019 12:58:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73465 invoked by uid 48); 5 Jan 2019 12:58:16 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/88707] Random failures of libgomp.c++/task-reduction-(8|10).C on x86_64-apple-darwin18
Date: Sat, 05 Jan 2019 12:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88707-4-0gUW1gXBUs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88707-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88707-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00552.txt.bz2
Content-length: 5229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88707
--- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> ---
(on Darwin17 I had a recent build)
I find that a built exe fails quite often; here's a sample of the hung program
(it appears deadlocked, not consuming any CPU).
The correct libraries are being loaded.
Sampling process 23844 for 3 seconds with 1 millisecond of run time between
samples
Sampling completed, processing symbols...
Analysis of sampling task-reduction-10.exe (pid 23844) every 1 millisecond
Process: task-reduction-10.exe [23844]
Path:
/Volumes/scratch/10-13-his/gcc-trunk-gcc/x86_64-apple-darwin17/libgomp/testsuite/task-reduction-10.exe
Load Address: 0x108350000
Identifier: task-reduction-10.exe
Version: 0
Code Type: X86-64
Parent Process: bash [34246]
Date/Time: 2019-01-05 12:53:30.784 +0000
Launch Time: 2019-01-05 12:52:40.943 +0000
OS Version: Mac OS X 10.13.6 (17G4015)
Report Version: 7
Analysis Tool: /usr/bin/sample
Physical footprint: 568K
Physical footprint (peak): 576K
----
Call graph:
2799 Thread_58184392 DispatchQueue_1: com.apple.main-thread (serial)
+ 2799 ??? (in <unknown binary>) [0x7f9679c02718]
+ 2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
+ 2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
+ 2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
+ 2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
2799 Thread_58184395
+ 2799 ??? (in <unknown binary>) [0x206000000000]
+ 2799 ??? (in <unknown binary>) [0x7f9679c02cb8]
+ 2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
+ 2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
+ 2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
+ 2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
2799 Thread_58184397
+ 2799 ??? (in <unknown binary>) [0x206000000000]
+ 2799 ??? (in <unknown binary>) [0x7f9679c030b8]
+ 2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
+ 2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
+ 2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
+ 2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
2799 Thread_58184398
+ 2799 ??? (in <unknown binary>) [0x206000000000]
+ 2799 ??? (in <unknown binary>) [0x7f9679c032b8]
+ 2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
+ 2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
+ 2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
+ 2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
2799 Thread_58184399
+ 2799 ??? (in <unknown binary>) [0x206000000000]
+ 2799 ??? (in <unknown binary>) [0x7f9679c034b8]
+ 2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
+ 2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
+ 2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
+ 2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
2799 Thread_58184400
+ 2799 ??? (in <unknown binary>) [0x206000000000]
+ 2799 ??? (in <unknown binary>) [0x7f9679d00118]
+ 2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
+ 2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
+ 2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
+ 2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
2799 Thread_58184401
2799 ??? (in <unknown binary>) [0x206000000000]
2799 ??? (in <unknown binary>) [0x7f9679d00318]
2799 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
2799 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
2799 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
2799 __psynch_cvwait (in libsystem_kernel.dylib) + 10
[0x7fff534aea16]
Total number in stack (recursive counted multiple, when >=5):
7 __psynch_cvwait (in libsystem_kernel.dylib) + 0
[0x7fff534aea0c]
7 _pthread_cond_wait (in libsystem_pthread.dylib) + 732
[0x7fff53677589]
7 gomp_barrier_wait_end (in libgomp.1.dylib) + 86 [0x10862d606]
bar.c:92
7 gomp_sem_wait (in libgomp.1.dylib) + 40 [0x10862d488]
sem.c:71
6 ??? (in <unknown binary>) [0x206000000000]
Sort by top of stack, same collapsed (when >= 5):
__psynch_cvwait (in libsystem_kernel.dylib) 19593
>From gcc-bugs-return-627744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 13:07:35 2019
Return-Path: <gcc-bugs-return-627744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89069 invoked by alias); 5 Jan 2019 13:07: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 89034 invoked by uid 48); 5 Jan 2019 13:07:30 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88632] [F08] function contained in module invisible to submodule unless declared public
Date: Sat, 05 Jan 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: link-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to attachments.created
Message-ID: <bug-88632-4-ISOAZCh9vk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88632-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88632-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00553.txt.bz2
Content-length: 1554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88632
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
--- Comment #2 from Paul Thomas <pault at gcc dot gnu.org> ---
Created attachment 45349
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45349&action=edit
A provisional patch that fixes the problem
The attached fixes this but causes regressions:
FAIL: gfortran.dg/module_private_2.f90 -O scan-tree-dump-times optimized
"priv" 0
FAIL: gfortran.dg/public_private_module_7.f90 -O scan-assembler-not
__m_common_attrs_MOD_other
FAIL: gfortran.dg/public_private_module_8.f90 -O scan-assembler-not
__m_MOD_myotherlen
FAIL: gfortran.dg/public_private_module_2.f90 -O scan-assembler-not two
FAIL: gfortran.dg/public_private_module_2.f90 -O scan-assembler-not six
FAIL: gfortran.dg/warn_unused_function_2.f90 -O (test for warnings, line
16)
I think that this is best dealt with by extending the patch by flagging the
module as having a module function/subroutine, which implies that there is a
submodule somewhere, and making all the module procedures TREE_PUBLIC. That
will suppress the above regressions.
Otherwise, I will have to find someway of persuading the linker to find the
symbol from the submodule.
First I must get the C-interop patch out of the way and then I will come back
to this PR.
Paul
>From gcc-bugs-return-627745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 13:31:04 2019
Return-Path: <gcc-bugs-return-627745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79332 invoked by alias); 5 Jan 2019 13:31: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 79188 invoked by uid 48); 5 Jan 2019 13:30:53 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/88708] New: help-dummy.o file left behind
Date: Sat, 05 Jan 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz 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-88708-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00554.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88708
Bug ID: 88708
Summary: help-dummy.o file left behind
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: drepper.fsp+rhbz at gmail dot com
Target Milestone: ---
When using
gcc -c -Q -O --help=optimizers
the driver leaves behind the help-dummy.o file. This happens with gcc trunk
and all prior versions I was able to test.
>From gcc-bugs-return-627746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 13:36:11 2019
Return-Path: <gcc-bugs-return-627746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84443 invoked by alias); 5 Jan 2019 13:36:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84316 invoked by uid 48); 5 Jan 2019 13:36:06 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sat, 05 Jan 2019 13:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88653-4-iKWHm4Zn7c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00555.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #13 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I checked this with the exact same version on Cygwin, no
errors detected.
So, this loos like an installation or hardware problem. Could
you maybe re-install the compiler?
>From gcc-bugs-return-627747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 14:29:02 2019
Return-Path: <gcc-bugs-return-627747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27103 invoked by alias); 5 Jan 2019 14:29:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26926 invoked by uid 48); 5 Jan 2019 14:28:57 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88698] Relax generic vector conversions
Date: Sat, 05 Jan 2019 14:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88698-4-JOAgnbsdKJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00556.txt.bz2
Content-length: 319
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88698
--- Comment #10 from Devin Hussey <husseydevin at gmail dot com> ---
Well what about a special type attribute or some kind of transparent_union like
thing for Intel's types? It seems that Intel's intrinsics are the main (only)
platform that uses generic types.
>From gcc-bugs-return-627748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 14:32:50 2019
Return-Path: <gcc-bugs-return-627748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30306 invoked by alias); 5 Jan 2019 14:32:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30258 invoked by uid 55); 5 Jan 2019 14:32:44 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88009] [9 Regression] ICE in find_intrinsic_vtab, at fortran/class.c:2761
Date: Sat, 05 Jan 2019 14:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88009-4-4kZaliSug6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88009-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00557.txt.bz2
Content-length: 1216
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88009
--- Comment #4 from janus at gcc dot gnu.org ---
Author: janus
Date: Sat Jan 5 14:32:12 2019
New Revision: 267598
URL: https://gcc.gnu.org/viewcvs?rev=267598&root=gcc&view=rev
Log:
2019-01-05 Janus Weil <janus@gcc.gnu.org>
PR fortran/88009
* class.c (gfc_find_derived_vtab): Mark the _final component as
artificial.
(find_intrinsic_vtab): Ditto. Also add an extra check to avoid
dereferencing a null pointer and adjust indentation.
* resolve.c (resolve_fl_variable): Add extra check to avoid
dereferencing a null pointer. Move variable declarations to local
scope.
(resolve_fl_procedure): Add extra check to avoid dereferencing a null
pointer.
* symbol.c (check_conflict): Suppress errors for artificial symbols.
2019-01-05 Janus Weil <janus@gcc.gnu.org>
PR fortran/88009
* gfortran.dg/blockdata_10.f90: New test case.
Added:
trunk/gcc/testsuite/gfortran.dg/blockdata_10.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/class.c
trunk/gcc/fortran/resolve.c
trunk/gcc/fortran/symbol.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 14:40:48 2019
Return-Path: <gcc-bugs-return-627749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46633 invoked by alias); 5 Jan 2019 14:40: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 46309 invoked by uid 48); 5 Jan 2019 14:40:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88709] New: Improve store-merging
Date: Sat, 05 Jan 2019 14:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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-88709-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00558.txt.bz2
Content-length: 2009
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88709
Bug ID: 88709
Summary: Improve store-merging
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
As shown in:
struct S { char buf[8]; };
void bar (struct S *);
void
foo (void)
{
struct S s = {};
s.buf[1] = 1;
s.buf[3] = 2;
bar (&s);
}
or
struct val_t
{
char data[16];
};
void optimize_me (val_t);
void optimize_me3 (val_t, val_t, val_t);
void
good ()
{
optimize_me ({ 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16 });
}
void
bad ()
{
optimize_me ({ 1, 2, 3, 4, 5 });
}
void
why ()
{
optimize_me ({ 1, 2, 3, 4, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 });
}
void
srsly ()
{
optimize_me3 ({ 1, 2, 3, 4, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
{ 11, 12, 13, 14, 15, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10,
10 },
{ 21, 22, 23, 24, 25, 20, 20, 20, 10, 20, 20, 20, 20, 20, 20
});
}
void
srsly_not_one_missing ()
{
optimize_me3 ({ 1, 2, 3, 4, 5, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 },
{ 11, 12, 13, 14, 15, 10, 10, 10, 10, 10, 10, 10, 10, 10, 10,
10 },
{ 21, 22, 23, 24, 25, 20, 20, 20, 10, 20, 20, 20, 20, 20, 20,
11 });
}
there is room for improvement in store-merging. In the first testcase, we
ignore the clearing because !lhs_valid_for_store_merging_p, the lhs is in that
case the whole VAR_DECL rather than a component of it. And in the second
testcase, we sometimes punt because of the same reason, sometimes because
rhs_valid_for_store_merging_p is false. Handling these = {} storage clearings
(or perhaps even __builtin_memset calls) is something we could handle, though
with extra care, we don't want to take apart those clears if it doesn't reduce
the amount of needed stores.
>From gcc-bugs-return-627750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 14:41:48 2019
Return-Path: <gcc-bugs-return-627750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52079 invoked by alias); 5 Jan 2019 14:41:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51516 invoked by uid 48); 5 Jan 2019 14:41:41 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88009] [9 Regression] ICE in find_intrinsic_vtab, at fortran/class.c:2761
Date: Sat, 05 Jan 2019 14:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88009-4-qUsqrZfVJE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88009-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88009-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00559.txt.bz2
Content-length: 413
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88009
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from janus at gcc dot gnu.org ---
Fixed with r267598. Closing.
>From gcc-bugs-return-627751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 14:49:50 2019
Return-Path: <gcc-bugs-return-627751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78538 invoked by alias); 5 Jan 2019 14:49: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 78479 invoked by uid 48); 5 Jan 2019 14:49:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88709] Improve store-merging
Date: Sat, 05 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: cc
Message-ID: <bug-88709-4-vzn3lpIgQN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88709-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88709-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00560.txt.bz2
Content-length: 762
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88709
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |redi at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Compared to the first testcase, we do handle
struct S { char buf[8]; };
void bar (struct S *);
void
foo (void)
{
struct S s;
int a = 0;
__builtin_memcpy (&s.buf[4], &a, sizeof (int));
s.buf[0] = 5;
s.buf[1] = 2;
s.buf[2] = 3;
s.buf[3] = 2;
s.buf[5] = 7;
bar (&s);
}
though, because the store is in that case MEM[&s + 4B] = {} and thus valid for
lhs.
>From gcc-bugs-return-627752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 14:55:05 2019
Return-Path: <gcc-bugs-return-627752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110641 invoked by alias); 5 Jan 2019 14:55:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110322 invoked by uid 48); 5 Jan 2019 14:55:01 -0000
From: "johnsonsr at ornl dot gov" <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: Sat, 05 Jan 2019 14:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: johnsonsr at ornl dot gov
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.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85855-4-LqakFfZNdd@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: 2019-01/txt/msg00561.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
Seth Johnson <johnsonsr at ornl dot gov> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |johnsonsr at ornl dot gov
--- Comment #6 from Seth Johnson <johnsonsr at ornl dot gov> ---
I'm seeing the same behavior on GCC 7.3; this looks to be a duplicate of
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504 .
>From gcc-bugs-return-627754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 15:02:07 2019
Return-Path: <gcc-bugs-return-627754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118163 invoked by alias); 5 Jan 2019 15:02:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117791 invoked by uid 48); 5 Jan 2019 15:02:03 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues
Date: Sat, 05 Jan 2019 15:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.1.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: trivial
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 resolution
Message-ID: <bug-24639-4-UFDBz42Pml@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-24639-4@http.gcc.gnu.org/bugzilla/>
References: <bug-24639-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00564.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 85855, which changed state.
Bug 85855 Summary: [7/8/9 Regression] (Maybe) uninitialized descriptor fields of an allocatable array component of a function result
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
>From gcc-bugs-return-627755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 15:02:10 2019
Return-Path: <gcc-bugs-return-627755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118489 invoked by alias); 5 Jan 2019 15:02: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 117611 invoked by uid 48); 5 Jan 2019 15:02:00 -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: Sat, 05 Jan 2019 15:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.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: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85855-4-CalewBFx4J@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: 2019-01/txt/msg00563.txt.bz2
Content-length: 640
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I'm seeing the same behavior on GCC 7.3; this looks to be a duplicate
> of https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504 .
I agree.
*** This bug has been marked as a duplicate of bug 77504 ***
>From gcc-bugs-return-627753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 15:02:05 2019
Return-Path: <gcc-bugs-return-627753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117876 invoked by alias); 5 Jan 2019 15:02: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 117678 invoked by uid 48); 5 Jan 2019 15:02:01 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77504] "is used uninitialized" with allocatable string and array constructors
Date: Sat, 05 Jan 2019 15:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-77504-4-VuNwgo5ij9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77504-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77504-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00562.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77504
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vladimir.fuka at gmail dot com
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 85855 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-627756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 15:39:51 2019
Return-Path: <gcc-bugs-return-627756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73106 invoked by alias); 5 Jan 2019 15:39:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73018 invoked by uid 48); 5 Jan 2019 15:39:42 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88706] [og8, nvptx, openacc] Inconsistencies when vector length set using vector_length clause or fopenacc-dim
Date: Sat, 05 Jan 2019 15:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88706-4-XX5KXOTIZT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88706-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88706-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00565.txt.bz2
Content-length: 2931
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88706
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> I think the same problem exists for the other work around in
> nvptx_adjust_parallelism, this one:
> ...
> /* FIXME: This is overly conservative; worker and vector loop will
>
> eventually be combined. */
> if (wv)
> return inner_mask & ~GOMP_DIM_MASK (GOMP_DIM_WORKER);
> ...
> It's just harder to spot because the workaround doesn't affect vector length.
Confirmed.
With this additional patch:
...
@@ -5695,7 +5696,10 @@ nvptx_adjust_parallelism (unsigned inner_mask, unsigned
outer_mask)
/* FIXME: This is overly conservative; worker and vector loop will
eventually be combined. */
if (wv)
- return inner_mask & ~GOMP_DIM_MASK (GOMP_DIM_WORKER);
+ {
+ fprintf (stderr, "worker-vector loop workaround applied in %s\n",
current_function_name ());
+ return inner_mask & ~GOMP_DIM_MASK (GOMP_DIM_WORKER);
+ }
/* It's difficult to guarantee that warps in large vector_lengths
will remain convergent when a vector loop is nested inside a
...
we see for the first case (vector_length set on parallel directive, no
-fopenacc-dim=):
...
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
worker-vector loop workaround applied in test2._omp_fn.1
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 128
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
...
and for the second case (no vector_length set on parallel directive, using
-fopenacc-dim=):
...
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
oa.vector_length in nvptx_adjust_parallelism: 32
...
>From gcc-bugs-return-627757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 16:17:59 2019
Return-Path: <gcc-bugs-return-627757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14948 invoked by alias); 5 Jan 2019 16:17: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 14907 invoked by uid 48); 5 Jan 2019 16:17:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/88708] help-dummy.o file left behind
Date: Sat, 05 Jan 2019 16:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 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: cc
Message-ID: <bug-88708-4-ruWQSxegSz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88708-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88708-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00566.txt.bz2
Content-length: 1109
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88708
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
No idea why the documentation suggests the -c there, without it it works just
fine.
With -S too, it actually calls cc1 with -o help-dummy.s but doesn't actually
emit there anything into that file (nor, if it exists previously, removes it or
modifies it).
With -E it actually fails:
./xgcc -B ./ -E -Q -O --help=optimizers
cc1: fatal error: help-dummy: No such file or directory
compilation terminated.
I wonder if we shouldn't treat -E as -S and -c as no -E/-S/-c with these help
options, which is IMHO the best thing. Without -E/-S/-c, cc1 is executed with
say -o /tmp/cc7Z9tXX.s but doesn't write that file, and as is executed with
-o /tmp/cc4DJDCT.o /tmp/cc7Z9tXX.s and all the temporary files are removed
afterwards.
>From gcc-bugs-return-627758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 16:43:46 2019
Return-Path: <gcc-bugs-return-627758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102589 invoked by alias); 5 Jan 2019 16:43:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102542 invoked by uid 48); 5 Jan 2019 16:43:41 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sat, 05 Jan 2019 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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-88653-4-mHnqlxT50y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00567.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #14 from Murat Tekeev <mtekeev at yandex dot ru> ---
I will establish anew Cygwin and I will try to repeat compilation.
When I used version 7.3, everything was good.
Eventually, there are also other compilers, except gfortran.
>From gcc-bugs-return-627759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 17:34:18 2019
Return-Path: <gcc-bugs-return-627759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89130 invoked by alias); 5 Jan 2019 17:34: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 89049 invoked by uid 48); 5 Jan 2019 17:34:12 -0000
From: "cfd@mnet-mail.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88710] New: [F08] Sourced allocation of array fails, yielding wrong bounds and result
Date: Sat, 05 Jan 2019 17: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: cfd@mnet-mail.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00568.txt.bz2
Content-length: 6215
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88710
Bug ID: 88710
Summary: [F08] Sourced allocation of array fails, yielding
wrong bounds and result
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: cfd@mnet-mail.de
Target Milestone: ---
The following code shows that sourced allocation of an allocatable
array with gfortran 8.1.0 leads to wrong lower and upper bounds
that do not correspond to those of the source expression.
Moreover, the initialized array therefore does not yield the correct
result expected from the value of the source expression.
$ cat test_alloc.F90
program test_alloc
implicit none
integer(4) :: i, j, k
real(8), dimension(:,:,:), allocatable :: a, b, c, t
allocate( a(-1:2,-1:1,1:1) )
allocate( b(-1:2,-1:1,1:1) )
allocate( c(-1:2,-1:1,1:1) )
a = 1.d0
b = 2.d0
c = 0.d0
allocate(t, source = (a + (c - b)) )
write(*,'(a,6(i5,1x))') 'lbound/ubound(a): ', lbound(a), ubound(a)
write(*,'(a,6(i5,1x))') 'lbound/ubound(b): ', lbound(b), ubound(b)
write(*,'(a,6(i5,1x))') 'lbound/ubound(c): ', lbound(c), ubound(c)
write(*,'(a,6(i5,1x))') 'lbound/ubound(t): ', lbound(t), ubound(t)
write(*,*) 'a, b, c, t: '
do k = lbound(a,3), ubound(a,3)
do j = lbound(a,2), ubound(a,2)
do i = lbound(a,1), ubound(a,1)
write(*,'(1p,4(e23.16,1x))') &
& a(i,j,k), b(i,j,k), c(i,j,k), t(i,j,k)
end do
end do
end do
end program test_alloc
Running this code with gfortran 8.1.0 gives the following output.
$ gfortran-8 test_alloc.F90 -o test.gfort; ./test.gfort
lbound/ubound(a): -1 -1 1 2 1 1
lbound/ubound(b): -1 -1 1 2 1 1
lbound/ubound(c): -1 -1 1 2 1 1
lbound/ubound(t): 0 0 0 3 2 0
a, b, c, t:
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
0.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
1.6304166312761136-322
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
1.0023829485142537E-95
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
3.4119363283543871-315
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
0.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
2.0716172530123468-320
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
9.6317959318370178-317
Both flang 6.0 and pgfortran 18.4-0 yield the following (correct) output
(notice the different bounds for t, and its values printed in the last column):
$ flang test_alloc.F90 -o test.flang; ./test.flang
lbound/ubound(a): -1 -1 1 2 1 1
lbound/ubound(b): -1 -1 1 2 1 1
lbound/ubound(c): -1 -1 1 2 1 1
lbound/ubound(t): -1 -1 1 2 1 1
a, b, c, t:
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
1.0000000000000000E+00 2.0000000000000000E+00 0.0000000000000000E+00
-1.0000000000000000E+00
Gfortran version used is:
$ gfortran-8 -v
Using built-in specs.
COLLECT_GCC=gfortran-8
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
8.1.0-5ubuntu1~16.04' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.1.0 (Ubuntu 8.1.0-5ubuntu1~16.04)
>From gcc-bugs-return-627760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 18:19:40 2019
Return-Path: <gcc-bugs-return-627760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96965 invoked by alias); 5 Jan 2019 18:19:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96872 invoked by uid 48); 5 Jan 2019 18:19:36 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] New: [regression 9.0] scan-ipa-dump inline "Inlined tp_sum/
Date: Sat, 05 Jan 2019 18:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 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 cc target_milestone
Message-ID: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00569.txt.bz2
Content-length: 960
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
Bug ID: 88711
Summary: [regression 9.0] scan-ipa-dump inline "Inlined
tp_sum/
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
CC: marxin at gcc dot gnu.org
Target Milestone: ---
A recent change (as in the last 12 hours) has introduce this regression
on x86_64-*-freebsd.
FAIL: gfortran.dg/pr79966.f90 -O scan-ipa-dump inline "Inlined
tp_sum/[0-9]+ into runtptests/[0-9]+"
The likely cause of this regression is
------------------------------------------------------------------------
r267600 | hubicka | 2019-01-05 09:47:34 -0800 (Sat, 05 Jan 2019) | 2 lines
* ipa-fnsummary.c (analyze_function_body): Fix accounting of time.
>From gcc-bugs-return-627761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 18:28:34 2019
Return-Path: <gcc-bugs-return-627761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117106 invoked by alias); 5 Jan 2019 18:28: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 117034 invoked by uid 48); 5 Jan 2019 18:28:29 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Sat, 05 Jan 2019 18:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85052-4-wAn6k0TYV9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00570.txt.bz2
Content-length: 1707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #6 from Devin Hussey <husseydevin at gmail dot com> ---
The patch seems to be working.
typedef unsigned u32x2 __attribute__((vector_size(8)));
typedef unsigned long long u64x2 __attribute__((vector_size(16)));
u64x2 cvt(u32x2 in)
{
return __builtin_convertvector(in, u64x2);
}
It doesn't generate the best code, but it isn't bad.
x86_64, SSE4.1:
cvt:
movq %xmm0, %rax
movd %eax, %xmm0
shrq $32, %rax
pinsrq $1, %rax, %xmm0
ret
x86_64, SSE2:
cvt:
movq %xmm0, %rax
movd %eax, %xmm0
shrq $32, %rax
movq %rax, %xmm1
punpcklqdq %xmm1, %xmm0
ret
ARMv7a NEON:
cvt:
sub sp, sp, #16
mov r3, #0
str r3, [sp, #4]
str r3, [sp, #12]
add r3, sp, #8
vst1.32 {d0[0]}, [sp]
vst1.32 {d0[1]}, [r3]
vld1.64 {d0-d1}, [sp:64]
add sp, sp, #16
bx lr
I haven't built the others yet.
The correct code would be this ([signed|unsigned]):
cvt:
vmovl.[s|u]32 q0, d0
bx lr
I am testing other targets now.
For the reference, this is what clang generates for other targets:
aarch64:
cvt:
[s|u]shll v0.2d, v0.2s, #0
ret
sse4.1/avx:
cvt:
[v]pmov[s|z]xdq xmm0, xmm0
ret
sse2:
signed_cvt:
pxor xmm1, xmm1
pcmpgtd xmm1, xmm0
punpckldq xmm0, xmm1 # xmm0 =
xmm0[0],xmm1[0],xmm0[1],xmm1[1]
ret
unsigned_cvt:
xorps xmm1, xmm1
unpcklps xmm0, xmm1 # xmm0 =
xmm0[0],xmm1[0],xmm0[1],xmm1[1]
ret
>From gcc-bugs-return-627762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 18:36:13 2019
Return-Path: <gcc-bugs-return-627762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122835 invoked by alias); 5 Jan 2019 18:36:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122784 invoked by uid 48); 5 Jan 2019 18:36:09 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Sat, 05 Jan 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85052-4-U9y0rvB8Wy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00571.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #7 from Devin Hussey <husseydevin at gmail dot com> ---
Wait, silly me, this isn't about optimizations, this is about patterns.
It does the same thing it was doing for this code:
typedef unsigned u32x2 __attribute__((vector_size(8)));
typedef unsigned long long u64x2 __attribute__((vector_size(16)));
u64x2 cvt(u32x2 in)
{
return (u64x2) { (unsigned long long)in[0], (unsigned long long)in[1] };
}
>From gcc-bugs-return-627763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 18:37:04 2019
Return-Path: <gcc-bugs-return-627763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124315 invoked by alias); 5 Jan 2019 18:37:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124151 invoked by uid 48); 5 Jan 2019 18:37:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Sat, 05 Jan 2019 18:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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-85052-4-3YbuvJ7YMO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00572.txt.bz2
Content-length: 308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, I've posted in the meantime a newer version of the patch that should
handle the 2x narrowing or 2x widening cases better, see
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00129.html
>From gcc-bugs-return-627764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 18:42:07 2019
Return-Path: <gcc-bugs-return-627764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2642 invoked by alias); 5 Jan 2019 18:42:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2572 invoked by uid 48); 5 Jan 2019 18:42:03 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] [regression 9.0] scan-ipa-dump inline "Inlined tp_sum/
Date: Sat, 05 Jan 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
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:
Message-ID: <bug-88711-4-CFiTGjfDFd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00573.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
--- Comment #1 from kargl at gcc dot gnu.org ---
> The likely cause of this regression is
>
> ------------------------------------------------------------------------
> r267600 | hubicka | 2019-01-05 09:47:34 -0800 (Sat, 05 Jan 2019) | 2 lines
>
> * ipa-fnsummary.c (analyze_function_body): Fix accounting of time.
Definitely caused by r267600. Verified by 'svn merge -r267600:267599 .'
to remove offending patch.
Perhaps, the scan line in the testcase needs to be adjusted?
>From gcc-bugs-return-627765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 19:35:10 2019
Return-Path: <gcc-bugs-return-627765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14333 invoked by alias); 5 Jan 2019 19:35:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14276 invoked by uid 48); 5 Jan 2019 19:35:05 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88710] [F08] Sourced allocation of array fails, yielding wrong bounds and result
Date: Sat, 05 Jan 2019 19:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-88710-4-FJWfBDSvmA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00574.txt.bz2
Content-length: 1441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88710
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-05
CC| |burnus at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The behavior has changed between revisions r265171 (2018-10-15)
lbound/ubound(a): -1 -1 1 2 1 1
lbound/ubound(b): -1 -1 1 2 1 1
lbound/ubound(c): -1 -1 1 2 1 1
lbound/ubound(t): 0 0 0 3 2 0
and r265310 (2018-10-19)
lbound/ubound(a): -1 -1 1 2 1 1
lbound/ubound(b): -1 -1 1 2 1 1
lbound/ubound(c): -1 -1 1 2 1 1
lbound/ubound(t): 1 1 1 4 3 1
likely r265212 (pr67125).
Note that the block
do k = lbound(a,3), ubound(a,3)
do j = lbound(a,2), ubound(a,2)
do i = lbound(a,1), ubound(a,1)
write(*,'(1p,4(e23.16,1x))') &
& a(i,j,k), b(i,j,k), c(i,j,k), t(i,j,k)
end do
end do
end do
accesses 't' outside its bounds in both cases.
>From gcc-bugs-return-627766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 21:42:44 2019
Return-Path: <gcc-bugs-return-627766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123293 invoked by alias); 5 Jan 2019 21:42:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123193 invoked by uid 48); 5 Jan 2019 21:42:38 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] [regression 9.0] scan-ipa-dump inline "Inlined tp_sum/
Date: Sat, 05 Jan 2019 21:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
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 everconfirmed
Message-ID: <bug-88711-4-8VyKhCIC5c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00575.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-05
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed on darwin.
>From gcc-bugs-return-627767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 21:53:16 2019
Return-Path: <gcc-bugs-return-627767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11100 invoked by alias); 5 Jan 2019 21:53: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 11040 invoked by uid 48); 5 Jan 2019 21:53:10 -0000
From: "gary_mills at fastmail dot fm" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Sat, 05 Jan 2019 21: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary_mills at fastmail dot fm
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-SKjnXVo6hr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00576.txt.bz2
Content-length: 5784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #26 from Gary Mills <gary_mills at fastmail dot fm> ---
I have no concerns about removal of gcc support for Solaris 10: That is an
obsolete operating system, after all. illumos is equivalent to Solaris 11.
gas is used for illumos compilers on x86. It works on SPARC too, and avoids
the ICE. Unfortunately, gcc with gas can't be used to compile the SPARC
kernel. That's because some SPARC kernel files are written in assembler
language. These won't compile with gas, only with the native assembler. It
would be difficult, but not impossible, to use gcc with gas on SPARC hardware.
I've just attempted to build gcc-7.3.0 on SPARC with an even more restricted
configuration:
$
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
--without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
The compilers are not specified on the command line but they are in the
environment. The compilers were identified correctly.
The build got considerably farther, but ended with this error:
libtool: compile:
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/xgcc
-shared-libgcc
-B/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc
-nostdinc++
-L/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/src
-L/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/src/.libs
-L/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/libsupc++/.libs
-B/usr/local/sparc-sun-solaris2.11/bin/ -B/usr/local/sparc-sun-solaris2.11/lib/
-isystem /usr/local/sparc-sun-solaris2.11/include -isystem
/usr/local/sparc-sun-solaris2.11/sys-include
-I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/../libgcc
-I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/sparc-sun-solaris2.11
-I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include
-I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++
-D_GLIBCXX_SHARED -fno-implicit-templates -Wall -Wextra -Wwrite-strings
-Wcast-qual -Wabi -fdiagnostics-show-location=once -ffunction-sections
-fdata-sections -frandom-seed=new_opa.lo -g -O2 -std=gnu++1z -c
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc
-fPIC -DPIC -D_GLIBCXX_SHARED -o new_opa.o
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:
In function 'void* operator new(std::size_t, std::align_val_t)':
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:103:33:
error: 'aligned_alloc' was not declared in this scope
while (__builtin_expect ((p = aligned_alloc (align, sz)) == 0, false))
^~~~~~~~~~~~~
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:103:33:
note: suggested alternative:
In file included from /usr/include/stdlib.h:39:0,
from
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/cstdlib:75,
from
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/stdlib.h:36,
from
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:27:
/usr/include/iso/stdlib_c11.h:60:14: note: 'std::aligned_alloc'
extern void *aligned_alloc(size_t, size_t);
^~~~~~~~~~~~~
Makefile:936: recipe for target 'new_opa.lo' failed
make[6]: *** [new_opa.lo] Error 1
make[6]: Leaving directory
'/dpool/export/home/mills/Downloads/code/oi-userland-apr/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/libsupc++'
There is a patch which seems to fix this error:
--- gcc-7.1.0.orig/libstdc++-v3/libsupc++/new_opa.cc 2017-01-26
15:30:45.000000000 +0100
+++ gcc-7.1.0/libstdc++-v3/libsupc++/new_opa.cc 2017-05-04 17:16:25.920300456
+0200
@@ -31,7 +31,6 @@
using std::new_handler;
using std::bad_alloc;
-#if !_GLIBCXX_HAVE_ALIGNED_ALLOC
#if _GLIBCXX_HAVE__ALIGNED_MALLOC
#define aligned_alloc(al,sz) _aligned_malloc(sz,al)
#elif _GLIBCXX_HAVE_POSIX_MEMALIGN
@@ -82,7 +81,6 @@
return aligned_ptr;
}
#endif
-#endif
_GLIBCXX_WEAK_DEFINITION void *
operator new (std::size_t sz, std::align_val_t al)
I can't be certain that this patch does not have unwanted side effects, but it
seems correct.
genmddeps seems to be correct now:
<mills@t2000:862>$ build/sparcv7/gcc/build/genmddeps -?
genmddeps: invalid option `-?'
At least, it doesn't dump core now. The build got well past that point. It
did build xgcc this time:
<mills@t2000:865>$ build/sparcv7/./gcc/xgcc -v
Using built-in specs.
COLLECT_GCC=build/sparcv7/./gcc/xgcc
Target: sparc-sun-solaris2.11
Configured with:
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
--without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
Thread model: posix
gcc version 7.3.0 (GCC)
>From gcc-bugs-return-627768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 22:13:47 2019
Return-Path: <gcc-bugs-return-627768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123096 invoked by alias); 5 Jan 2019 22:13:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123024 invoked by uid 55); 5 Jan 2019 22:13:38 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Sat, 05 Jan 2019 22:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.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-87836-4-aHC29xUljO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00577.txt.bz2
Content-length: 7299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #27 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #26 from Gary Mills <gary_mills at fastmail dot fm> ---
> I have no concerns about removal of gcc support for Solaris 10: That is an
I've only mentioned it to make clear that the oldest version of Solaris
as that's going to be tested with change quite a bit once S10 support is
gone, certainly to something much newer than the snv_121 as in Illumos.
> obsolete operating system, after all. illumos is equivalent to Solaris 11.
No, it's not: while it's certainly closer to S11 than S10, it has still
been quite a way from snv_147 (the last OpenSolaris build) to snv_175
(aka Solaris 11.0). No need to tell me about OpenSolaris/Illumos, btw.:
I've been in the OpenSolaris Pilot from day one.
> gas is used for illumos compilers on x86. It works on SPARC too, and avoids
> the ICE. Unfortunately, gcc with gas can't be used to compile the SPARC
> kernel. That's because some SPARC kernel files are written in assembler
> language. These won't compile with gas, only with the native assembler. It
It shouldn't be too hard to introduce make rules (or rather change cw)
to build them with as directly, even if gcc on SPARC starts using gas.
Hasn't this already been done for Illumos on x86?
Alternatively, you can always rewrite them to use gas syntax, and I
doubt that there are many as-specific constructs or directives in there:
it's low-level kernel code, after all.
> would be difficult, but not impossible, to use gcc with gas on SPARC hardware.
>
> I've just attempted to build gcc-7.3.0 on SPARC with an even more restricted
> configuration:
>
> $
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
> --without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
>
> The compilers are not specified on the command line but they are in the
> environment. The compilers were identified correctly.
>
> The build got considerably farther, but ended with this error:
>
> libtool: compile:
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/xgcc
> -shared-libgcc
> -B/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc
> -nostdinc++
> -L/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/src
> -L/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/src/.libs
> -L/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/libsupc++/.libs
> -B/usr/local/sparc-sun-solaris2.11/bin/ -B/usr/local/sparc-sun-solaris2.11/lib/
> -isystem /usr/local/sparc-sun-solaris2.11/include -isystem
> /usr/local/sparc-sun-solaris2.11/sys-include
> -I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/../libgcc
> -I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/sparc-sun-solaris2.11
> -I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include
> -I/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++
> -D_GLIBCXX_SHARED -fno-implicit-templates -Wall -Wextra -Wwrite-strings
> -Wcast-qual -Wabi -fdiagnostics-show-location=once -ffunction-sections
> -fdata-sections -frandom-seed=new_opa.lo -g -O2 -std=gnu++1z -c
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc
> -fPIC -DPIC -D_GLIBCXX_SHARED -o new_opa.o
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:
> In function 'void* operator new(std::size_t, std::align_val_t)':
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:103:33:
> error: 'aligned_alloc' was not declared in this scope
> while (__builtin_expect ((p = aligned_alloc (align, sz)) == 0, false))
> ^~~~~~~~~~~~~
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:103:33:
> note: suggested alternative:
> In file included from /usr/include/stdlib.h:39:0,
> from
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/cstdlib:75,
> from
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/include/stdlib.h:36,
> from
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/libstdc++-v3/libsupc++/new_opa.cc:27:
> /usr/include/iso/stdlib_c11.h:60:14: note: 'std::aligned_alloc'
> extern void *aligned_alloc(size_t, size_t);
> ^~~~~~~~~~~~~
> Makefile:936: recipe for target 'new_opa.lo' failed
> make[6]: *** [new_opa.lo] Error 1
> make[6]: Leaving directory
> '/dpool/export/home/mills/Downloads/code/oi-userland-apr/components/developer/gcc-7/build/sparcv7/sparc-sun-solaris2.11/libstdc++-v3/libsupc++'
>
> There is a patch which seems to fix this error:
>
> --- gcc-7.1.0.orig/libstdc++-v3/libsupc++/new_opa.cc 2017-01-26
> 15:30:45.000000000 +0100
> +++ gcc-7.1.0/libstdc++-v3/libsupc++/new_opa.cc 2017-05-04 17:16:25.920300456
> +0200
> @@ -31,7 +31,6 @@
> using std::new_handler;
> using std::bad_alloc;
>
> -#if !_GLIBCXX_HAVE_ALIGNED_ALLOC
> #if _GLIBCXX_HAVE__ALIGNED_MALLOC
> #define aligned_alloc(al,sz) _aligned_malloc(sz,al)
> #elif _GLIBCXX_HAVE_POSIX_MEMALIGN
> @@ -82,7 +81,6 @@
> return aligned_ptr;
> }
> #endif
> -#endif
>
> _GLIBCXX_WEAK_DEFINITION void *
> operator new (std::size_t sz, std::align_val_t al)
This is already fixed in gcc 7.4.0.
> I can't be certain that this patch does not have unwanted side effects, but it
> seems correct.
>
> genmddeps seems to be correct now:
>
> <mills@t2000:862>$ build/sparcv7/gcc/build/genmddeps -?
> genmddeps: invalid option `-?'
>
> At least, it doesn't dump core now. The build got well past that point. It
> did build xgcc this time:
>
> <mills@t2000:865>$ build/sparcv7/./gcc/xgcc -v
> Using built-in specs.
> COLLECT_GCC=build/sparcv7/./gcc/xgcc
> Target: sparc-sun-solaris2.11
> Configured with:
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
> --without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
> Thread model: posix
> gcc version 7.3.0 (GCC)
Which suggest to let it complete and run make check afterwards, so you
can see if there are any unexpected failures. You should fine regular
postings of Solaris 10 and 11/SPARC testresults from the gcc-7 branch
there for comparison.
So unless something unexpected comes up, I belive this PR can be closed?
>From gcc-bugs-return-627769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 22:48:57 2019
Return-Path: <gcc-bugs-return-627769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23527 invoked by alias); 5 Jan 2019 22:48:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23255 invoked by uid 48); 5 Jan 2019 22:48:21 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Sat, 05 Jan 2019 22:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-VegISZXkaq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00578.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #3 from Matthias Kretz <kretz at kde dot org> ---
Did you consider the error introduced by scaling with __amax? I made sure that
the division is without error by zeroing the mantissa bits. Here's a motivating
example that shows an error of 1 ulp otherwise: https://godbolt.org/z/_U2K7e
About std::fma, how bad is the performance hit if there's no instruction for
it?
>From gcc-bugs-return-627770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 22:59:26 2019
Return-Path: <gcc-bugs-return-627770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59565 invoked by alias); 5 Jan 2019 22:59: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 59517 invoked by uid 48); 5 Jan 2019 22:59:22 -0000
From: "cfd@mnet-mail.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88710] [F08] Sourced allocation of array fails, yielding wrong bounds and result
Date: Sat, 05 Jan 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cfd@mnet-mail.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-88710-4-sbyhBWTxLV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00579.txt.bz2
Content-length: 351
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88710
--- Comment #2 from cfd@mnet-mail.de ---
Yes, the said block accesses 't' outside its bounds (because
the returned bounds are wrong).
Thanks for mentioning this.
For what it's worth, I have compiled the code also with '-Wall'
and '-Warray-bounds' but both these options didn't give any warning.
>From gcc-bugs-return-627771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 23:03:50 2019
Return-Path: <gcc-bugs-return-627771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64343 invoked by alias); 5 Jan 2019 23:03:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64276 invoked by uid 48); 5 Jan 2019 23:03:45 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Sat, 05 Jan 2019 23:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85052-4-EiraQbSuaq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00580.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #9 from Matthias Kretz <kretz at kde dot org> ---
(In reply to Devin Hussey from comment #7)
> Wait, silly me, this isn't about optimizations, this is about patterns.
Regarding optimizations, PR85048 is a first step (it lists all x86
single-instruction SIMD conversions). I also linked my library implementation
in #5, which provides optimizations for all cases on x86.
>From gcc-bugs-return-627772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 23:06:55 2019
Return-Path: <gcc-bugs-return-627772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72879 invoked by alias); 5 Jan 2019 23:06: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 72836 invoked by uid 48); 5 Jan 2019 23:06:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88710] [F08] Sourced allocation of array fails, yielding wrong bounds and result
Date: Sat, 05 Jan 2019 23:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88710-4-fMtAFCjeAb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00581.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88710
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> For what it's worth, I have compiled the code also with '-Wall'
> and '-Warray-bounds' but both these options didn't give any warning.
The relevant option is -fcheck=bounds.
>From gcc-bugs-return-627773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 23:10:17 2019
Return-Path: <gcc-bugs-return-627773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108419 invoked by alias); 5 Jan 2019 23:10:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108383 invoked by uid 48); 5 Jan 2019 23:10:13 -0000
From: "cfd@mnet-mail.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88710] [F08] Sourced allocation of array fails, yielding wrong bounds and result
Date: Sat, 05 Jan 2019 23:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cfd@mnet-mail.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-88710-4-0c8pLEgfPS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88710-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00582.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88710
--- Comment #4 from cfd@mnet-mail.de ---
Thanks, this caught the bounds violation with the following output:
lbound/ubound(a): -1 -1 1 2 1 1
lbound/ubound(b): -1 -1 1 2 1 1
lbound/ubound(c): -1 -1 1 2 1 1
lbound/ubound(t): 0 0 0 3 2 0
a, b, c, t:
At line 28 of file test_alloc.F90
Fortran runtime error: Index '1' of dimension 3 of array 't' above upper bound
of 0
Error termination. Backtrace:
#0 0x2b3018cf341a
#1 0x2b3018cf3f75
#2 0x2b3018cf4347
#3 0x403e97
#4 0x40400f
#5 0x2b301917182f
#6 0x4008d8
#7 0xffffffffffffffff
>From gcc-bugs-return-627774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 23:46:25 2019
Return-Path: <gcc-bugs-return-627774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128902 invoked by alias); 5 Jan 2019 23:46: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 128814 invoked by uid 48); 5 Jan 2019 23:46:20 -0000
From: "matt at godbolt dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88712] New: Optimization: mov edx, 0 not replaced with xor edx, edx in this case
Date: Sat, 05 Jan 2019 23:46: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matt at godbolt dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00583.txt.bz2
Content-length: 1153
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88712
Bug ID: 88712
Summary: Optimization: mov edx, 0 not replaced with xor edx,
edx in this case
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: matt at godbolt dot org
Target Milestone: ---
The code:
---snip
int func(int val, const int *ptr)
{
int res = val + 1234;
if (res == *ptr)
{
res = 0;
}
return res;
}
---
generates the following ASM on all version of GCC back to 4.9.x:
---
func(int, int const*):
lea eax, [rdi+1234]
mov edx, 0
cmp DWORD PTR [rsi], eax
cmove eax, edx
ret
---
The `mov edx, 0` is surprising to me. All the other compilers I tested (see
https://godbolt.org/z/Nt9pKp for more details) use the common `xor edx, edx`
(or `xor eax, eax`) idiom for zeroing edx.
Is this a missed optimization in the case of a cmov being generated, or am I
missing something subtle?
>From gcc-bugs-return-627775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 05 23:54:01 2019
Return-Path: <gcc-bugs-return-627775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10686 invoked by alias); 5 Jan 2019 23:54: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 10625 invoked by uid 48); 5 Jan 2019 23:53:56 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88712] Optimization: mov edx, 0 not replaced with xor edx, edx in this case
Date: Sat, 05 Jan 2019 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget
Message-ID: <bug-88712-4-foBuFrQEr3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00584.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88712
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is normally controlled by TARGET_USE_MOV0 but that seems like it is only
enabled for k6 and maybe size.
>From gcc-bugs-return-627776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 00:09:25 2019
Return-Path: <gcc-bugs-return-627776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29201 invoked by alias); 6 Jan 2019 00: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 29089 invoked by uid 48); 6 Jan 2019 00:09:20 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Sun, 06 Jan 2019 00:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-ZRSmmhw6Db@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00585.txt.bz2
Content-length: 1018
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #4 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Matthias Kretz from comment #3)
> Did you consider the error introduced by scaling with __amax? I made sure
> that the division is without error by zeroing the mantissa bits. Here's a
> motivating example that shows an error of 1 ulp otherwise:
> https://godbolt.org/z/_U2K7e
Your "reference" number seems strange. Why not do the computation with double
(or long double or mpfr) or use __builtin_hypotf? Note that it changes the
value.
How precise is hypot supposed to be? I know it is supposed to try and avoid
spurious overflow/underflow, but I am not convinced that it should aim for
correct rounding.
(I see that you are using clang in that godbolt link, with gcc I need to mark
the global variables with "extern const" to get a similar asm)
> About std::fma, how bad is the performance hit if there's no instruction for
> it?
FMA doesn't seem particularly relevant here.
>From gcc-bugs-return-627777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 00:19:58 2019
Return-Path: <gcc-bugs-return-627777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63660 invoked by alias); 6 Jan 2019 00:19: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 63593 invoked by uid 48); 6 Jan 2019 00:19:53 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/81871] bogus attribute alloc_align accepted
Date: Sun, 06 Jan 2019 00:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81871-4-bCYG9aP0Li@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00586.txt.bz2
Content-length: 200
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81871
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #3)
> Let me fix this.
Any progress?
>From gcc-bugs-return-627778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 00:29:45 2019
Return-Path: <gcc-bugs-return-627778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71941 invoked by alias); 6 Jan 2019 00: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 71870 invoked by uid 48); 6 Jan 2019 00:29:40 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/81871] bogus attribute alloc_align accepted
Date: Sun, 06 Jan 2019 00:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone cf_known_to_fail
Message-ID: <bug-81871-4-rJvBYgnTeu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00587.txt.bz2
Content-length: 1219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81871
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
Known to fail| |8.2.0
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Looks like r266195 fixed it.
$ cat t.c && gcc -S t.c
void __attribute__ ((alloc_align (1))) f (int);
void* __attribute__ ((alloc_align (1))) g (void*);
t.c:1:1: warning: ‘alloc_align’ attribute ignored on a function returning
‘void’ [-Wattributes]
1 | void __attribute__ ((alloc_align (1))) f (int);
| ^~~~
t.c:3:1: warning: ‘alloc_align’ attribute argument value ‘1’ refers to
parameter type ‘void *’ [-Wattributes]
3 | void* __attribute__ ((alloc_align (1))) g (void*);
| ^~~~
It's being tested by gcc.dg/attr-alloc_align-4.c so the bug can be resolved.
Thanks for the reminder!
>From gcc-bugs-return-627779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 00:38:42 2019
Return-Path: <gcc-bugs-return-627779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82209 invoked by alias); 6 Jan 2019 00:38: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 82131 invoked by uid 48); 6 Jan 2019 00:38:36 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85048] [missed optimization] vector conversions
Date: Sun, 06 Jan 2019 00:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85048-4-YemThcSd6g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85048-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85048-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00588.txt.bz2
Content-length: 1229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85048
Devin Hussey <husseydevin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |husseydevin at gmail dot com
--- Comment #5 from Devin Hussey <husseydevin at gmail dot com> ---
ARM/AArch64 NEON use these:
From To Intrinsic ARMv7-a AArch64
intXxY_t -> int2XxY_t vmovl_sX vmovl.sX sshll #0?
uintXxY_t. -> uint2XxY_t vmovl_uX vmovl.uX ushll #0?
[u]int2XxY_t -> [u]intXxY_t vmovn_[us]X vmovn.iX xtn
floatXxY_t -> intXxY_t vcvt[q]_sX_fX vcvt.sX.fX fcvtzs
floatXxY_t -> uintXxY_t vcvt[q]_uX_fX vcvt.uX.fX fcvtzu
intXxY_t -> floatXxY_t vcvt[q]_fX_sX vcvt.fX.sX scvtf
uintXxY_t -> floatXxY_t vcvt[q]_fX_uX vcvt.fX.uX ucvtf
float32x2_t -> float64x2_t vcvt_f32_f64 2x vcvt.f64.f32 fcvtl
float64x2_t -> float32x2_t vcvt_f64_f32 2x vcvt.f32.f64 fcvtn
Clang optimizes vmovl to vshll by zero for some reason.
float32x2_t <-> float64x2_t requires 2 VFP instructions on ARMv7-a.
>From gcc-bugs-return-627780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 00:49:49 2019
Return-Path: <gcc-bugs-return-627780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92264 invoked by alias); 6 Jan 2019 00:49: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 91935 invoked by uid 55); 6 Jan 2019 00:49:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88607] forward_list.h contains utf-8 charactor
Date: Sun, 06 Jan 2019 00:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88607-4-6sjne91ZkS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88607-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00589.txt.bz2
Content-length: 1180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88607
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sun Jan 6 00:49:11 2019
New Revision: 267607
URL: https://gcc.gnu.org/viewcvs?rev=267607&root=gcc&view=rev
Log:
PR libstdc++/88607 add tests using -finput-charset=ascii
This verifies that the <bits/extc++.h> header can be compiled with ASCII
as the input character set.
PR libstdc++/88607
* testsuite/17_intro/headers/c++1998/charset.cc: New test.
* testsuite/17_intro/headers/c++2011/charset.cc: New test.
* testsuite/17_intro/headers/c++2014/charset.cc: New test.
* testsuite/17_intro/headers/c++2017/charset.cc: New test.
* testsuite/17_intro/headers/c++2020/charset.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/17_intro/headers/c++1998/charset.cc
trunk/libstdc++-v3/testsuite/17_intro/headers/c++2011/charset.cc
trunk/libstdc++-v3/testsuite/17_intro/headers/c++2014/charset.cc
trunk/libstdc++-v3/testsuite/17_intro/headers/c++2017/charset.cc
trunk/libstdc++-v3/testsuite/17_intro/headers/c++2020/charset.cc
Modified:
trunk/libstdc++-v3/ChangeLog
>From gcc-bugs-return-627781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 05:01:40 2019
Return-Path: <gcc-bugs-return-627781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60362 invoked by alias); 6 Jan 2019 05:01: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 60154 invoked by uid 48); 6 Jan 2019 05:01:30 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/63156] web can't handle AUTOINC correctly
Date: Sun, 06 Jan 2019 05:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
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 assigned_to
Message-ID: <bug-63156-4-bhegEkANCj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00590.txt.bz2
Content-length: 878
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63156
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steven at gcc dot gnu.org
Assignee|steven at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #12 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #11)
> (In reply to Steven Bosscher from comment #7)
> > (In reply to Carrot from comment #6)
> > > Since it is intentionally to remove flag DF_REF_READ_WRITE on use,
> >
> > Ah, but I don't think that was the correct fix. The DEF and USE refs should
> > both have the flag set.
>
> Are you still working on this?
Guess not; unassigning and moving to cc
>From gcc-bugs-return-627782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 05:21:02 2019
Return-Path: <gcc-bugs-return-627782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75203 invoked by alias); 6 Jan 2019 05:21: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 75035 invoked by uid 48); 6 Jan 2019 05:20:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/78502] Analyze 'final'/'override' even for uninstantiated class templates
Date: Sun, 06 Jan 2019 05: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: 6.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-78502-4-VE46HJhxhx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78502-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78502-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00591.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78502
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at redhat dot com,
| |nathan at gcc dot gnu.org
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
since this might be an accepts-invalid for gcc (or a rejects-valid for clang)
I'm cc-ing the C++ FE maintainers for their interpretation of the standard.
>From gcc-bugs-return-627783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 05:22:58 2019
Return-Path: <gcc-bugs-return-627783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76746 invoked by alias); 6 Jan 2019 05:22: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 76712 invoked by uid 48); 6 Jan 2019 05:22:54 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80789] Better error for passing lambda with capture as function pointer
Date: Sun, 06 Jan 2019 05:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80789-4-NBo577Fhba@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00592.txt.bz2
Content-length: 213
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80789
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
not sure whether to cc the C++ FE maintainers or the diagnostics maintainers on
this...
>From gcc-bugs-return-627784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 05:25:38 2019
Return-Path: <gcc-bugs-return-627784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79632 invoked by alias); 6 Jan 2019 05:25: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 79008 invoked by uid 48); 6 Jan 2019 05:24:47 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/81980] Spurious -Wmissing-format-attribute warning in 32-bit mode
Date: Sun, 06 Jan 2019 05:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-81980-4-pfGlsPo9BE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00593.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81980
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org,
| |dodji at gcc dot gnu.org
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing diagnostics maintainers
>From gcc-bugs-return-627785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 06:51:26 2019
Return-Path: <gcc-bugs-return-627785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27953 invoked by alias); 6 Jan 2019 06:51:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27894 invoked by uid 48); 6 Jan 2019 06:51:20 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] New: _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 06:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: elrodc 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-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00594.txt.bz2
Content-length: 1429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Bug ID: 88713
Summary: _gfortran_internal_pack@PLT prevents vectorization
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: elrodc at gmail dot com
Target Milestone: ---
Created attachment 45350
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45350&action=edit
Fortran version of vectorization test.
I am attaching Fortran and C++ translations of a simple working example.
The C++ version is vectorized, while the Fortran version is not.
The code consists of two functions. One simply runs a for loop, calling the
other function.
The function is vectorizable across loop iterations. g++ does this
succcesfully.
However, gfortran does not, because it repacks data with
call _gfortran_internal_pack@PLT
so that it can no longer be vectorized across iterations.
I compiled with:
gfortran -Ofast -march=skylake-avx512 -mprefer-vector-width=512
-fno-semantic-interposition -shared -fPIC -S vectorization_test.cpp -o
gfortvectorization_test.s
g++ -Ofast -march=skylake-avx512 -mprefer-vector-width=512 -shared -fPIC -S
vectorization_test.cpp -o gppvectorization_test.s
LLVM (via flang and clang) successfully vectorizes both versions.
>From gcc-bugs-return-627786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 06:52:02 2019
Return-Path: <gcc-bugs-return-627786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29109 invoked by alias); 6 Jan 2019 06:52: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 29051 invoked by uid 48); 6 Jan 2019 06:51:57 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 06:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-oDmNrYTb4z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00595.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #1 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45351
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45351&action=edit
C++ version of the vectorization test case.
>From gcc-bugs-return-627787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 06:53:20 2019
Return-Path: <gcc-bugs-return-627787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39978 invoked by alias); 6 Jan 2019 06:53: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 39944 invoked by uid 48); 6 Jan 2019 06:53:13 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 06:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-hf35JW3cbO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00596.txt.bz2
Content-length: 241
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #2 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45352
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45352&action=edit
gfortran assembly output
>From gcc-bugs-return-627788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 06:54:04 2019
Return-Path: <gcc-bugs-return-627788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40916 invoked by alias); 6 Jan 2019 06:54: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 40830 invoked by uid 48); 6 Jan 2019 06:53:57 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 06:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-yzsG2Ol4l7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00597.txt.bz2
Content-length: 236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #3 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45353
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45353&action=edit
g++ assembly output
>From gcc-bugs-return-627789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 09:50:26 2019
Return-Path: <gcc-bugs-return-627789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1217 invoked by alias); 6 Jan 2019 09:50:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1166 invoked by uid 48); 6 Jan 2019 09:50:21 -0000
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] New: [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Sun, 06 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikpelinux at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00598.txt.bz2
Content-length: 3030
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Bug ID: 88714
Summary: [9 regression] bootstrap comparison failure on armv7l
since r265398
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: mikpelinux at gmail dot com
Target Milestone: ---
Attempting to bootstrap gcc-9.0 on armv7l fails for me with bootstrap
comparison failures on a large number of files:
rm -f stage_current
make[3]: Leaving directory '/mnt/scratch/objdir9'
Comparing stages 2 and 3
Bootstrap comparison failure!
armv7l-unknown-linux-gnueabi/libgomp/proc.o differs
armv7l-unknown-linux-gnueabi/libgomp/affinity.o differs
armv7l-unknown-linux-gnueabi/libgomp/oacc-parallel.o differs
armv7l-unknown-linux-gnueabi/libgomp/task.o differs
armv7l-unknown-linux-gnueabi/libgomp/env.o differs
armv7l-unknown-linux-gnueabi/libgomp/splay-tree.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/proc.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/affinity.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/oacc-parallel.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/task.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/env.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/splay-tree.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/oacc-mem.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/target.o differs
armv7l-unknown-linux-gnueabi/libgomp/.libs/priority_queue.o differs
.. about 600 more lines of the same
zlib/libz_a-uncompr.o differs
zlib/libz_a-crc32.o differs
zlib/libz_a-inftrees.o differs
zlib/libz_a-gzlib.o differs
zlib/libz_a-trees.o differs
Makefile:22315: recipe for target 'compare' failed
make[2]: *** [compare] Error 1
make[2]: Leaving directory '/mnt/scratch/objdir9'
Makefile:22294: recipe for target 'stage3-bubble' failed
make[1]: *** [stage3-bubble] Error 2
make[1]: Leaving directory '/mnt/scratch/objdir9'
Makefile:22357: recipe for target 'bootstrap' failed
make: *** [bootstrap] Error 2
Started with r265398 and still happens at r267600. I don't see this issue on
other targets, or when bootstrapping gcc-8.
Configured as:
/mnt/scratch/gcc-9-r267600/configure --prefix=/mnt/scratch/install9
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-linker-hash-style=gnu --enable-languages=c,c++ --enable-initfini-array
--disable-lto --disable-plugin --disable-libmudflap --without-isl
--without-cloog --disable-sjlj-exceptions --with-arch=armv7-a
--with-tune=cortex-a9 --with-float=hard --with-fpu=vfpv3-d16
--build=armv7l-unknown-linux-gnueabi
--with-gmp=/home/mikpe/pkgs/linux-armv7l/gmp-6.1.2
--with-mpfr=/home/mikpe/pkgs/linux-armv7l/mpfr-4.0.1
--with-mpc=/home/mikpe/pkgs/linux-armv7l/mpc-1.1.0
>From gcc-bugs-return-627790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:14:08 2019
Return-Path: <gcc-bugs-return-627790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17231 invoked by alias); 6 Jan 2019 10:14: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 17177 invoked by uid 48); 6 Jan 2019 10:14:01 -0000
From: "tomsies at mighty dot co.za" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] New: Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Sun, 06 Jan 2019 10:14: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tomsies at mighty dot co.za
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00599.txt.bz2
Content-length: 2468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
Bug ID: 88715
Summary: Cross Compile on Debian Linux to create a uClibc tool
chain GCC fails to compile
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tomsies at mighty dot co.za
Target Milestone: ---
System is Debian Linux (Debian 3.16.36-1+deb8u2 (2016-10-19) x86_64 GNU/Linux)
I have compiled uClibc-ng-1.0.31 using linux headers LinuxHeaders-2.6.32.25
This is installed in /opt/uCx
I try to build a cross compiler targeting this libc as follows
../gnuSource/gcc-8.2.0/configure --prefix=/opt/uCx --with-sysroot=/opt/uCx
--with-pkgversion=DDT --disable-bootstrap --target=i686-uClibc-linux
--enable-shared=no --disable-lto-plugin --disable-libsanitizer
--disable-boehm-gc --disable-libmudflap --disable-libgcj
--enable-languages=c,c++,fortran,lto,objc,obj-c++ --enable-libstdcxx-time
--enable-libstdcxx-threads --with-host-libstdcxx='-static -lstdc++ -lm'
--with-boot-ldflags='-static-libstdc++ -static-libgcc'
As soon as the compile starts to build i686-uClibc-linux objects configure
fails as below
configure:3687: /src/abuild/./gcc/xgcc -B/src/abuild/./gcc/
-B/opt/uCx/i686-uClibc-linux/bin/ -B/opt/uCx/i686-uClibc-linux/lib/ -isystem
/opt/uCx/i686-uClibc-linux/include -isystem
/opt/uCx/i686-uClibc-linux/sys-include -c -g -O2 conftest.c >&5
/src/abuild/./gcc/as: 106: exec: --32: not found
configure:3691: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "GNU C Runtime Library"
| #define PACKAGE_TARNAME "libgcc"
| #define PACKAGE_VERSION "1.0"
| #define PACKAGE_STRING "GNU C Runtime Library 1.0"
| #define PACKAGE_BUGREPORT ""
| #define PACKAGE_URL "http://www.gnu.org/software/libgcc/"
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:3705: error: in `/src/abuild/i686-uClibc-linux/libgcc':
configure:3708: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
What the issue seems to be is that the x-compile in GCC has built a script to
replace the as command using exec. This script is using exec without proper
quoting so exec is trying to exec --32 as well as as
/src/abuild/./gcc/as --32 -o conftest.o /tmp/ccE1mSpa.s
>From gcc-bugs-return-627791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:22:41 2019
Return-Path: <gcc-bugs-return-627791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23611 invoked by alias); 6 Jan 2019 10:22: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 23561 invoked by uid 48); 6 Jan 2019 10:22:36 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Sun, 06 Jan 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antoshkka at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87431-4-4yhEhJIC6z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00600.txt.bz2
Content-length: 383
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
--- Comment #11 from Antony Polukhin <antoshkka at gmail dot com> ---
Looks good.
Note that boost::variant went further: if all the types are nothrow movable
then variant always does the trick with moving from temporary. In that way
`valueless_by_exception()` like states never happen.
Such approach may not fit the libstdc++.
>From gcc-bugs-return-627792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:26:24 2019
Return-Path: <gcc-bugs-return-627792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31767 invoked by alias); 6 Jan 2019 10:26:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31666 invoked by uid 55); 6 Jan 2019 10:26:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88363] [9 Regression] alloc_align attribute doesn't accept enumerated arguments
Date: Sun, 06 Jan 2019 10:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88363-4-UcYsBsNIbN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00601.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88363
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sun Jan 6 10:25:46 2019
New Revision: 267608
URL: https://gcc.gnu.org/viewcvs?rev=267608&root=gcc&view=rev
Log:
PR c/88363
* c-c++-common/attributes-4.c (falloc_align_int128,
falloc_size_int128): Guard with #ifdef __SIZEOF_INT128__.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/c-c++-common/attributes-4.c
>From gcc-bugs-return-627793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:42:25 2019
Return-Path: <gcc-bugs-return-627793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60403 invoked by alias); 6 Jan 2019 10:42:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60335 invoked by uid 48); 6 Jan 2019 10:42:20 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sun, 06 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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-88653-4-UQNN6jJDC0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00602.txt.bz2
Content-length: 526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #15 from Murat Tekeev <mtekeev at yandex dot ru> ---
I downloaded the current version of Cygwin and reinstalled it all again
(previously removing everything that was installed).
On a 64-bit version of Cygwin and now everything runs fine with gfortran
7.4.0-1.
On the 32-bit version of Cygwin with the gfortran 7.4.0-1 compiler, the problem
remained (which for me, however, is not so important).
Thank you very much, Thomas!
Sincerely yours, Murat Tekeev
>From gcc-bugs-return-627794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:43:10 2019
Return-Path: <gcc-bugs-return-627794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69457 invoked by alias); 6 Jan 2019 10:43: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 66465 invoked by uid 48); 6 Jan 2019 10:43:05 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc blocked bug_severity
Message-ID: <bug-88713-4-lLdUb5acBl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00603.txt.bz2
Content-length: 1689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
Blocks| |36854
Severity|normal |enhancement
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
First, a few remarks on the code: It is written in a suboptmial way
regarding the way Fortran lays out its memory.
The code does
real, dimension(N,3), intent(out) :: X
real, dimension(N,10), intent(in) :: BPP
and then
do concurrent (i = 1:N)
X(i,:) = fpdbacksolve(BPP(i,1:3), BPP(i,5:10))
end do
The problem is that BPP(i,1:3) is not contiguous in memory.
Fortran lays out the memory for that array as
BPP(1,1), BPP(2,1), BPP(3,1), BPP(4,1), ..., BPP(1,2)
so you are accessing your memory with a stride of n in the
expressions BPP(i,1:3) and BPP(i,5:10). This is very inefficient
anyway, vectorization would not really help in this case.
So, if you change your code to
real, dimension(3,N), intent(out) :: X
real, dimension(10,N), intent(in) :: BPP
do concurrent (i = 1:N)
X(i,:) = fpdbacksolve(BPP(1:3,i), BPP(5:10,i))
end do
then processBPP will be inlined completely, and memory accesses will
be contiguous.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36854
[Bug 36854] [meta-bug] fortran front-end optimization
>From gcc-bugs-return-627795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:47:39 2019
Return-Path: <gcc-bugs-return-627795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26701 invoked by alias); 6 Jan 2019 10:47: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 26633 invoked by uid 48); 6 Jan 2019 10:47:32 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sun, 06 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88653-4-Nz2AM2zAiW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00604.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #16 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
OK, I'll close this one as WORKSFORME then.
Regards
Thomas
>From gcc-bugs-return-627796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 10:58:41 2019
Return-Path: <gcc-bugs-return-627796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38389 invoked by alias); 6 Jan 2019 10:58:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38336 invoked by uid 48); 6 Jan 2019 10:58:37 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Sun, 06 Jan 2019 10:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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:
Message-ID: <bug-88653-4-7HkqgONpkZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00605.txt.bz2
Content-length: 148
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #17 from Murat Tekeev <mtekeev at yandex dot ru> ---
Thank you very much, Thomas!
>From gcc-bugs-return-627797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 11:02:45 2019
Return-Path: <gcc-bugs-return-627797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44149 invoked by alias); 6 Jan 2019 11:02: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 43657 invoked by uid 48); 6 Jan 2019 11:02:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88712] Optimization: mov edx, 0 not replaced with xor edx, edx in this case
Date: Sun, 06 Jan 2019 11:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 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: cc
Message-ID: <bug-88712-4-qCFeNbv92v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00606.txt.bz2
Content-length: 1929
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88712
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In this case it is because this transformation (mov $0, reg to xor reg, reg) is
done during peephole2 and on this testcase it isn't possible, because we have:
(insn 28 4 21 2 (set (reg/v:SI 0 ax [orig:83 <retval> ] [83])
(plus:SI (reg:SI 5 di [88])
(const_int 1234 [0x4d2]))) "pr88712.c":4:7 186 {*leasi}
(expr_list:REG_DEAD (reg:SI 5 di [88])
(nil)))
(insn 21 28 26 2 (set (reg:CCZ 17 flags)
(compare:CCZ (mem:SI (reg:DI 4 si [89]) [1 *ptr_6(D)+0 S4 A32])
(reg/v:SI 0 ax [orig:83 <retval> ] [83]))) "pr88712.c":6:9 11
{*cmpsi_1}
(expr_list:REG_DEAD (reg:DI 4 si [89])
(nil)))
(insn 26 21 23 2 (set (reg:SI 1 dx [87])
(const_int 0 [0])) "pr88712.c":6:9 67 {*movsi_internal}
(expr_list:REG_EQUIV (const_int 0 [0])
(nil)))
(insn 23 26 18 2 (set (reg/v:SI 0 ax [orig:83 <retval> ] [83])
(if_then_else:SI (ne (reg:CCZ 17 flags)
(const_int 0 [0]))
(reg/v:SI 0 ax [orig:83 <retval> ] [83])
(reg:SI 1 dx [87]))) "pr88712.c":6:9 939 {*movsicc_noc}
(expr_list:REG_DEAD (reg:CCZ 17 flags)
(expr_list:REG_DEAD (reg:SI 1 dx [87])
(nil))))
so the clearing of %edx is sandwiched in between the cmp and cmov. Later on in
this case sched2 reorders those and so we at that point could replace it, but
we don't have another peephole2 pass and passes after sched2 don't have the
needed infrastructure to check if the flags are dead (because movl $0, reg
doesn't clobber flags, but xorl reg, reg does).
>From gcc-bugs-return-627798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 11:45:53 2019
Return-Path: <gcc-bugs-return-627798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85272 invoked by alias); 6 Jan 2019 11:45:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85108 invoked by uid 48); 6 Jan 2019 11:45:46 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88716] New: Improved diagnostics: No detection of conflicting function definitions in some cases.
Date: Sun, 06 Jan 2019 11:45: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: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88716-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00607.txt.bz2
Content-length: 1308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88716
Bug ID: 88716
Summary: Improved diagnostics: No detection of conflicting
function definitions in some cases.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Consider the following two test cases (prog1.c):
void f(x)
int x;
{
}
void f(int, int);
void f();
int main() {}
and (prog2.c):
void f(x)
int x;
{
}
void f();
void f(int, int);
int main() {}
Both have compile time undefined behaviour because of conflicting declarations
of the function f.
The only difference between them is the reordering of the two last
declarations.
When the first test case is compiled with
gcc prog1.c -Wall -Wextra -std=c11 -pedantic-errors
The undefined behaviour is detected and an error message is outputed.
When the second test case is compiled with
gcc prog2.c -Wall -Wextra -std=c11 -pedantic-errors
The undefined behaviour is not detected.
It would be good if gcc could detect the undefined behaviour even in the second
case.
>From gcc-bugs-return-627799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:03:19 2019
Return-Path: <gcc-bugs-return-627799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101545 invoked by alias); 6 Jan 2019 12:03:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101452 invoked by uid 48); 6 Jan 2019 12:03:12 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Sun, 06 Jan 2019 12:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: REOPENED
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:
Message-ID: <bug-87431-4-mpneVWQRuX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00608.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yeah that unconditional move might actually be more expensive than just
constructing directly. E.g. if the move constructor isn't really cheap, or if
it will memcpy a large object. If an exception is rare in practice, then it
might be better to "risk" the exception by constructing directly. It's a trade
off.
>From gcc-bugs-return-627800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:07:14 2019
Return-Path: <gcc-bugs-return-627800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104927 invoked by alias); 6 Jan 2019 12:07: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 104875 invoked by uid 48); 6 Jan 2019 12:07:09 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88716] Improved diagnostics: No detection of conflicting function definitions in some cases.
Date: Sun, 06 Jan 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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 bug_severity
Message-ID: <bug-88716-4-yLJXH9bsaI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88716-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88716-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00609.txt.bz2
Content-length: 523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88716
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-06
Ever confirmed|0 |1
Severity|normal |enhancement
>From gcc-bugs-return-627802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:49:48 2019
Return-Path: <gcc-bugs-return-627802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40117 invoked by alias); 6 Jan 2019 12:49: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 40038 invoked by uid 55); 6 Jan 2019 12:49:41 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88658] [9 Regression] Intrinsic MAX1 returns a REAL result, should be INTEGER.
Date: Sun, 06 Jan 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88658-4-3vUpwkHyBP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00611.txt.bz2
Content-length: 888
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88658
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Jan 6 12:48:58 2019
New Revision: 267609
URL: https://gcc.gnu.org/viewcvs?rev=267609&root=gcc&view=rev
Log:
2019-01-06 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/88658
* gfortran.h: Add macro gfc_real_4_kind
* simplify.c (simplify_min_max): Special case for the types of
AMAX0, AMIN0, MAX1 and MIN1, which actually change the types of
their arguments.
2019-01-06 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/88658
* gfortran.dg/min_max_type_2.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/min_max_type_2.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/simplify.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:49:16 2019
Return-Path: <gcc-bugs-return-627801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39240 invoked by alias); 6 Jan 2019 12:49: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 39190 invoked by uid 48); 6 Jan 2019 12:49:11 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Sun, 06 Jan 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antoshkka at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87431-4-2EZ5NBGBBL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00610.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
--- Comment #13 from Antony Polukhin <antoshkka at gmail dot com> ---
Yeah... but some whitelist of types to move could be hardcoded. For example
std::basic_string, std::vector, std::unique_ptr and std::shared_ptr could be
safely moved and `valueless_by_exception()` never happen for them. Those types
cover some of the popular std::variant usages and the overhead from
`valueless_by_exception()` will be avoided for those cases.
>From gcc-bugs-return-627803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:50:42 2019
Return-Path: <gcc-bugs-return-627803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41162 invoked by alias); 6 Jan 2019 12:50: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 41130 invoked by uid 48); 6 Jan 2019 12:50:38 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88658] [9 Regression] Intrinsic MAX1 returns a REAL result, should be INTEGER.
Date: Sun, 06 Jan 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88658-4-oVNrTLf5I2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00612.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88658
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk, closing.
>From gcc-bugs-return-627804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:53:55 2019
Return-Path: <gcc-bugs-return-627804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43333 invoked by alias); 6 Jan 2019 12:53: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 43152 invoked by uid 48); 6 Jan 2019 12:53:47 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88584] GCC thinks that the type is complete dispite shaddowing.
Date: Sun, 06 Jan 2019 12:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88584-4-AI0aWgpA43@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88584-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88584-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00613.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88584
--- Comment #7 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #6)
> This looks like a case that was missed in, or broken by, my fix for bug
> 13801, which was supposed to address such cases of entities with different
> (compatible) types in different scopes. It seems GCC handled this
> correctly (i.e. produced an error) in the 3.4 release series only.
Does this mean that we can change the status for this bug report from
UNCONFIRMED to NEW?
>From gcc-bugs-return-627805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:54:44 2019
Return-Path: <gcc-bugs-return-627805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44526 invoked by alias); 6 Jan 2019 12:54:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44444 invoked by uid 48); 6 Jan 2019 12:54:40 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/66229] LTO fails with -fauto-profile on mcf
Date: Sun, 06 Jan 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-66229-4-WjY9vOKpgW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00614.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66229
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-06
Assignee|hubicka at gcc dot gnu.org |unassigned at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Does this still fail with Bin's fixes?
>From gcc-bugs-return-627806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:58:11 2019
Return-Path: <gcc-bugs-return-627806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48754 invoked by alias); 6 Jan 2019 12:58:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48662 invoked by uid 48); 6 Jan 2019 12:58:04 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81668] LTO ODR warnings are not helpful
Date: Sun, 06 Jan 2019 12:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81668-4-iPpxKM9X88@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00615.txt.bz2
Content-length: 299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81668
--- Comment #13 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Warnings from comment #8 are fixed now. I would love to know if there are any
issues with what GCC 9 outputs. We still can't track locations to the original
.o files though.
>From gcc-bugs-return-627807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 12:59:04 2019
Return-Path: <gcc-bugs-return-627807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50045 invoked by alias); 6 Jan 2019 12:59: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 49984 invoked by uid 48); 6 Jan 2019 12:59:01 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84044] Spurious -Wodr warning with -flto
Date: Sun, 06 Jan 2019 12:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-84044-4-4Bkg095MLV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84044-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00616.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84044
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Fixed some time ago.
>From gcc-bugs-return-627808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 13:02:36 2019
Return-Path: <gcc-bugs-return-627808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53751 invoked by alias); 6 Jan 2019 13:02:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53646 invoked by uid 48); 6 Jan 2019 13:02:31 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85433] -fdiagnostics-color=auto doesn't work properly with LTO
Date: Sun, 06 Jan 2019 13: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.0.1
X-Bugzilla-Keywords: diagnostic, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to
Message-ID: <bug-85433-4-tKf2EXsLlB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85433-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85433-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00617.txt.bz2
Content-length: 1240
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85433
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at redhat dot com
Assignee|hubicka at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I looked into this more and problem is collect2 which creates the file. This is
done to handle rpo files. For those compilation is done multiple times until
all templates are needed. In this case error messages from earlier runs are
discarded and that is why we can't output the directly to terminal.
Obviously this is silly to do with LTO, but at the time we create temporary we
do not know if we will LTO or not because linker is called later.
Jason, I wonder are RPO files still relevant and whether there is something to
do about this? I am unassigning myself since I do not know what to do. However
in my tree I simply have hack that disables the RPO path and this gets me nice
colorful warnings (and they come when they are found, not several minutes
later)
>From gcc-bugs-return-627809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 13:04:31 2019
Return-Path: <gcc-bugs-return-627809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55810 invoked by alias); 6 Jan 2019 13:04:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55723 invoked by uid 48); 6 Jan 2019 13:04:24 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/87525] [7/8/9 Regression] infinite loop generated for fread() if enabling -flto and -D_FORTIFY_SOURCE=2
Date: Sun, 06 Jan 2019 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-87525-4-AwZtGevHkz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87525-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87525-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00618.txt.bz2
Content-length: 763
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87525
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|infinite loop generated for |[7/8/9 Regression] infinite
|fread() if enabling -flto |loop generated for fread()
|and -D_FORTIFY_SOURCE=2 |if enabling -flto and
| |-D_FORTIFY_SOURCE=2
--- Comment #12 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I will take a look - symtab handling with multiple declarations is sliperly :(.
I have added regression marker because it definitly regress wrt pre-lto time.
>From gcc-bugs-return-627810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 13:26:22 2019
Return-Path: <gcc-bugs-return-627810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27363 invoked by alias); 6 Jan 2019 13: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 27292 invoked by uid 48); 6 Jan 2019 13:26:16 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88713-4-fh4JLqegPS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00619.txt.bz2
Content-length: 787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
An additional point. The called routine has
pure function fpdbacksolve(x, S) result(Uix)
real, dimension(3) :: Uix
... and so on. This _requires_ Uix to be contiguous in memory,
so we need to call the internal pack routine.
This is something we cannot change easily. So, the workaround:
Use the appropriate memory layout in your Fortran programs.
>From gcc-bugs-return-627811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 13:26:22 2019
Return-Path: <gcc-bugs-return-627811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27379 invoked by alias); 6 Jan 2019 13:26:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27309 invoked by uid 48); 6 Jan 2019 13:26:18 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36854] [meta-bug] fortran front-end optimization
Date: Sun, 06 Jan 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-36854-4-xy9LAVlxxr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00620.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36854
Bug 36854 depends on bug 88713, which changed state.
Bug 88713 Summary: _gfortran_internal_pack@PLT prevents vectorization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
>From gcc-bugs-return-627812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 13:49:44 2019
Return-Path: <gcc-bugs-return-627812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101704 invoked by alias); 6 Jan 2019 13:49:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101634 invoked by uid 48); 6 Jan 2019 13:49:39 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88606] ICE: verify_type failed (error: type variant differs by TYPE_TRANSPARENT_AGGR)
Date: Sun, 06 Jan 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88606-4-7Hy9mzMyqY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00621.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88606
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-627813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 13:58:12 2019
Return-Path: <gcc-bugs-return-627813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107358 invoked by alias); 6 Jan 2019 13:58:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107300 invoked by uid 48); 6 Jan 2019 13:58:08 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88606] [9 Regression] ICE: verify_type failed (error: type variant differs by TYPE_TRANSPARENT_AGGR)
Date: Sun, 06 Jan 2019 13:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88606-4-yoBwSFPmpG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00622.txt.bz2
Content-length: 628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88606
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|ICE: verify_type failed |[9 Regression] ICE:
|(error: type variant |verify_type failed (error:
|differs by |type variant differs by
|TYPE_TRANSPARENT_AGGR) |TYPE_TRANSPARENT_AGGR)
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Regression then, will take a look.
>From gcc-bugs-return-627814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 14:18:51 2019
Return-Path: <gcc-bugs-return-627814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2898 invoked by alias); 6 Jan 2019 14:18: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 2846 invoked by uid 48); 6 Jan 2019 14:18:47 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] New: Unnecessary vzeroupper
Date: Sun, 06 Jan 2019 14:18: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: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00623.txt.bz2
Content-length: 1317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
Bug ID: 88717
Summary: Unnecessary vzeroupper
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: ubizjak at gmail dot com, wei3.xiao at intel dot com,
xuepeng.guo at intel dot com
Target Milestone: ---
Target: i386,x86_64
[hjl@gnu-cfl-1 tmp]$ cat x.i
typedef float __v16sf __attribute__ ((__vector_size__ (64)));
typedef float __m512 __attribute__ ((__vector_size__ (64), __may_alias__));
void
foo (float *p, __m512 x)
{
*p = ((__v16sf)x)[0];
}
[hjl@gnu-cfl-1 tmp]$ gcc -mavx512f -S x.i -O2
[hjl@gnu-cfl-1 tmp]$ cat x.s
.file "x.i"
.text
.p2align 4,,15
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
vmovss %xmm0, (%rdi)
vzeroupper
ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.ident "GCC: (GNU) 8.2.1 20181215 (Red Hat 8.2.1-6)"
.section .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 tmp]$
Since __m512 is passed to foo, vzeroupper isn't needed.
>From gcc-bugs-return-627815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 14:35:31 2019
Return-Path: <gcc-bugs-return-627815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17816 invoked by alias); 6 Jan 2019 14:35:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17778 invoked by uid 48); 6 Jan 2019 14:35:26 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88718] New: Strange inconsistency between old style and new style declarations of iinline functions.
Date: Sun, 06 Jan 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00624.txt.bz2
Content-length: 1289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88718
Bug ID: 88718
Summary: Strange inconsistency between old style and new style
declarations of iinline functions.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
GCC is behaving inconsistently for the following two test cases:
prog1.c:
static int x;
inline void g(int a[sizeof(x)])
{
}
int main()
{
}
prog2.c:
static int x;
inline void g(a)
int a[sizeof(x)];
{
}
int main()
{
}
Compiling the first test case with the following compilation command line
gcc prog1.c -Wall -Wextra -std=c11 -pedantic-errors
gives no error message.
Compiling the second test case with the following compilation command line
gcc prog2.c -Wall -Wextra -std=c11 -pedantic-errors
gives the following error message:
error: 'x' is static but used in inline function 'g' which is not static
I think there should be an error message in both cases because of 6.7.4/3. At
least the two test cases should behave consistently.
>From gcc-bugs-return-627816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 15:20:52 2019
Return-Path: <gcc-bugs-return-627816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32076 invoked by alias); 6 Jan 2019 15:20:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32018 invoked by uid 48); 6 Jan 2019 15:20:47 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88694] constexpr isn't captured correctly in lambda
Date: Sun, 06 Jan 2019 15:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88694-4-zKrAAT9YvI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00625.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88694
ensadc at mailnesia dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ensadc at mailnesia dot com
--- Comment #4 from ensadc at mailnesia dot com ---
Further reduced:
template <typename T, T U> struct A {
static constexpr T e = U;
constexpr operator int () { return e; }
};
struct D { template <int> void print (); };
int
main ()
{
D d;
[&](auto i) { auto x = [&] { d.print<i>(); }; }(A<int, 0>{});
}
>From gcc-bugs-return-627817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 15:43:19 2019
Return-Path: <gcc-bugs-return-627817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18999 invoked by alias); 6 Jan 2019 15:43:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12928 invoked by uid 48); 6 Jan 2019 15:43:14 -0000
From: "chenjunjie9208 at 163 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88719] New: [9 Regression] wrong code at -O2, -O3, and -Os on x86_64-linux-gnu
Date: Sun, 06 Jan 2019 15:43: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: chenjunjie9208 at 163 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-88719-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00626.txt.bz2
Content-length: 2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88719
Bug ID: 88719
Summary: [9 Regression] wrong code at -O2, -O3, and -Os on
x86_64-linux-gnu
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: chenjunjie9208 at 163 dot com
Target Milestone: ---
$ gcc -v
Using built-in specs.
COLLECT_GCC=./gcc
COLLECT_LTO_WRAPPER=/home/wgc/installs/gcc_trunks/trunk_r267367/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ./configure LDFLAGS=-Wl,--no-as-needed
--prefix=/home/wgc/installs/gcc_trunks/trunk_r267367
--with-gmp=/home/wgc/installs/gmp-6.1.2
--with-mpfr=/home/wgc/installs/mpfr-4.0.1
--with-mpc=/home/wgc/installs/mpc-1.1.0 --with-isl= --with-cloog=
--enable-languages=c,c++ --disable-multilib --disable-bootstrap
Thread model: posix
gcc version 9.0.0 20181223 (experimental) (GCC)
$ gcc -O0 program.c
$ ./a.out
0
$ gcc -O1 program.c
$ ./a.out
0
$ gcc -O2 program.c
$ ./a.out
-60
$ gcc -O3 program.c
$ ./a.out
-60
$ gcc -Os program.c
$ ./a.out
-60
$ cat program.c
struct a {
unsigned char b;
};
union {
short int c;
long int b;
} d = {2};
short int *e = &d.c;
long int *f[][1] = {&d.b, &d.b, &d.b, &d.b};
long int **g = &f[0][3];
unsigned int h;
int main() {
struct a i = {};
for (; i.b != 60; ++i.b)
if (**g = 0)
;
else if (*e)
--h;
printf("%d\n", h);
return 0;
}
The used operating system and CPU are as below:
Distributor ID: Ubuntu
Description: Ubuntu 14.04.5 LTS
Release: 14.04
Codename: trusty
Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
>From gcc-bugs-return-627819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 15:52:24 2019
Return-Path: <gcc-bugs-return-627819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22633 invoked by alias); 6 Jan 2019 15:52: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 22506 invoked by uid 55); 6 Jan 2019 15:52:19 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86517] relocation R_X86_64_32 against `.rodata.str1.1' can not be used when making a shared object with LTO
Date: Sun, 06 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86517-4-IVcQ3nZMl6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00628.txt.bz2
Content-length: 581
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86517
--- Comment #10 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Sun Jan 6 15:51:45 2019
New Revision: 267610
URL: https://gcc.gnu.org/viewcvs?rev=267610&root=gcc&view=rev
Log:
PR lto/86517
PR lto/88185
* lto-opts.c (lto_write_options): Always stream PIC/PIE mode.
* lto-wrapper.c (merge_and_complain): Fix merging of PIC/PIE.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/lto-opts.c
branches/gcc-8-branch/gcc/lto-wrapper.c
>From gcc-bugs-return-627818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 15:52:24 2019
Return-Path: <gcc-bugs-return-627818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22624 invoked by alias); 6 Jan 2019 15:52: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 22499 invoked by uid 55); 6 Jan 2019 15:52:18 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88185] LTO merges -fPIC/fpie and -fPIE/-fpie options to nothing - fails to warn when both are specified
Date: Sun, 06 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88185-4-cAaHvr9PQh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00627.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88185
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Sun Jan 6 15:51:45 2019
New Revision: 267610
URL: https://gcc.gnu.org/viewcvs?rev=267610&root=gcc&view=rev
Log:
PR lto/86517
PR lto/88185
* lto-opts.c (lto_write_options): Always stream PIC/PIE mode.
* lto-wrapper.c (merge_and_complain): Fix merging of PIC/PIE.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/lto-opts.c
branches/gcc-8-branch/gcc/lto-wrapper.c
>From gcc-bugs-return-627820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 15:53:44 2019
Return-Path: <gcc-bugs-return-627820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25819 invoked by alias); 6 Jan 2019 15: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 25739 invoked by uid 48); 6 Jan 2019 15:53:38 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88185] LTO merges -fPIC/fpie and -fPIE/-fpie options to nothing - fails to warn when both are specified
Date: Sun, 06 Jan 2019 15:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88185-4-weqJsoNvqA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00629.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88185
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 15:56:18 2019
Return-Path: <gcc-bugs-return-627821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29302 invoked by alias); 6 Jan 2019 15:56:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29156 invoked by uid 48); 6 Jan 2019 15:56:14 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] New: Strange error message about nested function declared but not defined when using inline.
Date: Sun, 06 Jan 2019 15:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00630.txt.bz2
Content-length: 907
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
Bug ID: 88720
Summary: Strange error message about nested function declared
but not defined when using inline.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
static void f();
int main()
{
inline void f();
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
The following error message was outputed:
error: nested function 'f' declared but never defined
Expected behaviour:
No error message outputed.
Note:
Clang accepts the program without any error message outputed.
>From gcc-bugs-return-627822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 16:03:57 2019
Return-Path: <gcc-bugs-return-627822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64837 invoked by alias); 6 Jan 2019 16:03: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 64683 invoked by uid 48); 6 Jan 2019 16:03:52 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/51765] Testsuite ICEs with -flto
Date: Sun, 06 Jan 2019 16:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51765-4-FP3LEwwlSS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00631.txt.bz2
Content-length: 137
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51765
--- Comment #7 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I get only 2 now.
>From gcc-bugs-return-627823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 16:08:21 2019
Return-Path: <gcc-bugs-return-627823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78311 invoked by alias); 6 Jan 2019 16:08: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 78258 invoked by uid 48); 6 Jan 2019 16:08:15 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/51765] [9 Regression] Testsuite ICEs with -flto
Date: Sun, 06 Jan 2019 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-51765-4-Mz8j4It6cI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00632.txt.bz2
Content-length: 3748
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51765
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Testsuite ICEs with -flto |[9 Regression] Testsuite
| |ICEs with -flto
--- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
... which I forgot to attach :)
FAIL: gcc.dg/nested-func-12.c (internal compiler error)
FAIL: gcc.dg/nested-func-9.c (internal compiler error)
UNRESOLVED: gcc.dg/tree-prof/pr77698.c scan-rtl-dump-times alignments "internal
loop alignment added" 1
FAIL: g++.dg/ext/vector33.C -std=c++14 (internal compiler error)
FAIL: g++.dg/ext/vector33.C -std=c++17 (internal compiler error)
/aux/hubicka/trunk4/gcc/testsuite/gcc.dg/nested-func-12.c: In function 'main':
/aux/hubicka/trunk4/gcc/testsuite/gcc.dg/nested-func-12.c:45:1: error: invalid
conversion in gimple call
struct S
struct S
# .MEM_37 = VDEF <.MEM_36>
MEM[(struct S *)_12] = fn (); [static-chain: &FRAME.5] [return slot
optimization]
/aux/hubicka/trunk4/gcc/testsuite/gcc.dg/nested-func-12.c:45:1: error: invalid
conversion in gimple call
struct S
struct S
# .MEM_45 = VDEF <.MEM_44>
MEM[(struct S *)_26] = fn (); [static-chain: &FRAME.5] [return slot
optimization]
during GIMPLE pass: fixup_cfg
/aux/hubicka/trunk4/gcc/testsuite/gcc.dg/nested-func-12.c:45:1: internal
compiler error: verify_gimple failed
0xc9c401 verify_gimple_in_cfg(function*, bool)
../../gcc/tree-cfg.c:5422
0xb7f85f execute_function_todo
../../gcc/passes.c:1977
0xb8045e execute_todo
../../gcc/passes.c:2031
/aux/hubicka/trunk4/build6/gcc/testsuite/g++11/../../xg++
-B/aux/hubicka/trunk4/build6/gcc/testsuite/g++11/../../
/aux/hubicka/trunk4/gcc/testsuite/g++.dg/ext/vector3
3.C -flto -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -nostdinc++
-I/aux/hubicka/trunk4/build6/x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64
-pc-linux-gnu
-I/aux/hubicka/trunk4/build6/x86_64-pc-linux-gnu/libstdc++-v3/include
-I/aux/hubicka/trunk4/libstdc++-v3/libsupc++
-I/aux/hubicka/trunk4/libstdc++-v3/include/backward -I/aux
/hubicka/trunk4/libstdc++-v3/testsuite/util -fmessage-length=0 -std=c++14
-pedantic-errors -Wno-long-long -S -o vector33.s
during IPA pass: fnsummary
/aux/hubicka/trunk4/gcc/testsuite/g++.dg/ext/vector33.C:10:1: internal compiler
error: tree code 'template_parm_index' is not supported in LTO streams
0xe32fd3 lto_write_tree
../../gcc/lto-streamer-out.c:448
0xe32fd3 lto_output_tree_1
../../gcc/lto-streamer-out.c:489
0xe32fd3 DFS::DFS(output_block*, tree_node*, bool, bool, bool)
../../gcc/lto-streamer-out.c:676
0xe33fcf lto_output_tree(output_block*, tree_node*, bool, bool)
../../gcc/lto-streamer-out.c:1628
0xe2c5bc write_global_stream
../../gcc/lto-streamer-out.c:2511
0xe35f7e lto_output_decl_state_streams(output_block*, lto_out_decl_state*)
../../gcc/lto-streamer-out.c:2558
0xe35f7e produce_asm_for_decls()
../../gcc/lto-streamer-out.c:2888
0xe9d0bf write_lto
../../gcc/passes.c:2596
0xea05ee ipa_write_summaries_1
../../gcc/passes.c:2657
0xea05ee ipa_write_summaries()
../../gcc/passes.c:2720
0xb8e132 ipa_passes
../../gcc/cgraphunit.c:2530
0xb8e132 symbol_table::compile()
../../gcc/cgraphunit.c:2618
0xb9016c symbol_table::compile()
../../gcc/cgraphunit.c:2597
0xb9016c symbol_table::finalize_compilation_unit()
../../gcc/cgraphunit.c:2863
Both free_lang_data related. Gimplifier ICE is type simplification so I mark
this as an regression.
>From gcc-bugs-return-627824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 16:09:05 2019
Return-Path: <gcc-bugs-return-627824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79565 invoked by alias); 6 Jan 2019 16:09:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79480 invoked by uid 48); 6 Jan 2019 16:08:58 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88047] [9 Regression] ICE in gfc_find_vtab, at fortran/class.c:2843
Date: Sun, 06 Jan 2019 16:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
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: 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-88047-4-zJpN6B79AJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00633.txt.bz2
Content-length: 376
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88047
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> A related test case, also changed between 20180909 and 20180916 :
Confirmed at r264350, not fixed by the patch in comment 2, but by the patch in
comment 3.
Janus, could please you figure out why class_array_3.f03 is failing with your
patch?
>From gcc-bugs-return-627825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 16:25:14 2019
Return-Path: <gcc-bugs-return-627825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92117 invoked by alias); 6 Jan 2019 16:25: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 91613 invoked by uid 48); 6 Jan 2019 16:24:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88482] ICE when wrongly declaring __cxa_allocate_exception
Date: Sun, 06 Jan 2019 16:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.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-88482-4-TjVOg8BaAi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88482-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88482-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00634.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88482
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 on the trunk, no plans to backport.
>From gcc-bugs-return-627826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:04:17 2019
Return-Path: <gcc-bugs-return-627826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110597 invoked by alias); 6 Jan 2019 17:04:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110471 invoked by uid 48); 6 Jan 2019 17:04:12 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] New: [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Sun, 06 Jan 2019 17:04: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: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00635.txt.bz2
Content-length: 1718
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
Bug ID: 88721
Summary: [9 regression] -Wmaybe-uninitialized warnings in
sparc.c
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org
Target Milestone: ---
Host: sparc-sun-solaris2.11
Target: sparc-sun-solaris2.11
Build: sparc-sun-solaris2.11
Between 20190104 (r267571) and 20190105 (r267602), Solaris/SPARC bootstrap
began
to fail:
/vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c: In function 'rtx_def*
sparc_function_incoming_arg(cumulative_args_t, machine_mode, const_tree,
bool)':
/vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c:7417:39: error: 'regno'
may be used uninitialized in this function [-Werror=maybe-uninitialized]
7417 | return function_arg_union_value (size, mode, slotno, regno);
| ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~
/vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c:7386:15: note: 'regno' was
declared here
7386 | int slotno, regno, padding;
| ^~~~~
/vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c: In function 'void
sparc_function_arg_advance(cumulative_args_t, machine_mode, const_tree, bool)':
/vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c:7603:14: error: 'padding'
may be used uninitialized in this function [-Werror=maybe-uninitialized]
7603 | cum->words += padding;
| ~~~~~~~~~~~^~~~~~~~~~
>From gcc-bugs-return-627828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:05:16 2019
Return-Path: <gcc-bugs-return-627828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113086 invoked by alias); 6 Jan 2019 17:05: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 113031 invoked by uid 48); 6 Jan 2019 17:05:11 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Sun, 06 Jan 2019 17:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88721-4-0BOBXGWgyy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00637.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:05:06 2019
Return-Path: <gcc-bugs-return-627827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112363 invoked by alias); 6 Jan 2019 17:05:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112264 invoked by uid 48); 6 Jan 2019 17:05:01 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Sun, 06 Jan 2019 17:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88721-4-k4gDzHHeAn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00636.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
--- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> ---
Created attachment 45354
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45354&action=edit
Possible patch
This patch allowed the bootstrap to finish.
>From gcc-bugs-return-627829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:16:40 2019
Return-Path: <gcc-bugs-return-627829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27321 invoked by alias); 6 Jan 2019 17:16:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27238 invoked by uid 55); 6 Jan 2019 17:16:34 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86020] [8/9 Regression] Performance regression in Eigen geometry.cpp test starting with r248334
Date: Sun, 06 Jan 2019 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86020-4-MTiQTLjzIb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00638.txt.bz2
Content-length: 515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Sun Jan 6 17:16:00 2019
New Revision: 267612
URL: https://gcc.gnu.org/viewcvs?rev=267612&root=gcc&view=rev
Log:
PR tree-opt/86020
Revert:
2017-05-22 Jan Hubicka <hubicka@ucw.cz>
* ipa-inline.c (edge_badness): Use inlined_time instead of
inline_summaries->get.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-inline.c
>From gcc-bugs-return-627830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:20:31 2019
Return-Path: <gcc-bugs-return-627830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37156 invoked by alias); 6 Jan 2019 17:20:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37069 invoked by uid 48); 6 Jan 2019 17:20:26 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86020] [8/9 Regression] Performance regression in Eigen geometry.cpp test starting with r248334
Date: Sun, 06 Jan 2019 17:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86020-4-qeXgLoTnVu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00639.txt.bz2
Content-length: 397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
--- Comment #6 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I spent good part of day today trying to recollect what was motivation for the
change. All i can think of is that it was mistaken micro-optimization as
mentioned in the mail I sent about reverting the patch.
I plan to backport the change if performance turns out to be OK.
>From gcc-bugs-return-627831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:41:07 2019
Return-Path: <gcc-bugs-return-627831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74287 invoked by alias); 6 Jan 2019 17:41: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 74182 invoked by uid 48); 6 Jan 2019 17:41:01 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88722] New: <no_file>:1: internal compiler error: in register_moduleinfo, at d/modules.cc:40 2
Date: Sun, 06 Jan 2019 17:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00640.txt.bz2
Content-length: 1588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88722
Bug ID: 88722
Summary: <no_file>:1: internal compiler error: in
register_moduleinfo, at d/modules.cc:40 2
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: danglin at gcc dot gnu.org
Target Milestone: ---
Host: hppa2.0w-hp-hpux11.11
Target: hppa2.0w-hp-hpux11.11
Build: hppa2.0w-hp-hpux11.11
spawn /test/gnu/gcc/objdir/gcc/testsuite/gdc/../../gdc
-B/test/gnu/gcc/objdir/gc
c/testsuite/gdc/../../ /test/gnu/gcc/gcc/gcc/testsuite/gdc.dg/gdc254.d
-fno-diag
nostics-show-caret -fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-I/test/gnu/gcc/gcc/gcc/testsuite/../../libphobos/libdruntime
-I/test/gnu/gcc/gc
c/gcc/testsuite/../../libphobos/src
-I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11
/./libstdc++-v3/include
-I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libstdc++
-v3/include/hppa2.0w-hp-hpux11.11
-I/test/gnu/gcc/gcc/gcc/testsuite/../../libstd
c++-v3/libsupc++ -O0 -I /test/gnu/gcc/gcc/gcc/testsuite/gdc.dg -S -o gdc254.s
/test/gnu/gcc/gcc/gcc/testsuite/gdc.dg/gdc254.d:13:1: error: class gdc254.C254
i
nterface function 'void F()' is not implemented
<no_file>:1: internal compiler error: in register_moduleinfo, at
d/modules.cc:40
2
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
>From gcc-bugs-return-627832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:52:48 2019
Return-Path: <gcc-bugs-return-627832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128273 invoked by alias); 6 Jan 2019 17:52: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 128208 invoked by uid 48); 6 Jan 2019 17:52:43 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] New: [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Sun, 06 Jan 2019 17:52: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00641.txt.bz2
Content-length: 2592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
Bug ID: 88723
Summary: [9 regression] PR debug/88635 patch breaks
testsuite_shared.cc compilation
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org, jakub at gcc dot gnu.org
Target Milestone: ---
Host: sparc-sun-solaris2.11
Target: sparc-sun-solaris2.11
Build: sparc-sun-solaris2.11
Between 20190104 (r267571) and 20190105 (r267602), libstdc++ testing got broken
on Solaris/SPARC:
+ERROR: could not compile testsuite_shared.cc
+ERROR: tcl error sourcing
/vol/gcc/src/hg/trunk/local/libstdc++-v3/testsuite/libstdc++-abi/abi.exp.
The log shows
In file included from
/var/gcc/regression/trunk/11.5-gcc/build/sparc-sun-solaris2.11/libstdc++-v3/include/sparc-sun-solaris2.11/bits/gthr.h:148,
from
/var/gcc/regression/trunk/11.5-gcc/build/sparc-sun-solaris2.11/libstdc++-v3/include/ext/atomicity.h:35,
from
/var/gcc/regression/trunk/11.5-gcc/build/sparc-sun-solaris2.11/libstdc++-v3/include/bits/basic_string.h:39,
from
/var/gcc/regression/trunk/11.5-gcc/build/sparc-sun-solaris2.11/libstdc++-v3/include/string:55,
from
/vol/gcc/src/hg/trunk/local/libstdc++-v3/testsuite/util/testsuite_shared.cc:18:
/var/gcc/regression/trunk/11.5-gcc/build/sparc-sun-solaris2.11/libstdc++-v3/include/sparc-sun-solaris2.11/bits/gthr-default.h:
In function 'int __gthread_active_p()':
/var/gcc/regression/trunk/11.5-gcc/build/sparc-sun-solaris2.11/libstdc++-v3/include/sparc-sun-solaris2.11/bits/gthr-default.h:181:
note: non-delegitimized UNSPEC UNSPEC_MOVE_GOTDATA (14) found in variable
location
and many more, and all compiler output lets target_compile think there's an
error, although the compilation succeeds otherwise.
It turns out that reverting just the dwarf2out.c partof
PR debug/88635
* dwarf2out.c (const_ok_for_output_1): Reject MINUS that contains
SYMBOL_REF, CODE_LABEL or UNSPEC in subexpressions of second argument.
Reject PLUS that contains SYMBOL_REF, CODE_LABEL or UNSPEC in
subexpressions of both operands.
(mem_loc_descriptor): Handle UNSPEC if target hook acks it and all the
subrtxes are CONSTANT_P.
Allows the compilation to succeed without error or messages.
>From gcc-bugs-return-627833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:53:22 2019
Return-Path: <gcc-bugs-return-627833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129173 invoked by alias); 6 Jan 2019 17:53: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 129106 invoked by uid 48); 6 Jan 2019 17:53:18 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Sun, 06 Jan 2019 17:53: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88723-4-rA25c6uun0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00642.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 17:53:57 2019
Return-Path: <gcc-bugs-return-627834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130559 invoked by alias); 6 Jan 2019 17:53:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130261 invoked by uid 48); 6 Jan 2019 17:53:35 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/88724] New: FAIL: gdc.dg/compilable.d -O0 (test for excess errors)
Date: Sun, 06 Jan 2019 17:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88724-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00643.txt.bz2
Content-length: 62576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88724
Bug ID: 88724
Summary: FAIL: gdc.dg/compilable.d -O0 (test for excess
errors)
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: danglin at gcc dot gnu.org
Target Milestone: ---
Host: hppa2.0w-hp-hpux11.11
Target: hppa2.0w-hp-hpux11.11
Build: hppa2.0w-hp-hpux11.11
spawn /test/gnu/gcc/objdir/gcc/testsuite/gdc/../../gdc
-B/test/gnu/gcc/objdir/gcc/testsuite/gdc/../../
/test/gnu/gcc/gcc/gcc/testsuite/gdc.dg/compilable.d -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-I/test/gnu/gcc/gcc/gcc/testsuite/../../libphobos/libdruntime
-I/test/gnu/gcc/gcc/gcc/testsuite/../../libphobos/src
-I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libstdc++-v3/include
-I/test/gnu/gcc/objdir/hppa2.0w-hp-hpux11.11/./libstdc++-v3/include/hppa2.0w-hp-hpux11.11
-I/test/gnu/gcc/gcc/gcc/testsuite/../../libstdc++-v3/libsupc++ -O0 -I
/test/gnu/gcc/gcc/gcc/testsuite/gdc.dg -I
/test/gnu/gcc/gcc/gcc/testsuite/gdc.dg/imports -Wno-psabi
/test/gnu/gcc/gcc/gcc/testsuite/gdc.dg/imports/gdc27.d
/test/gnu/gcc/gcc/gcc/testsuite/gdc.dg/imports/gdc231.d -S -o compilable.s
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:201:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:203:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:205:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:207:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:151:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:151:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:153:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:153:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:155:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:155:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:157:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:159:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:161:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:161:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:163:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:163:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:165:17: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:89:14: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:92:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:92:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:94:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:94:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:95:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:95:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:97:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:97:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:99:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:99:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:100:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:100:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:102:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:104:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:106:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:108:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:126:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:126:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:128:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:128:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:86:7: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:135:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:137:12: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:137:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:141:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:141:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:141:10: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:143:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:143:10: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:151:12: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:153:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:155:12: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:155:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:162:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:171:16: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:176:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:176:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:178:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:178:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:180:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:180:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:182:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:182:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:184:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:184:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:186:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:186:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:188:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:188:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:191:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:191:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:191:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:193:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:193:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:193:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:195:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:195:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:195:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:197:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:197:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:197:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:199:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:199:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:201:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:201:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:203:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:203:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:205:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:205:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:207:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:207:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:207:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:209:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:209:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:211:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:211:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:211:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:213:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:213:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:213:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:215:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:215:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:217:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:217:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:217:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:221:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:224:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:224:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:224:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:226:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:226:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:228:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:228:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:228:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:230:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:230:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:230:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:232:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:232:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:232:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:235:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:235:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:235:8: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:263:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:265:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:267:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:269:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:168:15: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:168:27: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:170:15: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:170:27: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:172:15: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:172:27: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:174:15: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:174:27: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:176:15: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:176:27: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:178:15: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:178:27: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:180:15: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:180:27: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:182:15: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:182:27: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:185:15: error:
undefined identifier 'uint8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:185:28: error:
undefined identifier 'uint8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:187:15: error:
undefined identifier 'uint16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:187:28: error:
undefined identifier 'uint16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:189:15: error:
undefined identifier 'uint32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:189:28: error:
undefined identifier 'uint32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:191:15: error:
undefined identifier 'uint64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:191:28: error:
undefined identifier 'uint64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:194:22: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:194:41: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:196:22: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:196:41: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:198:22: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:198:41: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:200:22: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:200:41: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:202:22: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:202:41: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:204:22: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:204:41: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:206:22: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:206:41: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:208:22: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:208:41: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:211:22: error:
undefined identifier 'uint_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:211:41: error:
undefined identifier 'uint_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:213:22: error:
undefined identifier 'uint_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:213:41: error:
undefined identifier 'uint_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:215:22: error:
undefined identifier 'uint_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:215:41: error:
undefined identifier 'uint_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:217:22: error:
undefined identifier 'uint_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:217:41: error:
undefined identifier 'uint_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:220:20: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:220:38: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:222:20: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:222:38: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:224:20: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:224:38: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:226:20: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:226:38: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:228:20: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:228:38: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:230:20: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:230:38: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:232:20: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:232:38: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:234:20: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:234:38: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:237:20: error:
undefined identifier 'uint_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:237:38: error:
undefined identifier 'uint_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:239:20: error:
undefined identifier 'uint_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:239:38: error:
undefined identifier 'uint_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:241:20: error:
undefined identifier 'uint_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:241:38: error:
undefined identifier 'uint_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:243:20: error:
undefined identifier 'uint_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:243:38: error:
undefined identifier 'uint_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:246:16: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:246:30: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:248:16: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:248:30: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:251:16: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:251:30: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:253:16: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:253:30: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:256:16: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:256:30: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:258:16: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:258:30: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:261:16: error:
undefined identifier 'uintmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:261:30: error:
undefined identifier 'uintmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:277:14: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:277:26: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:279:14: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:279:26: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:31:12: error:
module core.stdc.stdint import 'intptr_t' not found
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1149:16: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1154:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1160:11: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1164:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1166:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1166:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1169:6: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1171:6: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1240:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1242:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1248:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1250:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1269:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1271:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1275:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1277:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1297:14: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1300:8: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1302:8: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1308:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1308:9: error:
undefined identifier 'fpos_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1310:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1310:9: error:
undefined identifier 'fpos_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1313:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1315:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:1926:16: error: undefined
identifier 'ClockType'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:1940:16: error: undefined
identifier 'ClockType'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:2009:21: error: undefined
identifier 'ClockType', did you mean variable 'clockType'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:2413:24: error: undefined
identifier 'ClockType'
/test/gnu/gcc/gcc-9/libphobos/src/std/typecons.d:71:8: error: module
core.stdc.stdint import 'uintptr_t' not found
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/timezone.d:1854:12: error:
module std.file import 'DirEntry' not found
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:358:16: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:366:13: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1126:42: error: undefined
identifier '_IOFBF'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1142:41: error: undefined
identifier '_IOFBF'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1935:29: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1946:11: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:2721:15: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:2724:27: error: undefined
identifier '_iobuf'
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/timezone.d:2017:85: error:
undefined identifier 'defaultTZDatabaseDir'
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/timezone.d:2365:85: error:
undefined identifier 'defaultTZDatabaseDir'
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:64:29: error:
undefined identifier 'ClockType', did you mean variable 'clockType'?
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:119:39: error:
undefined identifier 'ClockType', did you mean variable 'clockType'?
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:348:12: error: module
core.stdc.time import 'tm' not found
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:2338:13: error:
undefined identifier 'timeval'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:736:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:736:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:812:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:1533:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3427:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3427:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3575:6: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3605:6: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3702:14: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3703:5: error: undefined
identifier 'DirHandle'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3703:5: error: undefined
identifier 'DirHandle'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3704:5: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3704:5: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3706:10: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3710:14: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3872:24: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3924:24: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/path.d:337:17: error: undefined
identifier 'osDefaultCaseSensitivity'
/test/gnu/gcc/gcc-9/libphobos/src/std/path.d:2649:53: error: undefined
identifier 'getcwd'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/errno.d:1583:5: error:
static assert "Unsupported platform"
compiler exited with status 1
output is:
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:201:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:203:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:205:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdlib.d:207:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:151:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:151:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:153:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:153:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:155:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:155:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:157:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:159:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:161:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:161:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:163:9: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:163:9: error:
undefined identifier 'time_t', did you mean function 'time'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/time.d:165:17: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:89:14: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:92:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:92:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:94:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:94:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:95:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:95:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:97:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:97:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:99:5: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:99:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:100:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:100:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:102:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:104:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:106:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:108:5: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:126:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:126:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:128:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:128:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:86:7: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:135:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:137:12: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:137:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:141:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:141:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:141:10: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:143:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:143:10: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:151:12: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:153:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:155:12: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:155:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:162:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:171:16: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:176:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:176:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:178:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:178:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:180:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:180:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:182:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:182:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:184:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:184:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:186:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:186:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:188:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:188:9: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:191:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:191:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:191:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:193:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:193:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:193:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:195:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:195:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:195:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:197:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:197:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:197:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:199:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:199:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:201:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:201:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:203:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:203:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:205:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:205:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:207:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:207:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:207:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:209:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:209:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:211:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:211:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:211:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:213:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:213:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:213:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:215:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:215:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:217:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:217:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:217:22: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:219:10: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:221:13: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:224:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:224:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:224:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:226:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:226:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:228:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:228:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:228:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:230:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:230:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:230:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:232:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:232:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:232:15: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:235:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:235:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:235:8: error:
undefined identifier 'tm'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:263:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:265:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:267:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/wchar_.d:269:8: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:168:15: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:168:27: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:170:15: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:170:27: error:
undefined identifier 'int8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:172:15: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:172:27: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:174:15: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:174:27: error:
undefined identifier 'int16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:176:15: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:176:27: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:178:15: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:178:27: error:
undefined identifier 'int32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:180:15: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:180:27: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:182:15: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:182:27: error:
undefined identifier 'int64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:185:15: error:
undefined identifier 'uint8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:185:28: error:
undefined identifier 'uint8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:187:15: error:
undefined identifier 'uint16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:187:28: error:
undefined identifier 'uint16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:189:15: error:
undefined identifier 'uint32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:189:28: error:
undefined identifier 'uint32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:191:15: error:
undefined identifier 'uint64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:191:28: error:
undefined identifier 'uint64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:194:22: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:194:41: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:196:22: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:196:41: error:
undefined identifier 'int_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:198:22: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:198:41: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:200:22: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:200:41: error:
undefined identifier 'int_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:202:22: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:202:41: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:204:22: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:204:41: error:
undefined identifier 'int_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:206:22: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:206:41: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:208:22: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:208:41: error:
undefined identifier 'int_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:211:22: error:
undefined identifier 'uint_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:211:41: error:
undefined identifier 'uint_least8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:213:22: error:
undefined identifier 'uint_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:213:41: error:
undefined identifier 'uint_least16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:215:22: error:
undefined identifier 'uint_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:215:41: error:
undefined identifier 'uint_least32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:217:22: error:
undefined identifier 'uint_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:217:41: error:
undefined identifier 'uint_least64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:220:20: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:220:38: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:222:20: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:222:38: error:
undefined identifier 'int_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:224:20: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:224:38: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:226:20: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:226:38: error:
undefined identifier 'int_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:228:20: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:228:38: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:230:20: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:230:38: error:
undefined identifier 'int_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:232:20: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:232:38: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:234:20: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:234:38: error:
undefined identifier 'int_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:237:20: error:
undefined identifier 'uint_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:237:38: error:
undefined identifier 'uint_fast8_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:239:20: error:
undefined identifier 'uint_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:239:38: error:
undefined identifier 'uint_fast16_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:241:20: error:
undefined identifier 'uint_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:241:38: error:
undefined identifier 'uint_fast32_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:243:20: error:
undefined identifier 'uint_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:243:38: error:
undefined identifier 'uint_fast64_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:246:16: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:246:30: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:248:16: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:248:30: error:
undefined identifier 'intptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:251:16: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:251:30: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:253:16: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:253:30: error:
undefined identifier 'uintptr_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:256:16: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:256:30: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:258:16: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:258:30: error:
undefined identifier 'intmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:261:16: error:
undefined identifier 'uintmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:261:30: error:
undefined identifier 'uintmax_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:277:14: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:277:26: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:279:14: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdint.d:279:26: error:
undefined identifier 'wchar_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:31:12: error:
module core.stdc.stdint import 'intptr_t' not found
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1149:16: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1154:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1160:11: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1164:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1166:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1166:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1169:6: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1171:6: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1240:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1242:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1248:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1250:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1269:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1271:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1275:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1277:7: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1297:14: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1300:8: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1302:8: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1308:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1308:9: error:
undefined identifier 'fpos_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1310:9: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1310:9: error:
undefined identifier 'fpos_t'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1313:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/stdio.d:1315:12: error:
undefined identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:1926:16: error: undefined
identifier 'ClockType'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:1940:16: error: undefined
identifier 'ClockType'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:2009:21: error: undefined
identifier 'ClockType', did you mean variable 'clockType'?
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/time.d:2413:24: error: undefined
identifier 'ClockType'
/test/gnu/gcc/gcc-9/libphobos/src/std/typecons.d:71:8: error: module
core.stdc.stdint import 'uintptr_t' not found
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/timezone.d:1854:12: error:
module std.file import 'DirEntry' not found
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:358:16: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:366:13: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1126:42: error: undefined
identifier '_IOFBF'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1142:41: error: undefined
identifier '_IOFBF'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1935:29: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:1946:11: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:2721:15: error: undefined
identifier 'FILE'
/test/gnu/gcc/gcc-9/libphobos/src/std/stdio.d:2724:27: error: undefined
identifier '_iobuf'
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/timezone.d:2017:85: error:
undefined identifier 'defaultTZDatabaseDir'
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/timezone.d:2365:85: error:
undefined identifier 'defaultTZDatabaseDir'
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:64:29: error:
undefined identifier 'ClockType', did you mean variable 'clockType'?
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:119:39: error:
undefined identifier 'ClockType', did you mean variable 'clockType'?
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:348:12: error: module
core.stdc.time import 'tm' not found
/test/gnu/gcc/gcc-9/libphobos/src/std/datetime/systime.d:2338:13: error:
undefined identifier 'timeval'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:736:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:736:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:812:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:1533:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3427:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3427:14: error: undefined
identifier 'FSChar'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3575:6: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3605:6: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3702:14: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3703:5: error: undefined
identifier 'DirHandle'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3703:5: error: undefined
identifier 'DirHandle'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3704:5: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3704:5: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3706:10: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3710:14: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3872:24: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/file.d:3924:24: error: undefined
identifier 'DirEntry'
/test/gnu/gcc/gcc-9/libphobos/src/std/path.d:337:17: error: undefined
identifier 'osDefaultCaseSensitivity'
/test/gnu/gcc/gcc-9/libphobos/src/std/path.d:2649:53: error: undefined
identifier 'getcwd'
/test/gnu/gcc/gcc-9/libphobos/libdruntime/core/stdc/errno.d:1583:5: error:
static assert "Unsupported platform"
FAIL: gdc.dg/compilable.d -O0 (test for excess errors)
>From gcc-bugs-return-627835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:02:21 2019
Return-Path: <gcc-bugs-return-627835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13272 invoked by alias); 6 Jan 2019 18:02: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 13203 invoked by uid 48); 6 Jan 2019 18:02:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Sun, 06 Jan 2019 18:02: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:
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-I8v02mFbcQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00644.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't have access to Solaris, can you attach preprocessed testsuite_shared.cc
+ the g++ options used to compile it?
The note generally shouldn't break stuff, it isn't an error, just a debugging
hint (goes away for --enable-checking=release builds) that maybe the sparc
delegitimize hook needs more work.
>From gcc-bugs-return-627836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:07:00 2019
Return-Path: <gcc-bugs-return-627836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17281 invoked by alias); 6 Jan 2019 18:07:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17215 invoked by uid 48); 6 Jan 2019 18:06:56 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Sun, 06 Jan 2019 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88723-4-8FiIJvJZiN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00645.txt.bz2
Content-length: 608
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #2 from Rainer Orth <ro at gcc dot gnu.org> ---
Created attachment 45355
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45355&action=edit
preprocessed input
Sure. The cc1plus invocation is
cc1plus -fpreprocessed testsuite_shared.ii -quiet -dumpbase testsuite_shared.cc
-mcpu=v9 -auxbase testsuite_shared -g -O2 -w -std=gnu++98 -version
-fdiagnostics-color=never -fchecking=1 -fmessage-length=0 -fno-show-column
-ffunction-sections -fdata-sections -fno-inline -fPIC
-fno-diagnostics-show-caret -o testsuite_shared.s
>From gcc-bugs-return-627837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:17:49 2019
Return-Path: <gcc-bugs-return-627837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23945 invoked by alias); 6 Jan 2019 18:17: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 23904 invoked by uid 48); 6 Jan 2019 18:17:44 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 18:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-Q6UZnOphDc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00646.txt.bz2
Content-length: 4327
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #6 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45356
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45356&action=edit
Code to demonstrate that transposing makes things slower.
Thomas Koenig, I am well aware that Fortran is column major. That is precisely
why I chose the memory layout I did.
Benchmark of the "optimal" corrected code:
@benchmark gforttest($X32t, $BPP32t, $N)
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 20.647 μs (0.00% GC)
median time: 20.860 μs (0.00% GC)
mean time: 21.751 μs (0.00% GC)
maximum time: 47.760 μs (0.00% GC)
--------------
samples: 10000
evals/sample: 1
Here is a benchmark (compiling with Flang) of my code, exactly as written
(suboptimal) in the attachments:
@benchmark flangtest($X32, $BPP32, $N)
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 658.329 ns (0.00% GC)
median time: 668.012 ns (0.00% GC)
mean time: 692.384 ns (0.00% GC)
maximum time: 1.192 μs (0.00% GC)
--------------
samples: 10000
evals/sample: 161
That is 20 microseconds, vs 670 nanoseconds.
N was 1024, and the exact same data used in both cases (but pretransposed, so I
do not benchmark tranposing).
Benchmarking was done by compiling shared libraries, and using `ccall` and
BenchmarkTools from Julia. As indicated by the reports, the benchmark was run
10,000 times for gfortran, and 1.61 million times for Flang, to get accurate
timings.
I compiled with (march=native is equivalent to march=skylake-avx512):
gfortran -Ofast -march=native -mprefer-vector-width=512
-fno-semantic-interposition -shared -fPIC vectorization_test_transposed.f90 -o
libgfortvectorization_test.so
flang -Ofast -march=native -mprefer-vector-width=512 -shared -fPIC
vectorization_test.f90 -o libflangvectorization_test.so
Flang was built with LLVM 7.0.1.
The "suboptimal" code was close to 32 times faster than the "optimal" code.
I was expecting it to be closer to 16 times faster, given the vector width.
To go into more detail:
"
Fortran lays out the memory for that array as
BPP(1,1), BPP(2,1), BPP(3,1), BPP(4,1), ..., BPP(1,2)
so you are accessing your memory with a stride of n in the
expressions BPP(i,1:3) and BPP(i,5:10). This is very inefficient
anyway, vectorization would not really help in this case.
"
Yes, each call to fpdbacksolve is accessing memory across strides.
But fpdbacksolve itself cannot be vectorized well at all.
What does work, however, is vectorizing across loop iterations.
For example, imagine calling fpdbacksolve on this:
BPP(1:16,1), BPP(1:16,2), BPP(1:16,3), BPP(1:16,5), ..., BPP(1:16,10)
and then performing every single scalar operation defined in fpdbacksolve on an
entire SIMD vector of floats (that is, on 16 floats) at a time.
That would of course require inlining fpdbacksolve (which was achieved with
-fno-semantic-interposition, as the assembly shows), and recompiling it.
Perhaps another way you can imagine it is that fpdbacksolve takes in 9 numbers
(BPP(:,4) was unused), and returns 3 numbers.
Because operations within it aren't vectorizable, we want to vectorize it
ACROSS loop iterations, not within them.
So to facilitate that, we have 9 vectors of contiguous inputs, and 3 vectors of
contiguous outputs. Now, all inputs1 are stored contiguously, as are all
inputs2, etc..., allowing the inputs to efficiently be loaded into SIMD
registers, and each loop iteration to calculate [SIMD vector width] of the
outputs at a time.
Of course, it is inconvenient to handle a dozen vectors. So if they all have
the same length, we can just concatenate them together.
I'll attach the assembly of both code examples as well.
The assembly makes it clear that the "suboptimal" way was vectorized, and the
"optimal" way was not.
The benchmarks make it resoundingly clear that the vectorized ("suboptimal")
version was dramatically faster.
As is, this is a missed optimization, and gfortran is severely falling behind
in performance versus LLVM-based Flang in the highest performance version of
the code.
>From gcc-bugs-return-627838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:24:40 2019
Return-Path: <gcc-bugs-return-627838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5435 invoked by alias); 6 Jan 2019 18:24: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 126978 invoked by uid 48); 6 Jan 2019 18:24:03 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 18:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-BsCkeUBFq4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00647.txt.bz2
Content-length: 3888
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #7 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45357
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45357&action=edit
Assembly generated by Flang compiler on the original version of the code.
This is the main loop body in the Flang compiled version of the original code
(starts line 132):
.LBB1_8: # %vector.body
# =>This Inner Loop Header: Depth=1
leaq (%rsi,%rbx,4), %r12
vmovups (%rcx,%r12), %zmm2
addq %rcx, %r12
leaq (%r12,%rcx), %rbp
vmovups (%r11,%rbp), %zmm3
addq %r11, %rbp
leaq (%rcx,%rbp), %r13
leaq (%rcx,%r13), %r8
leaq (%r8,%rcx), %r10
leaq (%r10,%rcx), %r14
vmovups (%rcx,%r14), %zmm4
vrsqrt14ps %zmm4, %zmm5
vmulps %zmm5, %zmm4, %zmm4
vfmadd213ps %zmm0, %zmm5, %zmm4 # zmm4 = (zmm5 * zmm4) + zmm0
vmulps %zmm1, %zmm5, %zmm5
vmulps %zmm4, %zmm5, %zmm4
.Ltmp1:
.loc 1 31 1 is_stmt 1 # vectorization_test.f90:31:1
vmulps (%rcx,%r8), %zmm4, %zmm5
.loc 1 32 1 # vectorization_test.f90:32:1
vmulps (%rcx,%r10), %zmm4, %zmm6
vmovups (%rcx,%r13), %zmm7
.loc 1 33 1 # vectorization_test.f90:33:1
vfnmadd231ps %zmm6, %zmm6, %zmm7 # zmm7 = -(zmm6 * zmm6) + zmm7
vrsqrt14ps %zmm7, %zmm8
vmulps %zmm8, %zmm7, %zmm7
vfmadd213ps %zmm0, %zmm8, %zmm7 # zmm7 = (zmm8 * zmm7) + zmm0
vmulps %zmm1, %zmm8, %zmm8
vmulps %zmm7, %zmm8, %zmm7
vmovups (%rcx,%rbp), %zmm8
.loc 1 35 1 # vectorization_test.f90:35:1
vfnmadd231ps %zmm5, %zmm6, %zmm8 # zmm8 = -(zmm6 * zmm5) + zmm8
vmulps %zmm8, %zmm7, %zmm8
vmulps %zmm5, %zmm5, %zmm9
vfmadd231ps %zmm8, %zmm8, %zmm9 # zmm9 = (zmm8 * zmm8) + zmm9
vsubps %zmm9, %zmm3, %zmm3
vrsqrt14ps %zmm3, %zmm9
vmulps %zmm9, %zmm3, %zmm3
vfmadd213ps %zmm0, %zmm9, %zmm3 # zmm3 = (zmm9 * zmm3) + zmm0
vmulps %zmm1, %zmm9, %zmm9
vmulps %zmm3, %zmm9, %zmm3
.loc 1 39 1 # vectorization_test.f90:39:1
vmulps %zmm8, %zmm7, %zmm8
.loc 1 40 1 # vectorization_test.f90:40:1
vmulps (%rcx,%r12), %zmm4, %zmm4
.loc 1 39 1 # vectorization_test.f90:39:1
vmulps %zmm3, %zmm8, %zmm8
.loc 1 41 1 # vectorization_test.f90:41:1
vmulps %zmm8, %zmm2, %zmm9
vfmsub231ps (%rsi,%rbx,4), %zmm3, %zmm9 # zmm9 = (zmm3 * mem) -
zmm9
vmulps %zmm5, %zmm3, %zmm3
vfmsub231ps %zmm8, %zmm6, %zmm3 # zmm3 = (zmm6 * zmm8) - zmm3
vfmadd213ps %zmm9, %zmm4, %zmm3 # zmm3 = (zmm4 * zmm3) + zmm9
.loc 1 42 1 # vectorization_test.f90:42:1
vmulps %zmm4, %zmm6, %zmm5
vmulps %zmm5, %zmm7, %zmm5
vfmsub231ps %zmm7, %zmm2, %zmm5 # zmm5 = (zmm2 * zmm7) - zmm5
.Ltmp2:
.loc 1 15 1 # vectorization_test.f90:15:1
vmovups %zmm3, (%rdi,%rbx,4)
movq -16(%rsp), %rbp # 8-byte Reload
vmovups %zmm5, (%rbp,%rbx,4)
vmovups %zmm4, (%rax,%rbx,4)
addq $16, %rbx
cmpq %rbx, %rdx
jne .LBB1_8
zmm registers are 64 byte registers. It vmovups from memory into registers,
performs a series of arithmetics and inverse square roots on them, and then
vmovups three of these 64 byte registers back into memory.
That is the most efficient memory access pattern (as demonstrated empirically
via benchmarks).
>From gcc-bugs-return-627839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:25:10 2019
Return-Path: <gcc-bugs-return-627839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18969 invoked by alias); 6 Jan 2019 18:25:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7062 invoked by uid 48); 6 Jan 2019 18:24:37 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88725] New: fails to deduce template specialization in friend declaration
Date: Sun, 06 Jan 2019 18: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp 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-88725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00648.txt.bz2
Content-length: 944
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88725
Bug ID: 88725
Summary: fails to deduce template specialization in friend
declaration
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: haining.cpp at gmail dot com
Target Milestone: ---
gcc fails to deduce that the friend declaration refers to ::func<int> in the
below
```
template <typename T>
void func(T);
class Cls {
friend void ::func(int);
};
```
Rejecting with
```
error: 'void func(int)' should have been declared inside '::'
friend void ::func(int);
^
```
I believe this should be allowed by [temp.friend]/1.3:
http://eel.is/c++draft/temp.friend#1.3
see discussion here: https://stackoverflow.com/q/54055575/1013719
>From gcc-bugs-return-627840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:33:47 2019
Return-Path: <gcc-bugs-return-627840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44486 invoked by alias); 6 Jan 2019 18:33:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44461 invoked by uid 48); 6 Jan 2019 18:33:42 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] New: GCC thinks that translation unit does not contain a definition of inline function.
Date: Sun, 06 Jan 2019 18:33: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: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00649.txt.bz2
Content-length: 908
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
Bug ID: 88726
Summary: GCC thinks that translation unit does not contain a
definition of inline function.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (test.c):
int main()
{
extern inline void f();
}
void f()
{
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed beaviour:
The following error message was outputed:
error: inline function 'f' declared but never defined
Expected behaviour:
No error message outputed.
Note:
Clang accepts the program without any error message outputed.
>From gcc-bugs-return-627841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:35:47 2019
Return-Path: <gcc-bugs-return-627841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46199 invoked by alias); 6 Jan 2019 18:35:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46089 invoked by uid 48); 6 Jan 2019 18:35:36 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 18:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-x80gTz0vb8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00650.txt.bz2
Content-length: 3142
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #8 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45358
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45358&action=edit
gfortran compiled assembly for the tranposed version of the original code.
Here is the assembly for the loop body of the transposed version of the code,
compiled by gfortran:
.L8:
vmovss 36(%rsi), %xmm0
addq $40, %rsi
vrsqrtss %xmm0, %xmm2, %xmm2
addq $12, %rdi
vmulss %xmm0, %xmm2, %xmm0
vmulss %xmm2, %xmm0, %xmm0
vmulss %xmm7, %xmm2, %xmm2
vaddss %xmm8, %xmm0, %xmm0
vmulss %xmm2, %xmm0, %xmm0
vmulss -8(%rsi), %xmm0, %xmm5
vmulss -12(%rsi), %xmm0, %xmm4
vmulss -32(%rsi), %xmm0, %xmm0
vmovaps %xmm5, %xmm3
vfnmadd213ss -16(%rsi), %xmm5, %xmm3
vmovaps %xmm4, %xmm2
vfnmadd213ss -20(%rsi), %xmm5, %xmm2
vmovss %xmm0, -4(%rdi)
vrsqrtss %xmm3, %xmm1, %xmm1
vmulss %xmm3, %xmm1, %xmm3
vmulss %xmm1, %xmm3, %xmm3
vmulss %xmm7, %xmm1, %xmm1
vaddss %xmm8, %xmm3, %xmm3
vmulss %xmm1, %xmm3, %xmm3
vmulss %xmm3, %xmm2, %xmm6
vmovaps %xmm4, %xmm2
vfnmadd213ss -24(%rsi), %xmm4, %xmm2
vfnmadd231ss %xmm6, %xmm6, %xmm2
vrsqrtss %xmm2, %xmm10, %xmm10
vmulss %xmm2, %xmm10, %xmm1
vmulss %xmm10, %xmm1, %xmm1
vmulss %xmm7, %xmm10, %xmm10
vaddss %xmm8, %xmm1, %xmm1
vmulss %xmm10, %xmm1, %xmm1
vmulss %xmm1, %xmm3, %xmm2
vmulss %xmm6, %xmm2, %xmm2
vmovss -36(%rsi), %xmm6
vxorps %xmm9, %xmm2, %xmm2
vmulss %xmm6, %xmm2, %xmm10
vmulss %xmm2, %xmm5, %xmm2
vfmadd231ss -40(%rsi), %xmm1, %xmm10
vfmadd132ss %xmm4, %xmm2, %xmm1
vfnmadd132ss %xmm0, %xmm10, %xmm1
vmulss %xmm0, %xmm5, %xmm0
vmovss %xmm1, -12(%rdi)
vsubss %xmm0, %xmm6, %xmm0
vmulss %xmm3, %xmm0, %xmm3
vmovss %xmm3, -8(%rdi)
cmpq %rsi, %rax
jne .L8
While Flang had a second loop of scalar code (to catch the N mod [SIMD vector
width] remainder of the vectorized loop), there are no secondary loops in the
gfortran code, meaning these must all be scalar operations (I have a hard time
telling apart SSE from scalar code...).
It looks similar in the operations it performs to Flang's vectorized loop,
except that it is only performing operations on a single number at a time.
Because to get efficient vectorization, we need corresponding elements to be
contiguous (ie, all the input1s, all the input2s).
We do not get any benefit from having all the different elements with the same
index (the first input1 next to the first input2, next to the first input3...)
being contiguous.
The memory layout I used is performance-optimal, but is something that gfortran
unfortunately often cannot handle automatically (without manual unrolling).
This is why I filed a report on bugzilla.
>From gcc-bugs-return-627842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 18:39:16 2019
Return-Path: <gcc-bugs-return-627842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49891 invoked by alias); 6 Jan 2019 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 49852 invoked by uid 48); 6 Jan 2019 18:39:11 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88713-4-B1WpogEYD6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00651.txt.bz2
Content-length: 392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Hm.
It would help if your benchmark was complete, so I could run it.
However, what happens if you put int
real, dimension(:) :: Uix
real, dimension(:), intent(in) :: x
real, dimension(:), intent(in) :: S
?
gfortran should not pack then.
>From gcc-bugs-return-627843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 19:20:13 2019
Return-Path: <gcc-bugs-return-627843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57272 invoked by alias); 6 Jan 2019 19:20: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 57223 invoked by uid 48); 6 Jan 2019 19:20:08 -0000
From: "colomar.6.4.3 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/80354] Poor support to silence -Wformat-truncation=1
Date: Sun, 06 Jan 2019 19:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.0.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: colomar.6.4.3 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80354-4-3N0eqs6SuQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80354-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80354-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00652.txt.bz2
Content-length: 2145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80354
Alejandro Colomar <colomar.6.4.3 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |colomar.6.4.3 at gmail dot com
--- Comment #10 from Alejandro Colomar <colomar.6.4.3 at gmail dot com> ---
In some cases, that warning saved me from writing dangerous code (using file
paths), and it's been very useful. But casting to void means one and only one
thing: _I DO know what I'm doing and I do NOT care, so STFU!_
And if the casting to void is dangerous (ie. casting to void the result of
storing a path), that's my fault.
I currently have a program where I want, for some reason, to truncate the
output to an 80-char line:
#include <stdio.h>
#define LINE_SIZE (80)
int main(int argc, char *argv[])
{
char truncated[LINE_SIZE];
(void)snprintf(truncated, LINE_SIZE, "I DO want to truncate this line "
"to a 80 char line, and discard any remaining text so "
"that it is not displayed or stored anywhere because I
"
"don't care about it. "
" Usually one would check for the return value of "
"snprintf, but in this precise situation, I do not "
"care about it, so the explicit cast to (void) should "
"silence the warning, just like it does in other "
"warnings such as -Wunused-variable.");
printf("%s\n", truncated);
return 0;
}
But in the same project I have paths and that kind of uses of snprintf where I
still want to have the warnings enabled (and even more, -Werror so that they
never compile):
if (snprintf(file_name, FILENAME_MAX, "%s/%s", file_path, saved_name))
{
goto err_path;
}
Many other warnings are supressed with (void), why is this one so special?
Anyways, I'm reporting a new bug, because this one is "RESOLVED INVALID".
>From gcc-bugs-return-627844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 19:38:51 2019
Return-Path: <gcc-bugs-return-627844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85961 invoked by alias); 6 Jan 2019 19:38: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 85902 invoked by uid 48); 6 Jan 2019 19:38:43 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88713] _gfortran_internal_pack@PLT prevents vectorization
Date: Sun, 06 Jan 2019 19:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88713-4-7V8zsnpDS0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00653.txt.bz2
Content-length: 6603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #10 from Chris Elrod <elrodc at gmail dot com> ---
(In reply to Thomas Koenig from comment #9)
> Hm.
>
> It would help if your benchmark was complete, so I could run it.
>
I don't suppose you happen to have and be familiar with Julia? If you (or
someone else here is), I'll attach the code to generate the fake data (the most
important point is that columns 5:10 of BPP are the upper triangle of a 3x3
symmetric positive definite matrix).
I have also already written a manually unrolled version that gfortran likes..
But I could write Fortran code to create an executable and run benchmarks.
What are best practices? system_clock?
(In reply to Thomas Koenig from comment #9)
>
> However, what happens if you put int
>
> real, dimension(:) :: Uix
> real, dimension(:), intent(in) :: x
> real, dimension(:), intent(in) :: S
>
> ?
>
> gfortran should not pack then.
You're right! I wasn't able to follow this exactly, because it didn't want me
to defer shape on Uix. Probably because it needs to compile a version of
fpdbacksolve that can be called from the shared library?
Interestingly, with that change, Flang failed to vectorize the code, but
gfortran did. Compilers are finicky.
Flang, original:
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 655.827 ns (0.00% GC)
median time: 665.698 ns (0.00% GC)
mean time: 689.967 ns (0.00% GC)
maximum time: 1.061 μs (0.00% GC)
--------------
samples: 10000
evals/sample: 162
Flang, not specifying shape: # assembly shows it is using xmm
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 8.086 μs (0.00% GC)
median time: 8.315 μs (0.00% GC)
mean time: 8.591 μs (0.00% GC)
maximum time: 20.299 μs (0.00% GC)
--------------
samples: 10000
evals/sample: 3
gfortran, transposed version (not vectorizable):
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 20.643 μs (0.00% GC)
median time: 20.901 μs (0.00% GC)
mean time: 21.441 μs (0.00% GC)
maximum time: 54.103 μs (0.00% GC)
--------------
samples: 10000
evals/sample: 1
gfortran, not specifying shape:
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 1.290 μs (0.00% GC)
median time: 1.316 μs (0.00% GC)
mean time: 1.347 μs (0.00% GC)
maximum time: 4.562 μs (0.00% GC)
--------------
samples: 10000
evals/sample: 10
Assembly confirms it is using zmm registers (but this time is much too fast not
to be vectorized, anyway).
For why gfortran is still slower than the Flang version, here is the loop body:
.L16:
vmovups (%r10,%rax), %zmm0
vcmpps $4, %zmm0, %zmm4, %k1
vrsqrt14ps %zmm0, %zmm1{%k1}{z}
vmulps %zmm0, %zmm1, %zmm2
vmulps %zmm1, %zmm2, %zmm0
vmulps %zmm5, %zmm2, %zmm2
vaddps %zmm6, %zmm0, %zmm0
vmulps %zmm2, %zmm0, %zmm0
vrcp14ps %zmm0, %zmm8
vmulps %zmm0, %zmm8, %zmm0
vmulps %zmm0, %zmm8, %zmm0
vaddps %zmm8, %zmm8, %zmm8
vsubps %zmm0, %zmm8, %zmm8
vmulps (%r8,%rax), %zmm8, %zmm9
vmulps (%r9,%rax), %zmm8, %zmm10
vmulps (%r12,%rax), %zmm8, %zmm8
vmovaps %zmm9, %zmm3
vfnmadd213ps 0(%r13,%rax), %zmm9, %zmm3
vcmpps $4, %zmm3, %zmm4, %k1
vrsqrt14ps %zmm3, %zmm2{%k1}{z}
vmulps %zmm3, %zmm2, %zmm3
vmulps %zmm2, %zmm3, %zmm1
vmulps %zmm5, %zmm3, %zmm3
vaddps %zmm6, %zmm1, %zmm1
vmulps %zmm3, %zmm1, %zmm1
vmovaps %zmm9, %zmm3
vfnmadd213ps (%rdx,%rax), %zmm10, %zmm3
vrcp14ps %zmm1, %zmm0
vmulps %zmm1, %zmm0, %zmm1
vmulps %zmm1, %zmm0, %zmm1
vaddps %zmm0, %zmm0, %zmm0
vsubps %zmm1, %zmm0, %zmm11
vmulps %zmm11, %zmm3, %zmm12
vmovaps %zmm10, %zmm3
vfnmadd213ps (%r14,%rax), %zmm10, %zmm3
vfnmadd231ps %zmm12, %zmm12, %zmm3
vcmpps $4, %zmm3, %zmm4, %k1
vrsqrt14ps %zmm3, %zmm1{%k1}{z}
vmulps %zmm3, %zmm1, %zmm3
vmulps %zmm1, %zmm3, %zmm0
vmulps %zmm5, %zmm3, %zmm3
vmovups (%rcx,%rax), %zmm1
vaddps %zmm6, %zmm0, %zmm0
vmulps %zmm3, %zmm0, %zmm0
vrcp14ps %zmm0, %zmm2
vmulps %zmm0, %zmm2, %zmm0
vmulps %zmm0, %zmm2, %zmm0
vaddps %zmm2, %zmm2, %zmm2
vsubps %zmm0, %zmm2, %zmm0
vmulps %zmm0, %zmm11, %zmm3
vmulps %zmm12, %zmm3, %zmm3
vxorps %zmm7, %zmm3, %zmm3
vmulps %zmm1, %zmm3, %zmm2
vmulps %zmm3, %zmm9, %zmm3
vfnmadd231ps %zmm8, %zmm9, %zmm1
vfmadd231ps (%r11,%rax), %zmm0, %zmm2
vfmadd132ps %zmm10, %zmm3, %zmm0
vmulps %zmm11, %zmm1, %zmm1
vfnmadd231ps %zmm0, %zmm8, %zmm2
vmovups %zmm2, (%rdi,%rax)
vmovups %zmm1, (%rbx,%rax)
vmovups %zmm8, (%r15,%rax)
addq $64, %rax
cmpq %rax, %rsi
jne .L16
I see far more arithmetic instructions here. Is that because gcc is adding
Newton-Raphson steps for the reciprocal square roots, and Flang is not?
Trying to compare with mpfr, both seem about the same accurate.
Extreme errors in X with gfortran:
-2.676151882353759158425593894760401386764929650751873229109107488336451373232463e-06
1.396013166812755065773272342567265482854011149035436404435394035182092107481168e-05
with Flang:
-3.086256120296619934226727657432734517145988850964563595564605964817907892518832e-05
2.28181026645836083851985181914739792956608114291961973078603672383927518755594e-06
on the data set I benchmarked with.
Anyway, thanks for the prompt responses.
And my issue was that gfortran didn't vectorize, but your second change fixed
the problem.
It would be nice of course if writing things one way would be optimized well
across all compilers and versions. But compilers are finicky. Simply reordering
operations and adding/removing temporary declarations in fpdbacksolve would
sometimes cause Flang to fail to vectorize!
Maybe I'll use #ifdefs around the declarations and save the files as .F90...
>From gcc-bugs-return-627845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 20:02:40 2019
Return-Path: <gcc-bugs-return-627845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124738 invoked by alias); 6 Jan 2019 20:02:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124568 invoked by uid 48); 6 Jan 2019 20:02:34 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85103] [8/9 Regression] Performance regressions on SPEC with r257582
Date: Sun, 06 Jan 2019 20:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-85103-4-5s4NVnQHUL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00654.txt.bz2
Content-length: 6523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85103
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |WAITING
--- Comment #18 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
I see, I can reproduce it when I remove __inline__ in the function and build
with O3. What happens is the following. MainGtU is quite large hand unrolled
implementation of N^2logN sorting
Bool mainGtU ( UInt32 i1,
UInt32 i2,
UChar* block,
UInt16* quadrant,
UInt32 nblock,
Int32* budget )
{
Int32 k;
UChar c1, c2;
UInt16 s1, s2;
AssertD ( i1 != i2, "mainGtU" );
/* 1 */
c1 = block[i1]; c2 = block[i2];
if (c1 != c2) return (c1 > c2);
i1++; i2++;
/* 2 */
c1 = block[i1]; c2 = block[i2];
if (c1 != c2) return (c1 > c2);
i1++; i2++;
/* 3 */
c1 = block[i1]; c2 = block[i2];
if (c1 != c2) return (c1 > c2);
i1++; i2++;
/* 4 */
c1 = block[i1]; c2 = block[i2];
if (c1 != c2) return (c1 > c2);
i1++; i2++;
...
we decide to split it after first 5 conditionals for some reason.
The partial function is large
IPA function summary for mainGtU.part.0/41 inlinable
global time: 240.000000
self size: 243
global size: 243
min size: 0
self stack: 0
global stack: 0
size:200.000000, time:199.000000
size:4.000000, time:2.000000, executed if:(not inlined)
size:10.000000, time:10.000000, nonconst if:(op0 changed)
size:10.000000, time:10.000000, nonconst if:(op1 changed)
size:9.000000, time:9.000000, nonconst if:(op0 changed || op2 changed)
size:9.000000, time:9.000000, nonconst if:(op1 changed || op2 changed)
size:1.000000, time:1.000000, nonconst if:(op4 changed)
calls:
While the outer function is:
IPA function summary for mainGtU/30 inlinable
global time: 29.125000
self size: 36
global size: 36
min size: 16
self stack: 0
global stack: 0
size:15.000000, time:15.000000
size:3.000000, time:2.000000, executed if:(not inlined)
size:3.000000, time:3.000000, nonconst if:(op0 changed || op2 changed)
size:3.000000, time:3.000000, nonconst if:(op2 changed || op1 changed)
size:2.000000, time:2.000000, nonconst if:(op0 changed)
size:2.000000, time:2.000000, nonconst if:(op1 changed)
calls:
mainGtU.part.0/41 function not considered for inlining
loop depth: 0 freq:0.12 size: 8 time: 17 callee size:121 stack: 0
with 200 instructions that we think can't be optimized (I am not sure why we do
not track accesses to individual block indices).
Later we indeed consider mainGtU.part before the split away part:
Badness calculation for mainGtU/30 -> mainGtU.part.0/41
size growth 231, time 238.000000 unspec 240.000000
-0.000181: guessed profile. frequency 0.125000, count -1 caller count -1
time w/o inlining 59.125000, time with inlining 56.750000 overall growth -12
(current) -12 (original) -12 (compensated)
later we consider the individual parts
Estimated badness is -0.000001, frequency 7718.74.
Badness calculation for mainSimpleSort/32 -> mainGtU/30
size growth 256, time 54.750000 unspec 56.750000 big_speedup
-0.000001: guessed profile. frequency 7718.740543, count -1 caller count
-1 time w/o inlining 827687.848633, time with inlining 681031.777832 overall
growth 501 (current) 39 (original) 1521 (compensated)
Adjusted by hints -0.000001
and inline first one because speedup is considered to be big, but after
inlining the function becomes heavy and remaining two are not inlined.
There is mis-accounting bug for the time needed for execution of manGtU. I
fixed it yesterday for trunk which now has more realistic time estimate for the
sequence of ifs:
IPA function summary for mainGtU.part.0/41 inlinable
global time: 19.766641
self size: 243
global size: 243
min size: 0
self stack: 0
global stack: 0
size:200.000000, time:9.771543
size:4.000000, time:2.004863, executed if:(not inlined)
size:10.000000, time:1.998047, nonconst if:(op0 changed)
size:10.000000, time:1.998047, nonconst if:(op1 changed)
size:9.000000, time:1.996094, nonconst if:(op0 changed || op2 changed)
size:9.000000, time:1.996094, nonconst if:(op1 changed || op2 changed)
size:1.000000, time:0.001953, nonconst if:(op4 changed)
calls:
which makes it to be inlined. Does it solve the perofmrance problem for both
benchmarks?
>From gcc-bugs-return-627846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 20:11:52 2019
Return-Path: <gcc-bugs-return-627846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 599 invoked by alias); 6 Jan 2019 20:11:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 557 invoked by uid 55); 6 Jan 2019 20:11:47 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88130] [9 Regression] ICE in copy_function_or_variable, at lto-streamer-out.c:2315 since r260963
Date: Sun, 06 Jan 2019 20:11: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88130-4-Es6WYu0HqT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00655.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88130
--- Comment #7 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Sun Jan 6 20:11:15 2019
New Revision: 267613
URL: https://gcc.gnu.org/viewcvs?rev=267613&root=gcc&view=rev
Log:
Backport from mainline
2019-01-02 Jan Hubicka <hubicka@ucw.cz>
PR lto/88130
* varpool.c (varpool_node::ctor_useable_for_folding_p): Also return
false at WPA time when body was removed.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/torture/pr88130.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/varpool.c
>From gcc-bugs-return-627847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 20:20:35 2019
Return-Path: <gcc-bugs-return-627847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12230 invoked by alias); 6 Jan 2019 20:20:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12186 invoked by uid 48); 6 Jan 2019 20:20:31 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88130] [9 Regression] ICE in copy_function_or_variable, at lto-streamer-out.c:2315 since r260963
Date: Sun, 06 Jan 2019 20:20: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88130-4-VmSuH285sc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00656.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88130
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 20:38:11 2019
Return-Path: <gcc-bugs-return-627848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33351 invoked by alias); 6 Jan 2019 20:38:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33301 invoked by uid 48); 6 Jan 2019 20:38:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Sun, 06 Jan 2019 20:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88723-4-EOWopU8lws@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00657.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45359
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45359&action=edit
gcc9-pr88723.patch
Actually, UNSPEC_MOVE_GOTDATA always has non-constant arguments, such UNSPECs
we would never consider in the hook before. Does the following patch fix that?
>From gcc-bugs-return-627849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 20:53:18 2019
Return-Path: <gcc-bugs-return-627849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53390 invoked by alias); 6 Jan 2019 20:53:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53341 invoked by uid 55); 6 Jan 2019 20:53:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Sun, 06 Jan 2019 20:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: REOPENED
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:
Message-ID: <bug-87431-4-gkGDgQBYqE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00658.txt.bz2
Content-length: 2119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sun Jan 6 20:52:34 2019
New Revision: 267614
URL: https://gcc.gnu.org/viewcvs?rev=267614&root=gcc&view=rev
Log:
PR libstdc++/87431 fix regression introduced by r264574
The previous patch for PR 87431 assumed that initialing a scalar type
could not throw, but it can obtain its value via a conversion operator,
which could throw. This meant the variant could get into a valueless
state, but the valueless_by_exception() member function would always
return false.
This patch fixes it by changing the emplace members to have strong
exception safety when initializing a contained value of trivially
copyable type. The _M_valid() member gets a corresponding change to
always return true for trivially copyable types, not just scalar types.
Strong exception safety (i.e. never becoming valueless) is achieved by
only replacing the current contained value once any potentially throwing
operations have completed. If constructing the new contained value can
throw then a new std::variant object is constructed to hold it, and then
move-assigned to *this (which won't throw).
PR libstdc++/87431
* include/std/variant (_Variant_storage<true, _Types...>::_M_valid):
Check is_trivially_copyable instead of is_scalar.
(variant::emplace<N, Args>(Args&&...)): If construction of the new
contained value can throw and its type is trivially copyable then
construct into a temporary variant and move from it, to provide the
strong exception safety guarantee.
(variant::emplace<N, U, Args>(initializer_list<U>, Args&&...)):
Likewise.
* testsuite/20_util/variant/87431.cc: New test.
* testsuite/20_util/variant/run.cc: Adjust test so that throwing
conversion causes valueless state.
Added:
trunk/libstdc++-v3/testsuite/20_util/variant/87431.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/std/variant
trunk/libstdc++-v3/testsuite/20_util/variant/run.cc
>From gcc-bugs-return-627850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 20:54:02 2019
Return-Path: <gcc-bugs-return-627850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54299 invoked by alias); 6 Jan 2019 20:54: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 54243 invoked by uid 48); 6 Jan 2019 20:53:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Sun, 06 Jan 2019 20:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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
Message-ID: <bug-87431-4-Bgioe01fGe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00659.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Should be fixed now.
>From gcc-bugs-return-627851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:20:51 2019
Return-Path: <gcc-bugs-return-627851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85505 invoked by alias); 6 Jan 2019 21:20:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85394 invoked by uid 48); 6 Jan 2019 21:20:46 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88727] New: Diagnostics improvement: Detection of undefined behaviour. Incomplete type in tenative definition with internal linkage.
Date: Sun, 06 Jan 2019 21:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00660.txt.bz2
Content-length: 1454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88727
Bug ID: 88727
Summary: Diagnostics improvement: Detection of undefined
behaviour. Incomplete type in tenative definition with
internal linkage.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
static struct S s;
int main()
{
}
struct S { int x; };
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
No error messages outputes.
Possible improvement of behaviour:
Outputing an error message about using an incomplete type in the tenative
definition static struct S s; .
The program has undefined behaviour becuase of a violation of 6.9.2/2:
"If the declaration of an identifier for an object is a tentative definition
and has internal linkage, the declared type shall not be an incomplete
type."
GCC detects such undefined behaviour in other cases (for example using the
incomplete type int []). It would be good if it could also hande the case in
the test case for this bug report.
Note:
Clang detects the undefined behaviour for this program and outputs an error
message.
>From gcc-bugs-return-627852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:52:55 2019
Return-Path: <gcc-bugs-return-627852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86712 invoked by alias); 6 Jan 2019 21:52:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86646 invoked by uid 48); 6 Jan 2019 21:52:49 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87651] [8/9 Regression] inner class with template template friend declaration of same name fails to compile in gcc 8.1, 8.2, and 9.0
Date: Sun, 06 Jan 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution cf_known_to_fail
Message-ID: <bug-87651-4-W2pA6xVWXF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00661.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87651
Ryan R Haining <haining.cpp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Known to fail|9.0 |
--- Comment #2 from Ryan R Haining <haining.cpp at gmail dot com> ---
It looks to be working on head now:
https://wandbox.org/permlink/FTjpi30scFEAgGyO
>From gcc-bugs-return-627853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:54:18 2019
Return-Path: <gcc-bugs-return-627853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88567 invoked by alias); 6 Jan 2019 21:54: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 88495 invoked by uid 48); 6 Jan 2019 21:54:13 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87652] [8/9 Regression] inner class template of outer class template can't access friend's protected data member
Date: Sun, 06 Jan 2019 21:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87652-4-JuboCdukn3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00662.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87652
Ryan R Haining <haining.cpp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Ryan R Haining <haining.cpp at gmail dot com> ---
working on head: https://wandbox.org/permlink/4dCLIfaIPWij81Vi
>From gcc-bugs-return-627854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:55:35 2019
Return-Path: <gcc-bugs-return-627854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90266 invoked by alias); 6 Jan 2019 21:55: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 90226 invoked by uid 48); 6 Jan 2019 21:55:30 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65799] Allows constexpr conversion from cv void * to other type
Date: Sun, 06 Jan 2019 21:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-65799-4-HlqSayz7Qf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00663.txt.bz2
Content-length: 507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65799
Ryan R Haining <haining.cpp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Ryan R Haining <haining.cpp at gmail dot com> ---
code is correctly failing on head:
https://wandbox.org/permlink/6vj1agxCRZaTYs7b
>From gcc-bugs-return-627855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:57:37 2019
Return-Path: <gcc-bugs-return-627855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94466 invoked by alias); 6 Jan 2019 21:57:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94436 invoked by uid 48); 6 Jan 2019 21:57:32 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79624] comma separate auto variables deduce different types under dependent lookup
Date: Sun, 06 Jan 2019 21:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79624-4-2VdviQXPGl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79624-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79624-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00664.txt.bz2
Content-length: 195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79624
--- Comment #4 from Ryan R Haining <haining.cpp at gmail dot com> ---
still a problem on head: https://wandbox.org/permlink/tPYbCp1jWYmc9O9J
>From gcc-bugs-return-627857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:59:52 2019
Return-Path: <gcc-bugs-return-627857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112235 invoked by alias); 6 Jan 2019 21: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 112196 invoked by uid 48); 6 Jan 2019 21:59:47 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68423] override/final doesn't cause error in templated class without base
Date: Sun, 06 Jan 2019 21:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-68423-4-WFLx0UqRe0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00666.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68423
Ryan R Haining <haining.cpp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WONTFIX |INVALID
--- Comment #3 from Ryan R Haining <haining.cpp at gmail dot com> ---
Seems like WONTFIX by the last comment
>From gcc-bugs-return-627856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 21:59:25 2019
Return-Path: <gcc-bugs-return-627856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111478 invoked by alias); 6 Jan 2019 21:59:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111437 invoked by uid 48); 6 Jan 2019 21:59:20 -0000
From: "haining.cpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68423] override/final doesn't cause error in templated class without base
Date: Sun, 06 Jan 2019 21:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: haining.cpp at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-68423-4-ERyzJaKfkV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00665.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68423
Ryan R Haining <haining.cpp at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #2 from Ryan R Haining <haining.cpp at gmail dot com> ---
Seems like WONTFIX by the last comment
>From gcc-bugs-return-627858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:35:10 2019
Return-Path: <gcc-bugs-return-627858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17551 invoked by alias); 6 Jan 2019 22:35:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17416 invoked by uid 55); 6 Jan 2019 22:35:01 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86756] Don't define __cpp_lib_filesystem unless --enable-libstdcxx-filesystem-ts
Date: Sun, 06 Jan 2019 22:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86756-4-BiFZDpl239@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00667.txt.bz2
Content-length: 10181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86756
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sun Jan 6 22:34:29 2019
New Revision: 267615
URL: https://gcc.gnu.org/viewcvs?rev=267615&root=gcc&view=rev
Log:
PR libstdc++/86756 add std::filesystem::path to libstdc++.so
Move the C++17 std::filesystem::path definitions from the libstdc++fs.a
archive to the main libstdc++ library. The path classes do not depend on
any OS functions, so can be defined unconditionally on all targets
(rather than depending on --enable-libstdcxx-filesystem-ts). The tests
should pass on all targets too.
PR libstdc++/86756
* config/abi/pre/gnu.ver (GLIBCXX_3.4): Make various patterns for
typeinfo and vtables less greedy.
(GLIBCXX_3.4.26): Export symbols for std::filesystem::path.
* src/c++17/Makefile.am: Add fs_path.cc and cow-fs_path.cc.
* src/c++17/Makefile.in: Regenerate.
* src/c++17/cow-fs_path.cc: Move src/filesystem/cow-std-path.cc to
here, and change name of included file.
* src/c++17/fs_path.cc: Move src/filesystem/std-path.cc to here.
* src/filesystem/Makefile.am: Remove std-path.cc and cow-std-path.cc
from sources.
* src/filesystem/Makefile.in: Regenerate.
* src/filesystem/cow-std-path.cc: Move to src/c++17/cow-fs_path.cc.
* src/filesystem/std-path.cc: Move to src/c++17/fs_path.cc.
* testsuite/27_io/filesystem/path/append/path.cc: Remove -lstdc++fs
from dg-options and remove dg-require-filesystem-ts.
* testsuite/27_io/filesystem/path/append/source.cc: Likewise.
* testsuite/27_io/filesystem/path/assign/assign.cc: Likewise.
* testsuite/27_io/filesystem/path/assign/copy.cc: Likewise.
* testsuite/27_io/filesystem/path/compare/compare.cc: Likewise.
* testsuite/27_io/filesystem/path/compare/lwg2936.cc: Likewise.
* testsuite/27_io/filesystem/path/compare/path.cc: Likewise.
* testsuite/27_io/filesystem/path/compare/strings.cc: Likewise.
* testsuite/27_io/filesystem/path/concat/path.cc: Likewise.
* testsuite/27_io/filesystem/path/concat/strings.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/80762.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/copy.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/default.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/format.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/locale.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/range.cc: Likewise.
* testsuite/27_io/filesystem/path/construct/string_view.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/extension.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/filename.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/parent_path.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/relative_path.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/root_directory.cc:
Likewise.
* testsuite/27_io/filesystem/path/decompose/root_name.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/root_path.cc: Likewise.
* testsuite/27_io/filesystem/path/decompose/stem.cc: Likewise.
* testsuite/27_io/filesystem/path/generation/normal.cc: Likewise.
* testsuite/27_io/filesystem/path/generation/normal2.cc: Likewise.
* testsuite/27_io/filesystem/path/generation/proximate.cc: Likewise.
* testsuite/27_io/filesystem/path/generation/relative.cc: Likewise.
* testsuite/27_io/filesystem/path/generic/generic_string.cc: Likewise.
* testsuite/27_io/filesystem/path/itr/components.cc: Likewise.
* testsuite/27_io/filesystem/path/itr/traversal.cc: Likewise.
* testsuite/27_io/filesystem/path/modifiers/clear.cc: Likewise.
* testsuite/27_io/filesystem/path/modifiers/make_preferred.cc:
Likewise.
* testsuite/27_io/filesystem/path/modifiers/remove_filename.cc:
Likewise.
* testsuite/27_io/filesystem/path/modifiers/replace_extension.cc:
Likewise.
* testsuite/27_io/filesystem/path/modifiers/replace_filename.cc:
Likewise.
* testsuite/27_io/filesystem/path/modifiers/swap.cc: Likewise.
* testsuite/27_io/filesystem/path/native/string.cc: Likewise.
* testsuite/27_io/filesystem/path/nonmember/append.cc: Likewise.
* testsuite/27_io/filesystem/path/nonmember/hash_value.cc: Likewise.
* testsuite/27_io/filesystem/path/query/empty.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_extension.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_filename.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_parent_path.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_relative_path.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_root_directory.cc:
Likewise.
* testsuite/27_io/filesystem/path/query/has_root_name.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_root_path.cc: Likewise.
* testsuite/27_io/filesystem/path/query/has_stem.cc: Likewise.
* testsuite/27_io/filesystem/path/query/is_absolute.cc: Likewise.
* testsuite/27_io/filesystem/path/query/is_relative.cc: Likewise.
Added:
trunk/libstdc++-v3/src/c++17/cow-fs_path.cc
- copied, changed from r267614,
trunk/libstdc++-v3/src/filesystem/cow-std-path.cc
trunk/libstdc++-v3/src/c++17/fs_path.cc
- copied, changed from r267614,
trunk/libstdc++-v3/src/filesystem/std-path.cc
Removed:
trunk/libstdc++-v3/src/filesystem/cow-std-path.cc
trunk/libstdc++-v3/src/filesystem/std-path.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/config/abi/pre/gnu.ver
trunk/libstdc++-v3/src/c++17/Makefile.am
trunk/libstdc++-v3/src/c++17/Makefile.in
trunk/libstdc++-v3/src/filesystem/Makefile.am
trunk/libstdc++-v3/src/filesystem/Makefile.in
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/append/path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/append/source.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/assign/assign.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/assign/copy.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/compare/compare.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/compare/lwg2936.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/compare/path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/compare/strings.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/concat/path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/concat/strings.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/80762.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/copy.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/default.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/format.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/locale.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/range.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/construct/string_view.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/extension.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/filename.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/parent_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/relative_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/root_directory.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/root_name.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/root_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/decompose/stem.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/generation/normal.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/generation/normal2.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/generation/proximate.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/generation/relative.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/generic/generic_string.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/itr/components.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/itr/traversal.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/modifiers/clear.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/modifiers/make_preferred.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/modifiers/remove_filename.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/modifiers/replace_extension.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/modifiers/replace_filename.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/modifiers/swap.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/native/string.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/nonmember/append.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/nonmember/hash_value.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/empty.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_extension.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_filename.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_parent_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_relative_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_root_directory.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_root_name.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_root_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/has_stem.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/is_absolute.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/path/query/is_relative.cc
>From gcc-bugs-return-627859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:35:19 2019
Return-Path: <gcc-bugs-return-627859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18255 invoked by alias); 6 Jan 2019 22:35: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 17642 invoked by uid 55); 6 Jan 2019 22:35:10 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86756] Don't define __cpp_lib_filesystem unless --enable-libstdcxx-filesystem-ts
Date: Sun, 06 Jan 2019 22:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86756-4-7dEwbu7e9C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00668.txt.bz2
Content-length: 9869
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86756
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sun Jan 6 22:34:37 2019
New Revision: 267616
URL: https://gcc.gnu.org/viewcvs?rev=267616&root=gcc&view=rev
Log:
PR libstdc++/86756 Move rest of std::filesystem to libstdc++.so
Move std::filesystem directory iterators and operations from
libstdc++fs.a to main libstdc++ library. These components have many
dependencies on OS support, which is not available on all targets. Some
additional autoconf checks and conditional compilation is needed to
ensure the files will build for all targets. Previously this code was
not compiled without --enable-libstdcxx-filesystem-ts but the C++17
components should be available for all hosted builds.
The tests for these components no longer need to link to libstdc++fs.a,
but are not expected to pass on all targets. To avoid numerous failures
on targets which are not expected to pass the tests (due to missing OS
functionality) leave the dg-require-filesystem-ts directives in place
for now. This will ensure the tests only run for builds where the
filesystem-ts library is built, which presumably means some level of OS
support is present.
PR libstdc++/86756
* acinclude.m4 (GLIBCXX_CHECK_FILESYSTEM_DEPS): Check for utime and
lstat and define _GLIBCXX_USE_UTIME and _GLIBCXX_USE_LSTAT.
* config.h.in: Regenerate.
* config/abi/pre/gnu.ver (GLIBCXX_3.4.26): Export symbols for
remaining std::filesystem types and functions.
* configure: Regenerate.
* src/c++17/Makefile.am: Add C++17 filesystem sources.
* src/c++17/Makefile.in: Regenerate.
* src/c++17/cow-fs_dir.cc: Move src/filesystem/cow-std-dir.cc to
here, and change name of included file.
* src/c++17/cow-fs_ops.cc: Move src/filesystem/cow-std-ops.cc to
here, and change name of included file.
* src/c++17/fs_dir.cc: Move src/filesystem/std-dir.cc to here. Change
path to dir-common.h.
* src/c++17/fs_ops.cc: Move src/filesystem/std-ops.cc to here. Change
path to ops-common.h. Disable -Wunused-parameter warnings.
(internal_file_clock): Define unconditionally.
[!_GLIBCXX_HAVE_SYS_STAT_H] (internal_file_clock::from_stat): Do not
define.
(do_copy_file, do_space): Move definitions to ops.common.h.
(copy, file_size, hard_link_count, last_write_time, space): Only
perform operation when _GLIBCXX_HAVE_SYS_STAT_H is defined, otherwise
report an error.
(last_write_time, read_symlink): Remove unused attributes from
parameters.
* src/filesystem/Makefile.am: Remove C++17 filesystem sources.
* src/filesystem/Makefile.in: Regenerate.
* src/filesystem/cow-std-dir.cc: Move to src/c++17/cow-fs_dir.cc.
* src/filesystem/cow-std-ops.cc: Move to src/c++17/cow-fs_ops.cc.
* src/filesystem/std-dir.cc: Move to src/c++17/fs_dir.cc.
* src/filesystem/std-ops.cc: Move to src/c++17/fs_ops.cc.
* src/filesystem/dir-common.h [!_GLIBCXX_HAVE_DIRENT_H]: Define
dummy types and functions instead of using #error.
* src/filesystem/dir.cc [!_GLIBCXX_HAVE_DIRENT_H]: Use #error.
* src/filesystem/ops-common.h [!_GLIBCXX_USE_LSTAT] (lstat): Define
in terms of stat.
[!_GLIBCXX_HAVE_UNISTD_H]: Define dummy types and functions.
(do_copy_file, do_space): Move definitions here from std-ops.cc.
* src/filesystem/ops.cc: Adjust calls to do_copy_file and do_space
to account for new namespace.
* testsuite/27_io/filesystem/directory_entry/86597.cc: Remove
-lstdc++fs from dg-options.
* testsuite/27_io/filesystem/directory_entry/lwg3171.cc: Likewise.
* testsuite/27_io/filesystem/file_status/1.cc: Likewise.
* testsuite/27_io/filesystem/filesystem_error/cons.cc: Likewise.
* testsuite/27_io/filesystem/filesystem_error/copy.cc: Likewise.
* testsuite/27_io/filesystem/iterators/directory_iterator.cc:
Likewise.
* testsuite/27_io/filesystem/iterators/pop.cc: Likewise.
* testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc:
Likewise.
* testsuite/27_io/filesystem/operations/absolute.cc: Likewise.
* testsuite/27_io/filesystem/operations/canonical.cc: Likewise.
* testsuite/27_io/filesystem/operations/copy.cc: Likewise.
* testsuite/27_io/filesystem/operations/copy_file.cc: Likewise.
* testsuite/27_io/filesystem/operations/create_directories.cc:
Likewise.
* testsuite/27_io/filesystem/operations/create_directory.cc: Likewise.
* testsuite/27_io/filesystem/operations/create_symlink.cc: Likewise.
* testsuite/27_io/filesystem/operations/current_path.cc: Likewise.
* testsuite/27_io/filesystem/operations/equivalent.cc: Likewise.
* testsuite/27_io/filesystem/operations/exists.cc: Likewise.
* testsuite/27_io/filesystem/operations/file_size.cc: Likewise.
* testsuite/27_io/filesystem/operations/is_empty.cc: Likewise.
* testsuite/27_io/filesystem/operations/last_write_time.cc: Likewise.
* testsuite/27_io/filesystem/operations/permissions.cc: Likewise.
* testsuite/27_io/filesystem/operations/proximate.cc: Likewise.
* testsuite/27_io/filesystem/operations/read_symlink.cc: Likewise.
* testsuite/27_io/filesystem/operations/relative.cc: Likewise.
* testsuite/27_io/filesystem/operations/remove.cc: Likewise.
* testsuite/27_io/filesystem/operations/remove_all.cc: Likewise.
* testsuite/27_io/filesystem/operations/space.cc: Likewise.
* testsuite/27_io/filesystem/operations/status.cc: Likewise.
* testsuite/27_io/filesystem/operations/symlink_status.cc: Likewise.
* testsuite/27_io/filesystem/operations/temp_directory_path.cc:
Likewise.
* testsuite/27_io/filesystem/operations/weakly_canonical.cc: Likewise.
Added:
trunk/libstdc++-v3/src/c++17/cow-fs_dir.cc
- copied, changed from r267615,
trunk/libstdc++-v3/src/filesystem/cow-std-dir.cc
trunk/libstdc++-v3/src/c++17/cow-fs_ops.cc
- copied, changed from r267615,
trunk/libstdc++-v3/src/filesystem/cow-std-ops.cc
trunk/libstdc++-v3/src/c++17/fs_dir.cc
- copied, changed from r267615,
trunk/libstdc++-v3/src/filesystem/std-dir.cc
trunk/libstdc++-v3/src/c++17/fs_ops.cc
- copied, changed from r267615,
trunk/libstdc++-v3/src/filesystem/std-ops.cc
Removed:
trunk/libstdc++-v3/src/filesystem/cow-std-dir.cc
trunk/libstdc++-v3/src/filesystem/cow-std-ops.cc
trunk/libstdc++-v3/src/filesystem/std-dir.cc
trunk/libstdc++-v3/src/filesystem/std-ops.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/acinclude.m4
trunk/libstdc++-v3/config.h.in
trunk/libstdc++-v3/config/abi/pre/gnu.ver
trunk/libstdc++-v3/configure
trunk/libstdc++-v3/src/c++17/Makefile.am
trunk/libstdc++-v3/src/c++17/Makefile.in
trunk/libstdc++-v3/src/filesystem/Makefile.am
trunk/libstdc++-v3/src/filesystem/Makefile.in
trunk/libstdc++-v3/src/filesystem/dir-common.h
trunk/libstdc++-v3/src/filesystem/dir.cc
trunk/libstdc++-v3/src/filesystem/ops-common.h
trunk/libstdc++-v3/src/filesystem/ops.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/directory_entry/86597.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/directory_entry/lwg3171.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/file_status/1.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/filesystem_error/cons.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/filesystem_error/copy.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/iterators/directory_iterator.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/iterators/pop.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/iterators/recursive_directory_iterator.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/absolute.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/canonical.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/copy.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/copy_file.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/create_directories.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/create_directory.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/create_symlink.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/current_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/equivalent.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/exists.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/file_size.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/is_empty.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/last_write_time.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/permissions.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/proximate.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/read_symlink.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/relative.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/remove.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/remove_all.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/space.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/status.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/symlink_status.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/temp_directory_path.cc
trunk/libstdc++-v3/testsuite/27_io/filesystem/operations/weakly_canonical.cc
>From gcc-bugs-return-627860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:37:35 2019
Return-Path: <gcc-bugs-return-627860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27172 invoked by alias); 6 Jan 2019 22:37:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27105 invoked by uid 48); 6 Jan 2019 22:37:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86756] Don't define __cpp_lib_filesystem unless --enable-libstdcxx-filesystem-ts
Date: Sun, 06 Jan 2019 22:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: 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-86756-4-ZkrZTkTar9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00669.txt.bz2
Content-length: 568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86756
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The C++17 std::filesystem library is now supported unconditionally, so it's
correct to define __cpp_lib_filesystem unconditionally. So this is fixed.
>From gcc-bugs-return-627861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:43:55 2019
Return-Path: <gcc-bugs-return-627861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40030 invoked by alias); 6 Jan 2019 22:43:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39982 invoked by uid 48); 6 Jan 2019 22:43:49 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65799] Allows constexpr conversion from cv void * to other type
Date: Sun, 06 Jan 2019 22:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: accepts-invalid
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: 7.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-65799-4-PozxwuvgpH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00670.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65799
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|8.2.0 |4.9.2
Target Milestone|--- |7.0
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 7.1 by r238909, which fixed:
PR c++/60760 - arithmetic on null pointers should not be allowed in
constant
PR c++/71091 - constexpr reference bound to a null pointer dereference
>From gcc-bugs-return-627862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:46:08 2019
Return-Path: <gcc-bugs-return-627862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42125 invoked by alias); 6 Jan 2019 22:46: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 42019 invoked by uid 48); 6 Jan 2019 22:45:59 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79624] comma separate auto variables deduce different types under dependent lookup
Date: Sun, 06 Jan 2019 22:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-79624-4-O2odJwpsAi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79624-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79624-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00671.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79624
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-06
Ever confirmed|0 |1
>From gcc-bugs-return-627865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:51:53 2019
Return-Path: <gcc-bugs-return-627865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50238 invoked by alias); 6 Jan 2019 22: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 50128 invoked by uid 48); 6 Jan 2019 22:51:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88716] Improved diagnostics: No detection of conflicting function definitions in some cases.
Date: Sun, 06 Jan 2019 22:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also
Message-ID: <bug-88716-4-nab5m2hSWB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88716-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88716-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00674.txt.bz2
Content-length: 866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88716
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=86418,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=83656,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=82922
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
See also pr82922 and pr86418.
>From gcc-bugs-return-627863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:51:17 2019
Return-Path: <gcc-bugs-return-627863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48536 invoked by alias); 6 Jan 2019 22:51:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48447 invoked by uid 48); 6 Jan 2019 22:51:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87651] [8 Regression] inner class with template template friend declaration of same name fails to compile in gcc 8.1, 8.2, and 9.0
Date: Sun, 06 Jan 2019 22:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work dependson resolution short_desc
Message-ID: <bug-87651-4-YcADF26cKO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00672.txt.bz2
Content-length: 1381
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87651
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Known to work| |9.0
Depends on| |86747
Resolution|FIXED |---
Summary|[8/9 Regression] inner |[8 Regression] inner class
|class with template |with template template
|template friend declaration |friend declaration of same
|of same name fails to |name fails to compile in
|compile in gcc 8.1, 8.2, |gcc 8.1, 8.2, and 9.0
|and 9.0 |
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But not fixed on gcc-8-branch, so it should be kept open until the regression
is fixed.
Started to compile with r266875, which fixed:
[PR86747] tsubst friend tpl ctxt before looking it up for dupes
Possibly a dup of that one. It might get fixed when that is backported to
gcc-8-branch.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
[Bug 86747] [8 Regression] rejects-valid with redundant friend declaration
>From gcc-bugs-return-627864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:51:41 2019
Return-Path: <gcc-bugs-return-627864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49344 invoked by alias); 6 Jan 2019 22: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 49245 invoked by uid 48); 6 Jan 2019 22:51:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87652] [8/9 Regression] inner class template of outer class template can't access friend's protected data member
Date: Sun, 06 Jan 2019 22:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status dependson resolution
Message-ID: <bug-87652-4-2mDzkJNu6d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00673.txt.bz2
Content-length: 909
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87652
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Depends on| |86747
Resolution|FIXED |---
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But not fixed on gcc-8-branch, so it should be kept open until the regression
is fixed.
Started to compile with r266875, which fixed:
[PR86747] tsubst friend tpl ctxt before looking it up for dupes
Possibly a dup of that one. It might get fixed when that is backported to
gcc-8-branch.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
[Bug 86747] [8 Regression] rejects-valid with redundant friend declaration
>From gcc-bugs-return-627866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:52:30 2019
Return-Path: <gcc-bugs-return-627866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52474 invoked by alias); 6 Jan 2019 22:52:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51881 invoked by uid 48); 6 Jan 2019 22:52:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86747] [8 Regression] rejects-valid with redundant friend declaration
Date: Sun, 06 Jan 2019 22:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: aoliva at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86747-4-STgYlRUBJq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00675.txt.bz2
Content-length: 208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86747
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This patch also fixed PR 87651 and PR 87652 which are also regressions on
gcc-8-branch.
>From gcc-bugs-return-627867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 22:59:05 2019
Return-Path: <gcc-bugs-return-627867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59757 invoked by alias); 6 Jan 2019 22:59: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 59642 invoked by uid 48); 6 Jan 2019 22:58:58 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Sun, 06 Jan 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87957-4-4MUdHhlWcf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00676.txt.bz2
Content-length: 1312
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at redhat dot com
--- Comment #23 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Hello,
sorry for late response. The assert which trigger is there so we do not copy
one DECL_NAME multiple times which code would do when there are multiple types
that points to same TYPE_NAME being simplified.
Because early debug info is already output we are supposed to translate all
TYPE_NAMEs to IDENTIFIER_NODE with exception of main variants of C++ ODR types
where TYPE_NAME is preserved and we compute its DECL_ASSEMBLER_NAME so we can
identify same types cross-module later.
The name is supposed to be simplified by fld_simplified_type_name.
I am not sure how to get command line for debugger but I assume that it does
not simplify type name because type_with_linkage_p returns true which is wrong
for Ada types (it tests whether it is C++ ODR type). type_with_linkage_p
basically assumes that only C++ types have DECL_NAME of TYPE_DECL which is not
true for Ada, so we need to find way to tell these types apart.
>From gcc-bugs-return-627868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:43:15 2019
Return-Path: <gcc-bugs-return-627868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 473 invoked by alias); 6 Jan 2019 23:43: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 131053 invoked by uid 48); 6 Jan 2019 23:43:09 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Sun, 06 Jan 2019 23: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on component blocked resolution short_desc everconfirmed
Message-ID: <bug-88713-4-wER0URDAqe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00677.txt.bz2
Content-length: 1332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Last reconfirmed| |2019-01-06
Component|fortran |tree-optimization
Blocks|36854 |53947
Resolution|WONTFIX |---
Summary|_gfortran_internal_pack@PLT |Vectorized code slow vs.
|prevents vectorization |flang
Ever confirmed|0 |1
--- Comment #11 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
OK, so I think it makes sense to reopen this bug as a missed
optimization for the vectorizer (reopen because it would be a shame
to lose all the info you already provided).
It seems like gcc could be much better, also possibly with some
more help from the gfortran front end. A factor of two is not to
be ignored.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36854
[Bug 36854] [meta-bug] fortran front-end optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
>From gcc-bugs-return-627869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:43:16 2019
Return-Path: <gcc-bugs-return-627869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 572 invoked by alias); 6 Jan 2019 23:43:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 346 invoked by uid 48); 6 Jan 2019 23:43:12 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/53947] [meta-bug] vectorizer missed-optimizations
Date: Sun, 06 Jan 2019 23:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-53947-4-jtCL85VYpT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53947-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53947-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00678.txt.bz2
Content-length: 454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
Bug 53947 depends on bug 88713, which changed state.
Bug 88713 Summary: Vectorized code slow vs. flang
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WONTFIX |---
>From gcc-bugs-return-627870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:52:13 2019
Return-Path: <gcc-bugs-return-627870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8074 invoked by alias); 6 Jan 2019 23:52: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 8042 invoked by uid 48); 6 Jan 2019 23:52:08 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88728] New: Boostrap with -Og fails with garbled file libgcov-profiler.i
Date: Sun, 06 Jan 2019 23:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
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-88728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00679.txt.bz2
Content-length: 2452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
Bug ID: 88728
Summary: Boostrap with -Og fails with garbled file
libgcov-profiler.i
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: preprocessor
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
Created attachment 45360
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45360&action=edit
Generated libgcov-profiler.i file
I tried booting with -Og, with a strange result.
Setting CFLAGS and CXXFLAGS to "-Og -save-temps" and running
with a recent trunk resulted in
RMAT -DHAVE_CC_TLS -DUSE_TLS -o _gcov_indirect_call_topn_profiler.o -MT
_gcov_indirect_call_topn_profiler.o -MD -MP -MF
_gcov_indirect_call_topn_profiler.dep -DL_gcov_indirect_call_topn_profiler -c
../../../ggdb3/libgcc/libgcov-profiler.c
../../../ggdb3/libgcc/libgcov-profiler.c:352:1: Warnung: Datendefinition hat
keinen Typ oder Speicherklasse
352 | #endif
| ^~~~
../../../ggdb3/libgcc/libgcov-profiler.c:352:1: Warnung: »int« ist Standardtyp
in Deklaration von »alue« [-Wimplicit-int]
../../../ggdb3/libgcc/libgcov-profiler.c:352:7: Fehler: expected identifier or
»(« before numeric constant
352 | #endif
| ^
../../../ggdb3/libgcc/libgcov-profiler.c:353:23: Fehler: expected declaration
specifiers or »...« before »&« token
353 |
| ^
../../../ggdb3/libgcc/libgcov-profiler.c:353:37: Fehler: expected declaration
specifiers or »...« before numeric constant
353 |
| ^
../../../ggdb3/libgcc/libgcov-profiler.c:353:40: Fehler: expected declaration
specifiers or »...« before numeric constant
353 |
| ^
../../../ggdb3/libgcc/libgcov-profiler.c:354:1: Fehler: expected identifier or
»(« before »}« token
The generated file libgcov-profiler.i (attached) is quite garbled:
# 159 "../../../ggdb3/libgcc/libgcov-profiler.c"
void
__gcov_one_value_profiler_atomic (gcov_type *counters, gcov_type value)
{
__gcov_one_value_profiler_body (counters, value, 1);
}
omic)
__atomic_fetch_add (&counters[2], 1, 0);
else
counters[2]++;
}
= value;
>From gcc-bugs-return-627871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:52:29 2019
Return-Path: <gcc-bugs-return-627871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9829 invoked by alias); 6 Jan 2019 23:52: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 9120 invoked by uid 48); 6 Jan 2019 23:52:22 -0000
From: "koenigni at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88729] New: ICE in libiberty during bootstrap with debug info
Date: Sun, 06 Jan 2019 23: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: koenigni at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00680.txt.bz2
Content-length: 5294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88729
Bug ID: 88729
Summary: ICE in libiberty during bootstrap with debug info
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: koenigni at gcc dot gnu.org
Target Milestone: ---
While trying to compile gcc with maximum debug info it ICE'd in
libiberty/d-demangle.c in expand_gimple_statement().
The error happens only on power (powerpc64le-unknown-linux-gnu), on x86-64 it
dies in a different way a bit later (Thomas will file the bug report for that).
Below is the way the compiler was configured and the command that caused the
ICE.
$ CFLAGS="-Og -ggdb3" CXXFLAGS="-Og -ggdb3" ../trunk/configure
--snip--
$ make
--snip--
gcc -c -DHAVE_CONFIG_H -Og -ggdb3 -save-temps -I.
-I../../../trunk/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat
-Wstrict-prototypes -Wshadow=local -pedantic -D_GNU_SOURCE
../../../trunk/libiberty/d-demangle.c -o noasan/d-demangle.o; \
else true; fi
gcc -c -DHAVE_CONFIG_H -Og -ggdb3 -save-temps -I.
-I../../../trunk/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat
-Wstrict-prototypes -Wshadow=local -pedantic -D_GNU_SOURCE
../../../trunk/libiberty/d-demangle.c -o d-demangle.o
../../../trunk/libiberty/d-demangle.c: In function ‘dlang_value’:
../../../trunk/libiberty/d-demangle.c:1278:14: warning: this statement may fall
through [-Wimplicit-fallthrough=]
1278 | mangled++;
| ~~~~~~~^~
../../../trunk/libiberty/d-demangle.c:1284:5: note: here
1284 | case '0': case '1': case '2': case '3': case '4':
| ^~~~
../../../trunk/libiberty/d-demangle.c: In function ‘dlang_type’:
../../../trunk/libiberty/d-demangle.c:619:10: warning: this statement may fall
through [-Wimplicit-fallthrough=]
619 | if (!dlang_call_convention_p (mangled))
| ^
../../../trunk/libiberty/d-demangle.c:626:5: note: here
626 | case 'F': /* function T (D) */
| ^~~~
during RTL pass: expand
../../../trunk/libiberty/d-demangle.c: In function ‘dlang_identifier’:
../../../trunk/libiberty/d-demangle.c:850:8: internal compiler error: in
set_value_range, at tree-vrp.c:289
850 | if (strncmp (mangled, "__ctor", len) == 0)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
0x10d620b3 set_value_range(value_range*, value_range_type, tree_node*,
tree_node*, bitmap_head*)
../../trunk-caf/gcc/tree-vrp.c:289
0x10d6c2d3 extract_range_from_binary_expr_1(value_range*, tree_code,
tree_node*, value_range*, value_range*)
../../trunk-caf/gcc/tree-vrp.c:1604
0x10d6e76b determine_value_range_1
../../trunk-caf/gcc/tree-vrp.c:6865
0x10d6eb43 determine_value_range(tree_node*,
generic_wide_int<wide_int_storage>*, generic_wide_int<wide_int_storage>*)
../../trunk-caf/gcc/tree-vrp.c:6900
0x10393243 get_size_range(tree_node*, tree_node**, bool)
../../trunk-caf/gcc/calls.c:1258
0x1039a00b maybe_warn_nonstring_arg(tree_node*, tree_node*)
../../trunk-caf/gcc/calls.c:1617
0x1039bafb initialize_argument_information
../../trunk-caf/gcc/calls.c:2197
0x1039cfdf expand_call(tree_node*, rtx_def*, int)
../../trunk-caf/gcc/calls.c:3577
0x10375c2f expand_builtin_strncmp
../../trunk-caf/gcc/builtins.c:4793
0x103861cb expand_builtin(tree_node*, rtx_def*, rtx_def*, machine_mode, int)
../../trunk-caf/gcc/builtins.c:7445
0x1054ae3f expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../trunk-caf/gcc/expr.c:10943
0x10564f53 expand_expr
../../trunk-caf/gcc/expr.h:279
0x10564f53 expand_expr_real_2(separate_ops*, rtx_def*, machine_mode,
expand_modifier)
../../trunk-caf/gcc/expr.c:8456
0x1054733b expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../trunk-caf/gcc/expr.c:11230
0x1055a9c7 expand_expr
../../trunk-caf/gcc/expr.h:279
0x1055a9c7 store_expr(tree_node*, rtx_def*, int, bool, bool)
../../trunk-caf/gcc/expr.c:5556
0x1055c653 expand_assignment(tree_node*, tree_node*, bool)
../../trunk-caf/gcc/expr.c:5420
0x103b6c6f expand_call_stmt
../../trunk-caf/gcc/cfgexpand.c:2685
0x103b6c6f expand_gimple_stmt_1
../../trunk-caf/gcc/cfgexpand.c:3575
0x103b6c6f expand_gimple_stmt
../../trunk-caf/gcc/cfgexpand.c:3734
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.
Makefile:703: recipe for target 'd-demangle.o' failed
make[3]: *** [d-demangle.o] Error 1
make[3]: Leaving directory
'/home/gcc/trunk-bin/build-powerpc64le-unknown-linux-gnu/libiberty'
Makefile:2686: recipe for target 'all-build-libiberty' failed
make[2]: *** [all-build-libiberty] Error 2
make[2]: Leaving directory '/home/gcc/trunk-bin'
Makefile:27153: recipe for target 'stage1-bubble' failed
make[1]: *** [stage1-bubble] Error 2
make[1]: Leaving directory '/home/gcc/trunk-bin'
Makefile:991: recipe for target 'all' failed
make: *** [all] Error 2
>From gcc-bugs-return-627872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:53:14 2019
Return-Path: <gcc-bugs-return-627872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11103 invoked by alias); 6 Jan 2019 23:53: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 11076 invoked by uid 48); 6 Jan 2019 23:53:09 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88728] Boostrap with -Og fails with garbled file libgcov-profiler.i
Date: Sun, 06 Jan 2019 23:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88728-4-wO22C7USRc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00681.txt.bz2
Content-length: 275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Created attachment 45361
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45361&action=edit
config log
Here's the config.log from the configure.
>From gcc-bugs-return-627873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:54:31 2019
Return-Path: <gcc-bugs-return-627873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12258 invoked by alias); 6 Jan 2019 23:54:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12219 invoked by uid 48); 6 Jan 2019 23:54:25 -0000
From: "koenigni at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88729] ICE in libiberty during bootstrap with debug info
Date: Sun, 06 Jan 2019 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: koenigni at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-88729-4-icmzGKnU7n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00682.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88729
Nicolas Koenig <koenigni at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |koenigni at gcc dot gnu.org
--- Comment #1 from Nicolas Koenig <koenigni at gcc dot gnu.org> ---
Forgot to add, it tested it with the current trunk (r267612)
>From gcc-bugs-return-627874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:55:18 2019
Return-Path: <gcc-bugs-return-627874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13609 invoked by alias); 6 Jan 2019 23:55: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 13562 invoked by uid 48); 6 Jan 2019 23:55:14 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88719] [9 Regression] wrong code at -O2, -O3, and -Os on x86_64-linux-gnu
Date: Sun, 06 Jan 2019 23:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88719-4-mGJ8VPVDmR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88719-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88719-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00683.txt.bz2
Content-length: 743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88719
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This is not a bug but undefined behavior as you have an alias violation; even
though you have an union there.
if (**g = 0)
;
else if (*e)
--h;
You store via long int but load via short int.
Since you don't type pune through the union type but rather the base types;
this is undefined behavior.
>From gcc-bugs-return-627875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:55:59 2019
Return-Path: <gcc-bugs-return-627875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14499 invoked by alias); 6 Jan 2019 23:55:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14467 invoked by uid 48); 6 Jan 2019 23:55:55 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88728] Boostrap with -Og fails with garbled file libgcov-profiler.i
Date: Sun, 06 Jan 2019 23:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88728-4-aeuNOjSRs8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00684.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Created attachment 45362
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45362&action=edit
config.status
And here is the config.log.
See also https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88729 , which
exposed am (apparently) different problem while trying -Og on a POWER9.
>From gcc-bugs-return-627876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 06 23:57:15 2019
Return-Path: <gcc-bugs-return-627876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17020 invoked by alias); 6 Jan 2019 23:57: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 16987 invoked by uid 48); 6 Jan 2019 23:57:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Sun, 06 Jan 2019 23:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88715-4-lKrbA1TgF3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00685.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-06
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Did you build binutils for i686-uClibc-linux? If not this is not a bug.
>From gcc-bugs-return-627877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 00:25:04 2019
Return-Path: <gcc-bugs-return-627877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40462 invoked by alias); 7 Jan 2019 00:25: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 40013 invoked by uid 48); 7 Jan 2019 00:24:54 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84436] [8/9 Regression] Missed optimization with switch on enum constants returning the same value
Date: Mon, 07 Jan 2019 00:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84436-4-zRPEN7XeJ3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00686.txt.bz2
Content-length: 2991
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84436
Romain Geissler <romain.geissler at amadeus dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |romain.geissler at amadeus dot com
--- Comment #10 from Romain Geissler <romain.geissler at amadeus dot com> ---
Hi,
FYI, I bisected this revision r265463 to introduce a regression when building
the llvm toolchain.
If you do the following:
- build gcc 9 >= r265463 (including recent revisions from late December)
- build clang 7 or clang 8 svn with this gcc 9 (it will work)
- finally with the resulting clang, build llvm's compiler-rt
then clang itself will ICE. Before r265463 it was not the case, and considering
the nature of the fix (missed optimization) I suspect more a gcc bug rather
than a clang one.
The exact clang failure is:
FAILED: CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o
/workdir/build/final-system/llvm-build/./bin/clang --target=x86_64-1a-linux-gnu
-DVISIBILITY_HIDDEN -O2 -mmmx -msse -msse2 -msse3
-I/workdir/build/final-system/llvm-temporary-static-dependencies/install/include
-I/workdir/build/final-system/llvm-temporary-static-dependencies/install/include/ncursesw
-O3 -DNDEBUG -m64 -std=c11 -fPIC -fno-builtin -fvisibility=hidden
-fomit-frame-pointer -MD -MT CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o
-MF CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o.d -o
CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o -c
/workdir/src/llvm-8.0.0/compiler-rt/lib/builtins/divtc3.c
fatal error: error in backend: Cannot select: 0x1a4b558: ch = fsqrt 0x199e868,
0x1a46e38, FrameIndex:i64<0>
0x1a46e38: f80,ch = CopyFromReg 0x199e868, Register:f80 %0
0x1a46d68: f80 = Register %0
0x1a4bd10: i64 = FrameIndex<0>
In function: __divtc3
clang-8: error: clang frontend command failed with exit code 70 (use -v to see
invocation)
clang version 8.0.0
Target: x86_64-1a-linux-gnu
Thread model: posix
InstalledDir: /workdir/build/final-system/llvm-build/./bin
clang-8: note: diagnostic msg: PLEASE submit a bug report to
https://bugs.llvm.org/ and include the crash backtrace, preprocessed source,
and associated run script.
clang-8: note: diagnostic msg:
********************
PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-8: note: diagnostic msg: /tmp/divtc3-106b93.c
clang-8: note: diagnostic msg: /tmp/divtc3-106b93.sh
clang-8: note: diagnostic msg:
Note: step 2 and 3 (build clang then build compiler-rt with the resulting
clang) is done automatically when bootstrapping a 2-stage PGO clang using this
cmake configuration:
https://github.com/llvm-mirror/clang/blob/master/cmake/caches/PGO.cmake
I don't know how to help more in investigating this regression. If I can do
something, please ask.
Cheers,
Romain
>From gcc-bugs-return-627878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 00:26:49 2019
Return-Path: <gcc-bugs-return-627878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42434 invoked by alias); 7 Jan 2019 00:26:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42343 invoked by uid 48); 7 Jan 2019 00:26:45 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Mon, 07 Jan 2019 00:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88713-4-QuiXOEBnam@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00687.txt.bz2
Content-length: 2134
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #12 from Chris Elrod <elrodc at gmail dot com> ---
Created attachment 45363
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45363&action=edit
Fortran program for running benchmarks.
Okay, thank you.
I attached a Fortran program you can run to benchmark the code.
It randomly generates valid inputs, and then times running the code 10^5 times.
Finally, it reports the average time in microseconds.
The SIMD times are the vectorized version, and the transposed times are the
non-vectorized versions. In both cases, Flang produces much faster code.
The results seem in line with what I got benchmarking shared libraries from
Julia.
I linked rt for access to the high resolution clock.
$ gfortran -Ofast -lrt -march=native -mprefer-vector-width=512
vectorization_tests.F90 -o gfortvectests
$ time ./gfortvectests
Transpose benchmark completed in 22.7799759
SIMD benchmark completed in 1.34003162
All are equal: F
All are approximately equal: F
Maximum relative error 8.27204276E-05
First record X: 1.02466011 -0.689792156 -0.404027045
First record Xt: 1.02465975 -0.689791918 -0.404026985
Second record X: -0.546353579 3.37308086E-03 1.15257287
Second record Xt: -0.546353400 3.37312138E-03 1.15257275
real 0m2.418s
user 0m2.412s
sys 0m0.003s
$ flang -Ofast -lrt -march=native -mprefer-vector-width=512
vectorization_tests.F90 -o flangvectests
$ time ./flangvectests
Transpose benchmark completed in 7.232568
SIMD benchmark completed in 0.6596010
All are equal: F
All are approximately equal: F
Maximum relative error 2.0917827E-04
First record X: 0.5867542 1.568364 0.1006735
First record Xt: 0.5867541 1.568363 0.1006735
Second record X: 0.2894785 -0.1510675 -9.3419194E-02
Second record Xt: 0.2894785 -0.1510675 -9.3419187E-02
real 0m0.801s
user 0m0.794s
sys 0m0.005s
>From gcc-bugs-return-627879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 01:46:57 2019
Return-Path: <gcc-bugs-return-627879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65886 invoked by alias); 7 Jan 2019 01:46: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 65847 invoked by uid 48); 7 Jan 2019 01:46:52 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88730] New: gcc generates wrong debug information at -Og
Date: Mon, 07 Jan 2019 01:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88730-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00688.txt.bz2
Content-length: 1691
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88730
Bug ID: 88730
Summary: gcc generates wrong debug information at -Og
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: qrzhang at gatech dot edu
Target Milestone: ---
Unlike PR88686, it happens at -Og.
The correct value of j should be 5. At "-Og", gdb prints "j = 2" incorrectly.
$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-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 20190106 (experimental) [trunk revision 267609] (GCC)
$ gcc-trunk -g abc.c outer.c
$ gdb-trunk -x cmds -batch a.out
Breakpoint 1 at 0x400507: file abc.c, line 11.
0
Breakpoint 1, main () at abc.c:11
11 optimize_me_not();
$1 = 5
$ gcc-trunk -g -Og abc.c outer.c
$ gdb-trunk -x cmds -batch a.out
Breakpoint 1 at 0x4004e4: file abc.c, line 11.
0
Breakpoint 1, main () at abc.c:11
11 optimize_me_not();
$1 = 2
=============== files to reproduce ============
$ cat abc.c
int a;
int main() {
int b, j;
b = 0;
for (; b < 1; b++) {
j = 0;
for (; j < 5; j++)
;
}
printf("%X\n", a);
optimize_me_not();
}
$ cat outer.c
optimize_me_not(){}
$ cat cmds
b 11
r
p j
kill
q
>From gcc-bugs-return-627880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 01:49:57 2019
Return-Path: <gcc-bugs-return-627880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69644 invoked by alias); 7 Jan 2019 01:49:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67963 invoked by uid 48); 7 Jan 2019 01:49:43 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88730] gcc generates wrong debug information at -Og
Date: Mon, 07 Jan 2019 01:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88730-4-jP1B902lAD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88730-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88730-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00689.txt.bz2
Content-length: 156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88730
--- Comment #1 from Qirun Zhang <qrzhang at gatech dot edu> ---
It appears to be a regression in 8.X.
>From gcc-bugs-return-627881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 02:31:19 2019
Return-Path: <gcc-bugs-return-627881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53511 invoked by alias); 7 Jan 2019 02:31:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52783 invoked by uid 48); 7 Jan 2019 02:30:27 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Mon, 07 Jan 2019 02: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88713-4-rugCb0W3kb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00690.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #13 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I noticed the Maximum Relative error in your benchmarks is significantly larger
in the flang test vs the gfortran test. Is this a factor that matters?
>From gcc-bugs-return-627882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 03:35:23 2019
Return-Path: <gcc-bugs-return-627882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100897 invoked by alias); 7 Jan 2019 03:35: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 100687 invoked by uid 48); 7 Jan 2019 03:35:03 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88731] New: Rejects well-formed program using bit-fields in _Generic.
Date: Mon, 07 Jan 2019 03:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00691.txt.bz2
Content-length: 1078
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88731
Bug ID: 88731
Summary: Rejects well-formed program using bit-fields in
_Generic.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
int main()
{
struct S { unsigned x:4; } s;
_Generic(s.x, unsigned: 0);
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
The following error message is outputed:
error: '_Generic' selector of type 'unsigned char:4' is not compatible
with any association
Expected behaviour:
No error message outputed.
See http://www.open-std.org/Jtc1/sc22/wg14/www/docs/summary.htm#dr_481:
"... It was noted that bitfields are of integer type. ..."
Note:
Clang accepts the program without any error message.
>From gcc-bugs-return-627883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 04:07:15 2019
Return-Path: <gcc-bugs-return-627883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17507 invoked by alias); 7 Jan 2019 04:07:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17449 invoked by uid 48); 7 Jan 2019 04:07:09 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Mon, 07 Jan 2019 04:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88713-4-AE5oSwtUcA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00692.txt.bz2
Content-length: 4911
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #14 from Chris Elrod <elrodc at gmail dot com> ---
It's not really reproducible across runs:
$ time ./gfortvectests
Transpose benchmark completed in 22.7010765
SIMD benchmark completed in 1.37529969
All are equal: F
All are approximately equal: F
Maximum relative error 6.20566949E-04
First record X: 0.188879877 0.377619117 -1.67841911E-02
First record Xt: 0.188880071 0.377619147 -1.67841911E-02
Second record X: -8.14126506E-02 -0.421755224 -0.199057430
Second record Xt: -8.14126655E-02 -0.421755224 -0.199057430
real 0m2.414s
user 0m2.406s
sys 0m0.005s
$ time ./flangvectests
Transpose benchmark completed in 7.630980
SIMD benchmark completed in 0.6455200
All are equal: F
All are approximately equal: F
Maximum relative error 2.0917827E-04
First record X: 0.5867542 1.568364 0.1006735
First record Xt: 0.5867541 1.568363 0.1006735
Second record X: 0.2894785 -0.1510675 -9.3419194E-02
Second record Xt: 0.2894785 -0.1510675 -9.3419187E-02
real 0m0.839s
user 0m0.832s
sys 0m0.006s
$ time ./gfortvectests
Transpose benchmark completed in 22.0195961
SIMD benchmark completed in 1.36087596
All are equal: F
All are approximately equal: F
Maximum relative error 2.49150675E-04
First record X: -0.284217566 2.13768221E-02 -0.475293010
First record Xt: -0.284217596 2.13767942E-02 -0.475293040
Second record X: 1.75664220E-02 -9.29893106E-02 -4.37139049E-02
Second record Xt: 1.75664220E-02 -9.29893106E-02 -4.37139049E-02
real 0m2.344s
user 0m2.338s
sys 0m0.003s
$ time ./flangvectests
Transpose benchmark completed in 7.881181
SIMD benchmark completed in 0.6132510
All are equal: F
All are approximately equal: F
Maximum relative error 2.0917827E-04
First record X: 0.5867542 1.568364 0.1006735
First record Xt: 0.5867541 1.568363 0.1006735
Second record X: 0.2894785 -0.1510675 -9.3419194E-02
Second record Xt: 0.2894785 -0.1510675 -9.3419187E-02
real 0m0.861s
user 0m0.853s
sys 0m0.006s
It's also probably wasn't quite right to call it "error", because it's
comparing the values from the scalar and vectorized versions. Although it is
unsettling if the differences are high; there should be an exact match,
ideally.
Back to Julia, using mpfr (set to 252 bits of precision), and rounding to
single precision for an exactly rounded answer...
X32gfort # calculated from gfortran
X32flang # calculated from flang
Xbf # mpfr, 252-bit precision ("BigFloat" in Julia)
julia> Xbf32 = Float32.(Xbf) # correctly rounded result
julia> function ULP(x, correct) # calculates ULP error
x == correct && return 0
if x < correct
error = 1
while nextfloat(x, error) != correct
error += 1
end
else
error = 1
while prevfloat(x, error) != correct
error += 1
end
end
error
end
ULP (generic function with 1 method)
julia> ULP.(X32gfort, Xbf32)'
3×1024 Adjoint{Int64,Array{Int64,2}}:
7 1 1 8 3 2 1 1 1 27 4 1 4 6 0 0 2 0 2 4 0 7 1 1 3 8
4 2 2 … 1 0 2 0 0 1 2 3 1 5 1 1 0 0 0 2 3 2 1 2 3 1 0
1 1 0 2 0 41
4 2 1 1 6 1 0 1 1 2 2 0 0 3 0 1 0 3 1 1 0 1 1 0 0 3
1 0 0 0 1 0 1 0 1 0 1 1 4 1 1 0 2 0 1 0 1 0 0 0 1 2
1 1 1 0 0 1
1 1 0 1 1 0 0 0 0 1 1 0 0 1 0 1 1 1 0 1 1 0 0 1 0 1
0 0 0 0 0 1 0 0 0 0 0 1 0 0 1 1 1 0 0 1 0 1 1 0 1 1
0 0 0 0 0 1
julia> mean(ans)
1.9462890625
julia> ULP.(X32flang, Xbf32)'
3×1024 Adjoint{Int64,Array{Int64,2}}:
4 1 0 3 0 0 0 1 1 5 2 1 1 6 3 0 1 0 0 1 1 21 0 1 2 8
2 3 0 0 … 1 1 1 15 2 1 1 5 1 1 1 0 0 0 0 0 2 1 3 1 1
1 1 1 1 1 0 11
3 1 1 0 1 0 0 1 0 0 1 0 0 2 1 1 1 6 0 0 0 2 1 0 1 4
1 1 0 3 1 1 1 1 2 1 1 0 1 1 0 0 1 0 1 0 0 1 0 0 1
1 1 0 1 0 0 0
1 0 1 0 0 0 1 1 0 1 0 0 0 1 1 0 0 1 1 0 1 1 0 1 0 1
0 0 1 0 0 0 1 0 0 0 0 0 0 2 0 0 0 0 0 1 1 1 1 0 1
0 0 0 0 0 0 1
julia> mean(ans)
1.3388671875
So in that case, gfortran's version had about 1.95 ULP error on average, and
Flang about 1.34 ULP error.
>From gcc-bugs-return-627884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 04:10:30 2019
Return-Path: <gcc-bugs-return-627884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20206 invoked by alias); 7 Jan 2019 04:10: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 20129 invoked by uid 48); 7 Jan 2019 04:10:25 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88731] [DR 481] Rejects well-formed program using bit-fields in _Generic.
Date: Mon, 07 Jan 2019 04: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: 9.0
X-Bugzilla-Keywords: rejects-valid
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-88731-4-uiKn6cVP01@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00693.txt.bz2
Content-length: 203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88731
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It is a TC rather than a DR which means it is not part of C11 but the next one.
>From gcc-bugs-return-627885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 05:37:54 2019
Return-Path: <gcc-bugs-return-627885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28406 invoked by alias); 7 Jan 2019 05:37:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28333 invoked by uid 55); 7 Jan 2019 05:37:32 -0000
From: "andi at firstfloor dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/66229] LTO fails with -fauto-profile on mcf
Date: Mon, 07 Jan 2019 05:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andi at firstfloor dot org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66229-4-hweEYofore@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00694.txt.bz2
Content-length: 342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66229
--- Comment #4 from andi at firstfloor dot org ---
Did some testing. Previously pretty much everything I tried failed.
I don't have mcf, but git, less, gcc LTO+autofdo bootstrap all appear to work
now.
So it's likely fixed.
Would be good if someone could confirm with the actual mcf.
>From gcc-bugs-return-627886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 05:40:54 2019
Return-Path: <gcc-bugs-return-627886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31772 invoked by alias); 7 Jan 2019 05:40:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31752 invoked by uid 48); 7 Jan 2019 05:40:48 -0000
From: "tomsies at mighty dot co.za" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Mon, 07 Jan 2019 05:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tomsies at mighty dot co.za
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-88715-4-KaeGBTCnD7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00695.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
--- Comment #2 from tomsies at mighty dot co.za ---
Actually binutils-2.29 (along with gmp-6.1.0, mpc-1.0.3 and mpfr-3.1.4) are
symlinked into the gcc source tree. So they should be built as part of the
compile.
My assumption is that the as script generated during the compile process is
there to pick up the relevant assembler at different stages of the compile, and
so this is a bug, because whatever assembler it is trying to exec will fail
with "as: 106: exec: --32: not found" because the exec string is not quoted?
>From gcc-bugs-return-627887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 05:50:21 2019
Return-Path: <gcc-bugs-return-627887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40430 invoked by alias); 7 Jan 2019 05:50: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 40332 invoked by uid 48); 7 Jan 2019 05:50:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Mon, 07 Jan 2019 05:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-88715-4-8ojl9OhjSO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00696.txt.bz2
Content-length: 471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you attach the full log? And also attach config.log in the top level
directory?
> Actually binutils-2.29 ... are symlinked into the gcc source tree.
How did you do the symlink here? Is it a symlink just to the binutils source
directory or symlinks to the files in the binutils source directories?
A combined tree requires a "merged" tree.
>From gcc-bugs-return-627888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 06:01:22 2019
Return-Path: <gcc-bugs-return-627888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48219 invoked by alias); 7 Jan 2019 06:01:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47920 invoked by uid 48); 7 Jan 2019 06:01:01 -0000
From: "amocywang at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88732] New: different results on -O0 and -O1, -O2, -O3, -Os
Date: Mon, 07 Jan 2019 06:01: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: amocywang 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-88732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00697.txt.bz2
Content-length: 2127
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88732
Bug ID: 88732
Summary: different results on -O0 and -O1, -O2, -O3, -Os
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: amocywang at gmail dot com
Target Milestone: ---
> $ gcc -v
Using built-in specs.
COLLECT_GCC=/home/wgc/installs/gcc_trunks/trunk_r267598/bin/gcc
COLLECT_LTO_WRAPPER=/home/wgc/installs/gcc_trunks/trunk_r267598/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ./configure LDFLAGS=-Wl,--no-as-needed
--prefix=/home/wgc/installs/gcc_trunks/trunk_r267598
--with-gmp=/home/wgc/installs/gmp-6.1.2
--with-mpfr=/home/wgc/installs/mpfr-4.0.1
--with-mpc=/home/wgc/installs/mpc-1.1.0 --with-isl= --with-cloog=
--enable-languages=c,c++ --disable-multilib --disable-bootstrap
Thread model: posix
gcc version 9.0.0 20190105 (experimental) (GCC)
$ gcc -O0 program.c
$ ./a.out
63
$ gcc -O1 program.c
$ ./a.out
64
$ gcc -O2 program.c
$ ./a.out
64
$ gcc -O3 program.c
$ ./a.out
64
$ gcc -Os program.c
$ ./a.out
64
$ cat program.c
static int a, b;
unsigned short int c() {
b = __builtin_clzl(a);
return a;
}
int main() {
c();
printf("%d\n", b);
return 0;
}
I have validated this difference with the command line option
"-fno-strict-aliasing -fwrapv" and the results are different on different
optimizing options, same with the results above. It seems the test program is
correct.
>From gcc-bugs-return-627889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 06:18:40 2019
Return-Path: <gcc-bugs-return-627889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87216 invoked by alias); 7 Jan 2019 06:18:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87161 invoked by uid 48); 7 Jan 2019 06:18:35 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88732] different results on -O0 and -O1, -O2, -O3, -Os
Date: Mon, 07 Jan 2019 06:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
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-88732-4-2WnXb8zOuH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00698.txt.bz2
Content-length: 206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88732
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
Why not read the documentation for that function?
"If x is 0, the result is undefined."
>From gcc-bugs-return-627890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 06:29:53 2019
Return-Path: <gcc-bugs-return-627890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95241 invoked by alias); 7 Jan 2019 06:29: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 95192 invoked by uid 48); 7 Jan 2019 06:29:46 -0000
From: "amocywang at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88732] different results on -O0 and -O1, -O2, -O3, -Os
Date: Mon, 07 Jan 2019 06:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amocywang at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88732-4-MML49lvWJd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00699.txt.bz2
Content-length: 388
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88732
--- Comment #2 from Amos Wang <amocywang at gmail dot com> ---
(In reply to Marc Glisse from comment #1)
> Why not read the documentation for that function?
> "If x is 0, the result is undefined."
Why the results are different at different optimizing optionss? If it's an
undefined behaviour, I think all results should be the same.
>From gcc-bugs-return-627891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 06:31:51 2019
Return-Path: <gcc-bugs-return-627891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97750 invoked by alias); 7 Jan 2019 06:31:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97698 invoked by uid 48); 7 Jan 2019 06:31:46 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88732] different results on -O0 and -O1, -O2, -O3, -Os
Date: Mon, 07 Jan 2019 06:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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-88732-4-GC0BRrLqdu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00700.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88732
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Amos Wang from comment #2)
> (In reply to Marc Glisse from comment #1)
> > Why not read the documentation for that function?
> > "If x is 0, the result is undefined."
>
> Why the results are different at different optimizing optionss? If it's an
> undefined behaviour, I think all results should be the same.
undefined behavior means that the value could be different at different times.
>From gcc-bugs-return-627892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 06:40:29 2019
Return-Path: <gcc-bugs-return-627892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103585 invoked by alias); 7 Jan 2019 06:40:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103532 invoked by uid 48); 7 Jan 2019 06:40:24 -0000
From: "tomsies at mighty dot co.za" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Mon, 07 Jan 2019 06:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tomsies at mighty dot co.za
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-88715-4-rnypWeSGhM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00701.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
--- Comment #4 from DirkInSA <tomsies at mighty dot co.za> ---
Symlink was a simply the whole binutils source directory into gcc source
directory.
I was not aware that each of bfd, binutils, config, cpu & etc needed to be
linked (I assume) into the base gcc directory - will have a go at that and see
what happens.
Is the issue here that the variable as is empty, and so exec is trying to exec
--32 ... instead of as --32 ...?
>From gcc-bugs-return-627893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 06:42:49 2019
Return-Path: <gcc-bugs-return-627893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117695 invoked by alias); 7 Jan 2019 06:42:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117596 invoked by uid 48); 7 Jan 2019 06:42:45 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Mon, 07 Jan 2019 06:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-88715-4-kWVBIudjzn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00702.txt.bz2
Content-length: 318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
https://raghunathlolur.wordpress.com/2014/06/30/combined-tree-build-of-gcc-binutils-and-libraries/
https://stackoverflow.com/questions/1726042/recipe-for-compiling-binutils-gcc-together
etc.
>From gcc-bugs-return-627894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:09:10 2019
Return-Path: <gcc-bugs-return-627894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3056 invoked by alias); 7 Jan 2019 07:09: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 3003 invoked by uid 48); 7 Jan 2019 07:09:05 -0000
From: "tomsies at mighty dot co.za" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88715] Cross Compile on Debian Linux to create a uClibc tool chain GCC fails to compile
Date: Mon, 07 Jan 2019 07: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tomsies at mighty dot co.za
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88715-4-kja2kAjLpL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00703.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88715
DirkInSA <tomsies at mighty dot co.za> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from DirkInSA <tomsies at mighty dot co.za> ---
Thanks, was just on the stack overflow thread that you kindly posted.
Will close this bug!
>From gcc-bugs-return-627895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:32:00 2019
Return-Path: <gcc-bugs-return-627895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64020 invoked by alias); 7 Jan 2019 07:31: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 63554 invoked by uid 55); 7 Jan 2019 07:31:54 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88521] gcc 9.0 from r266355 miscompile x265 for mingw-w64 target
Date: Mon, 07 Jan 2019 07:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88521-4-RZgzRPf47z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00704.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88521
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Mon Jan 7 07:31:19 2019
New Revision: 267622
URL: https://gcc.gnu.org/viewcvs?rev=267622&root=gcc&view=rev
Log:
PR target/88521
* config/i386/i386.c (function_value_ms_64): Return small sturct in
AX_REG and float/double in FIRST_SSE_REG for 4 or 8 byte modes.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr88521.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:32:36 2019
Return-Path: <gcc-bugs-return-627896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65176 invoked by alias); 7 Jan 2019 07:32: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 65115 invoked by uid 48); 7 Jan 2019 07:32:32 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Mon, 07 Jan 2019 07:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88717-4-uoMpEAkYGX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00705.txt.bz2
Content-length: 1003
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
--- Comment #1 from åˆ˜è¢‹é¼ <crazylht at gmail dot com> ---
Pass_insert_vzeroupper uses mode_switch to insert `vzeroupper`.
In function entry and functon body, 256bits/512bits registers are used ,so it
will set mode as `AVX_U128_DIRTY`. But for function exit no 256bits/512bits
register is returned, so `AVX_U128_CLEAN` is set.
Then `case AVX_U128_CLEAN` will be triggered for mode switching, maybe we
should handle ix86_avx_u128_mode_exit.
Simple case show vzeroupper disappear when return a 512bits register.
```
test.i:
----------------------------
typedef float __v16sf __attribute__ ((__vector_size__ (64)));
typedef float __m512 __attribute__ ((__vector_size__ (64), __may_alias__));
__m512
foo (float *p, __m512 x)
{
*p = ((__v16sf)x)[0];
return x;
}
test.s
----------------------------------
foo:
.LFB0:
.cfi_startproc
vmovss %xmm0, (%rdi)
ret
.cfi_endproc
.LFE0:
```
>From gcc-bugs-return-627897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:34:29 2019
Return-Path: <gcc-bugs-return-627897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67592 invoked by alias); 7 Jan 2019 07:34: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 67523 invoked by uid 48); 7 Jan 2019 07:34:24 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] [9 Regression] scan-ipa-dump inline "Inlined tp_sum/
Date: Mon, 07 Jan 2019 07:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88711-4-eF7tBMopoq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00706.txt.bz2
Content-length: 385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
>From gcc-bugs-return-627898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:40:56 2019
Return-Path: <gcc-bugs-return-627898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75227 invoked by alias); 7 Jan 2019 07:40:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75125 invoked by uid 48); 7 Jan 2019 07:40:51 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84436] [8/9 Regression] Missed optimization with switch on enum constants returning the same value
Date: Mon, 07 Jan 2019 07:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84436-4-ng0v0D4cCt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00707.txt.bz2
Content-length: 2972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84436
--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Romain Geissler from comment #10)
> Hi,
>
> FYI, I bisected this revision r265463 to introduce a regression when
> building the llvm toolchain.
>
> If you do the following:
> - build gcc 9 >= r265463 (including recent revisions from late December)
> - build clang 7 or clang 8 svn with this gcc 9 (it will work)
> - finally with the resulting clang, build llvm's compiler-rt
>
> then clang itself will ICE. Before r265463 it was not the case, and
> considering the nature of the fix (missed optimization) I suspect more a gcc
> bug rather than a clang one.
>
> The exact clang failure is:
> FAILED: CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o
> /workdir/build/final-system/llvm-build/./bin/clang
> --target=x86_64-1a-linux-gnu -DVISIBILITY_HIDDEN -O2 -mmmx -msse -msse2
> -msse3
> -I/workdir/build/final-system/llvm-temporary-static-dependencies/install/
> include
> -I/workdir/build/final-system/llvm-temporary-static-dependencies/install/
> include/ncursesw -O3 -DNDEBUG -m64 -std=c11 -fPIC -fno-builtin
> -fvisibility=hidden -fomit-frame-pointer -MD -MT
> CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o -MF
> CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o.d -o
> CMakeFiles/clang_rt.builtins-x86_64.dir/divtc3.c.o -c
> /workdir/src/llvm-8.0.0/compiler-rt/lib/builtins/divtc3.c
> fatal error: error in backend: Cannot select: 0x1a4b558: ch = fsqrt
> 0x199e868, 0x1a46e38, FrameIndex:i64<0>
> 0x1a46e38: f80,ch = CopyFromReg 0x199e868, Register:f80 %0
> 0x1a46d68: f80 = Register %0
> 0x1a4bd10: i64 = FrameIndex<0>
> In function: __divtc3
> clang-8: error: clang frontend command failed with exit code 70 (use -v to
> see invocation)
> clang version 8.0.0
> Target: x86_64-1a-linux-gnu
> Thread model: posix
> InstalledDir: /workdir/build/final-system/llvm-build/./bin
> clang-8: note: diagnostic msg: PLEASE submit a bug report to
> https://bugs.llvm.org/ and include the crash backtrace, preprocessed source,
> and associated run script.
> clang-8: note: diagnostic msg:
> ********************
>
> PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
> Preprocessed source(s) and associated run script(s) are located at:
> clang-8: note: diagnostic msg: /tmp/divtc3-106b93.c
> clang-8: note: diagnostic msg: /tmp/divtc3-106b93.sh
> clang-8: note: diagnostic msg:
>
> Note: step 2 and 3 (build clang then build compiler-rt with the resulting
> clang) is done automatically when bootstrapping a 2-stage PGO clang using
> this cmake configuration:
> https://github.com/llvm-mirror/clang/blob/master/cmake/caches/PGO.cmake
>
> I don't know how to help more in investigating this regression. If I can do
> something, please ask.
>
> Cheers,
> Romain
Thank you for the report. Can you please provide exact steps how to build the
llvm/clang?
>From gcc-bugs-return-627899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:51:54 2019
Return-Path: <gcc-bugs-return-627899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67616 invoked by alias); 7 Jan 2019 07: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 67543 invoked by uid 48); 7 Jan 2019 07:51:46 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Mon, 07 Jan 2019 07:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87957-4-y7riEi9cac@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00708.txt.bz2
Content-length: 1183
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
--- Comment #24 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I am not sure how to get command line for debugger but I assume that it does
> not simplify type name because type_with_linkage_p returns true which is
> wrong for Ada types (it tests whether it is C++ ODR type).
Run the gnat.dg testsuite and copy-and-paste the command line from the log file
without the -q option in the middle. You'll get:
/home/eric/build/gcc/native/gcc/xgcc -c
-I/home/eric/svn/gcc/gcc/testsuite/gnat.dg/ -B/home/eric/build/gcc/native/gcc
--RTS=/home/eric/build/gcc/native/x86_64-suse-linux/./libada
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -gnatws -flto -lm -I-
/home/eric/svn/gcc/gcc/testsuite/gnat.dg/lto8.adb
+===========================GNAT BUG DETECTED==============================+
| 9.0.0 20190104 (experimental) [trunk revision 267574] (x86_64-suse-linux) GCC
error:|
| in fld_incomplete_type_of, at tree.c:5348 |
>From gcc-bugs-return-627900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:52:15 2019
Return-Path: <gcc-bugs-return-627900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68462 invoked by alias); 7 Jan 2019 07:52: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 68392 invoked by uid 48); 7 Jan 2019 07:52:10 -0000
From: "andriusspamtest at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88331] [9 Regression] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Mon, 07 Jan 2019 07:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andriusspamtest 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88331-4-Rmf6XqEUpQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00709.txt.bz2
Content-length: 4113
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
Andrius Burokas <andriusspamtest at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andriusspamtest at gmail dot com
--- Comment #12 from Andrius Burokas <andriusspamtest at gmail dot com> ---
While trying to compile GCC trunk (commit
cea12873eeeaa7952e315626991b2e162218e134, Thu Dec 27 16:31:50 2018 +0000) on
Cygwin (CYGWIN_NT-10.0 LT04LT1279HR2 2.11.2(0.329/5/3) 2018-11-08 14:34 x86_64
Cygwin) got an ICE similar to one reported by Rainer
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331#c6)
==================================
configure parameters before 'make'
==================================
andbur@LT04LT1279HR2 ~/gcc
$ ./../gcc_source/configure --build=x86_64-pc-cygwin --host=x86_64-pc-cygwin
--target=x86_64-pc-cygwin --without-libiconv-prefix --without-libintl-prefix
--enable-shared --enable-shared-libgcc --enable-static
--enable-version-specific-runtime-libs --enable-bootstrap --enable-__cxa_atexit
--with-dwarf2 --with-tune=generic
--enable-languages=c,c++,fortran,lto,objc,obj-c++ --enable-graphite
--enable-threads=posix --enable-libatomic --enable-libcilkrts --enable-libgomp
--enable-libitm --enable-libquadmath --enable-libquadmath-support
--disable-libssp --enable-libada --disable-symvers --with-gnu-ld --with-gnu-as
--without-libiconv-prefix --without-libintl-prefix --with-system-zlib
--enable-linker-build-id --with-default-libstdcxx-abi=gcc4-compatible
--enable-libstdcxx-filesystem-ts
--with-cloog-include=/usr/local/include/cloog-isl --enable-lto
--enable-checking=release
==========================================
Last few lines where the compilation broke
==========================================
libtool: compile: /home/andbur/gcc/./gcc/xgcc -B/home/andbur/gcc/./gcc/
-B/usr/local/x86_64-pc-cygwin/bin/ -B/usr/local/x86_64-pc-cygwin/lib/ -isystem
/usr/local/x86_64-pc-cygwin/include -isystem
/usr/local/x86_64-pc-cygwin/sys-include -fno-checking -DHAVE_CONFIG_H -I.
-I../.././../gcc_source/libgfortran -iquote../.././../gcc_source/libgfortran/io
-I../.././../gcc_source/libgfortran/../gcc
-I../.././../gcc_source/libgfortran/../gcc/config
-I../.././../gcc_source/libgfortran/../libquadmath -I../.././gcc
-I../.././../gcc_source/libgfortran/../libgcc -I../libgcc
-I../.././../gcc_source/libgfortran/../libbacktrace -I../libbacktrace
-I../libbacktrace -std=gnu11 -Wall -Wstrict-prototypes -Wmissing-prototypes
-Wold-style-definition -Wextra -Wwrite-strings
-Werror=implicit-function-declaration -Werror=vla -fcx-fortran-rules
-ffunction-sections -fdata-sections -ffast-math -ftree-vectorize -funroll-loops
--param max-unroll-times=4 -g -O2 -MT matmul_i4.lo -MD -MP -MF
.deps/matmul_i4.Tpo -c ../.././../gcc_source/libgfortran/generated/matmul_i4.c
-DDLL_EXPORT -DPIC -o .libs/matmul_i4.o
during RTL pass: postreload
../.././../gcc_source/libgfortran/generated/matmul_i4.c: In function
‘matmul_i4_avx2’:
../.././../gcc_source/libgfortran/generated/matmul_i4.c:1210:1: internal
compiler error: in reload_combine_note_use, at postreload.c:1547
1210 | }
| ^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
make[3]: *** [Makefile:4194: matmul_i4.lo] Error 1
make[3]: Leaving directory '/home/andbur/gcc/x86_64-pc-cygwin/libgfortran'
make[2]: *** [Makefile:1562: all] Error 2
make[2]: Leaving directory '/home/andbur/gcc/x86_64-pc-cygwin/libgfortran'
make[1]: *** [Makefile:18695: all-target-libgfortran] Error 2
make[1]: Leaving directory '/home/andbur/gcc'
make: *** [Makefile:988: all] Error 2
>From gcc-bugs-return-627901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 07:56:00 2019
Return-Path: <gcc-bugs-return-627901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102700 invoked by alias); 7 Jan 2019 07:56: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 100576 invoked by uid 48); 7 Jan 2019 07:55:56 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Mon, 07 Jan 2019 07:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87957-4-NOHFQvEGkw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00710.txt.bz2
Content-length: 281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
--- Comment #25 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Or, alternatively, from the top-level build directory where you have copied the
gnat.dg/lto8* files, just: gcc/xgcc -Bgcc -S lto8.adb -flto -I gcc/ada/rts
>From gcc-bugs-return-627902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:01:19 2019
Return-Path: <gcc-bugs-return-627902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107289 invoked by alias); 7 Jan 2019 08:01:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106983 invoked by uid 48); 7 Jan 2019 08:01:14 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Mon, 07 Jan 2019 08:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88721-4-7qTkVjPGwt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00711.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Two false positives I think.
>From gcc-bugs-return-627903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:05:50 2019
Return-Path: <gcc-bugs-return-627903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110644 invoked by alias); 7 Jan 2019 08:05:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110580 invoked by uid 48); 7 Jan 2019 08:05:46 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Mon, 07 Jan 2019 08:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88721-4-ltmgX1XruK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00712.txt.bz2
Content-length: 563
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> This patch allowed the bootstrap to finish.
There are 3 callers of function_arg_slotno so we would potentially need to add
6 initializations already. So I'd rather initialize pregno and ppadding at the
beginning of the function if this works:
enum mode_class mclass = GET_MODE_CLASS (mode);
/* Silence warnings in the callers. */
*pregno = -1;
*ppadding = -1;
if (type && TREE_ADDRESSABLE (type))
return -1;
>From gcc-bugs-return-627904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:09:50 2019
Return-Path: <gcc-bugs-return-627904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115537 invoked by alias); 7 Jan 2019 08:09:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115342 invoked by uid 48); 7 Jan 2019 08:09:46 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 08:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88723-4-wVu0Kf4imn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00713.txt.bz2
Content-length: 405
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
>From gcc-bugs-return-627905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:11:33 2019
Return-Path: <gcc-bugs-return-627905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11161 invoked by alias); 7 Jan 2019 08:11:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11099 invoked by uid 55); 7 Jan 2019 08:11:29 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128
Date: Mon, 07 Jan 2019 08:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85381-4-smqoYqbSvH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85381-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85381-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00714.txt.bz2
Content-length: 1188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Mon Jan 7 08:10:56 2019
New Revision: 267630
URL: https://gcc.gnu.org/viewcvs?rev=267630&root=gcc&view=rev
Log:
[nvptx] Don't emit barriers for empty loops -- fix
When compiling an empty loop:
...
long long v1;
#pragma acc parallel num_gangs (640) num_workers(1) vector_length (128)
#pragma acc loop
for (v1 = 0; v1 < 20; v1 += 2)
;
...
the compiler emits two subsequent bar.syncs. This triggers some bug on my
quadro m1200 (I'm assuming in the ptxas/JIT compiler) that hangs the testcase.
This patch works around the bug by doing an optimization: we detect that this
is
an empty loop (a forked immediately followed by a joining), and don't emit the
barriers.
The patch does not include the test-case yet, since vector_length (128) is not
yet supported at this point.
2019-01-07 Tom de Vries <tdevries@suse.de>
PR target/85381
* config/nvptx/nvptx.c (nvptx_process_pars): Don't emit barriers for
empty loops.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/nvptx/nvptx.c
>From gcc-bugs-return-627906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:46:36 2019
Return-Path: <gcc-bugs-return-627906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19010 invoked by alias); 7 Jan 2019 08:46:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18959 invoked by uid 48); 7 Jan 2019 08:46:31 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88700] C11 Annex K builtins
Date: Mon, 07 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88700-4-CSiFWfUV6Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00715.txt.bz2
Content-length: 377
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88700
--- Comment #4 from Jonny Grant <jg at jguk dot org> ---
Ok I see, thank you for the links. Yes, I would support amending/fixing for any
issues.
There are lots of APIs that have evolved. eg creat() still present, but I
wouldn't use it as there are better alternatives. So I would be happy to see
safer string functions.
>From gcc-bugs-return-627907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:47:48 2019
Return-Path: <gcc-bugs-return-627907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20206 invoked by alias); 7 Jan 2019 08:47:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20124 invoked by uid 48); 7 Jan 2019 08:47:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Mon, 07 Jan 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88398-4-5RYooOFTh1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00716.txt.bz2
Content-length: 940
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think the only chance would be for FDO to flag the loop as hot plus assign
it a reasonably low expected niter so GCC could consider "fully" peeling it.
But then whether peeling it that situation is profitable depends highly on
the target (that is, the number of peeled copies that might be profitable).
Considering the various forms of pre-decoded yop caches we have in modern
CPUs peeling might do more harm than good (you only get away with the
mispredicted exit jump, plus you add mispredictions of the peeled exits
in case niter fluctuates a lot).
>From gcc-bugs-return-627908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:49:46 2019
Return-Path: <gcc-bugs-return-627908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27664 invoked by alias); 7 Jan 2019 08:49: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 27594 invoked by uid 55); 7 Jan 2019 08:49:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Mon, 07 Jan 2019 08:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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-85052-4-1lKcYFPOTx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00717.txt.bz2
Content-length: 2830
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 7 08:49:08 2019
New Revision: 267632
URL: https://gcc.gnu.org/viewcvs?rev=267632&root=gcc&view=rev
Log:
PR c++/85052
* tree-vect-generic.c: Include insn-config.h and recog.h.
(expand_vector_piecewise): Add defaulted ret_type argument,
if non-NULL, use that in preference to type for the result type.
(expand_vector_parallel): Formatting fix.
(do_vec_conversion, do_vec_narrowing_conversion,
expand_vector_conversion): New functions.
(expand_vector_operations_1): Call expand_vector_conversion
for VEC_CONVERT ifn calls.
* internal-fn.def (VEC_CONVERT): New internal function.
* internal-fn.c (expand_VEC_CONVERT): New function.
* fold-const-call.c (fold_const_vec_convert): New function.
(fold_const_call): Use it for CFN_VEC_CONVERT.
* doc/extend.texi (__builtin_convertvector): Document.
c-family/
* c-common.h (enum rid): Add RID_BUILTIN_CONVERTVECTOR.
(c_build_vec_convert): Declare.
* c-common.c (c_build_vec_convert): New function.
c/
* c-parser.c (c_parser_postfix_expression): Parse
__builtin_convertvector.
cp/
* cp-tree.h (cp_build_vec_convert): Declare.
* parser.c (cp_parser_postfix_expression): Parse
__builtin_convertvector.
* constexpr.c: Include fold-const-call.h.
(cxx_eval_internal_function): Handle IFN_VEC_CONVERT.
(potential_constant_expression_1): Likewise.
* semantics.c (cp_build_vec_convert): New function.
* pt.c (tsubst_copy_and_build): Handle CALL_EXPR to
IFN_VEC_CONVERT.
testsuite/
* c-c++-common/builtin-convertvector-1.c: New test.
* c-c++-common/torture/builtin-convertvector-1.c: New test.
* g++.dg/ext/builtin-convertvector-1.C: New test.
* g++.dg/cpp0x/constexpr-builtin4.C: New test.
Added:
trunk/gcc/testsuite/c-c++-common/builtin-convertvector-1.c
trunk/gcc/testsuite/c-c++-common/torture/builtin-convertvector-1.c
trunk/gcc/testsuite/g++.dg/cpp0x/constexpr-builtin4.C
trunk/gcc/testsuite/g++.dg/ext/builtin-convertvector-1.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-common.c
trunk/gcc/c-family/c-common.h
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-parser.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/constexpr.c
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/parser.c
trunk/gcc/cp/pt.c
trunk/gcc/cp/semantics.c
trunk/gcc/doc/extend.texi
trunk/gcc/fold-const-call.c
trunk/gcc/internal-fn.c
trunk/gcc/internal-fn.def
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-generic.c
>From gcc-bugs-return-627909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:51:33 2019
Return-Path: <gcc-bugs-return-627909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102401 invoked by alias); 7 Jan 2019 08:51:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97087 invoked by uid 55); 7 Jan 2019 08:51:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88619] [9 Regression] ICE in asan_emit_stack_protection, at asan.c:1574 since r266664
Date: Mon, 07 Jan 2019 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88619-4-Cl48Q9JEYq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00718.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88619
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 7 08:50:57 2019
New Revision: 267633
URL: https://gcc.gnu.org/viewcvs?rev=267633&root=gcc&view=rev
Log:
PR sanitizer/88619
* cfgexpand.c (expand_stack_vars): Only align prev_offset to
ASAN_MIN_RED_ZONE_SIZE, not to maximum of that and alignb.
* c-c++-common/asan/pr88619.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/asan/pr88619.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cfgexpand.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-627910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:52:42 2019
Return-Path: <gcc-bugs-return-627910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115955 invoked by alias); 7 Jan 2019 08: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 115845 invoked by uid 55); 7 Jan 2019 08:52:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88676] missed opportunity in integer conditional
Date: Mon, 07 Jan 2019 08:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.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-88676-4-toQPICznGW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00719.txt.bz2
Content-length: 823
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 7 08:51:59 2019
New Revision: 267634
URL: https://gcc.gnu.org/viewcvs?rev=267634&root=gcc&view=rev
Log:
PR tree-optimization/88676
* tree-ssa-phiopt.c (two_value_replacement): New function.
(tree_ssa_phiopt_worker): Call it.
* gcc.dg/tree-ssa/pr88676.c: New test.
* gcc.dg/pr88676.c: New test.
* gcc.dg/tree-ssa/pr15826.c: Just verify there is no goto,
allow &.
Added:
trunk/gcc/testsuite/gcc.dg/pr88676.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr88676.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr15826.c
trunk/gcc/tree-ssa-phiopt.c
>From gcc-bugs-return-627913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:55:31 2019
Return-Path: <gcc-bugs-return-627913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124069 invoked by alias); 7 Jan 2019 08:55:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123840 invoked by uid 48); 7 Jan 2019 08:55:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/87525] [7/8/9 Regression] infinite loop generated for fread() if enabling -flto and -D_FORTIFY_SOURCE=2
Date: Mon, 07 Jan 2019 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-87525-4-kttpOlwe7O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87525-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87525-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00722.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87525
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
>From gcc-bugs-return-627912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:55:22 2019
Return-Path: <gcc-bugs-return-627912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123357 invoked by alias); 7 Jan 2019 08: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 122834 invoked by uid 48); 7 Jan 2019 08:55:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82521] [7/8/9 Regression] No -Wtype-limits warning when using templates
Date: Mon, 07 Jan 2019 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-82521-4-Gte10nRZER@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00721.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82521
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
>From gcc-bugs-return-627911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:55:17 2019
Return-Path: <gcc-bugs-return-627911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122644 invoked by alias); 7 Jan 2019 08:55: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 122566 invoked by uid 48); 7 Jan 2019 08:55:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/51765] [9 Regression] Testsuite ICEs with -flto
Date: Mon, 07 Jan 2019 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-51765-4-eSXl47peKR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00720.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51765
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:56:59 2019
Return-Path: <gcc-bugs-return-627914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127086 invoked by alias); 7 Jan 2019 08:56:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127032 invoked by uid 48); 7 Jan 2019 08:56:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87943] [6 regression] severe regression on iso_varying_string (?)
Date: Mon, 07 Jan 2019 08:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-87943-4-DU8QTG1QsF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87943-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87943-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00723.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87943
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |6.5
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed in GCC 7+, GCC 6 will stay broken.
>From gcc-bugs-return-627917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:57:56 2019
Return-Path: <gcc-bugs-return-627917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129887 invoked by alias); 7 Jan 2019 08:57:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129808 invoked by uid 48); 7 Jan 2019 08:57:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Mon, 07 Jan 2019 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
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-88678-4-Do6v2QzJYq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00726.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:57:03 2019
Return-Path: <gcc-bugs-return-627915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127724 invoked by alias); 7 Jan 2019 08:57: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 127117 invoked by uid 48); 7 Jan 2019 08:56:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88606] [9 Regression] ICE: verify_type failed (error: type variant differs by TYPE_TRANSPARENT_AGGR)
Date: Mon, 07 Jan 2019 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88606-4-ShuvftcO24@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00724.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88606
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:57:21 2019
Return-Path: <gcc-bugs-return-627916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128892 invoked by alias); 7 Jan 2019 08:57:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128841 invoked by uid 48); 7 Jan 2019 08:57:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Mon, 07 Jan 2019 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-88677-4-dPVdZtlWaz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00725.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Target Milestone|--- |9.0
>From gcc-bugs-return-627919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:58:14 2019
Return-Path: <gcc-bugs-return-627919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 730 invoked by alias); 7 Jan 2019 08:58:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 604 invoked by uid 48); 7 Jan 2019 08:58:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88685] [8/9 regression] pointer class array argument indexing
Date: Mon, 07 Jan 2019 08:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
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: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-88685-4-2AA0LOkBQ0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88685-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00728.txt.bz2
Content-length: 348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88685
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |8.2.1
Target Milestone|--- |8.3
>From gcc-bugs-return-627918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:58:05 2019
Return-Path: <gcc-bugs-return-627918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130711 invoked by alias); 7 Jan 2019 08:58: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 130615 invoked by uid 48); 7 Jan 2019 08:58:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88680] [9 Regression] bogus -Wtype-limits for constant expressions after r267272
Date: Mon, 07 Jan 2019 08: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88680-4-yJftRDctDf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88680-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88680-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00727.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88680
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 08:58:17 2019
Return-Path: <gcc-bugs-return-627920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1102 invoked by alias); 7 Jan 2019 08:58:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 645 invoked by uid 48); 7 Jan 2019 08:58:11 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88733] New: [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Mon, 07 Jan 2019 08:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00729.txt.bz2
Content-length: 2228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
Bug ID: 88733
Summary: [9 Regression] ICE in wide_int_to_tree_1, at
tree.c:1561
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
seen with trunk 20190103, extracted from the rna-star package. Both -fopenmp
-flto are needed to see the ICE.
$ cat STAR.ii
class a {
public:
int b;
int c;
};
class e {
public:
long *d;
};
class h {
public:
e *f;
};
long g;
void k() {
a i;
h *j[i.b];
for (;;)
#pragma omp parallel num_threads(i.c)
g = j[0]->f->d[0];
}
$ g++ -std=c++11 -Wno-unused-result -fopenmp -flto -fstack-protector-strong -c
STAR.ii
during IPA pass: *free_lang_data
STAR.ii:21:1: internal compiler error: in wide_int_to_tree_1, at tree.c:1561
21 | }
| ^
0x5ce5ac wide_int_to_tree_1
../../src/gcc/tree.c:1561
0xdbed1b wide_int_to_tree(tree_node*, poly_int<1u,
generic_wide_int<wide_int_ref_storage<false, true> > > const&)
../../src/gcc/tree.c:1686
0xdbed1b build_int_cst(tree_node*, poly_int<1u, long>)
../../src/gcc/tree.c:1355
0x9107d3 round_up_loc(unsigned int, tree_node*, unsigned int)
../../src/gcc/fold-const.c:14374
0xb714f4 finalize_type_size
../../src/gcc/stor-layout.c:1931
0xb72e9b layout_type(tree_node*)
../../src/gcc/stor-layout.c:2596
0xdc02e1 build_array_type_1
../../src/gcc/tree.c:8302
0xdc55f3 fld_process_array_type
../../src/gcc/tree.c:5249
0xdc712a fld_incomplete_type_of
../../src/gcc/tree.c:5303
0xdc7068 fld_incomplete_type_of
../../src/gcc/tree.c:5285
0xdc9334 fld_simplified_type
../../src/gcc/tree.c:5374
0xdc9334 free_lang_data_in_decl
../../src/gcc/tree.c:5746
0xdc9334 free_lang_data_in_cgraph
../../src/gcc/tree.c:6175
0xdc9334 free_lang_data
../../src/gcc/tree.c:6216
0xdc9334 execute
../../src/gcc/tree.c:6288
Please submit a full bug report,
with preprocessed source if appropriate.
>From gcc-bugs-return-627921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:01:04 2019
Return-Path: <gcc-bugs-return-627921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36468 invoked by alias); 7 Jan 2019 09:01:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23439 invoked by uid 48); 7 Jan 2019 09:00:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [7/8/9 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Mon, 07 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords version target_milestone short_desc
Message-ID: <bug-88702-4-4sSJ4FM3nf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00730.txt.bz2
Content-length: 850
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Version|unknown |9.0
Target Milestone|--- |7.5
Summary|[6/7/8 regression] We do |[7/8/9 regression] We do
|terrible job optimizing |terrible job optimizing
|IsHTMLWhitespace from |IsHTMLWhitespace from
|Firefox |Firefox
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
You could also add match.pd rules merging stuff pair-wise...
How's this a regression btw?
>From gcc-bugs-return-627922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:01:05 2019
Return-Path: <gcc-bugs-return-627922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36918 invoked by alias); 7 Jan 2019 09:01:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28447 invoked by uid 48); 7 Jan 2019 09:00:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] [9 Regression] scan-ipa-dump inline "Inlined tp_sum/
Date: Mon, 07 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88711-4-nGLTn2rvQ6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00732.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:01:11 2019
Return-Path: <gcc-bugs-return-627923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37690 invoked by alias); 7 Jan 2019 09:01: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 33437 invoked by uid 48); 7 Jan 2019 09:00:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Mon, 07 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
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-88714-4-A4BwRKQJT0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00731.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:10:25 2019
Return-Path: <gcc-bugs-return-627924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57996 invoked by alias); 7 Jan 2019 09:10: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 57880 invoked by uid 55); 7 Jan 2019 09:10:20 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [7/8/9 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Mon, 07 Jan 2019 09:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88702-4-qRcbKDegX8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00733.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
--- Comment #6 from Jan Hubicka <hubicka at ucw dot cz> ---
> You could also add match.pd rules merging stuff pair-wise...
>
> How's this a regression btw?
I was comparing with GCC 6 build where inlining apparently happened.
I believe inlining happens again - I am waiting for benchmarks to
finish.
Honza
>From gcc-bugs-return-627925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:13:34 2019
Return-Path: <gcc-bugs-return-627925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64685 invoked by alias); 7 Jan 2019 09:13:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64587 invoked by uid 48); 7 Jan 2019 09:13:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] [9 Regression] Spurious "redundant move in return statement"
Date: Mon, 07 Jan 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed short_desc cf_known_to_fail
Message-ID: <bug-88692-4-SITZL1haws@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00734.txt.bz2
Content-length: 1111
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |8.2.0
Keywords| |diagnostic
Last reconfirmed| |2019-01-07
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
Summary|Spurious "redundant move in |[9 Regression] Spurious
|return statement" |"redundant move in return
| |statement"
Known to fail| |9.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Confirmed. Making the suggested change (removing std::move) would cause a copy
from an lvalue, so it's certainly not redundant.
This is a new warning, so I'm marking it as a regression.
>From gcc-bugs-return-627926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:31:02 2019
Return-Path: <gcc-bugs-return-627926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129910 invoked by alias); 7 Jan 2019 09:31: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 129846 invoked by uid 48); 7 Jan 2019 09:30:57 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88734] New: [8/9 Regression] AArch64's ACLE intrinsics give an ICE instead of compile error when option mismatch.
Date: Mon, 07 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00735.txt.bz2
Content-length: 2576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88734
Bug ID: 88734
Summary: [8/9 Regression] AArch64's ACLE intrinsics give an ICE
instead of compile error when option mismatch.
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tnfchris at gcc dot gnu.org
Target Milestone: ---
Target: aarch64*-*-*
Using a neon intrinsics with the wrong commandline option used to lead to a
nice options mismatch error. Instead now in GCC 8 and 9 we get an ICE from
recog because the RTX is generated but can't be matched.
This code
```
#include <arm_neon.h>
int main ()
{
float32x4_t r = {0};
float16x8_t a = {0};
float16x8_t b = {0};
float32x4_t res = vfmlslq_laneq_high_u32 (r, a, b, 0);
return 0;
}
```
shouldn't ice when compiled with
```
aarch64-none-elf-gcc test2.c -specs=aem-validation.specs -O3
```
but it does with
```
test2.c: In function 'main':
test2.c:10:1: error: unrecognizable insn:
}
^
(insn 8 7 9 2 (set (reg:V4SF 91)
(fma:V4SF (float_extend:V4SF (neg:V4HF (vec_select:V4HF (reg:V8HF 93)
(parallel:V8HF [
(const_int 4 [0x4])
(const_int 5 [0x5])
(const_int 6 [0x6])
(const_int 7 [0x7])
]))))
(float_extend:V4SF (vec_duplicate:V4HF (vec_select:HF (reg:V8HF 94)
(parallel [
(const_int 0 [0])
]))))
(reg:V4SF 92))) "arm_neon.h":32284 -1
(nil))
during RTL pass: vregs
test2.c:10:1: internal compiler error: in extract_insn, at recog.c:2304
```
The RTX is generated when it shouldn't have been.
Seems to be an issue in arm_neon.h, one option after vadd_f16 must have popped
something it shouldn't have as that works.
The expected behavior is to get
```
../include/arm_neon.h:18282:1: error: inlining failed in call to always_inline
'vfmlslq_laneq_high_u32': target specific option mismatch
18282 | vfmlslq_laneq_high_u32 (float32x4_t __r, float16x8_t __a, float16x8_t
__b,
| ^~~~~~~~~~~~~~~~~~~~~~
test2.c:8:21: note: called from here
8 | float32x4_t res = vfmlslq_laneq_high_u32 (r, a, b, 0);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
```
as one does on arm-*
>From gcc-bugs-return-627928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:31:17 2019
Return-Path: <gcc-bugs-return-627928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 532 invoked by alias); 7 Jan 2019 09:31:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 491 invoked by uid 48); 7 Jan 2019 09:31:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88676] missed opportunity in integer conditional
Date: Mon, 07 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status resolution
Message-ID: <bug-88676-4-yFIgTeCHEW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88676-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00737.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88676
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:31:03 2019
Return-Path: <gcc-bugs-return-627927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130044 invoked by alias); 7 Jan 2019 09:31: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 129863 invoked by uid 48); 7 Jan 2019 09:30:58 -0000
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88735] New: Nested assignment triggers call of final method for right hand side
Date: Mon, 07 Jan 2019 09:31: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mscfd at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00736.txt.bz2
Content-length: 2166
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88735
Bug ID: 88735
Summary: Nested assignment triggers call of final method for
right hand side
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: mscfd at gmx dot net
Target Milestone: ---
In the following code a type "t" is defined in module mod, which provides an
assignment method and a final routine. The program itself defines a type "s",
with a component of type "t". Assignment "b=a" should call the final method for
b%x, as procedure "set" has intent(out) for self. However, as can be seen from
the output, finalise is called for the right hand side (the intent(in)
argument). The set routine is called afterwards, surprisingly still thinks that
x%i is allocated (it has been wrongly deallocated within finalise). The value
however is somehow set to zero (looks like the deallocated memory zeroed?).
The problem does not occur with intent(inout) for argument "self" in procedure
"set", as finalise is not called at all. The problem does not occur if a and b
are of type t. The nested assignment via type s is necessary to trigger the
bug.
module mod
implicit none
private
type, public :: t
integer, pointer :: i => null()
contains
procedure, public :: set
generic, public :: assignment(=) => set
final :: finalise
end type t
contains
subroutine set(self, x)
class(t), intent(out) :: self
class(t), intent(in) :: x
if (associated(x%i)) then
print *, 'setting: ', x%i
self%i => x%i
self%i = self%i + 1
end if
end subroutine set
subroutine finalise(self)
type(t), intent(inout) :: self
if (associated(self%i)) then
print *, 'finalising: ', self%i
deallocate(self%i)
end if
end subroutine finalise
end module mod
program finalise_assign
use mod
implicit none
type :: s
type(t) :: x
end type s
type(s) :: a, b
allocate(a%x%i)
a%x%i = 123
b = a
end program finalise_assign
>From gcc-bugs-return-627929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:32:28 2019
Return-Path: <gcc-bugs-return-627929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14671 invoked by alias); 7 Jan 2019 09:32: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 14588 invoked by uid 48); 7 Jan 2019 09:32:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Mon, 07 Jan 2019 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status assigned_to
Message-ID: <bug-88677-4-iDkHuQ4r4w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00738.txt.bz2
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look.
>From gcc-bugs-return-627930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:33:36 2019
Return-Path: <gcc-bugs-return-627930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19944 invoked by alias); 7 Jan 2019 09: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 19848 invoked by uid 48); 7 Jan 2019 09:33:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88680] [9 Regression] bogus -Wtype-limits for constant expressions after r267272
Date: Mon, 07 Jan 2019 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88680-4-PaxyQwNVjx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88680-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88680-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00739.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88680
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-627931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:39:38 2019
Return-Path: <gcc-bugs-return-627931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43061 invoked by alias); 7 Jan 2019 09:39: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 42971 invoked by uid 48); 7 Jan 2019 09:39:33 -0000
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88735] Nested assignment triggers call of final method for right hand side
Date: Mon, 07 Jan 2019 09:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mscfd at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88735-4-ircrGMzqHG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00740.txt.bz2
Content-length: 371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88735
--- Comment #1 from martin <mscfd at gmx dot net> ---
Remark: output should be one line
setting: 123
If the output starts with
finalising: 123
then this is wrong (as b%x%i is not associated when finalise is called for
b%x).
Also present in current gfortran-9 branch compiled a couple of days ago.
>From gcc-bugs-return-627932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:43:19 2019
Return-Path: <gcc-bugs-return-627932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102123 invoked by alias); 7 Jan 2019 09:43:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97036 invoked by uid 48); 7 Jan 2019 09:43:15 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88735] Nested assignment triggers call of final method for right hand side
Date: Mon, 07 Jan 2019 09:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority bug_status cf_reconfirmed_on blocked everconfirmed
Message-ID: <bug-88735-4-iABrzHsU45@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00741.txt.bz2
Content-length: 897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88735
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Blocks| |37336
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from 4.9 up to trunk (9.0), finalization is not yet implemented in
4.8.
Note that I get a segfault at run time.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37336
[Bug 37336] [F03] Finish derived-type finalization
>From gcc-bugs-return-627933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:46:41 2019
Return-Path: <gcc-bugs-return-627933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43274 invoked by alias); 7 Jan 2019 09:46: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 43091 invoked by uid 48); 7 Jan 2019 09:46:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88686] [7/8/9 Regression] gcc generates wrong debug information at -O1
Date: Mon, 07 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component cf_known_to_work version target_milestone short_desc cf_known_to_fail
Message-ID: <bug-88686-4-942AWb1sob@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00742.txt.bz2
Content-length: 1023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|debug |rtl-optimization
Known to work| |4.8.5, 5.5.0
Version|unknown |8.2.1
Target Milestone|--- |7.5
Summary|gcc generates wrong debug |[7/8/9 Regression] gcc
|information at -O1 |generates wrong debug
| |information at -O1
Known to fail| |7.2.1, 8.2.0
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Works for me with GCC 4.8 and GCC 5, fails with GCC 7 and 8 at least.
The code is a bit convoluted but correct at RTL expansion time so this
goes wrong on RTL somehow (I guess cross-jumping or whatever).
>From gcc-bugs-return-627934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:49:11 2019
Return-Path: <gcc-bugs-return-627934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47700 invoked by alias); 7 Jan 2019 09:49: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 47066 invoked by uid 48); 7 Jan 2019 09:49:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88690] [7/8/9 Regression] c++17 internal compiler error: in output_constructor_regular_field, at varasm.c:5031
Date: Mon, 07 Jan 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-88690-4-QoluoDgNM6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88690-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00743.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88690
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P3 |P2
>From gcc-bugs-return-627935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:49:41 2019
Return-Path: <gcc-bugs-return-627935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49155 invoked by alias); 7 Jan 2019 09:49:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48618 invoked by uid 48); 7 Jan 2019 09:49:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] [9 Regression] Spurious "redundant move in return statement"
Date: Mon, 07 Jan 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88692-4-cWBdWN3AwU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00744.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-627936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:52:23 2019
Return-Path: <gcc-bugs-return-627936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56012 invoked by alias); 7 Jan 2019 09:52: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 55920 invoked by uid 55); 7 Jan 2019 09:52:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 09:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-xV7j4yQatv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00745.txt.bz2
Content-length: 642
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 7 09:51:46 2019
New Revision: 267638
URL: https://gcc.gnu.org/viewcvs?rev=267638&root=gcc&view=rev
Log:
PR debug/88723
* dwarf2out.c (const_ok_for_output_1): Remove redundant call to
const_not_ok_for_debug_p target hook.
(mem_loc_descriptor) <case UNSPEC>: Only call const_ok_for_output_1
on UNSPEC and subexpressions thereof if all subexpressions of the
UNSPEC are CONSTANT_P.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/dwarf2out.c
>From gcc-bugs-return-627937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:58:12 2019
Return-Path: <gcc-bugs-return-627937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128556 invoked by alias); 7 Jan 2019 09:58:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128472 invoked by uid 48); 7 Jan 2019 09:58:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 09:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-NFV7Rm50qW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00746.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Should be fixed, I'll let you test it before closing though.
That said, I think this exact UNSPEC should be delegitimized by the target
hook,
(define_insn "movsi_pic_gotdata_op"
[(set (match_operand:SI 0 "register_operand" "=r")
(unspec:SI [(match_operand:SI 1 "register_operand" "r")
(match_operand:SI 2 "register_operand" "r")
(match_operand 3 "symbolic_operand" "")]
UNSPEC_MOVE_GOTDATA))]
"flag_pic && check_pic (1)"
{
#ifdef HAVE_AS_SPARC_GOTDATA_OP
return "ld\t[%1 + %2], %0, %%gdop(%a3)";
#else
return "ld\t[%1 + %2], %0";
#endif
}
suggests that (unspec:MODE [(reg:MODE) (reg:MODE) (symbol_ref)]) is either
(mem:MODE (plus:MODE (reg:MODE) (reg:MODE))) or perhaps the third operand
itself?
>From gcc-bugs-return-627938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 09:59:03 2019
Return-Path: <gcc-bugs-return-627938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4071 invoked by alias); 7 Jan 2019 09:59:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3954 invoked by uid 48); 7 Jan 2019 09:58:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88619] [9 Regression] ICE in asan_emit_stack_protection, at asan.c:1574 since r266664
Date: Mon, 07 Jan 2019 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to
Message-ID: <bug-88619-4-INTmBoXske@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88619-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00747.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88619
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Assignee|marxin at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-627939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:01:54 2019
Return-Path: <gcc-bugs-return-627939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31324 invoked by alias); 7 Jan 2019 10:01:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29146 invoked by uid 48); 7 Jan 2019 10:01:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Mon, 07 Jan 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85052-4-sPgHfNYRAD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00748.txt.bz2
Content-length: 748
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Implemented on the trunk now. The 4x/8x narrowing/widening conversions will
need further work to handle them efficiently, though for 8x conversions we are
e.g. on x86 already outside of the realm of natively supported vectors (we
don't really want MMX and for 1024 bit and wider generic vectors we don't
always emit best code).
>From gcc-bugs-return-627940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:01:56 2019
Return-Path: <gcc-bugs-return-627940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31883 invoked by alias); 7 Jan 2019 10:01:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30346 invoked by uid 48); 7 Jan 2019 10:01:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88670] [meta-bug] generic vector extension issues
Date: Mon, 07 Jan 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88670-4-RdGR3P9RWT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00750.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88670
Bug 88670 depends on bug 85052, which changed state.
Bug 85052 Summary: Implement support for clang's __builtin_convertvector
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-627942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:02:18 2019
Return-Path: <gcc-bugs-return-627942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39757 invoked by alias); 7 Jan 2019 10:02: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 34081 invoked by uid 48); 7 Jan 2019 10:02:08 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88734] [8/9 Regression] AArch64's ACLE intrinsics give an ICE instead of compile error when option mismatch.
Date: Mon, 07 Jan 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov 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 bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed target_milestone cf_known_to_fail
Message-ID: <bug-88734-4-M03c4GMh2M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00751.txt.bz2
Content-length: 818
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88734
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Known to work| |7.4.1
Keywords| |ice-on-invalid-code
Last reconfirmed| |2019-01-07
CC| |ktkachov at gcc dot gnu.org
Ever confirmed|0 |1
Target Milestone|--- |8.3
Known to fail| |8.2.1, 9.0
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed.
>From gcc-bugs-return-627941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:02:00 2019
Return-Path: <gcc-bugs-return-627941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32527 invoked by alias); 7 Jan 2019 10:02: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 30092 invoked by uid 48); 7 Jan 2019 10:01:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88601] We may consider adding __builtin_convertvector and __builtin_shufflevector for better compaitbility with Clang
Date: Mon, 07 Jan 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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_status resolution
Message-ID: <bug-88601-4-K2WpDgrlMG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88601-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88601-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00749.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88601
Bug 88601 depends on bug 85052, which changed state.
Bug 85052 Summary: Implement support for clang's __builtin_convertvector
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-627943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:02:29 2019
Return-Path: <gcc-bugs-return-627943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44367 invoked by alias); 7 Jan 2019 10:02: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 42109 invoked by uid 55); 7 Jan 2019 10:02:25 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85486] [og7, nvptx] ref-1.C fails with vector length 128
Date: Mon, 07 Jan 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85486-4-ZvOn2h3NG6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85486-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85486-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00752.txt.bz2
Content-length: 1033
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85486
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Mon Jan 7 10:01:49 2019
New Revision: 267640
URL: https://gcc.gnu.org/viewcvs?rev=267640&root=gcc&view=rev
Log:
[nvptx] Force vl32 if calling vector-partitionable routines
With PTX_MAX_VECTOR_LENGTH set to larger than PTX_WARP_SIZE, routines can be
called from offloading regions with vector-size set to larger than warp size.
OTOH, vector-partitionable routines assume warp-sized vector length.
Detect if we're calling a vector-partitionable routine from an offloading
region, and if so, fall back to warp-sized vector length in that region.
2019-01-07 Tom de Vries <tdevries@suse.de>
PR target/85486
* config/nvptx/nvptx.c (has_vector_partitionable_routine_calls_p): New
function.
(nvptx_goacc_validate_dims): Force vl32 if calling vector-partitionable
routines.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/nvptx/nvptx.c
>From gcc-bugs-return-627944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:04:10 2019
Return-Path: <gcc-bugs-return-627944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47957 invoked by alias); 7 Jan 2019 10:04:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47828 invoked by uid 55); 7 Jan 2019 10:04:06 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 10:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-LO4ZRW3z5u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00753.txt.bz2
Content-length: 329
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Should be fixed, I'll let you test it before closing though.
I did last night and it worked fine. Thanks.
>From gcc-bugs-return-627945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:07:33 2019
Return-Path: <gcc-bugs-return-627945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51818 invoked by alias); 7 Jan 2019 10:07:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51769 invoked by uid 48); 7 Jan 2019 10:07:29 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88697] New test case gcc.target/powerpc/pr88457.c in r267307 fails because of glibc requirement
Date: Mon, 07 Jan 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88697-4-c2akr6QvP3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88697-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88697-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00754.txt.bz2
Content-length: 198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88697
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
you can add a new effective target (or adjust the existing one accordingly)
>From gcc-bugs-return-627947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:17:19 2019
Return-Path: <gcc-bugs-return-627947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66066 invoked by alias); 7 Jan 2019 10:17:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65649 invoked by uid 48); 7 Jan 2019 10:17:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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: 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-88723-4-qmxFAuYvKV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00756.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Closing then. Eric, please consider the sparc_delegitimize_address addition
though.
>From gcc-bugs-return-627946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:17:12 2019
Return-Path: <gcc-bugs-return-627946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65368 invoked by alias); 7 Jan 2019 10:17: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 65312 invoked by uid 48); 7 Jan 2019 10:17:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Mon, 07 Jan 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88701-4-NxzClaeXHl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00755.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-627948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:18:12 2019
Return-Path: <gcc-bugs-return-627948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67403 invoked by alias); 7 Jan 2019 10:18: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 67315 invoked by uid 55); 7 Jan 2019 10:18:07 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 10:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-tiB0nYZ0gj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00757.txt.bz2
Content-length: 1327
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #8 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> I don't have access to Solaris, can you attach preprocessed testsuite_shared.cc
> + the g++ options used to compile it?
Just in case, there are Solaris/SPARC systems in the compile farm now:
gcc210 running Solaris 10 and gcc211 running Solaris 11.
> The note generally shouldn't break stuff, it isn't an error, just a debugging
> hint (goes away for --enable-checking=release builds) that maybe the sparc
> delegitimize hook needs more work.
I've done some digging on that front:
* While libstdc++-dg-prune does prune notes, it is only used from
dg-test and friends.
* However, the libstdc++ testsuite support code is compiled with
v3_target_compile, ultimately calling DejaGnu's target.exp
(default_target_compile). That does some pruning itself using
prune_warnings, but that mostly applies to linker warnings.
* The libstdc++ testsuite support code is compiled with -w to suppress
warnings, but there's no equivalent way to suppress notes:
diagnostic_inhibit_notes is only called from toplev.c
(process_options) for -fcompare-debug. Maybe that's something to be
changed?
>From gcc-bugs-return-627949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:19:02 2019
Return-Path: <gcc-bugs-return-627949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68628 invoked by alias); 7 Jan 2019 10: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 68520 invoked by uid 48); 7 Jan 2019 10:18:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88704] Accepts invalid program with [*] outside function prototype scope.
Date: Mon, 07 Jan 2019 10:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88704-4-XymKVlOdem@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00758.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88704
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I guess we treat it the K&R way
>From gcc-bugs-return-627950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:22:13 2019
Return-Path: <gcc-bugs-return-627950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85164 invoked by alias); 7 Jan 2019 10:22:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85091 invoked by uid 48); 7 Jan 2019 10:22:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88709] Improve store-merging
Date: Mon, 07 Jan 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88709-4-lcorkBCXKl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88709-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88709-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00759.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88709
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
>From gcc-bugs-return-627951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:23:47 2019
Return-Path: <gcc-bugs-return-627951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88488 invoked by alias); 7 Jan 2019 10:23:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88413 invoked by uid 48); 7 Jan 2019 10:23:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88712] Optimization: mov edx, 0 not replaced with xor edx, edx in this case
Date: Mon, 07 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88712-4-E9to1UE1UF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88712-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00760.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88712
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
>From gcc-bugs-return-627952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:28:45 2019
Return-Path: <gcc-bugs-return-627952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71967 invoked by alias); 7 Jan 2019 10:28:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71881 invoked by uid 48); 7 Jan 2019 10:28:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Mon, 07 Jan 2019 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88713-4-dXVY8lh8Yy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00761.txt.bz2
Content-length: 533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
So can the fortran FE inline the _gfortran_internal_pack() call? It looks like
flang manages to elide this when inlining the function at least?
>From gcc-bugs-return-627953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:30:50 2019
Return-Path: <gcc-bugs-return-627953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85670 invoked by alias); 7 Jan 2019 10:30: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 85044 invoked by uid 48); 7 Jan 2019 10:30:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Mon, 07 Jan 2019 10:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority cc
Message-ID: <bug-88714-4-ZKMJrXnt3N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00762.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Priority|P3 |P1
CC| |segher at gcc dot gnu.org
>From gcc-bugs-return-627954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:31:53 2019
Return-Path: <gcc-bugs-return-627954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89969 invoked by alias); 7 Jan 2019 10:31:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89851 invoked by uid 48); 7 Jan 2019 10:31:48 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Mon, 07 Jan 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 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: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-rN5JAoSe0n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00763.txt.bz2
Content-length: 955
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> That said, I think this exact UNSPEC should be delegitimized by the target
> hook,
> (define_insn "movsi_pic_gotdata_op"
> [(set (match_operand:SI 0 "register_operand" "=r")
> (unspec:SI [(match_operand:SI 1 "register_operand" "r")
> (match_operand:SI 2 "register_operand" "r")
> (match_operand 3 "symbolic_operand" "")]
> UNSPEC_MOVE_GOTDATA))]
> "flag_pic && check_pic (1)"
> {
> #ifdef HAVE_AS_SPARC_GOTDATA_OP
> return "ld\t[%1 + %2], %0, %%gdop(%a3)";
> #else
> return "ld\t[%1 + %2], %0";
> #endif
> }
> suggests that (unspec:MODE [(reg:MODE) (reg:MODE) (symbol_ref)]) is either
> (mem:MODE (plus:MODE (reg:MODE) (reg:MODE))) or perhaps the third operand
> itself?
Yes, operand #3 is the {LABEL,SYMBOL}_REF that we want to return in this case.
>From gcc-bugs-return-627955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:36:54 2019
Return-Path: <gcc-bugs-return-627955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105788 invoked by alias); 7 Jan 2019 10:36:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105723 invoked by uid 48); 7 Jan 2019 10:36:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88728] Boostrap with -Og fails with garbled file libgcov-profiler.i
Date: Mon, 07 Jan 2019 10:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88728-4-7O1711p0UF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00764.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think the proper way of booting with -Og would be setting BOOT_CFLAGS
rather than CFLAGS/CXXFLAGS. Note the issue might be the use of -save-temps.
>From gcc-bugs-return-627956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:37:52 2019
Return-Path: <gcc-bugs-return-627956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106878 invoked by alias); 7 Jan 2019 10:37: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 106820 invoked by uid 48); 7 Jan 2019 10:37:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88729] ICE in libiberty during bootstrap with debug info
Date: Mon, 07 Jan 2019 10:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88729-4-tNrA4YRdxk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00765.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88729
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
There was some intermediate related ICE introduced and now fixed, so maybe
re-try.
>From gcc-bugs-return-627957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:43:05 2019
Return-Path: <gcc-bugs-return-627957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15630 invoked by alias); 7 Jan 2019 10:43:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15451 invoked by uid 48); 7 Jan 2019 10:42:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88730] [8 Regression] gcc generates wrong debug information at -Og
Date: Mon, 07 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work version cf_reconfirmed_on component cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-88730-4-Ja3WrFFPqp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88730-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88730-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00766.txt.bz2
Content-length: 1167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88730
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |7.3.1, 9.0
Version|unknown |8.2.1
Last reconfirmed| |2019-01-07
Component|debug |rtl-optimization
CC| |aoliva at gcc dot gnu.org
Ever confirmed|0 |1
Summary|gcc generates wrong debug |[8 Regression] gcc
|information at -Og |generates wrong debug
| |information at -Og
Target Milestone|--- |8.3
Known to fail| |8.2.1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
again RTL issue. With GCC 7 we get <optimized out> for j, so do we for GCC 9.
But the underlying issue might be latent.
>From gcc-bugs-return-627958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:43:19 2019
Return-Path: <gcc-bugs-return-627958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16440 invoked by alias); 7 Jan 2019 10:43:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16368 invoked by uid 55); 7 Jan 2019 10:43:14 -0000
From: "hainque at adacore dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/448] <stdint.h>-related issues (C99 issues)
Date: Mon, 07 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 2.96
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hainque at adacore 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-448-4-5m5Ynv3wAt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-448-4@http.gcc.gnu.org/bugzilla/>
References: <bug-448-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00767.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=448
--- Comment #41 from hainque at adacore dot com <hainque at adacore dot com> ---
> On 2 Jan 2019, at 23:33, joseph at codesourcery dot com <gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=448
>
> --- Comment #40 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
> The definitions have been added for VxWorks at some point.
Yes, https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00761.html
I think.
>From gcc-bugs-return-627959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:44:52 2019
Return-Path: <gcc-bugs-return-627959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29015 invoked by alias); 7 Jan 2019 10:44:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26274 invoked by uid 48); 7 Jan 2019 10:44:47 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88736] New: nullptr_t available without namespace qualification
Date: Mon, 07 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz 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-88736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00768.txt.bz2
Content-length: 696
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88736
Bug ID: 88736
Summary: nullptr_t available without namespace qualification
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: drepper.fsp+rhbz at gmail dot com
Target Milestone: ---
I don't think the following should work and clang indeed complains. gcc 8.2.1
and current trunk both accept it without warning, even with -pedantic.
#include <cstddef>
int f(nullptr_t) {
return 0;
}
Obviously gcc should recommend using std::nullptr_t.
>From gcc-bugs-return-627960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:46:26 2019
Return-Path: <gcc-bugs-return-627960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45949 invoked by alias); 7 Jan 2019 10:46: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 45859 invoked by uid 48); 7 Jan 2019 10:46:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88732] different results on -O0 and -O1, -O2, -O3, -Os
Date: Mon, 07 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88732-4-iUEWXpFVAy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00769.txt.bz2
Content-length: 519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88732
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
With optimization we constant-fold it, without the runtime expansion exploits
undefinedness.
>From gcc-bugs-return-627961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:50:07 2019
Return-Path: <gcc-bugs-return-627961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53202 invoked by alias); 7 Jan 2019 10:50: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 53108 invoked by uid 48); 7 Jan 2019 10:50:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88733] [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Mon, 07 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status keywords cf_reconfirmed_on component cc everconfirmed target_milestone
Message-ID: <bug-88733-4-RPUs6Az5is@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00770.txt.bz2
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |ASSIGNED
Keywords| |lto
Last reconfirmed| |2019-01-07
Component|other |lto
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
Target Milestone|--- |9.0
>From gcc-bugs-return-627962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:53:24 2019
Return-Path: <gcc-bugs-return-627962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58344 invoked by alias); 7 Jan 2019 10:53: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 58263 invoked by uid 48); 7 Jan 2019 10:53:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88686] [7/8/9 Regression] gcc generates wrong debug information at -O1
Date: Mon, 07 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88686-4-OngM1AbPVV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00771.txt.bz2
Content-length: 1587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Single-source testcase:
volatile int a, b;
int c;
__attribute__ ((noipa))
void optimize_me_not (void)
{
asm volatile ("":"+g" (a), "+g" (b), "+g" (c));
}
int
main ()
{
int j;
for (; b < 10; b++)
{
j = 0;
for (; j < 2; j++)
{
optimize_me_not ();
c = 0;
for (; c < 6; c++)
a = b + c;
}
}
return 0;
}
This looks like a clear GDB bug to me.
We emit two different call optimize_me_not instructions. The first one is:
# DEBUG j => 0x1
# pr88686-3.c:19:4
.loc 1 19 4 is_stmt 1
call optimize_me_not
and the second one is:
.L3:
# DEBUG j => 0
# pr88686-3.c:19:4
.loc 1 19 4 is_stmt 1
call optimize_me_not
but before the first hunk there is already
jmp .L3
If you b main and step through, you'll see that on the first spot where
optimize_me_not () is called, j is 0, the second 1, the third 0 etc.
But if you b 19, you can see it placed breakpoint solely on the first location,
not the second one.
In readelf -wl dump, I see:
[0x00000054] Set is_stmt to 1
[0x00000055] Special opcode 236: advance Address by 16 to 0x40113e and Line
by 7 to 19
(0x40113e is the first call where j is supposed to be 1) and
[0x00000085] Set is_stmt to 1
[0x00000086] Special opcode 80: advance Address by 5 to 0x401182 and Line by
5 to 19
(0x401182 is the second call where j is supposed to be 0).
>From gcc-bugs-return-627963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 10:56:28 2019
Return-Path: <gcc-bugs-return-627963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62417 invoked by alias); 7 Jan 2019 10:56: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 62377 invoked by uid 48); 7 Jan 2019 10:56:24 -0000
From: "neal at walfield dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] New: RFE: Track ownership moves
Date: Mon, 07 Jan 2019 10:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: neal at walfield dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00772.txt.bz2
Content-length: 1226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
Bug ID: 88737
Summary: RFE: Track ownership moves
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: neal at walfield dot org
Target Milestone: ---
I would like an attribute to indicate that ownership of an argument is moved to
the function. That is, any subsequent accesses to the variable should be
considered invalid, and gcc should emit a warning, if possible.
Consider the following example:
```
#include <stdlib.h>
#include <stdio.h>
int
main(int argc, char *argv[]) {
int *a = malloc(sizeof(int));
*a = 1;
printf("%d\n", *a);
free(a);
printf("%d\n", *a);
return 0;
}
```
Compiling this with -Wall (using gcc 6.3.0-18+deb9u1 from Debian) does not emit
a warning even though there is a use-after-free bug.
Although freeing a variable is the most obvious example of this pattern, this
pattern often arises when dealing with pointers.
This RFE is based on my experience using Rust's lifetimes, which prevent this
type of error in Rust.
>From gcc-bugs-return-627964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:01:43 2019
Return-Path: <gcc-bugs-return-627964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72030 invoked by alias); 7 Jan 2019 11:01: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 71975 invoked by uid 48); 7 Jan 2019 11:01:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-88737-4-3BTgmKPOyz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00773.txt.bz2
Content-length: 299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-627966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:03:12 2019
Return-Path: <gcc-bugs-return-627966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74147 invoked by alias); 7 Jan 2019 11: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 73605 invoked by uid 48); 7 Jan 2019 11:03:07 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 11:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-88737-4-raIUDaHq10@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00775.txt.bz2
Content-length: 301
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-627965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:03:07 2019
Return-Path: <gcc-bugs-return-627965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73602 invoked by alias); 7 Jan 2019 11:03: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 73407 invoked by uid 48); 7 Jan 2019 11:02:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 11:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc bug_severity
Message-ID: <bug-88737-4-FEcX8ozBph@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00774.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |msebor at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Severity|enhancement |normal
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Practically the implementation could mark a end-of-life like the following:
free (a);
a = {CLOBBER};
printf("%d\n", *a);
and you'd get a uninitialized use warning on the *a dereference.
This is something gimplification could emit after free() calls without
any extension(?)
>From gcc-bugs-return-627967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:06:06 2019
Return-Path: <gcc-bugs-return-627967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114367 invoked by alias); 7 Jan 2019 11:06: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 114267 invoked by uid 48); 7 Jan 2019 11:06:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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-88737-4-yrjDiHnf5f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00776.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Wouldn't that break e.g. programs that
free (a);
return (uintptr_t) a % 16;
or similar (i.e. inspect the bits of the pointer rather than what it points
to)?
That should be valid even after free, free doesn't modify the pointer, only
says that what it points to is no longer available.
>From gcc-bugs-return-627968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:08:07 2019
Return-Path: <gcc-bugs-return-627968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43665 invoked by alias); 7 Jan 2019 11:08: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 43573 invoked by uid 55); 7 Jan 2019 11:08:02 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88737-4-qK3TnM6cKO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00777.txt.bz2
Content-length: 757
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 7 Jan 2019, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
>
> --- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> Wouldn't that break e.g. programs that
> free (a);
> return (uintptr_t) a % 16;
> or similar (i.e. inspect the bits of the pointer rather than what it points
> to)?
> That should be valid even after free, free doesn't modify the pointer, only
> says that what it points to is no longer available.
Indeed. So it would be
*a = {CLOBBER};
which is of course somewhat difficult since we do not know the size
of the object pointed to.
>From gcc-bugs-return-627969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:12:12 2019
Return-Path: <gcc-bugs-return-627969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91825 invoked by alias); 7 Jan 2019 11:12:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91756 invoked by uid 48); 7 Jan 2019 11:12:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88733] [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Mon, 07 Jan 2019 11:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also
Message-ID: <bug-88733-4-6iSkfuLVl7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00778.txt.bz2
Content-length: 582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=88140
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Similar to PR88140 started with r266325.
>From gcc-bugs-return-627970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:13:11 2019
Return-Path: <gcc-bugs-return-627970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109801 invoked by alias); 7 Jan 2019 11:13:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107069 invoked by uid 48); 7 Jan 2019 11:13:06 -0000
From: "neal at walfield dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 11:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: neal at walfield dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88737-4-5PwnIOGcQ4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00779.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
--- Comment #4 from Neal H. Walfield <neal at walfield dot org> ---
I'm not sure what '*a = {CLOBBER};' does and I'm having trouble finding
documentation for it so the following comment might be unnecessary.
Nevertheless: when I say "move", I don't mean that the object is necessarily
freed, just that the object's ownership has been transferred to the callee and,
as such, the caller is not allowed to access it anymore.
>From gcc-bugs-return-627971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:16:13 2019
Return-Path: <gcc-bugs-return-627971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53417 invoked by alias); 7 Jan 2019 11:16: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 53337 invoked by uid 48); 7 Jan 2019 11:16:03 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88738] New: treat shared_ptr and unique_ptr more like plain old pointers
Date: Mon, 07 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz 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-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00780.txt.bz2
Content-length: 1256
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
Bug ID: 88738
Summary: treat shared_ptr and unique_ptr more like plain old
pointers
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: drepper.fsp+rhbz at gmail dot com
Target Milestone: ---
The implementations are obviously more complicated but the warning handling the
current implementation allows is less than optimal. For the test case below
gcc (8.2.1, current trunk) doesn't emit any warning, even with -Wall. clang on
the other hand reports
$ clang++ -c -O -Wall -g v.cc -std=gnu++17
v.cc:8:9: warning: equality comparison result unused [-Wunused-comparison]
res == nullptr;
~~~~^~~~~~~~~~
v.cc:8:9: note: use '=' to turn this equality comparison into an assignment
res == nullptr;
^~
=
Test (compile with -std=c++17):
#include <memory>
using type = std::shared_ptr<int>;
type f(int a) {
auto res = std::make_shared<int>(3);
if (a == 0)
res == nullptr; // <- obviously incorrect
return res;
}
>From gcc-bugs-return-627972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:17:45 2019
Return-Path: <gcc-bugs-return-627972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59247 invoked by alias); 7 Jan 2019 11:17:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59139 invoked by uid 48); 7 Jan 2019 11:17:36 -0000
From: "stephen.kim at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/88262] gcc uses crt1.o in place of Scrt1.o when the main function is in a PIC shared lib
Date: Mon, 07 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: stephen.kim at oracle dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88262-4-2qX52nurzy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88262-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88262-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00781.txt.bz2
Content-length: 753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88262
--- Comment #19 from Stephen Kim <stephen.kim at oracle dot com> ---
Thank you for all of your comments! I have talked with our team members again.
It seems that there has been miscommunication. They seemed to have intended
that Go tools should give Scrt1.o. However, as Go tools is just an ordinary
client of gcc (and clang or whatsoever), I believed that Go tools is not
supposed to know about Scrt1.o or crt1.o. They are internals. That made me
think that the gcc driver must be the culprit.
However, it seems that the gcc driver is supposed to give crt1.o, and I could
now convince myself.
If that's the case, this issue should be resolved either in glibc or gold.
Thanks again!
>From gcc-bugs-return-627973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:22:21 2019
Return-Path: <gcc-bugs-return-627973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72664 invoked by alias); 7 Jan 2019 11:22: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 72581 invoked by uid 48); 7 Jan 2019 11:22:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88733] [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Mon, 07 Jan 2019 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88733-4-AZvXmPYnWS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00782.txt.bz2
Content-length: 554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
error_mark_node is used for the cases where the outlined region doesn't get
passed the corresponding size in any way.
See https://gcc.gnu.org/ml/gcc-patches/2018-05/msg01778.html and the
discussions in that thread.
I have a newer version of that patch which fixes this ICE too, but from what I
remember at least back in November where I've updated the patch it broke some
Fortran VLA testcases, so I'll need to have a closer look.
>From gcc-bugs-return-627974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:22:45 2019
Return-Path: <gcc-bugs-return-627974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73515 invoked by alias); 7 Jan 2019 11:22: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 73426 invoked by uid 48); 7 Jan 2019 11:22:41 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Mon, 07 Jan 2019 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 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: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cc assigned_to
Message-ID: <bug-88677-4-7N8iWygXT5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00783.txt.bz2
Content-length: 3415
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|ASSIGNED |NEW
CC| |rguenth at gcc dot gnu.org
Assignee|rguenth at gcc dot gnu.org |hubicka at gcc dot gnu.org
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Value numbering stmt = SR.10_27 = MEM[(struct D *)&m];
-Setting value number of SR.10_27 to SR.10_27 (changed)
+Setting value number of SR.10_27 to SR.9_23 (changed)
but then of course the code-difference
<bb 7> :
- # SR.10_12 = PHI <0(5), SR.10_27(6)>
return;
is somewhat spurious since nothing uses SR.10_12, we're getting to
removal only because eliding SR.10_27 enables DCE.
<bb 6> :
SR.10_27 = MEM[(struct D *)&m];
<bb 7> :
# SR.10_12 = PHI <0(5), SR.10_27(6)>
return;
So the code-gen difference is likely because of the following which makes
dropping TYPE_NEEDS_CONSTRUCTING a suspicious change.
/* Return true if VAR may be aliased. A variable is considered as
maybe aliased if it has its address taken by the local TU
or possibly by another TU and might be modified through a pointer. */
static inline bool
may_be_aliased (const_tree var)
{
return (TREE_CODE (var) != CONST_DECL
&& (TREE_PUBLIC (var)
|| DECL_EXTERNAL (var)
|| TREE_ADDRESSABLE (var))
&& !((TREE_STATIC (var) || TREE_PUBLIC (var) || DECL_EXTERNAL (var))
&& ((TREE_READONLY (var)
&& !TYPE_NEEDS_CONSTRUCTING (TREE_TYPE (var)))
|| (TREE_CODE (var) == VAR_DECL
&& DECL_NONALIASED (var)))));
}
the variable in question is
<var_decl 0x7ffff7fefcf0 m
type <record_type 0x7ffff69e6a80 D readonly needs-constructing type_1
type_5 SI
size <integer_cst 0x7ffff689c078 constant 32>
unit-size <integer_cst 0x7ffff689c090 constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff69e6a80
fields <function_decl 0x7ffff69f5c00 __ct type <method_type
0x7ffff69f3000>
public abstract external autoinline decl_3 QI t.ii:2:29 align:16
warn_if_not_align:0 context <record_type 0x7ffff69e69d8 D>
full-name "constexpr D<j>::D(D<j>&&) noexcept (<uninstantiated>)"
not-really-extern chain <function_decl 0x7ffff69f5e00 __ct_base >>
context <translation_unit_decl 0x7ffff6887168 t.ii>
full-name "const class D<j>"
needs-constructor X(constX&) this=(X&) n_parents=1 use_template=1
interface-unknown
pointer_to_this <pointer_type 0x7ffff69f30a8> reference_to_this
<reference_type 0x7ffff69f3150>>
readonly addressable used public external read decl_2 VOID t.ii:17:19
align:8 warn_if_not_align:0 context <translation_unit_decl 0x7ffff6887168
t.ii> chain <type_decl 0x7ffff699cc78 j>>
may_be_aliased tries to avoid claiming R/O data can be written to, but of
course that's not true for the global ctor.
-> You can't simply remove this flag. You could set it to true conservatively.
Or we could stop marking globals that need constructing TREE_READONLY.
>From gcc-bugs-return-627975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:23:19 2019
Return-Path: <gcc-bugs-return-627975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74488 invoked by alias); 7 Jan 2019 11:23:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74359 invoked by uid 48); 7 Jan 2019 11:23:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88521] gcc 9.0 from r266355 miscompile x265 for mingw-w64 target
Date: Mon, 07 Jan 2019 11:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: 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-88521-4-PTDuu1hBhg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00784.txt.bz2
Content-length: 512
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88521
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Hopefully fixed now.
>From gcc-bugs-return-627977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:25:38 2019
Return-Path: <gcc-bugs-return-627977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95715 invoked by alias); 7 Jan 2019 11:25:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95657 invoked by uid 48); 7 Jan 2019 11:25:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88729] ICE in libiberty during bootstrap with debug info
Date: Mon, 07 Jan 2019 11:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88729-4-mW82LCnTFN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00786.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88729
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-07
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-627976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:25:12 2019
Return-Path: <gcc-bugs-return-627976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94843 invoked by alias); 7 Jan 2019 11:25: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 94794 invoked by uid 48); 7 Jan 2019 11:25:06 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Mon, 07 Jan 2019 11:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drepper.fsp+rhbz at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88738-4-YbX2faX880@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00785.txt.bz2
Content-length: 361
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #1 from Ulrich Drepper <drepper.fsp+rhbz at gmail dot com> ---
BTW, this also applies to the "unused variable" warning as in the code below
but clang doesn't warn about that either.
#include <memory>
using type = std::shared_ptr<int>;
type g;
int f(int a) {
auto p = g;
return a+1;
}
>From gcc-bugs-return-627978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:31:08 2019
Return-Path: <gcc-bugs-return-627978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107216 invoked by alias); 7 Jan 2019 11:31:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107009 invoked by uid 48); 7 Jan 2019 11:30:58 -0000
From: "mateuszb at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85667] (x86_64) ms_abi rules aren't followed when returning short structs with float values
Date: Mon, 07 Jan 2019 11:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mateuszb at poczta dot onet.pl
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85667-4-erp6xMQuku@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85667-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85667-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00787.txt.bz2
Content-length: 200
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85667
--- Comment #6 from mateuszb at poczta dot onet.pl ---
Now it is fixed for 64-bit GCC 9.
For 32-bit GCC 9 it is not fixed (return goes to st(0)).
>From gcc-bugs-return-627979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:34:53 2019
Return-Path: <gcc-bugs-return-627979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114703 invoked by alias); 7 Jan 2019 11:34:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114617 invoked by uid 48); 7 Jan 2019 11:34:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88709] Improve store-merging
Date: Mon, 07 Jan 2019 11:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88709-4-B7Znz0bZvU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88709-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88709-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00788.txt.bz2
Content-length: 1174
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88709
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, especially with large constructors, unlike other overlapping stores it
might not be feasible to merge the large clearing or memset with the other
stores, but still it might be possible to merge several later stores using info
on what we know has been stored in the gaps in between.
So, say:
struct S { char a[16]; };
void
foo (void)
{
struct S s = {};
s.a[3] = 1; // We don't want to bump this into a larger store unless we can
// eliminate the whole 16 byte initialization through it (still, in this case
// it is likely beneficial, but we should see what would that = {} be
expanded
// to, depending on can_store_by_pieces etc.
bar (&s);
}
struct T { char a[1024]; };
void
foo (void)
{
struct T t = {};
t.a[54] = 1;
t.a[52] = 2; // But we can using the info that t = {} cleared the whole
// var merge these two stores, not using unnecessary masking etc. because
// we know what the gaps will contain and can even extend the store
// on either side or both to find optimal store size
bar (&s);
}
>From gcc-bugs-return-627980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 11:35:28 2019
Return-Path: <gcc-bugs-return-627980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115725 invoked by alias); 7 Jan 2019 11:35: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 115628 invoked by uid 48); 7 Jan 2019 11:35:23 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88686] [7/8/9 Regression] gcc generates wrong debug information at -O1
Date: Mon, 07 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.1
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: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88686-4-1Jz1AGp2F9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88686-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00789.txt.bz2
Content-length: 454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88686
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This really should be fixed in GDB.
>From gcc-bugs-return-627981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:06:01 2019
Return-Path: <gcc-bugs-return-627981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15344 invoked by alias); 7 Jan 2019 12:06: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 15252 invoked by uid 48); 7 Jan 2019 12:05:57 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85052] Implement support for clang's __builtin_convertvector
Date: Mon, 07 Jan 2019 12:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85052-4-nOAMfoRDPq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85052-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00790.txt.bz2
Content-length: 919
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85052
--- Comment #12 from Matthias Kretz <kretz at kde dot org> ---
(In reply to Jakub Jelinek from comment #11)
> [...] though for 8x conversions we
> are e.g. on x86 already outside of the realm of natively supported vectors
> (we don't really want MMX and for 1024 bit and wider generic vectors we
> don't always emit best code).
Creatively thinking, consider constants stored as (u)char arrays (for bandwith
optimization), converted to double or (u)llong when used. I'd want to use a
half-SSE load + subsequent conversion to AVX-512 vector (e.g. vpmovsxbq +
vcvtqq2pd) or even full SSE load + one shift and two conversions to AVX-512.
Similar motivation for the reverse direction. (Though a lot less likely to be
used in practice, I believe. Hmm, maybe AI applications can prove that
expectation wrong.)
But we should track optimizations in their own issues.
>From gcc-bugs-return-627982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:06:46 2019
Return-Path: <gcc-bugs-return-627982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16511 invoked by alias); 7 Jan 2019 12:06:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16462 invoked by uid 48); 7 Jan 2019 12:06:41 -0000
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88739] New: union bug on ARM64
Date: Mon, 07 Jan 2019 12:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dongjianqiang2 at huawei 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-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00791.txt.bz2
Content-length: 2304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
Bug ID: 88739
Summary: union bug on ARM64
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dongjianqiang2 at huawei dot com
Target Milestone: ---
Created attachment 45364
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45364&action=edit
demo code to recur error
#include<stdio.h>
typedef unsigned int U32;
typedef unsigned short U16;
typedef unsigned char U8;
typedef struct MEM_HEAD_4DW
{
/* first word */
U32 b11 : 1;
U32 b12 : 3;
U32 b13 : 3;
U32 b14 : 1;
U32 b15 : 16;
U32 b16 : 8;
/* second word */
U32 b21 : 16;
U32 b22 : 1;
U32 b23 : 4;
U32 b24 : 11;
/* third word */
U32 b31 : 32;
/* fourth word */
U32 b30AddrL : 30;
U32 b2AddrType : 2;
}MEM_REQ_HEAD_4DW;
typedef union HEAD_DW4_UNION
{
MEM_REQ_HEAD_4DW strMemHead;
U32 aulValue[4];
U16 ausValue[8];
U8 aucValue[16];
}HEAD_REQ_DW4_UNION;
U32 Test_func(U32 ulAddr)
{
HEAD_REQ_DW4_UNION unData;
unData.strMemHead.b30AddrL = ulAddr >> 2;
unData.strMemHead.b2AddrType = 0;
printf("unData.strMemHead.b30AddrL=0x%x\r\n",unData.strMemHead.b30AddrL);
printf("unData.strMemHead.b2AddrType=0x%x\r\n",unData.strMemHead.b2AddrType);
printf("unData.aulValue[3]=0x%x\r\n",unData.aulValue[3]); // 0000
0000 0000 0001 0000 0010 0010 0100
printf("unData.ausValue[6]=0x%x\r\n",unData.ausValue[6]); // why get
0x0 instead of 0x1 ?
printf("unData.ausValue[7]=0x%x\r\n",unData.ausValue[7]);
return 0;
}
int main()
{
Test_func(0x10224);
return 0;
}
Hi,
For ARM64 big-endian, when compiled above code with -O0, the output of
ausValue[6] is 0x1 which is correct, but when I try to compile with -O1 or -O2,
the output of ausValue[6] is 0x0 which is wrong. Will appreciate if you can
help me look into this issue? is this gcc bug?
>From gcc-bugs-return-627983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:09:35 2019
Return-Path: <gcc-bugs-return-627983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26409 invoked by alias); 7 Jan 2019 12:09: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 26293 invoked by uid 48); 7 Jan 2019 12:09:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Mon, 07 Jan 2019 12:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88568-4-RwYTvOPT8V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00792.txt.bz2
Content-length: 324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45365
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45365&action=edit
gcc9-pr88568.patch
Full untested patch. Can somebody please bootstrap/regtest that on mingw or
cygwin?
>From gcc-bugs-return-627984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:12:39 2019
Return-Path: <gcc-bugs-return-627984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30780 invoked by alias); 7 Jan 2019 12:12: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 30731 invoked by uid 48); 7 Jan 2019 12:12:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Mon, 07 Jan 2019 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88684-4-4aA2dWslcj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00793.txt.bz2
Content-length: 2016
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
I can confirm that:
$ g++ lib.cc -shared -fPIC -o libx.so -fsanitize=undefined && g++ test.cc -lx
-L. -fvisibility=hidden -fsanitize=undefined && ./a.out
3bar (0x7ffff7ff2007), 3bar (0x7ffff7ff2007)
3bar (0x7ffff7ff2007), 3foo (0x402048)
3foo (0x7ffff7ff200c), 3foo (0x402048)
lib.hh:4:8: runtime error: member call on address 0x7fffffffdc38 which does not
point to an object of type 'foo'
0x7fffffffdc38: note: object is of type 'bar'
ff 7f 00 00 50 3d 40 00 00 00 00 00 70 14 40 00 00 00 00 00 eb 6f cf f6 ff
7f 00 00 68 ff ff ff
^~~~~~~~~~~~~~~~~~~~~~~
vptr for 'bar'
with the suggested patch:
$ g++ lib.cc -shared -fPIC -o libx.so -fsanitize=undefined && g++ test.cc -lx
-L. -fsanitize=undefined && ./a.out
3bar (0x7ffff7ff2007), 3bar (0x7ffff7ff2007)
3bar (0x7ffff7ff2007), 3foo (0x402048)
3foo (0x402048), 3foo (0x402048)
Jakub do you prefer to come up with a run-time option or hard-code
SANITIZER_NON_UNIQUE_TYPEINFO == 1?
Btw. llvm looks to survive the test, the difference I see in nm is:
GCC:
$ nm -C a.out | grep 'typeinfo name'
0000000000402048 V typeinfo name for foo
$ nm -C libx.so | grep 'typeinfo name'
0000000000002007 V typeinfo name for bar
000000000000200c V typeinfo name for foo
clang7:
$ nm -C a.out | grep 'typeinfo name'
000000000042ca70 V typeinfo name for foo
000000000042c9f7 V typeinfo name for int (int, char**)
$ nm -C libx.so | grep 'typeinfo name'
000000000000201c R typeinfo name for bar
0000000000002034 V typeinfo name for foo
>From gcc-bugs-return-627985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:14:46 2019
Return-Path: <gcc-bugs-return-627985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33896 invoked by alias); 7 Jan 2019 12:14: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 33831 invoked by uid 48); 7 Jan 2019 12:14:40 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88728] Boostrap with -Og fails with garbled file libgcov-profiler.i
Date: Mon, 07 Jan 2019 12:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88728-4-zqrjRo3dw5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00794.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> I think the proper way of booting with -Og would be setting BOOT_CFLAGS
> rather than CFLAGS/CXXFLAGS. Note the issue might be the use of -save-temps.
I saw the same effecct without -save-temps, I specified this because
I wanted to see what the problem was.
>From gcc-bugs-return-627987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:17:47 2019
Return-Path: <gcc-bugs-return-627987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42198 invoked by alias); 7 Jan 2019 12:17: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 42132 invoked by uid 55); 7 Jan 2019 12:17:42 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Mon, 07 Jan 2019 12:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88598-4-4K5wWddeBh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00796.txt.bz2
Content-length: 1676
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
--- Comment #9 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Mon Jan 7 12:17:10 2019
New Revision: 267646
URL: https://gcc.gnu.org/viewcvs?rev=267646&root=gcc&view=rev
Log:
[2/2] PR88598: Optimise reduc (bit_and)
This patch folds certain reductions of X & CST to X[I] & CST[I] if I is
the only nonzero element of CST. This includes the motivating case in
which CST[I] is -1.
We could do the same for REDUC_MAX on unsigned types, but I wasn't sure
that that special case was worth it.
2019-01-07 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR tree-optimization/88598
* tree.h (single_nonzero_element): Declare.
* tree.c (single_nonzero_element): New function.
* match.pd: Fold certain reductions of X & CST to X[I] & CST[I]
if I is the only nonzero element of CST.
gcc/testsuite/
PR tree-optimization/88598
* gcc.dg/vect/pr88598-1.c: New test.
* gcc.dg/vect/pr88598-2.c: Likewise.
* gcc.dg/vect/pr88598-3.c: Likewise.
* gcc.dg/vect/pr88598-4.c: Likewise.
* gcc.dg/vect/pr88598-5.c: Likewise.
* gcc.dg/vect/pr88598-6.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/vect/pr88598-1.c
trunk/gcc/testsuite/gcc.dg/vect/pr88598-2.c
trunk/gcc/testsuite/gcc.dg/vect/pr88598-3.c
trunk/gcc/testsuite/gcc.dg/vect/pr88598-4.c
trunk/gcc/testsuite/gcc.dg/vect/pr88598-5.c
trunk/gcc/testsuite/gcc.dg/vect/pr88598-6.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree.c
trunk/gcc/tree.h
>From gcc-bugs-return-627986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:17:16 2019
Return-Path: <gcc-bugs-return-627986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41272 invoked by alias); 7 Jan 2019 12:17:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40553 invoked by uid 55); 7 Jan 2019 12:17:09 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Mon, 07 Jan 2019 12:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88598-4-xjoPtDjXkz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00795.txt.bz2
Content-length: 1888
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
--- Comment #8 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Mon Jan 7 12:16:30 2019
New Revision: 267645
URL: https://gcc.gnu.org/viewcvs?rev=267645&root=gcc&view=rev
Log:
[1/2] PR88598: Optimise x * { 0 or 1, 0 or 1, ... }
The PR has:
vect__6.24_42 = vect__5.23_41 * { 0.0, 1.0e+0, 0.0, 0.0 };
which for -fno-signed-zeros -fno-signaling-nans can be simplified to:
vect__6.24_42 = vect__5.23_41 & { 0, -1, 0, 0 };
I deliberately didn't handle COMPLEX_CST or CONSTRUCTOR in
initializer_each_zero_or_onep since there are no current use cases.
The patch also makes (un)signed_type_for handle floating-point types.
I tried to audit all callers and the few that handle null returns would
be unaffected.
2019-01-07 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR tree-optimization/88598
* tree.h (initializer_each_zero_or_onep): Declare.
* tree.c (initializer_each_zero_or_onep): New function.
(signed_or_unsigned_type_for): Handle float types too.
(unsigned_type_for, signed_type_for): Update comments accordingly.
* match.pd: Fold x * { 0 or 1, 0 or 1, ...} to
x & { 0 or -1, 0 or -1, ... }.
gcc/testsuite/
PR tree-optimization/88598
* gcc.dg/pr88598-1.c: New test.
* gcc.dg/pr88598-2.c: Likewise.
* gcc.dg/pr88598-3.c: Likewise.
* gcc.dg/pr88598-4.c: Likewise.
* gcc.dg/pr88598-5.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/pr88598-1.c
trunk/gcc/testsuite/gcc.dg/pr88598-2.c
trunk/gcc/testsuite/gcc.dg/pr88598-3.c
trunk/gcc/testsuite/gcc.dg/pr88598-4.c
trunk/gcc/testsuite/gcc.dg/pr88598-5.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree.c
trunk/gcc/tree.h
>From gcc-bugs-return-627988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:19:00 2019
Return-Path: <gcc-bugs-return-627988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44239 invoked by alias); 7 Jan 2019 12:19: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 44142 invoked by uid 48); 7 Jan 2019 12:18:56 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88598] simplification of multiplication by 1 or 0 fails
Date: Mon, 07 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88598-4-5ts4nWPfzs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00797.txt.bz2
Content-length: 469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88598
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-627989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:20:35 2019
Return-Path: <gcc-bugs-return-627989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46156 invoked by alias); 7 Jan 2019 12:20: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 46064 invoked by uid 48); 7 Jan 2019 12:20:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Mon, 07 Jan 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88684-4-8aXwB5SW9t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00798.txt.bz2
Content-length: 705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Please make |[7/8/9 Regression] Please
|SANITIZER_NON_UNIQUE_TYPEIN |make
|FO a runtime flag (or |SANITIZER_NON_UNIQUE_TYPEIN
|always true) |FO a runtime flag (or
| |always true)
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r241977 when merge from trunk was done.
>From gcc-bugs-return-627990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:20:50 2019
Return-Path: <gcc-bugs-return-627990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46960 invoked by alias); 7 Jan 2019 12:20: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 46873 invoked by uid 48); 7 Jan 2019 12:20:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Mon, 07 Jan 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-Q9qxJHvmFb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00799.txt.bz2
Content-length: 156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
https://reviews.llvm.org/D11502
>From gcc-bugs-return-627991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:27:05 2019
Return-Path: <gcc-bugs-return-627991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81740 invoked by alias); 7 Jan 2019 12:27:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81585 invoked by uid 48); 7 Jan 2019 12:26:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Mon, 07 Jan 2019 12:27: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-4cB6p1vkXT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00800.txt.bz2
Content-length: 721
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Given that the GCC default is
#ifndef __GXX_MERGED_TYPEINFO_NAMES
// By default, typeinfo names are not merged.
#define __GXX_MERGED_TYPEINFO_NAMES 0
#endif
we should use strcmp on Linux too.
Note, what libsanitizer does doesn't match what typeinfo does, which is:
return ((__name == __arg.__name)
|| (__name[0] != '*' &&
__builtin_strcmp (__name, __arg.__name) == 0));
for equality and
{ return (__name[0] == '*' && __arg.__name[0] == '*')
? __name < __arg.__name
: __builtin_strcmp (__name, __arg.__name) < 0; }
for before.
>From gcc-bugs-return-627992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:37:07 2019
Return-Path: <gcc-bugs-return-627992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130815 invoked by alias); 7 Jan 2019 12:37: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 130708 invoked by uid 48); 7 Jan 2019 12:37:03 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Mon, 07 Jan 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution bug_severity
Message-ID: <bug-85949-4-8GNl0eSO25@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00801.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |marxin at gcc dot gnu.org,
| |msebor at gcc dot gnu.org
Resolution|--- |FIXED
Severity|normal |enhancement
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Was improved in r266195, please reopen if it's still not enough.
>From gcc-bugs-return-627993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:43:26 2019
Return-Path: <gcc-bugs-return-627993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13624 invoked by alias); 7 Jan 2019 12:43: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 13563 invoked by uid 48); 7 Jan 2019 12:43:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Mon, 07 Jan 2019 12:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88701-4-xupFKDbBEs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00802.txt.bz2
Content-length: 829
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45366
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45366&action=edit
gcc9-pr88701.patch
For what I wanted to achieve with that change (i.e. put the compound literal
decls in the block scope they belong to), the following works too; it is fine
if the compound literals in the function parameters are handled as before - in
the scope of the function.
>From gcc-bugs-return-627994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:47:36 2019
Return-Path: <gcc-bugs-return-627994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110642 invoked by alias); 7 Jan 2019 12:47: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 88656 invoked by uid 48); 7 Jan 2019 12:47:30 -0000
From: "csaba_22 at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88263] ICE in coverage_begin_function
Date: Mon, 07 Jan 2019 12:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: csaba_22 at yahoo dot co.uk
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88263-4-JIpr80dWB1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00803.txt.bz2
Content-length: 4019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88263
Csaba Ráduly <csaba_22 at yahoo dot co.uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #4 from Csaba Ráduly <csaba_22 at yahoo dot co.uk> ---
Alas, it's not enough.
$ cat ../logger/src/logger2.cc
#include <sstream>
namespace log {
class Logstream {
public:
~Logstream();
private:
/// The logging stream
static thread_local std::ostringstream os_;
};
}
namespace log {
thread_local std::ostringstream Logstream::os_;
Logstream::~Logstream()
{
os_.clear();
}
}
$ g++-99 -v -save-temps --coverage -std=c++11 logger2.cc
Using built-in specs.
COLLECT_GCC=g++-99
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: ../trunk/configure --program-suffix=-99
--enable-version-specific-runtime-libs --enable-languages=c,c++,lto :
(reconfigured) ../trunk/configure --program-suffix=-99
--enable-version-specific-runtime-libs --enable-languages=c,c++,lto :
(reconfigured) ../trunk/configure --program-suffix=-99
--enable-version-specific-runtime-libs --enable-languages=c,c++,lto --no-create
--no-recursion
Thread model: posix
gcc version 9.0.0 20190107 (experimental) (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-coverage' '-std=c++11'
'-shared-libgcc' '-mtune=generic' '-march=x86-64'
/usr/local/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/cc1plus -E -quiet -v
-imultiarch x86_64-linux-gnu -D_GNU_SOURCE logger2.cc -mtune=generic
-march=x86-64 -std=c++11 -fpch-preprocess -o logger2.ii
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory
"/usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/include/c++
/usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/include/c++/x86_64-pc-linux-gnu
/usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/include/c++/backward
/usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/include
/usr/local/include
/usr/local/lib/gcc/x86_64-pc-linux-gnu/9.0.0/include-fixed
/usr/include/x86_64-linux-gnu
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-coverage' '-std=c++11'
'-shared-libgcc' '-mtune=generic' '-march=x86-64'
/usr/local/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/cc1plus -fpreprocessed
logger2.ii -quiet -dumpbase logger2.cc -mtune=generic -march=x86-64 -auxbase
logger2 -std=c++11 -version -fprofile-arcs -ftest-coverage -o logger2.s
GNU C++11 (GCC) version 9.0.0 20190107 (experimental) (x86_64-pc-linux-gnu)
compiled by GNU C version 9.0.0 20190107 (experimental), GMP version
6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU C++11 (GCC) version 9.0.0 20190107 (experimental) (x86_64-pc-linux-gnu)
compiled by GNU C version 9.0.0 20190107 (experimental), GMP version
6.1.2, MPFR version 4.0.1, MPC version 1.1.0, isl version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: 1e0a258bbf182f940eab1b98ac38dd40
during IPA pass: profile
logger2.cc: In function ‘std::ostringstream&
_ZTWN3log9Logstream3os_B5cxx11E()’:
logger2.cc:25:1: internal compiler error: in coverage_begin_function, at
coverage.c:655
25 | }
| ^
0x6ca694 coverage_begin_function(unsigned int, unsigned int)
../../trunk/gcc/basic-block.h:432
0xe843de branch_prob(bool)
../../trunk/gcc/profile.c:1233
0xfeba15 tree_profiling
../../trunk/gcc/tree-profile.c:793
0xfeba15 execute
../../trunk/gcc/tree-profile.c:898
>From gcc-bugs-return-627995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:50:10 2019
Return-Path: <gcc-bugs-return-627995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109596 invoked by alias); 7 Jan 2019 12:50:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108980 invoked by uid 48); 7 Jan 2019 12:50:05 -0000
From: "csaba_22 at yahoo dot co.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88263] ICE in coverage_begin_function
Date: Mon, 07 Jan 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: csaba_22 at yahoo dot co.uk
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88263-4-VsxCbnGOQm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00804.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88263
--- Comment #5 from Csaba Ráduly <csaba_22 at yahoo dot co.uk> ---
Created attachment 45367
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45367&action=edit
preprocessor output from -save-temps for the second version (with destructor)
>From gcc-bugs-return-627996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:52:40 2019
Return-Path: <gcc-bugs-return-627996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80131 invoked by alias); 7 Jan 2019 12:52:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76452 invoked by uid 48); 7 Jan 2019 12:52:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88263] ICE in coverage_begin_function
Date: Mon, 07 Jan 2019 12:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88263-4-IHTcZlJYiQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00805.txt.bz2
Content-length: 152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88263
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, let me fix that.
>From gcc-bugs-return-627997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 12:57:11 2019
Return-Path: <gcc-bugs-return-627997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120417 invoked by alias); 7 Jan 2019 12:57:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120334 invoked by uid 48); 7 Jan 2019 12:57:06 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Mon, 07 Jan 2019 12:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-ZUNwOUqM3Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00806.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #13 from Wilco <wilco at gcc dot gnu.org> ---
So to add some real numbers to the discussion, the average number of iterations
is 4.31. Frequency stats (16 includes all iterations > 16 too):
1: 29.0
2: 4.2
3: 1.0
4: 36.7
5: 8.7
6: 3.4
7: 3.0
8: 2.6
9: 2.1
10: 1.9
11: 1.6
12: 1.2
13: 0.9
14: 0.8
15: 0.7
16: 2.1
So unrolling 4x is perfect for this loop. Note the official xz version has
optimized this loop since 2014(!) using unaligned accesses:
https://git.tukaani.org/?p=xz.git;a=blob;f=src/liblzma/common/memcmplen.h
>From gcc-bugs-return-627998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:11:23 2019
Return-Path: <gcc-bugs-return-627998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12797 invoked by alias); 7 Jan 2019 13:11:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11493 invoked by uid 48); 7 Jan 2019 13:11:18 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Mon, 07 Jan 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88717-4-1D36fQRQlF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00807.txt.bz2
Content-length: 1100
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to åˆ˜è¢‹é¼ from comment #1)
> Pass_insert_vzeroupper uses mode_switch to insert `vzeroupper`.
>
> In function entry and functon body, 256bits/512bits registers are used ,so
> it will set mode as `AVX_U128_DIRTY`. But for function exit no
> 256bits/512bits register is returned, so `AVX_U128_CLEAN` is set.
>
> Then `case AVX_U128_CLEAN` will be triggered for mode switching, maybe we
> should handle ix86_avx_u128_mode_exit.
>
When mode is AVX_U128_DIRTY at the function entry because of function
caller mode is AVX_U128_DIRTY, we should set mode to AVX_U128_DIRTY at
function exit. Will it work?
>From gcc-bugs-return-627999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:11:35 2019
Return-Path: <gcc-bugs-return-627999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14761 invoked by alias); 7 Jan 2019 13:11: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 13657 invoked by uid 48); 7 Jan 2019 13:11:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Mon, 07 Jan 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88611-4-qetuyhgvcM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00808.txt.bz2
Content-length: 419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So maybe even return null_pointer_node; ?
>From gcc-bugs-return-628000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:13:12 2019
Return-Path: <gcc-bugs-return-628000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16122 invoked by alias); 7 Jan 2019 13:13: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 16056 invoked by uid 55); 7 Jan 2019 13:13:07 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Mon, 07 Jan 2019 13:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88721-4-hUOxgC3V87@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00809.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
>> This patch allowed the bootstrap to finish.
>
> There are 3 callers of function_arg_slotno so we would potentially need to add
> 6 initializations already. So I'd rather initialize pregno and ppadding at the
> beginning of the function if this works:
>
> enum mode_class mclass = GET_MODE_CLASS (mode);
>
> /* Silence warnings in the callers. */
> *pregno = -1;
> *ppadding = -1;
>
> if (type && TREE_ADDRESSABLE (type))
> return -1;
I've just successfully finished a sparc-sun-solaris2.11 with it: worked fine.
Thanks.
Rainer
>From gcc-bugs-return-628001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:17:46 2019
Return-Path: <gcc-bugs-return-628001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20958 invoked by alias); 7 Jan 2019 13:17: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 20885 invoked by uid 48); 7 Jan 2019 13:17:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Mon, 07 Jan 2019 13:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc everconfirmed
Message-ID: <bug-88587-4-OFyy2EygZ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00810.txt.bz2
Content-length: 1920
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
CC| |jakub at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Summary|internal compiler error: in |ICE in
|expand_debug_locations, at |expand_debug_locations, at
|cfgexpand.c:5450 |cfgexpand.c:5450
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, there's a reduced test-case:
$ cat pr88587.c
__attribute__((target_clones("default,sse2"))) void a() {
__attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
}
$ gcc -c -m32 -mno-sse -O -g pr88587.c
during RTL pass: expand
pr88587.c: In function ‘a.sse2.0’:
pr88587.c:1:53: internal compiler error: in expand_debug_locations, at
cfgexpand.c:5450
1 | __attribute__((target_clones("default,sse2"))) void a() {
| ^
0x8f386a expand_debug_locations
/home/marxin/Programming/gcc/gcc/cfgexpand.c:5446
0x8f6961 execute
/home/marxin/Programming/gcc/gcc/cfgexpand.c:6505
It's quite strange that following is fine:
$ cat pr88587-2.c
__attribute__((target("default"))) void a() {
__attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
}
__attribute__((target("sse2"))) void a2() {
__attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
}
$ gcc -c -m32 -mno-sse -O -g pr88587-2.c
I'll investigate how precisely the debug insn looks like in both situations.
>From gcc-bugs-return-628002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:19:12 2019
Return-Path: <gcc-bugs-return-628002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29074 invoked by alias); 7 Jan 2019 13:19:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28766 invoked by uid 48); 7 Jan 2019 13:19:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Mon, 07 Jan 2019 13:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88587-4-5Xs5BiHLGz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00811.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
>From gcc-bugs-return-628003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:41:13 2019
Return-Path: <gcc-bugs-return-628003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112502 invoked by alias); 7 Jan 2019 13:41:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109854 invoked by uid 48); 7 Jan 2019 13:41:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Mon, 07 Jan 2019 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-D89GwuUWQc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00812.txt.bz2
Content-length: 6187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
So the problem is that new function body is copied in:
(gdb) bt
#0 __memmove_avx_unaligned_erms () at
../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:342
#1 0x0000000000fd7378 in copy_node (node=node@entry=<var_decl 0x7ffff7feeab0
b>) at /home/marxin/Programming/gcc/gcc/tree.c:1183
#2 0x0000000000db07bf in copy_decl_no_change (decl=<var_decl 0x7ffff7feeab0
b>, id=0x7fffffffd5d0) at /home/marxin/Programming/gcc/gcc/tree-inline.c:5557
#3 0x0000000000db0b2d in remap_decl (decl=<optimized out>, id=0x7fffffffd5d0)
at /home/marxin/Programming/gcc/gcc/tree-inline.c:366
#4 0x0000000000db0d9d in remap_decls (decls=<optimized out>,
nonlocalized_list=0x7ffff6c60508<error reading variable: Cannot access memory
at address 0x4>, id=0x7fffffffd5d0) at
/home/marxin/Programming/gcc/gcc/tree-inline.c:656
#5 0x0000000000db29c2 in remap_block (block=0x7fffffffd498, id=0x7fffffffd5d0)
at /home/marxin/Programming/gcc/gcc/tree.h:3177
#6 0x0000000000db2a86 in remap_blocks (block=<block 0x7ffff6c602a0>,
id=0x7fffffffd5d0) at /home/marxin/Programming/gcc/gcc/tree-inline.c:736
#7 0x0000000000dbd5c8 in tree_function_versioning
(old_decl=old_decl@entry=<function_decl 0x7ffff6c5c200 a>,
new_decl=new_decl@entry=<function_decl 0x7ffff6c5c800 a.sse2.0>,
tree_map=tree_map@entry=0x0, update_clones=update_clones@entry=false,
args_to_skip=args_to_skip@entry=0x0, skip_return=skip_return@entry=false,
blocks_to_copy=<optimized out>, new_entry=<optimized out>) at
/home/marxin/Programming/gcc/gcc/tree.h:3291
#8 0x000000000093f8b1 in cgraph_node::create_version_clone_with_body
(this=this@entry=<cgraph_node * const 0x7ffff6b552d0 "a"/0>,
redirect_callers=..., redirect_callers@entry=..., tree_map=tree_map@entry=0x0,
args_to_skip=args_to_skip@entry=0x0,
skip_return=skip_return@entry=false, bbs_to_copy=bbs_to_copy@entry=0x0,
new_entry_block=<optimized out>, suffix=<optimized out>) at
/home/marxin/Programming/gcc/gcc/cgraphclones.c:1060
#9 0x00000000015d8c18 in create_target_clone (name=0x21fddc0 "sse2",
definition=<optimized out>, node=<cgraph_node * 0x7ffff6b552d0 "a"/0>) at
/home/marxin/Programming/gcc/gcc/multiple_target.c:303
#10 expand_target_clones (definition=<optimized out>, node=<optimized out>) at
/home/marxin/Programming/gcc/gcc/multiple_target.c:403
#11 ipa_target_clone () at
/home/marxin/Programming/gcc/gcc/multiple_target.c:509
#12 (anonymous namespace)::pass_target_clone::execute (this=<optimized out>) at
/home/marxin/Programming/gcc/gcc/multiple_target.c:545
#13 0x0000000000c53605 in execute_one_pass (pass=<opt_pass* 0x220d2a0
"targetclone"(65)>) at /home/marxin/Programming/gcc/gcc/passes.c:2483
#14 0x0000000000c5c0d6 in execute_ipa_pass_list (pass=<opt_pass* 0x220d2a0
"targetclone"(65)>) at /home/marxin/Programming/gcc/gcc/passes.c:2923
#15 0x0000000000939853 in ipa_passes () at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2482
#16 symbol_table::compile (this=0x7ffff6b56100) at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2618
#17 0x000000000093bbed in symbol_table::compile (this=0x7ffff6b56100) at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2863
#18 symbol_table::finalize_compilation_unit (this=0x7ffff6b56100) at
/home/marxin/Programming/gcc/gcc/cgraphunit.c:2863
#19 0x0000000000d3a62b in compile_file () at
/home/marxin/Programming/gcc/gcc/toplev.c:481
#20 0x00000000007a630a in do_compile () at
/home/marxin/Programming/gcc/gcc/toplev.c:2176
#21 toplev::main (this=this@entry=0x7fffffffd9de, argc=<optimized out>,
argc@entry=24, argv=<optimized out>, argv@entry=0x7fffffffdad8) at
/home/marxin/Programming/gcc/gcc/toplev.c:2311
#22 0x00000000007a98eb in main (argc=24, argv=0x7fffffffdad8) at
/home/marxin/Programming/gcc/gcc/main.c:39
so we copy the 'b' with copy_decl_no_change and thus we end up with same mode.
On the other hand when using target("sse2"), the V4SI mode is set here:
#0 layout_decl (decl=<result_decl 0x7ffff6b60d98>, known_align=0) at
/home/marxin/Programming/gcc/gcc/stor-layout.c:605
#1 0x0000000000fc1be2 in build_decl (loc=loc@entry=255680,
code=code@entry=RESULT_DECL, name=name@entry=<tree 0x0>, type=<void_type
0x7ffff6b740a8 void>) at /home/marxin/Programming/gcc/gcc/tree.c:5035
#2 0x00000000007cab6f in start_function (declspecs=declspecs@entry=0x225f0f0,
declarator=declarator@entry=0x225f200, attributes=<optimized out>,
attributes@entry=<tree_list 0x7ffff6c59758>) at
/home/marxin/Programming/gcc/gcc/c/c-decl.c:8991
#3 0x000000000081d8d3 in c_parser_declaration_or_fndef (parser=0x7ffff6b60d20,
fndef_ok=true, static_assert_ok=<optimized out>, empty_ok=<optimized out>,
nested=<optimized out>, start_attr_ok=<optimized out>,
objc_foreach_object_declaration=<optimized out>,
omp_declare_simd_clauses=..., oacc_routine_data=<optimized out>,
fallthru_attr_p=<optimized out>) at
/home/marxin/Programming/gcc/gcc/c/c-parser.c:2256
#4 0x00000000008252e0 in c_parser_external_declaration (parser=0x7ffff6b60d20)
at /home/marxin/Programming/gcc/gcc/c/c-parser.c:1653
#5 0x0000000000825b2a in c_parser_translation_unit (parser=<optimized out>) at
/home/marxin/Programming/gcc/gcc/c/c-parser.c:1534
#6 c_parse_file () at /home/marxin/Programming/gcc/gcc/c/c-parser.c:19807
#7 0x0000000000878de1 in c_common_parse_file () at
/home/marxin/Programming/gcc/gcc/c-family/c-opts.c:1151
#8 0x0000000000d3a3cf in compile_file () at
/home/marxin/Programming/gcc/gcc/toplev.c:456
#9 0x00000000007a630a in do_compile () at
/home/marxin/Programming/gcc/gcc/toplev.c:2176
#10 toplev::main (this=this@entry=0x7fffffffd9ce, argc=<optimized out>,
argc@entry=24, argv=<optimized out>, argv@entry=0x7fffffffdac8) at
/home/marxin/Programming/gcc/gcc/toplev.c:2311
#11 0x00000000007a98eb in main (argc=24, argv=0x7fffffffdac8) at
/home/marxin/Programming/gcc/gcc/main.c:39
So call to relayout_decl will be needed. I'm investigating..
>From gcc-bugs-return-628004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:42:09 2019
Return-Path: <gcc-bugs-return-628004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7185 invoked by alias); 7 Jan 2019 13:42: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 4722 invoked by uid 48); 7 Jan 2019 13:42:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Mon, 07 Jan 2019 13:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88611-4-m2DKuZKHHg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00813.txt.bz2
Content-length: 1138
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
But given that the right type we want is already passed in type, I'd say:
--- gcc/trans-expr.c.jj 2019-01-01 12:37:52.000000000 +0100
+++ gcc/trans-expr.c 2019-01-07 14:41:02.146885618 +0100
@@ -7085,21 +7085,7 @@ gfc_conv_initializer (gfc_expr * expr, g
the 'expr' to be that for a (void *). */
if (expr != NULL && expr->ts.type == BT_DERIVED
&& expr->ts.is_iso_c && expr->ts.u.derived)
- {
- gfc_symbol *derived = expr->ts.u.derived;
-
- /* The derived symbol has already been converted to a (void *). Use
- its kind. */
- if (derived->ts.kind == 0)
- derived->ts.kind = gfc_default_integer_kind;
- expr = gfc_get_int_expr (derived->ts.kind, NULL, 0);
- expr->ts.f90_type = derived->ts.f90_type;
-
- gfc_init_se (&se, NULL);
- gfc_conv_constant (&se, expr);
- gcc_assert (TREE_CODE (se.expr) != CONSTRUCTOR);
- return se.expr;
- }
+ return build_int_cst (type, 0);
if (array && !procptr)
{
is best.
>From gcc-bugs-return-628005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:43:32 2019
Return-Path: <gcc-bugs-return-628005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14936 invoked by alias); 7 Jan 2019 13:43:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14870 invoked by uid 48); 7 Jan 2019 13:43:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88740] New: [7/8/9 Regression] libstdc++ tests no longer print assertion failure messages
Date: Mon, 07 Jan 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00814.txt.bz2
Content-length: 2167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88740
Bug ID: 88740
Summary: [7/8/9 Regression] libstdc++ tests no longer print
assertion failure messages
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
r241069 redefined the VERIFY macro so that instead of using assert it does:
#define VERIFY(fn) \
do \
{ \
if (! (fn)) \
{ \
__builtin_printf("%s:%d: %s: Assertion '%s' failed.\n", \
__FILE__, __LINE__, __PRETTY_FUNCTION__, #fn); \
__builtin_abort(); \
} \
} while (false)
Unlike assert, this prints to stdout not stderr.
Due to some unidentified issue in dejagnu (or expect or tcl or something else)
unflushed output sent to stdout does not get captured by dejagnu and written to
the test logs on recent versions of Fedora (and maybe other distros).
This means that testsuite failures don't show the reason for failure, just an
unhelpful:
spawn [open ...]
FAIL: 27_io/filesystem/operations/remove.cc execution test
The expected result is:
spawn [open ...]
/home/jwakely/src/gcc/libstdc++-v3/testsuite/27_io/filesystem/operations/remove.cc:38:
void test01(): Assertion '!ec' failed.
FAIL: 27_io/filesystem/operations/remove.cc execution test
The missing output can be fixed by including <cstdio> in testsuite_hooks.h and
then either changing __builtin_printf(...) to __builtin_fprintf(stderr, ...) or
alternatively adding a call to fflush(stdout) before the __builtin_abort().
>From gcc-bugs-return-628006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:49:04 2019
Return-Path: <gcc-bugs-return-628006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21880 invoked by alias); 7 Jan 2019 13:49:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21124 invoked by uid 48); 7 Jan 2019 13:48:45 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88737-4-H5dce5E6dq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00815.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #3)
> Indeed. So it would be
>
> *a = {CLOBBER};
>
> which is of course somewhat difficult since we do not know the size
> of the object pointed to.
One thing we discussed before is having a pass (like FRE?) transform the read
*a into an uninitialized default-def ssa_name when it notices that the previous
must-alias/clobber write is free (except that free is not considered a
write/clobber IIRC).
>From gcc-bugs-return-628007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:50:11 2019
Return-Path: <gcc-bugs-return-628007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23034 invoked by alias); 7 Jan 2019 13:50:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22927 invoked by uid 48); 7 Jan 2019 13:50:07 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Mon, 07 Jan 2019 13:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
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-88611-4-R9yQygYhbu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00816.txt.bz2
Content-length: 1322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> But given that the right type we want is already passed in type, I'd say:
> --- gcc/trans-expr.c.jj 2019-01-01 12:37:52.000000000 +0100
> +++ gcc/trans-expr.c 2019-01-07 14:41:02.146885618 +0100
> @@ -7085,21 +7085,7 @@ gfc_conv_initializer (gfc_expr * expr, g
> the 'expr' to be that for a (void *). */
> if (expr != NULL && expr->ts.type == BT_DERIVED
> && expr->ts.is_iso_c && expr->ts.u.derived)
> - {
> - gfc_symbol *derived = expr->ts.u.derived;
> -
> - /* The derived symbol has already been converted to a (void *). Use
> - its kind. */
> - if (derived->ts.kind == 0)
> - derived->ts.kind = gfc_default_integer_kind;
> - expr = gfc_get_int_expr (derived->ts.kind, NULL, 0);
> - expr->ts.f90_type = derived->ts.f90_type;
> -
> - gfc_init_se (&se, NULL);
> - gfc_conv_constant (&se, expr);
> - gcc_assert (TREE_CODE (se.expr) != CONSTRUCTOR);
> - return se.expr;
> - }
> + return build_int_cst (type, 0);
>
> if (array && !procptr)
> {
> is best.
I regression-tested this, without issues.
Pre-approved for trunk (or obvious and simple).
>From gcc-bugs-return-628008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:53:44 2019
Return-Path: <gcc-bugs-return-628008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33271 invoked by alias); 7 Jan 2019 13:53:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32972 invoked by uid 48); 7 Jan 2019 13:53:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Mon, 07 Jan 2019 13:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88611-4-CePAkimO2k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00817.txt.bz2
Content-length: 383
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
>From gcc-bugs-return-628009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 13:58:47 2019
Return-Path: <gcc-bugs-return-628009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101463 invoked by alias); 7 Jan 2019 13:58:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96600 invoked by uid 55); 7 Jan 2019 13:58:41 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Mon, 07 Jan 2019 13:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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-88398-4-VUNvZR7IaA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00818.txt.bz2
Content-length: 1100
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 7 Jan 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
>
> --- Comment #13 from Wilco <wilco at gcc dot gnu.org> ---
> So to add some real numbers to the discussion, the average number of iterations
> is 4.31. Frequency stats (16 includes all iterations > 16 too):
>
> 1: 29.0
> 2: 4.2
> 3: 1.0
> 4: 36.7
> 5: 8.7
> 6: 3.4
> 7: 3.0
> 8: 2.6
> 9: 2.1
> 10: 1.9
> 11: 1.6
> 12: 1.2
> 13: 0.9
> 14: 0.8
> 15: 0.7
> 16: 2.1
>
> So unrolling 4x is perfect for this loop. Note the official xz version has
> optimized this loop since 2014(!) using unaligned accesses:
> https://git.tukaani.org/?p=xz.git;a=blob;f=src/liblzma/common/memcmplen.h
I guess if we'd have some data to guide then classical unrolling using
duffs device would be best here? Because peeling will increase the
number of dynamic branches and likely the actual distribution of
#iterations isn't so that they will be well predicted?
>From gcc-bugs-return-628010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:02:16 2019
Return-Path: <gcc-bugs-return-628010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118740 invoked by alias); 7 Jan 2019 14:02: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 118618 invoked by uid 48); 7 Jan 2019 14:02:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Mon, 07 Jan 2019 14:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-sx3IrIV2eX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00819.txt.bz2
Content-length: 977
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> Given that the GCC default is
> #ifndef __GXX_MERGED_TYPEINFO_NAMES
> // By default, typeinfo names are not merged.
> #define __GXX_MERGED_TYPEINFO_NAMES 0
> #endif
> we should use strcmp on Linux too.
> Note, what libsanitizer does doesn't match what typeinfo does, which is:
> return ((__name == __arg.__name)
> || (__name[0] != '*' &&
> __builtin_strcmp (__name, __arg.__name) == 0));
> for equality and
> { return (__name[0] == '*' && __arg.__name[0] == '*')
> ? __name < __arg.__name
> : __builtin_strcmp (__name, __arg.__name) < 0; }
> for before.
Do you suggest to propose an upstream change where I'll enable that for Linux
and I'll also adjust the equality operator? Or do we prefer to adjust that
locally GCC project?
>From gcc-bugs-return-628011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:04:17 2019
Return-Path: <gcc-bugs-return-628011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121508 invoked by alias); 7 Jan 2019 14:04:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121436 invoked by uid 48); 7 Jan 2019 14:04:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Mon, 07 Jan 2019 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: wilco at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-hZA6EWOwMR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00820.txt.bz2
Content-length: 365
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Not everything is optimized during GIMPLE optimizations, we have simplify-rtx.c
and combine.c for a reason. So, if it is possible to accurately describe the
behavior of the instruction without UNSPECs, it is generally preferable to do
so.
>From gcc-bugs-return-628012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:04:33 2019
Return-Path: <gcc-bugs-return-628012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122283 invoked by alias); 7 Jan 2019 14:04:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122181 invoked by uid 48); 7 Jan 2019 14:04:24 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Mon, 07 Jan 2019 14: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88684-4-cPuQZM7qQ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00821.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
>From gcc-bugs-return-628013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:12:36 2019
Return-Path: <gcc-bugs-return-628013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76542 invoked by alias); 7 Jan 2019 14: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 72590 invoked by uid 48); 7 Jan 2019 14:12:32 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] [9 Regression] Spurious "redundant move in return statement"
Date: Mon, 07 Jan 2019 14:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88692-4-NRJdHFbao7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00822.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
>From gcc-bugs-return-628014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:25:16 2019
Return-Path: <gcc-bugs-return-628014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90369 invoked by alias); 7 Jan 2019 14:25:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90272 invoked by uid 48); 7 Jan 2019 14:25:09 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87305] [9 Regression] Segfault in end_hard_regno in setup_live_pseudos_and_spill_after_risky_transforms on aarch64 big-endian
Date: Mon, 07 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87305-4-rOihB9caCK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00823.txt.bz2
Content-length: 2305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87305
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This is in code added in r244942:
198204 vmakarov if (!lra_reg_val_equal_p (conflict_regno, val, offset)
192719 vmakarov /* If it is multi-register pseudos they should
start on
192719 vmakarov the same hard register. */
192719 vmakarov || hard_regno != reg_renumber[conflict_regno])
244942 vmakarov {
244942 vmakarov int conflict_hard_regno =
reg_renumber[conflict_regno];
244942 vmakarov machine_mode biggest_mode =
lra_reg_info[conflict_regno].biggest_mode;
252014 rsandifo int biggest_nregs = hard_regno_nregs
(conflict_hard_regno,
252014 rsandifo
biggest_mode);
252014 rsandifo int nregs_diff
252014 rsandifo = (biggest_nregs
252014 rsandifo - hard_regno_nregs (conflict_hard_regno,
252014 rsandifo PSEUDO_REGNO_MODE
(conflict_regno)));
244942 vmakarov add_to_hard_reg_set (&conflict_set,
244942 vmakarov biggest_mode,
244942 vmakarov conflict_hard_regno
244942 vmakarov - (WORDS_BIG_ENDIAN ?
nregs_diff : 0));
244942 vmakarov }
hard_regno is 3, conflict_regno 94, reg_renumber[conflict_regno] aka
conflict_hard_regno 0.
biggest_mode is V4SImode, biggest_nregs 2, PSEUDO_REGNO_MODE is SImode and so
nregs_diff is 1.
But, as conflict_hard_regno is 0, this actually means we call
add_to_hard_reg_set with -1U as the last argument.
Vlad, could you please have a look?
Do we allow V4SImode to be allocated on any regnos, or just multiples of the
size?
Should we e.g. in a loop find out for WORDS_BIG_ENDIAN which of the regnos from
MAX (conflict_hard_regno - nregs_diff, 0) to conflict_hard_regno inclusive
first satisfies
targetm.hard_regno_mode_ok (regno, biggest_mode) and use that regno for the
add_to_hard_reg_set
argument? Or just do there the MAX (conflict_hard_regno - (WORDS_BIG_ENDIAN ?
nregs_diff : 0), 0) ?
>From gcc-bugs-return-628015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:33:07 2019
Return-Path: <gcc-bugs-return-628015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19607 invoked by alias); 7 Jan 2019 14:33: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 19468 invoked by uid 48); 7 Jan 2019 14:33:01 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Mon, 07 Jan 2019 14:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-86891-4-GJm8WBqtI5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00824.txt.bz2
Content-length: 758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|wilco at gcc dot gnu.org |rearnsha at gcc dot gnu.org
--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> Not everything is optimized during GIMPLE optimizations, we have
> simplify-rtx.c and combine.c for a reason. So, if it is possible to
> accurately describe the behavior of the instruction without UNSPECs, it is
> generally preferable to do so.
It is possible, and I'm just polishing up a patch that does so.
>From gcc-bugs-return-628016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:41:40 2019
Return-Path: <gcc-bugs-return-628016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62352 invoked by alias); 7 Jan 2019 14:41:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62293 invoked by uid 48); 7 Jan 2019 14:41:36 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84436] [8/9 Regression] Missed optimization with switch on enum constants returning the same value
Date: Mon, 07 Jan 2019 14:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84436-4-genkvPZT39@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00825.txt.bz2
Content-length: 2537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84436
--- Comment #12 from Romain Geissler <romain.geissler at amadeus dot com> ---
Hi,
I have tried the following script directly inside docker using the official
"debian:buster" docker image, so I hope it will not require much more
dependencies than what is written here.
Tested with x86-64.
<<END_OF_SCRIPT
#!/bin/bash
set -e
# Install a few dependencies
apt-get update
apt-get install -y curl tar build-essential cmake python
LLVM_DIRECTORY=/llvm
LLVM_TAR="http://releases.llvm.org/7.0.1/llvm-7.0.1.src.tar.xz"
CLANG_TAR="http://releases.llvm.org/7.0.1/cfe-7.0.1.src.tar.xz"
COMPILER_RT_TAR="http://releases.llvm.org/7.0.1/compiler-rt-7.0.1.src.tar.xz"
mkdir -p "${LLVM_DIRECTORY}/src"
mkdir -p "${LLVM_DIRECTORY}/build"
cd "${LLVM_DIRECTORY}/src"
curl "${LLVM_TAR}" | tar -Jx --strip-components=1 -f -
mkdir -p "${LLVM_DIRECTORY}/src/tools/clang"
cd "${LLVM_DIRECTORY}/src/tools/clang"
curl "${CLANG_TAR}" | tar -Jx --strip-components=1 -f -
mkdir -p "${LLVM_DIRECTORY}/src/projects/compiler-rt"
cd "${LLVM_DIRECTORY}/src/projects/compiler-rt"
curl "${COMPILER_RT_TAR}" | tar -Jx --strip-components=1 -f -
cd "${LLVM_DIRECTORY}/build"
cmake -G "Unix Makefiles" -C
"${LLVM_DIRECTORY}/src/tools/clang/cmake/caches/PGO.cmake"
"${LLVM_DIRECTORY}/src"
make -j 32 stage2-instrumented-generate-profdata
END_OF_SCRIPT
in order to use your own gcc, make sure that you update the $PATH environment
variable when running cmake/make.
I suggest you build clang both with and without your fix in gcc, then explore
the whole build tree and find all *.o files which differ (I hope there aren't a
lot), to check why they behave differently.
Note that it seems like gcc had an earlier regression, making the clang
bootstrap fail a bit later after building compiler-rt, with an error like:
FAILED: tools/clang/include/clang/AST/StmtNodes.inc
cd /workdir/build/final-system/llvm-build/tools/clang/stage2-instrumented-bins
&&
/workdir/build/final-system/llvm-build/tools/clang/stage2-instrumented-bins/bin/clang-tblgen
-gen-clang-stmt-nodes -I /workdir/src/llvm-8.0.0/clang/include/clang/AST -I
/workdir/src/llvm-8.0.0/llvm/include
/workdir/src/llvm-8.0.0/clang/include/clang/AST/../Basic/StmtNodes.td -o
tools/clang/include/clang/AST/StmtNodes.inc -d
tools/clang/include/clang/AST/StmtNodes.inc.d
This is an unrelated error, which I think comes from a gcc regression too, and
which I will bisect as well.
If you need more info, just ask.
Cheers,
Romain
>From gcc-bugs-return-628017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:42:58 2019
Return-Path: <gcc-bugs-return-628017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64849 invoked by alias); 7 Jan 2019 14:42:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64110 invoked by uid 48); 7 Jan 2019 14:42:52 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Mon, 07 Jan 2019 14:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88717-4-f5XHrOUHIa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00826.txt.bz2
Content-length: 1774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
Like this
diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
index d01278d866f..9b49a2c1d9c 100644
--- a/gcc/config/i386/i386.c
+++ b/gcc/config/i386/i386.c
@@ -19100,7 +19100,11 @@ ix86_avx_u128_mode_entry (void)
rtx incoming = DECL_INCOMING_RTL (arg);
if (incoming && ix86_check_avx_upper_register (incoming))
- return AVX_U128_DIRTY;
+ {
+ /* Caller is AVX_U128_DIRTY. */
+ cfun->machine->caller_avx_u128_dirty = true;
+ return AVX_U128_DIRTY;
+ }
}
return AVX_U128_CLEAN;
@@ -19130,6 +19134,10 @@ ix86_mode_entry (int entity)
static int
ix86_avx_u128_mode_exit (void)
{
+ /* Exit mode is set to AVX_U128_DIRTY if caller is AVX_U128_DIRTY. */
+ if (cfun->machine->caller_avx_u128_dirty)
+ return AVX_U128_DIRTY;
+
rtx reg = crtl->return_rtx;
/* Exit mode is set to AVX_U128_DIRTY if there are 256bit
diff --git a/gcc/config/i386/i386.h b/gcc/config/i386/i386.h
index 83b025e0cf5..c053b657a55 100644
--- a/gcc/config/i386/i386.h
+++ b/gcc/config/i386/i386.h
@@ -2747,6 +2747,9 @@ struct GTY(()) machine_function {
/* If true, ENDBR is queued at function entrance. */
BOOL_BITFIELD endbr_queued_at_entrance : 1;
+ /* If true, caller is AVX_U128_DIRTY. */
+ BOOL_BITFIELD caller_avx_u128_dirty : 1;
+
/* The largest alignment, in bytes, of stack slot actually used. */
unsigned int max_used_stack_alignment;
>From gcc-bugs-return-628018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:46:31 2019
Return-Path: <gcc-bugs-return-628018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61668 invoked by alias); 7 Jan 2019 14:46: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 36250 invoked by uid 48); 7 Jan 2019 14:46:07 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Mon, 07 Jan 2019 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88611-4-e2MM7Ozg8L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00827.txt.bz2
Content-length: 4195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #6)
> (In reply to Jakub Jelinek from comment #5)
> > But given that the right type we want is already passed in type, I'd say:
> > --- gcc/trans-expr.c.jj 2019-01-01 12:37:52.000000000 +0100
> > +++ gcc/trans-expr.c 2019-01-07 14:41:02.146885618 +0100
> > @@ -7085,21 +7085,7 @@ gfc_conv_initializer (gfc_expr * expr, g
> > the 'expr' to be that for a (void *). */
> > if (expr != NULL && expr->ts.type == BT_DERIVED
> > && expr->ts.is_iso_c && expr->ts.u.derived)
> > - {
> > - gfc_symbol *derived = expr->ts.u.derived;
> > -
> > - /* The derived symbol has already been converted to a (void *). Use
> > - its kind. */
> > - if (derived->ts.kind == 0)
> > - derived->ts.kind = gfc_default_integer_kind;
> > - expr = gfc_get_int_expr (derived->ts.kind, NULL, 0);
> > - expr->ts.f90_type = derived->ts.f90_type;
> > -
> > - gfc_init_se (&se, NULL);
> > - gfc_conv_constant (&se, expr);
> > - gcc_assert (TREE_CODE (se.expr) != CONSTRUCTOR);
> > - return se.expr;
> > - }
> > + return build_int_cst (type, 0);
> >
> > if (array && !procptr)
> > {
> > is best.
>
> I regression-tested this, without issues.
>
> Pre-approved for trunk (or obvious and simple).
So unfortunately it doesn't work but ICEs
FAIL: gfortran.dg/c_loc_tests_12.f03 -O (internal compiler error)
FAIL: gfortran.dg/c_loc_tests_12.f03 -O (test for excess errors)
FAIL: gfortran.dg/c_loc_tests_6.f03 -O (internal compiler error)
FAIL: gfortran.dg/c_loc_tests_6.f03 -O (test for excess errors)
FAIL: gfortran.dg/c_loc_tests_7.f03 -O (internal compiler error)
FAIL: gfortran.dg/c_loc_tests_7.f03 -O (test for excess errors)
FAIL: gfortran.dg/c_loc_tests_8.f03 -O (internal compiler error)
FAIL: gfortran.dg/c_loc_tests_8.f03 -O (test for excess errors)
where for example for c_loc_tests_12.f03 we end up with type being an
ARRAY_TYPE:
(gdb) p debug_tree (type)
<array_type 0x7ffff6a45738
type <pointer_type 0x7ffff6896000
type <void_type 0x7ffff688ff18 void VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff688ff18
pointer_to_this <pointer_type 0x7ffff6896000>>
public unsigned DI
size <integer_cst 0x7ffff687ab70 constant 64>
unit-size <integer_cst 0x7ffff687ab88 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7ffff6896000
pointer_to_this <pointer_type 0x7ffff689b738> reference_to_this
...
(gdb) p expr->ts.u.derived->ts.f90_type
$5 = BT_VOID
I wonder if in this case we want to return an empty CONSTRUCTOR instead?
Can c_null_ptr appear in a struct initialization as well, literally
as it seems to be the case for arrays?
type(c_ptr), dimension(1), target :: argv = c_null_ptr
Thus, amended patch which passes the affected testcases:
diff --git a/gcc/fortran/trans-expr.c b/gcc/fortran/trans-expr.c
index 27eb2d2ee38..c45752e516a 100644
--- a/gcc/fortran/trans-expr.c
+++ b/gcc/fortran/trans-expr.c
@@ -7086,19 +7086,12 @@ gfc_conv_initializer (gfc_expr * expr, gfc_typespec *
ts, tree type,
if (expr != NULL && expr->ts.type == BT_DERIVED
&& expr->ts.is_iso_c && expr->ts.u.derived)
{
- gfc_symbol *derived = expr->ts.u.derived;
-
- /* The derived symbol has already been converted to a (void *). Use
- its kind. */
- if (derived->ts.kind == 0)
- derived->ts.kind = gfc_default_integer_kind;
- expr = gfc_get_int_expr (derived->ts.kind, NULL, 0);
- expr->ts.f90_type = derived->ts.f90_type;
-
- gfc_init_se (&se, NULL);
- gfc_conv_constant (&se, expr);
- gcc_assert (TREE_CODE (se.expr) != CONSTRUCTOR);
- return se.expr;
+ if (TREE_CODE (type) == ARRAY_TYPE)
+ return build_constructor (type, NULL);
+ else if (POINTER_TYPE_P (type))
+ return build_int_cst (type, 0);
+ else
+ gcc_unreachable ();
}
if (array && !procptr)
>From gcc-bugs-return-628019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:46:42 2019
Return-Path: <gcc-bugs-return-628019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73394 invoked by alias); 7 Jan 2019 14:46:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67635 invoked by uid 48); 7 Jan 2019 14:46:37 -0000
From: "lh_mouse at 126 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61189] ICE with __builtin_return_address() in noexcept lambda on x86
Date: Mon, 07 Jan 2019 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lh_mouse at 126 dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-61189-4-euiNAxxpK3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61189-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61189-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00828.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61189
Liu Hao <lh_mouse at 126 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Liu Hao <lh_mouse at 126 dot com> ---
This is confirmed to have been fixed as of GCC 8.2. The exact version is
unknown, however.
>From gcc-bugs-return-628020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:49:51 2019
Return-Path: <gcc-bugs-return-628020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38659 invoked by alias); 7 Jan 2019 14:49:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30023 invoked by uid 55); 7 Jan 2019 14:49:45 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Mon, 07 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-dd2UdJAehJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00829.txt.bz2
Content-length: 3254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #8 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Mon Jan 7 14:49:00 2019
New Revision: 267650
URL: https://gcc.gnu.org/viewcvs?rev=267650&root=gcc&view=rev
Log:
Investigating PR target/86891 revealed a number of issues with the way
the AArch64 backend was handing overflow detection patterns. Firstly,
expansion for signed and unsigned types is not the same as in one form
the overflow is detected via the C flag and in the other it is done
via the V flag in the PSR. Secondly, particular care has to be taken
when describing overflow of signed types: the comparison has to be
performed conceptually on a value that cannot overflow and compared to
a value that might have overflowed.
It became apparent that some of the patterns were simply unmatchable
(they collapse to NEG in the RTL rather than subtracting from zero)
and a number of patterns were overly restrictive in terms of the
immediate constants that they supported. I've tried to address all of
these issues as well.
gcc:
PR target/86891
* config/aarch64/aarch64.c (aarch64_expand_subvti): New parameter
unsigned_p. Handle signed and unsigned overflow correction as
required.
* config/aarch64/aarch64-protos.h (aarch64_expand_subvti): Update
prototype.
* config/aarch64/aarch64.md (addv<mode>4): Use aarch64_plus_operand
for operand 2.
(add<mode>3_compareV_imm): Make this callable for expanding.
(subv<GPI:mode>4): Use register_operand for operand 1. Use
aarch64_plus_operand for operand 2.
(subv<GPI:mode>_insn): New insn pattern.
(subv<GPI:mode>_imm): Likewise.
(negv<GPI:mode>3): New expand pattern.
(negv<GPI:mode>_insn): New insn pattern.
(negv<GPI:mode>_cmp_only): Likewise.
(cmpv<GPI:mode>_insn): Likewise.
(subvti4): Use register_operand for operand 1. Update call to
aarch64_expand_subvti.
(usubvti4): Likewise.
(negvti3): New expand pattern.
(negdi_carryout): New insn pattern.
(negvdi_carryinV): New insn pattern.
(sub<mode3>_compare1_imm): Delete named insn pattern, make anonymous
version the named version.
(peepholes to convert to sub<mode3>_compare1_imm): Adjust order of
operands.
(usub<GPI:mode>3_carryinC, usub<GPI:mode>3_carryinC_z1): New insn
patterns.
(usub<GPI:mode>3_carryinC_z2, usub<GPI:mode>3_carryinC): New insn
patterns.
(sub<mode>3_carryinCV, sub<mode>3_carryinCV_z1_z2): Delete.
(sub<mode>3_carryinCV_z1, sub<mode>3_carryinCV_z2): Delete.
(sub<mode>3_carryinCV): Delete.
(sub<GPI:mode>3_carryinV): New expand pattern.
sub<mode>3_carryinV, sub<mode>3_carryinV_z2): New insn patterns.
testsuite:
* gcc.target/aarch64/subs_compare_2.c: Make '#' immediate prefix
optional in scan pattern.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/aarch64/aarch64-protos.h
trunk/gcc/config/aarch64/aarch64.c
trunk/gcc/config/aarch64/aarch64.md
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/aarch64/subs_compare_2.c
>From gcc-bugs-return-628021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:53:17 2019
Return-Path: <gcc-bugs-return-628021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106153 invoked by alias); 7 Jan 2019 14:53:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106100 invoked by uid 48); 7 Jan 2019 14:53:13 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Mon, 07 Jan 2019 14:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86891-4-RbZuDg0KFN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00830.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:59:26 2019
Return-Path: <gcc-bugs-return-628022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16425 invoked by alias); 7 Jan 2019 14:59:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16320 invoked by uid 55); 7 Jan 2019 14:59:21 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87787] [UBSAN] runtime error: null pointer passed as argument 2, which is declared to never be null
Date: Mon, 07 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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:
Message-ID: <bug-87787-4-TCTlNDZ9I8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00831.txt.bz2
Content-length: 1181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87787
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jan 7 14:58:44 2019
New Revision: 267651
URL: https://gcc.gnu.org/viewcvs?rev=267651&root=gcc&view=rev
Log:
PR libstdc++/87787 avoid undefined null args to memcpy and memmove
The C++ char_traits and ctype APIs do not disallow null pointer
arguments, so we need explicit checks to ensure we don't forward null
pointers to memcpy or memmove.
PR libstdc++/87787
* include/bits/char_traits.h (char_traits::move): Do not pass null
pointers to memmove.
* include/bits/locale_facets.h
(ctype<char>::widen(const char*, const char*, char*)): Do not
pass null pointers to memcpy.
(ctype<char>::narrow(const char*, const char*, char, char*)):
Likewise.
(ctype<char>::do_widen(const char*, const char*, char*)):
Likewise.
(ctype<char>::do_narrow(const char*, const char*, char, char*)):
Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/char_traits.h
trunk/libstdc++-v3/include/bits/locale_facets.h
>From gcc-bugs-return-628024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:59:43 2019
Return-Path: <gcc-bugs-return-628024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23492 invoked by alias); 7 Jan 2019 14:59: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 21140 invoked by uid 48); 7 Jan 2019 14:59:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63426] [meta-bug] Issues found with -fsanitize=undefined
Date: Mon, 07 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-63426-4-FyaLYIGMyx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00833.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
Bug 63426 depends on bug 87787, which changed state.
Bug 87787 Summary: [UBSAN] runtime error: null pointer passed as argument 2, which is declared to never be null
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87787
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 14:59:43 2019
Return-Path: <gcc-bugs-return-628023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23315 invoked by alias); 7 Jan 2019 14:59: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 20572 invoked by uid 48); 7 Jan 2019 14:59:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87787] [UBSAN] runtime error: null pointer passed as argument 2, which is declared to never be null
Date: Mon, 07 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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
Message-ID: <bug-87787-4-Mw7vvgFERt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00832.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87787
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The other issues are real problems, and are now fixed.
>From gcc-bugs-return-628025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:01:19 2019
Return-Path: <gcc-bugs-return-628025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28981 invoked by alias); 7 Jan 2019 15:01:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27527 invoked by uid 48); 7 Jan 2019 15:00:38 -0000
From: "steinar+gcc at gunderson dot no" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88741] New: [9 Regression] Spurious "too long" error inside template
Date: Mon, 07 Jan 2019 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steinar+gcc at gunderson dot no
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00834.txt.bz2
Content-length: 2418
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88741
Bug ID: 88741
Summary: [9 Regression] Spurious "too long" error inside
template
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: steinar+gcc at gunderson dot no
Target Milestone: ---
Hi,
Since recent GCC 9 snapshots, this code now fails:
template <class T>
void foo() {
char row[] = {"test"};
}
void bar() {
foo<int>();
}
I believe it's spurious, since the code works fine outside a template. Works
with GCC 8 and Clang 7.
atum17:~> /usr/lib/gcc-snapshot/bin/g++ -v
Using built-in specs.
COLLECT_GCC=/usr/lib/gcc-snapshot/bin/g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc-snapshot/libexec/gcc/x86_64-linux-gnu/9/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 20190102-1'
--with-bugurl=file:///usr/share/doc/gcc-snapshot/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++
--prefix=/usr/lib/gcc-snapshot --with-gcc-major-version-only --program-prefix=
--enable-shared --enable-linker-build-id --disable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-plugin --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --enable-checking=yes
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 9.0.0 20190102 (experimental) [trunk revision 267505] (Debian
20190102-1)
atum17:~> /usr/lib/gcc-snapshot/bin/g++ -c test.cc
test.cc: In instantiation of 'void foo() [with T = int]':
test.cc:3:23: required from here
test.cc:1:47: error: initializer-string for array of chars is too long
[-fpermissive]
1 | template <class T> void foo() { char row[] = {"test"}; }
|
>From gcc-bugs-return-628026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:06:30 2019
Return-Path: <gcc-bugs-return-628026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83179 invoked by alias); 7 Jan 2019 15:06:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83127 invoked by uid 48); 7 Jan 2019 15:06:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88545] std::find compile to memchr in trivial random access cases (patch)
Date: Mon, 07 Jan 2019 15:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
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 bug_severity
Message-ID: <bug-88545-4-4EtvSUX8Az@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88545-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88545-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00835.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88545
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
Severity|normal |enhancement
>From gcc-bugs-return-628027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:10:58 2019
Return-Path: <gcc-bugs-return-628027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35615 invoked by alias); 7 Jan 2019 15:10: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 33216 invoked by uid 48); 7 Jan 2019 15:10:53 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88741] [9 Regression] Spurious "too long" error inside template
Date: Mon, 07 Jan 2019 15:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88741-4-Dwv5nNJCoY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00836.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88741
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
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 r267272.
>From gcc-bugs-return-628028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:11:50 2019
Return-Path: <gcc-bugs-return-628028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43983 invoked by alias); 7 Jan 2019 15:11: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 43842 invoked by uid 48); 7 Jan 2019 15:11:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 15:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88572-4-26psW1H5oz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00837.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Will Wray from comment #0)
> The discussion thread is here:
> http://clang-developers.42468.n3.nabble.com/braces-around-scalar-initializer-
> warning-should-be-error-td4063311.html
A proper link, because nabble is abysmal:
http://lists.llvm.org/pipermail/cfe-dev/2018-December/060598.html
>From gcc-bugs-return-628029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:11:53 2019
Return-Path: <gcc-bugs-return-628029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44434 invoked by alias); 7 Jan 2019 15:11: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 43927 invoked by uid 48); 7 Jan 2019 15:11:47 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Mon, 07 Jan 2019 15:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-hSmoJve1VM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00838.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #10 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #9)
> Fixed.
Yes looking at git blame all of the addv/subv support was added for GCC9, so no
backporting is needed.
>From gcc-bugs-return-628030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:19:08 2019
Return-Path: <gcc-bugs-return-628030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40294 invoked by alias); 7 Jan 2019 15:19:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40194 invoked by uid 48); 7 Jan 2019 15:19:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 15:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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-88572-4-4FJuERzLPM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00839.txt.bz2
Content-length: 1490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The relevant code is:
/* It is invalid to initialize a non-aggregate type with a
brace-enclosed initializer before C++0x.
We need to check for BRACE_ENCLOSED_INITIALIZER_P here because
of g++.old-deja/g++.mike/p7626.C: a pointer-to-member constant is
a CONSTRUCTOR (with a record type). */
if (TREE_CODE (stripped_init) == CONSTRUCTOR
/* Don't complain about a capture-init. */
&& !CONSTRUCTOR_IS_DIRECT_INIT (stripped_init)
&& BRACE_ENCLOSED_INITIALIZER_P (stripped_init)) /* p7626.C */
{
if (SCALAR_TYPE_P (type))
{
if (cxx_dialect < cxx11
/* Isn't value-initialization. */
|| CONSTRUCTOR_NELTS (stripped_init) > 0)
{
if (complain & tf_error)
error ("braces around scalar initializer for type %qT",
type);
init = error_mark_node;
}
}
The condition means we give an error for any braced-init-list in C++98, and for
a non-empty braced-init-list in later dialects . But the latter condition is
wrong, it should allow a single element (and presumably more than one element
will be rejected as an invalid initializer anyway).
I'm not even sure we should warn about this.
>From gcc-bugs-return-628031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:23:03 2019
Return-Path: <gcc-bugs-return-628031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52809 invoked by alias); 7 Jan 2019 15:23:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52701 invoked by uid 48); 7 Jan 2019 15:22:56 -0000
From: "gary_mills at fastmail dot fm" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Mon, 07 Jan 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary_mills at fastmail dot fm
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-0PhfOBn1nz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00840.txt.bz2
Content-length: 2353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #28 from Gary Mills <gary_mills at fastmail dot fm> ---
I installed the patch mentioned above to bypass that error. Now, with this
minimal configuration:
$
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
--without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
I got a successful build. Still, we are not quite at the root cause. This
result does suggest that something in the previous configuration caused the
ICE. Note that /usr/local, the default prefix, does not exist. Also,
/usr/gcc/7, the desired prefix, does not exist. I'm going to try to
re-introduce some of the previous configuration to identify what causes the
ICE. This will take some time, as each build takes about three days. Any
suggestions about the culprit in the previous configuration will be
appreciated.
I do see this error in all six copies of libgcc/config.log:
configure:3471:
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/xgcc
-B/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/
-B/usr/local/sparc-sun-solaris2.11/bin/ -B/usr/local/sparc-sun-solaris2.11/lib/
-isystem /usr/local/sparc-sun-solaris2.11/include -isystem
/usr/local/sparc-sun-solaris2.11/sys-include -o conftest -g -O2 conftest.c
>&5
ld: fatal: file crtp.o: open failed: No such file or directory
ld: fatal: file crtbegin.o: open failed: No such file or directory
ld: fatal: file crtend.o: open failed: No such file or directory
ld: fatal: file processing errors. No output written to conftest
collect2: error: ld returned 1 exit status
configure:3474: $? = 1
configure:3662: checking for suffix of object files
It happens because the configure script ran before the crt*.o files had been
created. Here's an example of the timestamps:
-rw-r--r-- 1 mills staff 504 Jan 7 05:43 build/sparcv7/gcc/crtp.o
-rw-r--r-- 1 mills staff 60825 Jan 7 05:38
build/sparcv7/sparc-sun-solaris2.11/libgcc/config.log
As far as I can tell, a failure of the linker at this point tells the script
that we are cross-compiling, and bypasses any subsequent tests that require the
linker. I don't know what effect these assumptions might have.
>From gcc-bugs-return-628032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:31:09 2019
Return-Path: <gcc-bugs-return-628032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94677 invoked by alias); 7 Jan 2019 15:31:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94451 invoked by uid 48); 7 Jan 2019 15:31:00 -0000
From: "steinar+gcc at gunderson dot no" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81668] LTO ODR warnings are not helpful
Date: Mon, 07 Jan 2019 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steinar+gcc at gunderson dot no
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81668-4-hPRIKwzz6M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00841.txt.bz2
Content-length: 940
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81668
--- Comment #14 from Steinar H. Gunderson <steinar+gcc at gunderson dot no> ---
I tested with a GCC snapshot (at r267505). I can now build all mysqld with LTO
and get exactly one LTO warning, and it's a true positive (two Bison parsers
that we haven't managed to untangle yet).
[1/1] Linking CXX executable runtime_output_directory/mysqld
../sql/sql_lex.h:2067:7: warning: type 'union YYSTYPE' violates the C++ One
Definition Rule [-Wodr]
2067 | union YYSTYPE {
| ^
../storage/innobase/include/fts0pars.h:50: note: a different type is defined in
another translation unit
50 | typedef union YYSTYPE
|
../sql/sql_lex.h:2071:18: note: the first difference of corresponding
definitions is field 'hint_type'
2071 | opt_hints_enum hint_type;
| ^
fts0pars.y:62: note: a field with different name is defined in another
translation unit
>From gcc-bugs-return-628033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:31:54 2019
Return-Path: <gcc-bugs-return-628033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100804 invoked by alias); 7 Jan 2019 15:31:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100718 invoked by uid 55); 7 Jan 2019 15:31:49 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Mon, 07 Jan 2019 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87957-4-KJLIyiUvYf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00842.txt.bz2
Content-length: 1372
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
--- Comment #26 from Jan Hubicka <hubicka at ucw dot cz> ---
> Run the gnat.dg testsuite and copy-and-paste the command line from the log file
> without the -q option in the middle. You'll get:
>
> /home/eric/build/gcc/native/gcc/xgcc -c
> -I/home/eric/svn/gcc/gcc/testsuite/gnat.dg/ -B/home/eric/build/gcc/native/gcc
> --RTS=/home/eric/build/gcc/native/x86_64-suse-linux/./libada
> -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> -fdiagnostics-color=never -gnatws -flto -lm -I-
> /home/eric/svn/gcc/gcc/testsuite/gnat.dg/lto8.adb
> +===========================GNAT BUG DETECTED==============================+
> | 9.0.0 20190104 (experimental) [trunk revision 267574] (x86_64-suse-linux) GCC
> error:|
> | in fld_incomplete_type_of, at tree.c:5348 |
Aha, i did that but ignored the command line. It was long bughunting
week, sorry for that :)
I already did printf debugging and indeed we only need to decide how to
adjust type_with_linkage_p so it returns false for all Ada types. Maybe
cleanest would be to add flag to TYPE_DECL which C++ FE will set and
other frontends won't, but perhaps there is easier way around. Jason?
Honza
>From gcc-bugs-return-628034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:32:35 2019
Return-Path: <gcc-bugs-return-628034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101848 invoked by alias); 7 Jan 2019 15:32: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 101702 invoked by uid 48); 7 Jan 2019 15:32:20 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88538] parse error with class nontype template parameter
Date: Mon, 07 Jan 2019 15:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88538-4-fGuqgAXWfB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00843.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88538
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I've raised this on the C++ core reflector, let's see how people feel about it.
>From gcc-bugs-return-628035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:36:05 2019
Return-Path: <gcc-bugs-return-628035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130351 invoked by alias); 7 Jan 2019 15:36:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130249 invoked by uid 48); 7 Jan 2019 15:36:01 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Mon, 07 Jan 2019 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
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: keywords cc see_also
Message-ID: <bug-88737-4-XKGRO4ELiU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00844.txt.bz2
Content-length: 668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=80532
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
bug 80532 is also about detecting use-after-free at compile time
>From gcc-bugs-return-628036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:37:27 2019
Return-Path: <gcc-bugs-return-628036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6297 invoked by alias); 7 Jan 2019 15:37: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 6217 invoked by uid 48); 7 Jan 2019 15:37:21 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Mon, 07 Jan 2019 15: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: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88721-4-1S0hPwurwo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00845.txt.bz2
Content-length: 615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |ebotcazou at gcc dot gnu.org
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I've just successfully finished a sparc-sun-solaris2.11 with it: worked fine.
Thanks, same for me but for some reason I didn't have the original failure.
>From gcc-bugs-return-628038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:42:47 2019
Return-Path: <gcc-bugs-return-628038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24773 invoked by alias); 7 Jan 2019 15:42:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24342 invoked by uid 48); 7 Jan 2019 15:42:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 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: 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-88572-4-wSgO0jrqTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00847.txt.bz2
Content-length: 1530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Changing it to a warning, like so:
--- a/gcc/cp/decl.c
+++ b/gcc/cp/decl.c
@@ -6054,15 +6054,19 @@ reshape_init_r (tree type, reshape_iter *d, bool
first_initializer_p,
{
if (SCALAR_TYPE_P (type))
{
- if (cxx_dialect < cxx11
- /* Isn't value-initialization. */
- || CONSTRUCTOR_NELTS (stripped_init) > 0)
+ if (cxx_dialect < cxx11)
{
if (complain & tf_error)
error ("braces around scalar initializer for type %qT",
type);
init = error_mark_node;
}
+ /* No warning for value-initialization. */
+ else if (CONSTRUCTOR_NELTS (stripped_init) > 0)
+ {
+ warning (0, "braces around scalar initializer for type %qT",
+ type);
+ }
}
else
maybe_warn_cpp0x (CPP0X_INITIALIZER_LISTS);
Causes the test code in comment 0 to issue lots of warnings (as expected) but
also a new error:
88572.cc:14:40: error: cannot bind non-const lvalue reference of type 'invalid'
{aka 'float&'} to an rvalue of type 'float'
14 | invalid scalar_2_brace = braces2<int>(0);
| ~~~~~~~~~~~~^~~
Which means that int{{0}} is now accepted, so my patch isn't right.
>From gcc-bugs-return-628037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:42:23 2019
Return-Path: <gcc-bugs-return-628037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22083 invoked by alias); 7 Jan 2019 15:42:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21158 invoked by uid 55); 7 Jan 2019 15:42:14 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Mon, 07 Jan 2019 15: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88677-4-bQVgzOaqK3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00846.txt.bz2
Content-length: 1761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #9 from Jan Hubicka <hubicka at ucw dot cz> ---
> https://gcc.gnu
> -> You can't simply remove this flag. You could set it to true conservatively.
> Or we could stop marking globals that need constructing TREE_READONLY.
I see, I was under impression that we already drop TREE_READONLY for
them. But it is bit more subtle and thus I was indeed to quick to drop
streaming here. In:
struct c { int a; c() { a=1; } };
const c cc;
const int dd=1;
extern const c ee;
int foo() { return ee.a; }
I get:
const c ee/8 (const c ee) @0x7f68d301ee80
Type: variable
Visibility: external public
References:
Referring: _Z3foov/5 (read)
Availability: not-ready
Varpool flags: read-only
const int dd/4 (const int dd) @0x7f68d301ec80
Type: variable definition analyzed
Visibility: force_output no_reorder
Aux: @0x7f68d316c450
References:
Referring:
Availability: not-ready
Varpool flags: initialized read-only const-value-known
const c cc/3 (const c cc) @0x7f68d301e900
Type: variable definition analyzed
Visibility: force_output no_reorder
Aux: @0x7f68d301ec80
References:
Referring: _Z41__static_initialization_and_destruction_0ii/6 (addr)
Availability: not-ready
Varpool flags:
So EE is indeed read-only, but CC is not.
I guess it is because constructor to CC is output locally and we clear
the flag, while constructor of EE is output externally. What is utility
of this information? Can we realy in some context that value of EE did
not change?
It seems to me that it is completely useless info, so I would be in
favor of dropping TREE_READONLY flag probably at cgraph
construction time (because I suppose it is relevant to front-end)
Honza
>From gcc-bugs-return-628039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:46:22 2019
Return-Path: <gcc-bugs-return-628039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84767 invoked by alias); 7 Jan 2019 15:46:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84671 invoked by uid 55); 7 Jan 2019 15:46:16 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81668] LTO ODR warnings are not helpful
Date: Mon, 07 Jan 2019 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81668-4-bJAkHpcU8P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00848.txt.bz2
Content-length: 1152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81668
--- Comment #15 from Jan Hubicka <hubicka at ucw dot cz> ---
> I tested with a GCC snapshot (at r267505). I can now build all mysqld with LTO
> and get exactly one LTO warning, and it's a true positive (two Bison parsers
> that we haven't managed to untangle yet).
>
> [1/1] Linking CXX executable runtime_output_directory/mysqld
> ../sql/sql_lex.h:2067:7: warning: type 'union YYSTYPE' violates the C++ One
> Definition Rule [-Wodr]
> 2067 | union YYSTYPE {
> | ^
> ../storage/innobase/include/fts0pars.h:50: note: a different type is defined in
> another translation unit
> 50 | typedef union YYSTYPE
> |
> ../sql/sql_lex.h:2071:18: note: the first difference of corresponding
> definitions is field 'hint_type'
> 2071 | opt_hints_enum hint_type;
> | ^
> fts0pars.y:62: note: a field with different name is defined in another
> translation unit
Looks good to me. I think it is reported corectly and should be easy for
developer to understand what is going on. So we can close the PR. Any
additional testcases would be great!
Honza
>From gcc-bugs-return-628040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:50:28 2019
Return-Path: <gcc-bugs-return-628040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55150 invoked by alias); 7 Jan 2019 15:50:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55067 invoked by uid 48); 7 Jan 2019 15:50:23 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 15:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray 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-88572-4-1QBCImVx0N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00849.txt.bz2
Content-length: 351
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #5 from Will Wray <wjwray at gmail dot com> ---
Right; the patch should only apply within aggregate initialization -
arrays and aggregate structures - as the initialization of actual scalars
was already correct.
I'll take a look now (as I meaning to fix my enum patch this week too).
>From gcc-bugs-return-628041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:53:20 2019
Return-Path: <gcc-bugs-return-628041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82174 invoked by alias); 7 Jan 2019 15:53: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 82097 invoked by uid 48); 7 Jan 2019 15:53:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/71176] trunk/fixincludes/fixincl.c:162: bad % specifier
Date: Mon, 07 Jan 2019 15:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: easyhack
X-Bugzilla-Severity: enhancement
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-71176-4-yFIN9ctf5H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71176-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71176-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00850.txt.bz2
Content-length: 193
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71176
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Patch posted to https://gcc.gnu.org/ml/gcc-patches/2018-12/msg01511.html
>From gcc-bugs-return-628042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:53:45 2019
Return-Path: <gcc-bugs-return-628042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82983 invoked by alias); 7 Jan 2019 15:53:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82879 invoked by uid 48); 7 Jan 2019 15:53:38 -0000
From: "steinar+gcc at gunderson dot no" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81668] LTO ODR warnings are not helpful
Date: Mon, 07 Jan 2019 15:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steinar+gcc at gunderson dot no
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81668-4-1NXfVBnQGN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00851.txt.bz2
Content-length: 251
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81668
--- Comment #16 from Steinar H. Gunderson <steinar+gcc at gunderson dot no> ---
Yes, I'm fine with closing this bug; the spurious cases are gone, and the
traces seem to be genuinely helpful now.
>From gcc-bugs-return-628043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 15:57:26 2019
Return-Path: <gcc-bugs-return-628043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96155 invoked by alias); 7 Jan 2019 15: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 96082 invoked by uid 48); 7 Jan 2019 15:57:22 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81668] LTO ODR warnings are not helpful
Date: Mon, 07 Jan 2019 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-81668-4-bxRbgitiDg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81668-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00852.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81668
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #17 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Thanks! New testcases would be welcome (as new PRs:)
>From gcc-bugs-return-628044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:02:05 2019
Return-Path: <gcc-bugs-return-628044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106984 invoked by alias); 7 Jan 2019 16:02: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 106545 invoked by uid 55); 7 Jan 2019 16:01:59 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88567] [9 Regression] ICE in get_initial_defs_for_reduction when building 521.wrf_r on AArch64 SVE
Date: Mon, 07 Jan 2019 16:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88567-4-us8W7pPlVJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00853.txt.bz2
Content-length: 1214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Mon Jan 7 16:00:52 2019
New Revision: 267652
URL: https://gcc.gnu.org/viewcvs?rev=267652&root=gcc&view=rev
Log:
Fix ICE in get_initial_defs_for_reduction (PR 88567)
The use of "j" in:
init = permute_results[number_of_vectors - j - 1];
was out-of-sync with the new flat loop structure. Now that all that
reversing is gone, we can just use the result of duplicate_and_interleave
directly.
The other cases shouldn't be affected by postponing the insertion
of ctor_seq, since gimple_build* appends to the seq without clearing
it first (unlike some of the gimplify routines).
The ICE is already covered by gcc.dg/vect/pr63379.c.
2019-01-07 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR middle-end/88567
* tree-vect-loop.c (get_initial_defs_for_reduction): Pass the
output vector directly to duplicate_and_interleave instead of
going through a temporary. Postpone insertion of ctor_seq to
the end of the loop.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree-vect-loop.c
>From gcc-bugs-return-628045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:02:28 2019
Return-Path: <gcc-bugs-return-628045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109054 invoked by alias); 7 Jan 2019 16:02: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 108938 invoked by uid 48); 7 Jan 2019 16:02:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 16:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-88572-4-AyiuipH3ji@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00854.txt.bz2
Content-length: 268
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I don't think reshape_init_r has the context of the type that contains the
object being initialized, so might need an extra parameter passed to it.
>From gcc-bugs-return-628046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:12:09 2019
Return-Path: <gcc-bugs-return-628046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129859 invoked by alias); 7 Jan 2019 16:12: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 129730 invoked by uid 48); 7 Jan 2019 16:11:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/79593] [7/8/9 Regression] Poor/Worse code generation for FPU on versions after 6
Date: Mon, 07 Jan 2019 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79593-4-k13EmCDZsI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00855.txt.bz2
Content-length: 392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79593
--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Well, RTL DSE isn't a very good fit either, it doesn't track the loads at all,
it will only process them and immediately forget, only stores are recorded. To
optimize these it would need to remember them somewhere, invalidate whenever we
clobber the registers etc.
>From gcc-bugs-return-628047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:17:29 2019
Return-Path: <gcc-bugs-return-628047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6950 invoked by alias); 7 Jan 2019 16: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 6905 invoked by uid 48); 7 Jan 2019 16:17:24 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88739] Big-endian union bug
Date: Mon, 07 Jan 2019 16:17: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.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component short_desc everconfirmed
Message-ID: <bug-88739-4-F1ob1fC5ul@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00856.txt.bz2
Content-length: 1659
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
CC| |wilco at gcc dot gnu.org
Component|target |middle-end
Summary|union bug on ARM64 |Big-endian union bug
Ever confirmed|0 |1
--- Comment #1 from Wilco <wilco at gcc dot gnu.org> ---
Confirmed - this is a generic mid-end bug that happens in fre1 when it replaces
the bitfield store and load with the wrong bitfield extract:
Test_func (U32 ulAddr)
{
union HEAD_REQ_DW4_UNION unData;
unsigned int _1;
<unnamed-unsigned:30> _2;
int _4;
unsigned int _7;
int _9;
short unsigned int _10;
int _11;
short unsigned int _23;
<bb 2> :
_1 = ulAddr_12(D) >> 2;
_2 = (<unnamed-unsigned:30>) _1;
unData.strMemHead.b30AddrL = _2;
unData.strMemHead.b2AddrType = 0;
_4 = (int) _2;
printf ("unData.strMemHead.b30AddrL=0x%x\r\n", _4);
printf ("unData.strMemHead.b2AddrType=0x%x\r\n", 0);
_7 = unData.aulValue[3];
printf ("unData.aulValue[3]=0x%x\r\n", _7);
_23 = BIT_FIELD_REF <_2, 16, 0>; // WRONG: should be _2, 14, 0
_9 = (int) _23;
printf ("unData.ausValue[6]=0x%x\r\n", _9);
_10 = unData.ausValue[7];
_11 = (int) _10;
printf ("unData.ausValue[7]=0x%x\r\n", _11);
unData ={v} {CLOBBER};
return 0;
}
>From gcc-bugs-return-628049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:19:55 2019
Return-Path: <gcc-bugs-return-628049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11034 invoked by alias); 7 Jan 2019 16:19: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 10974 invoked by uid 48); 7 Jan 2019 16:19:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/79593] [7/8/9 Regression] Poor/Worse code generation for FPU on versions after 6
Date: Mon, 07 Jan 2019 16:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-79593-4-t7YURxh2qw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00858.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79593
--- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45368
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45368&action=edit
gcc9-pr79593.patch
This patch solves that with a peephole2 (untested so far). I agree it would be
better to solve generally in some pass, but no pass is a good fit for that
right now.
>From gcc-bugs-return-628048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:19:29 2019
Return-Path: <gcc-bugs-return-628048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10240 invoked by alias); 7 Jan 2019 16:19:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10187 invoked by uid 48); 7 Jan 2019 16:19:25 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88567] [9 Regression] ICE in get_initial_defs_for_reduction when building 521.wrf_r on AArch64 SVE
Date: Mon, 07 Jan 2019 16:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88567-4-o4YAuJIOxh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88567-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00857.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-628050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:21:57 2019
Return-Path: <gcc-bugs-return-628050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14315 invoked by alias); 7 Jan 2019 16:21:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14246 invoked by uid 48); 7 Jan 2019 16:21:52 -0000
From: "danielberger at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/77384] Assembler error - std::forward(decimal64) already defined
Date: Mon, 07 Jan 2019 16:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danielberger at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77384-4-bDc4qwviwn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77384-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77384-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00859.txt.bz2
Content-length: 227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77384
--- Comment #1 from danielberger at gmail dot com ---
Anyone have a chance to take a look at this? It still reproduces in 8.2 and
trunk. Any more information I can provide?
>From gcc-bugs-return-628051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:23:47 2019
Return-Path: <gcc-bugs-return-628051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15951 invoked by alias); 7 Jan 2019 16:23:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15894 invoked by uid 48); 7 Jan 2019 16:23:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88066] [7/8/9 Regression] Relative includes in bits/locale_conv.h should be prefixed
Date: Mon, 07 Jan 2019 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work assigned_to short_desc cf_known_to_fail
Message-ID: <bug-88066-4-6CAyrA4i6C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88066-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88066-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00860.txt.bz2
Content-length: 1084
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88066
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Last reconfirmed|2018-11-17 00:00:00 |2019-1-7
Known to work| |4.9.4
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Summary|Relative includes in |[7/8/9 Regression] Relative
|bits/locale_conv.h should |includes in
|be prefixed |bits/locale_conv.h should
| |be prefixed
Known to fail| |5.5.0, 6.4.0, 7.3.0, 8.2.0,
| |9.0
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is a regression against 4.9, because the <bits/locale_conv.h> header with
these relative includes was added in 5.1
>From gcc-bugs-return-628052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:26:03 2019
Return-Path: <gcc-bugs-return-628052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21252 invoked by alias); 7 Jan 2019 16:26: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 21161 invoked by uid 48); 7 Jan 2019 16:25:58 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88739] Big-endian union bug
Date: Mon, 07 Jan 2019 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-0rVsXnRAwT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00861.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
> _23 = BIT_FIELD_REF <_2, 16, 0>; // WRONG: should be _2, 14, 0
_2 is declared as a 30-bit integer, so perhaps the statement is right, but
expand needs to understand that the shift extract of the top 16 bits comes from
a different location in big-endian.
>From gcc-bugs-return-628053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:28:00 2019
Return-Path: <gcc-bugs-return-628053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56013 invoked by alias); 7 Jan 2019 16:28:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55952 invoked by uid 48); 7 Jan 2019 16:27:55 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88739] Big-endian union bug
Date: Mon, 07 Jan 2019 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-ojxwuF1nGQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00862.txt.bz2
Content-length: 633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #3 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #2)
> > _23 = BIT_FIELD_REF <_2, 16, 0>; // WRONG: should be _2, 14, 0
>
> _2 is declared as a 30-bit integer, so perhaps the statement is right, but
> expand needs to understand that the shift extract of the top 16 bits comes
> from a different location in big-endian.
So the question becomes what format is this in?
<unnamed-unsigned:30> _2;
Is it big-endian memory format (so value is in top 30 bits) or simply a 30-bit
value in a virtual register?
>From gcc-bugs-return-628054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:33:04 2019
Return-Path: <gcc-bugs-return-628054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60188 invoked by alias); 7 Jan 2019 16:33: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 60038 invoked by uid 48); 7 Jan 2019 16:32:56 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/81980] Spurious -Wmissing-format-attribute warning in 32-bit mode
Date: Mon, 07 Jan 2019 16:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.2.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:
Message-ID: <bug-81980-4-p4BgXH9hLA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00863.txt.bz2
Content-length: 1543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81980
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
With -m32 on ix86 we hit:
9282 static tree
9283 ix86_build_builtin_va_list (void)
9284 {
9285 if (TARGET_64BIT)
....
9318 else
9319 {
9320 /* For i386 we use plain pointer to argument area. */
9321 return build_pointer_type (char_type_node);
and so __builtin_va_list and thus va_list is "char *".
Then, in c-format.c:check_function_format
1147 /* Check if the current function has a parameter to
which
1148 the format attribute could be attached; if not, it
1149 can't be a candidate for a format attribute,
despite
1150 the vprintf-like or vscanf-like call. */
1151 tree args;
1152 for (args = DECL_ARGUMENTS (current_function_decl);
1153 args != 0;
1154 args = DECL_CHAIN (args))
1155 {
1156 if (TREE_CODE (TREE_TYPE (args)) == POINTER_TYPE
1157 && (TYPE_MAIN_VARIANT (TREE_TYPE (TREE_TYPE
(args)))
1158 == char_type_node))
1159 break;
1160 }
1161 if (args != 0)
with -m32, the "va_list ap" is "char *" and thus matches the test at lines
1156-1158;
without -m32 it doesn't.
>From gcc-bugs-return-628055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:39:15 2019
Return-Path: <gcc-bugs-return-628055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65115 invoked by alias); 7 Jan 2019 16:39: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 65019 invoked by uid 48); 7 Jan 2019 16:39:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80916] [7/8/9 Regression] Spurious "declared 'static' but never defined" warning
Date: Mon, 07 Jan 2019 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80916-4-e3tlkoTWd5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00864.txt.bz2
Content-length: 1128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80916
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The wording could be improved, but why do you think the warning is spurious?
While the method isn't static, it is effectively static, because it is internal
linkage (i.e. visibility constrained to the current TU in which it is not
really defined). If you ask for -Wunused-function, you get it if the compiler
can figure it out. The reason it doesn't warn at -O0 is that it doesn't see it
unless it tries to devirtualize.
Not sure if we have a way to find out if !TREE_PUBLIC is because it has been
declared static or because it has internal linkage and constrain_visibility
VISIBILITY_ANON has been called on it (and would need a langhook anyway to
determine that).
>From gcc-bugs-return-628056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:47:20 2019
Return-Path: <gcc-bugs-return-628056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72644 invoked by alias); 7 Jan 2019 16:47: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 72544 invoked by uid 48); 7 Jan 2019 16:47:12 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/77384] Assembler error - std::forward(decimal64) already defined
Date: Mon, 07 Jan 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-77384-4-SXqAi8z3hH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77384-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77384-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00865.txt.bz2
Content-length: 1180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77384
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This only happens for C++11 and later.
Modified testcase that's valid in C++98 too:
#include <decimal/decimal>
#include <utility>
using std::decimal::decimal64;
std::pair<int, decimal64> x( 1, 1.5dd );
std::pair<int, decimal64> u( 1, decimal64(1.5dd) );
tmp$ g++ d64.cc
/tmp/cceiwvNA.s: Assembler messages:
/tmp/cceiwvNA.s:1386: Error: symbol `_ZNSt4pairIiDdEC1IiDdLb1EEEOT_OT0_' is
already defined
/tmp/cceiwvNA.s:1390: Error: symbol
`_ZSt7forwardIDdEOT_RNSt16remove_referenceIS0_E4typeE' is already defined
tmp$ g++ d64.cc -std=c++98
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../lib64/crt1.o: In function
`_start':
(.text+0x20): undefined reference to `main'
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-628057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:47:23 2019
Return-Path: <gcc-bugs-return-628057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73083 invoked by alias); 7 Jan 2019 16:47:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72605 invoked by uid 48); 7 Jan 2019 16:47:18 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray 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-88572-4-yUNbd8KDXF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00866.txt.bz2
Content-length: 1505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #7 from Will Wray <wjwray at gmail dot com> ---
I guess that the bug persisted so long *because* of the status quo;
portable code had to delete extra braces to silence warnings or to compile
i.e. the warning on Clang served the purpose of promoting portability to GCC.
So, as to whether it should be a warning; I think not, but...
for practical portability reasons, it probably should be left as a warning
at least until some epoch like C++2a where both GCC & Clang could remove
the warning under the -std=c++2a flag. Make sense?
FYI My use case is counting aggregate members, similar to fields_count
in boost/pfr 'magic_get', but extended to support array members:
https://github.com/apolukhin/magic_get/blob/develop/include/boost/pfr/detail/fields_count.hpp
That code initializes an aggregate T from an index_sequence I... as
T{ ubiq{I}... } (where ubiq is a 'convert to anything' type)
To support 'skipping' arrays, you want to initialize the aggregate as
T{ {ubiq{I}}...}
but, for scalar members, this is what currently fails on GCC / warns on Clang.
Another reason that the bug persisted is the general confusion around braces
and uniform initialization - this fix will give a generic, uniform, way to
initialize the leading members of an aggregate.
I wonder if the extra braces should have additional benefits like not allowing
narrowing conversions. My limited experiments (on Clang) show no difference.
>From gcc-bugs-return-628058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:51:04 2019
Return-Path: <gcc-bugs-return-628058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120404 invoked by alias); 7 Jan 2019 16:51:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119931 invoked by uid 48); 7 Jan 2019 16:50:59 -0000
From: "ks1322 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88742] New: Debugger jumps back when stepping over class destructor
Date: Mon, 07 Jan 2019 16:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ks1322 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-88742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00867.txt.bz2
Content-length: 1845
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88742
Bug ID: 88742
Summary: Debugger jumps back when stepping over class
destructor
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: ks1322 at gmail dot com
Target Milestone: ---
This is basically the same bug report as the Bug 49951 because it can be
reproduced with recent version of gcc.
I don't know whether Bug 49951 should be reopened or not, so I am reporting the
new one.
In short, when stepping to destructor code in debugger, it jumps back to the
declaration of the class.
The code:
#include <stdio.h>
class MyClass
{
public:
MyClass() {}; // constructor
~MyClass() {}; // destructor
};
int main ()
{
int i = 1;
MyClass m;
if (i == 1)
{
printf ("Hello world %d\n", i);
}
}
Compiling:
g++ -Wall -Wextra -g -O0 t03.cpp
Debugging:
$ gdb -q a.out
Reading symbols from a.out...done.
(gdb) start
Temporary breakpoint 1 at 0x40114f: file t03.cpp, line 13.
Starting program: /tmp/a.out
Missing separate debuginfos, use: dnf debuginfo-install
glibc-2.28-23.fc29.x86_64
Temporary breakpoint 1, main () at t03.cpp:13
13 int i = 1;
Missing separate debuginfos, use: dnf debuginfo-install
libgcc-8.2.1-5.fc29.x86_64 libstdc++-8.2.1-5.fc29.x86_64
(gdb) n
14 MyClass m;
(gdb)
16 if (i == 1)
(gdb)
18 printf ("Hello world %d\n", i);
(gdb)
Hello world 1
14 MyClass m;
(gdb)
20 }
Note the jump back to line 14 before continuing to line 20.
I don't observe this behavior with clang, no jumps back in debugger (clang
version 7.0.0).
>From gcc-bugs-return-628059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 16:52:45 2019
Return-Path: <gcc-bugs-return-628059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122035 invoked by alias); 7 Jan 2019 16:52:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121919 invoked by uid 48); 7 Jan 2019 16:52:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 16:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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-88572-4-oSo8CkyRiA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00868.txt.bz2
Content-length: 1030
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Will Wray from comment #7)
> So, as to whether it should be a warning; I think not, but...
> for practical portability reasons, it probably should be left as a warning
> at least until some epoch like C++2a where both GCC & Clang could remove
> the warning under the -std=c++2a flag. Make sense?
No, I don't think so. I don't see why the warning should be given for C++11 but
not C++2a when the code is valid for both.
I think it should be accepted without a warning. I'd be more inclined to say it
should be accepted in C++98 with a -pedantic warning, rather than give a
warning for C++11.
> I wonder if the extra braces should have additional benefits like not
> allowing
> narrowing conversions. My limited experiments (on Clang) show no difference.
The outermost braces already mean it's a context that doesn't allow narrowing,
so the additional inner braces make no difference.
>From gcc-bugs-return-628060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:04:47 2019
Return-Path: <gcc-bugs-return-628060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22007 invoked by alias); 7 Jan 2019 17:04: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 21971 invoked by uid 48); 7 Jan 2019 17:04:43 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88741] [9 Regression] Spurious "too long" error inside template
Date: Mon, 07 Jan 2019 17: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88741-4-8Wfyydj8Ig@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00869.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88741
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Looks like we neglect to strip the location wrapper in complete_array_type (if
it's in a CONSTRUCTOR). Lookin' more.
>From gcc-bugs-return-628061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:06:24 2019
Return-Path: <gcc-bugs-return-628061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24727 invoked by alias); 7 Jan 2019 17:06:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24638 invoked by uid 48); 7 Jan 2019 17:06:17 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] [9 Regression] scan-ipa-dump inline "Inlined tp_sum/
Date: Mon, 07 Jan 2019 17:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88711-4-PMCwrVzyeV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00870.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
Christophe Lyon <clyon at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |clyon at gcc dot gnu.org
--- Comment #3 from Christophe Lyon <clyon at gcc dot gnu.org> ---
Seen on arm and aarch64 too.
>From gcc-bugs-return-628064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:09:31 2019
Return-Path: <gcc-bugs-return-628064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29257 invoked by alias); 7 Jan 2019 17:09:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28676 invoked by uid 55); 7 Jan 2019 17:09:24 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69696] incorrect initialization of block-scope flexible array members
Date: Mon, 07 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-69696-4-uqLlhm0nNo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00873.txt.bz2
Content-length: 2451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69696
--- Comment #3 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Author: edlinger
Date: Mon Jan 7 17:08:51 2019
New Revision: 267653
URL: https://gcc.gnu.org/viewcvs?rev=267653&root=gcc&view=rev
Log:
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* cp-tree.h (LOOKUP_ALLOW_FLEXARRAY_INIT): New flag value.
* typeck2.c (digest_init_r): Raise an error for non-static
initialization of a flexible array member.
(process_init_constructor, massage_init_elt,
process_init_constructor_array, process_init_constructor_record,
process_init_constructor_union, process_init_constructor): Add the
flags parameter and pass it thru.
(store_init_value): Pass LOOKUP_ALLOW_FLEXARRAY_INIT parameter to
digest_init_flags for static decls.
gcc/testsuite:
2019-01-07 Bernd Edlinger <bernd.edlinger@hotmail.de>
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* gcc.dg/array-6.c: Move from here ...
* c-c++-common/array-6.c: ... to here and add some more test coverage.
* g++.dg/pr69338.C: New test.
* g++.dg/pr69697.C: Likewise.
* g++.dg/ext/flexary32.C: Likewise.
* g++.dg/ext/flexary3.C: Adjust test.
* g++.dg/ext/flexary12.C: Likewise.
* g++.dg/ext/flexary13.C: Likewise.
* g++.dg/ext/flexary15.C: Likewise.
* g++.dg/warn/Wplacement-new-size-1.C: Likewise.
* g++.dg/warn/Wplacement-new-size-2.C: Likewise.
* g++.dg/warn/Wplacement-new-size-6.C: Likewise.
Added:
trunk/gcc/testsuite/c-c++-common/array-6.c
- copied, changed from r267652, trunk/gcc/testsuite/gcc.dg/array-6.c
trunk/gcc/testsuite/g++.dg/ext/flexary32.C
trunk/gcc/testsuite/g++.dg/pr69338.C
trunk/gcc/testsuite/g++.dg/pr69697.C
Removed:
trunk/gcc/testsuite/gcc.dg/array-6.c
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/ext/flexary12.C
trunk/gcc/testsuite/g++.dg/ext/flexary13.C
trunk/gcc/testsuite/g++.dg/ext/flexary15.C
trunk/gcc/testsuite/g++.dg/ext/flexary3.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-1.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-2.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-6.C
>From gcc-bugs-return-628063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:09:31 2019
Return-Path: <gcc-bugs-return-628063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29217 invoked by alias); 7 Jan 2019 17:09: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 28622 invoked by uid 55); 7 Jan 2019 17:09:24 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69338] incorrect ctor initialization of a flexible array member
Date: Mon, 07 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-69338-4-OG95xrpBya@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69338-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69338-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00872.txt.bz2
Content-length: 2451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69338
--- Comment #3 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Author: edlinger
Date: Mon Jan 7 17:08:51 2019
New Revision: 267653
URL: https://gcc.gnu.org/viewcvs?rev=267653&root=gcc&view=rev
Log:
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* cp-tree.h (LOOKUP_ALLOW_FLEXARRAY_INIT): New flag value.
* typeck2.c (digest_init_r): Raise an error for non-static
initialization of a flexible array member.
(process_init_constructor, massage_init_elt,
process_init_constructor_array, process_init_constructor_record,
process_init_constructor_union, process_init_constructor): Add the
flags parameter and pass it thru.
(store_init_value): Pass LOOKUP_ALLOW_FLEXARRAY_INIT parameter to
digest_init_flags for static decls.
gcc/testsuite:
2019-01-07 Bernd Edlinger <bernd.edlinger@hotmail.de>
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* gcc.dg/array-6.c: Move from here ...
* c-c++-common/array-6.c: ... to here and add some more test coverage.
* g++.dg/pr69338.C: New test.
* g++.dg/pr69697.C: Likewise.
* g++.dg/ext/flexary32.C: Likewise.
* g++.dg/ext/flexary3.C: Adjust test.
* g++.dg/ext/flexary12.C: Likewise.
* g++.dg/ext/flexary13.C: Likewise.
* g++.dg/ext/flexary15.C: Likewise.
* g++.dg/warn/Wplacement-new-size-1.C: Likewise.
* g++.dg/warn/Wplacement-new-size-2.C: Likewise.
* g++.dg/warn/Wplacement-new-size-6.C: Likewise.
Added:
trunk/gcc/testsuite/c-c++-common/array-6.c
- copied, changed from r267652, trunk/gcc/testsuite/gcc.dg/array-6.c
trunk/gcc/testsuite/g++.dg/ext/flexary32.C
trunk/gcc/testsuite/g++.dg/pr69338.C
trunk/gcc/testsuite/g++.dg/pr69697.C
Removed:
trunk/gcc/testsuite/gcc.dg/array-6.c
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/ext/flexary12.C
trunk/gcc/testsuite/g++.dg/ext/flexary13.C
trunk/gcc/testsuite/g++.dg/ext/flexary15.C
trunk/gcc/testsuite/g++.dg/ext/flexary3.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-1.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-2.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-6.C
>From gcc-bugs-return-628066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:09:32 2019
Return-Path: <gcc-bugs-return-628066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29541 invoked by alias); 7 Jan 2019 17:09:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28651 invoked by uid 55); 7 Jan 2019 17:09:24 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69697] incorrect runtime initialization of static flexible array members
Date: Mon, 07 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-69697-4-xNMhnr5cSU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69697-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69697-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00875.txt.bz2
Content-length: 2451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69697
--- Comment #3 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Author: edlinger
Date: Mon Jan 7 17:08:51 2019
New Revision: 267653
URL: https://gcc.gnu.org/viewcvs?rev=267653&root=gcc&view=rev
Log:
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* cp-tree.h (LOOKUP_ALLOW_FLEXARRAY_INIT): New flag value.
* typeck2.c (digest_init_r): Raise an error for non-static
initialization of a flexible array member.
(process_init_constructor, massage_init_elt,
process_init_constructor_array, process_init_constructor_record,
process_init_constructor_union, process_init_constructor): Add the
flags parameter and pass it thru.
(store_init_value): Pass LOOKUP_ALLOW_FLEXARRAY_INIT parameter to
digest_init_flags for static decls.
gcc/testsuite:
2019-01-07 Bernd Edlinger <bernd.edlinger@hotmail.de>
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* gcc.dg/array-6.c: Move from here ...
* c-c++-common/array-6.c: ... to here and add some more test coverage.
* g++.dg/pr69338.C: New test.
* g++.dg/pr69697.C: Likewise.
* g++.dg/ext/flexary32.C: Likewise.
* g++.dg/ext/flexary3.C: Adjust test.
* g++.dg/ext/flexary12.C: Likewise.
* g++.dg/ext/flexary13.C: Likewise.
* g++.dg/ext/flexary15.C: Likewise.
* g++.dg/warn/Wplacement-new-size-1.C: Likewise.
* g++.dg/warn/Wplacement-new-size-2.C: Likewise.
* g++.dg/warn/Wplacement-new-size-6.C: Likewise.
Added:
trunk/gcc/testsuite/c-c++-common/array-6.c
- copied, changed from r267652, trunk/gcc/testsuite/gcc.dg/array-6.c
trunk/gcc/testsuite/g++.dg/ext/flexary32.C
trunk/gcc/testsuite/g++.dg/pr69338.C
trunk/gcc/testsuite/g++.dg/pr69697.C
Removed:
trunk/gcc/testsuite/gcc.dg/array-6.c
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/ext/flexary12.C
trunk/gcc/testsuite/g++.dg/ext/flexary13.C
trunk/gcc/testsuite/g++.dg/ext/flexary15.C
trunk/gcc/testsuite/g++.dg/ext/flexary3.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-1.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-2.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-6.C
>From gcc-bugs-return-628065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:09:32 2019
Return-Path: <gcc-bugs-return-628065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29448 invoked by alias); 7 Jan 2019 17:09:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28666 invoked by uid 55); 7 Jan 2019 17:09:24 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88261] [9 Regression] ICE: verify_gimple failed (error: non-trivial conversion at assignment)
Date: Mon, 07 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid, ice-checking, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bernd.edlinger at hotmail dot de
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88261-4-UcawONPpzl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88261-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88261-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00874.txt.bz2
Content-length: 2452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88261
--- Comment #12 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Author: edlinger
Date: Mon Jan 7 17:08:51 2019
New Revision: 267653
URL: https://gcc.gnu.org/viewcvs?rev=267653&root=gcc&view=rev
Log:
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* cp-tree.h (LOOKUP_ALLOW_FLEXARRAY_INIT): New flag value.
* typeck2.c (digest_init_r): Raise an error for non-static
initialization of a flexible array member.
(process_init_constructor, massage_init_elt,
process_init_constructor_array, process_init_constructor_record,
process_init_constructor_union, process_init_constructor): Add the
flags parameter and pass it thru.
(store_init_value): Pass LOOKUP_ALLOW_FLEXARRAY_INIT parameter to
digest_init_flags for static decls.
gcc/testsuite:
2019-01-07 Bernd Edlinger <bernd.edlinger@hotmail.de>
PR c++/88261
PR c++/69338
PR c++/69696
PR c++/69697
* gcc.dg/array-6.c: Move from here ...
* c-c++-common/array-6.c: ... to here and add some more test coverage.
* g++.dg/pr69338.C: New test.
* g++.dg/pr69697.C: Likewise.
* g++.dg/ext/flexary32.C: Likewise.
* g++.dg/ext/flexary3.C: Adjust test.
* g++.dg/ext/flexary12.C: Likewise.
* g++.dg/ext/flexary13.C: Likewise.
* g++.dg/ext/flexary15.C: Likewise.
* g++.dg/warn/Wplacement-new-size-1.C: Likewise.
* g++.dg/warn/Wplacement-new-size-2.C: Likewise.
* g++.dg/warn/Wplacement-new-size-6.C: Likewise.
Added:
trunk/gcc/testsuite/c-c++-common/array-6.c
- copied, changed from r267652, trunk/gcc/testsuite/gcc.dg/array-6.c
trunk/gcc/testsuite/g++.dg/ext/flexary32.C
trunk/gcc/testsuite/g++.dg/pr69338.C
trunk/gcc/testsuite/g++.dg/pr69697.C
Removed:
trunk/gcc/testsuite/gcc.dg/array-6.c
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/typeck2.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/ext/flexary12.C
trunk/gcc/testsuite/g++.dg/ext/flexary13.C
trunk/gcc/testsuite/g++.dg/ext/flexary15.C
trunk/gcc/testsuite/g++.dg/ext/flexary3.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-1.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-2.C
trunk/gcc/testsuite/g++.dg/warn/Wplacement-new-size-6.C
>From gcc-bugs-return-628062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:09:26 2019
Return-Path: <gcc-bugs-return-628062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28715 invoked by alias); 7 Jan 2019 17: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 28458 invoked by uid 48); 7 Jan 2019 17:09:21 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Mon, 07 Jan 2019 17: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: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-4Uh5kQcMvp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00871.txt.bz2
Content-length: 255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #13 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> 2. Apply this patch to GCC (assuming it still applies cleanly...).
FYI I'm in the process of rewriting it using mode iterators.
>From gcc-bugs-return-628067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:11:51 2019
Return-Path: <gcc-bugs-return-628067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49961 invoked by alias); 7 Jan 2019 17:11:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49884 invoked by uid 48); 7 Jan 2019 17:11:47 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84497] link errors with trivial external thread_local variables
Date: Mon, 07 Jan 2019 17:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-84497-4-0EgyjZuSHQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84497-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84497-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00876.txt.bz2
Content-length: 961
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84497
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 45369
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45369&action=edit
assembler for PR84497 with/without -DDEF
It's probable that the test for PR84497 has never passed for emulated TLS
targets.
Although I see this on Darwin, GCC's emulated TLS impl. is between the FE and
ME, it doesn't have a back-end requirement (i.e. I'd expect it to fail for all
emulated TLS targets).
with -DDEF, I see that a __tls_init function is created.
without, there no references to any init function(s).
[it could be that this is a separate bug, but let's start here].
>From gcc-bugs-return-628069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:13:35 2019
Return-Path: <gcc-bugs-return-628069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56850 invoked by alias); 7 Jan 2019 17:13:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56711 invoked by uid 48); 7 Jan 2019 17:13:30 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59994] [meta-bug] thread_local
Date: Mon, 07 Jan 2019 17:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-59994-4-qxILMO5hj3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00878.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59994
Bug 59994 depends on bug 84497, which changed state.
Bug 84497 Summary: link errors with trivial external thread_local variables
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84497
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
>From gcc-bugs-return-628068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:13:34 2019
Return-Path: <gcc-bugs-return-628068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56759 invoked by alias); 7 Jan 2019 17:13:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56658 invoked by uid 48); 7 Jan 2019 17:13:29 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84497] link errors with trivial external thread_local variables
Date: Mon, 07 Jan 2019 17:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on resolution everconfirmed
Message-ID: <bug-84497-4-6HW4gHM0gZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84497-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84497-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00877.txt.bz2
Content-length: 535
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84497
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Last reconfirmed| |2019-01-07
Resolution|FIXED |---
Ever confirmed|0 |1
--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
so reopening.
>From gcc-bugs-return-628070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:19:55 2019
Return-Path: <gcc-bugs-return-628070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81850 invoked by alias); 7 Jan 2019 17:19:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81721 invoked by uid 48); 7 Jan 2019 17:19:51 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88742] [7/8/9 Regression] Debugger jumps back when stepping over class destructor
Date: Mon, 07 Jan 2019 17:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work see_also short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-88742-4-AeHoVlxVtL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00879.txt.bz2
Content-length: 975
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88742
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Known to work| |4.7.4, 4.8.5, 4.9.4
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=49951
Summary|Debugger jumps back when |[7/8/9 Regression] Debugger
|stepping over class |jumps back when stepping
|destructor |over class destructor
Ever confirmed|0 |1
Known to fail| |5.5.0, 6.4.0, 7.3.0, 8.2.0,
| |9.0
>From gcc-bugs-return-628071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:28:37 2019
Return-Path: <gcc-bugs-return-628071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96102 invoked by alias); 7 Jan 2019 17:28:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96024 invoked by uid 48); 7 Jan 2019 17:28:33 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88261] [9 Regression] ICE: verify_gimple failed (error: non-trivial conversion at assignment)
Date: Mon, 07 Jan 2019 17:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid, ice-checking, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: bernd.edlinger at hotmail dot de
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88261-4-xPwjZyFrnM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88261-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88261-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00880.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88261
Bernd Edlinger <bernd.edlinger at hotmail dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Fixed.
>From gcc-bugs-return-628072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:28:40 2019
Return-Path: <gcc-bugs-return-628072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96424 invoked by alias); 7 Jan 2019 17:28: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 96060 invoked by uid 48); 7 Jan 2019 17:28:34 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88741] [9 Regression] Spurious "too long" error inside template
Date: Mon, 07 Jan 2019 17:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to target_milestone
Message-ID: <bug-88741-4-1XMhjZ3JC0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00881.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88741
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Target Milestone|--- |9.0
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
In cp_complete_array_type actually. Testing a fix.
>From gcc-bugs-return-628073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:31:27 2019
Return-Path: <gcc-bugs-return-628073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100956 invoked by alias); 7 Jan 2019 17:31: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 100499 invoked by uid 48); 7 Jan 2019 17:31:04 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84497] link errors with trivial external thread_local variables
Date: Mon, 07 Jan 2019 17:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-84497-4-JgdQDpbuBL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84497-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84497-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00882.txt.bz2
Content-length: 596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84497
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45369|0 |1
is obsolete| |
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 45370
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45370&action=edit
assembler for PR84497 with/without -DDEF
and now with the correct file, containing both cases.
>From gcc-bugs-return-628074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:32:11 2019
Return-Path: <gcc-bugs-return-628074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102453 invoked by alias); 7 Jan 2019 17:32: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 102350 invoked by uid 48); 7 Jan 2019 17:32:05 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88739] Big-endian union bug
Date: Mon, 07 Jan 2019 17:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-8Anrbijlxn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00883.txt.bz2
Content-length: 219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
manual inspection of the output from gcc-5.4.0 suggests this version produces
correct code.
>From gcc-bugs-return-628075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:33:00 2019
Return-Path: <gcc-bugs-return-628075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104162 invoked by alias); 7 Jan 2019 17:33:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104116 invoked by uid 48); 7 Jan 2019 17:32:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88742] [7/8/9 Regression] Debugger jumps back when stepping over class destructor
Date: Mon, 07 Jan 2019 17:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88742-4-fXJfbIT1cs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00884.txt.bz2
Content-length: 418
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88742
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This broke with r220886 aka PR58123 fix.
>From gcc-bugs-return-628076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:35:02 2019
Return-Path: <gcc-bugs-return-628076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127725 invoked by alias); 7 Jan 2019 17:35: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 125529 invoked by uid 48); 7 Jan 2019 17:34:57 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69338] incorrect ctor initialization of a flexible array member
Date: Mon, 07 Jan 2019 17:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-69338-4-mWPjUrwlas@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69338-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69338-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00885.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69338
Bernd Edlinger <edlinger at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-628077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:35:02 2019
Return-Path: <gcc-bugs-return-628077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127957 invoked by alias); 7 Jan 2019 17:35:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126010 invoked by uid 48); 7 Jan 2019 17:34:58 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69698] [meta-bug] flexible array members
Date: Mon, 07 Jan 2019 17:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-69698-4-qw3EUUMZuZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00886.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69698
Bug 69698 depends on bug 69338, which changed state.
Bug 69338 Summary: incorrect ctor initialization of a flexible array member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69338
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:36:25 2019
Return-Path: <gcc-bugs-return-628078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3889 invoked by alias); 7 Jan 2019 17:36:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3793 invoked by uid 48); 7 Jan 2019 17:36:21 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69696] incorrect initialization of block-scope flexible array members
Date: Mon, 07 Jan 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-69696-4-96CWdf6ket@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00887.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69696
Bernd Edlinger <edlinger at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-628079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:36:29 2019
Return-Path: <gcc-bugs-return-628079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4401 invoked by alias); 7 Jan 2019 17:36: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 3825 invoked by uid 48); 7 Jan 2019 17:36:21 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69698] [meta-bug] flexible array members
Date: Mon, 07 Jan 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-69698-4-ljx96q9xfK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00888.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69698
Bug 69698 depends on bug 69696, which changed state.
Bug 69696 Summary: incorrect initialization of block-scope flexible array members
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69696
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:38:07 2019
Return-Path: <gcc-bugs-return-628080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13402 invoked by alias); 7 Jan 2019 17:38:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8130 invoked by uid 48); 7 Jan 2019 17:38:02 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69697] incorrect runtime initialization of static flexible array members
Date: Mon, 07 Jan 2019 17:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-69697-4-5LEBziIBlE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69697-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69697-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00889.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69697
Bernd Edlinger <edlinger at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-628081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:38:08 2019
Return-Path: <gcc-bugs-return-628081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13829 invoked by alias); 7 Jan 2019 17:38:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8742 invoked by uid 48); 7 Jan 2019 17:38:04 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69698] [meta-bug] flexible array members
Date: Mon, 07 Jan 2019 17:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-69698-4-SIJ30D2PDH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00890.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69698
Bug 69698 depends on bug 69697, which changed state.
Bug 69697 Summary: incorrect runtime initialization of static flexible array members
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69697
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:43:10 2019
Return-Path: <gcc-bugs-return-628082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61392 invoked by alias); 7 Jan 2019 17:43: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 61349 invoked by uid 48); 7 Jan 2019 17:43:05 -0000
From: "seurer at linux dot vnet.ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88743] New: [9 regression] test case gfortran.dg/pr79966.f90 fails starting with r267600
Date: Mon, 07 Jan 2019 17:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at linux dot vnet.ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-88743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00891.txt.bz2
Content-length: 2878
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88743
Bug ID: 88743
Summary: [9 regression] test case gfortran.dg/pr79966.f90 fails
starting with r267600
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at linux dot vnet.ibm.com
Target Milestone: ---
Executing on host:
/home/seurer/gcc/build/gcc-test2/gcc/testsuite/gfortran/../../gfortran
-B/home/seurer/gcc/build/gcc-test2/gcc/testsuite/gfortran/../../
-B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/pr79966.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O -O2 -fpeel-loops -finline-functions
-fipa-cp-clone -fdump-ipa-inline-details -S -o pr79966.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test2/gcc/testsuite/gfortran/../../gfortran
-B/home/seurer/gcc/build/gcc-test2/gcc/testsuite/gfortran/../../
-B/home/seurer/gcc/build/gcc-test2/powerpc64-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/pr79966.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -O -O2 -fpeel-loops -finline-functions -fipa-cp-clone
-fdump-ipa-inline-details -S -o pr79966.s^M
PASS: gfortran.dg/pr79966.f90 -O (test for excess errors)
FAIL: gfortran.dg/pr79966.f90 -O scan-ipa-dump inline "Inlined
tp_sum/[0-9]+ into runtptests/[0-9]+"
So prior to this revision:
seurer@makalu-lp1:~/gcc/build/gcc-test$ grep "Inlined" pr79966.f90.076i.inline
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/pr79966.f90:57:0:
optimized: Inlined mysum.constprop/33 into tp_sum/5 which now has time
81.000001 and size 89, net change of -25.
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/pr79966.f90:94:0:
optimized: Inlined tp_sum/34 into runtptests/3 which now has time 8099.743263
and size 180, net change of +76.
Inlined 4 calls, eliminated 2 functions
and with this revision:
seurer@makalu-lp1:~/gcc/build/gcc-test2$ grep "Inlined" pr79966.f90.076i.inline
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/pr79966.f90:57:0:
optimized: Inlined mysum.constprop/34 into tp_sum/5 which now has time
1969.128286 and size 89, net change of -25.
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/pr79966.f90:82:0:
optimized: Inlined generategrid.constprop/33 into runtptests/3 which now has
time 4418.145081 and size 208, net change of -16.
Inlined 4 calls, eliminated 3 functions
r267600 | hubicka | 2019-01-05 11:47:34 -0600 (Sat, 05 Jan 2019) | 2 lines
* ipa-fnsummary.c (analyze_function_body): Fix accounting of time.
>From gcc-bugs-return-628083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:47:25 2019
Return-Path: <gcc-bugs-return-628083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65808 invoked by alias); 7 Jan 2019 17:47: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 65744 invoked by uid 48); 7 Jan 2019 17:47:16 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88538] parse error with class nontype template parameter
Date: Mon, 07 Jan 2019 17:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88538-4-evisYAdhUW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00892.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88538
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
The results is that this ought to work. I'll open a DR and I think we can fix
this right away in GCC.
>From gcc-bugs-return-628084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:53:33 2019
Return-Path: <gcc-bugs-return-628084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71327 invoked by alias); 7 Jan 2019 17:53:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71225 invoked by uid 48); 7 Jan 2019 17:53:29 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/88743] [9 regression] test case gfortran.dg/pr79966.f90 fails starting with r267600
Date: Mon, 07 Jan 2019 17:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 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: 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-88743-4-ZwkaJlXtdc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88743-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00893.txt.bz2
Content-length: 503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88743
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Dup.
*** This bug has been marked as a duplicate of bug 88711 ***
>From gcc-bugs-return-628085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 17:53:34 2019
Return-Path: <gcc-bugs-return-628085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71383 invoked by alias); 7 Jan 2019 17:53:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71263 invoked by uid 48); 7 Jan 2019 17:53:30 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88711] [9 Regression] scan-ipa-dump inline "Inlined tp_sum/
Date: Mon, 07 Jan 2019 17:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88711-4-cyhxE5pWhm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00894.txt.bz2
Content-length: 465
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88711
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |seurer at linux dot vnet.ibm.com
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 88743 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-628086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:05:22 2019
Return-Path: <gcc-bugs-return-628086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81345 invoked by alias); 7 Jan 2019 18:05: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 81268 invoked by uid 48); 7 Jan 2019 18:05:16 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88047] [9 Regression] ICE in gfc_find_vtab, at fortran/class.c:2843
Date: Mon, 07 Jan 2019 18:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88047-4-igo4LdVVQ4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00895.txt.bz2
Content-length: 1406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88047
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |janus at gcc dot gnu.org
--- Comment #7 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #6)
> Janus, could please you figure out why class_array_3.f03 is failing with
> your patch?
I think the problem is that for class arrays the proper array refs are only
established at resolution stage, so that gfc_expr_attr does not yet work at
parsing stage, leading to the ICE shown in comment #4. I see no simple way to
change that.
In consequence, I propose the following patch:
@@ -2846,7 +2846,10 @@ gfc_find_vtab (gfc_typespec *ts)
case BT_DERIVED:
return gfc_find_derived_vtab (ts->u.derived);
case BT_CLASS:
- return gfc_find_derived_vtab (ts->u.derived->components->ts.u.derived);
+ if (ts->u.derived->components &&
ts->u.derived->components->ts.u.derived)
+ return gfc_find_derived_vtab (ts->u.derived->components->ts.u.derived);
+ else
+ return NULL;
default:
return find_intrinsic_vtab (ts);
}
It fixes the ICEs on comment #0 and comment #5 and regtests cleanly.
>From gcc-bugs-return-628087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:12:43 2019
Return-Path: <gcc-bugs-return-628087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88215 invoked by alias); 7 Jan 2019 18:12:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88183 invoked by uid 55); 7 Jan 2019 18:12:39 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88584] GCC thinks that the type is complete dispite shaddowing.
Date: Mon, 07 Jan 2019 18:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88584-4-0kKpcyyY3D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88584-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88584-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00896.txt.bz2
Content-length: 219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88584
--- Comment #8 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Yes, I consider this a confirmed (and, strictly, regression from 3.4) bug.
>From gcc-bugs-return-628088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:14:42 2019
Return-Path: <gcc-bugs-return-628088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90224 invoked by alias); 7 Jan 2019 18:14: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 90155 invoked by uid 48); 7 Jan 2019 18:14:37 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88744] New: class non-type template parameters doesn't work with default template parameters
Date: Mon, 07 Jan 2019 18:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00897.txt.bz2
Content-length: 1229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88744
Bug ID: 88744
Summary: class non-type template parameters doesn't work with
default template parameters
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
This ought to work:
struct S {
int a;
int b;
};
template<S s = {1, 2}> struct X {};
X x; // ok, X<{1, 2}>
but we reject it with:
z.C:7:3: error: class template argument deduction failed:
7 | X x; // ok, X<{1, 2}>
| ^
z.C:7:3: error: no matching function for call to ‘X()’
z.C:6:31: note: candidate: ‘template<S s> X()-> X<s>’
6 | template<S s = {1, 2}> struct X {};
| ^
z.C:6:31: note: template argument deduction/substitution failed:
z.C:6:21: error: could not convert ‘{1, 2}’ from ‘<brace-enclosed initializer
list>’ to ‘S’
6 | template<S s = {1, 2}> struct X {};
| ^
>From gcc-bugs-return-628089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:16:18 2019
Return-Path: <gcc-bugs-return-628089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92152 invoked by alias); 7 Jan 2019 18:16: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 91851 invoked by uid 48); 7 Jan 2019 18:16:06 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88584] [7/8/9 Regression] GCC thinks that the type is complete dispite shaddowing.
Date: Mon, 07 Jan 2019 18:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88584-4-hqh3bRyrdu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88584-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88584-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00898.txt.bz2
Content-length: 806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88584
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |7.5
Summary|GCC thinks that the type is |[7/8/9 Regression] GCC
|complete dispite |thinks that the type is
|shaddowing. |complete dispite
| |shaddowing.
Ever confirmed|0 |1
>From gcc-bugs-return-628090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:34:06 2019
Return-Path: <gcc-bugs-return-628090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126733 invoked by alias); 7 Jan 2019 18:34: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 126624 invoked by uid 55); 7 Jan 2019 18:34:01 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88727] Diagnostics improvement: Detection of undefined behaviour. Incomplete type in tenative definition with internal linkage.
Date: Mon, 07 Jan 2019 18:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88727-4-exIiDLuGIK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00899.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88727
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
This was the case mentioned in bug 26581 comment 4, but without a separate
bug filed for it at the time.
>From gcc-bugs-return-628091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:42:50 2019
Return-Path: <gcc-bugs-return-628091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11438 invoked by alias); 7 Jan 2019 18:42:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11349 invoked by uid 48); 7 Jan 2019 18:42:43 -0000
From: "edlinger at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80228] inconsistent handling of ctor initialization of flexible array members
Date: Mon, 07 Jan 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: accepts-invalid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: edlinger at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-80228-4-E6Ex8X2RIM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80228-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80228-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00900.txt.bz2
Content-length: 3190
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80228
Bernd Edlinger <edlinger at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|diagnostic, rejects-valid |wrong-code
--- Comment #3 from Bernd Edlinger <edlinger at gcc dot gnu.org> ---
This is half fixed by r267653
B was already correctly rejected, and is invalid in C++11:
$ cat x.cc
struct A { int n, a[]; };
struct B
{
int n = 3;
int a1[] = { 2, 1, 0 }; // rejected (see pr72775)
} b;
struct C
{
A a2 = { 3, { 2, 1, 0 } }; // accepted
} c;
struct E
{
A a4;
E ():
a4 {3, { 2, 1, 0 } } { } // accepted
} e;
$ g++ x.cc
x.cc:6:7: error: initializer for flexible array member 'int B::a1 []'
6 | int a1[] = { 2, 1, 0 }; // rejected (see pr72775)
| ^~
x.cc:11:27: error: non-static initialization of a flexible array member
11 | A a2 = { 3, { 2, 1, 0 } }; // accepted
| ^
x.cc: In constructor 'E::E()':
x.cc:19:24: error: non-static initialization of a flexible array member
19 | a4 {3, { 2, 1, 0 } } { } // accepted
| ^
C and E are diagnosed as non-static initialization which is fine.
But D is still accepted:
$ cat t.cc
struct A { int n, a[]; };
struct D
{
int n, a3[];
D ():
n (3),
a3 {2, 1, 0} { } // silently accepted
} d;
D* foo ()
{
return new D;
}
void bar ()
{
volatile D vd;
}
$ g++ -S -O3 t.cc
$ cat t.s
.file "t.cc"
.text
.p2align 4
.globl _Z3foov
.type _Z3foov, @function
_Z3foov:
.LFB3:
.cfi_startproc
subq $8, %rsp
.cfi_def_cfa_offset 16
movl $4, %edi <<<--- allocate only 4 byte, 16 neeeded
call _Znwm
movdqa .LC0(%rip), %xmm0
movups %xmm0, (%rax)
addq $8, %rsp
.cfi_def_cfa_offset 8
ret
.cfi_endproc
.LFE3:
.size _Z3foov, .-_Z3foov
.p2align 4
.globl _Z3barv
.type _Z3barv, @function
_Z3barv:
.LFB4:
.cfi_startproc <<<--- didn't I declare vd as volatile?
ret
.cfi_endproc
.LFE4:
.size _Z3barv, .-_Z3barv
.section .text.startup,"ax",@progbits
.p2align 4
.type _GLOBAL__sub_I_d, @function
_GLOBAL__sub_I_d:
.LFB6:
.cfi_startproc
movdqa .LC0(%rip), %xmm0
movaps %xmm0, d(%rip)
ret
.cfi_endproc
.LFE6:
.size _GLOBAL__sub_I_d, .-_GLOBAL__sub_I_d
.section .init_array,"aw"
.align 8
.quad _GLOBAL__sub_I_d
.globl d
.bss
.align 16
.type d, @object
.size d, 4
d:
.zero 4 <<<--- object has only 4 bytes, 16 needed
.section .rodata.cst16,"aM",@progbits,16
.align 16
.LC0:
.long 3
.long 2
.long 1
.long 0
.ident "GCC: (GNU) 9.0.0 20190104 (experimental)"
.section .note.GNU-stack,"",@progbits
>From gcc-bugs-return-628092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 18:57:45 2019
Return-Path: <gcc-bugs-return-628092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64926 invoked by alias); 7 Jan 2019 18:57:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64617 invoked by uid 48); 7 Jan 2019 18:57:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88733] [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Mon, 07 Jan 2019 18:57: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: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-88733-4-7IDtWq792p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00901.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45371
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45371&action=edit
gcc9-pr88733.patch
Patch, so far tested just with make check-target-libgomp and gomp.exp
check-{gcc,c++-all,gfortran}.
>From gcc-bugs-return-628093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:09:52 2019
Return-Path: <gcc-bugs-return-628093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10916 invoked by alias); 7 Jan 2019 19:09:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10648 invoked by uid 48); 7 Jan 2019 19:09:48 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] [9 Regression] Spurious "redundant move in return statement"
Date: Mon, 07 Jan 2019 19:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88692-4-BuSlU50Clw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00902.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
FWIW, this tickles mongodb, julia, clang, mellowplayer and root within Fedora
rawhide.
>From gcc-bugs-return-628094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:13:42 2019
Return-Path: <gcc-bugs-return-628094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17588 invoked by alias); 7 Jan 2019 19:13: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 17495 invoked by uid 48); 7 Jan 2019 19:13:36 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/82283] Wrong warning with -Wmissing-field-initializers
Date: Mon, 07 Jan 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82283-4-yK8JMKYj3R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82283-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82283-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00903.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82283
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org,
| |dodji at gcc dot gnu.org
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing diagnostics maintainers
>From gcc-bugs-return-628095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:15:04 2019
Return-Path: <gcc-bugs-return-628095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20184 invoked by alias); 7 Jan 2019 19:15: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 20021 invoked by uid 48); 7 Jan 2019 19:14:56 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82295] Two errors produced with private/protected deleted methods
Date: Mon, 07 Jan 2019 19:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-82295-4-xhIJdwKXVX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00904.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82295
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org,
| |nathan at gcc dot gnu.org
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
cc-ing C++ FE maintainers
>From gcc-bugs-return-628096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:18:16 2019
Return-Path: <gcc-bugs-return-628096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24968 invoked by alias); 7 Jan 2019 19: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 24864 invoked by uid 48); 7 Jan 2019 19:18:11 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug objc/80912] enhancement: -Wundeclared-selector improvements
Date: Mon, 07 Jan 2019 19:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: objc
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80912-4-KKeW6DTOdw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80912-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80912-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00905.txt.bz2
Content-length: 237
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80912
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to mrs@gcc.gnu.org from comment #3)
> Yes, what you say seems reasonable.
cool, thanks for confirming.
>From gcc-bugs-return-628097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:26:18 2019
Return-Path: <gcc-bugs-return-628097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81598 invoked by alias); 7 Jan 2019 19:26: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 81417 invoked by uid 55); 7 Jan 2019 19:26:13 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88741] [9 Regression] Spurious "too long" error inside template
Date: Mon, 07 Jan 2019 19:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88741-4-0CvT9fX4Aa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00906.txt.bz2
Content-length: 590
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88741
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Mon Jan 7 19:25:41 2019
New Revision: 267656
URL: https://gcc.gnu.org/viewcvs?rev=267656&root=gcc&view=rev
Log:
PR c++/88741 - wrong error with initializer-string.
* decl.c (cp_complete_array_type): Strip any location wrappers.
* g++.dg/init/array50.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/init/array50.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:27:30 2019
Return-Path: <gcc-bugs-return-628098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83115 invoked by alias); 7 Jan 2019 19: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 83077 invoked by uid 48); 7 Jan 2019 19:27:26 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88741] [9 Regression] Spurious "too long" error inside template
Date: Mon, 07 Jan 2019 19: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88741-4-xqfalMksqu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00907.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88741
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:28:00 2019
Return-Path: <gcc-bugs-return-628099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83993 invoked by alias); 7 Jan 2019 19:27: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 83952 invoked by uid 48); 7 Jan 2019 19:27:55 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/88745] New: Darwin lacks an implementation for libbacktrace
Date: Mon, 07 Jan 2019 19:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00908.txt.bz2
Content-length: 541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Bug ID: 88745
Summary: Darwin lacks an implementation for libbacktrace
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: libbacktrace
Assignee: unassigned at gcc dot gnu.org
Reporter: iains at gcc dot gnu.org
CC: ian at gcc dot gnu.org
Target Milestone: ---
see: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00136.html
>From gcc-bugs-return-628100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:29:16 2019
Return-Path: <gcc-bugs-return-628100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85375 invoked by alias); 7 Jan 2019 19:29:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85330 invoked by uid 48); 7 Jan 2019 19:29:12 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/88745] Darwin lacks an implementation for libbacktrace
Date: Mon, 07 Jan 2019 19:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget priority bug_status keywords cf_reconfirmed_on cf_gcchost everconfirmed target_milestone
Message-ID: <bug-88745-4-N7wirQdx3N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00909.txt.bz2
Content-length: 687
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |*-*-darwin*
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Keywords| |diagnostic
Last reconfirmed| |2019-01-07
Host| |*-*-darwin*
Ever confirmed|0 |1
Target Milestone|--- |10.0
>From gcc-bugs-return-628101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:31:49 2019
Return-Path: <gcc-bugs-return-628101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89470 invoked by alias); 7 Jan 2019 19:31:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89364 invoked by uid 55); 7 Jan 2019 19:31:41 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45424] [F08] Add IS_CONTIGUOUS intrinsic
Date: Mon, 07 Jan 2019 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-45424-4-89p9usctRr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00910.txt.bz2
Content-length: 2884
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Mon Jan 7 19:30:28 2019
New Revision: 267657
URL: https://gcc.gnu.org/viewcvs?rev=267657&root=gcc&view=rev
Log:
2019-01-07 Thomas Koenig <tkoenig@gcc.gnu.org>
Harald Anlauf <anlauf@gmx.de>
Tobias Burnus <burnus@gcc.gnu.org>
PR fortran/45424
* check.c (gfc_check_is_contiguous): New function.
* expr.c (gfc_is_not_contiguous): New function.
* gfortran.h (gfc_isym_id): Add GFC_ISYM_IS_CONTIGUOUS.
Add prototype for gfc_is_not_contiguous.
* intrinsic.c (do_ts29113_check): Add GFC_ISYM_IS_CONTIGUOUS.
(add_function): Add is_contiguous.
* intrinsic.h: Add prototypes for gfc_check_is_contiguous,
gfc_simplify_is_contiguous and gfc_resolve_is_contiguous.
* intrinsic.texi: Add IS_CONTIGUOUS.
* iresolve.c (gfc_resolve_is_contiguous): New function.
* simplify.c (gfc_simplify_is_contiguous): New function.
* trans-decl.c (gfor_fncecl_is_contiguous0): New variable.
(gfc_build_intrinsic_function_decl): Add it.
* trans-intrinsic.c (gfc_conv_intrinsic_is_contiguous): New
function.
(gfc_conv_intrinsic_function): Handle GFC_ISYM_IS_CONTIGUOUS.
2019-01-07 Thomas Koenig <tkoenig@gcc.gnu.org>
Harald Anlauf <anlauf@gmx.de>
Tobias Burnus <burnus@gcc.gnu.org>
PR fortran/45424
* Makefile.am: Add intrinsics/is_contiguous.c.
* Makefile.in: Regenerated.
* gfortran.map: Add _gfortran_is_contiguous0.
* intrinsics/is_contiguous.c: New file.
* libgfortran.h: Add prototype for is_contiguous0.
2019-01-07 Thomas Koenig <tkoenig@gcc.gnu.org>
Harald Anlauf <anlauf@gmx.de>
Tobias Burnus <burnus@gcc.gnu.org>
* gfortran.dg/is_contiguous_1.f90: New test.
* gfortran.dg/is_contiguous_2.f90: New test.
* gfortran.dg/is_contiguous_3.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/is_contiguous_1.f90
trunk/gcc/testsuite/gfortran.dg/is_contiguous_2.f90
trunk/gcc/testsuite/gfortran.dg/is_contiguous_3.f90
trunk/libgfortran/intrinsics/is_contiguous.c
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/check.c
trunk/gcc/fortran/expr.c
trunk/gcc/fortran/gfortran.h
trunk/gcc/fortran/intrinsic.c
trunk/gcc/fortran/intrinsic.h
trunk/gcc/fortran/intrinsic.texi
trunk/gcc/fortran/iresolve.c
trunk/gcc/fortran/simplify.c
trunk/gcc/fortran/trans-decl.c
trunk/gcc/fortran/trans-intrinsic.c
trunk/gcc/fortran/trans.h
trunk/gcc/testsuite/ChangeLog
trunk/libgfortran/ChangeLog
trunk/libgfortran/Makefile.am
trunk/libgfortran/Makefile.in
trunk/libgfortran/gfortran.map
trunk/libgfortran/libgfortran.h
>From gcc-bugs-return-628102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:41:59 2019
Return-Path: <gcc-bugs-return-628102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97665 invoked by alias); 7 Jan 2019 19:41:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97521 invoked by uid 48); 7 Jan 2019 19:41:54 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45424] [F08] Add IS_CONTIGUOUS intrinsic
Date: Mon, 07 Jan 2019 19:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-45424-4-Mapbm7Rxw0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45424-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00911.txt.bz2
Content-length: 596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tkoenig at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Implemented, closing.
Harald, thanks a lot for picking this up again and for preparing
the patch.
>From gcc-bugs-return-628103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:42:00 2019
Return-Path: <gcc-bugs-return-628103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97837 invoked by alias); 7 Jan 2019 19:41:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97585 invoked by uid 48); 7 Jan 2019 19:41:56 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/39627] [meta-bug] Fortran 2008 support
Date: Mon, 07 Jan 2019 19:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-39627-4-0iIjLFio9T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-39627-4@http.gcc.gnu.org/bugzilla/>
References: <bug-39627-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00912.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39627
Bug 39627 depends on bug 45424, which changed state.
Bug 45424 Summary: [F08] Add IS_CONTIGUOUS intrinsic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:42:01 2019
Return-Path: <gcc-bugs-return-628104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98079 invoked by alias); 7 Jan 2019 19:42: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 97607 invoked by uid 48); 7 Jan 2019 19:41:56 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53320] -fcheck=pointer should diagnose pointer-assignment of a noncontiguous tgt to a CONTIGUOUS ptr
Date: Mon, 07 Jan 2019 19:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-53320-4-tnrYFKeMkW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53320-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53320-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00913.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53320
Bug 53320 depends on bug 45424, which changed state.
Bug 45424 Summary: [F08] Add IS_CONTIGUOUS intrinsic
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45424
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:46:17 2019
Return-Path: <gcc-bugs-return-628105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105182 invoked by alias); 7 Jan 2019 19:46:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105093 invoked by uid 48); 7 Jan 2019 19:46:09 -0000
From: "davmac at davmac dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80916] [7/8/9 Regression] Spurious "declared 'static' but never defined" warning
Date: Mon, 07 Jan 2019 19: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: 7.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davmac at davmac dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80916-4-VRCtaLHnvS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00914.txt.bz2
Content-length: 694
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80916
--- Comment #6 from Davin McCall <davmac at davmac dot org> ---
> The wording could be improved, but why do you think the warning is spurious?
I guess I think that the warning is spurious given the current wording? It may
well be legitimate to warn that there is a declaration of a function with
internal linkage but no definition, which may be what triggered this warning
originally (it no longer triggers in my current code base, so I can't easily
verify). But that's not what the warning does say.
If you'd prefer to change the title to reflect that the wording of the warning
doesn't match its cause, I have no issue with that.
>From gcc-bugs-return-628106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:55:25 2019
Return-Path: <gcc-bugs-return-628106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116491 invoked by alias); 7 Jan 2019 19:55:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116375 invoked by uid 48); 7 Jan 2019 19:55:19 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/88728] Boostrap with -Og fails with garbled file libgcov-profiler.i
Date: Mon, 07 Jan 2019 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88728-4-HPJ9xT1Zr8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00915.txt.bz2
Content-length: 590
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I updated trunk, started bootstrap again, and now it goes past
the error.
So, cosmic rays or something that came and went. Strange.
Closing as WORKSFORME for now.
>From gcc-bugs-return-628107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 19:55:25 2019
Return-Path: <gcc-bugs-return-628107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116629 invoked by alias); 7 Jan 2019 19:55: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 116425 invoked by uid 48); 7 Jan 2019 19:55:21 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/82738] [meta-bug] issues with the -Og optimization level
Date: Mon, 07 Jan 2019 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 7.2.1
X-Bugzilla-Keywords: meta-bug
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_status resolution
Message-ID: <bug-82738-4-Cy0OTV6YP4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00916.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82738
Bug 82738 depends on bug 88728, which changed state.
Bug 88728 Summary: Boostrap with -Og fails with garbled file libgcov-profiler.i
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88728
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
>From gcc-bugs-return-628108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:09:42 2019
Return-Path: <gcc-bugs-return-628108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125104 invoked by alias); 7 Jan 2019 20:09: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 111698 invoked by uid 48); 7 Jan 2019 20:09:37 -0000
From: "nipatriknilsson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88746] New: structs: internal compiler error: in output_constructor_regular_field, at varasm.c:5030
Date: Mon, 07 Jan 2019 20:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nipatriknilsson 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-88746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00917.txt.bz2
Content-length: 2883
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88746
Bug ID: 88746
Summary: structs: internal compiler error: in
output_constructor_regular_field, at varasm.c:5030
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nipatriknilsson at gmail dot com
Target Milestone: ---
Created attachment 45372
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45372&action=edit
Source code to generate the compiler error
Below is a code which generates an internal compiler error. Removing "MENU2"
and its siblings produce a executable code.
/*
cc src/structerror.cpp -o build/structerror
src/structerror.cpp:45:1: internal compiler error: in
output_constructor_regular_field, at varasm.c:5030
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
*/
struct xxxx_option
{
const char *option;
const char *description;
};
struct xxxx_menu_sub
{
const char *category;
struct xxxx_option option [];
};
struct xxxx_menu_sub menu [] =
{
{
"MENU1",
{
{ "a", "AAA" },
{ "b", "BBB" }
}
},
{
"MENU2",
{
{ "c", "CCC" },
{ "d", "DDD" }
}
}
};
int main ()
{
return 0;
}//Line 45
/*
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.3.0-27ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
*/
>From gcc-bugs-return-628109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:11:55 2019
Return-Path: <gcc-bugs-return-628109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39914 invoked by alias); 7 Jan 2019 20:11: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 30534 invoked by uid 48); 7 Jan 2019 20:11:51 -0000
From: "nipatriknilsson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88746] structs: internal compiler error: in output_constructor_regular_field, at varasm.c:5030
Date: Mon, 07 Jan 2019 20:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nipatriknilsson at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88746-4-FDTWFIwvaP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00918.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88746
--- Comment #1 from Patrik Nilsson <nipatriknilsson at gmail dot com> ---
Created attachment 45373
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45373&action=edit
ii file from the compiler
>From gcc-bugs-return-628110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:13:01 2019
Return-Path: <gcc-bugs-return-628110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60719 invoked by alias); 7 Jan 2019 20:13:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51297 invoked by uid 48); 7 Jan 2019 20:12:57 -0000
From: "nipatriknilsson at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88746] structs: internal compiler error: in output_constructor_regular_field, at varasm.c:5030
Date: Mon, 07 Jan 2019 20:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nipatriknilsson at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88746-4-25qP7r5Iz7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00919.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88746
--- Comment #2 from Patrik Nilsson <nipatriknilsson at gmail dot com> ---
Created attachment 45374
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45374&action=edit
s file produced by the compiler
>From gcc-bugs-return-628111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:18:49 2019
Return-Path: <gcc-bugs-return-628111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55386 invoked by alias); 7 Jan 2019 20:18:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55227 invoked by uid 48); 7 Jan 2019 20:18:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87851] [8/9 Regression] Wrong return type for len_trim
Date: Mon, 07 Jan 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
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-87851-4-XP6UT7ah4Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00920.txt.bz2
Content-length: 1898
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87851
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Here is the result of running f951 with -O under the debugger
and breaking on optimize_expr:
Breakpoint 1, optimize_expr (e=0x2688cf0, walk_subtrees=0x7fffffffd81c,
data=0x0) at ../../trunk/gcc/fortran/frontend-passes.c:340
(gdb) call gfc_debug_expr(*e)
__len_trim1[[((main:c) ((arg not-present)))]]
(gdb) p (*e)->ts
$2 = {type = BT_INTEGER, kind = 4, u = {derived = 0x0, cl = 0x0, pad = 0},
interface = 0x0, is_c_interop = 0, is_iso_c = 0, f90_type = BT_UNKNOWN,
deferred = false, interop_kind = 0x0}
This is wrong, the kind should be 8.
Setting (*e)->ts.kind to 8 and letting the test run to completion,
and comparing the different assemblies generated (len_trim_8.s
is the one with the kind set to 8)
--- len_trim_8.s 2019-01-07 21:13:33.494640974 +0100
+++ len_trim.s 2019-01-07 21:13:41.526726760 +0100
@@ -10,20 +10,20 @@
.cfi_startproc
subq $552, %rsp
.cfi_def_cfa_offset 560
- movw $8289, 533(%rsp)
- movb $32, 535(%rsp)
+ movw $8289, 537(%rsp)
+ movb $32, 539(%rsp)
movq $.LC0, 8(%rsp)
movl $4, 16(%rsp)
movl $128, (%rsp)
movl $6, 4(%rsp)
movq %rsp, %rdi
call _gfortran_st_write
- leaq 533(%rsp), %rsi
+ leaq 537(%rsp), %rsi
movl $3, %edi
call _gfortran_string_len_trim
- movq %rax, 536(%rsp)
- movl $8, %edx
- leaq 536(%rsp), %rsi
+ movl %eax, 540(%rsp)
+ movl $4, %edx
+ leaq 540(%rsp), %rsi
movq %rsp, %rdi
call _gfortran_transfer_integer_write
movq %rsp, %rdi
If I read this correctly, the function is called with
four-byte arguments, but it should be eight.
>From gcc-bugs-return-628112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:33:10 2019
Return-Path: <gcc-bugs-return-628112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89034 invoked by alias); 7 Jan 2019 20:33: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 88956 invoked by uid 48); 7 Jan 2019 20:33:05 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/88747] New: jit testsuite failures: test-sum-of-squares.c.exe (and test-combination)
Date: Mon, 07 Jan 2019 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00921.txt.bz2
Content-length: 611
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88747
Bug ID: 88747
Summary: jit testsuite failures: test-sum-of-squares.c.exe (and
test-combination)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: jit
Assignee: dmalcolm at gcc dot gnu.org
Reporter: dmalcolm at gcc dot gnu.org
Target Milestone: ---
As noted in https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00227.html one of the
assertions in test-sum-of-squares.c has started failing.
>From gcc-bugs-return-628113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:37:28 2019
Return-Path: <gcc-bugs-return-628113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98486 invoked by alias); 7 Jan 2019 20:37: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 98375 invoked by uid 48); 7 Jan 2019 20:37:22 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84849] Ambiguous resolution of braze initializer list to a class with explicit constructors
Date: Mon, 07 Jan 2019 20:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84849-4-Aekfy2yEtf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00922.txt.bz2
Content-length: 700
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84849
ensadc at mailnesia dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ensadc at mailnesia dot com
--- Comment #5 from ensadc at mailnesia dot com ---
This is also ambiguous and seems to have the same cause (i.e. overload
resolution accepts list-initialization that calls explicit constructor when
forming the implicit conversion sequence):
template<class>
struct in_place_type_t { explicit in_place_type_t() = default; };
struct A { };
int f(A);
int f(in_place_type_t<A>);
int x = f({});
>From gcc-bugs-return-628114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:39:19 2019
Return-Path: <gcc-bugs-return-628114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101499 invoked by alias); 7 Jan 2019 20:39: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 101378 invoked by uid 48); 7 Jan 2019 20:39:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82295] Two errors produced with private/protected deleted methods
Date: Mon, 07 Jan 2019 20:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82295-4-bLZrXGBPK9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00923.txt.bz2
Content-length: 325
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82295
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This was already fixed for GCC 8, by r258003
PR c++/84447 - ICE with deleted inherited ctor with default arg.
* call.c (build_over_call): Handle deleted functions in one place.
>From gcc-bugs-return-628115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 20:46:58 2019
Return-Path: <gcc-bugs-return-628115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106769 invoked by alias); 7 Jan 2019 20:46:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106701 invoked by uid 55); 7 Jan 2019 20:46:51 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Mon, 07 Jan 2019 20:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88721-4-Hi2vE96KoX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00924.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
--- Comment #6 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
>> I've just successfully finished a sparc-sun-solaris2.11 with it: worked fine.
>
> Thanks, same for me but for some reason I didn't have the original failure.
This is weird indeed: I've just successfully bootstrapped mainline as of
r267652 without either patch.
>From gcc-bugs-return-628116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:21:49 2019
Return-Path: <gcc-bugs-return-628116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81972 invoked by alias); 7 Jan 2019 21:21:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81894 invoked by uid 48); 7 Jan 2019 21:21:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Mon, 07 Jan 2019 21:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88713-4-6lWeUVKtRi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00925.txt.bz2
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |koenigni at gcc dot gnu.org
--- Comment #16 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #15)
> So can the fortran FE inline the _gfortran_internal_pack() call? It looks
> like
> flang manages to elide this when inlining the function at least?
In principle, this could be done. I guess it would be a good idea to
create a test case first which would emulate what inlining pack would do.
>From gcc-bugs-return-628117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:26:36 2019
Return-Path: <gcc-bugs-return-628117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87726 invoked by alias); 7 Jan 2019 21:26:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87695 invoked by uid 48); 7 Jan 2019 21:26:30 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/88747] [9 Regression] jit testsuite failures: test-sum-of-squares.c.exe (and test-combination)
Date: Mon, 07 Jan 2019 21:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88747-4-3Z9IkbULEj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00926.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88747
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Am testing a fix for this.
>From gcc-bugs-return-628118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:29:20 2019
Return-Path: <gcc-bugs-return-628118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94730 invoked by alias); 7 Jan 2019 21:29:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92557 invoked by uid 55); 7 Jan 2019 21:29:14 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88731] [DR 481] Rejects well-formed program using bit-fields in _Generic.
Date: Mon, 07 Jan 2019 21:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88731-4-SKxC9hCDb0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00927.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88731
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
GCC makes the integer type of the bit-field in question "unsigned:4".
See DR#315 (also, see the line of C90 DRs that led to the wording changes
in C99 relating to types of bit-fields, references in
<https://gcc.gnu.org/ml/gcc/2017-10/msg00192.html>).
>From gcc-bugs-return-628119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:34:50 2019
Return-Path: <gcc-bugs-return-628119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 654 invoked by alias); 7 Jan 2019 21:34:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128687 invoked by uid 48); 7 Jan 2019 21:34:45 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88748] New: IS_CONTIGUOUS mishandles arrays of derived type components
Date: Mon, 07 Jan 2019 21: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00928.txt.bz2
Content-length: 872
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88748
Bug ID: 88748
Summary: IS_CONTIGUOUS mishandles arrays of derived type
components
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: anlauf at gmx dot de
Target Milestone: ---
The patch committed to fix to PR 45424 does not handle the examples given
there in comment 1:
type t
integer :: i, j
end type t
type(t) :: x(5)
print *, is_contiguous(x(:)) ! Shall be (and is) true
print *, is_contiguous(x(:)%i) ! Shall be false - but prints "true".
end
gfortran rev. 267658 prints:
T
T
while Intel v15 (and later) and NAG 6.2 print:
T
F
(Note to self: need to check PR 45424 comment 2).
>From gcc-bugs-return-628120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:41:49 2019
Return-Path: <gcc-bugs-return-628120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32953 invoked by alias); 7 Jan 2019 21:41: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 32886 invoked by uid 48); 7 Jan 2019 21:41:45 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/56428] [C++11] "is not a constant expression" when comparing non-type template argument to nullptr
Date: Mon, 07 Jan 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-56428-4-0RttAVAqDv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56428-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00929.txt.bz2
Content-length: 583
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56428
Barry Revzin <barry.revzin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #2 from Barry Revzin <barry.revzin at gmail dot com> ---
Mr. Wakely's example now passes on trunk, but this one fails:
template <bool> struct Z { };
struct C
{
void f();
Z<&C::f == nullptr> z;
};
I'm not sure incompleteness matters?
>From gcc-bugs-return-628121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:44:05 2019
Return-Path: <gcc-bugs-return-628121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35104 invoked by alias); 7 Jan 2019 21:44:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35055 invoked by uid 48); 7 Jan 2019 21:44:00 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88748] IS_CONTIGUOUS mishandles arrays of derived type components
Date: Mon, 07 Jan 2019 21:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.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-88748-4-dKkEMvlhWi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00930.txt.bz2
Content-length: 551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88748
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
On darwin with r267657 I get
% gfc pr88748.f90
% ./a.out
T
F
>From gcc-bugs-return-628122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 21:56:37 2019
Return-Path: <gcc-bugs-return-628122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81716 invoked by alias); 7 Jan 2019 21:56:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81662 invoked by uid 48); 7 Jan 2019 21:56:33 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84436] [8/9 Regression] Missed optimization with switch on enum constants returning the same value
Date: Mon, 07 Jan 2019 21:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84436-4-T329FmFDly@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00931.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84436
--- Comment #13 from Romain Geissler <romain.geissler at amadeus dot com> ---
Apparently the clang-tlbgen failures started with r265241. Checking if it still
happens on gcc trunk with r265463 reverted.
>From gcc-bugs-return-628123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:16:03 2019
Return-Path: <gcc-bugs-return-628123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9633 invoked by alias); 7 Jan 2019 22:16:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9455 invoked by uid 48); 7 Jan 2019 22:15:57 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 22:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray 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-88572-4-m66ZiY8l9l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00932.txt.bz2
Content-length: 1549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #9 from Will Wray <wjwray at gmail dot com> ---
The patch below seems to work as far as I've tested - please review.
It looks like the bool first_initializer_p argument to reshape_init_r
gives the context that is needed, according to the function comment;
/* ...
FIRST_INITIALIZER_P is true if this is the first initializer of the
outermost CONSTRUCTOR node. */
If I read this right then this bool arg is true for scalar init and
false when initializing a scalar member of an aggregate (class or array).
The patch below rejects
int ii{{0}};
--- gcc/cp/decl.c
+++ gcc/cp/decl.c
@@ -6054,16 +6054,19 @@ reshape_init_r (tree type, reshape_iter
{
if (SCALAR_TYPE_P (type))
{
- if (cxx_dialect < cxx11
- /* Isn't value-initialization. */
- || CONSTRUCTOR_NELTS (stripped_init) > 0)
+ if (cxx_dialect < cxx11 || first_initializer_p)
{
if (complain & tf_error)
error ("braces around scalar initializer for type %qT",
type);
init = error_mark_node;
}
- }
+ else if (CONSTRUCTOR_NELTS (stripped_init) > 0)
+ {
+ warning (0, "braces around scalar initializer for type %qT",
+ type);
+ }
+ }
else
maybe_warn_cpp0x (CPP0X_INITIALIZER_LISTS);
}
>From gcc-bugs-return-628124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:20:03 2019
Return-Path: <gcc-bugs-return-628124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13312 invoked by alias); 7 Jan 2019 22:20: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 13240 invoked by uid 48); 7 Jan 2019 22:19:58 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] New: Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 22:20: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: romain.geissler at amadeus dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00933.txt.bz2
Content-length: 2062
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
Bug ID: 88749
Summary: Failure while building
libstdc++-v3/src/filesystem/ops.cc on trunk
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: romain.geissler at amadeus dot com
Target Milestone: ---
Hi,
With the latest move of libstdc++fs.so in libstdc++.so, I am seeing these new
build errors:
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc: In function 'void
std::experimental::filesystem::v1::last_write_time(const
std::experimental::filesystem::v1::path&,
std::experimental::filesystem::v1::file_time_type, std::error_code&)':
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:913:10: error:
'utimbuf' is not a member of 'posix'; did you mean 'utimbuf'?
913 | posix::utimbuf times;
| ^~~~~~~
In file included from
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:50,
from
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/cow-ops.cc:26:
/home/jenkins/workspace/OTF_Toolchain_release_20.0-GWCRYYLPVAZ3GI64ZF43J2FVALYHUCNKGFBXVRTH6NJF73DCK7SQ/output/build/temporary-system/install/include/utime.h:36:8:
note: 'utimbuf' declared here
36 | struct utimbuf
| ^~~~~~~
In file included from
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/cow-ops.cc:26:
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:914:3: error: 'times'
was not declared in this scope; did you mean 'time'?
914 | times.modtime = s.count();
| ^~~~~
| time
/workdir/src/gcc-9.0.0/libstdc++-v3/src/filesystem/ops.cc:917:14: error:
'utime' is not a member of 'posix'; did you mean 'utime'?
917 | if (posix::utime(p.c_str(), ×))
| ^~~~~
So there may need some fixes around things like _GLIBCXX_USE_UTIMENSAT or
_GLIBCXX_HAVE_UTIME_H.
Cheers,
Romain
>From gcc-bugs-return-628125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:25:36 2019
Return-Path: <gcc-bugs-return-628125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86406 invoked by alias); 7 Jan 2019 22: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 85183 invoked by uid 48); 7 Jan 2019 22:24:51 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 22:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray 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-88572-4-voNb1bqBNX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00934.txt.bz2
Content-length: 312
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #10 from Will Wray <wjwray at gmail dot com> ---
Re: warnings; I certainly prefer to have this accepted with no warning
(i.e. remove the 'else if' warning in the patch above).
Saves having to disable the warning in GCC, as I have to do in Clang.
>From gcc-bugs-return-628126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:31:04 2019
Return-Path: <gcc-bugs-return-628126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98525 invoked by alias); 7 Jan 2019 22:31: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 98311 invoked by uid 48); 7 Jan 2019 22:30:50 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88748] IS_CONTIGUOUS mishandles arrays of derived type components
Date: Mon, 07 Jan 2019 22:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
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-88748-4-fJyiiOsn0N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00935.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88748
Harald Anlauf <anlauf at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from Harald Anlauf <anlauf at gmx dot de> ---
(In reply to Dominique d'Humieres from comment #1)
> On darwin with r267657 I get
>
> % gfc pr88748.f90
> % ./a.out
> T
> F
Damn, I picked the wrong installation path. You're right. Closing.
>From gcc-bugs-return-628127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:40:21 2019
Return-Path: <gcc-bugs-return-628127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110876 invoked by alias); 7 Jan 2019 22:40:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110779 invoked by uid 55); 7 Jan 2019 22:40:16 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] Strange error message about nested function declared but not defined when using inline.
Date: Mon, 07 Jan 2019 22:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88720-4-4TXEvzCLFe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00936.txt.bz2
Content-length: 2273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
--- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Mon Jan 7 22:39:43 2019
New Revision: 267665
URL: https://gcc.gnu.org/viewcvs?rev=267665&root=gcc&view=rev
Log:
Fix diagnostics for never-defined inline and nested functions (PR c/88720, PR
c/88726).
Bugs 88720 and 88726 report issues where a function is declared inline
in an inner scope, resulting in spurious diagnostics about it being
declared but never defined when that scope is left (possibly in some
cases also wrongly referring to the function as a nested function).
These are regressions that were introduced with the support for C99
inline semantics in 4.3 (they don't appear with 4.2; it's possible
some aspects of the bugs might have been introduced later than 4.3).
For the case of functions being wrongly referred to as nested,
DECL_EXTERNAL was not the right condition for a function being
non-nested; TREE_PUBLIC is appropriate for the case of non-nested
functions with external linkage, while !b->nested means this is the
outermost scope in which the function was declared and so avoids
catching the case of a file-scope static being redeclared inline
inside a function.
For the non-nested, external-linkage case, the code attempts to avoid
duplicate diagnostics by diagnosing only when scope != external_scope,
but actually scope == external_scope is more appropriate, as it's only
when the file and external scopes are popped that the code can
actually tell whether a function ended up being defined, and all such
functions will appear in the (GCC-internal) external scope.
Bootstrapped with no regressions on x86_64-pc-linux-gnu.
PR c/88720
PR c/88726
gcc/c:
* c-decl.c (pop_scope): Use TREE_PUBLIC and b->nested to determine
whether a function is nested, not DECL_EXTERNAL. Diagnose inline
functions declared but never defined only for external scope, not
for other scopes.
gcc/testsuite:
* gcc.dg/inline-40.c, gcc.dg/inline-41.c: New tests.
Added:
trunk/gcc/testsuite/gcc.dg/inline-40.c
trunk/gcc/testsuite/gcc.dg/inline-41.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:40:21 2019
Return-Path: <gcc-bugs-return-628128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110904 invoked by alias); 7 Jan 2019 22:40: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 110754 invoked by uid 55); 7 Jan 2019 22:40:15 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] GCC thinks that translation unit does not contain a definition of inline function.
Date: Mon, 07 Jan 2019 22:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88726-4-NLeZOYfllD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00937.txt.bz2
Content-length: 2273
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
--- Comment #1 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Mon Jan 7 22:39:43 2019
New Revision: 267665
URL: https://gcc.gnu.org/viewcvs?rev=267665&root=gcc&view=rev
Log:
Fix diagnostics for never-defined inline and nested functions (PR c/88720, PR
c/88726).
Bugs 88720 and 88726 report issues where a function is declared inline
in an inner scope, resulting in spurious diagnostics about it being
declared but never defined when that scope is left (possibly in some
cases also wrongly referring to the function as a nested function).
These are regressions that were introduced with the support for C99
inline semantics in 4.3 (they don't appear with 4.2; it's possible
some aspects of the bugs might have been introduced later than 4.3).
For the case of functions being wrongly referred to as nested,
DECL_EXTERNAL was not the right condition for a function being
non-nested; TREE_PUBLIC is appropriate for the case of non-nested
functions with external linkage, while !b->nested means this is the
outermost scope in which the function was declared and so avoids
catching the case of a file-scope static being redeclared inline
inside a function.
For the non-nested, external-linkage case, the code attempts to avoid
duplicate diagnostics by diagnosing only when scope != external_scope,
but actually scope == external_scope is more appropriate, as it's only
when the file and external scopes are popped that the code can
actually tell whether a function ended up being defined, and all such
functions will appear in the (GCC-internal) external scope.
Bootstrapped with no regressions on x86_64-pc-linux-gnu.
PR c/88720
PR c/88726
gcc/c:
* c-decl.c (pop_scope): Use TREE_PUBLIC and b->nested to determine
whether a function is nested, not DECL_EXTERNAL. Diagnose inline
functions declared but never defined only for external scope, not
for other scopes.
gcc/testsuite:
* gcc.dg/inline-40.c, gcc.dg/inline-41.c: New tests.
Added:
trunk/gcc/testsuite/gcc.dg/inline-40.c
trunk/gcc/testsuite/gcc.dg/inline-41.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:42:19 2019
Return-Path: <gcc-bugs-return-628129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119805 invoked by alias); 7 Jan 2019 22:42:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119753 invoked by uid 48); 7 Jan 2019 22:42:15 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] [7/8 Regression] Strange error message about nested function declared but not defined when using inline.
Date: Mon, 07 Jan 2019 22:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on target_milestone short_desc everconfirmed
Message-ID: <bug-88720-4-IL8E6V9cYz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00938.txt.bz2
Content-length: 912
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Target Milestone|--- |8.3
Summary|Strange error message about |[7/8 Regression] Strange
|nested function declared |error message about nested
|but not defined when using |function declared but not
|inline. |defined when using inline.
Ever confirmed|0 |1
--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed so far for GCC 9.
>From gcc-bugs-return-628130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:43:29 2019
Return-Path: <gcc-bugs-return-628130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122541 invoked by alias); 7 Jan 2019 22:43: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 122458 invoked by uid 48); 7 Jan 2019 22:43:24 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] [7/8 Regression] GCC thinks that translation unit does not contain a definition of inline function.
Date: Mon, 07 Jan 2019 22:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone short_desc everconfirmed
Message-ID: <bug-88726-4-OLwoj2tTP0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00939.txt.bz2
Content-length: 844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-07
Target Milestone|--- |8.3
Summary|GCC thinks that translation |[7/8 Regression] GCC thinks
|unit does not contain a |that translation unit does
|definition of inline |not contain a definition of
|function. |inline function.
Ever confirmed|0 |1
--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed so far for GCC 9.
>From gcc-bugs-return-628131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:54:09 2019
Return-Path: <gcc-bugs-return-628131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8035 invoked by alias); 7 Jan 2019 22:54:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7949 invoked by uid 48); 7 Jan 2019 22:54:04 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 22:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-JlWw3wtHaJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00940.txt.bz2
Content-length: 186
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
What target is this on? If Linux what libc (including version)?
>From gcc-bugs-return-628132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:55:20 2019
Return-Path: <gcc-bugs-return-628132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10374 invoked by alias); 7 Jan 2019 22:55: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 10271 invoked by uid 55); 7 Jan 2019 22:55:14 -0000
From: "amodra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88614] ICE: output_operand: invalid %z value
Date: Mon, 07 Jan 2019 22:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amodra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88614-4-qFSR9O25p9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88614-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88614-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00941.txt.bz2
Content-length: 1575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88614
--- Comment #1 from Alan Modra <amodra at gcc dot gnu.org> ---
Author: amodra
Date: Mon Jan 7 22:54:40 2019
New Revision: 267666
URL: https://gcc.gnu.org/viewcvs?rev=267666&root=gcc&view=rev
Log:
genattrtab bit-rot, and if_then_else in values
This patch started off just by adding if_then_else support in
write_attr_value to be able to write a saner expression for powerpc
tls_gdld_nomark length. Then I noticed bit-rot in functions used to
calculate insn_default_length, insn_min_length, and length_unit_log
(which are used by the shorten_branches pass). These functions
don't handle a const_int length value and return an "unknown" status
that isn't used, or in the case of or_attr_value, doesn't need to be
used. min_attr_value also attempts to return INT_MAX for the
unhandled rtl case, but this can get lost in recursive calls. I fixed
that problem by returning INT_MIN instead, and translating that to
INT_MAX in the only caller of min_attr_value.
PR target/88614
* genattrtab.c (max_attr_value, min_attr_value, or_attr_value):
Delete "unknownp" parameter. Adjust callers. Handle
CONST_INT, PLUS, MINUS, and MULT.
(attr_value_aligned): Renamed from or_attr_value.
(min_attr_value): Return INT_MIN for unhandled rtl case..
(min_fn): ..and translate to INT_MAX here.
(write_length_unit_log): Modify to cope without "unknown".
(write_attr_value): Handle IF_THEN_ELSE.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/genattrtab.c
>From gcc-bugs-return-628133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:56:25 2019
Return-Path: <gcc-bugs-return-628133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11933 invoked by alias); 7 Jan 2019 22:56:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11858 invoked by uid 55); 7 Jan 2019 22:56:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Mon, 07 Jan 2019 22:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88701-4-46XrHNCG8r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00942.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 7 22:55:48 2019
New Revision: 267667
URL: https://gcc.gnu.org/viewcvs?rev=267667&root=gcc&view=rev
Log:
PR c/88701
* c-decl.c (build_compound_literal): If not TREE_STATIC, only pushdecl
if current_function_decl is non-NULL.
* gcc.dg/pr88701.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/pr88701.c
Modified:
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 22:57:46 2019
Return-Path: <gcc-bugs-return-628134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13986 invoked by alias); 7 Jan 2019 22:57:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13891 invoked by uid 48); 7 Jan 2019 22:57:41 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86020] [8/9 Regression] Performance regression in Eigen geometry.cpp test starting with r248334
Date: Mon, 07 Jan 2019 22:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86020-4-UrsbQPnxqL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00943.txt.bz2
Content-length: 194
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86020
--- Comment #7 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Thanks! I've asked our performance team to re-measure with this change.
>From gcc-bugs-return-628135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:01:27 2019
Return-Path: <gcc-bugs-return-628135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24022 invoked by alias); 7 Jan 2019 23:01:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22267 invoked by uid 48); 7 Jan 2019 23:00:06 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] New: [9.0 regression] runtime error in statically binaries
Date: Mon, 07 Jan 2019 23:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00944.txt.bz2
Content-length: 1643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
Bug ID: 88750
Summary: [9.0 regression] runtime error in statically binaries
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: juergen.reuter at desy dot de
Target Milestone: ---
This is really tricky, in our test-suite, we do have a static test. You can get
our code from
http://whizard.tp.nt.uni-siegen.de/tarballs/whizard-nightly-latest.tar.gz
You need gfortran [gcc/g++ for interfaces] as well as the OCaml compiler.
Then you do ./configure, make -j4, make -j4 check. The check you can also just
perform `make check` in the build/tests/functional_tests directory. There are
two tests, static_1.run and static_2.run which you can separately run as `make
check TESTS="static_1.run static_2.run". Both segfault now as
static_2.exe(65376,0x1186ee5c0) malloc: *** error for object 0x115f18ee0:
pointer being freed was not allocated
static_2.exe(65376,0x1186ee5c0) malloc: *** set a breakpoint in
malloc_error_break to debug
./static_2.run: line 25: 65376 Abort trap: 6 ./$exe $exe.sin
--logfile $exe.log --no-library --no-logging --no-model --no-banner --rebuild
They have been linked using gfortran. The operating system is MAC OS X 10.14.2
and XCode 10.1. I couldn't yet reproduce this on Linux, and I haven't yet been
able to boil this down to a simpler example. Unfortunately, on MAC OS X I
somehow cannot even run gdb properly. I hope you can help.
>From gcc-bugs-return-628136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:02:47 2019
Return-Path: <gcc-bugs-return-628136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27920 invoked by alias); 7 Jan 2019 23:02: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 27771 invoked by uid 48); 7 Jan 2019 23:02:35 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/79593] [7/8/9 Regression] Poor/Worse code generation for FPU on versions after 6
Date: Mon, 07 Jan 2019 23:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79593-4-HOZR6d9yo4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00945.txt.bz2
Content-length: 199
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79593
--- Comment #24 from Jeffrey A. Law <law at redhat dot com> ---
Given how rare this is, I won't object to trying to deal with it via a
peephole.
>From gcc-bugs-return-628137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:08:25 2019
Return-Path: <gcc-bugs-return-628137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34804 invoked by alias); 7 Jan 2019 23:08:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34695 invoked by uid 48); 7 Jan 2019 23:08:21 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Mon, 07 Jan 2019 23:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87957-4-oyqK4e9OIW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00946.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
--- Comment #27 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I already did printf debugging and indeed we only need to decide how to
> adjust type_with_linkage_p so it returns false for all Ada types. Maybe
> cleanest would be to add flag to TYPE_DECL which C++ FE will set and
> other frontends won't, but perhaps there is easier way around. Jason?
What does it mean exactly for a type to have or not have a linkage?
>From gcc-bugs-return-628138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:31:46 2019
Return-Path: <gcc-bugs-return-628138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75195 invoked by alias); 7 Jan 2019 23:31:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74450 invoked by uid 48); 7 Jan 2019 23:31:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 23:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to short_desc everconfirmed
Message-ID: <bug-88749-4-0hvdGdx9jC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00947.txt.bz2
Content-length: 1022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-07
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Summary|Failure while building |[9 Regression] Failure
|libstdc++-v3/src/filesystem |while building
|/ops.cc on trunk |libstdc++-v3/src/filesystem
| |/ops.cc on trunk
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I added _GLIBCXX_USE_UTIME to be used instead of _GLIBCXX_HAVE_UTIME_H but only
changed one of the two places that should use it.
>From gcc-bugs-return-628139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:39:42 2019
Return-Path: <gcc-bugs-return-628139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30993 invoked by alias); 7 Jan 2019 23:39:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30925 invoked by uid 55); 7 Jan 2019 23:39:37 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Mon, 07 Jan 2019 23:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87957-4-5LwZErzuRv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00948.txt.bz2
Content-length: 826
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
--- Comment #28 from Jan Hubicka <hubicka at ucw dot cz> ---
> > I already did printf debugging and indeed we only need to decide how to
> > adjust type_with_linkage_p so it returns false for all Ada types. Maybe
> > cleanest would be to add flag to TYPE_DECL which C++ FE will set and
> > other frontends won't, but perhaps there is easier way around. Jason?
>
> What does it mean exactly for a type to have or not have a linkage?
Types with linkage are C++ ODR types. They have associated mangled name
(which is after free lang data available by DECL_ASSEMBLER_NAME of
the TYPE_DECL of TYPE_NAME) and if the names match in different units,
one knows that they are same types even if tree representation diverges.
In C++ those are records, unions and enums.
Honza
>From gcc-bugs-return-628140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:42:46 2019
Return-Path: <gcc-bugs-return-628140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54450 invoked by alias); 7 Jan 2019 23:42:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54398 invoked by uid 48); 7 Jan 2019 23:42:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 23:42: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: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-mCHKMLwIRj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00949.txt.bz2
Content-length: 913
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I don't understand why the configure script would not have set
_GLIBCXX_USE_UTIME when utimbuf and utime() are apparently available (because
GCC is suggesting them as alternatives for posix::utimbuf and posix::utime).
I think this should fix it, but as Andrew requested, please provide a lot more
information about your target:
--- a/libstdc++-v3/src/filesystem/ops.cc
+++ b/libstdc++-v3/src/filesystem/ops.cc
@@ -909,7 +909,7 @@ fs::last_write_time(const path& p
__attribute__((__unused__)),
ec.assign(errno, std::generic_category());
else
ec.clear();
-#elif _GLIBCXX_HAVE_UTIME_H
+#elif _GLIBCXX_USE_UTIME && _GLIBCXX_HAVE_SYS_STAT_H
posix::utimbuf times;
times.modtime = s.count();
times.actime = do_stat(p, ec, [](const auto& st) { return st.st_atime; },
>From gcc-bugs-return-628141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:46:05 2019
Return-Path: <gcc-bugs-return-628141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58759 invoked by alias); 7 Jan 2019 23:46:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58290 invoked by uid 48); 7 Jan 2019 23:45:26 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 23:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-fsRpIEyrsz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00950.txt.bz2
Content-length: 311
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #4 from Romain Geissler <romain.geissler at amadeus dot com> ---
Thanks I will test this ASAP.
I am using x86-64, and a very recent glibc near current master:
GLIBC_VERSION="2.28.90"
GLIBC_COMMIT="0253580a75decdaf22b6abce60d8265b2adb7dea"
>From gcc-bugs-return-628142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:46:11 2019
Return-Path: <gcc-bugs-return-628142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59323 invoked by alias); 7 Jan 2019 23:46:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58752 invoked by uid 48); 7 Jan 2019 23:46:04 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Mon, 07 Jan 2019 23:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88713-4-UBhR05EWJX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00951.txt.bz2
Content-length: 1148
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #17 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
What an inline packing would (approximately) produce is this:
subroutine processBPP(X, BPP, N)
integer, intent(in) :: N
real, dimension(N,3), intent(out) :: X
real, dimension(N,10), intent(in) :: BPP
integer :: i
real :: tmp1(3)
real :: tmp2(6)
integer :: k1, k2
do concurrent (i = 1:N)
k1 = 0
do
if (.not. k1 < 3) exit
tmp1(k1+1) = BPP(i,k1+1)
k1 = k1 + 1
end do
k2 = 0
do
if (.not. k2 < 6) exit
tmp2(k2+1) = BPP(i,k2+5)
k2 = k2 + 1
end do
X(i,:) = fpdbacksolve(tmp1, tmp2)
end do
end subroutine processBPP
I see no timing difference for gfortran with this to the (:) version.
Chris, can you confirm this?
And is flang still faster by a factor of two if you use this version?
>From gcc-bugs-return-628144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:47:33 2019
Return-Path: <gcc-bugs-return-628144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62659 invoked by alias); 7 Jan 2019 23:47:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62595 invoked by uid 48); 7 Jan 2019 23:47:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 23:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-FXvxT9c0Ap@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00953.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That makes no sense, because you should have _GLIBCXX_USE_UTIMENSAT defined and
never reach the lines that give errors.
>From gcc-bugs-return-628143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:47:23 2019
Return-Path: <gcc-bugs-return-628143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61947 invoked by alias); 7 Jan 2019 23:47:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61885 invoked by uid 48); 7 Jan 2019 23:47:19 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 23:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-ptVSZQ2lFy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00952.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #5 from Romain Geissler <romain.geissler at amadeus dot com> ---
Note that it was building fine with gcc commit
4a4bec8257aa255cca9be7f24a61159cadb36942 from Fri Dec 28 (aka r267451), and the
same glibc commit.
>From gcc-bugs-return-628145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:50:34 2019
Return-Path: <gcc-bugs-return-628145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71479 invoked by alias); 7 Jan 2019 23:50:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71432 invoked by uid 48); 7 Jan 2019 23:50:29 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9.0 regression] runtime error in statically linked binaries
Date: Mon, 07 Jan 2019 23:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 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-88750-4-jELIASxasl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00954.txt.bz2
Content-length: 624
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-07
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> ... Both segfault now as ...
What is the "now"? Did the tests worked after your update to MAC OS X 10.14.2
or to your latest Xcode?
>From gcc-bugs-return-628146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:53:45 2019
Return-Path: <gcc-bugs-return-628146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74204 invoked by alias); 7 Jan 2019 23:53:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74108 invoked by uid 48); 7 Jan 2019 23:53:40 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9.0 regression] runtime error in statically linked binaries
Date: Mon, 07 Jan 2019 23:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-UsPzcK3T8Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00955.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #2 from Jürgen Reuter <juergen.reuter at desy dot de> ---
The tests worked till yesterday, but only today major parts of gcc recompiled
because all files in gcc got a new timstamp. I am now trying to recompile also
gmp, mpfr and mpc with the llvm-clang from XCode 10.1 (which is from November
apparently). But my update to Mojave was before the compilation of gmp, mpfr,
and mpc (which happened end of September).
>From gcc-bugs-return-628147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:54:32 2019
Return-Path: <gcc-bugs-return-628147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75441 invoked by alias); 7 Jan 2019 23:54:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75337 invoked by uid 48); 7 Jan 2019 23:54:27 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9.0 regression] runtime error in statically linked binaries
Date: Mon, 07 Jan 2019 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-JcfKWswDdM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00956.txt.bz2
Content-length: 243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #3 from Jürgen Reuter <juergen.reuter at desy dot de> ---
And I am seeing the same problem on another Macbook (Macbook Air) since roughly
Christmas (maybe a bit before).
>From gcc-bugs-return-628148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:57:08 2019
Return-Path: <gcc-bugs-return-628148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80316 invoked by alias); 7 Jan 2019 23:57: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 80128 invoked by uid 48); 7 Jan 2019 23:57:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Mon, 07 Jan 2019 23:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-88572-4-eTUxSQ2Mks@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00957.txt.bz2
Content-length: 838
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Will Wray from comment #9)
> The patch below seems to work as far as I've tested - please review.
>
> It looks like the bool first_initializer_p argument to reshape_init_r
> gives the context that is needed, according to the function comment;
>
> /* ...
> FIRST_INITIALIZER_P is true if this is the first initializer of the
> outermost CONSTRUCTOR node. */
>
> If I read this right then this bool arg is true for scalar init and
> false when initializing a scalar member of an aggregate (class or array).
I understood it to mean something like {{1}, 2} is the first,
^^^
but apparently not. The patch works for me, but I can't review it properly.
>From gcc-bugs-return-628149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 07 23:59:33 2019
Return-Path: <gcc-bugs-return-628149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82854 invoked by alias); 7 Jan 2019 23:59: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 82765 invoked by uid 48); 7 Jan 2019 23:59:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Mon, 07 Jan 2019 23:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-UMTFTKhf1b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00958.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
What does your $target/libstdc++-v3/config.log show for the utime tests?
With glibc-2.28 I get:
configure:80229: checking for utime.h
configure:80229: result: yes
configure:80254: checking whether to build Filesystem TS support
configure:80278: result: yes
configure:80292: checking for struct dirent.d_type
configure:80352: result: yes
configure:80354: checking for realpath
configure:80432: result: yes
configure:80434: checking for utimensat
configure:80500: result: yes
configure:80502: checking for utime
configure:80566: result: yes
>From gcc-bugs-return-628150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 00:04:32 2019
Return-Path: <gcc-bugs-return-628150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89954 invoked by alias); 8 Jan 2019 00:04: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 89776 invoked by uid 48); 8 Jan 2019 00:04:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86934] Feature test macros in <version> should respect _GLIBCXX_HOSTED
Date: Tue, 08 Jan 2019 00:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86934-4-DDIC5kROLz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00959.txt.bz2
Content-length: 1450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86934
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> The current <version> header doesn't account for the fact that many features
> are not defined for freestanding builds.
>
> Also, the --enable-libstdcxx-filesystem-ts configure option means that
> <filesystem> isn't always present, even for hsoted builds (but that should
> change for GCC 9 anyway).
That was PR 86756 and is fixed now.
> I'm not sure how to do this cleanly so that <version> is always consistent
> with the real values in other headers. We could generate <version> from a
> script that processes the headers (separately for freestanding and hosted
> headers) and just extracts the __cpp_lib_* macros and the preprocessor
> conditions they depend on.
Or maybe just a script that generates the file from input like:
filesystem 201703 c++17
launder 201606 c++17 _GLIBCXX_HAVE_BUILTIN_LAUNDER
shared_timed_mutex 201402 c++14 _GLIBCXX_HAS_GTHREADS
> Also, in https://gcc.gnu.org/ml/libstdc++/2018-07/msg00128.html I said:
>
> It would be nice if we had tests to check that every macro in
> <version> matches the other definition of it (i.e. either both are
> defined to the same value, or neither is defined).
That should be simple, just include <bits/stdc++.h> and <version> and compile
with -Wsystem-headers to check for redefinition warnings.
>From gcc-bugs-return-628151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 00:08:28 2019
Return-Path: <gcc-bugs-return-628151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97696 invoked by alias); 8 Jan 2019 00:08:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97631 invoked by uid 48); 8 Jan 2019 00:08:24 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBpcGEvODc5NTddIFs5IFJlZ3Jlc3Npb25dIElDRSB0cmVlIGNoZWNr?= =?UTF-8?B?OiBleHBlY3RlZCB0cmVlIHRoYXQgY29udGFpbnMg4oCYZGVjbCBtaW5pbWFs?= =?UTF-8?B?4oCZIHN0cnVjdHVyZSwgaGF2ZSDigJhpZGVudGlmaWVyX25vZGXigJkgaW4g?= =?UTF-8?B?d2Fybl9vZHIsIGF0IGlwYS1kZXZpcnQuYzoxMDUxIHNpbmNlIHIyNjU1MTk=?Date: Tue, 08 Jan 2019 00:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87957-4-Nf4lZEc7fx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87957-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00960.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87957
--- Comment #29 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Types with linkage are C++ ODR types. They have associated mangled name
> (which is after free lang data available by DECL_ASSEMBLER_NAME of
> the TYPE_DECL of TYPE_NAME) and if the names match in different units,
> one knows that they are same types even if tree representation diverges.
>
> In C++ those are records, unions and enums.
In Ada every user-defined type has this property and the ODR cannot be
violated.
>From gcc-bugs-return-628152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 00:52:30 2019
Return-Path: <gcc-bugs-return-628152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17864 invoked by alias); 8 Jan 2019 00:52: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 17242 invoked by uid 48); 8 Jan 2019 00:52:24 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 00:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-GAYet5bvRn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00961.txt.bz2
Content-length: 1647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #8 from Romain Geissler <romain.geissler at amadeus dot com> ---
Your patch is working.
I may add some context to better understand this strange scenario. In my case,
the config log says:
configure:80434: checking for utimensat
configure:80484: x86_64-1a-linux-gnu-g++ -o conftest -O2 -mmmx -msse -msse2
-msse3 -fno-exceptions -O2 -mmmx -msse -msse2 -msse3 conftest.cpp >&5
/home/jenkins/workspace/OTF_Toolchain_release_20.0-GWCRYYLPVAZ3GI64ZF43J2FVALYHUCNKGFBXVRTH6NJF73DCK7SQ/output/build/temporary-system/install/bin/../lib/gcc/x86_64-1a-linux-gnu/9.0.0/../../../../x86_64-1a-linux-gnu/bin/ld:
cannot find -lstdc++
for all find of header check, so in the end they all end up being as not found.
I don't just build gcc or libstdc++ in my build, actually it's a full toolchain
bootstrap following what is done in Linux From Scratch. I build in that order:
- binutils, with a linker configured to look for system libraries in a
non-standard folder, empty for now
- gcc, without libstdc++
- glibc, using the above binutils/gcc, which fills in the non standard lib
folder with only a libc.
- libstdc++, using the above binutils/gcc/glibc.
At the moment we build this first libstdc++, there is no existing libstdc++
yet, thus the above configure failures.
Note that this is just the beginning of the bootstrap. After this other
gcc/libstdc++ are being built, and this time the configure script works
unpatched.
So with these explanations, do you think the patch you proposed should land in
trunk (it worked for me in that specific bootstrap configuration).
>From gcc-bugs-return-628153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 01:39:45 2019
Return-Path: <gcc-bugs-return-628153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92545 invoked by alias); 8 Jan 2019 01:39: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 92509 invoked by uid 55); 8 Jan 2019 01:39:40 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/88747] [9 Regression] jit testsuite failures: test-sum-of-squares.c.exe (and test-combination)
Date: Tue, 08 Jan 2019 01:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88747-4-rnSDbr4G2T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00962.txt.bz2
Content-length: 1061
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88747
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Author: dmalcolm
Date: Tue Jan 8 01:39:09 2019
New Revision: 267671
URL: https://gcc.gnu.org/viewcvs?rev=267671&root=gcc&view=rev
Log:
Fix jit test case (PR jit/88747)
Amongst other changes, r266077 updated value_range_base::dump so
that it additionally prints the type. This broke an assertion within
the jit testsuite, in jit.dg/test-sum-of-squares.c, which was checking
for:
": [-INF, n_"
but was now getting:
": signed int [-INF, n_"
The test is merely intended as a simple verification that we can read
dump files via gcc_jit_context_enable_dump.
This patch loosens the requirements on the dump so that it should work
with either version of value_range_base::dump.
gcc/testsuite/ChangeLog:
PR jit/88747
* jit.dg/test-sum-of-squares.c (verify_code): Update expected vrp
dump to reflect r266077.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/jit.dg/test-sum-of-squares.c
>From gcc-bugs-return-628154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 01:43:43 2019
Return-Path: <gcc-bugs-return-628154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77502 invoked by alias); 8 Jan 2019 01:43:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63069 invoked by uid 48); 8 Jan 2019 01:43:39 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/88747] [9 Regression] jit testsuite failures: test-sum-of-squares.c.exe (and test-combination)
Date: Tue, 08 Jan 2019 01:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88747-4-rUqNxZZQEt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00963.txt.bz2
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88747
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed by r267671.
>From gcc-bugs-return-628155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 02:06:47 2019
Return-Path: <gcc-bugs-return-628155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13620 invoked by alias); 8 Jan 2019 02:06:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12040 invoked by uid 48); 8 Jan 2019 02:06:41 -0000
From: "elrodc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88713] Vectorized code slow vs. flang
Date: Tue, 08 Jan 2019 02:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: elrodc at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88713-4-k7H8M7XLDy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00964.txt.bz2
Content-length: 7121
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88713
--- Comment #18 from Chris Elrod <elrodc at gmail dot com> ---
I can confirm that the inlined packing does allow gfortran to vectorize the
loop. So allowing packing to inline does seem (to me) like an optimization well
worth making.
However, performance seems to be about the same as before, still close to 2x
slower than Flang.
There is definitely something interesting going on in Flang's SLP
vectorization, though.
I defined the function:
#ifndef VECTORWIDTH
#define VECTORWIDTH 16
#endif
subroutine vpdbacksolve(Uix, x, S)
real, dimension(VECTORWIDTH,3) :: Uix
real, dimension(VECTORWIDTH,3), intent(in) :: x
real, dimension(VECTORWIDTH,6), intent(in) :: S
real, dimension(VECTORWIDTH) :: U11, U12, U22, U13, U23, U33,
&
Ui11, Ui12, Ui22, Ui33
U33 = sqrt(S(:,6))
Ui33 = 1 / U33
U13 = S(:,4) * Ui33
U23 = S(:,5) * Ui33
U22 = sqrt(S(:,3) - U23**2)
Ui22 = 1 / U22
U12 = (S(:,2) - U13*U23) * Ui22
U11 = sqrt(S(:,1) - U12**2 - U13**2)
Ui11 = 1 / U11 ! u11
Ui12 = - U12 * Ui11 * Ui22 ! u12
Uix(:,3) = Ui33*x(:,3)
Uix(:,1) = Ui11*x(:,1) + Ui12*x(:,2) - (U13 * Ui11 + U23 * Ui12) *
Uix(:,3)
Uix(:,2) = Ui22*x(:,2) - U23 * Ui22 * Uix(:,3)
end subroutine vpdbacksolve
in a .F90 file, so that VECTORWIDTH can be set appropriately while compiling.
I wanted to modify the Fortran file to benchmark these, but I'm pretty sure
Flang cheated in the benchmarks. So compiling into a shared library, and
benchmarking from Julia:
julia> @benchmark flangvtest($Uix, $x, $S)
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 15.104 ns (0.00% GC)
median time: 15.563 ns (0.00% GC)
mean time: 16.017 ns (0.00% GC)
maximum time: 49.524 ns (0.00% GC)
--------------
samples: 10000
evals/sample: 998
julia> @benchmark gfortvtest($Uix, $x, $S)
BenchmarkTools.Trial:
memory estimate: 0 bytes
allocs estimate: 0
--------------
minimum time: 24.394 ns (0.00% GC)
median time: 24.562 ns (0.00% GC)
mean time: 25.600 ns (0.00% GC)
maximum time: 58.652 ns (0.00% GC)
--------------
samples: 10000
evals/sample: 996
That is over 60% faster for Flang, which would account for much, but not all,
of the runtime difference in the actual for loops.
For comparison, the vectorized loop in processbpp covers 16 samples per
iteration. The benchmarks above were with N = 1024, so 1024/16 = 64 iterations.
For the three gfortran benchmarks (that averaged 100,000 runs of the loop),
that means each loop iteration averaged at about
1000 * (1.34003162 + 1.37529969 + 1.36087596) / (3*64)
21.230246197916664
For flang, that was:
1000 * (0.6596010 + 0.6455200 + 0.6132510) / (3*64)
9.991520833333334
so we have about 21 vs 10 ns for the loop body in gfortran vs Flang,
respectively.
Comparing the asm between:
1. Flang processbpp loop body
2. Flang vpdbacksolve
3. gfortran processbpp loop body
4. gfortran vpdbacksolve
Here are a few things I notice.
1. gfortran always uses masked reciprocal square root operations, to make sure
it only takes the square root of non-negative (positive?) numbers:
vxorps %xmm5, %xmm5, %xmm5
...
vmovups (%rsi,%rax), %zmm0
vmovups 0(%r13,%rax), %zmm9
vcmpps $4, %zmm0, %zmm5, %k1
vrsqrt14ps %zmm0, %zmm1{%k1}{z}
This might be avx512f specific?
Either way, Flang does not use masks:
vmovups (%rcx,%r14), %zmm4
vrsqrt14ps %zmm4, %zmm5
I'm having a hard time finding any information on what the performance impact
of this may be.
Agner Fog's instruction tables, for example, don't mention mask arguments for
vrsqrt14ps.
2. Within the loop body, Flang has 0 unnecessary vmov(u/a)ps. There are 8 total
plus 3 "vmuls" and 1 vfmsub231ps accessing memory, for the 12 expected per loop
iteration (fpdbacksolve's arguments are a vector of length 3 and another of
length 6; it returns a vector of length 3).
gfortran's loop body has 3 unnecessary vmovaps, copying register contents.
gfortran's vpdbacksolve subroutine has 4 unnecessary vmovaps, copying register
contents.
Flang's vpdbacksolve subroutine has 13 unnecessary vmovaps, and a couple
unnecessary memory accesses. Ouch!
They also moved on/off (the stack?)
vmovaps %zmm2, .BSS4+192(%rip)
...
vmovaps %zmm5, .BSS4+320(%rip)
...
vmovaps .BSS4+192(%rip), %zmm5
... #zmm5 is overwritten in here, I just mean to show the sort of stuff that
goes on
vmulps .BSS4+320(%rip), %zmm5, %zmm0
Some of those moves also don't get used again, and some other things are just
plain weird:
vxorps %xmm3, %xmm3, %xmm3
vfnmsub231ps %zmm2, %zmm0, %zmm3 # zmm3 = -(zmm0 * zmm2) - zmm3
vmovaps %zmm3, .BSS4+576(%rip)
Like, why zero out the 128 bit portion of zmm3 ?
I verified that the answers are still correct.
I don't know that much about how compiler's and loop vectorizer's work, but I'm
guessing in the loop, Flang managed to verify lots of things that helped out
the register allocator. And that without it, it struggled.
gfortran's vpdbacksolve also did some stuff I don't understand:
vmulps %zmm1, %zmm2, %zmm2
vxorps .LC3(%rip), %zmm2, %zmm2
vmulps %zmm6, %zmm2, %zmm4
This happens in gfortran's loop too, except the move from .LC3(%rip) was
hoisted out of the loop.
It definitely handled register allocation much better in just the function,
although not as well in the loop.
Given that Flang's vpdbacksolve did the worst here, but was still >60% faster
than gfortran's vpdbacksolve, I don't think we can attribute worse performance
here.
3. Arithmetic instructions:
vaddps:
flang-loop body: 0
flang-vpdbacksolve: 0
gfortran-loop-body: 6
gfortran-vpdbacksolve: 6
vsubps
flang-loop body: 1
flang-vpdbacksolve: 1
gfortran-loop-body: 3
gfortran-vpdbacksolve: 4
vmulps
flang-loop body: 20
flang-vpdbacksolve: 18
gfortran-loop-body: 27
gfortran-vpdbacksolve: 29
Total unfused operations:
flang-loop body: 21
flang-vpdbacksolve: 19
gfortran-loop-body: 30
gfortran-vpdbacksolve: 33
vfmadd
flang-loop body: 5
flang-vpdbacksolve: 6
gfortran-loop-body: 2
gfortran-vpdbacksolve: 3
vfnmadd
flang-loop body: 2
flang-vpdbacksolve: 4
gfortran-loop-body: 6
gfortran-vpdbacksolve: 2
vfmsub
flang-loop body: 3
flang-vpdbacksolve: 0
gfortran-loop-body: 0
gfortran-vpdbacksolve: 2
vfnmsub
flang-loop body: 0
flang-vpdbacksolve: 1
gfortran-loop-body: 0
gfortran-vpdbacksolve: 0
Total fused operations:
flang-loop body: 10
flang-vpdbacksolve: 11
gfortran-loop-body: 8
gfortran-vpdbacksolve: 7
Total arithmetic operations:
flang-loop body: 31
flang-vpdbacksolve: 30
gfortran-loop-body: 38
gfortran-vpdbacksolve: 40
So gfortran's version had more overall arithmetic instructions (but less fused
operations), but definitely not by a factor approaching the degree to which it
was slower.
>From gcc-bugs-return-628156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 02:50:36 2019
Return-Path: <gcc-bugs-return-628156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79244 invoked by alias); 8 Jan 2019 02:50: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 79116 invoked by uid 48); 8 Jan 2019 02:50:23 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Tue, 08 Jan 2019 02:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88717-4-uUsBVwp1DY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00965.txt.bz2
Content-length: 5099
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
--- Comment #4 from åˆ˜è¢‹é¼ <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #3)
> Like this
>
> diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
> index d01278d866f..9b49a2c1d9c 100644
> --- a/gcc/config/i386/i386.c
> +++ b/gcc/config/i386/i386.c
> @@ -19100,7 +19100,11 @@ ix86_avx_u128_mode_entry (void)
> rtx incoming = DECL_INCOMING_RTL (arg);
>
> if (incoming && ix86_check_avx_upper_register (incoming))
> - return AVX_U128_DIRTY;
> + {
> + /* Caller is AVX_U128_DIRTY. */
> + cfun->machine->caller_avx_u128_dirty = true;
> + return AVX_U128_DIRTY;
> + }
> }
>
> return AVX_U128_CLEAN;
> @@ -19130,6 +19134,10 @@ ix86_mode_entry (int entity)
> static int
> ix86_avx_u128_mode_exit (void)
> {
> + /* Exit mode is set to AVX_U128_DIRTY if caller is AVX_U128_DIRTY. */
> + if (cfun->machine->caller_avx_u128_dirty)
> + return AVX_U128_DIRTY;
> +
> rtx reg = crtl->return_rtx;
>
> /* Exit mode is set to AVX_U128_DIRTY if there are 256bit
> diff --git a/gcc/config/i386/i386.h b/gcc/config/i386/i386.h
> index 83b025e0cf5..c053b657a55 100644
> --- a/gcc/config/i386/i386.h
> +++ b/gcc/config/i386/i386.h
> @@ -2747,6 +2747,9 @@ struct GTY(()) machine_function {
> /* If true, ENDBR is queued at function entrance. */
> BOOL_BITFIELD endbr_queued_at_entrance : 1;
>
> + /* If true, caller is AVX_U128_DIRTY. */
> + BOOL_BITFIELD caller_avx_u128_dirty : 1;
> +
> /* The largest alignment, in bytes, of stack slot actually used. */
> unsigned int max_used_stack_alignment;
My thought is AVX_U128_DIRTY would be set when ymm/zmm appeared, and
AVX_U128_CLEAN for xmm, AVX_U128_ANY for other situations. This also works for
this case.
diff --git a/gcc/config/i386/i386.c b/gcc/config/i386/i386.c
index 61dbc95c086..233f46c116b 100644
--- a/gcc/config/i386/i386.c
+++ b/gcc/config/i386/i386.c
@@ -18912,6 +18912,12 @@ ix86_check_avx_upper_register (const_rtx exp)
return SSE_REG_P (exp) && GET_MODE_BITSIZE (GET_MODE (exp)) > 128;
}
+/* Check if a 128bit SSE register is referenced inside of EXP. */
+static bool
+ix86_check_sse_register (const_rtx exp)
+{
+ return SSE_REG_P (exp) && GET_MODE_BITSIZE (GET_MODE (exp)) == 128;
+}
/* Return needed mode for entity in optimize_mode_switching pass. */
static int
@@ -18920,6 +18926,7 @@ ix86_avx_u128_mode_needed (rtx_insn *insn)
if (CALL_P (insn))
{
rtx link;
+ bool flag_clean = 0;
/* Needed mode is set to AVX_U128_CLEAN if there are
no 256bit or 512bit modes used in function arguments. */
@@ -18933,10 +18940,14 @@ ix86_avx_u128_mode_needed (rtx_insn *insn)
if (ix86_check_avx_upper_register (arg))
return AVX_U128_DIRTY;
+ if (ix86_check_sse_register (arg))
+ flag_clean = true;
}
}
- return AVX_U128_CLEAN;
+ if(flag_clean)
+ return AVX_U128_CLEAN;
+ return AVX_U128_ANY;
}
/* Require DIRTY mode if a 256bit or 512bit AVX register is referenced.
@@ -19033,6 +19044,15 @@ ix86_check_avx_upper_stores (rtx dest, const_rtx, void
*data)
}
}
+static void
+ix86_check_sse_stores (rtx dest, const_rtx, void *data)
+{
+ if (ix86_check_sse_register (dest))
+ {
+ bool *used = (bool *)data;
+ *used = true;
+ }
+}
/* Calculate mode of upper 128bit AVX registers after the insn. */
static int
@@ -19049,9 +19069,10 @@ ix86_avx_u128_mode_after (int mode, rtx_insn *insn)
if (CALL_P (insn))
{
bool avx_upper_reg_found = false;
+ bool sse_reg_found = false;
note_stores (pat, ix86_check_avx_upper_stores, &avx_upper_reg_found);
-
- return avx_upper_reg_found ? AVX_U128_DIRTY : AVX_U128_CLEAN;
+ note_stores (pat, ix86_check_sse_stores, &sse_reg_found);
+ return avx_upper_reg_found ? AVX_U128_DIRTY : sse_reg_found ?
AVX_U128_CLEAN : AVX_U128_ANY;
}
/* Otherwise, return current mode. Remember that if insn
@@ -19096,7 +19117,7 @@ static int
ix86_avx_u128_mode_entry (void)
{
tree arg;
-
+ bool flag_clean = false;
/* Entry mode is set to AVX_U128_DIRTY if there are
256bit or 512bit modes used in function arguments. */
for (arg = DECL_ARGUMENTS (current_function_decl); arg;
@@ -19106,9 +19127,14 @@ ix86_avx_u128_mode_entry (void)
if (incoming && ix86_check_avx_upper_register (incoming))
return AVX_U128_DIRTY;
+
+ if (incoming && ix86_check_sse_register (incoming))
+ flag_clean = true;
}
- return AVX_U128_CLEAN;
+ if (flag_clean)
+ return AVX_U128_CLEAN;
+ return AVX_U128_ANY;
}
/* Return a mode that ENTITY is assumed to be
@@ -19142,7 +19168,9 @@ ix86_avx_u128_mode_exit (void)
if (reg && ix86_check_avx_upper_register (reg))
return AVX_U128_DIRTY;
- return AVX_U128_CLEAN;
+ if (reg && ix86_check_sse_register (reg))
+ return AVX_U128_CLEAN;
+ return AVX_U128_ANY;
}
/* Return a mode that ENTITY is assumed to be
>From gcc-bugs-return-628157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 03:08:18 2019
Return-Path: <gcc-bugs-return-628157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86898 invoked by alias); 8 Jan 2019 03:08: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 86595 invoked by uid 48); 8 Jan 2019 03:08:14 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Tue, 08 Jan 2019 03:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88717-4-APwE8ihDvZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00966.txt.bz2
Content-length: 611
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to åˆ˜è¢‹é¼ from comment #4)
>
> My thought is AVX_U128_DIRTY would be set when ymm/zmm appeared, and
> AVX_U128_CLEAN for xmm, AVX_U128_ANY for other situations. This also works
> for this case.
>
Your change touches many difference places. Please do
1. For each line of change, find a testcase to verify that it is needed.
2. Bootstrap GCC with --with-arch=native and all languages. Run the complete
GCC testssuites with and without your whole patch.
>From gcc-bugs-return-628158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 03:38:41 2019
Return-Path: <gcc-bugs-return-628158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34515 invoked by alias); 8 Jan 2019 03:38: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 34395 invoked by uid 48); 8 Jan 2019 03:38:37 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82295] Two errors produced with private/protected deleted methods
Date: Tue, 08 Jan 2019 03:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status see_also resolution
Message-ID: <bug-82295-4-DOmW9E2GTe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00967.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82295
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=84447
Resolution|--- |FIXED
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> This was already fixed for GCC 8, by r258003
>
> PR c++/84447 - ICE with deleted inherited ctor with default arg.
>
> * call.c (build_over_call): Handle deleted functions in one
> place.
Oh ok, closing then.
>From gcc-bugs-return-628159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 03:41:34 2019
Return-Path: <gcc-bugs-return-628159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36767 invoked by alias); 8 Jan 2019 03:41: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 36701 invoked by uid 48); 8 Jan 2019 03:41:30 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Tue, 08 Jan 2019 03:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88717-4-qGxjTCiPvq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00968.txt.bz2
Content-length: 706
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
--- Comment #6 from åˆ˜è¢‹é¼ <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #5)
> (In reply to åˆ˜è¢‹é¼ from comment #4)
> >
> > My thought is AVX_U128_DIRTY would be set when ymm/zmm appeared, and
> > AVX_U128_CLEAN for xmm, AVX_U128_ANY for other situations. This also works
> > for this case.
> >
>
> Your change touches many difference places. Please do
>
> 1. For each line of change, find a testcase to verify that it is needed.
> 2. Bootstrap GCC with --with-arch=native and all languages. Run the complete
> GCC testssuites with and without your whole patch.
yes!
>From gcc-bugs-return-628160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 03:44:18 2019
Return-Path: <gcc-bugs-return-628160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38871 invoked by alias); 8 Jan 2019 03:44: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 38831 invoked by uid 48); 8 Jan 2019 03:44:13 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46495] target.h and function.h require tm.h
Date: Tue, 08 Jan 2019 03:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-46495-4-VSdhlhf9SC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46495-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46495-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00969.txt.bz2
Content-length: 633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46495
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jorn Wolfgang Rennecke from comment #0)
> Because of their dependence on CUMULATIVE_ARGS and HARD_REG_SET,
> target.h and function.h include tm.h This needs to be rectified to stop
> the uncontrolled use of target macros.
How?
>From gcc-bugs-return-628161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 03:50:49 2019
Return-Path: <gcc-bugs-return-628161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43149 invoked by alias); 8 Jan 2019 03:50: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 43080 invoked by uid 48); 8 Jan 2019 03:50:44 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/46636] attribute aligned should use bytes (as documented), instead of addressable units (as it currently behaves).
Date: Tue, 08 Jan 2019 03:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-46636-4-HvpMklxUgf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00970.txt.bz2
Content-length: 898
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46636
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
Summary|attribute aligned is |attribute aligned should
|documented as using bytes, |use bytes (as documented),
|uses addressable units |instead of addressable
|instead. |units (as it currently
| |behaves).
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to sandra from comment #5)
> Summarizing the discussion here, I think this is a code bug rather than a
> documentation bug.
ok, retitling then
>From gcc-bugs-return-628162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 03:55:36 2019
Return-Path: <gcc-bugs-return-628162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47885 invoked by alias); 8 Jan 2019 03:55: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 47823 invoked by uid 48); 8 Jan 2019 03:55:31 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/71003] __extension__ silences pedwarn for "\e" in C but not in C++
Date: Tue, 08 Jan 2019 03: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: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-71003-4-TElYy9UCaH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71003-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71003-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00971.txt.bz2
Content-length: 717
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71003
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #3)
> I'm pretty sure that this applies to all pedantic warnings that occur while
> preprocessing:
>
> const int a0 = 0b101010;
> const int a1 = __extension__ 0b101010;
>
> C++ lexes everything at once without parsing __extension__.
>
> Same problem with pragma diagnostics (bug 53431).
>
> Either these warnings are moved from the preprocessor to the FE, that is,
> somehow delayed, or the preprocessor has to learn about __extension__ and
> pragma diagnostics.
I think the second option would make more sense
>From gcc-bugs-return-628163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 05:40:00 2019
Return-Path: <gcc-bugs-return-628163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10113 invoked by alias); 8 Jan 2019 05:40: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 10004 invoked by uid 48); 8 Jan 2019 05:39:53 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9.0 regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 05:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-gb5iA6iCnX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00972.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #4 from Jürgen Reuter <juergen.reuter at desy dot de> ---
The linker before throws this warning:
ld: warning: direct access in function 'operator new[](unsigned long,
std::nothrow_t const&) [clone .cold]' from file
'/usr/local/lib/libstdc++.a(new_opvnt.o)' to global weak symbol 'operator
new[](unsigned long, std::nothrow_t const&)' from file
'/usr/local/lib/libstdc++.a(new_opvnt.o)' means the weak symbol cannot be
overridden at runtime. This was likely caused by different translation units
being compiled with different visibility settings.
This could very well be a change in MACOSX or the static stdc++ library.
>From gcc-bugs-return-628164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 07:45:13 2019
Return-Path: <gcc-bugs-return-628164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112841 invoked by alias); 8 Jan 2019 07:45: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 112642 invoked by uid 48); 8 Jan 2019 07:45:00 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88746] structs: internal compiler error: in output_constructor_regular_field, at varasm.c:5030
Date: Tue, 08 Jan 2019 07:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-88746-4-7mCb2Q2vXV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00973.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88746
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |marxin at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Dup.
*** This bug has been marked as a duplicate of bug 80135 ***
>From gcc-bugs-return-628165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 07:45:21 2019
Return-Path: <gcc-bugs-return-628165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113076 invoked by alias); 8 Jan 2019 07:45: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 112722 invoked by uid 48); 8 Jan 2019 07:45:03 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80135] [7 Regression] ICE in output_constructor_regular_field, at varasm.c:4968
Date: Tue, 08 Jan 2019 07:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80135-4-xguTpdNFca@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80135-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80135-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00974.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80135
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nipatriknilsson at gmail dot com
--- Comment #12 from Martin Liška <marxin at gcc dot gnu.org> ---
*** Bug 88746 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-628166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:19:43 2019
Return-Path: <gcc-bugs-return-628166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122621 invoked by alias); 8 Jan 2019 08:19:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122570 invoked by uid 48); 8 Jan 2019 08:19:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 08:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88750-4-hj3v1JpcBx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00975.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-628167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:20:07 2019
Return-Path: <gcc-bugs-return-628167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123544 invoked by alias); 8 Jan 2019 08:20: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 123400 invoked by uid 48); 8 Jan 2019 08:20:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88749-4-q79LneRYXC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00976.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-628168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:20:17 2019
Return-Path: <gcc-bugs-return-628168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124290 invoked by alias); 8 Jan 2019 08:20:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124205 invoked by uid 48); 8 Jan 2019 08:20:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug jit/88747] [9 Regression] jit testsuite failures: test-sum-of-squares.c.exe (and test-combination)
Date: Tue, 08 Jan 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: jit
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-88747-4-aiWV9mCHim@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00977.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88747
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Target Milestone|--- |9.0
>From gcc-bugs-return-628169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:23:27 2019
Return-Path: <gcc-bugs-return-628169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53567 invoked by alias); 8 Jan 2019 08:23: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 53343 invoked by uid 48); 8 Jan 2019 08:23:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88742] [7/8/9 Regression] Debugger jumps back when stepping over class destructor
Date: Tue, 08 Jan 2019 08:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.2.1
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority cc target_milestone
Message-ID: <bug-88742-4-P3VLZrE6LT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00978.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88742
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Priority|P3 |P2
CC| |aldyh at gcc dot gnu.org
Target Milestone|--- |7.5
>From gcc-bugs-return-628170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:26:36 2019
Return-Path: <gcc-bugs-return-628170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58132 invoked by alias); 8 Jan 2019 08:26:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58091 invoked by uid 48); 8 Jan 2019 08:26:31 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88663] [9 Regression] internal compiler error: in check, at tree-vrp.c:188
Date: Tue, 08 Jan 2019 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88663-4-gTobGRgJrg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00979.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88663
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Just for the record, the patch fixes a miscompilation in icu package on i586:
https://bugzilla.opensuse.org/show_bug.cgi?id=1120781#c1
>From gcc-bugs-return-628171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:47:33 2019
Return-Path: <gcc-bugs-return-628171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106096 invoked by alias); 8 Jan 2019 08:47:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99956 invoked by uid 48); 8 Jan 2019 08:47:29 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 08:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-BKopvUG6y8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00980.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #9 from Romain Geissler <romain.geissler at amadeus dot com> ---
This may be some naive question, but if we are currently trying to build a
libstdc++, shouldn't we assume there is no pre-existing libstdc++ and run the
different checks in the configure script either with the C compiler (if indeed
we never use C++) or with CXXFLAGS like -nodefaultlib ?
>From gcc-bugs-return-628172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:48:59 2019
Return-Path: <gcc-bugs-return-628172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30551 invoked by alias); 8 Jan 2019 08:48:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7182 invoked by uid 48); 8 Jan 2019 08:48:53 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88751] New: Performance regression reload vs lra
Date: Tue, 08 Jan 2019 08:48: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00981.txt.bz2
Content-length: 1914
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88751
Bug ID: 88751
Summary: Performance regression reload vs lra
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: krebbel at gcc dot gnu.org
Target Milestone: ---
There is a big performance drop in OpenJ9 after they have updated from GCC
4.8.5 to GCC 7.3.0.
- The performance regression disappears after compiling the byte code
interpreter loop with -mno-lra.
https://github.com/eclipse/openj9/blob/master/runtime/vm/BytecodeInterpreter.hpp
- The problem comes from the frequently accessed _pc and _sp variables being
assigned to stack slots instead of registers. With GCC 4.8 both variables end
up in hard regs.
- The problem can be seen on x86 as well as on S/390.
- In LRA the root cause of the problem is a threshold which prevents LRA from
running the full register coloring step (ira.c):
/* If there are too many pseudos and/or basic blocks (e.g. 10K
pseudos and 10K blocks or 100K pseudos and 1K blocks), we will
use simplified and faster algorithms in LRA. */
lra_simple_p = (ira_use_lra_p && max_reg_num () >= (1 << 26) /
last_basic_block_for_fn (cfun));
For the huge run() function in the byte code interpreter the numbers are:
(gdb) p max_reg_num()
$6 = 27089
(gdb) p last_basic_block_for_fn(cfun)
$7 = 4799
Forcing GCC to run the full coloring pass makes the _pc and _sp variables to
get hard regs assigned again.
As a quick workaround we might want to turn this threshold into a parameter.
Long-term it would be good if we could either enable the heuristic to estimate
whether full coloring would be beneficial or improve the fallback coloring to
cover such important cases.
>From gcc-bugs-return-628173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 08:58:34 2019
Return-Path: <gcc-bugs-return-628173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72178 invoked by alias); 8 Jan 2019 08:58: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 69502 invoked by uid 55); 8 Jan 2019 08:58:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88554] [9 Regression] Segfault ICE when falling off the end of a reference-returning friend operator
Date: Tue, 08 Jan 2019 08: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88554-4-8UYi5dSusp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00982.txt.bz2
Content-length: 673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88554
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 08:57:58 2019
New Revision: 267672
URL: https://gcc.gnu.org/viewcvs?rev=267672&root=gcc&view=rev
Log:
PR c++/88554
* decl.c (finish_function): For -Wreturn-type don't add a return *this;
fixit hint if current_class_ref is NULL. Use a single if instead of
two nested ones.
* g++.dg/warn/Wreturn-type-11.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/warn/Wreturn-type-11.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:02:13 2019
Return-Path: <gcc-bugs-return-628174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50013 invoked by alias); 8 Jan 2019 09:02: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 39165 invoked by uid 48); 8 Jan 2019 09:02:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 09:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-65wCRewbPj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00983.txt.bz2
Content-length: 1019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Romain Geissler from comment #8)
> So with these explanations, do you think the patch you proposed should land
> in trunk (it worked for me in that specific bootstrap configuration).
Yes the patch is correct regardless and I'll commit it shortly. The explanation
also makes sense of the results too.
(In reply to Romain Geissler from comment #9)
> This may be some naive question, but if we are currently trying to build a
> libstdc++, shouldn't we assume there is no pre-existing libstdc++ and run
> the different checks in the configure script either with the C compiler (if
> indeed we never use C++)
No, because testing whether a C compiler can use those functions tells us
nothing about whether G++ will be able to use them. C libraries expose
different declarations to C and C++ programs.
> or with CXXFLAGS like -nodefaultlib ?
That would also make libc unavailable.
>From gcc-bugs-return-628175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:27:48 2019
Return-Path: <gcc-bugs-return-628175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31498 invoked by alias); 8 Jan 2019 09:27:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31429 invoked by uid 48); 8 Jan 2019 09:27:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88554] [9 Regression] Segfault ICE when falling off the end of a reference-returning friend operator
Date: Tue, 08 Jan 2019 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
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-88554-4-C29RJFHaPP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00984.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88554
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:31:34 2019
Return-Path: <gcc-bugs-return-628176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64003 invoked by alias); 8 Jan 2019 09:31:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63168 invoked by uid 48); 8 Jan 2019 09:31:29 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88648] [7/8/9 Regression] Force unified syntax for inline assembly not functional (-masm-syntax-unified)
Date: Tue, 08 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-88648-4-aIPYnlyzMG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00985.txt.bz2
Content-length: 1092
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88648
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |ktkachov at gcc dot gnu.org
Known to work| |5.4.1
Target Milestone|--- |7.5
Summary|Force unified syntax for |[7/8/9 Regression] Force
|inline assembly not |unified syntax for inline
|functional |assembly not functional
|(-masm-syntax-unified) |(-masm-syntax-unified)
Ever confirmed|0 |1
Known to fail| |6.5.0, 7.4.1, 8.2.1, 9.0
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed on all the branches since GCC 6. GCC 5 did the right thing.
I think r222995 is to blame
>From gcc-bugs-return-628177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:39:50 2019
Return-Path: <gcc-bugs-return-628177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93097 invoked by alias); 8 Jan 2019 09:39:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93047 invoked by uid 48); 8 Jan 2019 09:39:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88751] Performance regression reload vs lra
Date: Tue, 08 Jan 2019 09:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88751-4-Jqvgh3qbLT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00986.txt.bz2
Content-length: 855
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88751
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
last_basic_block_for_fn is odd anyways, shouldn't it be n_basic_blocks_for_fn?
it would make things worse here of course (divide by a possibly lower number).
Likewise max_reg_num () sounds off in a similar way.
But agreed, 1<<26 should be a --param.
Not sure whether n-basic-blocks * n-pseudos is a good thing to limit though.
The comment might want to explain that part X of LRA is quadratic in the
number of blocks / pseudos, etc.
I'll note that your case (130000111) is close to the 1<<26 limit (about
double).
Would be interesting to know the sparseness of regs / BBs for your testcase
at the point of LRA and whether compacting regs (do we ever do that?) might
be a good idea in general. (we do compact BBs regularly)
>From gcc-bugs-return-628178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:47:00 2019
Return-Path: <gcc-bugs-return-628178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120336 invoked by alias); 8 Jan 2019 09:46:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120205 invoked by uid 55); 8 Jan 2019 09:46:52 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Tue, 08 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88677-4-wtFdlzcCPM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00987.txt.bz2
Content-length: 2543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 7 Jan 2019, hubicka at ucw dot cz wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
>
> --- Comment #9 from Jan Hubicka <hubicka at ucw dot cz> ---
> > https://gcc.gnu
> > -> You can't simply remove this flag. You could set it to true conservatively.
> > Or we could stop marking globals that need constructing TREE_READONLY.
>
> I see, I was under impression that we already drop TREE_READONLY for
> them. But it is bit more subtle and thus I was indeed to quick to drop
> streaming here. In:
>
> struct c { int a; c() { a=1; } };
> const c cc;
> const int dd=1;
> extern const c ee;
> int foo() { return ee.a; }
>
> I get:
> const c ee/8 (const c ee) @0x7f68d301ee80
> Type: variable
> Visibility: external public
> References:
> Referring: _Z3foov/5 (read)
> Availability: not-ready
> Varpool flags: read-only
> const int dd/4 (const int dd) @0x7f68d301ec80
> Type: variable definition analyzed
> Visibility: force_output no_reorder
> Aux: @0x7f68d316c450
> References:
> Referring:
> Availability: not-ready
> Varpool flags: initialized read-only const-value-known
> const c cc/3 (const c cc) @0x7f68d301e900
> Type: variable definition analyzed
> Visibility: force_output no_reorder
> Aux: @0x7f68d301ec80
> References:
> Referring: _Z41__static_initialization_and_destruction_0ii/6 (addr)
> Availability: not-ready
> Varpool flags:
>
> So EE is indeed read-only, but CC is not.
> I guess it is because constructor to CC is output locally and we clear
> the flag, while constructor of EE is output externally. What is utility
> of this information? Can we realy in some context that value of EE did
> not change?
>
> It seems to me that it is completely useless info, so I would be in
> favor of dropping TREE_READONLY flag probably at cgraph
> construction time (because I suppose it is relevant to front-end)
I guess the FE needs the info. But yes, dropping TREE_READONLY
for TYPE_NEEDS_CONSTRUCTION decls at some point may make sense.
Generally it would be nice to know (for alias analysis) that
an object is not written to via a pointer. For const globals
with a constructor such writes can only happen inside the global
ctor function(s). Not sure if IPA reference could be of help
here, it is really language stuff. There's also const_cast
and mutable where things get into murky territorry...
>From gcc-bugs-return-628179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:47:40 2019
Return-Path: <gcc-bugs-return-628179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121672 invoked by alias); 8 Jan 2019 09:47:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121622 invoked by uid 55); 8 Jan 2019 09:47:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87898] [8 Regression] ICE in separate_decls_in_region_debug, at tree-parloops.c:961
Date: Tue, 08 Jan 2019 09:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87898-4-MkVcJwGwB5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87898-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87898-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00988.txt.bz2
Content-length: 786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87898
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:47:03 2019
New Revision: 267676
URL: https://gcc.gnu.org/viewcvs?rev=267676&root=gcc&view=rev
Log:
Backported from mainline
2018-11-13 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/87898
* omp-simd-clone.c (ipa_simd_modify_function_body): Remove debug stmts
where the first argument was changed into a non-decl.
* gcc.dg/gomp/pr87898.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr87898.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/omp-simd-clone.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:49:39 2019
Return-Path: <gcc-bugs-return-628180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124287 invoked by alias); 8 Jan 2019 09:49:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124090 invoked by uid 55); 8 Jan 2019 09:49:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88018] [8 Regression] ICE in insert_insn_on_edge at cfgrtl.c:1952 since r255066
Date: Tue, 08 Jan 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88018-4-AxxjTfyoUn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88018-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88018-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00989.txt.bz2
Content-length: 792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88018
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:48:47 2019
New Revision: 267677
URL: https://gcc.gnu.org/viewcvs?rev=267677&root=gcc&view=rev
Log:
Backported from mainline
2018-11-15 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/88018
* cfgrtl.c (fixup_abnormal_edges): Guard moving insns to fallthru edge
on the presence of fallthru edge, rather than if it is a USE or not.
* g++.dg/tsan/pr88018.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/tsan/pr88018.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/cfgrtl.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:50:53 2019
Return-Path: <gcc-bugs-return-628181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130855 invoked by alias); 8 Jan 2019 09:50: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 130729 invoked by uid 55); 8 Jan 2019 09:50:47 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88677] [9 Regression] Divergence in -O2 and -O2 -flto early opts
Date: Tue, 08 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88677-4-ohKpLM0KVf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00990.txt.bz2
Content-length: 862
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88677
--- Comment #11 from Jan Hubicka <hubicka at ucw dot cz> ---
>
> I guess the FE needs the info. But yes, dropping TREE_READONLY
> for TYPE_NEEDS_CONSTRUCTION decls at some point may make sense.
>
> Generally it would be nice to know (for alias analysis) that
> an object is not written to via a pointer. For const globals
> with a constructor such writes can only happen inside the global
> ctor function(s). Not sure if IPA reference could be of help
If I have global ctor of C++ readonly structure, I would expect to be
able to call external function to construct its parts that may call back
to the unit, so it seems to me that we can not track much?
If the ctor is leaf we probably can track down the info, but won't
currently. It is soemthing that ipa-ref could try to do if it was not
lame.
>From gcc-bugs-return-628182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:50:59 2019
Return-Path: <gcc-bugs-return-628182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 752 invoked by alias); 8 Jan 2019 09:50:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130864 invoked by uid 55); 8 Jan 2019 09:50:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87475] [8 Regression] ICE in patch_jump_insn, at cfgrtl.c:1275
Date: Tue, 08 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87475-4-WwTOf5ohxP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00991.txt.bz2
Content-length: 804
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87475
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:50:21 2019
New Revision: 267678
URL: https://gcc.gnu.org/viewcvs?rev=267678&root=gcc&view=rev
Log:
Backported from mainline
2018-11-16 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/87475
* cfgrtl.c (patch_jump_insn): Allow redirection failure for
CROSSING_JUMP_P insns.
(cfg_layout_redirect_edge_and_branch): Don't ICE if ret is NULL.
* g++.dg/opt/pr87475.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/opt/pr87475.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/cfgrtl.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:52:08 2019
Return-Path: <gcc-bugs-return-628183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2481 invoked by alias); 8 Jan 2019 09:52:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2383 invoked by uid 55); 8 Jan 2019 09:52:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/87039] [8 Regression] DW_OP_fbreg used without a frame base on a C++ code w/ -fopenmp
Date: Tue, 08 Jan 2019 09:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87039-4-YrYXqNp8Oi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87039-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87039-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00992.txt.bz2
Content-length: 1750
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87039
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:51:19 2019
New Revision: 267679
URL: https://gcc.gnu.org/viewcvs?rev=267679&root=gcc&view=rev
Log:
Backported from mainline
2018-11-19 Jakub Jelinek <jakub@redhat.com>
PR debug/87039
* omp-expand.c: Don't include debug.h.
(adjust_context_and_scope): Add REGION argument. Find DECL_CONTEXT
from innermost outer parallel, task, or target that has a
child_fn set, or, if there is no such outer region, use
current_function_decl. Do the DECL_CONTEXT adjustment regardless of
whether a suitable BLOCK is found or not.
(expand_parallel_call): Don't call adjust_context_and_scope here.
(grid_expand_target_grid_body): Revert 2017-01-25 changes.
(expand_omp_taskreg, expand_omp_target): Likewise. Call
adjust_context_and_scope.
* dwarf2out.c (dwarf2out_early_global_decl): For
decl_function_context recurse instead of calling dwarf2out_decl.
* g++.dg/gomp/pr78363-4.C: New test.
* g++.dg/gomp/pr78363-5.C: New test.
* g++.dg/gomp/pr78363-6.C: New test.
* g++.dg/gomp/pr78363-7.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/gomp/pr78363-4.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/gomp/pr78363-5.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/gomp/pr78363-6.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/gomp/pr78363-7.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/dwarf2out.c
branches/gcc-8-branch/gcc/omp-expand.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:53:26 2019
Return-Path: <gcc-bugs-return-628184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4637 invoked by alias); 8 Jan 2019 09:53: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 4555 invoked by uid 55); 8 Jan 2019 09:53:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60994] gcc does not recognize hidden/shadowed enumeration as valid nested-name-specifier
Date: Tue, 08 Jan 2019 09:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60994-4-MdnRYUmRx8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00993.txt.bz2
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60994
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:52:44 2019
New Revision: 267681
URL: https://gcc.gnu.org/viewcvs?rev=267681&root=gcc&view=rev
Log:
Backported from mainline
2018-11-19 Jakub Jelinek <jakub@redhat.com>
PR c++/60994
* g++.dg/lookup/pr60994.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/lookup/pr60994.C
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:54:13 2019
Return-Path: <gcc-bugs-return-628185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6435 invoked by alias); 8 Jan 2019 09:54:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6049 invoked by uid 55); 8 Jan 2019 09:54:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88071] [8 Regression] ICE: verify_gimple failed (error: dead STMT in EH table)
Date: Tue, 08 Jan 2019 09:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88071-4-ReS4rTDdjJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88071-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00994.txt.bz2
Content-length: 934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88071
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:53:35 2019
New Revision: 267682
URL: https://gcc.gnu.org/viewcvs?rev=267682&root=gcc&view=rev
Log:
Backported from mainline
2018-11-19 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/88071
* tree-vect-loop.c (vectorize_fold_left_reduction): Pass true instead
of false as last argument to gsi_remove.
* tree-vect-stmts.c (vect_finish_replace_stmt): Pass true instead of
false as last argument to gsi_replace.
* gcc.dg/pr88071.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pr88071.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/tree-vect-loop.c
branches/gcc-8-branch/gcc/tree-vect-stmts.c
>From gcc-bugs-return-628186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:55:16 2019
Return-Path: <gcc-bugs-return-628186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31000 invoked by alias); 8 Jan 2019 09:55: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 24123 invoked by uid 55); 8 Jan 2019 09:55:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87895] [7/8 Regression] ICE in purge_dead_edges, at cfgrtl.c:3246
Date: Tue, 08 Jan 2019 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-invalid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87895-4-iCynt8jbgy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87895-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87895-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00995.txt.bz2
Content-length: 1214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87895
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:54:36 2019
New Revision: 267684
URL: https://gcc.gnu.org/viewcvs?rev=267684&root=gcc&view=rev
Log:
Backported from mainline
2018-11-20 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/87895
* omp-simd-clone.c (ipa_simd_modify_function_body): When removing
or replacing GIMPLE_RETURN, set EDGE_FALLTHRU on the edge to EXIT.
(simd_clone_adjust): Don't set EDGE_FALLTHRU here. In a loop that
redirects edges to EXIT to edges to incr_bb, iterate while EXIT
has any preds and always use EDGE_PRED (, 0).
* gcc.dg/gomp/pr87895-1.c: New test.
* gcc.dg/gomp/pr87895-2.c: New test.
* gcc.dg/gomp/pr87895-3.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr87895-1.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr87895-2.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr87895-3.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/omp-simd-clone.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:56:04 2019
Return-Path: <gcc-bugs-return-628187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86694 invoked by alias); 8 Jan 2019 09: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 79617 invoked by uid 55); 8 Jan 2019 09:55:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88122] [9 Regression] g++ ICE: internal compiler error: Segmentation fault
Date: Tue, 08 Jan 2019 09:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88122-4-B5s3skjPGB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88122-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88122-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00996.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88122
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:55:26 2019
New Revision: 267685
URL: https://gcc.gnu.org/viewcvs?rev=267685&root=gcc&view=rev
Log:
Backported from mainline
2018-11-21 Jakub Jelinek <jakub@redhat.com>
PR c++/88122
* method.c (maybe_explain_implicit_delete): If
FUNCTION_FIRST_USER_PARMTYPE (decl) is NULL, set const_p to false
instead of ICEing.
* g++.dg/cpp0x/implicit15.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/implicit15.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/method.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:57:15 2019
Return-Path: <gcc-bugs-return-628188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103630 invoked by alias); 8 Jan 2019 09:57:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103039 invoked by uid 55); 8 Jan 2019 09:57:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85644] [8 Regression] -fstack-protector generates invalid read to %fs:0x0 on mac
Date: Tue, 08 Jan 2019 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85644-4-5VtHBqCvQb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00997.txt.bz2
Content-length: 909
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85644
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:56:36 2019
New Revision: 267686
URL: https://gcc.gnu.org/viewcvs?rev=267686&root=gcc&view=rev
Log:
Backported from mainline
2018-11-22 Jakub Jelinek <jakub@redhat.com>
PR target/85644
PR target/86832
* config/i386/i386.c (ix86_option_override_internal): Default
ix86_stack_protector_guard to SSP_TLS only if TARGET_THREAD_SSP_OFFSET
is defined.
* config/i386/i386.md (stack_protect_set, stack_protect_set_<mode>,
stack_protect_test, stack_protect_test_<mode>): Use empty condition
instead of TARGET_SSP_TLS_GUARD.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/i386.c
branches/gcc-8-branch/gcc/config/i386/i386.md
>From gcc-bugs-return-628189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:57:16 2019
Return-Path: <gcc-bugs-return-628189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103757 invoked by alias); 8 Jan 2019 09:57:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103139 invoked by uid 55); 8 Jan 2019 09:57:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86832] [8 Regression] GCC v8.2.0 tries to use native TLS with -fstack-protector-strong on Windows (mingw-w64)
Date: Tue, 08 Jan 2019 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86832-4-OkglohtVzr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00998.txt.bz2
Content-length: 910
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86832
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:56:36 2019
New Revision: 267686
URL: https://gcc.gnu.org/viewcvs?rev=267686&root=gcc&view=rev
Log:
Backported from mainline
2018-11-22 Jakub Jelinek <jakub@redhat.com>
PR target/85644
PR target/86832
* config/i386/i386.c (ix86_option_override_internal): Default
ix86_stack_protector_guard to SSP_TLS only if TARGET_THREAD_SSP_OFFSET
is defined.
* config/i386/i386.md (stack_protect_set, stack_protect_set_<mode>,
stack_protect_test, stack_protect_test_<mode>): Use empty condition
instead of TARGET_SSP_TLS_GUARD.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/i386.c
branches/gcc-8-branch/gcc/config/i386/i386.md
>From gcc-bugs-return-628190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:57:49 2019
Return-Path: <gcc-bugs-return-628190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105707 invoked by alias); 8 Jan 2019 09:57:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105632 invoked by uid 55); 8 Jan 2019 09:57:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85794] [8/9 Regression][AArch64] ICE in expand_vector_condition in GIMPLE pass: veclower2
Date: Tue, 08 Jan 2019 09:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85794-4-mEG091nANC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg00999.txt.bz2
Content-length: 561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85794
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:57:10 2019
New Revision: 267687
URL: https://gcc.gnu.org/viewcvs?rev=267687&root=gcc&view=rev
Log:
Backported from mainline
2018-11-22 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/85794
* gcc.dg/vect/O3-pr85794.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/vect/O3-pr85794.c
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:58:40 2019
Return-Path: <gcc-bugs-return-628191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107725 invoked by alias); 8 Jan 2019 09:58: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 107611 invoked by uid 55); 8 Jan 2019 09:58:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86900] [8 Regression] -gdwarf-5 -O2 -ffunction-sections = assembler error
Date: Tue, 08 Jan 2019 09:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86900-4-HMi7umMhRP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86900-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01000.txt.bz2
Content-length: 829
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86900
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:58:04 2019
New Revision: 267688
URL: https://gcc.gnu.org/viewcvs?rev=267688&root=gcc&view=rev
Log:
Backported from mainline
2018-11-26 Jakub Jelinek <jakub@redhat.com>
PR c++/86900
* dwarf2out.c (secname_for_decl): For functions with
DECL_SECTION_NAME if in_cold_section_p, try to return
current_function_section's name if it is a named section.
* g++.dg/debug/dwarf2/pr86900.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/debug/dwarf2/pr86900.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/dwarf2out.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 09:59:27 2019
Return-Path: <gcc-bugs-return-628192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109103 invoked by alias); 8 Jan 2019 09:59: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 108992 invoked by uid 55); 8 Jan 2019 09:59:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88181] [7/8 Regression] ICE: verify_type failed (error: type variant differs by TYPE_PACKED)
Date: Tue, 08 Jan 2019 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88181-4-z1c1FtzPYV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88181-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88181-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01001.txt.bz2
Content-length: 723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88181
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:58:48 2019
New Revision: 267689
URL: https://gcc.gnu.org/viewcvs?rev=267689&root=gcc&view=rev
Log:
Backported from mainline
2018-11-27 Jakub Jelinek <jakub@redhat.com>
PR c++/88181
* class.c (fixup_attribute_variants): Also propagate TYPE_PACKED
to variants.
* g++.dg/debug/pr88181.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/debug/pr88181.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/class.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:01:38 2019
Return-Path: <gcc-bugs-return-628194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113333 invoked by alias); 8 Jan 2019 10:01:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113250 invoked by uid 55); 8 Jan 2019 10:01:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87539] [8 Regression] internal compiler error when compiling project with Os optimization flag
Date: Tue, 08 Jan 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: needs-reduction
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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87539-4-7FM7m1pUMF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87539-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87539-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01003.txt.bz2
Content-length: 543
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87539
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:00:42 2019
New Revision: 267691
URL: https://gcc.gnu.org/viewcvs?rev=267691&root=gcc&view=rev
Log:
Backported from mainline
2018-11-29 Jakub Jelinek <jakub@redhat.com>
PR c++/87539
* g++.dg/cpp0x/pr87539.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/pr87539.C
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:01:07 2019
Return-Path: <gcc-bugs-return-628193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111934 invoked by alias); 8 Jan 2019 10:01:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111532 invoked by uid 55); 8 Jan 2019 10:00:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88215] UBSAN: Internal compiler error with attribute(unused)
Date: Tue, 08 Jan 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.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-88215-4-3BTnXr1dF3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88215-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01002.txt.bz2
Content-length: 885
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88215
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 09:59:34 2019
New Revision: 267690
URL: https://gcc.gnu.org/viewcvs?rev=267690&root=gcc&view=rev
Log:
Backported from mainline
2018-11-28 Jakub Jelinek <jakub@redhat.com>
PR c++/88215
* c-ubsan.c: Include langhooks.h.
(ubsan_instrument_division): Change gcc_assert that main variants
of op0 and op1 types are equal to gcc_checking_assert that the
main variants are compatible types.
* c-c++-common/ubsan/pr88215.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/c-c++-common/ubsan/pr88215.c
Modified:
branches/gcc-8-branch/gcc/c-family/ChangeLog
branches/gcc-8-branch/gcc/c-family/c-ubsan.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:04:16 2019
Return-Path: <gcc-bugs-return-628195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118578 invoked by alias); 8 Jan 2019 10:04: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 118343 invoked by uid 55); 8 Jan 2019 10:04:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88234] UBsan and runtime error: signed integer overflow using unsigned vector
Date: Tue, 08 Jan 2019 10:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88234-4-A4gEdhfh7M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88234-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88234-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01004.txt.bz2
Content-length: 876
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88234
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:03:34 2019
New Revision: 267692
URL: https://gcc.gnu.org/viewcvs?rev=267692&root=gcc&view=rev
Log:
Backported from mainline
2018-11-29 Jakub Jelinek <jakub@redhat.com>
PR target/88234
* config/rs6000/rs6000.c (rs6000_gimple_fold_builtin): For
vec_add and vec_sub builtins, perform PLUS_EXPR or MINUS_EXPR
in unsigned_type_for instead of vector integral type where overflow
doesn't wrap.
* gcc.dg/ubsan/pr88234.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/ubsan/pr88234.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/rs6000/rs6000.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:05:30 2019
Return-Path: <gcc-bugs-return-628196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122283 invoked by alias); 8 Jan 2019 10:05:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121431 invoked by uid 55); 8 Jan 2019 10:05:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/85550] [7/8/9 Regression] -fdebug-types-section broken with DW_OP_addr in DW_AT_location
Date: Tue, 08 Jan 2019 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85550-4-IDHlz6lzgu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85550-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85550-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01005.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85550
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:04:51 2019
New Revision: 267693
URL: https://gcc.gnu.org/viewcvs?rev=267693&root=gcc&view=rev
Log:
Backported from mainline
2018-11-30 Jakub Jelinek <jakub@redhat.com>
PR debug/85550
* g++.dg/debug/dwarf2/pr85550.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/debug/dwarf2/pr85550.C
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:05:58 2019
Return-Path: <gcc-bugs-return-628198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3565 invoked by alias); 8 Jan 2019 10:05: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 1268 invoked by uid 55); 8 Jan 2019 10:05:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/71109] gcc ICE at -O3 on valid code on x86_64-linux-gnu in "maybe_record_trace_start"
Date: Tue, 08 Jan 2019 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-71109-4-wmbYIhGzC8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01007.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71109
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:05:20 2019
New Revision: 267694
URL: https://gcc.gnu.org/viewcvs?rev=267694&root=gcc&view=rev
Log:
Backported from mainline
2018-12-03 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/71109
* gcc.c-torture/compile/pr71109.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.c-torture/compile/pr71109.c
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:05:43 2019
Return-Path: <gcc-bugs-return-628197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128006 invoked by alias); 8 Jan 2019 10:05:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125150 invoked by uid 48); 8 Jan 2019 10:05:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82295] Two errors produced with private/protected deleted methods
Date: Tue, 08 Jan 2019 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-82295-4-x427KWhjwy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82295-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01006.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82295
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The bug isn't the same though, so we should add a testcase for this one to
ensure it doesn't regress.
>From gcc-bugs-return-628199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:07:10 2019
Return-Path: <gcc-bugs-return-628199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6618 invoked by alias); 8 Jan 2019 10:07:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6504 invoked by uid 55); 8 Jan 2019 10:07:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88103] [7/8/9 Regression] Wrong value category when conditional expression result is used as object expression
Date: Tue, 08 Jan 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88103-4-PTmKvo3YDl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01008.txt.bz2
Content-length: 768
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88103
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:06:33 2019
New Revision: 267695
URL: https://gcc.gnu.org/viewcvs?rev=267695&root=gcc&view=rev
Log:
Backported from mainline
2018-12-04 Jakub Jelinek <jakub@redhat.com>
PR c++/88103
* typeck.c (build_class_member_access_expr): If unary_complex_lvalue
turned xvalue_p into non-xvalue_p, call move on it.
* g++.dg/cpp0x/rv-cond3.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/rv-cond3.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/typeck.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:09:42 2019
Return-Path: <gcc-bugs-return-628200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9554 invoked by alias); 8 Jan 2019 10:09: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 9429 invoked by uid 55); 8 Jan 2019 10:09:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87320] [8/9 Regression] Last iteration of vectorized loop not executed when peeling for gaps
Date: Tue, 08 Jan 2019 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
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-87320-4-apPagRFWPp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87320-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87320-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01009.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87320
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:09:05 2019
New Revision: 267696
URL: https://gcc.gnu.org/viewcvs?rev=267696&root=gcc&view=rev
Log:
Backported from mainline
2018-12-04 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/87320
* gcc.dg/pr87320.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pr87320.c
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:11:14 2019
Return-Path: <gcc-bugs-return-628201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12184 invoked by alias); 8 Jan 2019 10: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 12032 invoked by uid 55); 8 Jan 2019 10:11:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87360] [8 Regression] ICE in remove_redundant_iv_tests at gcc/tree-ssa-loop-ivcanon.c:571 since r255467
Date: Tue, 08 Jan 2019 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87360-4-kLg1n56amw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87360-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87360-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01010.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87360
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:10:34 2019
New Revision: 267697
URL: https://gcc.gnu.org/viewcvs?rev=267697&root=gcc&view=rev
Log:
Backported from mainline
2018-12-05 Jakub Jelinek <jakub@redhat.com>
PR tree-optimization/87360
* gimple-loop-jam.c (tree_loop_unroll_and_jam): On failure to analyze
data dependencies, don't return false, just continue.
* g++.dg/opt/pr87360.C: New test.
* gfortran.dg/pr87360.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/opt/pr87360.C
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr87360.f90
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/gimple-loop-jam.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:11:59 2019
Return-Path: <gcc-bugs-return-628202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13602 invoked by alias); 8 Jan 2019 10:11:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13514 invoked by uid 48); 8 Jan 2019 10:11:55 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88739] [7,8,9 Regression ] Big-endian union bug
Date: Tue, 08 Jan 2019 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-vplKjtP2EB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01011.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #5 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Also on Arm and probably other big-endian machines as well.
>From gcc-bugs-return-628203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:12:02 2019
Return-Path: <gcc-bugs-return-628203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14040 invoked by alias); 8 Jan 2019 10:12: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 13569 invoked by uid 48); 8 Jan 2019 10:11:57 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88752] New: ICE in enclosing_instantiation_of, at cp/pt.c:13328
Date: Tue, 08 Jan 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01012.txt.bz2
Content-length: 5815
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
Bug ID: 88752
Summary: ICE in enclosing_instantiation_of, at cp/pt.c:13328
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Created attachment 45375
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45375&action=edit
not-reduced test case
Compile attached test case with `-std=gnu++17 -march=skylake -mrtm ~/ice.cpp`.
/home/mkretz/src/gcc/libstdc++-v3/testsuite/experimental/simd/tests/trigonometric.h:17:895:
internal compiler error: in enclosing_instantiation_of, at cp/pt.c:13328
17 | MAKE_TESTER(acos), MAKE_TESTER(tan), MAKE_TESTER(acosh),
|
^
0x624ca1 enclosing_instantiation_of
/home/mkretz/src/gcc/gcc/cp/pt.c:13327
0x986934 tsubst_copy
/home/mkretz/src/gcc/gcc/cp/pt.c:15494
0x9a0023 tsubst_copy
/home/mkretz/src/gcc/gcc/cp/pt.c:15377
0x9a0023 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:19257
0x9a030c tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:18169
0x9a0976 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:18638
0x98ef5f tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:17756
0x992542 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:15346
0x992542 tsubst_init
/home/mkretz/src/gcc/gcc/cp/pt.c:15350
0x9910c4 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:16997
0x98e34d tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:16862
0x98bb21 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:17163
0x98e34d tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:16862
0x98bb21 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:17163
0x9a415e tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:16847
0x9a415e tsubst_lambda_expr(tree_node*, tree_node*, int, tree_node*)
/home/mkretz/src/gcc/gcc/cp/pt.c:18023
0x9a2d53 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:19344
0x9a0976 tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:18638
0x9a07bb tsubst_copy_and_build(tree_node*, tree_node*, int, tree_node*, bool,
bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:18346
0x98ef5f tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
/home/mkretz/src/gcc/gcc/cp/pt.c:17756
>From gcc-bugs-return-628204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:12:13 2019
Return-Path: <gcc-bugs-return-628204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15113 invoked by alias); 8 Jan 2019 10:12:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14590 invoked by uid 55); 8 Jan 2019 10:12:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87598] [8 Regression] Rejects "%a0" with constant
Date: Tue, 08 Jan 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87598-4-epkb7mEHmL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01013.txt.bz2
Content-length: 841
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87598
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:11:29 2019
New Revision: 267698
URL: https://gcc.gnu.org/viewcvs?rev=267698&root=gcc&view=rev
Log:
Backported from mainline
2018-12-06 Jakub Jelinek <jakub@redhat.com>
PR target/87598
* config/aarch64/aarch64.c (aarch64_print_address_internal): Don't
call output_operand_lossage on VOIDmode CONST_INTs. After
output_operand_lossage do return false.
* gcc.target/aarch64/asm-5.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/aarch64/asm-5.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/aarch64/aarch64.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:13:00 2019
Return-Path: <gcc-bugs-return-628205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16637 invoked by alias); 8 Jan 2019 10:13:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16504 invoked by uid 55); 8 Jan 2019 10:12:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87506] [7/8 Regression] ICE with inherited constexpr constructor with const argument
Date: Tue, 08 Jan 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87506-4-xJOHLEz2PH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87506-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87506-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01014.txt.bz2
Content-length: 715
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87506
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:12:22 2019
New Revision: 267699
URL: https://gcc.gnu.org/viewcvs?rev=267699&root=gcc&view=rev
Log:
Backported from mainline
2018-12-07 Jakub Jelinek <jakub@redhat.com>
PR c++/87506
* constexpr.c (adjust_temp_type): Handle EMPTY_CLASS_EXPR.
* g++.dg/cpp0x/constexpr-87506.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/constexpr-87506.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/constexpr.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:13:44 2019
Return-Path: <gcc-bugs-return-628206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18301 invoked by alias); 8 Jan 2019 10:13:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18245 invoked by uid 55); 8 Jan 2019 10:13:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88377] ICE in gfc_omp_clause_copy_ctor, at fortran/trans-openmp.c:614
Date: Tue, 08 Jan 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88377-4-9CDlA4oHgD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88377-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88377-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01015.txt.bz2
Content-length: 951
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88377
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:13:07 2019
New Revision: 267700
URL: https://gcc.gnu.org/viewcvs?rev=267700&root=gcc&view=rev
Log:
Backported from mainline
2018-12-07 Jakub Jelinek <jakub@redhat.com>
PR fortran/88377
* trans-openmp.c (gfc_omp_clause_default_ctor,
gfc_omp_clause_copy_ctor, gfc_omp_clause_assign_op,
gfc_omp_clause_linear_ctor, gfc_omp_clause_dtor): Only consider
GFC_DECL_GET_SCALAR_ALLOCATABLE vars as scalar allocatables if they
have pointer type.
* gfortran.dg/gomp/pr88377.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/gomp/pr88377.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-openmp.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:14:57 2019
Return-Path: <gcc-bugs-return-628207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22433 invoked by alias); 8 Jan 2019 10:14: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 22345 invoked by uid 55); 8 Jan 2019 10:14:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85593] [7/8 Regression] GCC on ARM allocates R3 for local variable when calling naked function with O2 optimizations enabled
Date: Tue, 08 Jan 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.4.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85593-4-CMakU5HHw0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01016.txt.bz2
Content-length: 757
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85593
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:14:12 2019
New Revision: 267701
URL: https://gcc.gnu.org/viewcvs?rev=267701&root=gcc&view=rev
Log:
Backported from mainline
2018-12-07 Jakub Jelinek <jakub@redhat.com>
PR target/85593
* final.c (rest_of_handle_final): Don't call collect_fn_hard_reg_usage
for functions with naked attribute.
* gcc.target/i386/pr85593.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/pr85593.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/final.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:16:50 2019
Return-Path: <gcc-bugs-return-628208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26897 invoked by alias); 8 Jan 2019 10:16:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26739 invoked by uid 55); 8 Jan 2019 10:16:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86669] [7/8 regression] Complete object constructor clone omits length for a c++11 braced initialiser
Date: Tue, 08 Jan 2019 10:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86669-4-4pExWafKfh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86669-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86669-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01017.txt.bz2
Content-length: 961
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86669
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:16:00 2019
New Revision: 267702
URL: https://gcc.gnu.org/viewcvs?rev=267702&root=gcc&view=rev
Log:
Backported from mainline
2018-12-07 Jakub Jelinek <jakub@redhat.com>
PR c++/86669
* call.c (make_temporary_var_for_ref_to_temp): Call pushdecl even for
automatic vars.
* g++.dg/cpp0x/initlist105.C: New test.
* g++.dg/cpp0x/initlist106.C: New test.
* g++.dg/other/pr86669.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/initlist105.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/initlist106.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/other/pr86669.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/call.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:18:11 2019
Return-Path: <gcc-bugs-return-628209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28979 invoked by alias); 8 Jan 2019 10:18: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 28789 invoked by uid 55); 8 Jan 2019 10:18:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88426] [8 Regression] Compiler crash if use special code with command line switch -fsanitize=float-cast-overflow
Date: Tue, 08 Jan 2019 10:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.1
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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88426-4-3zqXoufi8o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01018.txt.bz2
Content-length: 789
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88426
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:17:32 2019
New Revision: 267703
URL: https://gcc.gnu.org/viewcvs?rev=267703&root=gcc&view=rev
Log:
Backported from mainline
2018-12-11 Jakub Jelinek <jakub@redhat.com>
PR sanitizer/88426
* c-convert.c (convert): Call c_fully_fold before calling
ubsan_instrument_float_cast.
* c-c++-common/ubsan/float-cast-overflow-11.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/c-c++-common/ubsan/float-cast-overflow-11.c
Modified:
branches/gcc-8-branch/gcc/c/ChangeLog
branches/gcc-8-branch/gcc/c/c-convert.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:19:15 2019
Return-Path: <gcc-bugs-return-628210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31384 invoked by alias); 8 Jan 2019 10:19:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31186 invoked by uid 55); 8 Jan 2019 10:19:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88463] Rejects conforming source, OpenMP Parallel region Default(None) reference to module parameter array, separate source
Date: Tue, 08 Jan 2019 10:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: openmp, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88463-4-dcBWkAGjij@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88463-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88463-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01019.txt.bz2
Content-length: 953
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88463
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:18:34 2019
New Revision: 267704
URL: https://gcc.gnu.org/viewcvs?rev=267704&root=gcc&view=rev
Log:
Backported from mainline
2018-12-12 Jakub Jelinek <jakub@redhat.com>
PR fortran/88463
* trans-openmp.c (gfc_omp_predetermined_sharing): Handle TREE_READONLY
VAR_DECLs with DECL_EXTERNAL like those with TREE_STATIC.
* testsuite/libgomp.fortran/pr88463-1.f90: New test.
* testsuite/libgomp.fortran/pr88463-2.f90: New test.
Added:
branches/gcc-8-branch/libgomp/testsuite/libgomp.fortran/pr88463-1.f90
branches/gcc-8-branch/libgomp/testsuite/libgomp.fortran/pr88463-2.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-openmp.c
branches/gcc-8-branch/libgomp/ChangeLog
>From gcc-bugs-return-628211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:19:31 2019
Return-Path: <gcc-bugs-return-628211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32494 invoked by alias); 8 Jan 2019 10:19:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32177 invoked by uid 55); 8 Jan 2019 10:19:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 10:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-4YUCqzMbip@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01020.txt.bz2
Content-length: 600
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jan 8 10:18:54 2019
New Revision: 267705
URL: https://gcc.gnu.org/viewcvs?rev=267705&root=gcc&view=rev
Log:
PR libstdc++/88749 fix build failure in src/filesystem/ops.cc
PR libstdc++/88749
* src/filesystem/ops.cc (last_write_time): Fix preprocessor condition
to match the one that controls whether utimbuf and utime are declared.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/filesystem/ops.cc
>From gcc-bugs-return-628214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:20:57 2019
Return-Path: <gcc-bugs-return-628214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36948 invoked by alias); 8 Jan 2019 10:20:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36204 invoked by uid 55); 8 Jan 2019 10:20:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88470] [7/8 Regression] ICE in maybe_record_trace_start, at dwarf2cfi.c:2354
Date: Tue, 08 Jan 2019 10:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88470-4-7uYUClROLr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88470-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88470-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01023.txt.bz2
Content-length: 820
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88470
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:20:17 2019
New Revision: 267707
URL: https://gcc.gnu.org/viewcvs?rev=267707&root=gcc&view=rev
Log:
Backported from mainline
2018-12-13 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/88470
* cfgcleanup.c (outgoing_edges_match): If the function is
shrink-wrapped and bb1 ends with a JUMP_INSN with a single fake
edge to EXIT, return false.
* gcc.target/i386/pr88470.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/pr88470.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/cfgcleanup.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:20:13 2019
Return-Path: <gcc-bugs-return-628213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34474 invoked by alias); 8 Jan 2019 10:20: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 33927 invoked by uid 48); 8 Jan 2019 10:20:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 10:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88749-4-QIHxfUFe5z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01022.txt.bz2
Content-length: 454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed now - thanks for the report.
>From gcc-bugs-return-628212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:20:06 2019
Return-Path: <gcc-bugs-return-628212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33718 invoked by alias); 8 Jan 2019 10:20:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33523 invoked by uid 55); 8 Jan 2019 10:20:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88416] [8 Regression] ICE in in df_uses_record, at df-scan.c:3013
Date: Tue, 08 Jan 2019 10:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88416-4-tSj3ARrsMQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88416-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88416-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01021.txt.bz2
Content-length: 751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88416
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:19:28 2019
New Revision: 267706
URL: https://gcc.gnu.org/viewcvs?rev=267706&root=gcc&view=rev
Log:
Backported from mainline
2018-12-13 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/88416
* valtrack.c (cleanup_auto_inc_dec): Handle pre/post-inc/dec/modify
even if !AUTO_INC_DEC.
* gcc.target/i386/pr88416.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/pr88416.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/valtrack.c
>From gcc-bugs-return-628216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:21:36 2019
Return-Path: <gcc-bugs-return-628216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42874 invoked by alias); 8 Jan 2019 10:21:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42598 invoked by uid 55); 8 Jan 2019 10:21:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87436] [7/8 Regression] G++ produces >300MB .rodata section to initialize struct with big array
Date: Tue, 08 Jan 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87436-4-EbyUR3ucog@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01025.txt.bz2
Content-length: 657
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87436
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:20:57 2019
New Revision: 267708
URL: https://gcc.gnu.org/viewcvs?rev=267708&root=gcc&view=rev
Log:
Backported from mainline
2018-12-14 Jakub Jelinek <jakub@redhat.com>
PR c++/82294
PR c++/87436
* init.c (build_vec_init): Change num_initialized_elts type from int
to HOST_WIDE_INT. Build a RANGE_EXPR if e needs to be repeated more
than once.
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/init.c
>From gcc-bugs-return-628215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:21:36 2019
Return-Path: <gcc-bugs-return-628215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42846 invoked by alias); 8 Jan 2019 10:21: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 42442 invoked by uid 55); 8 Jan 2019 10:21:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82294] Array of objects with constexpr constructors initialized from space-inefficient memory image
Date: Tue, 08 Jan 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82294-4-tvRt89W7Th@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82294-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01024.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82294
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:20:57 2019
New Revision: 267708
URL: https://gcc.gnu.org/viewcvs?rev=267708&root=gcc&view=rev
Log:
Backported from mainline
2018-12-14 Jakub Jelinek <jakub@redhat.com>
PR c++/82294
PR c++/87436
* init.c (build_vec_init): Change num_initialized_elts type from int
to HOST_WIDE_INT. Build a RANGE_EXPR if e needs to be repeated more
than once.
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/init.c
>From gcc-bugs-return-628218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:22:38 2019
Return-Path: <gcc-bugs-return-628218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48065 invoked by alias); 8 Jan 2019 10:22: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 47616 invoked by uid 55); 8 Jan 2019 10:22:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87436] [7/8 Regression] G++ produces >300MB .rodata section to initialize struct with big array
Date: Tue, 08 Jan 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87436-4-T2fcAzxIwC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01027.txt.bz2
Content-length: 1566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87436
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:22:00 2019
New Revision: 267709
URL: https://gcc.gnu.org/viewcvs?rev=267709&root=gcc&view=rev
Log:
Backported from mainline
2018-12-14 Jakub Jelinek <jakub@redhat.com>
PR c++/82294
PR c++/87436
* expr.h (categorize_ctor_elements): Add p_unique_nz_elts argument.
* expr.c (categorize_ctor_elements_1): Likewise. Compute it like
p_nz_elts, except don't multiply it by mult. Adjust recursive call.
Fix up COMPLEX_CST handling.
(categorize_ctor_elements): Add p_unique_nz_elts argument, initialize
it and pass it through to categorize_ctor_elements_1.
(mostly_zeros_p, all_zeros_p): Adjust categorize_ctor_elements callers.
* gimplify.c (gimplify_init_constructor): Likewise. Don't force
ctor into readonly data section if num_unique_nonzero_elements is
smaller or equal to 1/8 of num_nonzero_elements and size is >= 64
bytes.
* g++.dg/tree-ssa/pr82294.C: New test.
* g++.dg/tree-ssa/pr87436.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/tree-ssa/pr82294.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/tree-ssa/pr87436.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/expr.c
branches/gcc-8-branch/gcc/expr.h
branches/gcc-8-branch/gcc/gimplify.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:22:38 2019
Return-Path: <gcc-bugs-return-628217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47939 invoked by alias); 8 Jan 2019 10:22: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 47599 invoked by uid 55); 8 Jan 2019 10:22:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82294] Array of objects with constexpr constructors initialized from space-inefficient memory image
Date: Tue, 08 Jan 2019 10: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: 7.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82294-4-4gERhQcbLj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82294-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01026.txt.bz2
Content-length: 1565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82294
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:22:00 2019
New Revision: 267709
URL: https://gcc.gnu.org/viewcvs?rev=267709&root=gcc&view=rev
Log:
Backported from mainline
2018-12-14 Jakub Jelinek <jakub@redhat.com>
PR c++/82294
PR c++/87436
* expr.h (categorize_ctor_elements): Add p_unique_nz_elts argument.
* expr.c (categorize_ctor_elements_1): Likewise. Compute it like
p_nz_elts, except don't multiply it by mult. Adjust recursive call.
Fix up COMPLEX_CST handling.
(categorize_ctor_elements): Add p_unique_nz_elts argument, initialize
it and pass it through to categorize_ctor_elements_1.
(mostly_zeros_p, all_zeros_p): Adjust categorize_ctor_elements callers.
* gimplify.c (gimplify_init_constructor): Likewise. Don't force
ctor into readonly data section if num_unique_nonzero_elements is
smaller or equal to 1/8 of num_nonzero_elements and size is >= 64
bytes.
* g++.dg/tree-ssa/pr82294.C: New test.
* g++.dg/tree-ssa/pr87436.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/tree-ssa/pr82294.C
branches/gcc-8-branch/gcc/testsuite/g++.dg/tree-ssa/pr87436.C
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/expr.c
branches/gcc-8-branch/gcc/expr.h
branches/gcc-8-branch/gcc/gimplify.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:23:22 2019
Return-Path: <gcc-bugs-return-628219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51608 invoked by alias); 8 Jan 2019 10:23: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 51546 invoked by uid 55); 8 Jan 2019 10:23:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88410] [8 Regression] internal compiler error: output_operand: invalid expression as operand
Date: Tue, 08 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88410-4-ltWcwxoRym@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88410-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88410-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01028.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88410
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:22:44 2019
New Revision: 267710
URL: https://gcc.gnu.org/viewcvs?rev=267710&root=gcc&view=rev
Log:
Backported from mainline
2018-12-17 Jakub Jelinek <jakub@redhat.com>
PR c++/88410
* cp-gimplify.c (cp_fold) <case ADDR_EXPR>: For offsetof-like folding,
call maybe_constant_value on val to see if it is INTEGER_CST.
* g++.dg/cpp0x/pr88410.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/pr88410.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-628220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:24:59 2019
Return-Path: <gcc-bugs-return-628220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53689 invoked by alias); 8 Jan 2019 10:24:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53054 invoked by uid 55); 8 Jan 2019 10:24:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87934] [8 regression] struct with NSDMI of enum makes initialization a non-constant expression
Date: Tue, 08 Jan 2019 10:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87934-4-26uMMgzxta@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01029.txt.bz2
Content-length: 825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87934
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:23:32 2019
New Revision: 267711
URL: https://gcc.gnu.org/viewcvs?rev=267711&root=gcc&view=rev
Log:
Backported from mainline
2018-12-19 Jakub Jelinek <jakub@redhat.com>
PR c++/87934
* constexpr.c (cxx_eval_constant_expression) <case CONSTRUCTOR>: Do
re-process TREE_CONSTANT CONSTRUCTORs if they aren't reduced constant
expressions.
* g++.dg/cpp0x/constexpr-87934.C: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/cpp0x/constexpr-87934.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/constexpr.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:25:43 2019
Return-Path: <gcc-bugs-return-628221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58236 invoked by alias); 8 Jan 2019 10:25: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 58150 invoked by uid 55); 8 Jan 2019 10:25:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88541] VPCLMULQDQ 256-bit inline function unavailable with optimization but without enabled AVX512VL support
Date: Tue, 08 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88541-4-Lo8GdmJJgA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88541-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01030.txt.bz2
Content-length: 825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88541
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:24:56 2019
New Revision: 267712
URL: https://gcc.gnu.org/viewcvs?rev=267712&root=gcc&view=rev
Log:
Backported from mainline
2018-12-19 Jakub Jelinek <jakub@redhat.com>
PR target/88541
* config/i386/vpclmulqdqintrin.h (_mm256_clmulepi64_epi128): Enable
for -mavx -mvpclmulqdq rather than just for -mavx512vl -mvpclmulqdq.
* gcc.target/i386/avx-vpclmulqdq-1.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/i386/avx-vpclmulqdq-1.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/vpclmulqdqintrin.h
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:26:32 2019
Return-Path: <gcc-bugs-return-628222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59940 invoked by alias); 8 Jan 2019 10:26:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59647 invoked by uid 55); 8 Jan 2019 10:26:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88180] [7/8 Regression] ICE in vec<tree_node*, va_gc, vl_embed>::quick_push(tree_node* const&)
Date: Tue, 08 Jan 2019 10:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88180-4-HlU9peKiBS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88180-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88180-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01031.txt.bz2
Content-length: 972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88180
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:25:54 2019
New Revision: 267713
URL: https://gcc.gnu.org/viewcvs?rev=267713&root=gcc&view=rev
Log:
Backported from mainline
2018-12-20 Jakub Jelinek <jakub@redhat.com>
PR c++/88180
* parser.c (cp_parser_class_specifier_1): If
cp_parser_check_type_definition fails, skip default arguments, NSDMIs,
etc. like for erroneous template args.
* g++.dg/parse/pr88180.C: New test.
* g++.dg/pr85039-1.C: Don't expect diagnostics inside of the type
definition's NSDMIs.
Added:
branches/gcc-8-branch/gcc/testsuite/g++.dg/parse/pr88180.C
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/parser.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/testsuite/g++.dg/pr85039-1.C
>From gcc-bugs-return-628223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:27:16 2019
Return-Path: <gcc-bugs-return-628223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63747 invoked by alias); 8 Jan 2019 10:27: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 63664 invoked by uid 55); 8 Jan 2019 10:27:11 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88563] [7/8 Regression] wrong code with -O2 -fno-code-hoisting -fno-tree-ccp -fno-tree-dominator-opts -fno-tree-forwprop -fno-tree-fre -fno-tree-pre -fno-tree-vrp
Date: Tue, 08 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88563-4-DqxlQ1s5t1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01032.txt.bz2
Content-length: 900
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88563
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:26:39 2019
New Revision: 267714
URL: https://gcc.gnu.org/viewcvs?rev=267714&root=gcc&view=rev
Log:
Backported from mainline
2018-12-21 Jakub Jelinek <jakub@redhat.com>
PR rtl-optimization/88563
* expr.c (expand_expr_real_2) <case WIDEN_MULT_EXPR>: Swap innermode
and mode arguments to convert_modes. Likewise swap mode and word_mode
arguments. Handle both arguments with VOIDmode before convert_modes
of one of them. Formatting fixes.
* gcc.dg/pr88563.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pr88563.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/expr.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:29:59 2019
Return-Path: <gcc-bugs-return-628225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71289 invoked by alias); 8 Jan 2019 10: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 71222 invoked by uid 55); 8 Jan 2019 10:29:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88522] Error: operand size mismatch for `vpgatherqq'
Date: Tue, 08 Jan 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88522-4-2skDIrua69@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88522-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88522-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01034.txt.bz2
Content-length: 1038
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88522
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:29:21 2019
New Revision: 267715
URL: https://gcc.gnu.org/viewcvs?rev=267715&root=gcc&view=rev
Log:
Backported from mainline
2018-12-21 Jakub Jelinek <jakub@redhat.com>
PR target/88522
* config/i386/sse.md (*avx512pf_gatherpf<mode>sf_mask,
*avx512pf_gatherpf<mode>df_mask, *avx512pf_scatterpf<mode>sf_mask,
*avx512pf_scatterpf<mode>df_mask): Use %X5 instead of %5 for
-masm=intel.
(gatherq_mode): Remove mode iterator.
(*avx512f_gathersi<mode>, *avx512f_gathersi<mode>_2): Use X instead
of <xtg_mode>.
(*avx512f_gatherdi<mode>): Use X instead of <gatherq_mode>.
(*avx512f_gatherdi<mode>_2, *avx512f_scattersi<mode>,
*avx512f_scatterdi<mode>): Use %X5 for -masm=intel.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/sse.md
>From gcc-bugs-return-628224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:29:09 2019
Return-Path: <gcc-bugs-return-628224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69717 invoked by alias); 8 Jan 2019 10:29:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69642 invoked by uid 48); 8 Jan 2019 10:29:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget priority cc component target_milestone short_desc
Message-ID: <bug-88739-4-iWxtTEMWDB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01033.txt.bz2
Content-length: 5208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|aarch64_be armb |aarch64be
Priority|P3 |P2
CC| |ebotcazou at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Component|middle-end |tree-optimization
Target Milestone|--- |7.5
Summary|[7,8,9 Regression ] |[7/8/9 Regression]
|Big-endian union bug |Big-endian union bug
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Wilco from comment #3)
> (In reply to Richard Earnshaw from comment #2)
> > > _23 = BIT_FIELD_REF <_2, 16, 0>; // WRONG: should be _2, 14, 0
> >
> > _2 is declared as a 30-bit integer, so perhaps the statement is right, but
> > expand needs to understand that the shift extract of the top 16 bits comes
> > from a different location in big-endian.
>
> So the question becomes what format is this in?
>
> <unnamed-unsigned:30> _2;
>
> Is it big-endian memory format (so value is in top 30 bits) or simply a
> 30-bit value in a virtual register?
The middle-end (GIMPLE) thinks this is a 30-bit value in a virtual register.
And BIT_FIELD_REF <..., 16, 0> reads the first (counting from LSB) 16 bits.
That is, as far as I understand "endianess" is irrelevant for registers
but matters for memory.
We expand
_1 = ulAddr_3(D) >> 2;
_2 = (<unnamed-unsigned:30>) _1;
_6 = BIT_FIELD_REF <_2, 16, 0>;
to (_6 is unsigned short)
(insn 6 5 7 (set (reg:SI 95)
(lshiftrt:SI (reg/v:SI 94 [ ulAddr ])
(const_int 2 [0x2]))) "t.c":42:48 -1
(nil))
(insn 7 6 8 (set (reg:SI 96)
(and:SI (reg:SI 95)
(const_int 1073741823 [0x3fffffff]))) "t.c":42:48 -1
(nil))
(insn 8 7 9 (set (subreg:DI (reg:HI 97) 0)
(zero_extract:DI (subreg:DI (reg:SI 96) 0)
(const_int 16 [0x10])
(const_int 16 [0x10]))) "t.c":44:8 -1
(nil))
now I suppose for subregs (and its offset) endianess starts to matter.
Now my head of course starts to hurt when we build a paradoxical DImode
subreg of a SImode reg in big endian.
But going back what possibly goes wrong is when FRE does
Value numbering stmt = unData.strMemHead.b30AddrL = _2;
No store match
Value numbering store unData.strMemHead.b30AddrL to _2
..
Value numbering stmt = _3 = unData.ausValue[6];
Inserting name _9 for expression BIT_FIELD_REF <_2, 16, 0>
Setting value number of _3 to _9 (changed)
it analyzes unData.strMemHead.b30AddrL to be a reference at
a bit-offset with some bit-size, matching that up with the
same data from unData.ausValue[6] and translating that to
a BIT_FIELD_REF:
base2 = get_ref_base_and_extent (gimple_assign_lhs (def_stmt),
&offset2, &size2, &maxsize2,
&reverse);
if (!reverse
&& known_size_p (maxsize2)
&& known_eq (maxsize2, size2)
&& operand_equal_p (base, base2, 0)
&& known_subrange_p (offset, maxsize, offset2, size2)
/* ??? We can't handle bitfield precision extracts without
either using an alternate type for the BIT_FIELD_REF and
then doing a conversion or possibly adjusting the offset
according to endianness. */
&& (! INTEGRAL_TYPE_P (vr->type)
|| known_eq (ref->size, TYPE_PRECISION (vr->type)))
&& multiple_p (ref->size, BITS_PER_UNIT))
{
gimple_match_op op (gimple_match_cond::UNCOND,
BIT_FIELD_REF, vr->type,
vn_valueize (gimple_assign_rhs1 (def_stmt)),
bitsize_int (ref->size),
bitsize_int (offset - offset2));
here def_stmt is unData.strMemHead.b30AddrL = _2 while offset / ref
are from the load. There's already a comment about endianess but
it's oddly applied to ref->size vs. vr->type precision equality.
I think we need adjustments whenever ref->size (from the load) is
not equal to size2 (from the store)? That is, arbitrary sub-parts,
while contiguous in memory, might not be contiguous in the register?
*head hurts*
for the testcase
(gdb) p ref->size
$1 = {<poly_int_pod<2u, long>> = {coeffs = {16, 0}}, <No data fields>}
(gdb) p size2
$2 = {<poly_int_pod<2u, long>> = {coeffs = {30, 0}}, <No data fields>}
and offset == offset2 == 0.
Oh, and there's of course a plethora of variants, not to mention
FLOAT_WORDS_BIG_ENDIAN and REG_WORDS_BIG_ENDIAN.
Note the code above was exactly added to elide this kind of memory
operation...
Since the folding happens only since GCC 7 this is a regression.
Andrew somewhere mentioned that BIT_INSERT_EXPR expansion is also
wrong for BE (it's currently only used for vector element stuff
so that's a latent issue).
>From gcc-bugs-return-628226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:31:53 2019
Return-Path: <gcc-bugs-return-628226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75017 invoked by alias); 8 Jan 2019 10:31:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74893 invoked by uid 55); 8 Jan 2019 10:31:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85594] ICE during expand when compiling with -fwrapv -fopenmp
Date: Tue, 08 Jan 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85594-4-ObK5oRC7We@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01035.txt.bz2
Content-length: 946
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85594
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:30:45 2019
New Revision: 267716
URL: https://gcc.gnu.org/viewcvs?rev=267716&root=gcc&view=rev
Log:
Backported from mainline
2018-12-21 Jakub Jelinek <jakub@redhat.com>
PR middle-end/85594
PR middle-end/88553
* omp-expand.c (extract_omp_for_update_vars): Regimplify the condition
if needed.
(expand_omp_for_generic): Don't clobber t temporary for ordered loops.
* gcc.dg/gomp/pr85594.c: New test.
* gcc.dg/gomp/pr88553.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr85594.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr88553.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/omp-expand.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:31:54 2019
Return-Path: <gcc-bugs-return-628227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75153 invoked by alias); 8 Jan 2019 10:31:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74906 invoked by uid 55); 8 Jan 2019 10:31:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88553] ICE: tree check: expected ssa_name, have var_decl in SSA_VAL, at tree-ssa-sccvn.c:461
Date: Tue, 08 Jan 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88553-4-fyVRAnCYfs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88553-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88553-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01036.txt.bz2
Content-length: 946
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88553
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:30:45 2019
New Revision: 267716
URL: https://gcc.gnu.org/viewcvs?rev=267716&root=gcc&view=rev
Log:
Backported from mainline
2018-12-21 Jakub Jelinek <jakub@redhat.com>
PR middle-end/85594
PR middle-end/88553
* omp-expand.c (extract_omp_for_update_vars): Regimplify the condition
if needed.
(expand_omp_for_generic): Don't clobber t temporary for ordered loops.
* gcc.dg/gomp/pr85594.c: New test.
* gcc.dg/gomp/pr88553.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr85594.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/gomp/pr88553.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/omp-expand.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:33:06 2019
Return-Path: <gcc-bugs-return-628228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78977 invoked by alias); 8 Jan 2019 10:33: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 78759 invoked by uid 55); 8 Jan 2019 10:33:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7/8 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Tue, 08 Jan 2019 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88644-4-FrJ01GCWpl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01037.txt.bz2
Content-length: 1133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:32:26 2019
New Revision: 267718
URL: https://gcc.gnu.org/viewcvs?rev=267718&root=gcc&view=rev
Log:
Backported from mainline
2019-01-03 Jakub Jelinek <jakub@redhat.com>
PR debug/88644
* dwarf2out.c (modified_type_die): If type is equal to sizetype,
change it to qualified_type.
* gcc.dg/debug/dwarf2/pr88644.c: New test.
2019-01-03 Iain Sandoe <iain@sandoe.co.uk>
* gcc.dg/pubtypes-2.c: Adjust expected pubtypes length.
* gcc.dg/pubtypes-3.c: Likewise.
* gcc.dg/pubtypes-4.c: Likewise.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/debug/dwarf2/pr88644.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/dwarf2out.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pubtypes-2.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pubtypes-3.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pubtypes-4.c
>From gcc-bugs-return-628230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:34:54 2019
Return-Path: <gcc-bugs-return-628230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89943 invoked by alias); 8 Jan 2019 10: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 89709 invoked by uid 55); 8 Jan 2019 10:34:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82564] ICE at -O1 and above: in assign_stack_temp_for_type, at function.c:783
Date: Tue, 08 Jan 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82564-4-qbuePvzCdG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82564-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82564-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01039.txt.bz2
Content-length: 917
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82564
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:34:14 2019
New Revision: 267720
URL: https://gcc.gnu.org/viewcvs?rev=267720&root=gcc&view=rev
Log:
Backported from mainline
2019-01-05 Jakub Jelinek <jakub@redhat.com>
PR middle-end/82564
PR target/88620
* expr.c (expand_assignment): For calls returning VLA structures
if to_rtx is not a MEM, force it into a stack temporary.
* gcc.dg/nested-func-12.c: New test.
* gcc.c-torture/compile/pr82564.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.c-torture/compile/pr82564.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/nested-func-12.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/expr.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:34:00 2019
Return-Path: <gcc-bugs-return-628229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87169 invoked by alias); 8 Jan 2019 10:34: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 87064 invoked by uid 55); 8 Jan 2019 10:33:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88594] [9 Regression] ICE in int_mode_for_mode, at stor-layout.c:403
Date: Tue, 08 Jan 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88594-4-ExPPAQdZzW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01038.txt.bz2
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88594
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:33:23 2019
New Revision: 267719
URL: https://gcc.gnu.org/viewcvs?rev=267719&root=gcc&view=rev
Log:
Backported from mainline
2019-01-04 Jakub Jelinek <jakub@redhat.com>
PR target/88594
* config/i386/i386.c (ix86_expand_divmod_libfunc): Use mode instead
of GET_MODE (opN) as modes of the libcall arguments.
* gcc.dg/pr88594.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/pr88594.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/i386/i386.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:34:55 2019
Return-Path: <gcc-bugs-return-628231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89961 invoked by alias); 8 Jan 2019 10: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 89715 invoked by uid 55); 8 Jan 2019 10:34:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88620] [7/8 Regression] ICE in assign_stack_temp_for_type, at function.c:837
Date: Tue, 08 Jan 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88620-4-te0tIkkYTM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01040.txt.bz2
Content-length: 917
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 10:34:14 2019
New Revision: 267720
URL: https://gcc.gnu.org/viewcvs?rev=267720&root=gcc&view=rev
Log:
Backported from mainline
2019-01-05 Jakub Jelinek <jakub@redhat.com>
PR middle-end/82564
PR target/88620
* expr.c (expand_assignment): For calls returning VLA structures
if to_rtx is not a MEM, force it into a stack temporary.
* gcc.dg/nested-func-12.c: New test.
* gcc.c-torture/compile/pr82564.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.c-torture/compile/pr82564.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/nested-func-12.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/expr.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:36:31 2019
Return-Path: <gcc-bugs-return-628232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92905 invoked by alias); 8 Jan 2019 10:36:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92827 invoked by uid 48); 8 Jan 2019 10:36:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 10:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-N5Fq5HWGto@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01041.txt.bz2
Content-length: 582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
So FRE tries to match up a store with (possibly bit-precision) type T with a
load of (possibly bit-precision) type U. The load and store are analyzed
by get_ref_base_and_extent to a common base object hand happen at
bit-position offset/offset2 with bitsize size/size2. Since they are
memory ops all the *_BIG_ENDIAN "matter" (since they are typed even
FLOAT_WORDS_BIG_ENDIAN might matter). In the end we are BIT_FIELD_REFing
the stored _register_ though...
>From gcc-bugs-return-628233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:42:02 2019
Return-Path: <gcc-bugs-return-628233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101527 invoked by alias); 8 Jan 2019 10:42: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 101355 invoked by uid 48); 8 Jan 2019 10:41:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85593] [7 Regression] GCC on ARM allocates R3 for local variable when calling naked function with O2 optimizations enabled
Date: Tue, 08 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.4.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-85593-4-B9lQ64iQIP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01042.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85593
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] GCC on ARM |[7 Regression] GCC on ARM
|allocates R3 for local |allocates R3 for local
|variable when calling naked |variable when calling naked
|function with O2 |function with O2
|optimizations enabled |optimizations enabled
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:43:23 2019
Return-Path: <gcc-bugs-return-628235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109869 invoked by alias); 8 Jan 2019 10:43: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 109617 invoked by uid 48); 8 Jan 2019 10:43:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85644] [8 Regression] -fstack-protector generates invalid read to %fs:0x0 on mac
Date: Tue, 08 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85644-4-anr0uy5yLG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01044.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85644
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:43:24 2019
Return-Path: <gcc-bugs-return-628236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110090 invoked by alias); 8 Jan 2019 10:43: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 109702 invoked by uid 48); 8 Jan 2019 10:43:19 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86832] [8 Regression] GCC v8.2.0 tries to use native TLS with -fstack-protector-strong on Windows (mingw-w64)
Date: Tue, 08 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86832-4-5c75F6A6Cr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01045.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86832
Bug 86832 depends on bug 85644, which changed state.
Bug 85644 Summary: [8 Regression] -fstack-protector generates invalid read to %fs:0x0 on mac
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85644
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:43:39 2019
Return-Path: <gcc-bugs-return-628237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111335 invoked by alias); 8 Jan 2019 10:43: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 111229 invoked by uid 48); 8 Jan 2019 10:43:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86669] [7 regression] Complete object constructor clone omits length for a c++11 braced initialiser
Date: Tue, 08 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-86669-4-pnBJAOatP8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86669-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86669-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01046.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86669
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 regression] Complete |[7 regression] Complete
|object constructor clone |object constructor clone
|omits length for a c++11 |omits length for a c++11
|braced initialiser |braced initialiser
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:43:04 2019
Return-Path: <gcc-bugs-return-628234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104662 invoked by alias); 8 Jan 2019 10:43:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103394 invoked by uid 48); 8 Jan 2019 10:43:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85594] ICE during expand when compiling with -fwrapv -fopenmp
Date: Tue, 08 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85594-4-N31BewbTyG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85594-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85594-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01043.txt.bz2
Content-length: 139
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85594
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:43:51 2019
Return-Path: <gcc-bugs-return-628238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112233 invoked by alias); 8 Jan 2019 10:43:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112143 invoked by uid 48); 8 Jan 2019 10:43:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86832] [8 Regression] GCC v8.2.0 tries to use native TLS with -fstack-protector-strong on Windows (mingw-w64)
Date: Tue, 08 Jan 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86832-4-SgiWc5vxFm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01047.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86832
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:44:33 2019
Return-Path: <gcc-bugs-return-628241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114549 invoked by alias); 8 Jan 2019 10:44:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114251 invoked by uid 48); 8 Jan 2019 10:44:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87360] [8 Regression] ICE in remove_redundant_iv_tests at gcc/tree-ssa-loop-ivcanon.c:571 since r255467
Date: Tue, 08 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87360-4-qDDgmK5pXV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87360-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87360-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01050.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87360
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:44:29 2019
Return-Path: <gcc-bugs-return-628240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114247 invoked by alias); 8 Jan 2019 10: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 113420 invoked by uid 48); 8 Jan 2019 10:44:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/87039] [8 Regression] DW_OP_fbreg used without a frame base on a C++ code w/ -fopenmp
Date: Tue, 08 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87039-4-JpqtF4OGiZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87039-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87039-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01049.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87039
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:44:11 2019
Return-Path: <gcc-bugs-return-628239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113235 invoked by alias); 8 Jan 2019 10:44:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113040 invoked by uid 48); 8 Jan 2019 10:44:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86900] [8 Regression] -gdwarf-5 -O2 -ffunction-sections = assembler error
Date: Tue, 08 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86900-4-9g5MDvMYTj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86900-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86900-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01048.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86900
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:00 2019
Return-Path: <gcc-bugs-return-628242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117104 invoked by alias); 8 Jan 2019 10:45: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 116043 invoked by uid 48); 8 Jan 2019 10:45:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87436] [7 Regression] G++ produces >300MB .rodata section to initialize struct with big array
Date: Tue, 08 Jan 2019 10:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-87436-4-zYAflJ3FXT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01051.txt.bz2
Content-length: 607
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87436
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] G++ |[7 Regression] G++ produces
|produces >300MB .rodata |>300MB .rodata section to
|section to initialize |initialize struct with big
|struct with big array |array
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:49 2019
Return-Path: <gcc-bugs-return-628250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118341 invoked by alias); 8 Jan 2019 10:46: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 117598 invoked by uid 48); 8 Jan 2019 10:46:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87934] [8 regression] struct with NSDMI of enum makes initialization a non-constant expression
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87934-4-Z4py1zh6DZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01059.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87934
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:22 2019
Return-Path: <gcc-bugs-return-628244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117791 invoked by alias); 8 Jan 2019 10:46: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 117237 invoked by uid 48); 8 Jan 2019 10:45:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87506] [7 Regression] ICE with inherited constexpr constructor with const argument
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-87506-4-jVWr0uTACm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87506-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87506-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01053.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87506
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] ICE with |[7 Regression] ICE with
|inherited constexpr |inherited constexpr
|constructor with const |constructor with const
|argument |argument
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:48 2019
Return-Path: <gcc-bugs-return-628249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118033 invoked by alias); 8 Jan 2019 10:46:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117641 invoked by uid 48); 8 Jan 2019 10:46:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88611-4-ivn4RevI5i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01055.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:22 2019
Return-Path: <gcc-bugs-return-628245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117902 invoked by alias); 8 Jan 2019 10:46:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117495 invoked by uid 48); 8 Jan 2019 10:46:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87898] [8 Regression] ICE in separate_decls_in_region_debug, at tree-parloops.c:961
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87898-4-pISKvSikdP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87898-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87898-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01054.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87898
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:22 2019
Return-Path: <gcc-bugs-return-628247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117978 invoked by alias); 8 Jan 2019 10:46:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117539 invoked by uid 48); 8 Jan 2019 10:46:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87895] [7 Regression] ICE in purge_dead_edges, at cfgrtl.c:3246
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-invalid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-87895-4-ZgAaqM7bS1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87895-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87895-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01052.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87895
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] ICE in |[7 Regression] ICE in
|purge_dead_edges, at |purge_dead_edges, at
|cfgrtl.c:3246 |cfgrtl.c:3246
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:47 2019
Return-Path: <gcc-bugs-return-628246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117924 invoked by alias); 8 Jan 2019 10:46:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117520 invoked by uid 48); 8 Jan 2019 10:46:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87598] [8 Regression] Rejects "%a0" with constant
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87598-4-y0Y0X00fKX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01057.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87598
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:23 2019
Return-Path: <gcc-bugs-return-628243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117738 invoked by alias); 8 Jan 2019 10:46: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 117234 invoked by uid 48); 8 Jan 2019 10:45:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87475] [8 Regression] ICE in patch_jump_insn, at cfgrtl.c:1275
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87475-4-FeH0NikNC9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01056.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87475
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:46:47 2019
Return-Path: <gcc-bugs-return-628248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118000 invoked by alias); 8 Jan 2019 10:46:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117417 invoked by uid 48); 8 Jan 2019 10:46:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87539] [8 Regression] internal compiler error when compiling project with Os optimization flag
Date: Tue, 08 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87539-4-3JFPXNRNG6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87539-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87539-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01058.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87539
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:47:44 2019
Return-Path: <gcc-bugs-return-628253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125923 invoked by alias); 8 Jan 2019 10:47:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125092 invoked by uid 48); 8 Jan 2019 10:47:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88071] [8 Regression] ICE: verify_gimple failed (error: dead STMT in EH table)
Date: Tue, 08 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88071-4-n9JwdPMk5v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88071-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88071-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01062.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88071
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:47:33 2019
Return-Path: <gcc-bugs-return-628252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124314 invoked by alias); 8 Jan 2019 10:47:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123564 invoked by uid 48); 8 Jan 2019 10:47:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88018] [8 Regression] ICE in insert_insn_on_edge at cfgrtl.c:1952 since r255066
Date: Tue, 08 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88018-4-H3D0UpcRLk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88018-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88018-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01061.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88018
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:47:33 2019
Return-Path: <gcc-bugs-return-628251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124276 invoked by alias); 8 Jan 2019 10:47:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123384 invoked by uid 55); 8 Jan 2019 10:47:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88611] [9 Regression] ICE in eliminate_stmt, at tree-ssa-sccvn.c:5011
Date: Tue, 08 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88611-4-NfHumqp2Qu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88611-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01060.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88611
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 8 10:46:04 2019
New Revision: 267721
URL: https://gcc.gnu.org/viewcvs?rev=267721&root=gcc&view=rev
Log:
2019-01-08 Richard Biener <rguenther@suse.de>
PR fortran/88611
* trans-expr.c (gfc_conv_initializer): For ISOCBINDING_NULL_*
directly build the expected GENERIC tree.
* gfortran.dg/pr88611.f90: New testcase.
Added:
trunk/gcc/testsuite/gfortran.dg/pr88611.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-expr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:48:57 2019
Return-Path: <gcc-bugs-return-628254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2938 invoked by alias); 8 Jan 2019 10:48: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 2242 invoked by uid 48); 8 Jan 2019 10:48:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88103] [7 Regression] Wrong value category when conditional expression result is used as object expression
Date: Tue, 08 Jan 2019 10:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to short_desc
Message-ID: <bug-88103-4-8BdJuqq7wj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01063.txt.bz2
Content-length: 817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88103
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
Summary|[7/8/9 Regression] Wrong |[7 Regression] Wrong value
|value category when |category when conditional
|conditional expression |expression result is used
|result is used as object |as object expression
|expression |
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9+ and 8.3+ too.
>From gcc-bugs-return-628255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:19 2019
Return-Path: <gcc-bugs-return-628255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3070 invoked by alias); 8 Jan 2019 10:48: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 2876 invoked by uid 48); 8 Jan 2019 10:48:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88180] [7 Regression] ICE in vec<tree_node*, va_gc, vl_embed>::quick_push(tree_node* const&)
Date: Tue, 08 Jan 2019 10:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88180-4-yH63r4dpeZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88180-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88180-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01064.txt.bz2
Content-length: 606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88180
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] ICE in |[7 Regression] ICE in
|vec<tree_node*, va_gc, |vec<tree_node*, va_gc,
|vl_embed>::quick_push(tree_ |vl_embed>::quick_push(tree_
|node* const&) |node* const&)
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:40 2019
Return-Path: <gcc-bugs-return-628260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4529 invoked by alias); 8 Jan 2019 10:49:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4121 invoked by uid 48); 8 Jan 2019 10:49:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88416] [8 Regression] ICE in in df_uses_record, at df-scan.c:3013
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88416-4-VY3hHbM55E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88416-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88416-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01070.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88416
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:42 2019
Return-Path: <gcc-bugs-return-628261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4919 invoked by alias); 8 Jan 2019 10:49: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 4071 invoked by uid 48); 8 Jan 2019 10:49:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88410] [8 Regression] internal compiler error: output_operand: invalid expression as operand
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.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: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88410-4-q980p8fxEP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88410-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88410-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01068.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88410
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:40 2019
Return-Path: <gcc-bugs-return-628259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4374 invoked by alias); 8 Jan 2019 10:49:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3580 invoked by uid 48); 8 Jan 2019 10:49:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88215] UBSAN: Internal compiler error with attribute(unused)
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.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-88215-4-7TPahrpiIy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88215-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01069.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88215
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:35 2019
Return-Path: <gcc-bugs-return-628256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3721 invoked by alias); 8 Jan 2019 10:49:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2983 invoked by uid 48); 8 Jan 2019 10:48:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88181] [7 Regression] ICE: verify_type failed (error: type variant differs by TYPE_PACKED)
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88181-4-bXFyoKsm3I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88181-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88181-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01065.txt.bz2
Content-length: 604
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88181
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] ICE: |[7 Regression] ICE:
|verify_type failed (error: |verify_type failed (error:
|type variant differs by |type variant differs by
|TYPE_PACKED) |TYPE_PACKED)
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:36 2019
Return-Path: <gcc-bugs-return-628257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4109 invoked by alias); 8 Jan 2019 10:49: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 3596 invoked by uid 48); 8 Jan 2019 10:49:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88234] UBsan and runtime error: signed integer overflow using unsigned vector
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88234-4-DDSNRJcOw6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88234-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88234-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01067.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88234
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:40 2019
Return-Path: <gcc-bugs-return-628258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4364 invoked by alias); 8 Jan 2019 10:49:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3673 invoked by uid 48); 8 Jan 2019 10:49:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88377] ICE in gfc_omp_clause_copy_ctor, at fortran/trans-openmp.c:614
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp
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-88377-4-h4YTUZwDVS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88377-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88377-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01066.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88377
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:49:45 2019
Return-Path: <gcc-bugs-return-628262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5328 invoked by alias); 8 Jan 2019 10:49:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4252 invoked by uid 48); 8 Jan 2019 10:49:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88426] [8 Regression] Compiler crash if use special code with command line switch -fsanitize=float-cast-overflow
Date: Tue, 08 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88426-4-N9RBGD0Eo6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01071.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88426
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:50:52 2019
Return-Path: <gcc-bugs-return-628266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13421 invoked by alias); 8 Jan 2019 10:50: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 12545 invoked by uid 48); 8 Jan 2019 10:50:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88563] [7 Regression] wrong code with -O2 -fno-code-hoisting -fno-tree-ccp -fno-tree-dominator-opts -fno-tree-forwprop -fno-tree-fre -fno-tree-pre -fno-tree-vrp
Date: Tue, 08 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88563-4-AQEQnVMiIU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88563-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88563-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01075.txt.bz2
Content-length: 820
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88563
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] wrong code |[7 Regression] wrong code
|with -O2 -fno-code-hoisting |with -O2 -fno-code-hoisting
|-fno-tree-ccp |-fno-tree-ccp
|-fno-tree-dominator-opts |-fno-tree-dominator-opts
|-fno-tree-forwprop |-fno-tree-forwprop
|-fno-tree-fre -fno-tree-pre |-fno-tree-fre -fno-tree-pre
|-fno-tree-vrp |-fno-tree-vrp
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:50:13 2019
Return-Path: <gcc-bugs-return-628264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8657 invoked by alias); 8 Jan 2019 10:50: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 7874 invoked by uid 48); 8 Jan 2019 10:50:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88470] [7 Regression] ICE in maybe_record_trace_start, at dwarf2cfi.c:2354
Date: Tue, 08 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88470-4-qtpjzfj0I9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88470-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88470-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01072.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88470
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] ICE in |[7 Regression] ICE in
|maybe_record_trace_start, |maybe_record_trace_start,
|at dwarf2cfi.c:2354 |at dwarf2cfi.c:2354
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:50:01 2019
Return-Path: <gcc-bugs-return-628263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7280 invoked by alias); 8 Jan 2019 10:50: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 6640 invoked by uid 48); 8 Jan 2019 10:49:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88463] Rejects conforming source, OpenMP Parallel region Default(None) reference to module parameter array, separate source
Date: Tue, 08 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: openmp, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88463-4-Kl7MK78M1L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88463-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88463-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01073.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88463
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:50:39 2019
Return-Path: <gcc-bugs-return-628265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11930 invoked by alias); 8 Jan 2019 10:50:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11209 invoked by uid 48); 8 Jan 2019 10:50:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88553] ICE: tree check: expected ssa_name, have var_decl in SSA_VAL, at tree-ssa-sccvn.c:461
Date: Tue, 08 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88553-4-lWixjZw919@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88553-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88553-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01074.txt.bz2
Content-length: 139
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88553
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:51:02 2019
Return-Path: <gcc-bugs-return-628267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14734 invoked by alias); 8 Jan 2019 10:51:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14034 invoked by uid 48); 8 Jan 2019 10:50:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88620] [7 Regression] ICE in assign_stack_temp_for_type, at function.c:837
Date: Tue, 08 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88620-4-ZR4YMXaxNq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01076.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88620
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] ICE in |[7 Regression] ICE in
|assign_stack_temp_for_type, |assign_stack_temp_for_type,
|at function.c:837 |at function.c:837
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:51:10 2019
Return-Path: <gcc-bugs-return-628268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16064 invoked by alias); 8 Jan 2019 10:51: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 15308 invoked by uid 48); 8 Jan 2019 10:51:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88644] [7 Regression] Unexpected pub type info eliminated after r246973 (causes pubtypes-*.c to regress).
Date: Tue, 08 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88644-4-xHMKEYw0zH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01077.txt.bz2
Content-length: 618
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88644
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8 Regression] Unexpected |[7 Regression] Unexpected
|pub type info eliminated |pub type info eliminated
|after r246973 (causes |after r246973 (causes
|pubtypes-*.c to regress). |pubtypes-*.c to regress).
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 8.3+ too.
>From gcc-bugs-return-628269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 10:58:05 2019
Return-Path: <gcc-bugs-return-628269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26266 invoked by alias); 8 Jan 2019 10:58: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 26086 invoked by uid 48); 8 Jan 2019 10:57:59 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 10:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-2kj0wqiHKz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01078.txt.bz2
Content-length: 1666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #10)
> (In reply to Romain Geissler from comment #9)
> > This may be some naive question, but if we are currently trying to build a
> > libstdc++, shouldn't we assume there is no pre-existing libstdc++ and run
> > the different checks in the configure script either with the C compiler (if
> > indeed we never use C++)
>
> No, because testing whether a C compiler can use those functions tells us
> nothing about whether G++ will be able to use them. C libraries expose
> different declarations to C and C++ programs.
>
> > or with CXXFLAGS like -nodefaultlib ?
>
> That would also make libc unavailable.
The C++ configure tests are done with the newly-built xgcc, which means it
won't try to link to libstdc++. In my config.log I see this command:
configure:80504: checking for utime
configure:80554: /tmp/build/./gcc/xgcc -shared-libgcc -B/tmp/build/./gcc
-nostdinc++ -L/tmp/build/x86_64-pc-linux-gnu/libstdc++-v3/src
-L/tmp/build/x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/tmp/build/x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-B/usr/local/x86_64-pc-linux-gnu/bin/ -B/usr/local/x86_64-pc-linux-gnu/lib/
-isystem /usr/local/x86_64-pc-linux-gnu/include -isystem
/usr/local/x86_64-pc-linux-gnu/sys-include -o conftest -g -O2 -D_GNU_SOURCE
-fno-exceptions -Wl,-t conftest.cpp >&5
There's no -lstdc++ there, and xgcc won't add it implicitly.
The problem is that you're using x86_64-1a-linux-gnu-g++ as the compiler for
these tests, and g++ automatically adds -lstdc++.
>From gcc-bugs-return-628271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:16:17 2019
Return-Path: <gcc-bugs-return-628271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64658 invoked by alias); 8 Jan 2019 11:16: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 64136 invoked by uid 48); 8 Jan 2019 11:16:12 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84436] [8/9 Regression] Missed optimization with switch on enum constants returning the same value
Date: Tue, 08 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-84436-4-BCLAMaJMmh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01080.txt.bz2
Content-length: 592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84436
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=88753
--- Comment #14 from Martin Liška <marxin at gcc dot gnu.org> ---
Thanks, I found that libzip package fails since the same revision. I'll start
with that. I create new PR for that: PR88753.
>From gcc-bugs-return-628270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:16:10 2019
Return-Path: <gcc-bugs-return-628270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63840 invoked by alias); 8 Jan 2019 11:16: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 63473 invoked by uid 48); 8 Jan 2019 11:15:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] New: Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01079.txt.bz2
Content-length: 2988
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
Bug ID: 88753
Summary: Wrong code since r265463 in tree switch conversion
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
As reported in https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84436#c12:
Romain Geissler 2019-01-07 14:41:34 UTC
Hi,
I have tried the following script directly inside docker using the official
"debian:buster" docker image, so I hope it will not require much more
dependencies than what is written here.
Tested with x86-64.
<<END_OF_SCRIPT
#!/bin/bash
set -e
# Install a few dependencies
apt-get update
apt-get install -y curl tar build-essential cmake python
LLVM_DIRECTORY=/llvm
LLVM_TAR="http://releases.llvm.org/7.0.1/llvm-7.0.1.src.tar.xz"
CLANG_TAR="http://releases.llvm.org/7.0.1/cfe-7.0.1.src.tar.xz"
COMPILER_RT_TAR="http://releases.llvm.org/7.0.1/compiler-rt-7.0.1.src.tar.xz"
mkdir -p "${LLVM_DIRECTORY}/src"
mkdir -p "${LLVM_DIRECTORY}/build"
cd "${LLVM_DIRECTORY}/src"
curl "${LLVM_TAR}" | tar -Jx --strip-components=1 -f -
mkdir -p "${LLVM_DIRECTORY}/src/tools/clang"
cd "${LLVM_DIRECTORY}/src/tools/clang"
curl "${CLANG_TAR}" | tar -Jx --strip-components=1 -f -
mkdir -p "${LLVM_DIRECTORY}/src/projects/compiler-rt"
cd "${LLVM_DIRECTORY}/src/projects/compiler-rt"
curl "${COMPILER_RT_TAR}" | tar -Jx --strip-components=1 -f -
cd "${LLVM_DIRECTORY}/build"
cmake -G "Unix Makefiles" -C
"${LLVM_DIRECTORY}/src/tools/clang/cmake/caches/PGO.cmake"
"${LLVM_DIRECTORY}/src"
make -j 32 stage2-instrumented-generate-profdata
END_OF_SCRIPT
in order to use your own gcc, make sure that you update the $PATH environment
variable when running cmake/make.
I suggest you build clang both with and without your fix in gcc, then explore
the whole build tree and find all *.o files which differ (I hope there aren't a
lot), to check why they behave differently.
Note that it seems like gcc had an earlier regression, making the clang
bootstrap fail a bit later after building compiler-rt, with an error like:
FAILED: tools/clang/include/clang/AST/StmtNodes.inc
cd /workdir/build/final-system/llvm-build/tools/clang/stage2-instrumented-bins
&&
/workdir/build/final-system/llvm-build/tools/clang/stage2-instrumented-bins/bin/clang-tblgen
-gen-clang-stmt-nodes -I /workdir/src/llvm-8.0.0/clang/include/clang/AST -I
/workdir/src/llvm-8.0.0/llvm/include
/workdir/src/llvm-8.0.0/clang/include/clang/AST/../Basic/StmtNodes.td -o
tools/clang/include/clang/AST/StmtNodes.inc -d
tools/clang/include/clang/AST/StmtNodes.inc.d
This is an unrelated error, which I think comes from a gcc regression too, and
which I will bisect as well.
If you need more info, just ask.
Cheers,
Romain
>From gcc-bugs-return-628272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:16:35 2019
Return-Path: <gcc-bugs-return-628272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65559 invoked by alias); 8 Jan 2019 11:16:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65522 invoked by uid 48); 8 Jan 2019 11:16:31 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88753-4-IPGbcce7iu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01081.txt.bz2
Content-length: 135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Mine. Also
>From gcc-bugs-return-628273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:17:04 2019
Return-Path: <gcc-bugs-return-628273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66541 invoked by alias); 8 Jan 2019 11:17:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66464 invoked by uid 48); 8 Jan 2019 11:16:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-88753-4-j61n0KYPVQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01082.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://bugzilla.opensuse.o
| |rg/show_bug.cgi?id=1121063
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Mine, also seen in libzip package.
>From gcc-bugs-return-628274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:17:14 2019
Return-Path: <gcc-bugs-return-628274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67290 invoked by alias); 8 Jan 2019 11:17:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67221 invoked by uid 48); 8 Jan 2019 11:17:10 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88753-4-OzsbIyobr0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01083.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-08
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-628275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:27:58 2019
Return-Path: <gcc-bugs-return-628275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11877 invoked by alias); 8 Jan 2019 11:27:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11611 invoked by uid 48); 8 Jan 2019 11:27:53 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80916] [7/8/9 Regression] Spurious "declared 'static' but never defined" warning
Date: Tue, 08 Jan 2019 11:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80916-4-xuRwAvevQg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01084.txt.bz2
Content-length: 632
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80916
--- Comment #7 from ensadc at mailnesia dot com ---
Note that the "never defined" part is also misleading: the warning persists
when `i::dispatch` does have a definition
(https://wandbox.org/permlink/MKif1shXFjt7aT6C):
struct j {
virtual void dispatch(void *) {}
};
template <typename>
struct i : j {
void dispatch(void *) {} // warning: 'void i< <template-parameter-1-1>
>::dispatch(void*) [with <template-parameter-1-1> = {anonymous}::l]' declared
'static' but never defined [-Wunused-function]
};
namespace {
struct l : i<l> {};
}
void f(j *k) {
k->dispatch(0);
}
>From gcc-bugs-return-628276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:41:15 2019
Return-Path: <gcc-bugs-return-628276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51051 invoked by alias); 8 Jan 2019 11:41: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 50983 invoked by uid 48); 8 Jan 2019 11:41:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88753-4-gdVkzd9swG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01085.txt.bz2
Content-length: 821
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:
$ cat zip.c
typedef unsigned short int uint16_t;
typedef unsigned char uint8_t;
uint16_t length;
uint16_t enc_method_global;
uint8_t
__attribute__((noipa))
_zip_buffer_get_8(int buffer)
{
return buffer;
}
int
__attribute__((noipa))
foo(int v)
{
uint16_t enc_method;
switch (_zip_buffer_get_8(v)) {
case 1:
enc_method = 0x0101;
break;
case 2:
enc_method = 0x0102;
break;
case 3:
enc_method = 0x0103;
break;
default:
__builtin_abort ();
}
enc_method_global = enc_method;
}
int main(int argc, char **argv)
{
foo (1);
if (enc_method_global != 0x0101)
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-628278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:55:41 2019
Return-Path: <gcc-bugs-return-628278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77068 invoked by alias); 8 Jan 2019 11:55:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77003 invoked by uid 48); 8 Jan 2019 11:55:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 11:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-DCvXgbhF7K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01087.txt.bz2
Content-length: 2548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
So I think part of a fix would be the following. Not sure if
REG_WORDS_BIG_ENDIAN or FLOAT_WORDS_BIG_ENDIAN come into play.
With the fix we no longer simplify this for aarch64 since
BITS_BIG_ENDIAN is 0 even in BE mode.
Index: gcc/tree-ssa-sccvn.c
===================================================================
--- gcc/tree-ssa-sccvn.c (revision 267553)
+++ gcc/tree-ssa-sccvn.c (working copy)
@@ -2229,13 +2229,18 @@ vn_reference_lookup_3 (ao_ref *ref, tree
according to endianness. */
&& (! INTEGRAL_TYPE_P (vr->type)
|| known_eq (ref->size, TYPE_PRECISION (vr->type)))
- && multiple_p (ref->size, BITS_PER_UNIT))
+ && multiple_p (ref->size, BITS_PER_UNIT)
+ && BYTES_BIG_ENDIAN == WORDS_BIG_ENDIAN
+ && BITS_BIG_ENDIAN == BYTES_BIG_ENDIAN)
{
gimple_match_op op (gimple_match_cond::UNCOND,
BIT_FIELD_REF, vr->type,
vn_valueize (gimple_assign_rhs1 (def_stmt)),
bitsize_int (ref->size),
- bitsize_int (offset - offset2));
+ bitsize_int
+ (BYTES_BIG_ENDIAN
+ ? size2 - (offset - offset2) - ref->size
+ : offset - offset2));
tree val = vn_nary_build_or_lookup (&op);
if (val
&& (TREE_CODE (val) != SSA_NAME
In case both sizes/offsets
are mutliples of BITS_PER_UNIT BITS_BIG_ENDIAN shouldn't matter
though (likewise if size2 < WORD_SIZE). So a less conservative check
might be
&& (known_le (size2, BITS_PER_WORD)
|| BYTES_BIG_ENDIAN == WORDS_BIG_ENDIAN)
&& (BITS_BIG_ENDIAN == BYTES_BIG_ENDIAN
|| (multiple_p (offset2, BITS_PER_UNIT)
&& multiple_p (offset, BITS_PER_UNIT)
&& (!BYTES_BIG_ENDIAN
|| multiple_p (size2, BITS_PER_UNIT)))))
but I guess we lack exhaustive testing (and a list of targets that cover
all combinations of endianesses).
That is, not sure if BIT_FIELD_REF <_2, 16, 14> would be correct as suggested
for aarch64_be because of that BITS_BIG_ENDIAN setting.
>From gcc-bugs-return-628277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:55:12 2019
Return-Path: <gcc-bugs-return-628277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75724 invoked by alias); 8 Jan 2019 11:55: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 75633 invoked by uid 48); 8 Jan 2019 11:55:06 -0000
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88754] New: Constructor call wrongly rejected
Date: Tue, 08 Jan 2019 11: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: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: reichelt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01086.txt.bz2
Content-length: 1164
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88754
Bug ID: 88754
Summary: Constructor call wrongly rejected
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: reichelt at gcc dot gnu.org
Target Milestone: ---
The following valid code snippet is wrongly rejected
(since at least GCC 4.1, probably even before):
=============================================
struct A
{
A(int);
void foo();
};
template<int N> int value() { return N; }
void bar()
{
A(value<0>()).foo(); // fails
(A(value<0>())).foo(); // OK
}
=============================================
bug.cc: In function 'void bar()':
bug.cc:11:4: error: invalid declaration of '::value<0>'
11 | A(value<0>()).foo();
| ^
The code is compiled by clang and MSVC.
>From gcc-bugs-return-628279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:56:37 2019
Return-Path: <gcc-bugs-return-628279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78660 invoked by alias); 8 Jan 2019 11:56: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 78608 invoked by uid 48); 8 Jan 2019 11:56:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88754] Constructor call wrongly rejected
Date: Tue, 08 Jan 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88754-4-X9pf7185nS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01088.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88754
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
Ever confirmed|0 |1
>From gcc-bugs-return-628280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:57:16 2019
Return-Path: <gcc-bugs-return-628280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79646 invoked by alias); 8 Jan 2019 11:57:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79604 invoked by uid 48); 8 Jan 2019 11:57:12 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88753-4-GYQYEesy99@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01089.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-628281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:57:34 2019
Return-Path: <gcc-bugs-return-628281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80438 invoked by alias); 8 Jan 2019 11:57: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 80404 invoked by uid 48); 8 Jan 2019 11:57:30 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] [9 Regression] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 11:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-88753-4-u5nMXLzhUT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01090.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |8.2.0
Target Milestone|--- |9.0
Summary|Wrong code since r265463 in |[9 Regression] Wrong code
|tree switch conversion |since r265463 in tree
| |switch conversion
Known to fail| |9.0
>From gcc-bugs-return-628282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 11:58:46 2019
Return-Path: <gcc-bugs-return-628282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82449 invoked by alias); 8 Jan 2019 11:58: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 82417 invoked by uid 48); 8 Jan 2019 11:58:42 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88752] ICE in enclosing_instantiation_of, at cp/pt.c:13328
Date: Tue, 08 Jan 2019 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-88752-4-u4u8qOuhhm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01091.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
Matthias Kretz <kretz at kde dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45375|0 |1
is obsolete| |
--- Comment #1 from Matthias Kretz <kretz at kde dot org> ---
Created attachment 45376
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45376&action=edit
reduced test case
>From gcc-bugs-return-628283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:00:51 2019
Return-Path: <gcc-bugs-return-628283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85096 invoked by alias); 8 Jan 2019 12:00:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84829 invoked by uid 48); 8 Jan 2019 12:00:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] [9 Regression] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 12:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88753-4-xSOhiAzHlu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01092.txt.bz2
Content-length: 152
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm testing patch for that.
>From gcc-bugs-return-628284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:03:15 2019
Return-Path: <gcc-bugs-return-628284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89456 invoked by alias); 8 Jan 2019 12:03:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89329 invoked by uid 48); 8 Jan 2019 12:03:11 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88754] Constructor call wrongly assumed to be a variable declaration
Date: Tue, 08 Jan 2019 12:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88754-4-Q3bprpabUx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01093.txt.bz2
Content-length: 142
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88754
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Related to PR 37213.
>From gcc-bugs-return-628285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:09:35 2019
Return-Path: <gcc-bugs-return-628285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86004 invoked by alias); 8 Jan 2019 12:09: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 85366 invoked by uid 48); 8 Jan 2019 12:09:31 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-IOW5ulal9U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01094.txt.bz2
Content-length: 586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
So somehow build up exhaustive testing via
struct S # n # AT # m { \
T pad : m; \
T val : n; \
};
T __attribute__((noinline)) load8at0 () { return u.s8at0.val; }
...
union U {
T val;
struct S8at0 s8at0;
...
} u;
int main()
{
volatile T val = 0x0102030405060708;
u.val = val;
if (u.s8at0.val != load8at0 ())
__builtin_abort ();
...
return 0;
}
with T possibly unsigned __int128_t, for n in {8, 16, 32, 64}
and m in [0, 128 - n].
>From gcc-bugs-return-628286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:11:31 2019
Return-Path: <gcc-bugs-return-628286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89283 invoked by alias); 8 Jan 2019 12:11: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 89168 invoked by uid 48); 8 Jan 2019 12:11:23 -0000
From: "ciro.santilli at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88648] [7/8/9 Regression] Force unified syntax for inline assembly not functional (-masm-syntax-unified)
Date: Tue, 08 Jan 2019 12:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ciro.santilli 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88648-4-UbnRV8Buvt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01095.txt.bz2
Content-length: 814
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88648
Ciro Santilli <ciro.santilli at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ciro.santilli at gmail dot com
--- Comment #2 from Ciro Santilli <ciro.santilli at gmail dot com> ---
I have observed a similar problem on GCC 5.4.0 on Ubuntu 16.04 package
gcc-arm-linux-gnueabihf.
The problem only happens if I give both -marm and -masm-syntax-unified, then it
seems to ignore -masm-syntax-unified.
But without -marm it generates thumb code, which is not what I want.
Previously asked at:
https://stackoverflow.com/questions/54078112/how-to-write-syntax-unified-ual-armv7-inline-assembly-in-gcc
>From gcc-bugs-return-628287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:26:25 2019
Return-Path: <gcc-bugs-return-628287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11518 invoked by alias); 8 Jan 2019 12:26:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11465 invoked by uid 48); 8 Jan 2019 12:26:19 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 12:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-CYEhAfIhtj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01096.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #5 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Indeed, things are more complicated. With a slim build of our software I don't
get the error, but only if we link the external library LCIO. This can be
downloaded from here: https://github.com/iLCSoft/LCIO/archive/v02-12-01.tar.gz
This is built in a build directory with
cmake .. -DCMAKE_INSTALL_PREFIX=<location> -DCMAKE_C_COMPILER=<gcc>
-DCMAKE_CXX_COMPILER=<gnu g++>
and then make, make test, make install
When building WHIZARD, during configure include --enable-lcio (if liblcio can
be found in directory known to the (DY)LD_LIBRAY_PATH).
>From gcc-bugs-return-628288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:27:07 2019
Return-Path: <gcc-bugs-return-628288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12750 invoked by alias); 8 Jan 2019 12: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 12661 invoked by uid 48); 8 Jan 2019 12:27:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12: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: 7.3.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88739-4-pT3BMSIOZp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01097.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45377
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45377&action=edit
exhaustive testcase
testcase, compile with -DT="unsigned long".
>From gcc-bugs-return-628289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:28:19 2019
Return-Path: <gcc-bugs-return-628289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46010 invoked by alias); 8 Jan 2019 12:28:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43296 invoked by uid 48); 8 Jan 2019 12:28:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88739-4-C56CgBvke5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01098.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45378
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45378&action=edit
script to generate testcase
Script to generate a testcase. The attached was created by
./t.sh 64 > t.c
expanding to __int128_t would be possible with passing 128.
trivial offset zero loads are not exercised.
>From gcc-bugs-return-628290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:29:22 2019
Return-Path: <gcc-bugs-return-628290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51238 invoked by alias); 8 Jan 2019 12:29: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 51155 invoked by uid 48); 8 Jan 2019 12:29:18 -0000
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dongjianqiang2 at huawei 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88739-4-LRSmTFsWjN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01099.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #12 from John Dong <dongjianqiang2 at huawei dot com> ---
Created attachment 45379
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45379&action=edit
temp patch for Bug 88739
I tried to fix this bug with attached patch, but we not sure if BIT_FIELD_REF
((unsigned:30)var, 16, 0) would appear in another situation, unless we can make
sure it will trigger the wrong input when expanding. please advise.
>From gcc-bugs-return-628292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:29:51 2019
Return-Path: <gcc-bugs-return-628292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52762 invoked by alias); 8 Jan 2019 12:29:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52699 invoked by uid 48); 8 Jan 2019 12:29:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88755] ICE in compute_fn_summary, at ipa-fnsummary.c:2513 since r267601
Date: Tue, 08 Jan 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88755-4-34epZSwmoR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01101.txt.bz2
Content-length: 602
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88755
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-08
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
Known to fail| |9.0
>From gcc-bugs-return-628291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:29:33 2019
Return-Path: <gcc-bugs-return-628291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51954 invoked by alias); 8 Jan 2019 12:29: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 51889 invoked by uid 48); 8 Jan 2019 12:29:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88755] New: ICE in compute_fn_summary, at ipa-fnsummary.c:2513 since r267601
Date: Tue, 08 Jan 2019 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 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-88755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01100.txt.bz2
Content-length: 1255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88755
Bug ID: 88755
Summary: ICE in compute_fn_summary, at ipa-fnsummary.c:2513
since r267601
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Following is ICEing:
$ cat /tmp/ice.i
void a(void) {}
$ ./xgcc -B. --param uninlined-function-insns=2000000000 /tmp/ice.i
../../gcc/ipa-fnsummary.c:2037:27: runtime error: signed integer overflow:
2000000000 * 2 cannot be represented in type 'int'
during GIMPLE pass: local-fnsummary
/tmp/ice.i: In function ‘a’:
/tmp/ice.i:1:1: internal compiler error: in compute_fn_summary, at
ipa-fnsummary.c:2513
1 | void a(void) {}
| ^~~~
0x1643f5e compute_fn_summary(cgraph_node*, bool)
../../gcc/ipa-fnsummary.c:2513
0x1643f8b compute_fn_summary_for_current
../../gcc/ipa-fnsummary.c:2523
0x164d2b2 execute
../../gcc/ipa-fnsummary.c:3578
>From gcc-bugs-return-628293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:31:14 2019
Return-Path: <gcc-bugs-return-628293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87587 invoked by alias); 8 Jan 2019 12:31:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85030 invoked by uid 48); 8 Jan 2019 12:31:10 -0000
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dongjianqiang2 at huawei 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-DomXTgjett@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01102.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #13 from John Dong <dongjianqiang2 at huawei dot com> ---
(In reply to John Dong from comment #12)
> Created attachment 45379 [details]
> temp patch for Bug 88739
>
> I tried to fix this bug with attached patch, but we not sure if
> BIT_FIELD_REF ((unsigned:30)var, 16, 0) would appear in another situation,
> unless we can make sure it will trigger the wrong input when expanding.
> please advise.
sorry, unless we can make sure it will not trigger the wrong input when
expanding.
>From gcc-bugs-return-628294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:37:13 2019
Return-Path: <gcc-bugs-return-628294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101996 invoked by alias); 8 Jan 2019 12:37:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101897 invoked by uid 48); 8 Jan 2019 12:37:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88739-4-tBUpkScfQk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01103.txt.bz2
Content-length: 858
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45380
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45380&action=edit
patch
Can folks please test this on aarch64_be (and maybe arm_be as well to cover
the multi-word case aka WORDS_BIG_ENDIAN).
I've commented the BITS_BIG_ENDIAN parts but I think it will be necessary
for aarch64_be/arm_be so you should see the new testcase FAIL.
It should pass on powerpc BE and s390x.
>From gcc-bugs-return-628295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:38:03 2019
Return-Path: <gcc-bugs-return-628295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103119 invoked by alias); 8 Jan 2019 12:38:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103065 invoked by uid 48); 8 Jan 2019 12:37:55 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88755] [9 Regression] ICE in compute_fn_summary, at ipa-fnsummary.c:2513 since r267601
Date: Tue, 08 Jan 2019 12:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88755-4-3iHLGPayBT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01104.txt.bz2
Content-length: 844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88755
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Similarly for:
$ ./xgcc -B. --param uninlined-function-time=200000000000 /tmp/ice.i -c
during GIMPLE pass: local-fnsummary
/tmp/ice.i: In function ‘a’:
/tmp/ice.i:1:1: internal compiler error: in account_size_time, at
ipa-fnsummary.c:179
1 | void a(void) {}
| ^~~~
0x162efd1 ipa_fn_summary::account_size_time(int, sreal, predicate const&,
predicate const&)
../../gcc/ipa-fnsummary.c:179
0x163f41b analyze_function_body
../../gcc/ipa-fnsummary.c:2037
0x1643b51 compute_fn_summary(cgraph_node*, bool)
../../gcc/ipa-fnsummary.c:2495
0x1643f8b compute_fn_summary_for_current
../../gcc/ipa-fnsummary.c:2523
0x164d2b2 execute
../../gcc/ipa-fnsummary.c:3578
>From gcc-bugs-return-628296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:41:08 2019
Return-Path: <gcc-bugs-return-628296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107720 invoked by alias); 8 Jan 2019 12:41: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 107636 invoked by uid 48); 8 Jan 2019 12:41:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-UiNZBkmgln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01105.txt.bz2
Content-length: 361
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
Oh, and with making U.val a same-sized float type one might be able to
test FLOAT_WORDS_BIG_ENDIAN effects (only mmix, pdp11, tilegx and visum
affected).
Not sure about REG_WORDS_BIG_ENDIAN at all (c6x is the only target defining
this).
>From gcc-bugs-return-628297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:43:26 2019
Return-Path: <gcc-bugs-return-628297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112717 invoked by alias); 8 Jan 2019 12:43: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 112604 invoked by uid 48); 8 Jan 2019 12:43:21 -0000
From: "10walls at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Tue, 08 Jan 2019 12:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 10walls 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: cc
Message-ID: <bug-88568-4-z3r4RZrNwg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01106.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
jon_y <10walls at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |10walls at gmail dot com
--- Comment #6 from jon_y <10walls at gmail dot com> ---
Test case seems to be working for me. What else should I test?
>From gcc-bugs-return-628298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:54:56 2019
Return-Path: <gcc-bugs-return-628298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28967 invoked by alias); 8 Jan 2019 12:54:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28835 invoked by uid 48); 8 Jan 2019 12:54:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Tue, 08 Jan 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88568-4-Mes7FZ6aNt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01107.txt.bz2
Content-length: 404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The testcase I've checked in the cross-compiler too, I was more interested in
knowing whether the compiler with the patch still bootstraps and doesn't
regress against unpatched gcc in the testsuite, which is something I can't test
easily without some emulator or access to the OS.
>From gcc-bugs-return-628299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 12:58:15 2019
Return-Path: <gcc-bugs-return-628299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34272 invoked by alias); 8 Jan 2019 12:58:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34023 invoked by uid 48); 8 Jan 2019 12:58:10 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 12:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-HouCkck99V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01108.txt.bz2
Content-length: 1397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #16 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #8)
> So I think part of a fix would be the following. Not sure if
> REG_WORDS_BIG_ENDIAN or FLOAT_WORDS_BIG_ENDIAN come into play.
> With the fix we no longer simplify this for aarch64 since
> BITS_BIG_ENDIAN is 0 even in BE mode.
A conservative fix to only do this for little endian would be fine given one
shouldn't really do this kind of low-level hacking frequently. I guess
FLOAT_WORDS_BIG_ENDIAN will matter too since you could store a double and read
back part of it as a bitfield (or store a __int128 bitfield and read a double
back). No idea why it would use BITS_BIG_ENDIAN
> That is, not sure if BIT_FIELD_REF <_2, 16, 14> would be correct as suggested
> for aarch64_be because of that BITS_BIG_ENDIAN setting.
Possibly - but then <_2, 16, 0> doing a right shift by 16 would be an incorrect
expansion for big-endian. So something is wrong there...
I think we need to simplify the many BIG_ENDIAN macros so it is feasible to get
big-endian to work reliably on all targets. There seem to be far too many
options which affect too many unrelated things. Big-endian is fundamentally
about memory byte ordering, so allowing to different byte/bit orderings in
registers just makes things overly complex without any benefit.
>From gcc-bugs-return-628300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:06:27 2019
Return-Path: <gcc-bugs-return-628300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51535 invoked by alias); 8 Jan 2019 13:06:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51383 invoked by uid 55); 8 Jan 2019 13:06:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86554] [7/8/9 Regression] Incorrect code generation with signed/unsigned comparison
Date: Tue, 08 Jan 2019 13:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86554-4-IKuaOITK0w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01109.txt.bz2
Content-length: 917
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86554
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 8 13:05:47 2019
New Revision: 267725
URL: https://gcc.gnu.org/viewcvs?rev=267725&root=gcc&view=rev
Log:
2019-01-08 Richard Biener <rguenther@suse.de>
PR tree-optimization/86554
* tree-ssa-sccvn.c (eliminate_dom_walker, rpo_elim,
rpo_avail): Move earlier.
(visit_nary_op): When value-numbering to expressions
with different overflow behavior make sure there's an
available expression on the path.
* gcc.dg/torture/pr86554-1.c: New testcase.
* gcc.dg/torture/pr86554-2.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr86554-1.c
trunk/gcc/testsuite/gcc.dg/torture/pr86554-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-sccvn.c
>From gcc-bugs-return-628302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:07:45 2019
Return-Path: <gcc-bugs-return-628302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53801 invoked by alias); 8 Jan 2019 13:07:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53724 invoked by uid 48); 8 Jan 2019 13:07:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86554] [7/8 Regression] Incorrect code generation with signed/unsigned comparison
Date: Tue, 08 Jan 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-86554-4-uUqWkVwfA5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86554-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86554-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01111.txt.bz2
Content-length: 769
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86554
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |9.0
Summary|[7/8/9 Regression] |[7/8 Regression] Incorrect
|Incorrect code generation |code generation with
|with signed/unsigned |signed/unsigned comparison
|comparison |
Known to fail|9.0 |
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed for trunk. Branches need something different (disabling the offending
path).
>From gcc-bugs-return-628301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:07:21 2019
Return-Path: <gcc-bugs-return-628301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52902 invoked by alias); 8 Jan 2019 13:07:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52836 invoked by uid 55); 8 Jan 2019 13:07:16 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-7prNErMRD3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01110.txt.bz2
Content-length: 762
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #17 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 8 Jan 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
>
> --- Comment #16 from Wilco <wilco at gcc dot gnu.org> ---
> I think we need to simplify the many BIG_ENDIAN macros so it is feasible to get
> big-endian to work reliably on all targets. There seem to be far too many
> options which affect too many unrelated things. Big-endian is fundamentally
> about memory byte ordering, so allowing to different byte/bit orderings in
> registers just makes things overly complex without any benefit.
It's unfortunately not the compiler writers choice but the CPU designers.
>From gcc-bugs-return-628303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:08:57 2019
Return-Path: <gcc-bugs-return-628303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56274 invoked by alias); 8 Jan 2019 13:08:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56114 invoked by uid 48); 8 Jan 2019 13:08:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88755] [9 Regression] ICE in compute_fn_summary, at ipa-fnsummary.c:2513 since r267601
Date: Tue, 08 Jan 2019 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88755-4-W85CAvTsvC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01112.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88755
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-628304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:25:57 2019
Return-Path: <gcc-bugs-return-628304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118463 invoked by alias); 8 Jan 2019 13:25:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118405 invoked by uid 55); 8 Jan 2019 13:25:51 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88066] [7/8/9 Regression] Relative includes in bits/locale_conv.h should be prefixed
Date: Tue, 08 Jan 2019 13:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88066-4-NmCnyH4JQg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88066-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88066-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01113.txt.bz2
Content-length: 1104
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88066
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jan 8 13:25:19 2019
New Revision: 267726
URL: https://gcc.gnu.org/viewcvs?rev=267726&root=gcc&view=rev
Log:
PR libstdc++/88066 use <> for includes not ""
Using #include "..." to include a header in the same directory fails if
the user compiles with -I-, so always use something like <bits/...> for
internal headers.
I haven't added tests for this, because dg-options adds options to the
end, and the position of -I- matters (if it's at the end then the tests
won't find any headers in the build tree, as they're specified by -I
options earlier in the flags). It's been manually tested though.
PR libstdc++/88066
* include/bits/locale_conv.h: Use <> for includes not "".
* include/ext/random: Likewise.
* include/ext/vstring.h: Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/locale_conv.h
trunk/libstdc++-v3/include/ext/random
trunk/libstdc++-v3/include/ext/vstring.h
>From gcc-bugs-return-628305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:26:34 2019
Return-Path: <gcc-bugs-return-628305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119922 invoked by alias); 8 Jan 2019 13:26: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 119524 invoked by uid 48); 8 Jan 2019 13:26:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88066] [7/8 Regression] Relative includes in bits/locale_conv.h should be prefixed
Date: Tue, 08 Jan 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88066-4-MXxed52Mj0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88066-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88066-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01114.txt.bz2
Content-length: 622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88066
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8/9 Regression] Relative |[7/8 Regression] Relative
|includes in |includes in
|bits/locale_conv.h should |bits/locale_conv.h should
|be prefixed |be prefixed
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk for now, backports to follow.
>From gcc-bugs-return-628306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:40:30 2019
Return-Path: <gcc-bugs-return-628306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37390 invoked by alias); 8 Jan 2019 13:40:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37257 invoked by uid 48); 8 Jan 2019 13:40:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/47896] wrong code with -O -fno-early-inlining -fipa-pta -fno-tree-dominator-opts -fno-tree-forwprop
Date: Tue, 08 Jan 2019 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work resolution
Message-ID: <bug-47896-4-hRa0vOrvQ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47896-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47896-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01115.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47896
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Known to work| |4.7.0
Resolution|--- |FIXED
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think I fixed this a long time ago. The testcase stopped failing with 4.7.0.
>From gcc-bugs-return-628307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:40:31 2019
Return-Path: <gcc-bugs-return-628307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37398 invoked by alias); 8 Jan 2019 13:40:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37297 invoked by uid 48); 8 Jan 2019 13:40:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48620] many libstdc++ tests FAIL with -m32 -fno-early-inlining -fipa-pta
Date: Tue, 08 Jan 2019 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-48620-4-lXNBVSvYeb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01116.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48620
Bug 48620 depends on bug 47896, which changed state.
Bug 47896 Summary: wrong code with -O -fno-early-inlining -fipa-pta -fno-tree-dominator-opts -fno-tree-forwprop
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47896
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:45:51 2019
Return-Path: <gcc-bugs-return-628308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44329 invoked by alias); 8 Jan 2019 13:45:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54863 invoked by uid 48); 8 Jan 2019 13:45:22 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/55752] __builtin_ia32_ldmxcsr / __builtin_ia32_stmxcsr are not scheduling barriers
Date: Tue, 08 Jan 2019 13:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to
Message-ID: <bug-55752-4-G80kINvw7T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01117.txt.bz2
Content-length: 768
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55752
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Last reconfirmed|2012-12-20 00:00:00 |2019-1-8
Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Reconfirmed with trunk, not working on it. As explained that GIMPLE doesn't
re-order things is pure luck, fixing TER to retain that luck doesn't make much
sense.
On GIMPLE the only scheduling barriers we have are implemented via CFG
bits (abnormal edges).
>From gcc-bugs-return-628310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:55:51 2019
Return-Path: <gcc-bugs-return-628310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48629 invoked by alias); 8 Jan 2019 13:55: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 48563 invoked by uid 48); 8 Jan 2019 13:55:46 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88756] New: [nvptx, openacc] Override too many num_workers in nvptx plugin, instead of erroring out
Date: Tue, 08 Jan 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01119.txt.bz2
Content-length: 4434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88756
Bug ID: 88756
Summary: [nvptx, openacc] Override too many num_workers in
nvptx plugin, instead of erroring out
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
Consider this minimized/modified test-case:
...
$ cat libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-1.c
/* { dg-do run } */
#include <stdlib.h>
const int nw = 64;
int
main (void)
{
const int n = 10;
int i;
int array[n];
for (i = 0; i < n; i++)
array[i] = i + 1;
{
int res, vres;
res = 0;
#pragma acc parallel num_workers (nw) copy (res)
#pragma acc loop worker reduction (+:res)
for (i = 0; i < n; i++)
res = res + array[i];
vres = 0;
for (i = 0; i < n; i++)
vres = vres + array[i];
if (res != vres)
abort ();
}
return 0;
}
...
When compiling with c.exp, we have:
...
PASS: libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-1.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O0 (test for excess errors)
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/reduction-1.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O0 execution test
...
while with c++.exp, we have:
...
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/reduction-1.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O0 (test for excess errors)
PASS: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/reduction-1.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O0 execution test
...
Looking first at c++, the c++ front-end delivers a hard-coded constant for
num_workers:
...
$ grep parallel reduction-1.c.004t.original
#pragma acc parallel map(tofrom:res) num_workers(64)
...
and the num_workers constant is then overridden in the compiler to 32:
...
In function 'main._omp_fn.0':
libgomp.oacc-c-c++-common/reduction-1.c:21:13: warning: using num_workers (32),
ignoring 64
$ grep FUNC_MAP reduction-1.s
//:FUNC_MAP "main$_omp_fn$0", 0x1, 0x20, 0x20
...
OTOH, the c frontend delivers a variable for num_workers (only at -O0,
otherwise it'll do the same as the c++ front-end):
...
$ grep parallel reduction-1.c.004t.original
#pragma acc parallel map(tofrom:res) num_workers(nw)
...
which cannot be overridden in the compiler (meaning, in
nvptx_goacc_validate_dims), given that it's value isn't known:
...
$ grep FUNC_MAP reduction-1.s
//:FUNC_MAP "main$_omp_fn$0", 0x1, 0, 0x20
...
and at runtime we run into a GOMP_PLUGIN_fatal in the libgomp nvptx plugin:
...
libgomp: The Nvidia accelerator has insufficient resources to launch
'main$_omp_fn$0' with num_workers = 64; recompile the program with 'num_workers
= 32' on that offloaded region or '-fopenacc-dim=:32'
...
For the user, it's somewhat confusing that this passes with warning when
compiling as C++, and fails to execute when compiling as C.
The difference originates in the front-ends, but that doesn't seem to be
openacc-specific, so while it looks possible to fix in the C frontend
(basically , make c_fully_fold_internal apply to launch dims even for
!optimize), I'm not sure that's a good and acceptable idea.
[ And, given this difference, it's probably good to test this behaviour in a
dedicated test-case, but otherwise avoid const int for dimension settings in
libgomp.oacc-c-c++-common test-case, which are tested for both C and C++. At
first glance, this would mean fixing
libgomp.oacc-c-c++-common/reduction-[1-5].c . ]
OTOH, we can also look at the consequences of the front-end difference, which
are either:
- an override in the compiler, or
- a failure at runtime.
[ In other words, we can abstract away from the const int handling, and
conclude that we see the same difference for:
...
int nw = 64;
#pragma acc parallel num_workers (nw) copy (res)
...
and
...
#pragma acc parallel num_workers (64) copy (res)
...
]
While it's clear that in the compiler (that is, in nvptx_goacc_validate_dims)
we can't do better, I wonder why we don't do the same in the plugin, that is,
override with warning.
We would have the more acceptable difference of "compile with warning and run"
vs "compile and run with warning".
>From gcc-bugs-return-628309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 13:55:06 2019
Return-Path: <gcc-bugs-return-628309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47346 invoked by alias); 8 Jan 2019 13:55:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47009 invoked by uid 48); 8 Jan 2019 13:55:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/57359] store motion causes wrong code for union access at -O3
Date: Tue, 08 Jan 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_reconfirmed_on short_desc
Message-ID: <bug-57359-4-ZhMknqa26j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57359-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57359-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01118.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57359
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |alias
Last reconfirmed|2013-05-31 00:00:00 |2019-1-8
Summary|wrong code for union access |store motion causes wrong
|at -O3 on x86_64-linux |code for union access at
| |-O3
--- Comment #16 from Richard Biener <rguenth at gcc dot gnu.org> ---
Re-confirmed. Not really working on this - all other compilers make the same
"mistake". Cost of "fixing" is quite high (peeling one iteration).
>From gcc-bugs-return-628311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:01:33 2019
Return-Path: <gcc-bugs-return-628311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72537 invoked by alias); 8 Jan 2019 14: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 72489 invoked by uid 48); 8 Jan 2019 14:01:28 -0000
From: "d25fe0be at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] New: GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Tue, 08 Jan 2019 14:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: d25fe0be at outlook 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-88757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01120.txt.bz2
Content-length: 1071
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88757
Bug ID: 88757
Summary: GCC wrongly treats dependent name as a type when it
should be treated as a value
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: d25fe0be at outlook dot com
Target Milestone: ---
GCC complains "error: no declaration matches 'int C<T>::x(typename
S<T>::size)'"
when compiling the following snippet:
```
template <class T> struct C {
static int x;
};
template <class U> struct S {
static const int size = 1;
};
template <class T> int C<T>::x(S<T>::size); // Here `S<T>::size` is treated as
a type.
```
GCC 8.2 / clang 7 does not exhibit this behavior.
Live example (GCC 9): https://wandbox.org/permlink/ob29FV2EK6Ie4wfY
Live example (GCC 8): https://wandbox.org/permlink/3hdIXnu8zn1QkYGP
Live example (clang 7): https://wandbox.org/permlink/m0zsTUKWIK3VjfHn
>From gcc-bugs-return-628312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:09:12 2019
Return-Path: <gcc-bugs-return-628312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87789 invoked by alias); 8 Jan 2019 14:09: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 87687 invoked by uid 48); 8 Jan 2019 14:09:07 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 08 Jan 2019 14:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-Jpw1uwkgII@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01121.txt.bz2
Content-length: 1576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #15 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #14)
> On Mon, 7 Jan 2019, wilco at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
> >
> > --- Comment #13 from Wilco <wilco at gcc dot gnu.org> ---
> > So to add some real numbers to the discussion, the average number of iterations
> > is 4.31. Frequency stats (16 includes all iterations > 16 too):
> >
> > 1: 29.0
> > 2: 4.2
> > 3: 1.0
> > 4: 36.7
> > 5: 8.7
> > 6: 3.4
> > 7: 3.0
> > 8: 2.6
> > 9: 2.1
> > 10: 1.9
> > 11: 1.6
> > 12: 1.2
> > 13: 0.9
> > 14: 0.8
> > 15: 0.7
> > 16: 2.1
> >
> > So unrolling 4x is perfect for this loop. Note the official xz version has
> > optimized this loop since 2014(!) using unaligned accesses:
> > https://git.tukaani.org/?p=xz.git;a=blob;f=src/liblzma/common/memcmplen.h
>
> I guess if we'd have some data to guide then classical unrolling using
> duffs device would be best here? Because peeling will increase the
> number of dynamic branches and likely the actual distribution of
> #iterations isn't so that they will be well predicted?
Duff's device is very slow on any CPU with branch prediction. It can't be used
here given you don't know the number of iterations in advance (only the
maximum).
Unrolling reduces the number of branches given the loop branch is only taken
once every N iterations. The loop overhead is significant here: 3 out of 7
instructions, with 4x unrolling that reduces to 3 in 19.
>From gcc-bugs-return-628313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:13:20 2019
Return-Path: <gcc-bugs-return-628313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102661 invoked by alias); 8 Jan 2019 14:13: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 98969 invoked by uid 48); 8 Jan 2019 14:13:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65425] code optimization leads to spurious FP exception
Date: Tue, 08 Jan 2019 14:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-65425-4-84oGTmE6pJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65425-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01122.txt.bz2
Content-length: 1794
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65425
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2015-03-18 00:00:00 |2019-1-8
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Reconfirmed. Now needs -ftree-loop-if-convert (which also makes it fail ontop
of -O[12]).
As said, not sure what to do - __builtin_log10 (and others) are const nothrow
with -fno-math-errno -ftrapping-math. if_convertible_stmt_p does
case GIMPLE_CALL:
{
tree fndecl = gimple_call_fndecl (stmt);
if (fndecl)
{
int flags = gimple_call_flags (stmt);
if ((flags & ECF_CONST)
&& !(flags & ECF_LOOPING_CONST_OR_PURE)
/* We can only vectorize some builtins at the moment,
so restrict if-conversion to those. */
&& fndecl_built_in_p (fndecl))
return true;
}
return false;
which fails to consider externally throwing stmts (internal throws would
be rejected by other means). But 'nothrow' doesn't go away with
-ftrapping-math (which is also the default btw). logN(0) is documented
to raise FE_DIVBYZERO.
One possibility here is to simply check flag_trapping_math but then
even functions like sin() would be flagged.
Joseph? How would you arrange things so that those builtin calls are
flagged as possibly trapping (rather than throwing)? We could add
a built_in_could_trap_p helper, explicitely spelling out things.
I think there's no function attribute glibc could place on a
function to say it won't ever trap? (even sin() is documented to
trap on +-Inf)
>From gcc-bugs-return-628314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:19:22 2019
Return-Path: <gcc-bugs-return-628314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51304 invoked by alias); 8 Jan 2019 14:19:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51202 invoked by uid 55); 8 Jan 2019 14:19:14 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 08 Jan 2019 14:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
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-88398-4-JeCFNafGBy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01123.txt.bz2
Content-length: 2567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #16 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 8 Jan 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
>
> --- Comment #15 from Wilco <wilco at gcc dot gnu.org> ---
> (In reply to rguenther@suse.de from comment #14)
> > On Mon, 7 Jan 2019, wilco at gcc dot gnu.org wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
> > >
> > > --- Comment #13 from Wilco <wilco at gcc dot gnu.org> ---
> > > So to add some real numbers to the discussion, the average number of iterations
> > > is 4.31. Frequency stats (16 includes all iterations > 16 too):
> > >
> > > 1: 29.0
> > > 2: 4.2
> > > 3: 1.0
> > > 4: 36.7
> > > 5: 8.7
> > > 6: 3.4
> > > 7: 3.0
> > > 8: 2.6
> > > 9: 2.1
> > > 10: 1.9
> > > 11: 1.6
> > > 12: 1.2
> > > 13: 0.9
> > > 14: 0.8
> > > 15: 0.7
> > > 16: 2.1
> > >
> > > So unrolling 4x is perfect for this loop. Note the official xz version has
> > > optimized this loop since 2014(!) using unaligned accesses:
> > > https://git.tukaani.org/?p=xz.git;a=blob;f=src/liblzma/common/memcmplen.h
> >
> > I guess if we'd have some data to guide then classical unrolling using
> > duffs device would be best here? Because peeling will increase the
> > number of dynamic branches and likely the actual distribution of
> > #iterations isn't so that they will be well predicted?
>
> Duff's device is very slow on any CPU with branch prediction. It can't be used
> here given you don't know the number of iterations in advance (only the
> maximum).
>
> Unrolling reduces the number of branches given the loop branch is only taken
> once every N iterations. The loop overhead is significant here: 3 out of 7
> instructions, with 4x unrolling that reduces to 3 in 19.
But you can't elide the checks in the peeled copies and for 4-times
unrolling you have most cases exiting on the first or fourth check.
Duffs device simply merges the prologue iterations for unrolling
with the loop body so I don't see why it can't be used. It's
switch (n % 4)
{
loop:
iter
n--;
case 3:
iter
n--;
case 2:
iter
n--
case 1:
iter
n--;
case 0:
if (n != 0)
goto loop;
}
it's cost is mainly the computed jump into the loop body. Then
you have a four-fold reduction in branches without the overhead
of having another three loop body copies in the prologue with
retained early exit checks.
>From gcc-bugs-return-628315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:21:03 2019
Return-Path: <gcc-bugs-return-628315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60752 invoked by alias); 8 Jan 2019 14:21: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 57840 invoked by uid 48); 8 Jan 2019 14:20:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] [9 Regression] GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Tue, 08 Jan 2019 14:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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: keywords target_milestone short_desc
Message-ID: <bug-88757-4-HcYMIq7lde@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01124.txt.bz2
Content-length: 648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88757
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Target Milestone|--- |9.0
Summary|GCC wrongly treats |[9 Regression] GCC wrongly
|dependent name as a type |treats dependent name as a
|when it should be treated |type when it should be
|as a value |treated as a value
>From gcc-bugs-return-628316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:31:14 2019
Return-Path: <gcc-bugs-return-628316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119638 invoked by alias); 8 Jan 2019 14:31: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 98040 invoked by uid 48); 8 Jan 2019 14:30:57 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 08 Jan 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-Nxr6aqL3SO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01125.txt.bz2
Content-length: 1310
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #17 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #16)
> But you can't elide the checks in the peeled copies and for 4-times
> unrolling you have most cases exiting on the first or fourth check.
See comment #8 for an example how it should be unrolled (it needs a simple
check at entry and a trailing loop as well of course).
> Duffs device simply merges the prologue iterations for unrolling
> with the loop body so I don't see why it can't be used. It's
>
> switch (n % 4)
> {
> loop:
> iter
> n--;
> case 3:
> iter
> n--;
> case 2:
> iter
> n--
> case 1:
> iter
> n--;
> case 0:
> if (n != 0)
> goto loop;
> }
>
> it's cost is mainly the computed jump into the loop body. Then
> you have a four-fold reduction in branches without the overhead
> of having another three loop body copies in the prologue with
> retained early exit checks.
Duff's device is a bad idea given it adds extra checks and dependencies that
aren't necessary if you unroll properly. There is never a need to merge the
trailing loop into the unrolled copy, and neither should we peel off 3
iterations for no gain.
>From gcc-bugs-return-628317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:46:45 2019
Return-Path: <gcc-bugs-return-628317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29512 invoked by alias); 8 Jan 2019 14:46: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 25946 invoked by uid 55); 8 Jan 2019 14:46:38 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] [9 Regression] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88753-4-74mjeC49tz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01126.txt.bz2
Content-length: 909
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Tue Jan 8 14:45:28 2019
New Revision: 267728
URL: https://gcc.gnu.org/viewcvs?rev=267728&root=gcc&view=rev
Log:
Use proper type in linear transformation in tree-switch-conversion (PR
tree-optimization/88753).
2019-01-08 Martin Liska <mliska@suse.cz>
PR tree-optimization/88753
* tree-switch-conversion.c (switch_conversion::build_one_array):
Come up with local variable constructor. Convert first to
type of constructor values.
2019-01-08 Martin Liska <mliska@suse.cz>
PR tree-optimization/88753
* gcc.dg/tree-ssa/pr88753.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr88753.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-switch-conversion.c
>From gcc-bugs-return-628318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:47:15 2019
Return-Path: <gcc-bugs-return-628318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34808 invoked by alias); 8 Jan 2019 14:47:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34744 invoked by uid 48); 8 Jan 2019 14:47:11 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88753] [9 Regression] Wrong code since r265463 in tree switch conversion
Date: Tue, 08 Jan 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88753-4-bgQGRGR7Th@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88753-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01127.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88753
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:48:53 2019
Return-Path: <gcc-bugs-return-628319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36894 invoked by alias); 8 Jan 2019 14:48:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36818 invoked by uid 48); 8 Jan 2019 14:48:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 08 Jan 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-k5tEy0RmyP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01128.txt.bz2
Content-length: 816
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The duffs device doesn't need to be done with computed jump, it can be done
with 3 conditional branches + 3 comparisons too. The advantage of doing that
is especially if the iter isn't really very small, by doing it that way you
don't need those 4 unrolled iterations + one scalar loop.
if (n & 2)
{
if (n & 1) { n++; goto loop3; }
{ n += 2; goto loop2; }
}
else if (n & 1)
{ n += 3; goto loop1; }
else if (n == 0)
goto end;
do
{
iter;
loop3:
iter;
loop2:
iter;
loop1:
iter;
n -= 4;
}
while (n != 0);
end:;
Of course, if iter is very short, it might be easier/more efficient to
duplicate iter more times than 4 and do something else.
>From gcc-bugs-return-628320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:50:46 2019
Return-Path: <gcc-bugs-return-628320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39170 invoked by alias); 8 Jan 2019 14:50: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 39077 invoked by uid 48); 8 Jan 2019 14:50:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Tue, 08 Jan 2019 14:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
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: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-SwlNRuCWpm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01129.txt.bz2
Content-length: 317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd check what would they say about upstream change and if they are strongly
against, make a local change. Even when clang++ is used with libstdc++ the
default is still strcmp, dunno about libc++.
>From gcc-bugs-return-628321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:51:55 2019
Return-Path: <gcc-bugs-return-628321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40337 invoked by alias); 8 Jan 2019 14:51:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40294 invoked by uid 48); 8 Jan 2019 14:51:49 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] New: [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Tue, 08 Jan 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01130.txt.bz2
Content-length: 2879
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Bug ID: 88758
Summary: [9 Regression] 186.crafty in SPEC CPU 2000 failed to
build
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
On x86-64, r267673 gave
$ gcc -O3 -funroll-loops -ffast-math -fwhole-program -flto=jobserver
-fuse-linker-plugin -DSPEC_CPU2000_LP64 searchr.o search.o repeat.o next.o
nextr.o history.o nexte.o quiesce.o evaluate.o movgen.o make.o unmake.o
lookup.o store.o attacks.o swap.o boolean.o draw.o utility.o valid.o drawn.o
edit.o enprise.o init.o input.o interupt.o iterate.o main.o option.o output.o
phase.o ponder.o preeval.o root.o setboard.o time.o validate.o -lm -o crafty
...
during GIMPLE pass: dom
preeval.c: In function 'PreEvaluate':
preeval.c:21:6: internal compiler error: Segmentation fault
21 | void PreEvaluate(int wtm)
| ^
0xc0d39f crash_signal
../../src-trunk/gcc/toplev.c:326
0xe93f77 location_wrapper_p(tree_node const*)
../../src-trunk/gcc/tree.h:3807
0xe93f77 tree_strip_any_location_wrapper(tree_node*)
../../src-trunk/gcc/tree.h:3819
0xe93f77 initializer_each_zero_or_onep(tree_node const*)
../../src-trunk/gcc/tree.c:11239
0xe94064 initializer_each_zero_or_onep(tree_node const*)
../../src-trunk/gcc/tree.c:11259
0x105d9f7 gimple_simplify_MULT_EXPR
/export/gnu/import/git/gcc-test-spec-lto/bld/gcc/gimple-match.c:47953
0xf7f84b gimple_simplify
/export/gnu/import/git/gcc-test-spec-lto/bld/gcc/gimple-match.c:90161
0xf8104c gimple_resimplify2(gimple**, gimple_match_op*, tree_node*
(*)(tree_node*))
../../src-trunk/gcc/gimple-match-head.c:285
0x1097862 gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node*
(*)(tree_node*), tree_node* (*)(tree_node*))
../../src-trunk/gcc/gimple-match-head.c:895
0x98c012 fold_stmt_1
../../src-trunk/gcc/gimple-fold.c:4934
0xd19df0 dom_opt_dom_walker::optimize_stmt(basic_block_def*,
gimple_stmt_iterator)
../../src-trunk/gcc/tree-ssa-dom.c:1967
0xd1b2c4 dom_opt_dom_walker::before_dom_children(basic_block_def*)
../../src-trunk/gcc/tree-ssa-dom.c:1468
0x13c4212 dom_walker::walk(basic_block_def*)
../../src-trunk/gcc/domwalk.c:353
0xd1c0ba execute
../../src-trunk/gcc/tree-ssa-dom.c:706
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
make[4]: *** [/tmp/cc6xP93L.mk:2: /tmp/crafty.qcool9.ltrans0.ltrans.o] Error 1
make[4]: *** Waiting for unfinished jobs....
r267631 is OK.
>From gcc-bugs-return-628322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:55:20 2019
Return-Path: <gcc-bugs-return-628322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50951 invoked by alias); 8 Jan 2019 14: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 48638 invoked by uid 48); 8 Jan 2019 14:55:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Tue, 08 Jan 2019 14:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88587-4-iIFmKpuv2M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01131.txt.bz2
Content-length: 833
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Jakub, Richard: So if I understand that correctly, the problem is that a vector
type has called 'layout_type' for somewhere in C FE. That includes setting
TYPE_MODE of the type.
Later then in IPA, we create a clone (multiple_target) and tree inliner inlines
body into nealy create target_clone. However one would need to reset layout for
the type and the copies variable.
Is it something we do somewhere in vectorizer, simd-clone, .. ?
>From gcc-bugs-return-628323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 14:56:21 2019
Return-Path: <gcc-bugs-return-628323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52165 invoked by alias); 8 Jan 2019 14:56:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52117 invoked by uid 48); 8 Jan 2019 14:56:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] [9 Regression] GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Tue, 08 Jan 2019 14:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88757-4-xO2A7KubR5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01132.txt.bz2
Content-length: 708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88757
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |jakub at gcc dot gnu.org,
| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
You forgot to say that with -std=c++2a only.
This started to be rejected with r266710.
>From gcc-bugs-return-628324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:02:47 2019
Return-Path: <gcc-bugs-return-628324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14691 invoked by alias); 8 Jan 2019 15:02:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12951 invoked by uid 48); 8 Jan 2019 15:02:42 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] [9 Regression] GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Tue, 08 Jan 2019 15: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: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88757-4-AYNUEMtajV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01133.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88757
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
>From gcc-bugs-return-628325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:09:13 2019
Return-Path: <gcc-bugs-return-628325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38987 invoked by alias); 8 Jan 2019 15:09: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 38904 invoked by uid 48); 8 Jan 2019 15:09:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Tue, 08 Jan 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-Uoy6MTOPoX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01134.txt.bz2
Content-length: 1003
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think the problem is that while we make TYPE_MODE something dynamic for
vector types (which takes into account whether the current function supports in
hw such vectors or not):
#define TYPE_MODE(NODE) \
(VECTOR_TYPE_P (TYPE_CHECK (NODE)) \
? vector_type_mode (NODE) : (NODE)->type_common.mode)
we don't do the same thing for DECL_MODE:
/* Holds the machine mode corresponding to the declaration of a variable or
field. Always equal to TYPE_MODE (TREE_TYPE (decl)) except for a
FIELD_DECL. */
#define DECL_MODE(NODE) (DECL_COMMON_CHECK (NODE)->decl_common.mode)
#define SET_DECL_MODE(NODE, MODE) \
(DECL_COMMON_CHECK (NODE)->decl_common.mode = (MODE))
We've run into this several times in the past already. See e.g. PR78643.
It is probably not the right time to change the DECL_MODE macro definition in
stage4, so that leaves us to do some hacks where needed.
>From gcc-bugs-return-628326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:10:25 2019
Return-Path: <gcc-bugs-return-628326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40422 invoked by alias); 8 Jan 2019 15:10: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 40328 invoked by uid 48); 8 Jan 2019 15:10:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Tue, 08 Jan 2019 15:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-N2EuusE7Hq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01135.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or just recompute DECL_MODE on all decls with vector type in the function
during the cloning for a different ISA.
>From gcc-bugs-return-628327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:12:31 2019
Return-Path: <gcc-bugs-return-628327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42682 invoked by alias); 8 Jan 2019 15:12:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42592 invoked by uid 48); 8 Jan 2019 15:12:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Tue, 08 Jan 2019 15:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-Ae0OYNn5QI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01136.txt.bz2
Content-length: 1788
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #6)
> I'd check what would they say about upstream change and if they are strongly
> against, make a local change. Even when clang++ is used with libstdc++ the
> default is still strcmp, dunno about libc++.
I'll prepare patch for it.
Btw. according to git grep:
$ git grep __GXX_MERGED_TYPEINFO_NAMES
gcc/config/arm/symbian.h: builtin_define
("__GXX_MERGED_TYPEINFO_NAMES=0"); \
gcc/config/i386/cygming.h: builtin_define
("__GXX_MERGED_TYPEINFO_NAMES=0"); \
gcc/config/m68k/uclinux.h: builtin_define
("__GXX_MERGED_TYPEINFO_NAMES=0"); \
libstdc++-v3/doc/html/manual/api.html:in <code
class="filename">typeinfo</code>, <code
class="literal">__GXX_MERGED_TYPEINFO_NAMES</code>
libstdc++-v3/doc/xml/manual/evolution.xml:in <filename
class="headerfile">typeinfo</filename>,
<literal>__GXX_MERGED_TYPEINFO_NAMES</literal>
libstdc++-v3/libsupc++/tinfo.cc:#if __GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/tinfo2.cc:#if __GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/typeinfo:// __GXX_MERGED_TYPEINFO_NAMES to 1 or 0 to
indicate whether or not pointer
libstdc++-v3/libsupc++/typeinfo:#ifndef __GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/typeinfo:#define __GXX_MERGED_TYPEINFO_NAMES 0
libstdc++-v3/libsupc++/typeinfo: #if !__GXX_MERGED_TYPEINFO_NAMES
libstdc++-v3/libsupc++/typeinfo:# if !__GXX_MERGED_TYPEINFO_NAMES
There are 3 header files that define __GXX_MERGED_TYPEINFO_NAMES=0 (which is
default): can that be removed?
And as __GXX_MERGED_TYPEINFO_NAMES is default, should I create a patch that
will always use strcmp in libsanitizer?
>From gcc-bugs-return-628329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:16:27 2019
Return-Path: <gcc-bugs-return-628329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47452 invoked by alias); 8 Jan 2019 15:16:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47309 invoked by uid 48); 8 Jan 2019 15:16:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Tue, 08 Jan 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-5hjQkQUfb8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01138.txt.bz2
Content-length: 1437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #5)
> I think the problem is that while we make TYPE_MODE something dynamic for
> vector types (which takes into account whether the current function supports
> in hw such vectors or not):
> #define TYPE_MODE(NODE) \
> (VECTOR_TYPE_P (TYPE_CHECK (NODE)) \
> ? vector_type_mode (NODE) : (NODE)->type_common.mode)
> we don't do the same thing for DECL_MODE:
> /* Holds the machine mode corresponding to the declaration of a variable or
> field. Always equal to TYPE_MODE (TREE_TYPE (decl)) except for a
> FIELD_DECL. */
> #define DECL_MODE(NODE) (DECL_COMMON_CHECK (NODE)->decl_common.mode)
> #define SET_DECL_MODE(NODE, MODE) \
> (DECL_COMMON_CHECK (NODE)->decl_common.mode = (MODE))
> We've run into this several times in the past already. See e.g. PR78643.
>
> It is probably not the right time to change the DECL_MODE macro definition
> in stage4, so that leaves us to do some hacks where needed.
I thought the same in a similar bug but ended up discarding that (I don't
remember enough though to explain why).
I think the canonical way of re-computing DECL_MODE would be to re-layout
decls since that also updates RTL if that was already set. There's
relayout_decl for this which is for example called from omp-simd-clone.c
and the vectorizer.
>From gcc-bugs-return-628330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:16:27 2019
Return-Path: <gcc-bugs-return-628330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47460 invoked by alias); 8 Jan 2019 15:16:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47358 invoked by uid 48); 8 Jan 2019 15:16:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Tue, 08 Jan 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88758-4-ES7UJNljW4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01139.txt.bz2
Content-length: 722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection,
| |needs-reduction
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, I'm bisecting and reducing.
>From gcc-bugs-return-628328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:16:01 2019
Return-Path: <gcc-bugs-return-628328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46555 invoked by alias); 8 Jan 2019 15:16:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46266 invoked by uid 48); 8 Jan 2019 15:15:41 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/87488] hyperlink filenames in diagnostics
Date: Tue, 08 Jan 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87488-4-0CiIp2prVg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87488-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01137.txt.bz2
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87488
--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
I'm unconvinced that doing it for filenames is a good idea (based on the
objections in comment #3), but I think that there could be other good uses
tagging URLs into the output.
For example, a static analysis plugin that emits e.g.:
error: NULL pointer 'p' passed as argument 1 to 'foo' [CWE-690]
might want to tag the "CWE-690" in the message/metadata with the URL
https://cwe.mitre.org/data/definitions/690.html
Similarly, any time we mention a GCC option, perhaps we could provide a URL to
the documentation of that option on the GCC website. (Sadly, most of our
options don't have good URLs)
>From gcc-bugs-return-628331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:18:20 2019
Return-Path: <gcc-bugs-return-628331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50537 invoked by alias); 8 Jan 2019 15:18:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50473 invoked by uid 48); 8 Jan 2019 15:18:16 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Tue, 08 Jan 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-88758-4-G1rm65hVhj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01140.txt.bz2
Content-length: 462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
CC| |rsandifo at gcc dot gnu.org
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r267645.
>From gcc-bugs-return-628332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:19:57 2019
Return-Path: <gcc-bugs-return-628332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52939 invoked by alias); 8 Jan 2019 15:19: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 52855 invoked by uid 48); 8 Jan 2019 15:19:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88701] [9 Regression] Internal compiler error for valid program using compound literal with variably modified type.
Date: Tue, 08 Jan 2019 15:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88701-4-E2YaeUFjIp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88701-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01141.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88701
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:24:59 2019
Return-Path: <gcc-bugs-return-628333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109648 invoked by alias); 8 Jan 2019 15:24:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109005 invoked by uid 48); 8 Jan 2019 15:24:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Tue, 08 Jan 2019 15:24: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.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on cf_known_to_fail
Message-ID: <bug-49330-4-0yfBuHjMvA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01142.txt.bz2
Content-length: 2255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2018-06-04 00:00:00 |2019-1-8
Known to fail| |9.0
--- Comment #18 from Richard Biener <rguenth at gcc dot gnu.org> ---
So for find_base_term to compute sth conservative we'd need to track
RTX_SURELY_NON_POINTER (what RTX is surely _not_ based on a pointer
and thus can be ignored). And when find_base_term ever figures
two bases in say a PLUS it has to conservatively return 0.
I fear the existing REG_POINTER does not help at all. For the testcase
we have
(plus:DI (reg:DI 83 [ d.0_2 ])
(symbol_ref:DI ("y") [flags 0x2] <var_decl 0x7ffff7fefb40 y>))
where reg:DI 83 is not marked with REG_POINTER and find_base_term
doesn't find it to be an alternate base. For the testcase the
offending MEM has a MEM_EXPR and we have proper points-to info.
IMHO the proper solution is to kill base_alias_check or all problematic
cases in find_base_term (binary ops with more than one non-CONST_INT
operand).
And eventually make sure to more properly preserve MEM_EXPRs.
Maybe sth as "simple" as the following which of course fixes the
testcase but will make find_base_term fail on any variable-indexed
thing.
diff --git a/gcc/alias.c b/gcc/alias.c
index 93f53543d12..3a66e10b431 100644
--- a/gcc/alias.c
+++ b/gcc/alias.c
@@ -2009,12 +2009,14 @@ find_base_term (rtx x, vec<std::pair<cselib_val *,
rtx base = find_base_term (tmp1, visited_vals);
if (base != NULL_RTX
&& ((REG_P (tmp1) && REG_POINTER (tmp1))
- || known_base_value_p (base)))
+ || known_base_value_p (base))
+ && CONST_INT_P (tmp2))
return base;
base = find_base_term (tmp2, visited_vals);
if (base != NULL_RTX
&& ((REG_P (tmp2) && REG_POINTER (tmp2))
- || known_base_value_p (base)))
+ || known_base_value_p (base))
+ && CONST_INT_P (tmp1))
return base;
/* We could not determine which of the two operands was the
>From gcc-bugs-return-628334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:25:53 2019
Return-Path: <gcc-bugs-return-628334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113717 invoked by alias); 8 Jan 2019 15:25: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 113677 invoked by uid 48); 8 Jan 2019 15:25:49 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Tue, 08 Jan 2019 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-88758-4-U8OwxTTA88@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01143.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |8.2.0
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-628335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:35:04 2019
Return-Path: <gcc-bugs-return-628335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4479 invoked by alias); 8 Jan 2019 15:35: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 4359 invoked by uid 48); 8 Jan 2019 15:35:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 08 Jan 2019 15:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88714-4-Y4flnsCsM9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01144.txt.bz2
Content-length: 913
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can you pick one of the smaller object files that differ, and verify if it is a
debug info issue or something else?
Like see if building the corresponding source with stage1 or stage2 compiler
generates an error with -fcompare-debug (+ the flags normally used)?
Or run both stage1 and stage2 compiler with the same options (i.e. remove the
-gtoggle from one of flag sets) and compare if the same assembly is created.
If it is -fcompare-debug issue, can you attach preprocessed source for that +
full xgcc/xg++ etc. command line?
>From gcc-bugs-return-628336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:36:16 2019
Return-Path: <gcc-bugs-return-628336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5959 invoked by alias); 8 Jan 2019 15:36:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5849 invoked by uid 48); 8 Jan 2019 15:36:10 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Tue, 08 Jan 2019 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88758-4-qp7FQRDyCg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01145.txt.bz2
Content-length: 2436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-reduction |
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:
$ cat a.i
void PreEvaluate ();
int main() { PreEvaluate(); }
$ cat b.i
extern int a[];
int b;
void PreEvaluate() {
int c;
b = 0;
for (; b < 8; b++)
a[b] = c * (b > 0 ? b - 1 : 0);
}
$ gcc [ab].i -flto -O3
during GIMPLE pass: dom
a.i: In function ‘main’:
a.i:3:5: internal compiler error: Segmentation fault
3 | int main() { PreEvaluate(); }
| ^
0xc1864f crash_signal
/home/marxin/Programming/gcc/gcc/toplev.c:326
0x7ffff6d8910f ???
/usr/src/debug/glibc-2.27-6.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0xeb6024 location_wrapper_p(tree_node const*)
/home/marxin/Programming/gcc/gcc/tree.h:3807
0xeb6024 tree_strip_any_location_wrapper(tree_node*)
/home/marxin/Programming/gcc/gcc/tree.h:3819
0xeb6024 initializer_each_zero_or_onep(tree_node const*)
/home/marxin/Programming/gcc/gcc/tree.c:11239
0xeb6104 initializer_each_zero_or_onep(tree_node const*)
/home/marxin/Programming/gcc/gcc/tree.c:11259
0x1083e5f gimple_simplify_MULT_EXPR
/dev/shm/objdir/gcc/gimple-match.c:47953
0xfa61ff gimple_simplify
/dev/shm/objdir/gcc/gimple-match.c:90161
0xfa7833 gimple_resimplify2(gimple**, gimple_match_op*, tree_node*
(*)(tree_node*))
/home/marxin/Programming/gcc/gcc/gimple-match-head.c:285
0x10bb06f gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node*
(*)(tree_node*), tree_node* (*)(tree_node*))
/home/marxin/Programming/gcc/gcc/gimple-match-head.c:895
0x98f2a4 fold_stmt_1
/home/marxin/Programming/gcc/gcc/gimple-fold.c:4934
0xd2c406 dom_opt_dom_walker::optimize_stmt(basic_block_def*,
gimple_stmt_iterator)
/home/marxin/Programming/gcc/gcc/tree-ssa-dom.c:1967
0xd2d9cc dom_opt_dom_walker::before_dom_children(basic_block_def*)
/home/marxin/Programming/gcc/gcc/tree-ssa-dom.c:1468
0x13fcf67 dom_walker::walk(basic_block_def*)
/home/marxin/Programming/gcc/gcc/domwalk.c:353
0xd2e83d execute
/home/marxin/Programming/gcc/gcc/tree-ssa-dom.c:706
>From gcc-bugs-return-628337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:36:30 2019
Return-Path: <gcc-bugs-return-628337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6755 invoked by alias); 8 Jan 2019 15:36:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6661 invoked by uid 48); 8 Jan 2019 15:36:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Tue, 08 Jan 2019 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.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: 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 cc
Message-ID: <bug-88678-4-Iv9nfXCdWA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01146.txt.bz2
Content-length: 363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |jakub at gcc dot gnu.org
>From gcc-bugs-return-628338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:47:38 2019
Return-Path: <gcc-bugs-return-628338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32548 invoked by alias); 8 Jan 2019 15:47:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32483 invoked by uid 48); 8 Jan 2019 15:47:31 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88759] New: `decltype(auto)` as return type of abbreviated function template strips cv-qualifications and referenceness
Date: Tue, 08 Jan 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88759-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01147.txt.bz2
Content-length: 1838
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88759
Bug ID: 88759
Summary: `decltype(auto)` as return type of abbreviated
function template strips cv-qualifications and
referenceness
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ensadc at mailnesia dot com
Target Milestone: ---
https://wandbox.org/permlink/hPwFtdVsAd4kIu44
(-fconcepts is required to silent the warning "use of 'auto' in parameter
declaration only available with -fconcepts", but otherwise the default setting
is enough to trigger the error.)
====
decltype(auto) f(auto x) {
return x[0];
}
const int x[] = {0};
extern decltype(f(x)) a;
extern const int& a;
====
prog.cc:8:19: error: conflicting declaration 'const int& a'
8 | extern const int& a;
| ^
prog.cc:7:23: note: previous declaration as 'int a'
7 | extern decltype(f(x)) a;
| ^
====
Originally discovered in
https://stackoverflow.com/questions/54062172/understanding-decltypeauto-difference-in-case-of-template-vs-auto-functions.
I rewrote the code to better illustrate the issue.
`decltype(f(x))` should be `const int&`, but GCC thinks it's `int`.
It seems that `decltype(auto)` is treated the same as `auto` when used as
return type of abbreviated function template.
Changing the abbreviated function template to a regular function template (i.e.
changing `decltype(auto) f(auto x)` to `template<class T> decltype(auto) f(T
x)`) removes the error.
Probably related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69448.
>From gcc-bugs-return-628339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 15:57:19 2019
Return-Path: <gcc-bugs-return-628339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67103 invoked by alias); 8 Jan 2019 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 65103 invoked by uid 55); 8 Jan 2019 15:56:29 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Tue, 08 Jan 2019 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.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-87836-4-WVpycZyUhf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01148.txt.bz2
Content-length: 3393
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #29 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #28 from Gary Mills <gary_mills at fastmail dot fm> ---
> I installed the patch mentioned above to bypass that error. Now, with this
> minimal configuration:
>
> $
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
> --without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as --with-as=/usr/bin/as
>
> I got a successful build. Still, we are not quite at the root cause. This
Good.
> result does suggest that something in the previous configuration caused the
> ICE. Note that /usr/local, the default prefix, does not exist. Also,
> /usr/gcc/7, the desired prefix, does not exist. I'm going to try to
The gcc build is careful to both build the compilers with -static-libgcc
-static-libstdc++ just to avoid unexpected uses of preinstalled gcc
runtime libs. On top of that, LD_LIBRARY_PATH and friends are set
during the build and make check phases to make sure only the freshly
built libs are used. Still, it's certainly safer to use a prefix that
is either empty or nonexistant to avoid interference.
> re-introduce some of the previous configuration to identify what causes the
> ICE. This will take some time, as each build takes about three days. Any
> suggestions about the culprit in the previous configuration will be
> appreciated.
Of the configure options used in Comment #23, CFLAGS= -O3 -mno-app-regs
seems somewhat dubious. You might just be triggering a bug in the
bootstrap gcc 4.9, which IIUC has quite a number of Illumos-specific
patches.
> I do see this error in all six copies of libgcc/config.log:
>
> configure:3471:
> /export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/xgcc
> -B/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/
> -B/usr/local/sparc-sun-solaris2.11/bin/ -B/usr/local/sparc-sun-solaris2.11/lib/
> -isystem /usr/local/sparc-sun-solaris2.11/include -isystem
> /usr/local/sparc-sun-solaris2.11/sys-include -o conftest -g -O2 conftest.c
> >&5
> ld: fatal: file crtp.o: open failed: No such file or directory
> ld: fatal: file crtbegin.o: open failed: No such file or directory
> ld: fatal: file crtend.o: open failed: No such file or directory
> ld: fatal: file processing errors. No output written to conftest
> collect2: error: ld returned 1 exit status
> configure:3474: $? = 1
> configure:3662: checking for suffix of object files
>
> It happens because the configure script ran before the crt*.o files had been
> created. Here's an example of the timestamps:
>
> -rw-r--r-- 1 mills staff 504 Jan 7 05:43 build/sparcv7/gcc/crtp.o
> -rw-r--r-- 1 mills staff 60825 Jan 7 05:38
> build/sparcv7/sparc-sun-solaris2.11/libgcc/config.log
>
> As far as I can tell, a failure of the linker at this point tells the script
> that we are cross-compiling, and bypasses any subsequent tests that require the
> linker. I don't know what effect these assumptions might have.
This is fully expected: since we are before building the crt files, link
tests cannot work, and libgcc/configure is careful to run its tests in a
way that don't require them (e.g. with -nostartfiles -nodefaultlibs).
>From gcc-bugs-return-628340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:01:25 2019
Return-Path: <gcc-bugs-return-628340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91727 invoked by alias); 8 Jan 2019 16:01: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 89156 invoked by uid 48); 8 Jan 2019 16:01:20 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Tue, 08 Jan 2019 16:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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:
Message-ID: <bug-88653-4-t0aEwoeifD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01149.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #18 from Murat Tekeev <mtekeev at yandex dot ru> ---
Unfortunately, I was happy too soon. I made a mistake - with Fortran 7.4 these
files still do not compile. Apparently
I installed the latest version of Cygwin on three different machines, the
installation is fine, but not all files are compiled.
I don't know what the problem is. With gfortran 7.3 no problems.
I will continue to use gfortran 7.3 and wait until the next version of Cygwin
is released.
Apparently, this is some kind of cygwin problem.
>From gcc-bugs-return-628341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:03:13 2019
Return-Path: <gcc-bugs-return-628341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62669 invoked by alias); 8 Jan 2019 16:03:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62586 invoked by uid 48); 8 Jan 2019 16:03:05 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Tue, 08 Jan 2019 16:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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:
Message-ID: <bug-88653-4-WrsnAhwxMD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01150.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #19 from Murat Tekeev <mtekeev at yandex dot ru> ---
Unfortunately, I was happy too soon. I made a mistake - with Fortran 7.4 these
files still do not compile. Apparently
I installed the latest version of Cygwin on three different machines, the
installation is fine, but not all files are compiled.
I don't know what the problem is. With gfortran 7.3 no problems.
I will continue to use gfortran 7.3 and wait until the next version of Cygwin
is released.
Apparently, this is some kind of cygwin problem.
>From gcc-bugs-return-628342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:04:20 2019
Return-Path: <gcc-bugs-return-628342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63812 invoked by alias); 8 Jan 2019 16:04: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 63697 invoked by uid 48); 8 Jan 2019 16:04:09 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Tue, 08 Jan 2019 16:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
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:
Message-ID: <bug-88653-4-6tGHM998YD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01151.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #20 from Murat Tekeev <mtekeev at yandex dot ru> ---
Unfortunately, I was happy too soon. I made a mistake - with Fortran 7.4 these
files still do not compile. Apparently
I installed the latest version of Cygwin on three different machines, the
installation is fine, but not all files are compiled.
I don't know what the problem is. With gfortran 7.3 no problems.
I will continue to use gfortran 7.3 and wait until the next version of Cygwin
is released.
Apparently, this is some kind of cygwin problem.
>From gcc-bugs-return-628343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:07:38 2019
Return-Path: <gcc-bugs-return-628343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69706 invoked by alias); 8 Jan 2019 16:07: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 69646 invoked by uid 48); 8 Jan 2019 16:07:34 -0000
From: "mtekeev at yandex dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Tue, 08 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mtekeev at yandex dot ru
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88653-4-TGE4cxMgFW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01152.txt.bz2
Content-length: 866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Murat Tekeev <mtekeev at yandex dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |NEW
Resolution|WORKSFORME |---
--- Comment #21 from Murat Tekeev <mtekeev at yandex dot ru> ---
Unfortunately, I was happy too soon. I made a mistake - with Fortran 7.4 these
files still do not compile. Apparently
I installed the latest version of Cygwin on three different machines, the
installation is fine, but not all files are compiled.
I don't know what the problem is. With gfortran 7.3 no problems.
I will continue to use gfortran 7.3 and wait until the next version of Cygwin
is released.
Apparently, this is some kind of cygwin problem.
>From gcc-bugs-return-628344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:19:45 2019
Return-Path: <gcc-bugs-return-628344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93592 invoked by alias); 8 Jan 2019 16:19:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93526 invoked by uid 48); 8 Jan 2019 16:19:39 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Tue, 08 Jan 2019 16:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88717-4-UfPxlQH8eO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01153.txt.bz2
Content-length: 851
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to åˆ˜è¢‹é¼ from comment #6)
> (In reply to H.J. Lu from comment #5)
> > (In reply to åˆ˜è¢‹é¼ from comment #4)
> > >
> > > My thought is AVX_U128_DIRTY would be set when ymm/zmm appeared, and
> > > AVX_U128_CLEAN for xmm, AVX_U128_ANY for other situations. This also works
> > > for this case.
> > >
> >
> > Your change touches many difference places. Please do
> >
> > 1. For each line of change, find a testcase to verify that it is needed.
> > 2. Bootstrap GCC with --with-arch=native and all languages. Run the complete
> > GCC testssuites with and without your whole patch.
A simpler patch is posted at
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00415.html
>From gcc-bugs-return-628345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:24:51 2019
Return-Path: <gcc-bugs-return-628345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119705 invoked by alias); 8 Jan 2019 16:24:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119632 invoked by uid 48); 8 Jan 2019 16:24:44 -0000
From: "d25fe0be at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88757] [9 Regression] GCC wrongly treats dependent name as a type when it should be treated as a value
Date: Tue, 08 Jan 2019 16:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: d25fe0be at outlook dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88757-4-UZnX2qOXSH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01154.txt.bz2
Content-length: 173
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88757
--- Comment #2 from d25fe0be@ <d25fe0be at outlook dot com> ---
Oops, I didn't realize this. Thank you for clarifying.
>From gcc-bugs-return-628347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:31:28 2019
Return-Path: <gcc-bugs-return-628347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1490 invoked by alias); 8 Jan 2019 16:31:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 889 invoked by uid 48); 8 Jan 2019 16:30:45 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libbacktrace/88745] Darwin lacks an implementation for libbacktrace
Date: Tue, 08 Jan 2019 16:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libbacktrace
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88745-4-Amu7f1hIqw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88745-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01156.txt.bz2
Content-length: 706
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88745
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
I tried to start doing this in my fork of gdb but I didn't get very far; here's
a brief TODO:
1. Get filetype.awk to recognize mach-o binaries
2. Add a mach-o case to the switch on libbacktrace_cv_sys_filetype in
configure.ac
3. Add a macho.c file to compile to macho.lo to use as the FORMAT_FILE in that
case
>From gcc-bugs-return-628346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:31:27 2019
Return-Path: <gcc-bugs-return-628346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1329 invoked by alias); 8 Jan 2019 16:31: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 925 invoked by uid 48); 8 Jan 2019 16:30:49 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85103] [8/9 Regression] Performance regressions on SPEC with r257582
Date: Tue, 08 Jan 2019 16:31: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85103-4-twA4RNpxGq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01155.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85103
--- Comment #19 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #18)
> which makes it to be inlined. Does it solve the perofmrance problem for both
> benchmarks?
Looking at our nightly spec runs, the bzip2 degradation has indeed been cleaned
up. But it looks like 175.vpr degraded another 2% or so over the last couple
days.
>From gcc-bugs-return-628348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:34:26 2019
Return-Path: <gcc-bugs-return-628348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5803 invoked by alias); 8 Jan 2019 16:34:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5745 invoked by uid 55); 8 Jan 2019 16:34:21 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46495] target.h and function.h require tm.h
Date: Tue, 08 Jan 2019 16:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-46495-4-vuznbtOVXz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46495-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46495-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01157.txt.bz2
Content-length: 993
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46495
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 8 Jan 2019, egallager at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46495
>
> Eric Gallager <egallager at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |egallager at gcc dot gnu.org
>
> --- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
> (In reply to Jorn Wolfgang Rennecke from comment #0)
> > Because of their dependence on CUMULATIVE_ARGS and HARD_REG_SET,
> > target.h and function.h include tm.h This needs to be rectified to stop
> > the uncontrolled use of target macros.
>
> How?
See bug 46500 for the introduction of cumulative_args_t. There's still
HARD_REG_SET to resolve (maybe similarly).
>From gcc-bugs-return-628349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:42:16 2019
Return-Path: <gcc-bugs-return-628349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15775 invoked by alias); 8 Jan 2019 16:42:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14999 invoked by uid 48); 8 Jan 2019 16:42:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88331] [9 Regression] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Tue, 08 Jan 2019 16:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-88331-4-SCFoD1nwin@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01158.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45381
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45381&action=edit
gcc9-pr88331.patch
I don't see how that could ever work when assign_stack_local_1 is called from
anywhere but the expand pass, one can't emit random code somewhere blindly
otherwise (e.g. from the RA). I think for now it is best to revert to previous
behavior when it isn't called during expansion, and if really needed, we can
figure out a way for GCC10 how to tell the RA it should emit the alignment
itself.
>From gcc-bugs-return-628350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:42:18 2019
Return-Path: <gcc-bugs-return-628350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15939 invoked by alias); 8 Jan 2019 16:42: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 15718 invoked by uid 55); 8 Jan 2019 16:42:13 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85103] [8/9 Regression] Performance regressions on SPEC with r257582
Date: Tue, 08 Jan 2019 16:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85103-4-3ClWQ73aNu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85103-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01159.txt.bz2
Content-length: 708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85103
--- Comment #20 from Jan Hubicka <hubicka at ucw dot cz> ---
> Looking at our nightly spec runs, the bzip2 degradation has indeed been cleaned
> up. But it looks like 175.vpr degraded another 2% or so over the last couple
> days.
Knowing what inline decision matters for VPR, I can try to fix it too.
It seems that the time accounting bug I fixed this weekend cured a lot
of mysteries I did not understand. I have one additional patch to
adjust way we compute badness metric which I plan to commit todar or
tomorrow (there was downtime with LNT spec testers). It may affect these
two benchmarks again - I am still waiting for runs to finish.
Honza
>From gcc-bugs-return-628351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 16:47:38 2019
Return-Path: <gcc-bugs-return-628351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127970 invoked by alias); 8 Jan 2019 16:47: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 112597 invoked by uid 55); 8 Jan 2019 16:47:32 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-JUmhUIHIfu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01160.txt.bz2
Content-length: 1950
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #14 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 8 Jan 2019, romain.geissler at amadeus dot com wrote:
> - binutils, with a linker configured to look for system libraries in a
> non-standard folder, empty for now
> - gcc, without libstdc++
The first GCC should be --enable-languages=c --disable-shared
--without-headers --with-newlib (where --with-newlib means "define
inhibit_libc", as required to stop libgcc from needing libc headers in
some cases) - you may need various other --disable- options for other GCC
libraries that can't be built without glibc headers (see the full options
used in glibc's build-many-glibcs.py for a list that is sufficient). In
particular, libstdc++ should not be built until glibc has been built.
> - glibc, using the above binutils/gcc, which fills in the non standard lib
> folder with only a libc.
> - libstdc++, using the above binutils/gcc/glibc.
A second GCC should be built with all languages you want, shared libraries
enabled (in particular, once you've built glibc you can build a proper
shared libgcc with DT_NEEDED pointing correctly to libc, which you can't
until glibc has been built).
It's true that ideally the host-side code in GCC would be built just once
(but libgcc built twice), but that's not currently supported by the GCC
build system.
> Note that this is just the beginning of the bootstrap. After this other
> gcc/libstdc++ are being built, and this time the configure script works
> unpatched.
Two GCC builds suffice with modern (c. 2012 and later; GCC 4.9 and later,
glibc 2.17 and later, roughly) tools. The stripped glibc shared libraries
built with the first GCC using the above process should be identical to
the stripped glibc shared libraries resulting from any longer alternating
series of GCC and glibc builds.
>From gcc-bugs-return-628352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:01:54 2019
Return-Path: <gcc-bugs-return-628352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2400 invoked by alias); 8 Jan 2019 17:01: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 2114 invoked by uid 55); 8 Jan 2019 17:01:43 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/65425] code optimization leads to spurious FP exception
Date: Tue, 08 Jan 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65425-4-NtzFtoVZRA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65425-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01161.txt.bz2
Content-length: 1130
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65425
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
<https://gcc.gnu.org/ml/gcc-patches/2018-10/msg00284.html> has my comments
on ways in which libm functions can be "const/pure with exceptions". It
would be possible to have attributes to describe the ways in which most
libm functions are const apart from rounding mode, exceptions and errno.
I didn't discuss there any possibilities relating to functions raising
some exceptions but not others, or the possible exceptions depending on
-ffinite-math-only. For example, sin can raise inexact and underflow for
finite arguments, as well as invalid for infinite arguments; cos can raise
inexact for finite arguments but not underflow. Most functions can raise
inexact.
(There's also the difference between raising exception flags, which is
what's available when using standard facilities, and actually generating a
signal and calling a signal handler, when using feenableexcept which is a
GNU extension. -ftrapping-math covers both at present.)
>From gcc-bugs-return-628353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:09:11 2019
Return-Path: <gcc-bugs-return-628353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59025 invoked by alias); 8 Jan 2019 17:09: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 58898 invoked by uid 48); 8 Jan 2019 17:09:05 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] New: GCC unrolling is suboptimal
Date: Tue, 08 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01162.txt.bz2
Content-length: 3452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
Bug ID: 88760
Summary: GCC unrolling is suboptimal
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ktkachov at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
One of the hot loops in 510.parest_r from SPEC2017 can be approximated through:
unsigned int *colnums;
double *val;
struct foostruct
{
unsigned int rows;
unsigned int *colnums;
unsigned int *rowstart;
};
struct foostruct *cols;
void
foo (double *dst, const double *src)
{
const unsigned int n_rows = cols->rows;
const double *val_ptr = &val[cols->rowstart[0]];
const unsigned int *colnum_ptr = &cols->colnums[cols->rowstart[0]];
double *dst_ptr = dst;
for (unsigned int row=0; row<n_rows; ++row)
{
double s = 0.;
const double *const val_end_of_row = &val[cols->rowstart[row+1]];
while (val_ptr != val_end_of_row)
s += *val_ptr++ * src[*colnum_ptr++];
*dst_ptr++ = s;
}
}
At -Ofast -mcpu=cortex-a57 on aarch64 GCC generates a tight FMA loop:
.L4:
ldr w3, [x7, x2, lsl 2]
cmp x6, x2
ldr d2, [x5, x2, lsl 3]
add x2, x2, 1
ldr d1, [x1, x3, lsl 3]
fmadd d0, d2, d1, d0
bne .L4
LLVM unrolls the loop more intelligently:
.LBB0_8: // %vector.body
// Parent Loop BB0_2 Depth=1
// => This Inner Loop Header: Depth=2
ldp w21, w22, [x20, #-8]
ldr d5, [x1, x21, lsl #3]
ldp d3, d4, [x7, #-16]
ldr d6, [x1, x22, lsl #3]
ldp w21, w22, [x20], #16
fmadd d2, d6, d4, d2
fmadd d1, d5, d3, d1
ldr d5, [x1, x21, lsl #3]
ldr d6, [x1, x22, lsl #3]
add x5, x5, #4 // =4
adds x19, x19, #2 // =2
ldp d3, d4, [x7], #32
fmadd d1, d5, d3, d1
fmadd d2, d6, d4, d2
b.ne .LBB0_8
With -funroll-loops GCC does do unrolling, but it does it differently:
<snip>
ands x12, x11, 7
beq .L70
cmp x12, 1
beq .L55
cmp x12, 2
beq .L57
cmp x12, 3
beq .L59
cmp x12, 4
beq .L61
cmp x12, 5
beq .L63
cmp x12, 6
bne .L72
.L65:
ldr w14, [x4, x2, lsl 2]
ldr d3, [x3, x2, lsl 3]
add x2, x2, 1
ldr d4, [x1, x14, lsl 3]
fmadd d0, d3, d4, d0
.L63:
ldr w5, [x4, x2, lsl 2]
ldr d5, [x3, x2, lsl 3]
add x2, x2, 1
ldr d6, [x1, x5, lsl 3]
fmadd d0, d5, d6, d0
.L61:
ldr w9, [x4, x2, lsl 2]
ldr d7, [x3, x2, lsl 3]
add x2, x2, 1
ldr d16, [x1, x9, lsl 3]
fmadd d0, d7, d16, d0
<snip>
On the whole of 510.parest_r this makes LLVM about 6% faster than GCC on
Cortex-A57.
Perhaps this can be used as a motivating testcase to move the GCC unrolling
discussions forward?
>From gcc-bugs-return-628354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:26:54 2019
Return-Path: <gcc-bugs-return-628354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86541 invoked by alias); 8 Jan 2019 17:26: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 86472 invoked by uid 48); 8 Jan 2019 17:26:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Tue, 08 Jan 2019 17:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to attachments.created
Message-ID: <bug-88758-4-v4L4uzmC0D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01163.txt.bz2
Content-length: 1578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45382
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45382&action=edit
gcc9-pr88758.patch
Untested fix. Unfortunately, the testcase isn't really usable, because it
fails to link when this ICE is fixed (plus contains uninitialized use).
The problem is that while for non-VECTOR_CST_STEPPED_P VECTOR_CSTs it is just
fine when initializer_each_zero_or_onep checks only the encoded elts, if there
are fewer than subparts, the last one is repeated. But, with
VECTOR_CST_STEPPED_P, the one after last one needs to be computed.
unsigned HOST_WIDE_INT nelts = vector_cst_encoded_nelts (expr);
if (VECTOR_CST_STEPPED_P (expr)
&& !TYPE_VECTOR_SUBPARTS (TREE_TYPE (expr)).is_constant (&nelts))
return false;
seems to had this in mind, the only problem is that it results in nelts being
larger than vector_cst_encoded_nelts for those VECTOR_CST_STEPPED_P csts. With
the attached patch, it will do what it did before for the encoded elts,
vector_cst_elt just returns what was used before.
>From gcc-bugs-return-628355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:34:17 2019
Return-Path: <gcc-bugs-return-628355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98092 invoked by alias); 8 Jan 2019 17:34:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97915 invoked by uid 48); 8 Jan 2019 17:34:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87855] std::optional<T> only copy-constructible if T is trivially copy-constructible
Date: Tue, 08 Jan 2019 17:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ville.voutilainen at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-87855-4-sHZFgXjmjI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01164.txt.bz2
Content-length: 4510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #18 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The minimal fix is:
PR libstdc++/87855 fix optional for types with non-trivial copy/move
When the contained value is not trivially copy (or move) constructible
the union's copy (or move) constructor will be deleted, and so the
_Optional_payload delegating constructors are invalid. G++ fails to
diagnose this because it incorrectly performs copy elision in the
delegating constructors. Clang does diagnose it (llvm.org/PR40245).
The solution is to avoid performing any copy (or move) when the
contained value's copy (or move) constructor isn't trivial. Instead the
contained value can be constructed by calling _M_construct. This is OK,
because the relevant constructor doesn't need to be constexpr when the
contained value isn't trivially copy (or move) constructible.
PR libstdc++/87855
* include/std/optional: Adjust whitespace.
(_Optional_payload<_Tp, true, C, M>): Use _M_construct to construct
the contained object when it isn't trivially copy/move constructible.
--- a/libstdc++-v3/include/std/optional
+++ b/libstdc++-v3/include/std/optional
@@ -334,11 +334,11 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
constexpr
_Optional_payload(bool __engaged, const _Optional_payload& __other)
- : _Optional_payload(__engaged ?
- _Optional_payload(__ctor_tag<bool>{},
- __other._M_payload) :
- _Optional_payload(__ctor_tag<void>{}))
- { }
+ : _M_engaged(__engaged)
+ {
+ if (__engaged)
+ _M_construct(__other._M_payload);
+ }
constexpr
_Optional_payload(bool __engaged, _Optional_payload&& __other)
@@ -453,20 +453,20 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
constexpr
_Optional_payload(bool __engaged, const _Optional_payload& __other)
- : _Optional_payload(__engaged ?
- _Optional_payload(__ctor_tag<bool>{},
- __other._M_payload) :
- _Optional_payload(__ctor_tag<void>{}))
- { }
-
- constexpr
- _Optional_payload(bool __engaged, _Optional_payload&& __other)
: _Optional_payload(__engaged
? _Optional_payload(__ctor_tag<bool>{},
- std::move(__other._M_payload))
+ __other._M_payload)
: _Optional_payload(__ctor_tag<void>{}))
{ }
+ constexpr
+ _Optional_payload(bool __engaged, _Optional_payload&& __other)
+ : _M_engaged(__engaged)
+ {
+ if (__engaged)
+ _M_construct(std::move(__other._M_payload));
+ }
+
_Optional_payload(const _Optional_payload&) = default;
_Optional_payload(_Optional_payload&&) = default;
@@ -573,19 +573,19 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
constexpr
_Optional_payload(bool __engaged, const _Optional_payload& __other)
- : _Optional_payload(__engaged ?
- _Optional_payload(__ctor_tag<bool>{},
- __other._M_payload) :
- _Optional_payload(__ctor_tag<void>{}))
- { }
+ : _M_engaged(__engaged)
+ {
+ if (__engaged)
+ _M_construct(std::move(__other._M_payload));
+ }
constexpr
_Optional_payload(bool __engaged, _Optional_payload&& __other)
- : _Optional_payload(__engaged
- ? _Optional_payload(__ctor_tag<bool>{},
- std::move(__other._M_payload))
- : _Optional_payload(__ctor_tag<void>{}))
- { }
+ : _M_engaged(__engaged)
+ {
+ if (__engaged)
+ _M_construct(std::move(__other._M_payload));
+ }
_Optional_payload(const _Optional_payload&) = default;
_Optional_payload(_Optional_payload&&) = default;
However, I have a better patch on the way, which hoists all those constructors
into a new base so we only need to fi it in one place (not three).
>From gcc-bugs-return-628356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:38:29 2019
Return-Path: <gcc-bugs-return-628356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104972 invoked by alias); 8 Jan 2019 17:38: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 104886 invoked by uid 55); 8 Jan 2019 17:38:23 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88548] [9 Regression] this accepted in static member functions
Date: Tue, 08 Jan 2019 17:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88548-4-OyOJQvzmQZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88548-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88548-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01165.txt.bz2
Content-length: 2428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88548
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Tue Jan 8 17:37:51 2019
New Revision: 267731
URL: https://gcc.gnu.org/viewcvs?rev=267731&root=gcc&view=rev
Log:
PR c++/88548 - this accepted in static member functions.
* parser.c (cp_debug_parser): Adjust printing of
local_variables_forbidden_p.
(cp_parser_new): Set local_variables_forbidden_p to 0 rather than
false.
(cp_parser_primary_expression): When checking
local_variables_forbidden_p, use THIS_FORBIDDEN or
LOCAL_VARS_FORBIDDEN.
(cp_parser_lambda_body): Update the type of
local_variables_forbidden_p. Set it to 0 rather than false.
(cp_parser_condition): Adjust call to cp_parser_declarator.
(cp_parser_explicit_instantiation): Likewise.
(cp_parser_init_declarator): Likewise.
(cp_parser_declarator): New parameter. Use it.
(cp_parser_direct_declarator): New parameter. Use it to set
local_variables_forbidden_p. Adjust call to cp_parser_declarator.
(cp_parser_type_id_1): Adjust call to cp_parser_declarator.
(cp_parser_parameter_declaration): Likewise.
(cp_parser_default_argument): Update the type of
local_variables_forbidden_p. Set it to LOCAL_VARS_AND_THIS_FORBIDDEN
rather than true.
(cp_parser_member_declaration): Tell cp_parser_declarator if we saw
'static' or 'friend'.
(cp_parser_exception_declaration): Adjust call to cp_parser_declarator.
(cp_parser_late_parsing_default_args): Update the type of
local_variables_forbidden_p. Set it to LOCAL_VARS_AND_THIS_FORBIDDEN
rather than true.
(cp_parser_cache_defarg): Adjust call to cp_parser_declarator.
(cp_parser_objc_class_ivars): Likewise.
(cp_parser_objc_struct_declaration): Likewise.
(cp_parser_omp_for_loop_init): Likewise.
* parser.h (cp_parser): Change the type of local_variables_forbidden_p
to unsigned char.
(LOCAL_VARS_FORBIDDEN, LOCAL_VARS_AND_THIS_FORBIDDEN, THIS_FORBIDDEN):
Define.
* g++.dg/cpp0x/this1.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/this1.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/parser.c
trunk/gcc/cp/parser.h
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:39:06 2019
Return-Path: <gcc-bugs-return-628357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105913 invoked by alias); 8 Jan 2019 17:39:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105839 invoked by uid 48); 8 Jan 2019 17:39:01 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88548] [9 Regression] this accepted in static member functions
Date: Tue, 08 Jan 2019 17:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88548-4-rIQeEGnIDp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88548-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88548-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01166.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88548
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Should be fixed for GCC 9.
>From gcc-bugs-return-628359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:40:56 2019
Return-Path: <gcc-bugs-return-628359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110726 invoked by alias); 8 Jan 2019 17:40: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 110620 invoked by uid 48); 8 Jan 2019 17:40:51 -0000
From: "joel.falcou at lri dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88761] New: ICE in tsubst_copy, at cp/pt.c:15478 when chaining lambda calls & fold-expressions
Date: Tue, 08 Jan 2019 17:40: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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel.falcou at lri dot fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01168.txt.bz2
Content-length: 778
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88761
Bug ID: 88761
Summary: ICE in tsubst_copy, at cp/pt.c:15478 when chaining
lambda calls & fold-expressions
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: joel.falcou at lri dot fr
Target Milestone: ---
The following code:
https://godbolt.org/z/RFZ_k6
compiles fine on g++ 7.x but fails in all g++ 8.x including trunk with an ICE
in tsubst_copy, at cp/pt.c:15478
Unrolling various fold-expression by hand has no effect, nor does capture of
the variable differently (value, mutable lambda etc...)
>From gcc-bugs-return-628358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:40:55 2019
Return-Path: <gcc-bugs-return-628358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110712 invoked by alias); 8 Jan 2019 17:40: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 110617 invoked by uid 55); 8 Jan 2019 17:40:51 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Tue, 08 Jan 2019 17:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl at gcc dot gnu.org
X-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:
Message-ID: <bug-88717-4-ijvPcBZgtM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01167.txt.bz2
Content-length: 865
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
--- Comment #8 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Tue Jan 8 17:40:18 2019
New Revision: 267732
URL: https://gcc.gnu.org/viewcvs?rev=267732&root=gcc&view=rev
Log:
x86: Don't generate vzeroupper if caller passes AVX/AVX512 registers
There is no need to generate vzeroupper if caller passes arguments in
AVX/AVX512 registers.
Tested on i686 and x86-64 with and without --with-arch=native.
gcc/
PR target/88717
* config/i386/i386.c (ix86_avx_u128_mode_exit): Call
ix86_avx_u128_mode_entry.
gcc/testsuite/
PR target/88717
* gcc.target/i386/pr88717.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr88717.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:41:31 2019
Return-Path: <gcc-bugs-return-628360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112273 invoked by alias); 8 Jan 2019 17:41:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112208 invoked by uid 48); 8 Jan 2019 17:41:27 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88717] Unnecessary vzeroupper
Date: Tue, 08 Jan 2019 17:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88717-4-5EBquWoQ1G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01169.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88717
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from H.J. Lu <hjl.tools at gmail dot com> ---
Fixed for GCC 9.
>From gcc-bugs-return-628361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:45:03 2019
Return-Path: <gcc-bugs-return-628361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116752 invoked by alias); 8 Jan 2019 17:45: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 116619 invoked by uid 48); 8 Jan 2019 17:44:57 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 08 Jan 2019 17:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-b8ZCuGCgMK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01170.txt.bz2
Content-length: 1008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #19 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #18)
> The duffs device doesn't need to be done with computed jump, it can be done
> with 3 conditional branches + 3 comparisons too. The advantage of doing
> that is especially if the iter isn't really very small, by doing it that way
> you don't need those 4 unrolled iterations + one scalar loop.
While that is better than an indirect branch, it still branches into the loop,
so you don't benefit from optimization across the loop. So using a trailing
loop is better in most cases.
> Of course, if iter is very short, it might be easier/more efficient to
> duplicate iter more times than 4 and do something else.
If iter is a small constant then peeling makes sense as you can completely
remove the loop counter and branches. Eg. for N=3 you end up with something
like this:
if (n >= 2)
iter1
iter2
n -= 2
if (n != 0)
iter3
>From gcc-bugs-return-628362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 17:59:07 2019
Return-Path: <gcc-bugs-return-628362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8560 invoked by alias); 8 Jan 2019 17:59:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8486 invoked by uid 48); 8 Jan 2019 17:59:03 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 08 Jan 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-R0rnSoKZRK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01171.txt.bz2
Content-length: 259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Or, do we have any machine in the compile farm on which this can be reproduced?
If so, could you give instructions for that please?
>From gcc-bugs-return-628363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:10:06 2019
Return-Path: <gcc-bugs-return-628363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49409 invoked by alias); 8 Jan 2019 18:10: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 49335 invoked by uid 48); 8 Jan 2019 18:10:01 -0000
From: "pkeir at outlook dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88762] New: C++17 Deduction guide and operator expression produces missing template argument error
Date: Tue, 08 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pkeir at outlook 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-88762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01172.txt.bz2
Content-length: 1219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88762
Bug ID: 88762
Summary: C++17 Deduction guide and operator expression produces
missing template argument error
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: pkeir at outlook dot com
Target Milestone: ---
Created attachment 45383
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45383&action=edit
C++ file which produces the error.
I believe the code below/attached should compile with:
g++ -c -std=c++17 gcc-deduction-expr.cpp
The code is already reduced, but I also tried changing the operator for a
method; and only using operator+ once; but the error disappears in both cases.
The code compiles with Clang. Here is the error:
error: missing template arguments after ‘Foo’
(Foo{x} + Foo{y}) + Foo{z};
^~~
The code:
template <typename T>
struct Foo {
Foo operator+(Foo &&f) { return f; }
T &x;
};
template <typename T> Foo(T) -> Foo<T>;
void zod()
{
int x,y,z;
(Foo{x} + Foo{y}) + Foo{z};
}
>From gcc-bugs-return-628364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:22:57 2019
Return-Path: <gcc-bugs-return-628364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4890 invoked by alias); 8 Jan 2019 18:22: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 4782 invoked by uid 48); 8 Jan 2019 18:22:52 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 18:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-M8viiq1Ojf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01173.txt.bz2
Content-length: 416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #18 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Well, it is always possible to generate code with the opposite endianness to
what the hardware "wants". It just won't be very fast code.
BITS_BIG_ENDIAN is just a convenience to the target code writer. The other
four do matter, and are quite obvious really (and all four are necessary).
>From gcc-bugs-return-628366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:36:29 2019
Return-Path: <gcc-bugs-return-628366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14567 invoked by alias); 8 Jan 2019 18:36: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 11651 invoked by uid 48); 8 Jan 2019 18:36:21 -0000
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88754] [7/8/9 Regression] Constructor call wrongly assumed to be a variable declaration
Date: Tue, 08 Jan 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: reichelt at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-88754-4-aB2LVMeVkb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88754-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01175.txt.bz2
Content-length: 934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88754
Volker Reichelt <reichelt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |3.4.0, 3.4.6, 4.1.0, 4.1.1
Summary|Constructor call wrongly |[7/8/9 Regression]
|assumed to be a variable |Constructor call wrongly
|declaration |assumed to be a variable
| |declaration
Known to fail| |4.1.2, 4.2.0, 5.0, 6.0,
| |7.0, 8.0, 9.0
--- Comment #2 from Volker Reichelt <reichelt at gcc dot gnu.org> ---
Unlike PR37213 this is actually a regression that was introduced in GCC 4.1.2.
The code compiled fine with GCC 3.4.0 - GCC 4.1.1.
>From gcc-bugs-return-628365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:36:17 2019
Return-Path: <gcc-bugs-return-628365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10813 invoked by alias); 8 Jan 2019 18:36: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 7795 invoked by uid 48); 8 Jan 2019 18:36:12 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/81980] Spurious -Wmissing-format-attribute and missing -Wformat for va_list in 32-bit mode
Date: Tue, 08 Jan 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc cf_known_to_fail
Message-ID: <bug-81980-4-Lvd9nx1rjc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81980-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81980-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01174.txt.bz2
Content-length: 1585
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81980
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
Summary|Spurious |Spurious
|-Wmissing-format-attribute |-Wmissing-format-attribute
|warning in 32-bit mode |and missing -Wformat for
| |va_list in 32-bit mode
Known to fail| |7.3.0, 8.2.0, 9.0
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
The same problem also results in a missing -Wformat for the following test
case:
#include <stdarg.h>
void f (va_list va)
{
__builtin_printf ("%s", va);
}
It's only diagnosed without -m32:
$ gcc -S -Wall -Wmissing-format-attribute t.c
t.c: In function ‘f’:
t.c:5:23: warning: format ‘%s’ expects argument of type ‘char *’, but argument
2 has type ‘__va_list_tag *’ [-Wformat=]
5 | __builtin_printf ("%s", va);
| ~^ ~~
| | |
| | __va_list_tag *
| char *
One way to deal with it would be compare the name of the type of the argument
to "va_list" Another might be to treat __builtin_va_list as a type distinct
from char* when it's defined to be char*.
>From gcc-bugs-return-628367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:39:52 2019
Return-Path: <gcc-bugs-return-628367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6159 invoked by alias); 8 Jan 2019 18:39:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3111 invoked by uid 48); 8 Jan 2019 18:39:46 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88398] vectorization failure for a small loop to do byte comparison
Date: Tue, 08 Jan 2019 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88398-4-Ox0ga687IA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88398-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01176.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88398
--- Comment #20 from Wilco <wilco at gcc dot gnu.org> ---
I see Kyrill added some examples that show LLVM knows how to unroll loops:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
This kind of thing is much worse than a trailing loop, both for branch
prediction and codesize:
ands x12, x11, 7
beq .L70
cmp x12, 1
beq .L55
cmp x12, 2
beq .L57
cmp x12, 3
beq .L59
cmp x12, 4
beq .L61
cmp x12, 5
beq .L63
cmp x12, 6
bne .L72
>From gcc-bugs-return-628368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:40:43 2019
Return-Path: <gcc-bugs-return-628368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62182 invoked by alias); 8 Jan 2019 18:40: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 57196 invoked by uid 48); 8 Jan 2019 18:40:38 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 18:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-sVrrXaNge8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01177.txt.bz2
Content-length: 871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #6 from Jürgen Reuter <juergen.reuter at desy dot de> ---
In the linking before I do see the following warning:
ld: warning: direct access in function 'operator new[](unsigned long,
std::nothrow_t const&) [clone .cold]' from file
'/usr/local/lib/libstdc++.a(new_opvnt.o)' to global weak symbol 'operator
new[](unsigned long, std::nothrow_t const&)' from file
'/usr/local/lib/libstdc++.a(new_opvnt.o)' means the weak symbol cannot be
overridden at runtime. This was likely ca
Not totally sure what that means. The problem appears that libtool links the
static stdc++ library into my test binary (via --static-libtool-libs), which
causes the warning above, and the malloc runtime error. When I link in by hand
the dynamic library via -lstdc++ then the warning goes away as well as the
runtime error.
>From gcc-bugs-return-628369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 18:42:28 2019
Return-Path: <gcc-bugs-return-628369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101336 invoked by alias); 8 Jan 2019 18:42: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 101305 invoked by uid 48); 8 Jan 2019 18:42:23 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] New: Better Output for Loop Unswitching
Date: Tue, 08 Jan 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01178.txt.bz2
Content-length: 1211
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
Bug ID: 88763
Summary: Better Output for Loop Unswitching
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marius.messerschmidt at googlemail dot com
Target Milestone: ---
I work on a project where we heavily rely on the loop-unswitching feature of
GCC (-funswitch-loops). I started working with the log generated by
-fdump-tree-unswitch.
I started noticing, that the output of the option is very limited. It does only
report a few cases where the optimizer could not unswitch a loop. But in the
source file (gcc/tree-ssa-loop-unswitch.c) there are quite a lot more checks
that lead to a not unswitched loop. Especially the "not invariant" case could
be realy helpfull in the logs.
I tried to implement further warnings, but I do not fully understand every case
in the file, so I am asking someone with better understanding of the internals
of GCC to either fix the bug or explain a few things for me.
Many thanks in Advance :)
>From gcc-bugs-return-628370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:04:57 2019
Return-Path: <gcc-bugs-return-628370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82143 invoked by alias); 8 Jan 2019 19:04:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82090 invoked by uid 48); 8 Jan 2019 19:04:52 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88752] ICE in enclosing_instantiation_of, at cp/pt.c:13328
Date: Tue, 08 Jan 2019 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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-88752-4-Xc5Ed5W9qo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01179.txt.bz2
Content-length: 641
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed but the reduced testcase seems to be overreduced because it's not
valid anymore.
>From gcc-bugs-return-628371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:08:16 2019
Return-Path: <gcc-bugs-return-628371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85812 invoked by alias); 8 Jan 2019 19:08:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85724 invoked by uid 48); 8 Jan 2019 19:08:12 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 19:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-izFzTD7LwS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01180.txt.bz2
Content-length: 871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #19 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #18)
> Well, it is always possible to generate code with the opposite endianness to
> what the hardware "wants". It just won't be very fast code.
>
> BITS_BIG_ENDIAN is just a convenience to the target code writer. The other
> four do matter, and are quite obvious really (and all four are necessary).
What I'm suggesting is that if you have a non-standard endian layout (eg.
FLOAT_WORDS_BIG_ENDIAN, WORDS_BIG_ENDIAN and REG_WORDS_BIG_ENDIAN are not the
same as BYTES_BIG_ENDIAN), optimizations which depend the particular layout
should be disabled. There are far too few occurrences of these macros to
believe that all possible combinations will work correctly on all optimizations
that rely on it.
>From gcc-bugs-return-628373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:10:30 2019
Return-Path: <gcc-bugs-return-628373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100486 invoked by alias); 8 Jan 2019 19:10: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 100371 invoked by uid 55); 8 Jan 2019 19:10:25 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88723] [9 regression] PR debug/88635 patch breaks testsuite_shared.cc compilation
Date: Tue, 08 Jan 2019 19:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
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: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88723-4-RHawjtchRI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88723-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01182.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88723
--- Comment #10 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Tue Jan 8 19:09:52 2019
New Revision: 267734
URL: https://gcc.gnu.org/viewcvs?rev=267734&root=gcc&view=rev
Log:
PR bootstrap/88721
* config/sparc/sparc.c (function_arg_slotno): Set *PPREGNO & *PPADDING
to -1 on entry.
PR debug/88723
* config/sparc/sparc.c (sparc_delegitimize_address): Deal with naked
UNSPECs and UNSPEC_MOVE_GOTDATA specifically.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/sparc/sparc.c
>From gcc-bugs-return-628372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:10:30 2019
Return-Path: <gcc-bugs-return-628372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100476 invoked by alias); 8 Jan 2019 19:10: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 100368 invoked by uid 55); 8 Jan 2019 19:10:25 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Tue, 08 Jan 2019 19:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88721-4-ejtV3smpit@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01181.txt.bz2
Content-length: 625
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Tue Jan 8 19:09:52 2019
New Revision: 267734
URL: https://gcc.gnu.org/viewcvs?rev=267734&root=gcc&view=rev
Log:
PR bootstrap/88721
* config/sparc/sparc.c (function_arg_slotno): Set *PPREGNO & *PPADDING
to -1 on entry.
PR debug/88723
* config/sparc/sparc.c (sparc_delegitimize_address): Deal with naked
UNSPECs and UNSPEC_MOVE_GOTDATA specifically.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/sparc/sparc.c
>From gcc-bugs-return-628374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:11:31 2019
Return-Path: <gcc-bugs-return-628374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104130 invoked by alias); 8 Jan 2019 19:11:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103977 invoked by uid 48); 8 Jan 2019 19:11:27 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88721] [9 regression] -Wmaybe-uninitialized warnings in sparc.c
Date: Tue, 08 Jan 2019 19:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88721-4-eKwI7Wsc1B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01183.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
.
>From gcc-bugs-return-628375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:11:32 2019
Return-Path: <gcc-bugs-return-628375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104399 invoked by alias); 8 Jan 2019 19:11: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 104063 invoked by uid 48); 8 Jan 2019 19:11:28 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/24639] [meta-bug] bug to track all Wuninitialized issues
Date: Tue, 08 Jan 2019 19:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.1.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: trivial
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-24639-4-QJf82Fd4Kp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-24639-4@http.gcc.gnu.org/bugzilla/>
References: <bug-24639-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01184.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24639
Bug 24639 depends on bug 88721, which changed state.
Bug 88721 Summary: [9 regression] -Wmaybe-uninitialized warnings in sparc.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88721
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:13:29 2019
Return-Path: <gcc-bugs-return-628376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119437 invoked by alias); 8 Jan 2019 19:13:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119394 invoked by uid 48); 8 Jan 2019 19:13:25 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88752] ICE in enclosing_instantiation_of, at cp/pt.c:13328
Date: Tue, 08 Jan 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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:
Message-ID: <bug-88752-4-ZTamzTly6Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01185.txt.bz2
Content-length: 179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Nevertheless the ICE seems to have started with r259043.
>From gcc-bugs-return-628377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:25:23 2019
Return-Path: <gcc-bugs-return-628377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60312 invoked by alias); 8 Jan 2019 19:25: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 60247 invoked by uid 48); 8 Jan 2019 19:25:18 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88761] ICE in tsubst_copy, at cp/pt.c:15478 when chaining lambda calls & fold-expressions
Date: Tue, 08 Jan 2019 19:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-88761-4-7j2SGkfh9Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01186.txt.bz2
Content-length: 707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88761
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Like PR 88752, started with r259043.
>From gcc-bugs-return-628378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:29:39 2019
Return-Path: <gcc-bugs-return-628378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64958 invoked by alias); 8 Jan 2019 19:29: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 64718 invoked by uid 55); 8 Jan 2019 19:29:34 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88047] [9 Regression] ICE in gfc_find_vtab, at fortran/class.c:2843
Date: Tue, 08 Jan 2019 19: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: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88047-4-tipLaAE6XG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01187.txt.bz2
Content-length: 756
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88047
--- Comment #8 from janus at gcc dot gnu.org ---
Author: janus
Date: Tue Jan 8 19:29:01 2019
New Revision: 267735
URL: https://gcc.gnu.org/viewcvs?rev=267735&root=gcc&view=rev
Log:
2019-01-08 Janus Weil <janus@gcc.gnu.org>
PR fortran/88047
* class.c (gfc_find_vtab): For polymorphic typespecs, the components of
the class container may not be available (in case of invalid code).
2019-01-08 Janus Weil <janus@gcc.gnu.org>
PR fortran/88047
* gfortran.dg/class_69.f90: New test case.
Added:
trunk/gcc/testsuite/gfortran.dg/class_69.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/class.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:33:00 2019
Return-Path: <gcc-bugs-return-628379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76582 invoked by alias); 8 Jan 2019 19:32:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76520 invoked by uid 48); 8 Jan 2019 19:32:54 -0000
From: "sbence92 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Tue, 08 Jan 2019 19:32: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: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: sbence92 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-k2f8bhnjjp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01188.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #13 from Bence Szabó <sbence92 at gmail dot com> ---
ICE still occurs with current trunk (r267728) patched with gcc9-pr88331.patch
from PR88331. r266345 seems to give quite a hard time for cygwin / mingw
targets, might be worth reverting as the gcc 9 release is comming up.
>From gcc-bugs-return-628380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:36:53 2019
Return-Path: <gcc-bugs-return-628380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6828 invoked by alias); 8 Jan 2019 19:36:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128592 invoked by uid 48); 8 Jan 2019 19:36:49 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88047] [9 Regression] ICE in gfc_find_vtab, at fortran/class.c:2843
Date: Tue, 08 Jan 2019 19:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88047-4-2W1XMqSXnY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01189.txt.bz2
Content-length: 413
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88047
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from janus at gcc dot gnu.org ---
Fixed with r267735. Closing.
>From gcc-bugs-return-628381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:46:16 2019
Return-Path: <gcc-bugs-return-628381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61866 invoked by alias); 8 Jan 2019 19:46:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56825 invoked by uid 48); 8 Jan 2019 19:46:11 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Tue, 08 Jan 2019 19:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.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:
Message-ID: <bug-88653-4-ncHO3OPesU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01190.txt.bz2
Content-length: 218
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
--- Comment #22 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Apparently, this is some kind of cygwin problem.
Did you report the problem to cygwin?
>From gcc-bugs-return-628382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:51:58 2019
Return-Path: <gcc-bugs-return-628382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63925 invoked by alias); 8 Jan 2019 19:51: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 63796 invoked by uid 48); 8 Jan 2019 19:51:49 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Tue, 08 Jan 2019 19:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray 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-88572-4-iRGhnW7lMO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01191.txt.bz2
Content-length: 2524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #12 from Will Wray <wjwray at gmail dot com> ---
On further investigation the logic of using first_initializer_p looks correct.
The comment on reshape_init suggests that it wasn't intended for scalar init:
/* Undo the brace-elision allowed by [dcl.init.aggr] in a
brace-enclosed aggregate initializer.
INIT is the CONSTRUCTOR containing the list of initializers describing
a brace-enclosed initializer for an entity of the indicated aggregate TYPE.
In fact, reshape_init is used more broadly to error-check braced-init-list -
- the first substantive case is direct enum init, a scalar init special-case.
Perhaps the general scalar case should be dealt with here at the top level.
Instead the recursive call to reshape_init_r is done next
setting first_initializer_p to true - the only place it is set true
(the true value will be forwarded to reshape_init_class for class type).
So, for a scalar init, the tree type passed to reshape_init is SCALAR_TYPE_P.
This is passed down to reshape_init_r with first_initializer_p set true.
Entering reshape_init_r we have
if (first_initializer_p && !CP_AGGREGATE_TYPE_P (type)
&& has_designator_problem (d, complain))
return error_mark_node;
Here, first_initializer_p && !CP_AGGREGATE_TYPE_P (type) covers scalar init
(and other non-aggregate init).
Arriving at our block, we also enter a context requiring a single-initializer
/* A non-aggregate type is always initialized with a single
initializer. */
if (!CP_AGGREGATE_TYPE_P (type))
and then further filter down to CONSTRUCTOR with BRACE_ENCLOSED_INITIALIZER_P
and, specifically of SCALAR_TYPE_P
if (TREE_CODE (stripped_init) == CONSTRUCTOR
/* Don't complain about a capture-init. */
&& !CONSTRUCTOR_IS_DIRECT_INIT (stripped_init)
&& BRACE_ENCLOSED_INITIALIZER_P (stripped_init)) /* p7626.C */
{
if (SCALAR_TYPE_P (type))
> I understood it to mean something like {{1}, 2} is the first,
> ^^^
Me too, but taking "outermost CONSTRUCTOR node" to mean the actual outer type
here (first_initializer_p==true) and with only a single scalar initializer:
like scalar_type{{1}} not { {1} }
^^^ scalar_type^^^
So, I've convinced myself that my patch follows the existing logic.
It'd be good to get review from someone not suffering from confirmation bias.
>From gcc-bugs-return-628383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 19:57:15 2019
Return-Path: <gcc-bugs-return-628383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94910 invoked by alias); 8 Jan 2019 19:57:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93673 invoked by uid 48); 8 Jan 2019 19:57:10 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88653] Is this a compiler bug?
Date: Tue, 08 Jan 2019 19:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88653-4-Az2drTkSDi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01192.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88653
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #23 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Well, if it is a problem in the cygwin binary distribution, it
is not a gfortran bug.
Also, since it works for me when installing from cygwin, this
does not appear to be a general problem.
Please report this to cygwin, there is not really anything
that we can do here.
>From gcc-bugs-return-628384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:00:01 2019
Return-Path: <gcc-bugs-return-628384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14216 invoked by alias); 8 Jan 2019 20:00:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14154 invoked by uid 48); 8 Jan 2019 19:59:56 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 20:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-FSvYuS957F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01193.txt.bz2
Content-length: 848
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #15 from Romain Geissler <romain.geissler at amadeus dot com> ---
Thanks for these remarks.
FYI, what I am following are the Linux From Scratch guidelines, which build the
initial gcc like this (with both c and C++ support, disabling libstdc++ build):
http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-pass1.html
Then after building the glibc, they do build the libstdc++ alone like this:
http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-libstdc++.html
With this PR I just found out that either my understanding of LFS is wrong,
either LFS itself is. Indeed I don't like much that when configured using my
bootstrap scripts libstdc++ doesn't use the C compiler but the C++ one to find
C headers. I will have a look to sort this out.
>From gcc-bugs-return-628385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:03:19 2019
Return-Path: <gcc-bugs-return-628385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23465 invoked by alias); 8 Jan 2019 20:03:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23390 invoked by uid 48); 8 Jan 2019 20:03:14 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Tue, 08 Jan 2019 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-kJA3ElcwPa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01194.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #14 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> ICE still occurs with current trunk (r267728) patched with
> gcc9-pr88331.patch from PR88331. r266345 seems to give quite a hard time for
> cygwin / mingw targets, might be worth reverting as the gcc 9 release is
> comming up.
I agree, the patch is quite weird and should not have been accepted.
>From gcc-bugs-return-628386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:16:34 2019
Return-Path: <gcc-bugs-return-628386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74450 invoked by alias); 8 Jan 2019 20:16:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72791 invoked by uid 48); 8 Jan 2019 20:16:05 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] [9 Regression] ICE in reference_record with data statement
Date: Tue, 08 Jan 2019 20:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
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: cc
Message-ID: <bug-86322-4-fmtLuHvHCr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01195.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #3 from janus at gcc dot gnu.org ---
I have not verified, but I'm pretty sure the regression is due to r260808:
2018-05-27 Steven G. Kargl <kargl@gcc.gnu.org>
* decl.c (match_data_constant): Fortran 2018 allows pointer
initialization in a data statement.
>From gcc-bugs-return-628387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:20:30 2019
Return-Path: <gcc-bugs-return-628387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79490 invoked by alias); 8 Jan 2019 20:20:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79414 invoked by uid 48); 8 Jan 2019 20:20:25 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/53320] -fcheck=pointer should diagnose pointer-assignment of a noncontiguous tgt to a CONTIGUOUS ptr
Date: Tue, 08 Jan 2019 20:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.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: 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-53320-4-6qzPR7ZSvr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53320-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53320-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01196.txt.bz2
Content-length: 508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53320
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #1)
> Duplicate or pr49232?
pr49232 was about compile-time warnings, this is about
run-time checks.
>From gcc-bugs-return-628388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:34:24 2019
Return-Path: <gcc-bugs-return-628388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8169 invoked by alias); 8 Jan 2019 20:34: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 8076 invoked by uid 55); 8 Jan 2019 20:34:18 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88749] [9 Regression] Failure while building libstdc++-v3/src/filesystem/ops.cc on trunk
Date: Tue, 08 Jan 2019 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88749-4-pUPaOfe6LN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88749-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01197.txt.bz2
Content-length: 1227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88749
--- Comment #16 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Tue, 8 Jan 2019, romain.geissler at amadeus dot com wrote:
> FYI, what I am following are the Linux From Scratch guidelines, which build the
> initial gcc like this (with both c and C++ support, disabling libstdc++ build):
> http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-pass1.html
> Then after building the glibc, they do build the libstdc++ alone like this:
> http://www.linuxfromscratch.org/lfs/view/development/chapter05/gcc-libstdc++.html
Those instructions use libc_cv_forced_unwind=yes libc_cv_c_cleanup=yes
with glibc, which haven't been needed since my commit
e7dbb1bec3be35897acb18aa277807ed276384c5, "Weaken two NPTL configure link
tests to compile tests.", March 2012.
I advise looking at how glibc's build-many-glibcs.py does things for the
modern approach for bootstrapping a cross-compilation toolchain for a
target using glibc. (Although some pieces may need adjusting if what you
want is a native toolchain using unusual directory arrangements, which
some of those LFS instructions seem to suggest.)
>From gcc-bugs-return-628389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:35:26 2019
Return-Path: <gcc-bugs-return-628389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10871 invoked by alias); 8 Jan 2019 20:35:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10818 invoked by uid 48); 8 Jan 2019 20:35:21 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88376] [7/8/9 Regression] ICE in is_illegal_recursion, at fortran/resolve.c:1689
Date: Tue, 08 Jan 2019 20:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88376-4-iq4h9z291l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01198.txt.bz2
Content-length: 873
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88376
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org,
| |kargl at gcc dot gnu.org
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #1)
> The change of behavior occurred between revision r258235 (2018-03-04, error)
> and r258362 (2018-03-08, ICE) and has been back ported to GCC6 and 7.
Based on this information, I'd guess that r258347 is the culprit:
2018-03-07 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/64124
PR fortran/70409
* decl.c (gfc_match_char_spec): Try to reduce a charlen to a constant.
>From gcc-bugs-return-628390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:37:16 2019
Return-Path: <gcc-bugs-return-628390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13828 invoked by alias); 8 Jan 2019 20:37: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 13724 invoked by uid 48); 8 Jan 2019 20:37:11 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Tue, 08 Jan 2019 20:37: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: bergner 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88678-4-29NFVOUtdE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01199.txt.bz2
Content-length: 2110
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |bergner at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Peter Bergner <bergner at gcc dot gnu.org> ---
Confirmed. I don't think the mentioned revision caused the problem, other than
adding a new test case that fails the same way. I simplified test case fails
for me with gcc 7.3. I don't have anything older to test with.
bergner@pike:~/gcc/BUGS/PR88678$ cat bug.f90
program foo
use ieee_arithmetic
implicit none
real x
x = ieee_value(x, ieee_signaling_nan)
if (.not. ieee_is_nan(x)) stop 1
end program foo
bergner@pike:~/gcc/BUGS/PR88678$ gfortran -ffpe-trap=invalid -static bug.f90
bergner@pike:~/gcc/BUGS/PR88678$ ./a.out
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic
operation.
Backtrace for this error:
#0 0x10001b1b
Floating point exception
bergner@pike:~/gcc/BUGS/PR88678$ gdb ./a.out
(gdb) break * 0x1000aad8
Breakpoint 1 at 0x1000aad8
(gdb) run
Starting program: /home/bergner/gcc/BUGS/PR88678/a.out
Breakpoint 1, 0x000000001000aad8 in __ieee_arithmetic_MOD_ieee_value_4 ()
1: x/i $pc
=> 0x1000aad8 <__ieee_arithmetic_MOD_ieee_value_4+120>: fsqrts f1,f1
(gdb) info registers f1
f1 -1 (raw 0xbff0000000000000)
(gdb) stepi
Program received signal SIGFPE, Arithmetic exception.
0x000000001000aad8 in __ieee_arithmetic_MOD_ieee_value_4 ()
1: x/i $pc
=> 0x1000aad8 <__ieee_arithmetic_MOD_ieee_value_4+120>: fsqrts f1,f1
So it seems, we still have floating point exceptions enabled when we try and
generate the signaling nan value which is causing the SIGFPE. Who was supposed
to disable them before we execute the fsqrt with -1 as the source value?
>From gcc-bugs-return-628391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:49:32 2019
Return-Path: <gcc-bugs-return-628391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56952 invoked by alias); 8 Jan 2019 20:49: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 56511 invoked by uid 48); 8 Jan 2019 20:48:54 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88764] New: [nvptx, libgomp, testsuite] Update testsuite for default vector length larger than 32
Date: Tue, 08 Jan 2019 20:49: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: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88764-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01200.txt.bz2
Content-length: 2606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88764
Bug ID: 88764
Summary: [nvptx, libgomp, testsuite] Update testsuite for
default vector length larger than 32
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
With the nvptx vector-length patches arriving on trunk, it starts to become
important to run the libgomp openacc testsuite with a vector-length default of
larger than 32, at the most extreme: 1024, f.i. by setting:
...
-#define PTX_DEFAULT_VECTOR_LENGTH PTX_WARP_SIZE
+#define PTX_DEFAULT_VECTOR_LENGTH PTX_CTA_SIZE
...
or by using -fopenacc-dim=::1024 as default in the libgomp testsuite.
There are however test-cases that assume default vector_length of 32, so we
need some way to indicate this, f.i. (or to start with) an effective target
openacc_default_vector_length_32, and update those test-cases.
Focusing on the execution failures, with '#define PTX_DEFAULT_VECTOR_LENGTH
PTX_CTA_SIZE' I see these tests failing with insufficient resources:
...
FAIL: libgomp.oacc-fortran/kernels-loop-2.f95 -DACC_DEVICE_TYPE_nvidia=1
-DACC_MEM_SHARED=0 -O2 execution test
FAIL: libgomp.oacc-fortran/kernels-loop-2.f95 -DACC_DEVICE_TYPE_nvidia=1
-DACC_MEM_SHARED=0 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops
-ftracer -finline-functions execution test
FAIL: libgomp.oacc-fortran/kernels-loop-2.f95 -DACC_DEVICE_TYPE_nvidia=1
-DACC_MEM_SHARED=0 -O3 -g execution test
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/kernels-loop-2.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O2 execution test
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/kernels-loop-2.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O2 execution test
...
and these tests failing due to a hard-coded check verifying default vector
length is 32:
...
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/parallel-dims.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O0 execution test
FAIL: libgomp.oacc-c++/../libgomp.oacc-c-c++-common/parallel-dims.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O2 execution test
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/parallel-dims.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O0 execution test
FAIL: libgomp.oacc-c/../libgomp.oacc-c-c++-common/parallel-dims.c
-DACC_DEVICE_TYPE_nvidia=1 -DACC_MEM_SHARED=0 -O2 execution test
...
>From gcc-bugs-return-628392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:50:15 2019
Return-Path: <gcc-bugs-return-628392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58171 invoked by alias); 8 Jan 2019 20:50: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 58071 invoked by uid 48); 8 Jan 2019 20:50:11 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/84245] [7/8/9 Regression] ICE in delete_root, at fortran/bbt.c:150
Date: Tue, 08 Jan 2019 20:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84245-4-bFrdfoc4Oo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84245-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84245-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01201.txt.bz2
Content-length: 508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84245
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to G. Steinmetz from comment #0)
> Changed between 20161023 and 20161030 :
I see two possible candidates (guessing for the second):
* r241450
* r241630
>From gcc-bugs-return-628393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:52:17 2019
Return-Path: <gcc-bugs-return-628393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76287 invoked by alias); 8 Jan 2019 20:52: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 76183 invoked by uid 48); 8 Jan 2019 20:52:13 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Tue, 08 Jan 2019 20:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner 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-88678-4-adAEW2GQjd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01202.txt.bz2
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #5 from Peter Bergner <bergner at gcc dot gnu.org> ---
Hmm, the test case is explicitly adding the options
-ffpe-trap=overflow,invalid, so is this a test case error? We tell it to trap
on invalid fp operations which we force it to do when generating the signaling
nan value. Removing the above option allows the reduced test case to not die.
bergner@pike:~/gcc/BUGS/PR88678$ gfortran -ffpe-trap=invalid -static bug.f90
bergner@pike:~/gcc/BUGS/PR88678$ ./a.out
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic
operation.
Backtrace for this error:
#0 0x10001b1b
Floating point exception
bergner@pike:~/gcc/BUGS/PR88678$ gfortran -static bug.f90
bergner@pike:~/gcc/BUGS/PR88678$ ./a.out
bergner@pike:~/gcc/BUGS/PR88678$
>From gcc-bugs-return-628394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 20:59:28 2019
Return-Path: <gcc-bugs-return-628394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90213 invoked by alias); 8 Jan 2019 20:59:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90135 invoked by uid 48); 8 Jan 2019 20:59:23 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-G665KHXgiD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01203.txt.bz2
Content-length: 362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #20 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> BITS_BIG_ENDIAN is just a convenience to the target code writer. The other
> four do matter, and are quite obvious really (and all four are necessary).
Yes, I agree that BITS_BIG_ENDIAN shouldn't matter here, it's pure RTL stuff.
>From gcc-bugs-return-628395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:02:28 2019
Return-Path: <gcc-bugs-return-628395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94293 invoked by alias); 8 Jan 2019 21:02: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 94225 invoked by uid 48); 8 Jan 2019 21:02:24 -0000
From: "mateuszb at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88331] [9 Regression] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Tue, 08 Jan 2019 21:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mateuszb at poczta dot onet.pl
X-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:
Message-ID: <bug-88331-4-kqgXbUsrqb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01204.txt.bz2
Content-length: 164
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #14 from mateuszb at poczta dot onet.pl ---
The patch from comment #13 solve my problems. Thanks!
>From gcc-bugs-return-628396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:07:47 2019
Return-Path: <gcc-bugs-return-628396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105997 invoked by alias); 8 Jan 2019 21:07:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105873 invoked by uid 48); 8 Jan 2019 21:07:40 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 21:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88750-4-qzvBr71gJ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01205.txt.bz2
Content-length: 2973
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
Iain Sandoe <iains at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |iains at gcc dot gnu.org
--- Comment #7 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #6)
> In the linking before I do see the following warning:
> ld: warning: direct access in function 'operator new[](unsigned long,
> std::nothrow_t const&) [clone .cold]' from file
> '/usr/local/lib/libstdc++.a(new_opvnt.o)' to global weak symbol 'operator
> new[](unsigned long, std::nothrow_t const&)' from file
> '/usr/local/lib/libstdc++.a(new_opvnt.o)' means the weak symbol cannot be
> overridden at runtime. This was likely ca
This is almost certainly a "red herring".. (of course, "almost certainly" until
proven).
> Not totally sure what that means.
GCC can optimise code to split it into parts that are frequently executed (or
'hot') and parts that are not ('cold').
The externally-visible function typically calls the .cold part to do some setup
(or it might be an exceptional or abort path). In order to facilitate debug,
the cold part of the function has a label (__xxxxx.cold:) which is visible to
the linker.
In fact, one would never call that symbol from outside the TU in which it's
created (it's linker-visible, but not a global) ..
.. but the linker's complaint here is that if one overrides the externally
visible weak "new" symbol that wouldn't override the __new.cold one.
However, the only caller of __new.cold is __new, and therefore if you override
__new, nothing will be trying to call __new.cold. So IMO (probably we should
file a radar) the linker warning is bogus (or at least overly conservative).
The problem appears that libtool links the
> static stdc++ library into my test binary (via --static-libtool-libs), which
> causes the warning above, and the malloc runtime error. When I link in by
> hand the dynamic library via -lstdc++ then the warning goes away as well as
> the runtime error.
* It's hard to deduce what's going on/changed without some specific points as
Dominque says...
"then"[working] and "now" [first known not-working] could do with some
definition - plus if possible where the actual failure is (with a backtrace)
* It's generally not possible for folks here to reproduce problems by trying to
replicate your builds - this is a volunteer workforce, with highly constrained
time resources ;) .. we will need you to narrow things down
* It's quite possible that when you link statically - you are getting the
compiler's libstdc++ .. and when you link the shared version, it's being
resolved to the one installed in /usr/lib.
Please post as minimum the output of "otool -Lv <binary>" for both the working
(lstdc++) and non-working (--static-libtool-libs).
>From gcc-bugs-return-628397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:25:27 2019
Return-Path: <gcc-bugs-return-628397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33302 invoked by alias); 8 Jan 2019 21:25:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32342 invoked by uid 48); 8 Jan 2019 21:24:46 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 21:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-674srCU7UX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01206.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #21 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #20)
> > BITS_BIG_ENDIAN is just a convenience to the target code writer. The other
> > four do matter, and are quite obvious really (and all four are necessary).
>
> Yes, I agree that BITS_BIG_ENDIAN shouldn't matter here, it's pure RTL stuff.
Is it really pure RTL, therefore not used in tree? So the above patch using
BITS_BIG_ENDIAN for tree stuff would be incorrect to use it?
>From gcc-bugs-return-628398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:31:20 2019
Return-Path: <gcc-bugs-return-628398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69472 invoked by alias); 8 Jan 2019 21:31:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67037 invoked by uid 48); 8 Jan 2019 21:30:30 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87305] [9 Regression] Segfault in end_hard_regno in setup_live_pseudos_and_spill_after_risky_transforms on aarch64 big-endian
Date: Tue, 08 Jan 2019 21:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87305-4-lcHd0V8r0L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01207.txt.bz2
Content-length: 246
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87305
--- Comment #3 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
>
> Vlad, could you please have a look?
I've just started to work on it.
>From gcc-bugs-return-628399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:35:02 2019
Return-Path: <gcc-bugs-return-628399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79203 invoked by alias); 8 Jan 2019 21:35:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79078 invoked by uid 48); 8 Jan 2019 21:34:56 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 21:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-2aVnG19FiG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01208.txt.bz2
Content-length: 2048
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #8 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Yes I know:
here is the non-working library resolution:
static_1.exe:
lib/libcuttools.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/libopenloops.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/liboneloop.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/libolcommon.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/librambo.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/local/lib/liblcio.2.12.dylib (compatibility version 2.12.0, current
version 2.12.1)
/usr/local/lib/libgfortran.5.dylib (compatibility version 6.0.0, current
version 6.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
1252.200.5)
/usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/local/lib/libquadmath.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
and this is the working one:
static_1.exe:
lib/libcuttools.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/libopenloops.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/liboneloop.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/libolcommon.dylib (compatibility version 0.0.0, current version 0.0.0)
lib/librambo.dylib (compatibility version 0.0.0, current version 0.0.0)
/usr/local/lib/liblcio.2.12.dylib (compatibility version 2.12.0, current
version 2.12.1)
/usr/local/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
version 7.26.0)
/usr/local/lib/libgfortran.5.dylib (compatibility version 6.0.0, current
version 6.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
1252.200.5)
/usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
version 1.0.0)
/usr/local/lib/libquadmath.0.dylib (compatibility version 1.0.0, current
version 1.0.0)
>From gcc-bugs-return-628400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:36:58 2019
Return-Path: <gcc-bugs-return-628400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82824 invoked by alias); 8 Jan 2019 21:36: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 82774 invoked by uid 55); 8 Jan 2019 21:36:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88457] ICE: Max. number of generated reload insns per insn is achieved (90)
Date: Tue, 08 Jan 2019 21:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88457-4-3LFiE6Pk7F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88457-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88457-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01209.txt.bz2
Content-length: 564
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88457
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 21:36:21 2019
New Revision: 267739
URL: https://gcc.gnu.org/viewcvs?rev=267739&root=gcc&view=rev
Log:
PR target/88457
* gcc.target/powerpc/pr88457.c: Remove -m32, -c and -mcpu=e300c3 from
dg-options. Require ppc_cpu_supports_hw effective target instead of
powerpc64*-*-*.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/powerpc/pr88457.c
>From gcc-bugs-return-628401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:40:35 2019
Return-Path: <gcc-bugs-return-628401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87188 invoked by alias); 8 Jan 2019 21: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 86615 invoked by uid 55); 8 Jan 2019 21:40:30 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] [9 Regression] ICE in reference_record with data statement
Date: Tue, 08 Jan 2019 21:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86322-4-jQIyLX0LuS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01210.txt.bz2
Content-length: 1300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jan 08, 2019 at 08:15:46PM +0000, janus at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
>
> janus at gcc dot gnu.org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |janus at gcc dot gnu.org
>
> --- Comment #3 from janus at gcc dot gnu.org ---
> I have not verified, but I'm pretty sure the regression is due to r260808:
>
> 2018-05-27 Steven G. Kargl <kargl@gcc.gnu.org>
>
> * decl.c (match_data_constant): Fortran 2018 allows pointer
> initialization in a data statement.
>
Naw, it is is not due to my patch. Rather my patch has
exposed or uncovered a bug in gfortran. gfortran needs
to check
F2018:C877 (R839) A data-i-do-object or a variable that appears as a
data-stmt-object shall not be an object designator in which a pointer
appears other than as the entire rightmost part-ref .
In decl.c (gfc_match_data), gfortran needs a check for C877.
I haven't gotten around to fixing this yet, and I likely won't
for the foreseeable future.
>From gcc-bugs-return-628402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:46:01 2019
Return-Path: <gcc-bugs-return-628402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112719 invoked by alias); 8 Jan 2019 21:46: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 112585 invoked by uid 48); 8 Jan 2019 21:45:53 -0000
From: "davmac at davmac dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80916] [7/8/9 Regression] Spurious "declared 'static' but never defined" warning
Date: Tue, 08 Jan 2019 21:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davmac at davmac dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80916-4-OOlOPg7Ah7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80916-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01211.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80916
--- Comment #8 from Davin McCall <davmac at davmac dot org> ---
(In reply to ensadc from comment #7)
> Note that the "never defined" part is also misleading: the warning persists
> when `i::dispatch` does have a definition
Yes; and actually, I note that in the original test case I supplied, the
dispatch function doesn't have a definition, but it doesn't have internal
linkage either.
So, I think the warning really is spurious and it's not just a case of it
saying "declared static" where it should say "has internal linkage".
>From gcc-bugs-return-628403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:49:48 2019
Return-Path: <gcc-bugs-return-628403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70732 invoked by alias); 8 Jan 2019 21:49: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 35052 invoked by uid 55); 8 Jan 2019 21:49:35 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Tue, 08 Jan 2019 21:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88678-4-ARCy7X2Y4k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01212.txt.bz2
Content-length: 1095
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #6 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jan 08, 2019 at 08:37:11PM +0000, bergner at gcc dot gnu.org wrote:
> Confirmed. I don't think the mentioned revision caused the problem, other than
> adding a new test case that fails the same way. I simplified test case fails
> for me with gcc 7.3. I don't have anything older to test with.
>
> bergner@pike:~/gcc/BUGS/PR88678$ cat bug.f90
> program foo
> use ieee_arithmetic
> implicit none
> real x
> x = ieee_value(x, ieee_signaling_nan)
> if (.not. ieee_is_nan(x)) stop 1
> end program foo
The backtrace in comment #2 has
#0 0x3fffb17f0477 in ???
#1 0x3fffb14f1694 in feenableexcept
at ../sysdeps/powerpc/fpu/feenablxcpt.c:44
#2 0x3fffb1765e73 in __ieee_exceptions_MOD_ieee_support_halting
at /home/seurer/gcc/gcc-test2/libgfortran/ieee/ieee_exceptions.F90:193
So, this is a better testcase.
program foo
use ieee_arithmetic
logical flag
flag = ieee_supporting_halting(ieee_signaling_nan)
end program
>From gcc-bugs-return-628405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:50:40 2019
Return-Path: <gcc-bugs-return-628405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127232 invoked by alias); 8 Jan 2019 21:50:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127150 invoked by uid 48); 8 Jan 2019 21:50:35 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 21:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-E3mmNE0luT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01214.txt.bz2
Content-length: 2990
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #9 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #8)
Thanks!
I've been using gmp-6.1.2, mpfr-3.1.6, mpc-1.1.0 isl-0.20 on all my recent
builds (for trunk, gcc-8 and gcc-7)
You don't (I think) mention whether the GCC you're using is trunk or 8 or 7?
I usually bootstrap gap &friends with the compiler, but that ought not to be
necessary.
----
I assume that all the code is built with the same compiler?
> here is the non-working library resolution:
> static_1.exe:
> lib/libcuttools.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> lib/libopenloops.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> lib/liboneloop.dylib (compatibility version 0.0.0, current version 0.0.0)
> lib/libolcommon.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> lib/librambo.dylib (compatibility version 0.0.0, current version 0.0.0)
> /usr/local/lib/liblcio.2.12.dylib (compatibility version 2.12.0, current
> version 2.12.1)
> /usr/local/lib/libgfortran.5.dylib (compatibility version 6.0.0, current
> version 6.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
> 1252.200.5)
> /usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
> version 1.0.0)
> /usr/local/lib/libquadmath.0.dylib (compatibility version 1.0.0, current
> version 1.0.0)
>
> and this is the working one:
>
> static_1.exe:
> lib/libcuttools.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> lib/libopenloops.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> lib/liboneloop.dylib (compatibility version 0.0.0, current version 0.0.0)
> lib/libolcommon.dylib (compatibility version 0.0.0, current version
> 0.0.0)
> lib/librambo.dylib (compatibility version 0.0.0, current version 0.0.0)
> /usr/local/lib/liblcio.2.12.dylib (compatibility version 2.12.0, current
> version 2.12.1)
> /usr/local/lib/libstdc++.6.dylib (compatibility version 7.0.0, current
> version 7.26.0)
^^^ this is the installation from the same compiler that you used to build the
non-working example above?
> /usr/local/lib/libgfortran.5.dylib (compatibility version 6.0.0, current
> version 6.0.0)
> /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version
> 1252.200.5)
> /usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current
> version 1.0.0)
> /usr/local/lib/libquadmath.0.dylib (compatibility version 1.0.0, current
> version 1.0.0)
* If you invoke the exe with
DYLD_PRINT_LIBRARIES=1 <exe>
you can confirm that it is, indeed, using the libraries listed there...
* So the linker/assembler/otool/ar/nm/strip/etc you're using come from Xcode
10.1?
* GCC binaries built with debug enabled are debugable by lldb, if you don't
have a working GDB.
(I use -Og -g3 as build options, FWIW)
>From gcc-bugs-return-628404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:50:03 2019
Return-Path: <gcc-bugs-return-628404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90795 invoked by alias); 8 Jan 2019 21:50: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 81952 invoked by uid 48); 8 Jan 2019 21:49:58 -0000
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 08 Jan 2019 21:50: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikpelinux at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88714-4-DGtyeOsNJn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01213.txt.bz2
Content-length: 1738
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #3 from Mikael Pettersson <mikpelinux at gmail dot com> ---
Created attachment 45384
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45384&action=edit
pre-processed source for libiberty/sort.c
One of the smallest .o files that differ is from libiberty's sort.c
(pre-processed source attached as sort.i; sorry haven't had time to minimize
it). stage1 and stage2 generate different code for this file:
> stage1-gcc/xgcc -Bstage1-gcc -O2 -S -o sort.s-stage1 sort.i
> stage2-gcc/xgcc -Bstage2-gcc -O2 -S -o sort.s-stage2 sort.i
> diff -u sort.s-stage[12] | wc
109 460 2005
> diff -u sort.s-stage[12] | head
--- sort.s-stage1 2019-01-08 22:10:50.288929388 +0100
+++ sort.s-stage2 2019-01-08 22:10:59.148975673 +0100
@@ -21,21 +21,23 @@
sort_pointers:
@ args = 0, pretend = 0, frame = 1024
@ frame_needed = 0, uses_anonymous_args = 0
- push {r4, r5, r6, r7, r8, lr}
- lsl r7, r0, #2
+ push {r4, r5, r6, r7, r8, r9, lr}
+ lsl r8, r0, #2
I wasn't able to trigger anything with -fcompare-debug, using either of the
stage1 or stage2 compilers.
Looking though the build log, I noticed that stage1 compiles stage2 with
-fno-checking, while stage2 compiles stage3 with -fchecking=1. (This is
deliberate according to the top-level Makefile.tpl.) Stage1 generates the same
code for sort.i with -fno-checking or -fchecking=1, and stage2 does the same.
Finally I checked the stage3 compiler and it generates the exact same code as
the stage1 does.
To me it looks like -fno-checking (possibly in combination with
--enable-checking=release) causes some breakage somewhere.
>From gcc-bugs-return-628406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:52:48 2019
Return-Path: <gcc-bugs-return-628406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130488 invoked by alias); 8 Jan 2019 21:52:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130409 invoked by uid 48); 8 Jan 2019 21:52:43 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-Pl1aCmMiAV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01215.txt.bz2
Content-length: 343
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #10 from Jürgen Reuter <juergen.reuter at desy dot de> ---
The trunk, svn 267657, all newest versions of gmp, mpfr, mpc. It seems that the
problem is also solved when I use the libtool flag -static instead of
-static-libtool-libs for libtool to build these executables.
>From gcc-bugs-return-628407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 21:56:06 2019
Return-Path: <gcc-bugs-return-628407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5254 invoked by alias); 8 Jan 2019 21:56: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 5140 invoked by uid 48); 8 Jan 2019 21:56:02 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88678] [9 regression] Many gfortran.dg/ieee/ieee_X.f90 test cases fail starting with r267465
Date: Tue, 08 Jan 2019 21:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88678-4-Utl2Ym37WK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88678-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01216.txt.bz2
Content-length: 1386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88678
--- Comment #7 from kargl at gcc dot gnu.org ---
(In reply to Peter Bergner from comment #5)
> Hmm, the test case is explicitly adding the options
> -ffpe-trap=overflow,invalid, so is this a test case error? We tell it to
> trap on invalid fp operations which we force it to do when generating the
> signaling nan value. Removing the above option allows the reduced test case
> to not die.
>
> bergner@pike:~/gcc/BUGS/PR88678$ gfortran -ffpe-trap=invalid -static bug.f90
> bergner@pike:~/gcc/BUGS/PR88678$ ./a.out
>
> Program received signal SIGFPE: Floating-point exception - erroneous
> arithmetic operation.
>
> Backtrace for this error:
> #0 0x10001b1b
> Floating point exception
> bergner@pike:~/gcc/BUGS/PR88678$ gfortran -static bug.f90
> bergner@pike:~/gcc/BUGS/PR88678$ ./a.out
> bergner@pike:~/gcc/BUGS/PR88678$
The testcase is correct. It appears that powerpc is
claiming that it has the ability for a user to manipulate
the floating-point exception handling, but it appears
something is going sideways. This is why all ieee testcases
are now failing only on powerpc64.
See my comment #3. I assume that fpu-target.h is pulling
in libgfortran/config/fpu-glibc.h, and either that file
is broken or as your backtrace in comment #2 suggests
sysdeps/powerpc/fpu/feenablxcpt.c is broken.
>From gcc-bugs-return-628408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:01:23 2019
Return-Path: <gcc-bugs-return-628408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11912 invoked by alias); 8 Jan 2019 22:01:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10922 invoked by uid 48); 8 Jan 2019 22:00:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 08 Jan 2019 22:01: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-830Ey4nxdI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01217.txt.bz2
Content-length: 932
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Thanks.
So, can you for that sort.i do -da -fdump-tree-all when compiled both with
stage1 and stage2 and see where things start to differ?
Or, try to change either:
STAGE1_TFLAGS += -fno-checking
STAGE2_CFLAGS += -fno-checking
STAGE2_TFLAGS += -fno-checking
in toplevel Makefile.in to -fchecking=1 or
STAGE3_CFLAGS += -fchecking=1
STAGE3_TFLAGS += -fchecking=1
after it to -fno-checking and see if the comparison failures go away. That
would verify your -fno-checking idea. If that proves to be true, where
sort.i.* starts to differ could hint on what TU from stage1 or stage2 could be
rebuilt with -fno-checking or -fchecking=1 to see if the difference goes away.
Or do a binary search among *.o files.
Sorry I can't help more, but this really isn't debuggable with cross-compilers.
>From gcc-bugs-return-628409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:01:27 2019
Return-Path: <gcc-bugs-return-628409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12594 invoked by alias); 8 Jan 2019 22:01:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11762 invoked by uid 48); 8 Jan 2019 22:01:04 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 22:01: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: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-icR9rlGFGx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01218.txt.bz2
Content-length: 660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #10)
> The trunk, svn 267657, all newest versions of gmp, mpfr, mpc. It seems that
> the problem is also solved when I use the libtool flag -static instead of
> -static-libtool-libs for libtool to build these executables.
Thanks, can you identify a "working" svn #?
Is it possible to attach a transcript of the build(s) with the three cases -
two working and one not?
We did make a number of commits over Christmas and, if there's a regression,
would like to pin it down as soon as possible.
>From gcc-bugs-return-628410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:03:37 2019
Return-Path: <gcc-bugs-return-628410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50390 invoked by alias); 8 Jan 2019 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 50110 invoked by uid 48); 8 Jan 2019 22:03:31 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 22:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-q8pKYextBQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01219.txt.bz2
Content-length: 284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #12 from Jürgen Reuter <juergen.reuter at desy dot de> ---
No, unfortunately a working svn # is difficult, I first observed it by doing
svn up on another Macbook around Christmas. What do you mean by transcripts?
>From gcc-bugs-return-628411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:06:30 2019
Return-Path: <gcc-bugs-return-628411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54336 invoked by alias); 8 Jan 2019 22:06:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54183 invoked by uid 48); 8 Jan 2019 22:06:25 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 22: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-thjdaI9ddO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01220.txt.bz2
Content-length: 522
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #12)
> No, unfortunately a working svn # is difficult, I first observed it by doing
> svn up on another Macbook around Christmas.
hmm ... that's tricky - a busy time .. so looks like well have to try to
detective work.
> What do you mean by transcripts?
the output of the build process, for a clean build (most interesting will be
link lines etc.) ..
>From gcc-bugs-return-628412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:26:40 2019
Return-Path: <gcc-bugs-return-628412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96999 invoked by alias); 8 Jan 2019 22:26:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93233 invoked by uid 48); 8 Jan 2019 22:26:33 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Tue, 08 Jan 2019 22:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-hAP0mLeSby@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01221.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #22 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Is it really pure RTL, therefore not used in tree? So the above patch using
> BITS_BIG_ENDIAN for tree stuff would be incorrect to use it?
I wouldn't say incorrect, just inappropriate and unnecessary. And, yes, it
isn't used at the tree level and should stay so IMO. BYTES_BIG_ENDIAN alone
already implicitly enforces a numbering on bits.
>From gcc-bugs-return-628413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:31:02 2019
Return-Path: <gcc-bugs-return-628413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1941 invoked by alias); 8 Jan 2019 22:31: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 125327 invoked by uid 55); 8 Jan 2019 22:30:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/79593] [7/8/9 Regression] Poor/Worse code generation for FPU on versions after 6
Date: Tue, 08 Jan 2019 22:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79593-4-fgkIdLdbZo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79593-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01222.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79593
--- Comment #25 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 8 22:29:56 2019
New Revision: 267740
URL: https://gcc.gnu.org/viewcvs?rev=267740&root=gcc&view=rev
Log:
PR rtl-optimization/79593
* config/i386/i386.md (reg = mem; mem = reg): New define_peephole2.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
>From gcc-bugs-return-628414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:33:40 2019
Return-Path: <gcc-bugs-return-628414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107749 invoked by alias); 8 Jan 2019 22: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 107690 invoked by uid 55); 8 Jan 2019 22:33:36 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88538] parse error with class nontype template parameter
Date: Tue, 08 Jan 2019 22:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88538-4-j6LMsVhu9c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01223.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88538
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Tue Jan 8 22:33:04 2019
New Revision: 267741
URL: https://gcc.gnu.org/viewcvs?rev=267741&root=gcc&view=rev
Log:
PR c++/88538 - braced-init-list in template-argument-list.
* parser.c (cp_parser_template_argument): Handle braced-init-list when
in C++20.
* g++.dg/cpp2a/nontype-class11.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/nontype-class11.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/parser.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:33:52 2019
Return-Path: <gcc-bugs-return-628415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108622 invoked by alias); 8 Jan 2019 22:33:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108438 invoked by uid 48); 8 Jan 2019 22:33:47 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 22:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-lDQTVREQc9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01224.txt.bz2
Content-length: 3974
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #14 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Well, it seems that r267488 from Dec 31 was still working, on the other hand, I
saw a problem on the other MACbook definitely around at latest Dec 26 or so.
Probably before Christmas. It might be that small updates did not trigger a
complete recompilation of the trunk?
This one is failing:
gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
static_1.exe .libs/static_1.exe_prclib_dispatcher.o
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
./.libs/static_1_lib.a
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
/usr/local//lib/libHepMC.a -llcio /usr/local/lib/libstdc++.a
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-lm
while that one is working:
gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
static_1.exe .libs/static_1.exe_prclib_dispatcher.o
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
./.libs/static_1_lib.a
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-lSystem -lgcc_ext.10.5 /usr/local//lib/libHepMC.a -lstdc++ -llcio -lm
But that's probably not very helpful for you.
>From gcc-bugs-return-628416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:37:04 2019
Return-Path: <gcc-bugs-return-628416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113622 invoked by alias); 8 Jan 2019 22:37:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113551 invoked by uid 48); 8 Jan 2019 22:36:59 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88538] parse error with class nontype template parameter
Date: Tue, 08 Jan 2019 22:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88538-4-RGNysWDxjk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88538-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01225.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88538
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This should work with GCC 9 now. Thanks for the report Hana!
>From gcc-bugs-return-628417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 22:46:20 2019
Return-Path: <gcc-bugs-return-628417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7034 invoked by alias); 8 Jan 2019 22:46:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6489 invoked by uid 48); 8 Jan 2019 22:46:10 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68426] Simplification of SPREAD with a derived type element is unimplemented
Date: Tue, 08 Jan 2019 22:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-68426-4-BuM2TH7wEZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01226.txt.bz2
Content-length: 986
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68426
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
This deceptively simple patch seems to do the job:
Index: simplify.c
===================================================================
--- simplify.c (Revision 267736)
+++ simplify.c (Arbeitskopie)
@@ -7572,7 +7572,7 @@ gfc_simplify_spread (gfc_expr *source, gfc_expr *d
return NULL;
}
- if (source->expr_type == EXPR_CONSTANT)
+ if (source->expr_type == EXPR_CONSTANT || source->expr_type ==
EXPR_STRUCTURE)
{
gcc_assert (dim == 0);
>From gcc-bugs-return-628418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:01:56 2019
Return-Path: <gcc-bugs-return-628418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46502 invoked by alias); 8 Jan 2019 23:01:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45944 invoked by uid 55); 8 Jan 2019 23:01:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87855] std::optional<T> only copy-constructible if T is trivially copy-constructible
Date: Tue, 08 Jan 2019 23:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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:
Message-ID: <bug-87855-4-XKzmdGU6Xo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01227.txt.bz2
Content-length: 3233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
--- Comment #19 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jan 8 23:00:46 2019
New Revision: 267742
URL: https://gcc.gnu.org/viewcvs?rev=267742&root=gcc&view=rev
Log:
PR libstdc++/87855 fix optional for types with non-trivial copy/move
When the contained value is not trivially copy (or move) constructible
the union's copy (or move) constructor will be deleted, and so the
_Optional_payload delegating constructors are invalid. G++ fails to
diagnose this because it incorrectly performs copy elision in the
delegating constructors. Clang does diagnose it (llvm.org/PR40245).
The solution is to avoid performing any copy (or move) when the
contained value's copy (or move) constructor isn't trivial. Instead the
contained value can be constructed by calling _M_construct. This is OK,
because the relevant constructor doesn't need to be constexpr when the
contained value isn't trivially copy (or move) constructible.
Additionally, this patch removes a lot of code duplication in the
_Optional_payload partial specializations and the _Optional_base partial
specialization, by hoisting it into common base classes.
The Python pretty printer for std::optional needs to be adjusted to
support the new layout. Retain support for the old layout, and add a
test to verify that the support still works.
PR libstdc++/87855
* include/std/optional (_Optional_payload_base): New class template
for common code hoisted from _Optional_payload specializations. Use
a template for the union, to allow a partial specialization for
types with non-trivial destructors. Add constructors for in-place
initialization to the union.
(_Optional_payload(bool, const _Optional_payload&)): Use _M_construct
to perform non-trivial copy construction, instead of relying on
non-standard copy elision in a delegating constructor.
(_Optional_payload(bool, _Optional_payload&&)): Likewise for
non-trivial move construction.
(_Optional_payload): Derive from _Optional_payload_base and use it
for everything except the non-trivial assignment operators, which are
defined as needed.
(_Optional_payload<false, C, M>): Derive from the specialization
_Optional_payload<true, false, false> and add a destructor.
(_Optional_base_impl::_M_destruct, _Optional_base_impl::_M_reset):
Forward to corresponding members of _Optional_payload.
(_Optional_base_impl::_M_is_engaged, _Optional_base_impl::_M_get):
Hoist common members from _Optional_base.
(_Optional_base): Make all members and base class public.
(_Optional_base::_M_get, _Optional_base::_M_is_engaged): Move to
_Optional_base_impl.
* python/libstdcxx/v6/printers.py (StdExpOptionalPrinter): Add
support for new std::optional layout.
* testsuite/libstdc++-prettyprinters/compat.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/std/optional
trunk/libstdc++-v3/python/libstdcxx/v6/printers.py
>From gcc-bugs-return-628419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:05:48 2019
Return-Path: <gcc-bugs-return-628419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61052 invoked by alias); 8 Jan 2019 23:05: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 60991 invoked by uid 48); 8 Jan 2019 23:05:44 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88718] Strange inconsistency between old style and new style definitions of inline functions.
Date: Tue, 08 Jan 2019 23:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed cf_known_to_fail
Message-ID: <bug-88718-4-3foSGHvJrQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01228.txt.bz2
Content-length: 1069
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88718
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-08
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |4.1.3, 4.3.5, 4.4.7, 4.8.5,
| |4.9.4, 5.4.0, 6.4.0, 7.3.0,
| |8.2.0, 9.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. The first test case was never diagnosed. Suppressing the error for
the second test case would be easy but I agree that we want it in both cases so
that the following is diagnosed as well as I think it should be:
static int x;
inline int f (int (*p)[sizeof x])
{
return sizeof *p;
}
>From gcc-bugs-return-628420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:06:21 2019
Return-Path: <gcc-bugs-return-628420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62084 invoked by alias); 8 Jan 2019 23:06:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62031 invoked by uid 55); 8 Jan 2019 23:06:16 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88376] [7/8/9 Regression] ICE in is_illegal_recursion, at fortran/resolve.c:1689
Date: Tue, 08 Jan 2019 23:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88376-4-cFY1zne1pS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01229.txt.bz2
Content-length: 1423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88376
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jan 08, 2019 at 08:35:21PM +0000, janus at gcc dot gnu.org wrote:
>
> --- Comment #2 from janus at gcc dot gnu.org ---
> (In reply to Dominique d'Humieres from comment #1)
> > The change of behavior occurred between revision r258235 (2018-03-04, error)
> > and r258362 (2018-03-08, ICE) and has been back ported to GCC6 and 7.
>
> Based on this information, I'd guess that r258347 is the culprit:
>
> 2018-03-07 Steven G. Kargl <kargl@gcc.gnu.org>
>
> PR fortran/64124
> PR fortran/70409
> * decl.c (gfc_match_char_spec): Try to reduce a charlen to a constant.
>
Index: gcc/fortran/resolve.c
===================================================================
--- gcc/fortran/resolve.c (revision 267735)
+++ gcc/fortran/resolve.c (working copy)
@@ -1686,8 +1686,6 @@ is_illegal_recursion (gfc_symbol* sym, gfc_namespace*
|| gfc_fl_struct (sym->attr.flavor))
return false;
- gcc_assert (sym->attr.flavor == FL_PROCEDURE);
-
/* If we've got an ENTRY, find real procedure. */
if (sym->attr.entry && sym->ns->entries)
proc_sym = sym->ns->entries->sym;
>From gcc-bugs-return-628421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:08:10 2019
Return-Path: <gcc-bugs-return-628421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81618 invoked by alias); 8 Jan 2019 23:08:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79432 invoked by uid 48); 8 Jan 2019 23:08:03 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Tue, 08 Jan 2019 23:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-Ivks0BXzkm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01230.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #15 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #14)
> Well, it seems that r267488 from Dec 31 was still working, on the other
> hand, I saw a problem on the other MACbook definitely around at latest Dec
> 26 or so. Probably before Christmas. It might be that small updates did not
> trigger a complete recompilation of the trunk?
Have you done a complete clean rebuild of both compiler and application?
( partial rebuilds are hard to analyse at the best of times ).
31st is after most of the Darwin-specific changes went in.
I will look at the transcripts tomorrow/
>From gcc-bugs-return-628422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:10:53 2019
Return-Path: <gcc-bugs-return-628422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105641 invoked by alias); 8 Jan 2019 23:10: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 105579 invoked by uid 48); 8 Jan 2019 23:10:49 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88744] class non-type template parameters doesn't work with default template parameters
Date: Tue, 08 Jan 2019 23:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88744-4-Bbay3uWAsv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01231.txt.bz2
Content-length: 941
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88744
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-08
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
But actually this works so I'm not sure if there's anything to be done except
adding the test.
#define SA(X) static_assert((X),#X)
struct S {
int a;
int b;
constexpr S(int, int) : a(1), b(2) { }
};
template<S s = {1, 2}>
struct X {
static constexpr int i = s.a;
static constexpr int j = s.b;
};
X x; // ok, X<{1, 2}>
SA (x.i == 1);
SA (x.j == 2);
>From gcc-bugs-return-628424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:16:36 2019
Return-Path: <gcc-bugs-return-628424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29006 invoked by alias); 8 Jan 2019 23:16:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28737 invoked by uid 55); 8 Jan 2019 23:16:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87431] valueless_by_exception() should unconditionally return false if all the constructors are noexcept
Date: Tue, 08 Jan 2019 23:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87431-4-j3XOsG0O4S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87431-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01233.txt.bz2
Content-length: 1119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87431
--- Comment #16 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jan 8 23:15:49 2019
New Revision: 267743
URL: https://gcc.gnu.org/viewcvs?rev=267743&root=gcc&view=rev
Log:
Pretty printer test fixes and improvements
Test that StdUniquePtrPrinter correctly prints std::unique_ptr objects
using the old layout, prior to the PR libstdc++/77990 changes.
The printer test for a valueless std::variant started to fail because
the PR libstdc++/87431 fix meant it no longer became valueless. Change
the test to use a type that is not trivially copyable, so that the
exception causes it to become valueless.
* testsuite/libstdc++-prettyprinters/compat.cc: Test printer support
for old std::unique_ptr layout.
* testsuite/libstdc++-prettyprinters/cxx17.cc: Fix std::variant test
to become valueless. Add filesystem::path tests.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/cxx17.cc
>From gcc-bugs-return-628423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:16:35 2019
Return-Path: <gcc-bugs-return-628423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28998 invoked by alias); 8 Jan 2019 23:16:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28740 invoked by uid 55); 8 Jan 2019 23:16:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77990] unique_ptr<T, D>::unique_ptr(T*) imposes CopyConstructible on the deleter
Date: Tue, 08 Jan 2019 23: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: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77990-4-9hOVExMxKI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77990-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77990-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01232.txt.bz2
Content-length: 1118
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77990
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Tue Jan 8 23:15:49 2019
New Revision: 267743
URL: https://gcc.gnu.org/viewcvs?rev=267743&root=gcc&view=rev
Log:
Pretty printer test fixes and improvements
Test that StdUniquePtrPrinter correctly prints std::unique_ptr objects
using the old layout, prior to the PR libstdc++/77990 changes.
The printer test for a valueless std::variant started to fail because
the PR libstdc++/87431 fix meant it no longer became valueless. Change
the test to use a type that is not trivially copyable, so that the
exception causes it to become valueless.
* testsuite/libstdc++-prettyprinters/compat.cc: Test printer support
for old std::unique_ptr layout.
* testsuite/libstdc++-prettyprinters/cxx17.cc: Fix std::variant test
to become valueless. Add filesystem::path tests.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/compat.cc
trunk/libstdc++-v3/testsuite/libstdc++-prettyprinters/cxx17.cc
>From gcc-bugs-return-628425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:17:43 2019
Return-Path: <gcc-bugs-return-628425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41716 invoked by alias); 8 Jan 2019 23:17:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38204 invoked by uid 48); 8 Jan 2019 23:17:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87855] std::optional<T> only copy-constructible if T is trivially copy-constructible
Date: Tue, 08 Jan 2019 23: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ville.voutilainen at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87855-4-bgdXwjcVWl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01234.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
--- Comment #20 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 9, but I might make the minimal fix on the gcc-8-branch.
>From gcc-bugs-return-628426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:20:34 2019
Return-Path: <gcc-bugs-return-628426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47562 invoked by alias); 8 Jan 2019 23:20:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47488 invoked by uid 48); 8 Jan 2019 23:20:29 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88744] class non-type template parameters doesn't work with default template parameters
Date: Tue, 08 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88744-4-N0eOA9OmSp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01235.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88744
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Err, this one:
#define SA(X) static_assert((X),#X)
struct S {
int a;
int b;
constexpr S(int a_, int b_) : a{a_}, b{b_} { }
};
template<S s = {1, 2}>
struct X {
static constexpr int i = s.a;
static constexpr int j = s.b;
};
X x; // ok, X<{1, 2}>
X<{3, 4}> x2;
SA (x.i == 1);
SA (x.j == 2);
SA (x2.i == 3);
SA (x2.j == 4);
>From gcc-bugs-return-628427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:55:27 2019
Return-Path: <gcc-bugs-return-628427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97378 invoked by alias); 8 Jan 2019 23:55: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 96977 invoked by uid 55); 8 Jan 2019 23:55:22 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88744] class non-type template parameters doesn't work with default template parameters
Date: Tue, 08 Jan 2019 23:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88744-4-YLOhB74TE9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01236.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88744
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Tue Jan 8 23:54:47 2019
New Revision: 267744
URL: https://gcc.gnu.org/viewcvs?rev=267744&root=gcc&view=rev
Log:
PR c++/88744
* g++.dg/cpp2a/nontype-class12.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp2a/nontype-class12.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 08 23:55:57 2019
Return-Path: <gcc-bugs-return-628428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98265 invoked by alias); 8 Jan 2019 23:55: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 98190 invoked by uid 48); 8 Jan 2019 23:55:51 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88744] class non-type template parameters doesn't work with default template parameters
Date: Tue, 08 Jan 2019 23:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88744-4-9EJvGC2L4p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01237.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88744
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Added.
>From gcc-bugs-return-628429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 00:08:33 2019
Return-Path: <gcc-bugs-return-628429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65018 invoked by alias); 9 Jan 2019 00:08: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 64955 invoked by uid 55); 9 Jan 2019 00:08:28 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88756] [nvptx, openacc] Override too many num_workers in nvptx plugin, instead of erroring out
Date: Wed, 09 Jan 2019 00:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88756-4-AsNU0oXst5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01238.txt.bz2
Content-length: 1471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88756
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Wed Jan 9 00:07:55 2019
New Revision: 267747
URL: https://gcc.gnu.org/viewcvs?rev=267747&root=gcc&view=rev
Log:
[libgomp, testsuite, openacc] Don't use const int for dimensions
Const int is handled differently at -O0 for -xc and -xc++, which can cause
noise
in testsuite/libgomp.oacc-c-c++-common test-cases (which are both run for c and
c++) if const int is used for launch dimensions.
Fix this by using #defines instead.
2019-01-09 Tom de Vries <tdevries@suse.de>
PR target/88756
* testsuite/libgomp.oacc-c-c++-common/reduction-1.c (ng, nw, vl): Use
#define instead of "const int".
* testsuite/libgomp.oacc-c-c++-common/reduction-2.c (ng, nw, vl): Same.
* testsuite/libgomp.oacc-c-c++-common/reduction-3.c (ng, nw, vl): Same.
* testsuite/libgomp.oacc-c-c++-common/reduction-4.c (ng, nw, vl): Same.
* testsuite/libgomp.oacc-c-c++-common/reduction-5.c (ng, nw, vl): Same.
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-1.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-2.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-3.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-4.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/reduction-5.c
>From gcc-bugs-return-628430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 01:04:49 2019
Return-Path: <gcc-bugs-return-628430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57138 invoked by alias); 9 Jan 2019 01:04: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 57070 invoked by uid 55); 9 Jan 2019 01:04:44 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88718] Strange inconsistency between old style and new style definitions of inline functions.
Date: Wed, 09 Jan 2019 01: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: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery 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-88718-4-bmCRd0NPBf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01239.txt.bz2
Content-length: 712
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88718
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Note that there are also such cases as
static int x;
struct s { int a[sizeof(x)]; } inline *f (void) { return 0; }
where the reference to x is part of the return type (still syntactically
part of the inline definition, so I think still included in what should be
diagnosed). So it will be necessary to track references to identifiers
with internal linkage in such contexts which might or might not turn out
to be part of an inline definition - not just (for example) in what might
or might not be a function prototype scope for an inline function.
>From gcc-bugs-return-628431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 01:35:30 2019
Return-Path: <gcc-bugs-return-628431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124490 invoked by alias); 9 Jan 2019 01:35:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124403 invoked by uid 55); 9 Jan 2019 01:35:23 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] ICE in reference_record with data statement
Date: Wed, 09 Jan 2019 01:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86322-4-cDdMjWPeVY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01240.txt.bz2
Content-length: 2664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jan 08, 2019 at 09:40:29PM +0000, sgk at troutmask dot
apl.washington.edu wrote:
>
> Naw, it is is not due to my patch. Rather my patch has
> exposed or uncovered a bug in gfortran. gfortran needs
> to check
>
> F2018:C877 (R839) A data-i-do-object or a variable that appears as a
> data-stmt-object shall not be an object designator in which a pointer
> appears other than as the entire rightmost part-ref .
>
> In decl.c (gfc_match_data), gfortran needs a check for C877.
> I haven't gotten around to fixing this yet, and I likely won't
> for the foreseeable future.
>
Index: gcc/fortran/decl.c
===================================================================
--- gcc/fortran/decl.c (revision 267735)
+++ gcc/fortran/decl.c (working copy)
@@ -655,6 +655,15 @@ gfc_match_data (void)
"near %C in DATA statement");
goto cleanup;
}
+
+ if (e->symtree->n.sym->ts.type == BT_DERIVED
+ && e->symtree->n.sym->attr.pointer
+ && e->ref->type == REF_COMPONENT)
+ {
+ gfc_error ("part-ref with pointer attribute near %L is not "
+ "rightmost component of data-stmt-object", &e->where);
+ goto cleanup;
+ }
}
m = top_val_list (new_data);
The above is marginally correct. It may be a starting point for
someone who cares about this bug and wants to fix it. The patch
checks if the leftmost part-ref has the pointer attribute and
the variable is a REF_COMPONENT, which means that a part-ref
other than the rightmost component has the pointer attribute.
This is the simple case. A better patch would need to check
each part-ref for the pointer attribute. That is none of a, b,
c, d, or e in a%b%c%d%e%i can have a pointer attribute.
Note, this works
program bar
type a
integer, pointer :: i
end type a
type b
type(a) j
end type b
integer, target, save :: k = 42
type(b) x
data x%j%i/k/
print *, x%j%i
end program bar
This gives an ICE like the one reported in this PR. 'j'
has the pointer attribute and so the program should be
rejected.
program bah
type a
integer :: i
end type a
type b
type(a), pointer :: j
end type b
integer, target, save :: k = 42
type(b) x
data x%j%i /k/
print *, x%j%i
end program bah
>From gcc-bugs-return-628432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 03:05:54 2019
Return-Path: <gcc-bugs-return-628432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71196 invoked by alias); 9 Jan 2019 03:05: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 71072 invoked by uid 48); 9 Jan 2019 03:05:49 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88718] Strange inconsistency between old style and new style definitions of inline functions.
Date: Wed, 09 Jan 2019 03:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
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 assigned_to
Message-ID: <bug-88718-4-wj2pmTwIOJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01241.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88718
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Agreed. Thanks for the test case. I'm working on a patch.
>From gcc-bugs-return-628433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 03:51:47 2019
Return-Path: <gcc-bugs-return-628433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24074 invoked by alias); 9 Jan 2019 03:51:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20481 invoked by uid 48); 9 Jan 2019 03:51:41 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87214] [9 Regression] r263772 miscompiled 520.omnetpp_r in SPEC CPU 2017
Date: Wed, 09 Jan 2019 03:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution short_desc
Message-ID: <bug-87214-4-ywzqSoScJI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01242.txt.bz2
Content-length: 5406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87214
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
CC| |crazylht at gmail dot com,
| |wei3.xiao at intel dot com,
| |xuepeng.guo at intel dot com
Resolution|WORKSFORME |---
Summary|[9 Regression] SPEC |[9 Regression] r263772
|CPU2017, CPU2006 520/620, |miscompiled 520.omnetpp_r
|403 runfails after r263772 |in SPEC CPU 2017
|with march=skylake-avx512 |
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
On Intel machine with AVX512F, r263772 miscompiled 520.omnetpp_r in SPEC
CPU 2017 with
-DSPEC -DSPEC_CPU -DNDEBUG -Isimulator/platdep -Isimulator -Imodel
-DWITH_NETBUILDER -DSPEC_AUTO_SUPPRESS_OPENMP -fno-unsafe-math-optimizations
-mfpmath=sse -g -march=native -Ofast -funroll-loops -flto -DSPEC_LP64
Program received signal SIGSEGV, Segmentation fault.
0x00000000004a8ddb in cObject::isName (s=<optimized out>, this=<optimized out>)
at simulator/cobject.h:118
118 bool isName(const char *s) const {return !opp_strcmp(getName(),s);}
(gdb) bt
#0 0x00000000004a8ddb in cObject::isName (s=<optimized out>,
this=<optimized out>) at simulator/cobject.h:118
#1 cComponent::findPar (this=0x699040, parname=0x669c58 "bs")
at simulator/ccomponent.cc:143
#2 0x00000000004acdb4 in cComponent::par (this=0x699040,
parname=0x669c58 "bs") at simulator/ccomponent.cc:133
#3 0x00000000004be27c in cNEDNetworkBuilder::doParam (this=0x7fffffffd500,
component=0x699040, paramNode=0x669bd0, isSubcomponent=<optimized out>)
at simulator/cnednetworkbuilder.cc:179
#4 0x00000000004c0020 in cNEDNetworkBuilder::doParams (isSubcomponent=false,
paramsNode=<optimized out>, component=0x699040, this=0x7fffffffd500)
at simulator/cnednetworkbuilder.cc:139
#5 cNEDNetworkBuilder::addParametersAndGatesTo (this=0x7fffffffd500,
component=0x699040, decl=0x695e60) at simulator/cnednetworkbuilder.cc:105
#6 0x000000000048a1bd in cDynamicModuleType::addParametersAndGatesTo (
module=0x699040, this=<optimized out>)
at /export/ssd/git/gcc-test-spec/usr/include/c++/9.0.0/bits/stl_tree.h:211
#7 cModuleType::create (this=<optimized out>, modname=<optimized out>,
parentmod=<optimized out>, vectorsize=<optimized out>,
index=<optimized out>) at simulator/ccomponenttype.cc:156
#8 0x00000000004643aa in cModuleType::create (parentmod=0x0,
modname=<optimized out>, this=<optimized out>)
at simulator/ccomponenttype.cc:106
--Type <RET> for more, q to quit, c to continue without paging--
#9 cSimulation::setupNetwork (network=<optimized out>, this=<optimized out>)
at simulator/csimulation.cc:369
#10 Cmdenv::run (this=0x624d80) at simulator/cmdenv.cc:253
#11 0x000000000051673c in EnvirBase::run (this=0x624d80, argc=<optimized out>,
argv=<optimized out>, configobject=0x61a640) at simulator/envirbase.cc:230
#12 0x00000000004421b2 in setupUserInterface(int, char**, cConfiguration*)
[clone .constprop.0] (argc=argc@entry=5, argv=argv@entry=0x7fffffffdc18,
cfg=0x0)
at simulator/startup.cc:234
#13 0x000000000042f2fd in main (argc=5, argv=0x7fffffffdc18)
at simulator/main.cc:39
(gdb)
...
0x00000000004a8db5 <+325>: lea 0x1(%r15),%rbx
0x00000000004a8db9 <+329>: mov 0x58(%rbp),%r8
0x00000000004a8dbd <+333>: lea (%rbx,%rbx,2),%rdi
0x00000000004a8dc1 <+337>: lea (%r8,%rdi,8),%rdi
0x00000000004a8dc5 <+341>: mov (%rdi),%r9
0x00000000004a8dc8 <+344>: mov %ebx,%r12d
0x00000000004a8dcb <+347>: mov 0x30(%r9),%rax
0x00000000004a8dcf <+351>: cmp $0x4a8080,%rax
0x00000000004a8dd5 <+357>: je 0x4a8d20 <cComponent::findPar(char
const*) const+176>
=> 0x00000000004a8ddb <+363>: callq *%rax
0x00000000004a8ddd <+365>: mov %rax,%rdi
0x00000000004a8de0 <+368>: test %rax,%rax
0x00000000004a8de3 <+371>: jne 0x4a8d47 <cComponent::findPar(char
const*) const+215>
0x00000000004a8de9 <+377>: cmpb $0x0,0x0(%r13)
0x00000000004a8dee <+382>: jne 0x4a8d57 <cComponent::findPar(char
const*) const+231>
0x00000000004a8df4 <+388>: add $0x8,%rsp
0x00000000004a8df8 <+392>: pop %rbx
0x00000000004a8df9 <+393>: pop %rbp
0x00000000004a8dfa <+394>: mov %r12d,%eax
0x00000000004a8dfd <+397>: pop %r12
0x00000000004a8dff <+399>: pop %r13
0x00000000004a8e01 <+401>: pop %r14
0x00000000004a8e03 <+403>: pop %r15
0x00000000004a8e05 <+405>: retq
0x00000000004a8e06 <+406>: nopw %cs:0x0(%rax,%rax,1)
0x00000000004a8e10 <+416>: callq *%rax
0x00000000004a8e12 <+418>: mov %rax,%rdi
--Type <RET> for more, q to quit, c to continue without paging--q
Quit
(gdb) p/x $rax
$1 = 0x5c8d480000009b85
(gdb) p/x *(long *) $rax
Cannot access memory at address 0x5c8d480000009b85
(gdb)
This address looks odd.
>From gcc-bugs-return-628434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 03:51:47 2019
Return-Path: <gcc-bugs-return-628434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24219 invoked by alias); 9 Jan 2019 03:51:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21467 invoked by uid 48); 9 Jan 2019 03:51:42 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Wed, 09 Jan 2019 03:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-26163-4-GltVuQoOza@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01243.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 87214, which changed state.
Bug 87214 Summary: [9 Regression] r263772 miscompiled 520.omnetpp_r in SPEC CPU 2017
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87214
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|WORKSFORME |---
>From gcc-bugs-return-628435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 04:28:11 2019
Return-Path: <gcc-bugs-return-628435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34945 invoked by alias); 9 Jan 2019 04:28: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 34742 invoked by uid 48); 9 Jan 2019 04:28:06 -0000
From: "metalcaedes at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87436] [7 Regression] G++ produces >300MB .rodata section to initialize struct with big array
Date: Wed, 09 Jan 2019 04:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: compile-time-hog, memory-hog, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: metalcaedes at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87436-4-JsmJ9kEmsO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87436-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01244.txt.bz2
Content-length: 161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87436
--- Comment #13 from Daniel Gibson <metalcaedes at gmail dot com> ---
Great, thanks a lot for fixing this!
>From gcc-bugs-return-628436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 05:12:18 2019
Return-Path: <gcc-bugs-return-628436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85942 invoked by alias); 9 Jan 2019 05:12: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 85890 invoked by uid 48); 9 Jan 2019 05:12:13 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 05:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-yaWuHg9usR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01245.txt.bz2
Content-length: 876
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #16 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Yes, after the problem occurred, I did a completely clean new build of gmp,
mpfr, mpc, gcc (configured with ../configure --prefix=/usr/local/
--with-gmp=/usr/local/ --with-mpfr=/usr/local/ --with-mpc=/usr/local/
--enable-checking=release --enable-languages=c,c++,fortran,lto),
all the tools our software depends, and our software. It turns out that
external C++ libraries linked into our (Fortran) project via bind(C) are not a
problem if they have been built via libtool, such that a .dylib, a .a and a .la
file are present. The two projects that have problem either exist as .dylib and
.a produced by hand-written configure and makefiles (i.e. not using autotools),
or only as dynamic libraries produced via cmake and make.
>From gcc-bugs-return-628437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 05:48:00 2019
Return-Path: <gcc-bugs-return-628437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62872 invoked by alias); 9 Jan 2019 05:48:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62738 invoked by uid 48); 9 Jan 2019 05:47:55 -0000
From: "npiggin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88765] New: powerpc64le-linux-gnu sub-optimal code generation for builtin atomic ops
Date: Wed, 09 Jan 2019 05:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: npiggin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01246.txt.bz2
Content-length: 3140
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88765
Bug ID: 88765
Summary: powerpc64le-linux-gnu sub-optimal code generation for
builtin atomic ops
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: npiggin at gmail dot com
Target Milestone: ---
Target: powerpc64le-linux-gnu
gcc version 8.2.0 (Debian 8.2.0-4)
Linux uses a lot of non-trivial operations, and implementing them with
compare_exchange results in sub-optimal code generation. A common one is
add_unless_zero, which is commonly used with RCU to take a reference count, or
fail if the last reference had already gone (which is a very rare case).
---
#include <stdbool.h>
bool add_unless_zero(unsigned long *mem, unsigned long inc)
{
unsigned long val;
do {
val = __atomic_load_n(mem, __ATOMIC_RELAXED);
if (__builtin_expect(val == 0, false))
return false;
} while (__builtin_expect(!__atomic_compare_exchange_n(mem,
&val, val + inc, true,
__ATOMIC_RELAXED, __ATOMIC_RELAXED), false));
return true;
}
---
This compiles to:
add_unless_zero:
.L4:
ld 10,0(3)
cmpdi 7,10,0
add 8,10,4
beq 7,.L5
ldarx 9,0,3
cmpd 0,9,10
bne 0,.L3
stdcx. 8,0,3
.L3:
bne 0,.L4
li 3,1
blr
.L5:
li 3,0
blr
Better would be
add_unless_zero:
.L4:
ldarx 9,0,3
cmpdi 0,9,0
add 9,9,4
bne 0,.L5
stdcx. 8,0,3
bne 0,.L4
li 3,1
blr
.L5:
li 3,0
blr
Using extended inline asm to implement these is an adequate workaround.
Unfortunately that does not work on 128 bit powerpc because no register pair
constraint, and much worse code generation with builtins. Changing types to
__int128_t gives a bad result:
add_unless_zero:
lq 10,0(3)
mr 6,3
or. 9,10,11
addc 3,11,4
mr 7,11
adde 11,10,5
beq 0,.L16
std 28,-32(1)
std 29,-24(1)
std 30,-16(1)
std 31,-8(1)
.L12:
lqarx 28,0,6
xor 9,29,7
xor 10,28,10
or. 9,9,10
bne 0,.L4
mr 30,11
mr 31,3
stqcx. 30,0,6
.L4:
mfcr 3,128
rlwinm 3,3,3,1
bne 0,.L17
.L2:
ld 28,-32(1)
ld 29,-24(1)
ld 30,-16(1)
ld 31,-8(1)
blr
.L17:
lq 10,0(6)
or. 9,10,11
addc 3,11,4
mr 7,11
adde 11,10,5
bne 0,.L12
li 3,0
b .L2
.L16:
li 3,0
blr
Closer to ideal would be
add_unless_zero:
.Lagain:
lqarx 6,0,3
or. 8,6,7
addc 6,6,4
adde 7,7,5
beq 0,.Lfail
stqcx. 6,0,3
bne 0,.Lagain
li 3,1
blr
.Lfail:
li 3,0
blr
>From gcc-bugs-return-628438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 06:54:51 2019
Return-Path: <gcc-bugs-return-628438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123281 invoked by alias); 9 Jan 2019 06:54:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115008 invoked by uid 48); 9 Jan 2019 06:54:45 -0000
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 06:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dongjianqiang2 at huawei dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-uRVfoeRrPa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01247.txt.bz2
Content-length: 1257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #23 from John Dong <dongjianqiang2 at huawei dot com> ---
diff -urp a/gcc/expr.c b/gcc/expr.c
--- a/gcc/expr.c 2019-01-09 03:19:03.750205982 +0800
+++ b/gcc/expr.c 2019-01-09 03:38:23.414174738 +0800
@@ -10760,6 +10760,16 @@ expand_expr_real_1 (tree exp, rtx target
&& GET_MODE_CLASS (ext_mode) == MODE_INT)
reversep = TYPE_REVERSE_STORAGE_ORDER (type);
+ int modePrecision = GET_MODE_PRECISION (TYPE_MODE (TREE_TYPE
(tem)));
+ int typePrecision = TYPE_PRECISION (TREE_TYPE (tem));
+ int shiftSize = modePrecision - typePrecision;
+ rtx regTarget = gen_reg_rtx (GET_MODE (op0));
+
+ if (shiftSize && REG_P (op0))
+ op0 = expand_shift (LSHIFT_EXPR, GET_MODE (op0), op0,
+ shiftSize, regTarget,
+ TYPE_UNSIGNED (TREE_TYPE (tem)));
+
op0 = extract_bit_field (op0, bitsize, bitpos, unsignedp,
(modifier == EXPAND_STACK_PARM
? NULL_RTX : target),
Tried to fix the bug when expand.
>From gcc-bugs-return-628439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 07:26:43 2019
Return-Path: <gcc-bugs-return-628439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70098 invoked by alias); 9 Jan 2019 07:26: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 70035 invoked by uid 48); 9 Jan 2019 07:26:39 -0000
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86979] [9 Regression] ICE: in maybe_record_trace_start, at dwarf2cfi.c:2348 with -m32 on darwin
Date: Wed, 09 Jan 2019 07:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: abel at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: abel at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86979-4-SLRkPqbSqy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86979-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86979-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01248.txt.bz2
Content-length: 1081
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86979
--- Comment #9 from Andrey Belevantsev <abel at gcc dot gnu.org> ---
Eric, thanks for pointing me out to the old PR. From that and what I could
understand here from the sched logs, it's not clear to me how to correctly
clone REG_ARGS_SIZE insns, so the safest patch of forbidding that completely
works fine. Alexander, if you have an idea of what can be checked in the
scheduler to relax that, please let me know, I'm happy to implement that.
The safe patch is just like this:
diff --git a/gcc/sel-sched-ir.c b/gcc/sel-sched-ir.c
index 85ff5bd3eb4..05d7eaa72c7 100644
--- a/gcc/sel-sched-ir.c
+++ b/gcc/sel-sched-ir.c
@@ -3024,6 +3024,10 @@ init_global_and_expr_for_insn (insn_t insn)
else
force_unique_p = false;
+ /* Do not copy REG_ARGS_SIZE insns as we fail to adjust them properly
(PR86979). */
+ if (find_reg_note (insn, REG_ARGS_SIZE, NULL))
+ force_unique_p = true;
+
if (targetm.sched.get_insn_spec_ds)
{
spec_done_ds = targetm.sched.get_insn_spec_ds (insn);
>From gcc-bugs-return-628440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 07:29:59 2019
Return-Path: <gcc-bugs-return-628440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88319 invoked by alias); 9 Jan 2019 07:29: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 88285 invoked by uid 89); 9 Jan 2019 07:29:57 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: =?ISO-8859-1?Q?Yes, score=7.5 required=5.0 testsºYES_80,BODY_8BITS,GARBLED_BODY,GIT_PATCH_3,HTML_MESSAGE,KAM_LAZY_DOMAIN_SECURITY,MISSING_MID,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_XBL,TVD_SPACE_RATIO_MINFP autolearn=no version=3.3.2 spammy=Hx-spam-relays-external:SKY-20150219JSJ, H*RU:SKY-20150219JSJ, H*r:SKY-20150219JSJ, °æ£è§?X-HELO: bhls.com
Received: from Unknown (HELO bhls.com) (114.99.29.21) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 09 Jan 2019 07:29:55 +0000
Received: from SKY-20150219JSJ ([127.0.0.1]) by localhost via TCP with ESMTPA; Wed, 09 Jan 2019 15:29:38 +0800
MIME-Version: 1.0
From: ootza <ootza@bhls.com>
Sender: ootza <ootza@bhls.com>
To: gcc-bugs@gcc.gnu.org
Date: Wed, 09 Jan 2019 07:29:00 -0000
Subject: =?utf-8?B?56iOKysr56WoKysr5LiaKyvliqE=?Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-SW-Source: 2019-01/txt/msg01249.txt.bz2
Content-length: 326
Z2NjLWJ1Z3NAZ2NjLmdudS5vcmcNCisrKysrKysrKysrKysrKysrKysrKysr
KysrKysrDQrlvIDlkITlnLDmraPop4Tmma7pgJrnqI7npajvvIzngrnkvJjm
g6DvvIzljIXnnJ/jgIINCuivpueUte+8mui1teWwj+WnkA0K5omL5py677ya
MTM2LTIwMi0xNzYtMDUNCuS4muWKoVFR77yaMTAwNy0yNTUtMDkwDQorKysr
KysrKysrKysrKysrKysrKysrKysrKysrKysxNToyOQ0K55qu6ZOc5YWz5LmD
5q+r5Yqf6YCP5Yqf6Lms
>From gcc-bugs-return-628441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 08:09:48 2019
Return-Path: <gcc-bugs-return-628441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93168 invoked by alias); 9 Jan 2019 08:09:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93089 invoked by uid 48); 9 Jan 2019 08:09:43 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 08:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-fbZXSjVcBg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01250.txt.bz2
Content-length: 1988
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #17 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #16)
> Yes, after the problem occurred, I did a completely clean new build of gmp,
> mpfr, mpc, gcc (configured with ../configure --prefix=/usr/local/
> --with-gmp=/usr/local/ --with-mpfr=/usr/local/ --with-mpc=/usr/local/
> --enable-checking=release --enable-languages=c,c++,fortran,lto),
> all the tools our software depends, and our software.
OK, FWIW (thinking a bit more last night) if you examine the logs from building
GCC, you will see the same linker complaint in the log for building
libstdc++.dylib. Which kinda reinforces the expectation that this is not the
source of the problem. However, I'm thinking to try and construct some small
experiment to check that the newer ld64 doesn't do something active as well as
complain.
> It turns out that
> external C++ libraries linked into our (Fortran) project via bind(C)
I might be wrong, but suspect there was some change to the C binding around
that time too - but I also recall seeing a recent patch go by to fix a problem
in that area (but not sure if it's been applied yet). Will let Dominique
comment on that.
> are not
> a problem if they have been built via libtool, such that a .dylib, a .a and
> a .la file are present. The two projects that have problem either exist as
> .dylib and .a produced by hand-written configure and makefiles (i.e. not
> using autotools), or only as dynamic libraries produced via cmake and make.
That's an interesting observation, what we need is to find the specific
difference in the output exe.
* Narrowing this down by knowing where and what causes the problem will become
important at some point - so a debug build and lldb session could be a useful
next step.
* as a general rule, it's also useful to see if an -O0 build exhibits the
problem - in case its an optimisation issue.
>From gcc-bugs-return-628442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 08:31:25 2019
Return-Path: <gcc-bugs-return-628442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45149 invoked by alias); 9 Jan 2019 08:31: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 44856 invoked by uid 48); 9 Jan 2019 08:31:18 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Wed, 09 Jan 2019 08:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88758-4-1ssMjfLlEE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01251.txt.bz2
Content-length: 2284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
What about this:
$ cat 11.i
void PreEvaluate(void);
int main() { PreEvaluate(); return 0; }
$ cat 22.i
cat 22.i
extern int a[];
int b;
int c;
void PreEvaluate(void) {
b = 0;
for (; b < 8; b++)
a[b] = c * (b > 0 ? b - 1 : 0);
}
$ gcc-8 11.i 22.i -flto -O3 -shared -fPIC
$ gcc 11.i 22.i -flto -O3 -shared -fPIC
during GIMPLE pass: dom
22.i: In function ‘PreEvaluate’:
22.i:5:6: internal compiler error: Segmentation fault
5 | void PreEvaluate(void) {
| ^
0xc186df crash_signal
/home/marxin/Programming/gcc/gcc/toplev.c:326
0x7ffff6d8910f ???
/usr/src/debug/glibc-2.27-6.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0xeb6184 location_wrapper_p(tree_node const*)
/home/marxin/Programming/gcc/gcc/tree.h:3807
0xeb6184 tree_strip_any_location_wrapper(tree_node*)
/home/marxin/Programming/gcc/gcc/tree.h:3819
0xeb6184 initializer_each_zero_or_onep(tree_node const*)
/home/marxin/Programming/gcc/gcc/tree.c:11239
0xeb6264 initializer_each_zero_or_onep(tree_node const*)
/home/marxin/Programming/gcc/gcc/tree.c:11259
0x1083fcf gimple_simplify_MULT_EXPR
/dev/shm/objdir/gcc/gimple-match.c:47953
0xfa636f gimple_simplify
/dev/shm/objdir/gcc/gimple-match.c:90161
0xfa79a3 gimple_resimplify2(gimple**, gimple_match_op*, tree_node*
(*)(tree_node*))
/home/marxin/Programming/gcc/gcc/gimple-match-head.c:285
0x10bb1df gimple_simplify(gimple*, gimple_match_op*, gimple**, tree_node*
(*)(tree_node*), tree_node* (*)(tree_node*))
/home/marxin/Programming/gcc/gcc/gimple-match-head.c:895
0x98f334 fold_stmt_1
/home/marxin/Programming/gcc/gcc/gimple-fold.c:4934
0xd2c566 dom_opt_dom_walker::optimize_stmt(basic_block_def*,
gimple_stmt_iterator)
/home/marxin/Programming/gcc/gcc/tree-ssa-dom.c:1967
0xd2db2c dom_opt_dom_walker::before_dom_children(basic_block_def*)
/home/marxin/Programming/gcc/gcc/tree-ssa-dom.c:1468
0x13fd3a7 dom_walker::walk(basic_block_def*)
/home/marxin/Programming/gcc/gcc/domwalk.c:353
0xd2e99d execute
/home/marxin/Programming/gcc/gcc/tree-ssa-dom.c:706
>From gcc-bugs-return-628443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 08:40:42 2019
Return-Path: <gcc-bugs-return-628443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57761 invoked by alias); 9 Jan 2019 08:40: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 57703 invoked by uid 48); 9 Jan 2019 08:40:38 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88752] ICE in enclosing_instantiation_of, at cp/pt.c:13328
Date: Wed, 09 Jan 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-88752-4-YLJ4Ce4wF4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01252.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
Matthias Kretz <kretz at kde dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #45376|0 |1
is obsolete| |
--- Comment #4 from Matthias Kretz <kretz at kde dot org> ---
Created attachment 45385
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45385&action=edit
valid code test case
True, I made an error in the verification script. Better reduction attached.
>From gcc-bugs-return-628444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 08:46:58 2019
Return-Path: <gcc-bugs-return-628444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75299 invoked by alias); 9 Jan 2019 08:46: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 75102 invoked by uid 55); 9 Jan 2019 08:46:52 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-nkA9ZkvzGl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01253.txt.bz2
Content-length: 1565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #24 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, dongjianqiang2 at huawei dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
>
> --- Comment #23 from John Dong <dongjianqiang2 at huawei dot com> ---
> diff -urp a/gcc/expr.c b/gcc/expr.c
> --- a/gcc/expr.c 2019-01-09 03:19:03.750205982 +0800
> +++ b/gcc/expr.c 2019-01-09 03:38:23.414174738 +0800
> @@ -10760,6 +10760,16 @@ expand_expr_real_1 (tree exp, rtx target
> && GET_MODE_CLASS (ext_mode) == MODE_INT)
> reversep = TYPE_REVERSE_STORAGE_ORDER (type);
>
> + int modePrecision = GET_MODE_PRECISION (TYPE_MODE (TREE_TYPE
> (tem)));
> + int typePrecision = TYPE_PRECISION (TREE_TYPE (tem));
> + int shiftSize = modePrecision - typePrecision;
> + rtx regTarget = gen_reg_rtx (GET_MODE (op0));
> +
> + if (shiftSize && REG_P (op0))
> + op0 = expand_shift (LSHIFT_EXPR, GET_MODE (op0), op0,
> + shiftSize, regTarget,
> + TYPE_UNSIGNED (TREE_TYPE (tem)));
> +
> op0 = extract_bit_field (op0, bitsize, bitpos, unsignedp,
> (modifier == EXPAND_STACK_PARM
> ? NULL_RTX : target),
>
> Tried to fix the bug when expand.
The bug is clearly in value-numbering, not RTL expansion
>From gcc-bugs-return-628445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 08:49:31 2019
Return-Path: <gcc-bugs-return-628445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95599 invoked by alias); 9 Jan 2019 08:49:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93938 invoked by uid 48); 9 Jan 2019 08:48:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Wed, 09 Jan 2019 08:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-JUDxYJUH1l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01254.txt.bz2
Content-length: 2988
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #19 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #18)
> So for find_base_term to compute sth conservative we'd need to track
> RTX_SURELY_NON_POINTER (what RTX is surely _not_ based on a pointer
> and thus can be ignored). And when find_base_term ever figures
> two bases in say a PLUS it has to conservatively return 0.
>
> I fear the existing REG_POINTER does not help at all. For the testcase
> we have
>
> (plus:DI (reg:DI 83 [ d.0_2 ])
> (symbol_ref:DI ("y") [flags 0x2] <var_decl 0x7ffff7fefb40 y>))
>
> where reg:DI 83 is not marked with REG_POINTER and find_base_term
> doesn't find it to be an alternate base. For the testcase the
> offending MEM has a MEM_EXPR and we have proper points-to info.
>
> IMHO the proper solution is to kill base_alias_check or all problematic
> cases in find_base_term (binary ops with more than one non-CONST_INT
> operand).
>
> And eventually make sure to more properly preserve MEM_EXPRs.
>
> Maybe sth as "simple" as the following which of course fixes the
> testcase but will make find_base_term fail on any variable-indexed
> thing.
>
> diff --git a/gcc/alias.c b/gcc/alias.c
> index 93f53543d12..3a66e10b431 100644
> --- a/gcc/alias.c
> +++ b/gcc/alias.c
> @@ -2009,12 +2009,14 @@ find_base_term (rtx x, vec<std::pair<cselib_val *,
> rtx base = find_base_term (tmp1, visited_vals);
> if (base != NULL_RTX
> && ((REG_P (tmp1) && REG_POINTER (tmp1))
> - || known_base_value_p (base)))
> + || known_base_value_p (base))
> + && CONST_INT_P (tmp2))
> return base;
> base = find_base_term (tmp2, visited_vals);
> if (base != NULL_RTX
> && ((REG_P (tmp2) && REG_POINTER (tmp2))
> - || known_base_value_p (base)))
> + || known_base_value_p (base))
> + && CONST_INT_P (tmp1))
> return base;
>
> /* We could not determine which of the two operands was the
"benchmarking" this by comparing cc1 with/without shows a difference mostly
in scheduling (but the number of differences is comparatively small!). Also
overall text size shrinks with the patch (whatever that means).
On GIMPLE we try hard to not construct addresses "based" on the wrong
object, in fact IVOPTs has code to avoid building IVs based on
things like &a - &b and propagation avoids turning unintptr_t arithmetic
into pointer arithmetic even if it can see the converted from addresses.
All those things cannot be done on RTL since we lost the distinction between
pointers and integers and there's only PLUS.
So I have a _very_ hard time seeing how RTL can ever be fixed to discover
bases for alias analysis purposes without just resorting to MEM_EXPRs.
That is, unless we want to live with this kind of wrong-code bugs.
Similarly fishy is may_be_sp_based_p.
>From gcc-bugs-return-628446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 08:51:22 2019
Return-Path: <gcc-bugs-return-628446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100542 invoked by alias); 9 Jan 2019 08:51:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100402 invoked by uid 48); 9 Jan 2019 08:51:16 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 08:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-PSVw7I5T5z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01255.txt.bz2
Content-length: 1837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #18 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #14)
does the application use exceptions?
> This one is failing:
> gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
> static_1.exe .libs/static_1.exe_prclib_dispatcher.o
<snip>
> /usr/local/lib/libstdc++.a
^^^ please confirm that this is from the "current compiler build".
<snip>
> -L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/
> libsupc++/.libs -lm
^^^^ note - no "-lSystem -lgcc_ext.10.5" (which is what I'd expect).
>
> while that one is working:
>
> gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
> static_1.exe .libs/static_1.exe_prclib_dispatcher.o
<snip>
> libsupc++/.libs -lSystem -lgcc_ext.10.5 /usr/local//lib/libHepMC.a -lstdc++
> -llcio -lm
^^^^^^^ this looks like the build process in this case is adding libs that the
compiler driver normally adds ( they are not present in the case above ).
* If you can extract these two fortran link lines - and then execute them
separately in the build dir with "-v" so that we can see the output of the
compiler-driver's internal link line and what its search paths are.
* According to your posted otool output, the version of libstdc++.dylib that is
bound is the one in /usr/local/lib/ which is where you pick up the static lib
in the non-working case.
* The object files used to build the static (.a) and dynamic (.dylib) versions
of libstdc++ are the same, so we really need to pin down where the issue
occurs.
* DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_BINDINGS=1 <exe>
will show you which libraries are used, and from which library each symbol is
resolved - it probably will produce a lot of output..
>From gcc-bugs-return-628447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 09:22:07 2019
Return-Path: <gcc-bugs-return-628447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27653 invoked by alias); 9 Jan 2019 09:22:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27518 invoked by uid 48); 9 Jan 2019 09:22:02 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87214] [9 Regression] r263772 miscompiled 520.omnetpp_r in SPEC CPU 2017
Date: Wed, 09 Jan 2019 09:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-87214-4-l48pR2gKhW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01256.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87214
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #4 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine then.
>From gcc-bugs-return-628448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 09:38:14 2019
Return-Path: <gcc-bugs-return-628448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100751 invoked by alias); 9 Jan 2019 09:38: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 100644 invoked by uid 55); 9 Jan 2019 09:38:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88204] New test case 26_numerics/complex/operators/more_constexpr.cc from r266416 fails
Date: Wed, 09 Jan 2019 09:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88204-4-ER73NoW4pm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01257.txt.bz2
Content-length: 955
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88204
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Wed Jan 9 09:37:34 2019
New Revision: 267757
URL: https://gcc.gnu.org/viewcvs?rev=267757&root=gcc&view=rev
Log:
PR libstdc++/88204 disable std::complex<long double> tests
The IBM128 long double format isn't foldable in constant expressions, so
conditionally skip the std::complex<long double> cases when they'll
fail.
PR libstdc++/88204
* testsuite/26_numerics/complex/operators/more_constexpr.cc: Do not
test std::complex<long double> if long double format is IBM128.
* testsuite/26_numerics/complex/requirements/more_constexpr.cc:
Likewise.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/testsuite/26_numerics/complex/operators/more_constexpr.cc
trunk/libstdc++-v3/testsuite/26_numerics/complex/requirements/more_constexpr.cc
>From gcc-bugs-return-628449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:01:21 2019
Return-Path: <gcc-bugs-return-628449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87134 invoked by alias); 9 Jan 2019 10:01: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 86406 invoked by uid 48); 9 Jan 2019 10:01:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Wed, 09 Jan 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88763-4-nB1rUaU6md@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01258.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
CC| |dmalcolm at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I guess the logging should be switched to dump_* so that -fopt-info- can
report these.
>From gcc-bugs-return-628450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:02:55 2019
Return-Path: <gcc-bugs-return-628450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89563 invoked by alias); 9 Jan 2019 10:02:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89475 invoked by uid 48); 9 Jan 2019 10:02:51 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88761] [8/9 Regression] ICE in tsubst_copy, at cp/pt.c:15478 when chaining lambda calls & fold-expressions
Date: Wed, 09 Jan 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: 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 cf_known_to_work version target_milestone short_desc
Message-ID: <bug-88761-4-1Y6T1Funax@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01259.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88761
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Known to work| |7.3.1
Version|8.2.0 |8.2.1
Target Milestone|9.0 |8.3
Summary|[9 Regression] ICE in |[8/9 Regression] ICE in
|tsubst_copy, at |tsubst_copy, at
|cp/pt.c:15478 when chaining |cp/pt.c:15478 when chaining
|lambda calls & |lambda calls &
|fold-expressions |fold-expressions
>From gcc-bugs-return-628451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:03:30 2019
Return-Path: <gcc-bugs-return-628451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122553 invoked by alias); 9 Jan 2019 10:03:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116599 invoked by uid 48); 9 Jan 2019 10:03:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Wed, 09 Jan 2019 10:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88758-4-GhBdOkvB9Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01260.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-628452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:12:14 2019
Return-Path: <gcc-bugs-return-628452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38148 invoked by alias); 9 Jan 2019 10:12:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38108 invoked by uid 48); 9 Jan 2019 10:12:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-n6ZdUkULyr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01261.txt.bz2
Content-length: 2215
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
So LLVM unrolls 4 times while GCC (always) unrolls 8 times. The unrolled body
for GCC (x86_64 this time) is
.L4:
movl (%rdx), %ecx
vmovsd (%rax), %xmm8
addq $32, %rdx
addq $64, %rax
vmovsd -56(%rax), %xmm9
vmovsd -48(%rax), %xmm10
vfmadd231sd (%rsi,%rcx,8), %xmm8, %xmm0
movl -28(%rdx), %ecx
vmovsd -40(%rax), %xmm11
vmovsd -32(%rax), %xmm12
vfmadd231sd (%rsi,%rcx,8), %xmm9, %xmm0
movl -24(%rdx), %ecx
vmovsd -24(%rax), %xmm13
vmovsd -16(%rax), %xmm14
vfmadd231sd (%rsi,%rcx,8), %xmm10, %xmm0
movl -20(%rdx), %ecx
vmovsd -8(%rax), %xmm15
vfmadd231sd (%rsi,%rcx,8), %xmm11, %xmm0
movl -16(%rdx), %ecx
vfmadd231sd (%rsi,%rcx,8), %xmm12, %xmm0
movl -12(%rdx), %ecx
vfmadd231sd (%rsi,%rcx,8), %xmm13, %xmm0
movl -8(%rdx), %ecx
vfmadd231sd (%rsi,%rcx,8), %xmm14, %xmm0
movl -4(%rdx), %ecx
vfmadd231sd (%rsi,%rcx,8), %xmm15, %xmm0
cmpq %rax, %r9
jne .L4
and what you quoted is the prologue. You didn't quote llvms prologue
but if I read my clangs outout correct it uses a loop there.
(is there sth like -fdump-tree-optimized for clang?)
Our RTL unroller cannot do a loopy prologue but it always has this
jump-into peeled copies thing. Using --param max-unroll-times=4
produces
.L4:
movl (%rdx), %ecx
vmovsd (%rax), %xmm2
addq $16, %rdx
addq $32, %rax
vmovsd -24(%rax), %xmm3
vmovsd -16(%rax), %xmm4
vfmadd231sd (%rsi,%rcx,8), %xmm2, %xmm0
movl -12(%rdx), %ecx
vmovsd -8(%rax), %xmm5
vfmadd231sd (%rsi,%rcx,8), %xmm3, %xmm0
movl -8(%rdx), %ecx
vfmadd231sd (%rsi,%rcx,8), %xmm4, %xmm0
movl -4(%rdx), %ecx
vfmadd231sd (%rsi,%rcx,8), %xmm5, %xmm0
cmpq %rax, %r8
jne .L4
which is nearly equivalent to clnags varaint?
>From gcc-bugs-return-628453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:16:48 2019
Return-Path: <gcc-bugs-return-628453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47726 invoked by alias); 9 Jan 2019 10:16:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47668 invoked by uid 55); 9 Jan 2019 10:16:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88331] [9 Regression] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Wed, 09 Jan 2019 10:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-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: 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:
Message-ID: <bug-88331-4-IkFvp1p9JC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01262.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 9 10:16:10 2019
New Revision: 267758
URL: https://gcc.gnu.org/viewcvs?rev=267758&root=gcc&view=rev
Log:
PR rtl-optimization/88331
* function.c (assign_stack_local_1): Don't set dynamic_align_addr if
not currently_expanding_to_rtl.
* gcc.target/i386/pr88331.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr88331.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/function.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:17:53 2019
Return-Path: <gcc-bugs-return-628455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50960 invoked by alias); 9 Jan 2019 10:17: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 50072 invoked by uid 55); 9 Jan 2019 10:17:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87855] std::optional<T> only copy-constructible if T is trivially copy-constructible
Date: Wed, 09 Jan 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ville.voutilainen at gmail dot com
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87855-4-cyvyfVxr1d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01264.txt.bz2
Content-length: 4393
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
--- Comment #22 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Wed Jan 9 10:17:10 2019
New Revision: 267759
URL: https://gcc.gnu.org/viewcvs?rev=267759&root=gcc&view=rev
Log:
PR libstdc++/87855 fix optional for types with non-trivial copy/move
Backport both parts of the fix for PR libstdc++/87855, as well as a test
tweak from r263657 to avoid having to adjust dg-error line numbers.
* testsuite/20_util/optional/cons/value_neg.cc: Change dg-error to
dg-prune-output. Remove unused header.
Backport from mainline
2019-01-08 Jonathan Wakely <jwakely@redhat.com>
When the contained value is not trivially copy (or move) constructible
the union's copy (or move) constructor will be deleted, and so the
_Optional_payload delegating constructors are invalid. G++ fails to
diagnose this because it incorrectly performs copy elision in the
delegating constructors. Clang does diagnose it (llvm.org/PR40245).
The solution is to avoid performing any copy (or move) when the
contained value's copy (or move) constructor isn't trivial. Instead the
contained value can be constructed by calling _M_construct. This is OK,
because the relevant constructor doesn't need to be constexpr when the
contained value isn't trivially copy (or move) constructible.
Additionally, this patch removes a lot of code duplication in the
_Optional_payload partial specializations and the _Optional_base partial
specialization, by hoisting it into common base classes.
The Python pretty printer for std::optional needs to be adjusted to
support the new layout. Retain support for the old layout, and add a
test to verify that the support still works.
PR libstdc++/87855
* include/std/optional (_Optional_payload_base): New class template
for common code hoisted from _Optional_payload specializations. Use
a template for the union, to allow a partial specialization for
types with non-trivial destructors. Add constructors for in-place
initialization to the union.
(_Optional_payload(bool, const _Optional_payload&)): Use _M_construct
to perform non-trivial copy construction, instead of relying on
non-standard copy elision in a delegating constructor.
(_Optional_payload(bool, _Optional_payload&&)): Likewise for
non-trivial move construction.
(_Optional_payload): Derive from _Optional_payload_base and use it
for everything except the non-trivial assignment operators, which are
defined as needed.
(_Optional_payload<false, C, M>): Derive from the specialization
_Optional_payload<true, false, false> and add a destructor.
(_Optional_base_impl::_M_destruct, _Optional_base_impl::_M_reset):
Forward to corresponding members of _Optional_payload.
(_Optional_base_impl::_M_is_engaged, _Optional_base_impl::_M_get):
Hoist common members from _Optional_base.
(_Optional_base): Make all members and base class public.
(_Optional_base::_M_get, _Optional_base::_M_is_engaged): Move to
_Optional_base_impl.
* python/libstdcxx/v6/printers.py (StdExpOptionalPrinter): Add
support for new std::optional layout.
* testsuite/libstdc++-prettyprinters/compat.cc: New test.
Backport from mainline
2018-11-19 Ville Voutilainen <ville.voutilainen@gmail.com>
PR libstdc++/87855
Also implement P0602R4 (variant and optional
should propagate copy/move triviality) for std::optional.
* include/std/optional (_Optional_payload): Change
the main constraints to check constructibility in
addition to assignability.
(operator=): Make constexpr.
(_M_reset): Likewise.
(_M_construct): Likewise.
(operator->): Likewise.
* testsuite/20_util/optional/assignment/8.cc: Adjust.
* testsuite/20_util/optional/assignment/9.cc: New.
Added:
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/optional/assignment/9.cc
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/include/std/optional
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/optional/assignment/8.cc
branches/gcc-8-branch/libstdc++-v3/testsuite/20_util/optional/cons/value_neg.cc
>From gcc-bugs-return-628454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:17:42 2019
Return-Path: <gcc-bugs-return-628454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49765 invoked by alias); 9 Jan 2019 10:17: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 49648 invoked by uid 48); 9 Jan 2019 10:17:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/87855] std::optional<T> only copy-constructible if T is trivially copy-constructible
Date: Wed, 09 Jan 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ville.voutilainen at gmail dot com
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-87855-4-VAgFMnfsJn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01263.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87855
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.3
--- Comment #21 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Also fixed for GCC 8.3
>From gcc-bugs-return-628456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:21:43 2019
Return-Path: <gcc-bugs-return-628456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72090 invoked by alias); 9 Jan 2019 10:21: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 72031 invoked by uid 48); 9 Jan 2019 10:21:38 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88756] [nvptx, openacc] Override too many num_workers in nvptx plugin, instead of erroring out
Date: Wed, 09 Jan 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88756-4-sU8fwkt2j2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88756-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88756-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01265.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88756
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #0)
> For the user, it's somewhat confusing that this passes with warning when
> compiling as C++, and fails to execute when compiling as C.
> I wonder why we don't do the
> same in the plugin, that is, override with warning.
>
> We would have the more acceptable difference of "compile with warning and
> run" vs "compile and run with warning".
Thomas, any comments from OpenACC usability perspective?
Thanks,
- Tom
>From gcc-bugs-return-628457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:25:34 2019
Return-Path: <gcc-bugs-return-628457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80680 invoked by alias); 9 Jan 2019 10:25: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 80592 invoked by uid 55); 9 Jan 2019 10:25:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Wed, 09 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
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: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88758-4-VdxvR6kogY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01266.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 9 10:24:43 2019
New Revision: 267760
URL: https://gcc.gnu.org/viewcvs?rev=267760&root=gcc&view=rev
Log:
PR middle-end/88758
* tree.c (initializer_each_zero_or_onep) <case VECTOR_CST>: Use
vector_cst_elt instead of VECTOR_CST_ENCODED_ELT.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/tree.c
>From gcc-bugs-return-628458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:26:14 2019
Return-Path: <gcc-bugs-return-628458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82765 invoked by alias); 9 Jan 2019 10:26:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82660 invoked by uid 48); 9 Jan 2019 10:26:09 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] New: [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 10:26: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: 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-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01267.txt.bz2
Content-length: 1476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
Bug ID: 88766
Summary: [9 Regression] Rejects valid? C code since r259641
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: jakub at gcc dot gnu.org, jsm28 at gcc dot gnu.org
Target Milestone: ---
Following code (reduced from gpg2) now fails to compile:
$ cat dns-stuff.i
struct dns_options {
struct {
void *a;
int b;
};
int *socks_host;
char *socks_user;
char *socks_password;
};
static char tor_socks_user[1], tor_socks_password[1];
struct {
int socks_host;
} libdns;
int d;
int *c();
int ax() {
int *az;
int ba;
az = c((&__extension__({
(struct dns_options){{0, 0},
0,
0,
.socks_host = &libdns.socks_host,
.socks_user = tor_socks_user,
.socks_password = tor_socks_password};
})),
&ba);
d = *az;
return 0;
}
$ gcc dns-stuff.i
dns-stuff.i: In function ‘ax’:
dns-stuff.i:19:11: error: lvalue required as unary ‘&’ operand
19 | az = c((&__extension__({
| ^
>From gcc-bugs-return-628459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:27:46 2019
Return-Path: <gcc-bugs-return-628459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86754 invoked by alias); 9 Jan 2019 10:27: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 86667 invoked by uid 48); 9 Jan 2019 10:27:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Wed, 09 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
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: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88758-4-RxPbaSQqtd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01268.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed. If you manage to turn the testcase into testsuite suitable form, please
commit it with this PR's number in the ChangeLog.
>From gcc-bugs-return-628460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:27:57 2019
Return-Path: <gcc-bugs-return-628460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87514 invoked by alias); 9 Jan 2019 10:27: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 87428 invoked by uid 48); 9 Jan 2019 10:27:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88331] [9 Regression] ICE in rtl_verify_bb_layout, at cfgrtl.c:2987
Date: Wed, 09 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-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: 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-88331-4-GPAj5P8geT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88331-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01269.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88331
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:28:17 2019
Return-Path: <gcc-bugs-return-628461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88392 invoked by alias); 9 Jan 2019 10: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 88317 invoked by uid 48); 9 Jan 2019 10:28:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
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-88766-4-OfLYc75vWr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01270.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-628462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:29:05 2019
Return-Path: <gcc-bugs-return-628462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89469 invoked by alias); 9 Jan 2019 10:29:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89360 invoked by uid 48); 9 Jan 2019 10:28:57 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-88760-4-wXsyACiJ7s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01271.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #2 from ktkachov at gcc dot gnu.org ---
Created attachment 45386
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45386&action=edit
aarch64-llvm output with -Ofast -mcpu=cortex-a57
I'm attaching the full LLVM aarch64 output.
The output you quoted is with -funroll-loops. If that's not given, GCC doesn't
seem to unroll by default at all (on aarch64 or x86_64 from my testing).
Is there anything we can do to make the default unrolling a bit more
aggressive?
>From gcc-bugs-return-628463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:44:28 2019
Return-Path: <gcc-bugs-return-628463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110654 invoked by alias); 9 Jan 2019 10:44:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110418 invoked by uid 48); 9 Jan 2019 10:44:15 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-wohAOUDkOS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01272.txt.bz2
Content-length: 26765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #19 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Iain Sandoe from comment #18)
> (In reply to Jürgen Reuter from comment #14)
>
> does the application use exceptions?
No exceptions, only a poor man's C signal catcher.
>
> > /usr/local/lib/libstdc++.a
>
> ^^^ please confirm that this is from the "current compiler build".
>
Yes, they are the same. Unfortunately, there is no uninstall target for gcc,
but all stdc++ libraries in /usr/local/lib are from my Jan 8 clean building.
>
> ^^^^^^^ this looks like the build process in this case is adding libs that
> the compiler driver normally adds ( they are not present in the case above ).
>
Yes, that is for a different reason, a different build with a tutorial C and
C++ wrapper for our code, but they don't hurt here.
> * If you can extract these two fortran link lines - and then execute them
> separately in the build dir with "-v" so that we can see the output of the
> compiler-driver's internal link line and what its search paths are.
This is the output for the non-working linking:
$ gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
static_1.exe .libs/static_1.exe_prclib_dispatcher.o
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
./.libs/static_1_lib.a
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
/usr/local//lib/libHepMC.a -llcio /usr/local/lib/libstdc++.a
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-lm -v
Driving: gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
static_1.exe .libs/static_1.exe_prclib_dispatcher.o
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
./.libs/static_1_lib.a
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
/usr/local//lib/libHepMC.a -llcio /usr/local/lib/libstdc++.a
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-lm -v -mmacosx-version-min=10.14.0 -asm_macosx_version_min=10.14 -l gfortran
-shared-libgcc
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/lto-wrapper
Target: x86_64-apple-darwin18.2.0
Configured with: ../configure --prefix=/usr/local/ --with-gmp=/usr/local/
--with-mpfr=/usr/local/ --with-mpc=/usr/local/ --enable-checking=release
--enable-languages=c,c++,fortran,lto
Thread model: posix
gcc version 9.0.0 20190107 (experimental) (GCC)
Reading specs from
/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../../libgfortran.spec
rename spec lib to liborig
COLLECT_GCC_OPTIONS='-g' '-O2' '-o' 'static_1.exe'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools'
'-L/usr/local/packages/OpenLoops/lib' '-L/usr/local/lib' '-L../src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs'
'-v' '-mmacosx-version-min=10.14.0' '-asm_macosx_version_min=10.14'
'-shared-libgcc' '-mtune=core2'
COMPILER_PATH=/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/:/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/
LIBRARY_PATH=/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../../
COLLECT_GCC_OPTIONS='-g' '-O2' '-o' 'static_1.exe'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools'
'-L/usr/local/packages/OpenLoops/lib' '-L/usr/local/lib' '-L../src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs'
'-v' '-mmacosx-version-min=10.14.0' '-asm_macosx_version_min=10.14'
'-shared-libgcc' '-mtune=core2'
/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/collect2 -dynamic -arch
x86_64 -macosx_version_min 10.14.0 -weak_reference_mismatches non-weak -o
static_1.exe
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../.. -rpath
/usr/local/packages/OpenLoops/lib .libs/static_1.exe_prclib_dispatcher.o
./.libs/static_1_lib.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
/usr/local//lib/libHepMC.a -llcio /usr/local/lib/libstdc++.a -lgfortran
-no_compact_unwind -lSystem -lgcc_ext.10.5 -lgcc -lquadmath -lm -lgcc_ext.10.5
-lgcc -lSystem -v -idsym
collect2 version 9.0.0 20190107 (experimental)
/usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.14.0
-weak_reference_mismatches non-weak -o static_1.exe
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../.. -rpath
/usr/local/packages/OpenLoops/lib .libs/static_1.exe_prclib_dispatcher.o
./.libs/static_1_lib.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
/usr/local//lib/libHepMC.a -llcio /usr/local/lib/libstdc++.a -lgfortran
-no_compact_unwind -lSystem -lgcc_ext.10.5 -lgcc -lquadmath -lm -lgcc_ext.10.5
-lgcc -lSystem -v
@(#)PROGRAM:ld PROJECT:ld64-409.12
BUILD 17:47:51 Sep 25 2018
configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h
armv6m armv7k armv7m armv7em arm64e arm64_32
ld: warning: directory not found for option '-L../src'
Library search paths:
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
/usr/local/packages/OpenLoops/lib
/usr/local/lib
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
/usr/local/lib
/usr/lib
/usr/local/lib
Framework search paths:
/Library/Frameworks/
/System/Library/Frameworks/
ld: warning: direct access in function 'operator new[](unsigned long,
std::nothrow_t const&) [clone .cold]' from file
'/usr/local/lib/libstdc++.a(new_opvnt.o)' to global weak symbol 'operator
new[](unsigned long, std::nothrow_t const&)' from file
'/usr/local/lib/libstdc++.a(new_opvnt.o)' means the weak symbol cannot be
overridden at runtime. This was likely caused by different translation units
being compiled with different visibility settings.
reuter@vpn-005:~/Physik/whizard/trunk/_build_quasi_naked/tests/functional_tests$
And this is the one for the working linking:
$ gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
static_1.exe .libs/static_1.exe_prclib_dispatcher.o
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
./.libs/static_1_lib.a
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-lSystem -lgcc_ext.10.5 /usr/local//lib/libHepMC.a -llcio -lstdc++ -lm -v
Driving: gfortran -g -O2 -Wl,-rpath -Wl,/usr/local/packages/OpenLoops/lib -o
static_1.exe .libs/static_1.exe_prclib_dispatcher.o
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
./.libs/static_1_lib.a
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-lSystem -lgcc_ext.10.5 /usr/local//lib/libHepMC.a -llcio -lstdc++ -lm -v
-mmacosx-version-min=10.14.0 -asm_macosx_version_min=10.14 -l gfortran
-shared-libgcc
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/lto-wrapper
Target: x86_64-apple-darwin18.2.0
Configured with: ../configure --prefix=/usr/local/ --with-gmp=/usr/local/
--with-mpfr=/usr/local/ --with-mpc=/usr/local/ --enable-checking=release
--enable-languages=c,c++,fortran,lto
Thread model: posix
gcc version 9.0.0 20190107 (experimental) (GCC)
Reading specs from
/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../../libgfortran.spec
rename spec lib to liborig
COLLECT_GCC_OPTIONS='-g' '-O2' '-o' 'static_1.exe'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools'
'-L/usr/local/packages/OpenLoops/lib' '-L/usr/local/lib' '-L../src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models'
'-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0'
'-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs'
'-v' '-mmacosx-version-min=10.14.0' '-asm_macosx_version_min=10.14'
'-shared-libgcc' '-mtune=core2'
COMPILER_PATH=/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/:/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/
LIBRARY_PATH=/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/:/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../../
COLLECT_GCC_OPTIONS='-g' '-O2' '-o' 'static_1.exe'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools'
'-L/usr/local/packages/OpenLoops/lib' '-L/usr/local/lib' '-L../src'
'-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models'
'-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0'
'-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs'
'-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs'
'-v' '-mmacosx-version-min=10.14.0' '-asm_macosx_version_min=10.14'
'-shared-libgcc' '-mtune=core2'
/usr/local/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/collect2 -dynamic -arch
x86_64 -macosx_version_min 10.14.0 -weak_reference_mismatches non-weak -o
static_1.exe
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../.. -rpath
/usr/local/packages/OpenLoops/lib .libs/static_1.exe_prclib_dispatcher.o
./.libs/static_1_lib.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
-lSystem -lgcc_ext.10.5 /usr/local//lib/libHepMC.a -llcio -lstdc++ -lgfortran
-no_compact_unwind -lSystem -lgcc_ext.10.5 -lgcc -lquadmath -lm -lgcc_ext.10.5
-lgcc -lSystem -v -idsym
collect2 version 9.0.0 20190107 (experimental)
/usr/bin/ld -dynamic -arch x86_64 -macosx_version_min 10.14.0
-weak_reference_mismatches non-weak -o static_1.exe
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
-L/usr/local/packages/OpenLoops/lib -L/usr/local/lib -L../src
-L/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../..
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
-L/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
-L/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0/../../.. -rpath
/usr/local/packages/OpenLoops/lib .libs/static_1.exe_prclib_dispatcher.o
./.libs/static_1_lib.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core/.libs/libwhizard_main.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libomega.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/omega/src/.libs/libomega_core.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/.libs/libwhizard.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/vamp/src/.libs/libvamp.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe1/src/.libs/libcirce1.a
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/circe2/src/.libs/libcirce2.a
-lcuttools -lopenloops -loneloop -lolcommon -lrambo /usr/local/lib/libLHAPDF.a
-lSystem -lgcc_ext.10.5 /usr/local//lib/libHepMC.a -llcio -lstdc++ -lgfortran
-no_compact_unwind -lSystem -lgcc_ext.10.5 -lgcc -lquadmath -lm -lgcc_ext.10.5
-lgcc -lSystem -v
@(#)PROGRAM:ld PROJECT:ld64-409.12
BUILD 17:47:51 Sep 25 2018
configured to support archs: armv6 armv7 armv7s arm64 i386 x86_64 x86_64h
armv6m armv7k armv7m armv7em arm64e arm64_32
ld: warning: directory not found for option '-L../src'
Library search paths:
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/whizard-core
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hepmc
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/lcio
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/hoppet
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/looptools
/usr/local/packages/OpenLoops/lib
/usr/local/lib
/Users/reuter/Physik/whizard/trunk/_build_quasi_naked/src/models
/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
/usr/local/lib
/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src
/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/src/.libs
/usr/local/packages/gcc_9.0/_build/x86_64-apple-darwin18.2.0/libstdc++-v3/libsupc++/.libs
/usr/local/lib/gcc/x86_64-apple-darwin18.2.0/9.0.0
/usr/local/lib
/usr/lib
/usr/local/lib
Framework search paths:
/Library/Frameworks/
/System/Library/Frameworks/
> * According to your posted otool output, the version of libstdc++.dylib that
> is bound is the one in /usr/local/lib/ which is where you pick up the static
> lib in the non-working case.
>
> * The object files used to build the static (.a) and dynamic (.dylib)
> versions of libstdc++ are the same, so we really need to pin down where the
> issue occurs.
>
> * DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_BINDINGS=1 <exe>
> will show you which libraries are used, and from which library each symbol
> is resolved - it probably will produce a lot of output..
I will attach this output.
>From gcc-bugs-return-628464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:47:21 2019
Return-Path: <gcc-bugs-return-628464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13670 invoked by alias); 9 Jan 2019 10:47: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 13535 invoked by uid 48); 9 Jan 2019 10:47:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-4KQSw9FoSr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01273.txt.bz2
Content-length: 2025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to ktkachov from comment #2)
> Created attachment 45386 [details]
> aarch64-llvm output with -Ofast -mcpu=cortex-a57
>
> I'm attaching the full LLVM aarch64 output.
>
> The output you quoted is with -funroll-loops. If that's not given, GCC
> doesn't seem to unroll by default at all (on aarch64 or x86_64 from my
> testing).
>
> Is there anything we can do to make the default unrolling a bit more
> aggressive?
Well, the RTL loop unroller is not enabled by default at any
optimization level (unless you are using FDO). There's also
related flags not enabled (-fsplit-ivs-in-unroller and
-fvariable-expansion-in-unroller).
The RTL loop unroller is simply not good at estimating benefit
of unrolling (which is also why you usually see it unrolling
--param max-unroll-times times) and the tunables it has are
not very well tuned across targets.
Micha did quite extensive benchmarking (on x86_64) which shows that
the cases where unrolling is profitable are rare and the reason
is often hard to understand.
That's of course in the context of CPUs having caches of
pre-decoded/fused/etc. instructions optimizing issue which
makes peeled prologues expensive as well as even more special
caches for small loops avoiding more frontend costs.
Not sure if arm archs have any of this.
I generally don't believe in unrolling as a separately profitable
transform. Rather unrolling could be done as part of another
transform (vectorization is the best example). For sth still
done on RTL that would then include scheduling which is where
the best cost estimates should be available (and if you do
this post-reload then you even have a very good idea of
register pressure). This is also why I think a standalone
unrolling phase belongs on RTL since I don't see a good way
of estimating cost/benefit on GIMPLE (see how difficult it is
to cost vectorization vs. non-vectorization there).
>From gcc-bugs-return-628466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:51:58 2019
Return-Path: <gcc-bugs-return-628466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30330 invoked by alias); 9 Jan 2019 10:51:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30266 invoked by uid 48); 9 Jan 2019 10:51:54 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88750-4-0e9xnBslD9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01275.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #21 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Created attachment 45388
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45388&action=edit
DYLD_PRINT output working example
DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_BINDINGS=1 ./static_1.exe > working_output
2>&1
>From gcc-bugs-return-628465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:51:05 2019
Return-Path: <gcc-bugs-return-628465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23560 invoked by alias); 9 Jan 2019 10:51:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22997 invoked by uid 48); 9 Jan 2019 10:51:00 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88750-4-m8mKxfXQJX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01274.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #20 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Created attachment 45387
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45387&action=edit
DYLD_PRINT output non-working example
DYLD_PRINT_LIBRARIES=1 DYLD_PRINT_BINDINGS=1 ./static_1.exe >
non_working_output 2>&1
>From gcc-bugs-return-628467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 10:56:39 2019
Return-Path: <gcc-bugs-return-628467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43087 invoked by alias); 9 Jan 2019 10:56: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 42360 invoked by uid 48); 9 Jan 2019 10:56:31 -0000
From: "helijia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] New: 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 10:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: helijia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01276.txt.bz2
Content-length: 3475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
Bug ID: 88767
Summary: 'unroll and jam' not optimizing some loops
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: helijia at gcc dot gnu.org
Target Milestone: ---
The test source is as follows:
__attribute__((noinline)) void calculate(const double* __restrict__ A, const
double* __restrict__ B, double* __restrict__ C) {
unsigned int l_m = 0;
unsigned int l_n = 0;
unsigned int l_k = 0;
A = (const double*)__builtin_assume_aligned(A,16);
B = (const double*)__builtin_assume_aligned(B,16);
C = (double*)__builtin_assume_aligned(C,16);
for ( l_n = 0; l_n < 9; l_n++ ) { // loop 1
for ( l_m = 0; l_m < 10; l_m++ ) { C[(l_n*10)+l_m] = 0.0; } // loop 2
for ( l_k = 0; l_k < 17; l_k++ ) { // loop 3
for ( l_m = 0; l_m < 10; l_m++ ) { // loop 4
C[(l_n*10)+l_m] += A[(l_k*20)+l_m] * B[(l_n*20)+l_k];
}
}
}
}
#define SIZE 36
double A[SIZE][SIZE] __attribute__((aligned(16)));
double B[SIZE][SIZE] __attribute__((aligned(16)));
double C[SIZE][SIZE] __attribute__((aligned(16)));
int main()
{
long r, i, j;
for (i=0; i < SIZE; i++) {
for (j=0; j < SIZE; j++) {
A[i][j] = 1.0;
B[i][j] = 2.0;
C[i][j] = 3.0;
}
}
for (r=0; r < 1000000; r++) {
calculate(&A[0][0],&B[0][0], &C[0][0]);
}
return 0;
}
First, I compile the test case with the following command. g++
unroll_jam_bug.cpp -O3 -funroll-loops -floop-unroll-and-jam -o unroll_jam_bug
-fdump-tree-unrolljam-details. In the generated file of
unroll_jam_bug.cpp.143t.unrolljam, I found that there is no unroll and jam
optimization for the loop in the calculate function.
Second, I added the -fdump-tree-all parameter to the command line. I found that
the innermost loop(loop 3 and 4) is completely unrolled because
pass_data_complete_unrolli pass thinks innermost loop is small. As the inner
loop is fully expanded, the original loop becomes large. When the loop is
expanded in the pass_loop_jam pass, the number of unroll_factor * loop
instruction > 200 will be judged. If the result is true, the optimization will
be abandoned. Otherwise, the optimization will proceed.
By the second analysis, I tried to ban the unrolli optimization.So I use the
following command line. g++ unroll_jam_bug.cpp -O3 -mcpu=power8
-fdisable-tree-cunrolli -floop-unroll-and-jam -o unroll_jam_bug
-fdump-tree-unrolljam-details
Using this command, loop unroll and jam
optimization will be executed, but there seems to be room for optimization.

Original code:
for ( l_n = 0; l_n < 9; l_n++ ) {
for ( l_m = 0; l_m < 10; l_m++ ) { C[(l_n*10)+l_m] = 0.0; }
for ( l_k = 0; l_k < 17; l_k++ ) {
for ( l_m = 0; l_m < 10; l_m++ ) {
C[(l_n*10)+l_m] += A[(l_k*20)+l_m] * B[(l_n*20)+l_k];
}
}
}
After unroll and jam pass:
for ( l_n = 0; l_n < 9; l_n++ ) {
for ( l_m = 0; l_m < 10; l_m++ ) { C[(l_n*10)+l_m] = 0.0; }
for ( l_k = 0; l_k < 17; l_k += 2 ) {
for ( l_m = 0; l_m < 10; l_m++ ) {
C[(l_n*10)+l_m] += A[(l_k*20)+l_m] * B[(l_n*20)+l_k];
C[(l_n*10)+l_m] += A[(l_k*20 + 20)+l_m] * B[(l_n*20)+l_k + 1];
}
}
}
>From gcc-bugs-return-628468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:01:52 2019
Return-Path: <gcc-bugs-return-628468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47808 invoked by alias); 9 Jan 2019 11:01:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47681 invoked by uid 48); 9 Jan 2019 11:01:45 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-VfuIkqNRtF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01277.txt.bz2
Content-length: 3916
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #22 from Jürgen Reuter <juergen.reuter at desy dot de> ---
This is the output from the lldb command (but this was not a debug build of gcc
yet):
$ lldb ./static_1.exe
(lldb) target create "./static_1.exe"
Current executable set to './static_1.exe' (x86_64).
(lldb) run
Process 36799 launched: './static_1.exe' (x86_64)
static_1.exe(36799,0x1048f75c0) malloc: *** error for object 0x105c5eee0:
pointer being freed was not allocated
static_1.exe(36799,0x1048f75c0) malloc: *** set a breakpoint in
malloc_error_break to debug
Process 36799 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
frame #0: 0x00007fff5a2d023e libsystem_kernel.dylib`__pthread_kill + 10
libsystem_kernel.dylib`__pthread_kill:
-> 0x7fff5a2d023e <+10>: jae 0x7fff5a2d0248 ; <+20>
0x7fff5a2d0240 <+12>: movq %rax, %rdi
0x7fff5a2d0243 <+15>: jmp 0x7fff5a2ca3b7 ; cerror_nocancel
0x7fff5a2d0248 <+20>: retq
Target 0: (static_1.exe) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = signal SIGABRT
* frame #0: 0x00007fff5a2d023e libsystem_kernel.dylib`__pthread_kill + 10
frame #1: 0x00007fff5a386c1c libsystem_pthread.dylib`pthread_kill + 285
frame #2: 0x00007fff5a2391c9 libsystem_c.dylib`abort + 127
frame #3: 0x00007fff5a3486e2 libsystem_malloc.dylib`malloc_vreport + 545
frame #4: 0x00007fff5a3484a3 libsystem_malloc.dylib`malloc_report + 152
frame #5: 0x0000000100929c84
static_1.exe`std::locale::_Impl::~_Impl(this=0x0000000105c5f0a0) at
locale.cc:243
frame #6: 0x0000000100929d8e
static_1.exe`std::locale::operator=(this=0x0000000105c611c0,
__other=0x00007ffeefbfdad8) at locale_classes.h:568
frame #7: 0x0000000100927aec
static_1.exe`std::ios_base::_M_init(this=0x0000000105c610f0) at
ios_locale.cc:44
frame #8: 0x000000010096cef1 static_1.exe`std::basic_ios<char,
std::char_traits<char> >::init(this=0x0000000105c610f0,
__sb=0x0000000105c60840) at basic_ios.tcc:129
frame #9: 0x0000000105afcdf9 libstdc++.6.dylib`std::ios_base::Init::Init()
+ 681
frame #10: 0x0000000105ad30a0
libsio.2.12.dylib`_GLOBAL__sub_I_SIO_blockManager.cc + 16
frame #11: 0x0000000104859cc8
dyld`ImageLoaderMachO::doModInitFunctions(ImageLoader::LinkContext const&) +
518
frame #12: 0x0000000104859ec6
dyld`ImageLoaderMachO::doInitialization(ImageLoader::LinkContext const&) + 40
frame #13: 0x00000001048550da
dyld`ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&,
unsigned int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) + 358
frame #14: 0x000000010485506d
dyld`ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&,
unsigned int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) + 249
frame #15: 0x000000010485506d
dyld`ImageLoader::recursiveInitialization(ImageLoader::LinkContext const&,
unsigned int, char const*, ImageLoader::InitializerTimingList&,
ImageLoader::UninitedUpwards&) + 249
frame #16: 0x0000000104854254
dyld`ImageLoader::processInitializers(ImageLoader::LinkContext const&, unsigned
int, ImageLoader::InitializerTimingList&, ImageLoader::UninitedUpwards&) + 134
frame #17: 0x00000001048542e8
dyld`ImageLoader::runInitializers(ImageLoader::LinkContext const&,
ImageLoader::InitializerTimingList&) + 74
frame #18: 0x0000000104843774 dyld`dyld::initializeMainExecutable() + 199
frame #19: 0x000000010484878f dyld`dyld::_main(macho_header const*,
unsigned long, int, char const**, char const**, char const**, unsigned long*) +
6237
frame #20: 0x00000001048424f6 dyld`dyldbootstrap::start(macho_header
const*, int, char const**, long, macho_header const*, unsigned long*) + 1154
frame #21: 0x0000000104842036 dyld`_dyld_start + 54
>From gcc-bugs-return-628469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:05:04 2019
Return-Path: <gcc-bugs-return-628469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53895 invoked by alias); 9 Jan 2019 11: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 53719 invoked by uid 48); 9 Jan 2019 11:04:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Wed, 09 Jan 2019 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-p2dcLtCKTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01278.txt.bz2
Content-length: 1077
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #20 from Richard Biener <rguenth at gcc dot gnu.org> ---
For stage3/gcc/*.o statistics show we perform 21051052 base_alias_check calls
and in the end 706852 times it is the one that would have disambiguated
things compared to if we remove it (thus as if we do base_alias_check last).
Note there's also
base = find_base_term (x_addr);
if (base && (GET_CODE (base) == LABEL_REF
|| (GET_CODE (base) == SYMBOL_REF
&& CONSTANT_POOL_ADDRESS_P (base))))
return 0;
which is suspicious but I guess harder to hit in practice so things go wrong.
base_alias_check is not exactly the first thing we check (but nearly) so
we'd roughly lose 3% disambiguations from RTL alias analysis if we scrap
base_alias_check completely.
That's probably too much.
Note the CONSTANT_POOL_ADDRESS_P thing isn't necessary and subsumed by
following checks so we could remove that without losing anything
(it hits only 84 times at all in the above set and later checks subsume it).
>From gcc-bugs-return-628470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:05:43 2019
Return-Path: <gcc-bugs-return-628470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57871 invoked by alias); 9 Jan 2019 11:05:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57793 invoked by uid 48); 9 Jan 2019 11:05:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Wed, 09 Jan 2019 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-49330-4-WnZCkk2yTQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01279.txt.bz2
Content-length: 275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #21 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45389
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45389&action=edit
statistic patch
patch I added to record statistics
>From gcc-bugs-return-628471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:15:57 2019
Return-Path: <gcc-bugs-return-628471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79752 invoked by alias); 9 Jan 2019 11:15:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79572 invoked by uid 48); 9 Jan 2019 11:15:41 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 11:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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 cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88767-4-9O6fM6Fqex@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01280.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-09
CC| |matz at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
What's the room for improvement? Why's unrolling the innermost loop not
profitable?
>From gcc-bugs-return-628472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:16:41 2019
Return-Path: <gcc-bugs-return-628472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80852 invoked by alias); 9 Jan 2019 11:16: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 80779 invoked by uid 48); 9 Jan 2019 11:16:35 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-D3o3olyXVv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01281.txt.bz2
Content-length: 842
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #23 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #22)
> This is the output from the lldb command (but this was not a debug build of
> gcc yet):
> $ lldb ./static_1.exe
> (lldb) target create "./static_1.exe"
> Current executable set to './static_1.exe' (x86_64).
> (lldb) run
<snip>
> __sb=0x0000000105c60840) at basic_ios.tcc:129
> frame #9: 0x0000000105afcdf9
> libstdc++.6.dylib`std::ios_base::Init::Init() + 681
> frame #10: 0x0000000105ad30a0
^^^^ so, you have a combination of things linking libstdc++ statically and
dynamically .. that seems fragile at best.
Having said that - the tricky thing now is to determine what has "broken" (it's
probably going to be hard without a "before" and "after" case).
>From gcc-bugs-return-628474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:23:30 2019
Return-Path: <gcc-bugs-return-628474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93252 invoked by alias); 9 Jan 2019 11:23:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93166 invoked by uid 48); 9 Jan 2019 11:23:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 11:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-swr1tJgetg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01283.txt.bz2
Content-length: 1060
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #23)
> (In reply to Jürgen Reuter from comment #22)
> > This is the output from the lldb command (but this was not a debug build of
> > gcc yet):
> > $ lldb ./static_1.exe
> > (lldb) target create "./static_1.exe"
> > Current executable set to './static_1.exe' (x86_64).
> > (lldb) run
>
> <snip>
>
> > __sb=0x0000000105c60840) at basic_ios.tcc:129
> > frame #9: 0x0000000105afcdf9
> > libstdc++.6.dylib`std::ios_base::Init::Init() + 681
> > frame #10: 0x0000000105ad30a0
>
> ^^^^ so, you have a combination of things linking libstdc++ statically and
> dynamically .. that seems fragile at best.
>
> Having said that - the tricky thing now is to determine what has "broken"
> (it's probably going to be hard without a "before" and "after" case).
Indeed - somehow you didn't get a statically linked executable. Quoting the
full final link command would be interesting.
>From gcc-bugs-return-628473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:23:20 2019
Return-Path: <gcc-bugs-return-628473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92483 invoked by alias); 9 Jan 2019 11:23: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 92401 invoked by uid 48); 9 Jan 2019 11:23:16 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88204] New test case 26_numerics/complex/operators/more_constexpr.cc from r266416 fails
Date: Wed, 09 Jan 2019 11:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88204-4-2011SKZYXA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01282.txt.bz2
Content-length: 196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88204
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GNU/Linux and AIX. Please reopen if it's still failing on Darwin.
>From gcc-bugs-return-628475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:25:04 2019
Return-Path: <gcc-bugs-return-628475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95041 invoked by alias); 9 Jan 2019 11:25:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94708 invoked by uid 48); 9 Jan 2019 11:24:58 -0000
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88768] New: Derived type io in conjunction with allocatable component and recursion fails
Date: Wed, 09 Jan 2019 11:25: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mscfd at gmx dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01284.txt.bz2
Content-length: 2420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88768
Bug ID: 88768
Summary: Derived type io in conjunction with allocatable
component and recursion fails
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: mscfd at gmx dot net
Target Milestone: ---
This is a strange bug, which requires a some kind of dt IO (defined as "
generic :: write(unformatted) => write_unformatted", but not used!), an
allocatable component with dimension(:) (a "character(len=:), allocatable"
triggers the bug as well), and a recursive function.
If the "write(unformatted)"-part is commented out, the bug does not occur.
Without recursing, the return value is fine (variable y). Also, if the
dimension(:) is omitted in the declaration of r, then the bug disappears as
well.
The code either show funny values for z or segfaults. Valgrind shows an illegal
memory read.
module mod
implicit none
private
type, public :: t
real, dimension(:), allocatable :: r
contains
procedure :: set
generic :: assignment(=) => set
procedure :: recurse
generic :: write(unformatted) => write_unformatted
procedure :: write_unformatted
end type t
contains
subroutine set(self, x)
class(t), intent(out) :: self
class(t), intent(in) :: x
real, dimension(:), allocatable :: tmp
if (allocated(x%r)) then
! make a local copy to avoid any aliasing issues
tmp = x%r
self%r = tmp
end if
end subroutine set
recursive function recurse(self, i) result(x)
type(t) :: x
class(t), intent(in) :: self
integer, intent(in) :: i
if (i > 0) then
x = self%recurse(i-1)
else
x = self
end if
end function recurse
subroutine write_unformatted(dtv, unit, iostat, iomsg)
class(t), intent(in) :: dtv
integer, intent(in) :: unit
integer, intent(out) :: iostat
character(len=*), intent(inout) :: iomsg
write(unit, iostat=iostat, iomsg=iomsg) 'unformatted'
end subroutine write_unformatted
end module mod
program dt_io
use mod
implicit none
type(t) :: x, y, z
x%r = [1.23, 2.21]
y = x%recurse(0) ! fine
z = x%recurse(1) ! fails
print *, x%r
print *, y%r
print *, z%r
end program dt_io
>From gcc-bugs-return-628476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:35:34 2019
Return-Path: <gcc-bugs-return-628476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119984 invoked by alias); 9 Jan 2019 11:35: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 119907 invoked by uid 48); 9 Jan 2019 11:35:29 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-DI4KxCOsOR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01285.txt.bz2
Content-length: 1165
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #25 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Richard Biener from comment #24)
> (In reply to Iain Sandoe from comment #23)
> > (In reply to Jürgen Reuter from comment #22)
>
> Indeed - somehow you didn't get a statically linked executable. Quoting the
> full final link command would be interesting.
The full link commands can be found here, I believe:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750#c14
Our code generates code for particle physics simulations in the form of dynamic
libraries that get linked and loaded. For batch clusters, we attempted to
provide static binaries for these simulations, however, we have order 10-15
external libraries that can be linked to our code (which are partially
mandatory). There are some of them which only exist as dynamic libraries, so
there our approach cannot result in a purely static binary. The static stdc++
library is sucked in via the libtool link mode/flag -static-libtool-libs while
the dynamic ones are sucked in via the external C++ libraries that are
available only dynamically.
>From gcc-bugs-return-628477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:37:23 2019
Return-Path: <gcc-bugs-return-628477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122927 invoked by alias); 9 Jan 2019 11:37: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 122847 invoked by uid 48); 9 Jan 2019 11:37:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Wed, 09 Jan 2019 11:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-eRPXQdtQoz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01286.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
I created upstream patch candidate:
https://reviews.llvm.org/D56485
>From gcc-bugs-return-628478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:38:24 2019
Return-Path: <gcc-bugs-return-628478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124140 invoked by alias); 9 Jan 2019 11:38: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 124064 invoked by uid 48); 9 Jan 2019 11:38:18 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] [7/8/9 Regression] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Wed, 09 Jan 2019 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88684-4-9uW17wclwZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01287.txt.bz2
Content-length: 295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-628479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 11:39:10 2019
Return-Path: <gcc-bugs-return-628479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125156 invoked by alias); 9 Jan 2019 11:39:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125083 invoked by uid 48); 9 Jan 2019 11:39:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88766-4-m25pY4lYDI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01288.txt.bz2
Content-length: 831
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase:
struct S { int s; };
void
foo (void)
{
void *p = &(struct S) { 0 };
void *q = &({ (struct S) { 0 }; });
}
The p initializer is accepted, q is rejected.
By my reading this is invalid, C99 6.5.2.5/6 says:
"If the compound literal occurs outside the body of a function, the object
has static storage duration; otherwise, it has automatic storage duration
associated with the enclosing block."
and the statement expression is still a compound statement and thus the
compound literal is associated with the statement expression's block. So it is
the same thing as:
void
bar (void)
{
void *r = &({ int a = 0; a; });
}
which fails with the same diagnostics.
Joseph, do you agree?
>From gcc-bugs-return-628480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:01:19 2019
Return-Path: <gcc-bugs-return-628480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104595 invoked by alias); 9 Jan 2019 12:01:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104361 invoked by uid 48); 9 Jan 2019 12:00:56 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Wed, 09 Jan 2019 12:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail 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-88763-4-HMA0r9XCDK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01289.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #2 from Marius Messerschmidt <marius.messerschmidt at googlemail dot com> ---
Sorry but I do not fully understand what you mean. Do you suggest using
different command line arguments?
So far I tried:
-fdump-tree-all
-fdump-tree-unswitch
and
-fopt-info-all-optall
But none of them told me the all the things that I would wish to know, most
important the reason why a particular loop was skipped during unswitching (e.g.
because it is not invariant or so (right now it already reports a few things
with -fdump-tree-unswitch like too-many-instructions or too-many-branches))
>From gcc-bugs-return-628481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:07:56 2019
Return-Path: <gcc-bugs-return-628481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6870 invoked by alias); 9 Jan 2019 12:07:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6782 invoked by uid 48); 9 Jan 2019 12:07:48 -0000
From: "krebbel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88751] Performance regression reload vs lra
Date: Wed, 09 Jan 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krebbel at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88751-4-34QOCxF4hO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88751-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88751-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01290.txt.bz2
Content-length: 1628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88751
--- Comment #2 from Andreas Krebbel <krebbel at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
...
> Would be interesting to know the sparseness of regs / BBs for your testcase
> at the point of LRA and whether compacting regs (do we ever do that?) might
> be a good idea in general. (we do compact BBs regularly)
Good point. Only 9352 of the 27089 pseudos appear to be actually referenced.
Hence the following patch fixes the problem for me:
diff --git a/gcc/ira.c b/gcc/ira.c
index c8f2df43dd1..965819e1ef9 100644
--- a/gcc/ira.c
+++ b/gcc/ira.c
@@ -5157,6 +5157,7 @@ ira (FILE *f)
int ira_max_point_before_emit;
bool saved_flag_caller_saves = flag_caller_saves;
enum ira_region saved_flag_ira_region = flag_ira_region;
+ int i, num_used_regs = 0;
clear_bb_flags ();
@@ -5172,12 +5173,17 @@ ira (FILE *f)
ira_conflicts_p = optimize > 0;
+ /* Determine the number of pseudos actually requiring coloring. */
+ for (i = FIRST_PSEUDO_REGISTER; i < max_reg_num (); i++)
+ num_used_regs += !!(DF_REG_USE_COUNT (i) + DF_REG_DEF_COUNT (i));
+
/* If there are too many pseudos and/or basic blocks (e.g. 10K
pseudos and 10K blocks or 100K pseudos and 1K blocks), we will
use simplified and faster algorithms in LRA. */
lra_simple_p
= (ira_use_lra_p
- && max_reg_num () >= (1 << 26) / last_basic_block_for_fn (cfun));
+ && num_used_regs >= (1 << 26) / last_basic_block_for_fn (cfun));
+
if (lra_simple_p)
{
/* It permits to skip live range splitting in LRA. */
>From gcc-bugs-return-628482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:25:31 2019
Return-Path: <gcc-bugs-return-628482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61688 invoked by alias); 9 Jan 2019 12:25:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61531 invoked by uid 48); 9 Jan 2019 12:25:11 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Wed, 09 Jan 2019 12:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-DKGvkN2ta6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01291.txt.bz2
Content-length: 705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #22 from Richard Biener <rguenth at gcc dot gnu.org> ---
Things we fail to disambiguate are
(mem:TF (pre_dec:SI (reg/f:SI 7 sp)) [0 S16 A8])
vs.
(mem/c:TF (plus:SI (reg/f:SI 19 frame)
(const_int -16 [0xfffffffffffffff0])) [1 S16 A128])
or
(mem:SI (pre_dec:SI (reg/f:SI 7 sp)) [3 S4 A32])
vs.
(mem/f/c:SI (symbol_ref:SI ("argv") [flags 0x2] <var_decl 0x7f782d1e6360 argv>)
[2 argv+0 S4 A32])
where I don't find anything besides CSELIB cselib_sp_based_value_p handling
in find_base_term that could be the one handling it?
I guess we should be able to somehow handle both sp and frame based
accesses in a more conservative way?
>From gcc-bugs-return-628483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:27:14 2019
Return-Path: <gcc-bugs-return-628483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87507 invoked by alias); 9 Jan 2019 12:27:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82282 invoked by uid 48); 9 Jan 2019 12:27:05 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 12: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: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-6VqmeYK4gM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01292.txt.bz2
Content-length: 1215
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #25 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #17)
> On Tue, 8 Jan 2019, wilco at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
> >
> > --- Comment #16 from Wilco <wilco at gcc dot gnu.org> ---
> > I think we need to simplify the many BIG_ENDIAN macros so it is feasible to get
> > big-endian to work reliably on all targets. There seem to be far too many
> > options which affect too many unrelated things. Big-endian is fundamentally
> > about memory byte ordering, so allowing to different byte/bit orderings in
> > registers just makes things overly complex without any benefit.
>
> It's unfortunately not the compiler writers choice but the CPU designers.
It's more a bad ABI choice. The initial Arm ABI had 4-byte aligned
little-endian long long and big-endian doubles! ARM2 only supported
little-endian so it didn't matter at the time. However it doesn't allow
unaligned accesses, tightly packed bitfields and runtime endian swapping as
required by the embedded space, or hardware floating point. No surprise it was
replaced by the Arm EABI.
>From gcc-bugs-return-628484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:27:54 2019
Return-Path: <gcc-bugs-return-628484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93594 invoked by alias); 9 Jan 2019 12:27:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93522 invoked by uid 48); 9 Jan 2019 12:27:49 -0000
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/69196] [5 Regression] code size regression with jump threading at -O2
Date: Wed, 09 Jan 2019 12: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: 6.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sebastian.huber@embedded-brains.de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-69196-4-PrGuNsZPzT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69196-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69196-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01293.txt.bz2
Content-length: 1401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69196
--- Comment #29 from Sebastian Huber <sebastian.huber@embedded-brains.de> ---
Just for reference some numbers for GCC 7.4.0 and GCC 9.0.0 20190104:
sparc-rtems5-gcc --version
sparc-rtems5-gcc (GCC) 7.4.0 20181206 (RTEMS 5, RSB
ddba5372522da341fa20b2c75dfe966231cb6790, Newlib
df6915f029ac9acd2b479ea898388cbd7dda4974)
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
sparc-rtems5-gcc -c -O2 -o vprintk.7.4.0.o vprintk.i
sparc-rtems6-gcc --version
sparc-rtems6-gcc (GCC) 9.0.0 20190104 (RTEMS 6, RSB
cd4a4f61ea5bbd4236f7717a94cd5e67f8b3ad20, Newlib
34d9bb709390b14b4ed0b1ea2656bf6bf5a055c3)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
sparc-rtems6-gcc -c -O2 -o vprintk.9.0.0.o vprintk.i
size *.o
text data bss dec hex filename
688 0 0 688 2b0 vprintk.4.9.4.o
1272 0 0 1272 4f8 vprintk.6.0.0.o
933 0 0 933 3a5 vprintk.7.4.0.o
825 0 0 825 339 vprintk.9.0.0.o
It seems the code size is quite volatile for this test case.
>From gcc-bugs-return-628485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:31:31 2019
Return-Path: <gcc-bugs-return-628485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98970 invoked by alias); 9 Jan 2019 12:31: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 98325 invoked by uid 48); 9 Jan 2019 12:30:25 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-iyDx4STRQd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01294.txt.bz2
Content-length: 1395
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #26 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Wilco from comment #25)
> (In reply to rguenther@suse.de from comment #17)
> > On Tue, 8 Jan 2019, wilco at gcc dot gnu.org wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
> > >
> > > --- Comment #16 from Wilco <wilco at gcc dot gnu.org> ---
> > > I think we need to simplify the many BIG_ENDIAN macros so it is feasible to get
> > > big-endian to work reliably on all targets. There seem to be far too many
> > > options which affect too many unrelated things. Big-endian is fundamentally
> > > about memory byte ordering, so allowing to different byte/bit orderings in
> > > registers just makes things overly complex without any benefit.
> >
> > It's unfortunately not the compiler writers choice but the CPU designers.
>
> It's more a bad ABI choice. The initial Arm ABI had 4-byte aligned
> little-endian long long and big-endian doubles! ARM2 only supported
> little-endian so it didn't matter at the time. However it doesn't allow
> unaligned accesses, tightly packed bitfields and runtime endian swapping as
> required by the embedded space, or hardware floating point. No surprise it
> was replaced by the Arm EABI.
Whatever ;)
Did anybody test the patch? Testing on x86_64 will be quite pointless...
>From gcc-bugs-return-628486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:32:27 2019
Return-Path: <gcc-bugs-return-628486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102878 invoked by alias); 9 Jan 2019 12:32: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 102800 invoked by uid 48); 9 Jan 2019 12:32:21 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-3G1DOFJNdM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01295.txt.bz2
Content-length: 744
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #27 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #22)
> > Is it really pure RTL, therefore not used in tree? So the above patch using
> > BITS_BIG_ENDIAN for tree stuff would be incorrect to use it?
>
> I wouldn't say incorrect, just inappropriate and unnecessary. And, yes, it
> isn't used at the tree level and should stay so IMO. BYTES_BIG_ENDIAN alone
> already implicitly enforces a numbering on bits.
I mean incorrect as in the optimization would still trigger and give incorrect
results if BITS_BIG_ENDIAN == BYTES_BIG_ENDIAN (given that BITS_BIG_ENDIAN has
no bearing on the bitfield offsets used on tree level).
>From gcc-bugs-return-628487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:34:34 2019
Return-Path: <gcc-bugs-return-628487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2605 invoked by alias); 9 Jan 2019 12:34: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 2554 invoked by uid 48); 9 Jan 2019 12:34:28 -0000
From: "per at pz dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88769] New: Call to sin() optimized away, disregarding possible side-effect (errno)
Date: Wed, 09 Jan 2019 12:34: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: per at pz dot se
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-88769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01296.txt.bz2
Content-length: 2841
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88769
Bug ID: 88769
Summary: Call to sin() optimized away, disregarding possible
side-effect (errno)
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: per at pz dot se
Target Milestone: ---
(This is my first GCC bug report, so please have patience with me...)
Test program:
#include <math.h>
void foo(float x)
{
sin(x);
}
When compiling with -O1 (or higher), the call to sin() is optimized away:
.file "test.c"
.text
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
rep ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.ident "GCC: (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0"
.section .note.GNU-stack,"",@progbits
However, the sin() call has possible side-effects; according to the glibc docs,
it sets errno to EDOM in case the argument is an infinity.
The math errno can be disabled with -fno-math-errno, but according to the GCC
docs it is enabled by default, and compiling with the -fmath-errno makes no
difference.
The behavior is the same with GCC 8.2 and "trunk" (via godbolt.org).
clang 6.0 does not optimize away the sin() call, except when called with
-fno-math-errno.
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.3.0-27ubuntu1~18.04' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
>From gcc-bugs-return-628488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:46:27 2019
Return-Path: <gcc-bugs-return-628488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75204 invoked by alias); 9 Jan 2019 12:46:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75156 invoked by uid 48); 9 Jan 2019 12:46:22 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 12:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-GxXZblOcFY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01297.txt.bz2
Content-length: 2253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #26 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #25)
> (In reply to Richard Biener from comment #24)
> > (In reply to Iain Sandoe from comment #23)
> > > (In reply to Jürgen Reuter from comment #22)
>
> >
> > Indeed - somehow you didn't get a statically linked executable. Quoting the
> > full final link command would be interesting.
>
> The full link commands can be found here, I believe:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750#c14
>
> Our code generates code for particle physics simulations in the form of
> dynamic libraries that get linked and loaded. For batch clusters, we
> attempted to provide static binaries for these simulations, however, we have
> order 10-15 external libraries that can be linked to our code (which are
> partially mandatory). There are some of them which only exist as dynamic
> libraries, so there our approach cannot result in a purely static binary.
> The static stdc++ library is sucked in via the libtool link mode/flag
> -static-libtool-libs while the dynamic ones are sucked in via the external
> C++ libraries that are available only dynamically.
So .. I appreciate it can be difficult with a sophisticated project. However,
it would seem prudent to try to arrange that you have only one instance of the
c++ library. Imagine creating an object in one instance, and that object
somehow finds it's way to be destroyed in a different one.
I've spent some time trying to make it possible to link GCC Darwin projects
'statically', (modulo the libSystem, which must be dynamic) - but that's only
going to work if all the project dependent libs are available as convenience
libs (or, I suppose, if no used dynamic ones have any external deps other than
libSystem).
If that's not possible, then it's most likely better to arrange to do a link -r
on everything that can be found as convenience .. and then link the result with
-lstdc++.
It might be that it worked before mostly from luck - although I'd still like to
have a reference for a known "working" static linked case. As the c++ library
grows, this is only going to be more fragile.
>From gcc-bugs-return-628489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:46:42 2019
Return-Path: <gcc-bugs-return-628489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76064 invoked by alias); 9 Jan 2019 12:46: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 75890 invoked by uid 48); 9 Jan 2019 12:46:37 -0000
From: "bisqwit at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88770] New: Redundant load opt. or CSE pessimizes code
Date: Wed, 09 Jan 2019 12:46: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: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bisqwit at iki dot fi
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01298.txt.bz2
Content-length: 2584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88770
Bug ID: 88770
Summary: Redundant load opt. or CSE pessimizes code
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bisqwit at iki dot fi
Target Milestone: ---
For this code (-xc -std=c99 or -xc++ -std=c++17):
struct guu { int a; int b; float c; char d; };
extern void test(struct guu);
void caller()
{
test( (struct guu){.a = 3, .b = 5, .c = 7, .d = 9} );
test( (struct guu){.a = 3, .b = 5, .c = 7, .d = 9} );
}
CSE (or some other form of redundant loads optimization) pessimizes the code.
Problem occurs on optimization levels -O1 and higher, including -Os.
If the function "caller" calls test() just once, the resulting code is (-O3
-fno-optimize-sibling-calls, stack alignment/push/pops omitted for brevity):
movabs rdi, 21474836483
movabs rsi, 39743127552
call test
If "caller" calls test() twice, the code is a lot longer and not just twice as
long. (Stack alignment/push/pops omitted for brevity):
movabs rbp, 21474836483
mov rdi, rbp
movabs rbx, 38654705664
mov rsi, rbx
or rbx, 1088421888
or rsi, 1088421888
call test
mov rsi, rbx
mov rdi, rbp
call test
If we change caller() such that the parameters in the two calls are not
identical:
void caller()
{
test( (struct guu){.a = 3, .b = 5, .c = 7, .d = 9} );
test( (struct guu){.a = 3, .b = 6, .c = 7, .d = 10} );
}
The generated code is optimal again as expected:
movabs rdi, 21474836483
movabs rsi, 39743127552
call test
movabs rdi, 25769803779
movabs rsi, 44038094848
call test
The problem in the first examples is that the compiler sees that the same
parameter is used twice, and it tries to save it in a callee-saves register, in
order to reuse the same values on the second call. However re-initializing the
registers from scratch would have been more efficient.
The problem occurs on GCC versions 4.8.1 and newer. It does not occur in GCC
version 4.7.4, which generated different code that is otherwise inefficient.
For reference, the problem also exists in Clang versions 3.5 and newer, but not
in versions 3.4 and earlier.
>From gcc-bugs-return-628490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:52:27 2019
Return-Path: <gcc-bugs-return-628490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88425 invoked by alias); 9 Jan 2019 12:52:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88350 invoked by uid 48); 9 Jan 2019 12:52:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 12:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-xbCVboEZd7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01299.txt.bz2
Content-length: 1598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #28 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Wilco from comment #27)
> (In reply to Eric Botcazou from comment #22)
> > > Is it really pure RTL, therefore not used in tree? So the above patch using
> > > BITS_BIG_ENDIAN for tree stuff would be incorrect to use it?
> >
> > I wouldn't say incorrect, just inappropriate and unnecessary. And, yes, it
> > isn't used at the tree level and should stay so IMO. BYTES_BIG_ENDIAN alone
> > already implicitly enforces a numbering on bits.
>
> I mean incorrect as in the optimization would still trigger and give
> incorrect results if BITS_BIG_ENDIAN == BYTES_BIG_ENDIAN (given that
> BITS_BIG_ENDIAN has no bearing on the bitfield offsets used on tree level).
Given that it matters for
/* If I2 is setting a pseudo to a constant and I3 is setting some
sub-part of it to another constant, merge them by making a new
constant. */
if (i1 == 0
...
if (GET_CODE (dest) == ZERO_EXTRACT)
{
...
if (BITS_BIG_ENDIAN)
offset = GET_MODE_PRECISION (dest_mode) - width - offset;
and VN tries to do sth similar I wonder if it does matter after all...
That said, the docs also refer to 'bit-field instructions' but do not
elaborate further -- I guess zero_extract is such but I'd have guessed
BIT_FIELD_REF (on trees) is as well. But yes, RTL expansion adjusts
things based on BITS_BIG_ENDIAN so it looks like GENERIC doesn't care
(or assumes BITS_BIG_ENDIAN == BYTES_BIG_ENDIAN).
>From gcc-bugs-return-628491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 12:56:54 2019
Return-Path: <gcc-bugs-return-628491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15118 invoked by alias); 9 Jan 2019 12:56: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 7564 invoked by uid 48); 9 Jan 2019 12:56:49 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 12:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-M1zLdndmWh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01300.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #29 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #26)
> Did anybody test the patch? Testing on x86_64 will be quite pointless...
Well that generates _18 = BIT_FIELD_REF <_2, 16, 14>; and becomes:
ubfx x1, x20, 2, 16
This extracts bits 2-17 of the 30-bit value instead of bits 14-29. The issue is
that we're using a bitfield reference on a value that is claimed not to be a
bitfield in comment 6. So I can't see how using BIT_FIELD_REF could ever work
correctly.
>From gcc-bugs-return-628492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:01:29 2019
Return-Path: <gcc-bugs-return-628492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32114 invoked by alias); 9 Jan 2019 13:01: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 31891 invoked by uid 48); 9 Jan 2019 13:01:14 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 13:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-1XeMMxVyGd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01301.txt.bz2
Content-length: 667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #30 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> That said, the docs also refer to 'bit-field instructions' but do not
> elaborate further -- I guess zero_extract is such but I'd have guessed
> BIT_FIELD_REF (on trees) is as well. But yes, RTL expansion adjusts
> things based on BITS_BIG_ENDIAN so it looks like GENERIC doesn't care
> (or assumes BITS_BIG_ENDIAN == BYTES_BIG_ENDIAN).
Yes, BYTES_BIG_ENDIAN is implicitly propagated to bits at the tree level.
I don't think that we want to support BITS_BIG_ENDIAN != BYTES_BIG_ENDIAN at
the tree level, that would be a nightmare.
>From gcc-bugs-return-628493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:03:06 2019
Return-Path: <gcc-bugs-return-628493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35255 invoked by alias); 9 Jan 2019 13:03:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35044 invoked by uid 48); 9 Jan 2019 13:02:56 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 13:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88760-4-gAVgVIUqdL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01302.txt.bz2
Content-length: 1128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
Wilco <wilco at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilco at gcc dot gnu.org
--- Comment #4 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to ktkachov from comment #2)
> Created attachment 45386 [details]
> aarch64-llvm output with -Ofast -mcpu=cortex-a57
>
> I'm attaching the full LLVM aarch64 output.
>
> The output you quoted is with -funroll-loops. If that's not given, GCC
> doesn't seem to unroll by default at all (on aarch64 or x86_64 from my
> testing).
>
> Is there anything we can do to make the default unrolling a bit more
> aggressive?
I don't think the RTL unroller works at all. It doesn't have the right
settings, and doesn't understand how to unroll, so we always get inefficient
and bloated code.
To do unrolling correctly it has to be integrated at tree level - for example
when vectorization isn't possible/beneficial, unrolling might still be a good
idea.
>From gcc-bugs-return-628494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:16:09 2019
Return-Path: <gcc-bugs-return-628494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65674 invoked by alias); 9 Jan 2019 13:16: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 54133 invoked by uid 48); 9 Jan 2019 13:15:43 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88767-4-17BKFiiJZl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01303.txt.bz2
Content-length: 924
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |UNCONFIRMED
Ever confirmed|1 |0
--- Comment #2 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Hi Richard -- This was reported to us internally. The performance of this test
case on a P8 server indicates that disabling complete unrolling and applying
unroll-and-jam could produce about a 1.5x speedup. I am going to have our
performance team verify that this is the case using just the options that Li
Jia used; the original report modified the source to provide the results of
unroll-and-jam since the reporter didn't know how to disable cunrolli. I'll
post the results here when we have them.
>From gcc-bugs-return-628495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:18:45 2019
Return-Path: <gcc-bugs-return-628495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68091 invoked by alias); 9 Jan 2019 13:18: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 68041 invoked by uid 48); 9 Jan 2019 13:18:40 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Wed, 09 Jan 2019 13:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail 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-88763-4-tkHmcOtdSF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01304.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #3 from Marius Messerschmidt <marius.messerschmidt at googlemail dot com> ---
Sorry but I do not fully understand what you mean. Do you suggest using
different command line arguments?
So far I tried:
-fdump-tree-all
-fdump-tree-unswitch
and
-fopt-info-all-optall
But none of them told me the all the things that I would wish to know, most
important the reason why a particular loop was skipped during unswitching (e.g.
because it is not invariant or so (right now it already reports a few things
with -fdump-tree-unswitch like too-many-instructions or too-many-branches))
>From gcc-bugs-return-628496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:19:17 2019
Return-Path: <gcc-bugs-return-628496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69016 invoked by alias); 9 Jan 2019 13:19:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68930 invoked by uid 48); 9 Jan 2019 13:19:12 -0000
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88767-4-5DSEkp9c2e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01305.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
--- Comment #3 from Michael Matz <matz at gcc dot gnu.org> ---
I don't see anything to improve either (as far as unroll-and-jam is concerned).
It's quite possible that cunrolli is harming more than helping in this case,
but with it disabled it seems the code is as it should be.
So, please state what you want to see changed: unroll-and-jam or cunrolli?
>From gcc-bugs-return-628497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:20:06 2019
Return-Path: <gcc-bugs-return-628497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70287 invoked by alias); 9 Jan 2019 13:20:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70127 invoked by uid 55); 9 Jan 2019 13:20:01 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 13:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-MqSkDDr0Yv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01306.txt.bz2
Content-length: 4181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #31 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
>
> --- Comment #29 from Wilco <wilco at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #26)
>
> > Did anybody test the patch? Testing on x86_64 will be quite pointless...
>
> Well that generates _18 = BIT_FIELD_REF <_2, 16, 14>; and becomes:
>
> ubfx x1, x20, 2, 16
>
> This extracts bits 2-17 of the 30-bit value instead of bits 14-29. The issue is
> that we're using a bitfield reference on a value that is claimed not to be a
> bitfield in comment 6. So I can't see how using BIT_FIELD_REF could ever work
> correctly.
So that's because TYPE_PRECISION != GET_MODE_PRECISION and the
BIT_FIELD_REF expansion counting from GET_MODE_PRECISION I suppose.
Thus there is a RTL expansion side of the bug after all?
The "fixed" RTL is
(insn 6 5 7 (set (reg:SI 95)
(lshiftrt:SI (reg/v:SI 94 [ ulAddr ])
(const_int 2 [0x2]))) "t.c":42:48 -1
(nil))
(insn 7 6 8 (set (reg:SI 96)
(and:SI (reg:SI 95)
(const_int 1073741823 [0x3fffffff]))) "t.c":42:48 -1
(nil))
(insn 8 7 9 (set (subreg:DI (reg:HI 97) 0)
(zero_extract:DI (subreg:DI (reg:SI 96) 0)
(const_int 16 [0x10])
(const_int 2 [0x2]))) "t.c":44:8 -1
(nil))
so the 30bit value is in reg:SI 96 (the :30 cast causes the
and with 0x3fffffff) but then the zero_extract we generate
is bogus.
So maybe the :30 cast should have been a shift for BYTES_BIG_ENDIAN?
We might be able to work around this by optimization on GIMPLE,
combining
_1 = ulAddr_3(D) >> 2;
_2 = (<unnamed-unsigned:30>) _1;
_6 = BIT_FIELD_REF <_2, 16, 14>;
as far as eliminating at least the non-mode precision type...
Of course that would just work around the underlying RTL expansion
bug?
Note we can end up with things like
_2 = (<unnamed-unsigned:35) _1;
_3 = (<unnamed-unsigned:35) _4;
_5 = _2 + 3;
as well so shifting at the conversion might not be the correct
answer (but instead BIT_FIELD_REF expansion needs to be fixed).
Alternatively we could declare it invalid GIMPLE and require
BIT_FIELD_REF positions to be always relative to the mode
(but then I'd rather disallow BIT_FIELD_REF on non-mode
precision entities...).
Sth like the following might fix the RTL expansion issue
which then generates
Test_func:
ubfx x0, x0, 2, 16
cmp w0, 1
bne .L6
mov w0, 0
and just
(insn 6 5 7 (set (reg:SI 95)
(lshiftrt:SI (reg/v:SI 94 [ ulAddr ])
(const_int 2 [0x2]))) "t.c":42:48 -1
(nil))
(insn 7 6 8 (set (reg:SI 96)
(and:SI (reg:SI 95)
(const_int 1073741823 [0x3fffffff]))) "t.c":42:48 -1
(nil))
(insn 8 7 9 (set (reg:SI 97)
(zero_extend:SI (subreg:HI (reg:SI 96) 2))) "t.c":44:8 -1
(nil))
Index: gcc/expr.c
===================================================================
--- gcc/expr.c (revision 267553)
+++ gcc/expr.c (working copy)
@@ -10562,6 +10562,15 @@ expand_expr_real_1 (tree exp, rtx target
infinitely recurse. */
gcc_assert (tem != exp);
+ /* When extracting from non-mode bitsize entities adjust the
+ bit position for BYTES_BIG_ENDIAN. */
+ if (INTEGRAL_TYPE_P (TREE_TYPE (tem))
+ && (TYPE_PRECISION (TREE_TYPE (tem))
+ < GET_MODE_BITSIZE (as_a <scalar_int_mode> (TYPE_MODE
(TREE_TYPE (tem)))))
+ && BYTES_BIG_ENDIAN)
+ bitpos += (GET_MODE_BITSIZE (as_a <scalar_int_mode> (TYPE_MODE
(TREE_TYPE (tem))))
+ - TYPE_PRECISION (TREE_TYPE (tem)));
+
/* If TEM's type is a union of variable size, pass TARGET to the
inner
computation, since it will need a temporary and TARGET is known
to have to do. This occurs in unchecked conversion in Ada. */
>From gcc-bugs-return-628498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:21:47 2019
Return-Path: <gcc-bugs-return-628498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72895 invoked by alias); 9 Jan 2019 13:21:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72797 invoked by uid 55); 9 Jan 2019 13:21:41 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88767-4-HeZL6Kzn4C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01307.txt.bz2
Content-length: 1487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, wschmidt at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
>
> Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|WAITING |UNCONFIRMED
> Ever confirmed|1 |0
>
> --- Comment #2 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
> Hi Richard -- This was reported to us internally. The performance of this test
> case on a P8 server indicates that disabling complete unrolling and applying
> unroll-and-jam could produce about a 1.5x speedup. I am going to have our
> performance team verify that this is the case using just the options that Li
> Jia used; the original report modified the source to provide the results of
> unroll-and-jam since the reporter didn't know how to disable cunrolli. I'll
> post the results here when we have them.
Note for cases like this it would be nice to extend our set of loop
pragmas so you could say
#pragma GCC loop unroll-and-jam [factor]
on the outer loop which should then disable unrolling of the inner.
If source modification is possible, that is. Using
-fdisable-tree-cunrolli isn't meant to be a "production thing"
>From gcc-bugs-return-628499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:22:54 2019
Return-Path: <gcc-bugs-return-628499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74169 invoked by alias); 9 Jan 2019 13:22: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 74104 invoked by uid 48); 9 Jan 2019 13:22:50 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88767-4-mGRzNqyF7c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01308.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
--- Comment #5 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
From the original reporter:
Partially unrolling the outermost loop in the innermost loop body enables data
reuse for array A (see source) thereby improving the mem-ops/compute ratio and
providing the performance gain.
>From gcc-bugs-return-628500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:23:58 2019
Return-Path: <gcc-bugs-return-628500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75436 invoked by alias); 9 Jan 2019 13:23:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75371 invoked by uid 48); 9 Jan 2019 13:23:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 13:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-vZbYaaEcVT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01309.txt.bz2
Content-length: 4760
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #32 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #31)
> On Wed, 9 Jan 2019, wilco at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
> >
> > --- Comment #29 from Wilco <wilco at gcc dot gnu.org> ---
> > (In reply to Richard Biener from comment #26)
> >
> > > Did anybody test the patch? Testing on x86_64 will be quite pointless...
> >
> > Well that generates _18 = BIT_FIELD_REF <_2, 16, 14>; and becomes:
> >
> > ubfx x1, x20, 2, 16
> >
> > This extracts bits 2-17 of the 30-bit value instead of bits 14-29. The issue is
> > that we're using a bitfield reference on a value that is claimed not to be a
> > bitfield in comment 6. So I can't see how using BIT_FIELD_REF could ever work
> > correctly.
>
> So that's because TYPE_PRECISION != GET_MODE_PRECISION and the
> BIT_FIELD_REF expansion counting from GET_MODE_PRECISION I suppose.
>
> Thus there is a RTL expansion side of the bug after all?
>
> The "fixed" RTL is
>
> (insn 6 5 7 (set (reg:SI 95)
> (lshiftrt:SI (reg/v:SI 94 [ ulAddr ])
> (const_int 2 [0x2]))) "t.c":42:48 -1
> (nil))
>
> (insn 7 6 8 (set (reg:SI 96)
> (and:SI (reg:SI 95)
> (const_int 1073741823 [0x3fffffff]))) "t.c":42:48 -1
> (nil))
>
> (insn 8 7 9 (set (subreg:DI (reg:HI 97) 0)
> (zero_extract:DI (subreg:DI (reg:SI 96) 0)
> (const_int 16 [0x10])
> (const_int 2 [0x2]))) "t.c":44:8 -1
> (nil))
>
> so the 30bit value is in reg:SI 96 (the :30 cast causes the
> and with 0x3fffffff) but then the zero_extract we generate
> is bogus.
>
> So maybe the :30 cast should have been a shift for BYTES_BIG_ENDIAN?
>
> We might be able to work around this by optimization on GIMPLE,
> combining
>
> _1 = ulAddr_3(D) >> 2;
> _2 = (<unnamed-unsigned:30>) _1;
> _6 = BIT_FIELD_REF <_2, 16, 14>;
>
> as far as eliminating at least the non-mode precision type...
>
> Of course that would just work around the underlying RTL expansion
> bug?
>
> Note we can end up with things like
>
> _2 = (<unnamed-unsigned:35) _1;
> _3 = (<unnamed-unsigned:35) _4;
> _5 = _2 + 3;
>
> as well so shifting at the conversion might not be the correct
> answer (but instead BIT_FIELD_REF expansion needs to be fixed).
>
> Alternatively we could declare it invalid GIMPLE and require
> BIT_FIELD_REF positions to be always relative to the mode
> (but then I'd rather disallow BIT_FIELD_REF on non-mode
> precision entities...).
>
> Sth like the following might fix the RTL expansion issue
> which then generates
>
> Test_func:
> ubfx x0, x0, 2, 16
> cmp w0, 1
> bne .L6
> mov w0, 0
>
> and just
>
> (insn 6 5 7 (set (reg:SI 95)
> (lshiftrt:SI (reg/v:SI 94 [ ulAddr ])
> (const_int 2 [0x2]))) "t.c":42:48 -1
> (nil))
>
> (insn 7 6 8 (set (reg:SI 96)
> (and:SI (reg:SI 95)
> (const_int 1073741823 [0x3fffffff]))) "t.c":42:48 -1
> (nil))
>
> (insn 8 7 9 (set (reg:SI 97)
> (zero_extend:SI (subreg:HI (reg:SI 96) 2))) "t.c":44:8 -1
> (nil))
>
> Index: gcc/expr.c
> ===================================================================
> --- gcc/expr.c (revision 267553)
> +++ gcc/expr.c (working copy)
> @@ -10562,6 +10562,15 @@ expand_expr_real_1 (tree exp, rtx target
> infinitely recurse. */
> gcc_assert (tem != exp);
>
> + /* When extracting from non-mode bitsize entities adjust the
> + bit position for BYTES_BIG_ENDIAN. */
> + if (INTEGRAL_TYPE_P (TREE_TYPE (tem))
> + && (TYPE_PRECISION (TREE_TYPE (tem))
> + < GET_MODE_BITSIZE (as_a <scalar_int_mode> (TYPE_MODE
> (TREE_TYPE (tem)))))
> + && BYTES_BIG_ENDIAN)
> + bitpos += (GET_MODE_BITSIZE (as_a <scalar_int_mode> (TYPE_MODE
> (TREE_TYPE (tem))))
> + - TYPE_PRECISION (TREE_TYPE (tem)));
> +
> /* If TEM's type is a union of variable size, pass TARGET to the
> inner
> computation, since it will need a temporary and TARGET is known
> to have to do. This occurs in unchecked conversion in Ada. */
Btw, this needs to be amended for WORDS_BIG_ENDIAN of course. I guess
we might even run into the case that such BIT_FIELD_REF references
a non-contiguous set of bits... (that's also true for BITS_BIG_ENDIAN !=
BYTES_BIG_ENDIAN I guess).
>From gcc-bugs-return-628501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:26:13 2019
Return-Path: <gcc-bugs-return-628501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90725 invoked by alias); 9 Jan 2019 13:26:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86710 invoked by uid 48); 9 Jan 2019 13:26:09 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88767-4-mBqgDAirvj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01310.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
--- Comment #6 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
Yes, we don't want to encourage disabling cunrolli by hand for production use.
This test case is interesting because it shows a tension between complete
unrolling of inner loops and classical HPC loop optimization, which wants
control over memory access patterns. I think we will eventually have to
address this more generally.
>From gcc-bugs-return-628502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:27:48 2019
Return-Path: <gcc-bugs-return-628502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6863 invoked by alias); 9 Jan 2019 13:27:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6780 invoked by uid 48); 9 Jan 2019 13:27:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88770] Redundant load opt. or CSE pessimizes code
Date: Wed, 09 Jan 2019 13:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88770-4-NxuBhmnk2B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88770-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88770-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01311.txt.bz2
Content-length: 710
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88770
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization, ra
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
CC| |vmakarov at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I guess being constants would make this a job for lra remat?
Confirmed also on trunk.
>From gcc-bugs-return-628503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:29:26 2019
Return-Path: <gcc-bugs-return-628503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12078 invoked by alias); 9 Jan 2019 13:29: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 11843 invoked by uid 48); 9 Jan 2019 13:29:21 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88767-4-lNflT4h987@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01312.txt.bz2
Content-length: 757
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
--- Comment #7 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
(In reply to Michael Matz from comment #3)
> I don't see anything to improve either (as far as unroll-and-jam is
> concerned).
> It's quite possible that cunrolli is harming more than helping in this case,
> but with it disabled it seems the code is as it should be.
>
> So, please state what you want to see changed: unroll-and-jam or cunrolli?
The question in my mind is what to do about the phase interaction between the
two. Classical optimizations of loop nests for HPC code optimize memory access
patterns, and cunrolli takes some of the options off the table before
unroll-and-jam (in this case) can analyze the loop.
>From gcc-bugs-return-628504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:31:23 2019
Return-Path: <gcc-bugs-return-628504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21717 invoked by alias); 9 Jan 2019 13:31: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 21658 invoked by uid 48); 9 Jan 2019 13:31:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88769] Call to sin() optimized away, disregarding possible side-effect (errno)
Date: Wed, 09 Jan 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component everconfirmed
Message-ID: <bug-88769-4-UuAHJZ09PJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01313.txt.bz2
Content-length: 867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88769
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
CC| |jsm28 at gcc dot gnu.org
Component|tree-optimization |c
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
This is because GCC thinks sin() doesn't set errno.
DEF_LIB_BUILTIN (BUILT_IN_SIN, "sin", BT_FN_DOUBLE_DOUBLE,
ATTR_MATHFN_FPROUNDING)
According to the C standard no error conditions are documented for sin or cos,
specifically no domain error is documented.
>From gcc-bugs-return-628505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:35:08 2019
Return-Path: <gcc-bugs-return-628505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90544 invoked by alias); 9 Jan 2019 13:35:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90460 invoked by uid 48); 9 Jan 2019 13:35:03 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 13:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-7JRj5gxiSB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01314.txt.bz2
Content-length: 1316
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #5 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Wilco from comment #4)
> (In reply to ktkachov from comment #2)
> > Created attachment 45386 [details]
> > aarch64-llvm output with -Ofast -mcpu=cortex-a57
> >
> > I'm attaching the full LLVM aarch64 output.
> >
> > The output you quoted is with -funroll-loops. If that's not given, GCC
> > doesn't seem to unroll by default at all (on aarch64 or x86_64 from my
> > testing).
> >
> > Is there anything we can do to make the default unrolling a bit more
> > aggressive?
>
> I don't think the RTL unroller works at all. It doesn't have the right
> settings, and doesn't understand how to unroll, so we always get inefficient
> and bloated code.
>
> To do unrolling correctly it has to be integrated at tree level - for
> example when vectorization isn't possible/beneficial, unrolling might still
> be a good idea.
To add some numbers to the conversation, the gain LLVM gets from default
unrolling is 4.5% on SPECINT2017 and 1.0% on SPECFP2017.
This clearly shows there is huge potential from unrolling, *if* we can teach
GCC to unroll properly like LLVM. That means early unrolling, using good
default settings and using a trailing loop rather than inefficient peeling.
>From gcc-bugs-return-628506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:36:34 2019
Return-Path: <gcc-bugs-return-628506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93281 invoked by alias); 9 Jan 2019 13:36: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 93181 invoked by uid 55); 9 Jan 2019 13:36:27 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Wed, 09 Jan 2019 13:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88767-4-9E1YNolEaH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01315.txt.bz2
Content-length: 1295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, wschmidt at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
>
> --- Comment #7 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
> (In reply to Michael Matz from comment #3)
> > I don't see anything to improve either (as far as unroll-and-jam is
> > concerned).
> > It's quite possible that cunrolli is harming more than helping in this case,
> > but with it disabled it seems the code is as it should be.
> >
> > So, please state what you want to see changed: unroll-and-jam or cunrolli?
>
> The question in my mind is what to do about the phase interaction between the
> two. Classical optimizations of loop nests for HPC code optimize memory access
> patterns, and cunrolli takes some of the options off the table before
> unroll-and-jam (in this case) can analyze the loop.
A improvement of the heuristics could be to turn down
--param max-completely-peel-times and friends for cunrolli.
cunrolli is important to remove abstraction in C++ since none of the
scalar optimization passes knows to unroll loops "virtually" (it's on
my list to experiment with such an idea for value-numbering)
>From gcc-bugs-return-628507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:37:33 2019
Return-Path: <gcc-bugs-return-628507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94915 invoked by alias); 9 Jan 2019 13:37:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94507 invoked by uid 48); 9 Jan 2019 13:37:28 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] New: [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 13:37: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01316.txt.bz2
Content-length: 1385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
Bug ID: 88771
Summary: [9 Regression] Misleading -Werror=array-bounds error
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Starting from r264956 I see error for:
$ cat om.i
typedef struct {
int a;
} * b;
char *c, *x;
int f;
void d() {
b e;
char a = f + 1 ?: f;
__builtin_strncpy(c, x, f);
if (a)
e->a = 0;
}
$ gcc om.i -c -O2 -Werror=array-bounds
om.i: In function ‘d’:
om.i:11:3: error: ‘__builtin_strncpy’ pointer overflow between offset 0 and
size [-1, 9223372036854775807] [-Werror=array-bounds]
11 | __builtin_strncpy(c, x, f);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
$ gcc om.i -c -O2 -Werror=array-bounds -m32
om.i: In function ‘d’:
om.i:11:3: error: ‘__builtin_strncpy’ pointer overflow between offset 0 and
size [4294967295, 2147483647] [-Werror=array-bounds]
11 | __builtin_strncpy(c, x, f);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
>From gcc-bugs-return-628508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:37:59 2019
Return-Path: <gcc-bugs-return-628508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95873 invoked by alias); 9 Jan 2019 13:37: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 95823 invoked by uid 48); 9 Jan 2019 13:37:55 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 13:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
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: 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: cf_reconfirmed_on cc cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-88771-4-zIIGlBgPhh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01317.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2019-1-9
CC| |msebor at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Known to work| |8.2.0
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-628509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:38:28 2019
Return-Path: <gcc-bugs-return-628509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97570 invoked by alias); 9 Jan 2019 13:38: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 97462 invoked by uid 55); 9 Jan 2019 13:38:23 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 13: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-yg29LYXhDi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01318.txt.bz2
Content-length: 1921
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
>
> --- Comment #5 from Wilco <wilco at gcc dot gnu.org> ---
> (In reply to Wilco from comment #4)
> > (In reply to ktkachov from comment #2)
> > > Created attachment 45386 [details]
> > > aarch64-llvm output with -Ofast -mcpu=cortex-a57
> > >
> > > I'm attaching the full LLVM aarch64 output.
> > >
> > > The output you quoted is with -funroll-loops. If that's not given, GCC
> > > doesn't seem to unroll by default at all (on aarch64 or x86_64 from my
> > > testing).
> > >
> > > Is there anything we can do to make the default unrolling a bit more
> > > aggressive?
> >
> > I don't think the RTL unroller works at all. It doesn't have the right
> > settings, and doesn't understand how to unroll, so we always get inefficient
> > and bloated code.
> >
> > To do unrolling correctly it has to be integrated at tree level - for
> > example when vectorization isn't possible/beneficial, unrolling might still
> > be a good idea.
>
> To add some numbers to the conversation, the gain LLVM gets from default
> unrolling is 4.5% on SPECINT2017 and 1.0% on SPECFP2017.
>
> This clearly shows there is huge potential from unrolling, *if* we can teach
> GCC to unroll properly like LLVM. That means early unrolling, using good
> default settings and using a trailing loop rather than inefficient peeling.
I don't see why this cannot be done on RTL where we have vastly more
information of whether there are execution resources that can be
used by unrolling. Note we also want unrolling to interleave
instructions to not rely on pre-reload scheduling which in turn means
having a good eye on register pressure (again sth not very well handled
on GIMPLE)
>From gcc-bugs-return-628510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:46:10 2019
Return-Path: <gcc-bugs-return-628510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53191 invoked by alias); 9 Jan 2019 13:46:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44518 invoked by uid 48); 9 Jan 2019 13:46:04 -0000
From: "per at pz dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88769] Call to sin() optimized away, disregarding possible side-effect (errno)
Date: Wed, 09 Jan 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: per at pz dot se
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88769-4-5j4EdPdJ7M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01319.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88769
--- Comment #2 from Per Zetterlund <per at pz dot se> ---
The POSIX standard describes domain error conditions for sin() :
http://pubs.opengroup.org/onlinepubs/9699919799/functions/sin.html .
I guess there is a discrepancy between the C standard and the POSIX standard in
this case.
>From gcc-bugs-return-628511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:46:53 2019
Return-Path: <gcc-bugs-return-628511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101473 invoked by alias); 9 Jan 2019 13:46:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98634 invoked by uid 48); 9 Jan 2019 13:46:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status everconfirmed
Message-ID: <bug-88771-4-FKrX200JP4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01320.txt.bz2
Content-length: 814
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's the restrict pass doing this after VRP figured we can simplify things
via threading:
# .MEM_22 = VDEF <.MEM_7(D)>
__builtin_strncpy (pretmp_9, pretmp_19, 18446744073709551615);
not sure what the warning is about though but I guess it's triggered
by seeing that e->a = 0 store?
The testcase seems to be reduced ad absurdum and the bisection looks odd.
Can you attach some original source?
>From gcc-bugs-return-628512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:49:37 2019
Return-Path: <gcc-bugs-return-628512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17094 invoked by alias); 9 Jan 2019 13:49: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 17051 invoked by uid 48); 9 Jan 2019 13:49:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88771-4-yZmrQsaauK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01321.txt.bz2
Content-length: 1113
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 45390
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45390&action=edit
original test-case
Original test that fails just with -m32:
$ gcc om-original.i -c -O2 -Werror=array-bounds -m32
In file included from /usr/include/string.h:494,
from /usr/include/X11/Xfuncs.h:46,
from ../../../include/X11/Xlibint.h:335,
from omGeneric.c:53:
In function ‘strncpy’,
inlined from ‘read_EncodingInfo’ at omGeneric.c:1836:9:
/usr/include/bits/string_fortified.h:106:10: error: ‘__builtin_strncpy’ pointer
overflow between offset 0 and size [4294967295, 2147483647]
[-Werror=array-bounds]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos
(__dest));
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
>From gcc-bugs-return-628513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:52:33 2019
Return-Path: <gcc-bugs-return-628513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31683 invoked by alias); 9 Jan 2019 13:52:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31200 invoked by uid 48); 9 Jan 2019 13:52:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 13:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-ykgS28RCUp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01322.txt.bz2
Content-length: 189
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Original test-case started to produce the warning since r263662.
>From gcc-bugs-return-628514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 13:59:47 2019
Return-Path: <gcc-bugs-return-628514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80556 invoked by alias); 9 Jan 2019 13:59:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80451 invoked by uid 48); 9 Jan 2019 13:59:39 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 09 Jan 2019 13:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-Ih5lY0clIs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01323.txt.bz2
Content-length: 3028
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #7 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #6)
> On Wed, 9 Jan 2019, wilco at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
> >
> > --- Comment #5 from Wilco <wilco at gcc dot gnu.org> ---
> > (In reply to Wilco from comment #4)
> > > (In reply to ktkachov from comment #2)
> > > > Created attachment 45386 [details]
> > > > aarch64-llvm output with -Ofast -mcpu=cortex-a57
> > > >
> > > > I'm attaching the full LLVM aarch64 output.
> > > >
> > > > The output you quoted is with -funroll-loops. If that's not given, GCC
> > > > doesn't seem to unroll by default at all (on aarch64 or x86_64 from my
> > > > testing).
> > > >
> > > > Is there anything we can do to make the default unrolling a bit more
> > > > aggressive?
> > >
> > > I don't think the RTL unroller works at all. It doesn't have the right
> > > settings, and doesn't understand how to unroll, so we always get inefficient
> > > and bloated code.
> > >
> > > To do unrolling correctly it has to be integrated at tree level - for
> > > example when vectorization isn't possible/beneficial, unrolling might still
> > > be a good idea.
> >
> > To add some numbers to the conversation, the gain LLVM gets from default
> > unrolling is 4.5% on SPECINT2017 and 1.0% on SPECFP2017.
> >
> > This clearly shows there is huge potential from unrolling, *if* we can teach
> > GCC to unroll properly like LLVM. That means early unrolling, using good
> > default settings and using a trailing loop rather than inefficient peeling.
>
> I don't see why this cannot be done on RTL where we have vastly more
> information of whether there are execution resources that can be
> used by unrolling. Note we also want unrolling to interleave
> instructions to not rely on pre-reload scheduling which in turn means
> having a good eye on register pressure (again sth not very well handled
> on GIMPLE)
The main issue is that other loop optimizations are done on tree, so things
like addressing modes, loop invariants, CSEs are run on the non-unrolled
version. Then when we unroll in RTL we end up with very non-optimal code.
Typical unrolled loop starts like this:
add x13, x2, 1
add x14, x2, 2
add x11, x2, 3
add x10, x2, 4
ldr w30, [x4, x13, lsl 2]
add x9, x2, 5
add x5, x2, 6
add x12, x2, 7
ldr d23, [x3, x2, lsl 3]
... rest of unrolled loop
So basically it decides to create a new induction variable for every unrolled
copy in the loop. This often leads to spills just because it creates way too
many redundant addressing instructions. It also blocks scheduling between
iterations since the alias optimization doesn't appear to understand simple
constant differences between indices.
So unrolling should definitely be done at a high level just like vectorization.
>From gcc-bugs-return-628515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:16:00 2019
Return-Path: <gcc-bugs-return-628515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118889 invoked by alias); 9 Jan 2019 14:16:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118705 invoked by uid 48); 9 Jan 2019 14:15:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Wed, 09 Jan 2019 14:16: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: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88450-4-pqrmMTWKro@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01324.txt.bz2
Content-length: 1958
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |uros at gcc dot gnu.org
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Because you are using -march=native -mtune=native by default, it is unclear
what exact ISA/tuning that is. From the dump I assume it must be something
with -mavx or -mavx2, so that is what I've used, but it would be nice to know
it more exact. Guess ./xgcc -B ./ -v -xc /dev/null -S would reveal that.
Anyway, seems on gimplify.ii the problematic change in assign_stack_local_1 is
triggered just once, and to me it looks completely unnecessarily.
assign_stack_temp_for_type is called with BLKmode, 24, and gimple_stmt_iterator
type. This is done because on the
seq = gsi_split_seq_after (iter);
call in gimplify_cleanup_point_expr inlined into gimplify_expr where iter is
clearly passed by invisible reference.
assign_stack_temp_for_type calls get_stack_local_alignment which does:
if (mode == BLKmode)
alignment = BIGGEST_ALIGNMENT;
else
alignment = GET_MODE_ALIGNMENT (mode);
/* Allow the frond-end to (possibly) increase the alignment of this
stack slot. */
if (! type)
type = lang_hooks.types.type_for_mode (mode, 0);
return STACK_SLOT_ALIGNMENT (type, mode, alignment);
It seems complete waste to me try to align the 24 byte structure to 32 byte
boundary and allocate 48 bytes for it on the stack, then dynamically adjust the
start so that it is 32 byte aligned. BIGGEST_ALIGNMENT is 256 bits because of
-mavx (could be even 512 bits for -mavx512f).
So, first of all, I'd think we should in i386 STACK_SLOT_ALIGNMENT undo this
unnecessary overalignment. But that doesn't explain why you get segfault
elsewhere.
>From gcc-bugs-return-628516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:18:14 2019
Return-Path: <gcc-bugs-return-628516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126282 invoked by alias); 9 Jan 2019 14:18: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 126195 invoked by uid 48); 9 Jan 2019 14:18:09 -0000
From: "ylatuya at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] New: Exception handling configured mode does not match the one finally used
Date: Wed, 09 Jan 2019 14:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ylatuya 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-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01325.txt.bz2
Content-length: 3693
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
Bug ID: 88772
Summary: Exception handling configured mode does not match the
one finally used
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: ylatuya at gmail dot com
Target Milestone: ---
I am building a multilib GCC+MinGW toolchain targeting Windows. I have built
the cross toolchain, which compiled and works correctly and I am now trying to
build the native one.
The cross toolchain is configured with:
../configure --prefix /home/andoni/mingw/linux/w64 --libdir
/home/andoni/mingw/linux/w64/lib --enable-introspection
--with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm'
--disable-shared --disable-libgomp --disable-libquadmath
--disable-libquadmath-support --disable-libmudflap --disable-libmpx
--disable-libssp --disable-nls --enable-threads=posix --enable-__cxa_atexit
--enable-lto --enable-plugin --enable-multiarch --enable-languages=c,c++
--enable-long-long
--with-sysroot=/home/andoni/mingw/linux/w64/x86_64-w64-mingw32/sysroot
--with-local-prefix=/home/andoni/mingw/linux/w64/x86_64-w64-mingw32/sysroot
--target=x86_64-w64-mingw32
The native toolchain is configured with the same settings, only changing the
host:
../configure --prefix /home/andoni/mingw/windows/w64 --libdir
/home/andoni/mingw/windows/w64/lib --disable-introspection
--with-host-libstdcxx='-static-libgcc -Wl,-Bstatic,-lstdc++,-Bdynamic -lm'
--disable-shared --disable-libgomp --disable-libquadmath
--disable-libquadmath-support --disable-libmudflap --disable-libmpx
--disable-libssp --disable-nls --enable-threads=posix --enable-__cxa_atexit
--enable-lto --enable-plugin --enable-multiarch --enable-languages=c,c++
--enable-long-long
--with-sysroot=/home/andoni/mingw/windows/w64/x86_64-w64-mingw32/sysroot
--with-local-prefix=/home/andoni/mingw/windows/w64/x86_64-w64-mingw32/sysroot
--target=x86_64-w64-mingw32 --host=x86_64-w64-mingw32
I none of them I force SJLJ or disable it, so from the documentation and the
headers it should be using SEH for 64 bits and SJLJ for 32 bits:
gcc/config/i386/cygming.h
369 /* If configured with --disable-sjlj-exceptions, use DWARF2 for 32-bit
370 mode else default to SJLJ. 64-bit code uses SEH unless you request
371 SJLJ. */
But what happens is that it ends up using i386/t-dw2-eh instead of
i386/t-seh-eh
and there is compilation error:
../../../../libgcc/unwind.inc: In function '_Unwind_RaiseException_Phase2':
../../../../libgcc/unwind.inc:53:62: error: 'struct _Unwind_Exception' has no
member named 'private_2'; did you mean 'private_'?
match_handler = (uw_identify_context (context) == exc->private_2
The error seems to be in the switch case for x86_64-mingw32 in
libgcc/config.host:
762 > # This has to match the logic for DWARF2_UNWIND_INFO in
gcc/config/i386/cygming.h
763 > if test x$ac_cv_sjlj_exceptions = xyes; then
764 > > tmake_eh_file="i386/t-sjlj-eh"
765 > elif test "${host_address}" = 32; then
766 > # biarch -m32 with --disable-sjlj-exceptions
767 > > tmake_eh_file="i386/t-dw2-eh"
768 > > md_unwind_header=i386/w32-unwind.h
769 > else
770 > > tmake_eh_file="i386/t-seh-eh"
771 > fi
^~~~~~~~~
private_
>From gcc-bugs-return-628517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:31:28 2019
Return-Path: <gcc-bugs-return-628517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108670 invoked by alias); 9 Jan 2019 14:31:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108135 invoked by uid 48); 9 Jan 2019 14:31:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Wed, 09 Jan 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-UGad1q9Nmh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01326.txt.bz2
Content-length: 2143
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The following patch does that. Guess the issues reported in this PR might go
away with that, but it is really just an attempt to fix inefficiency in the
generated code rather than fix the wrong-code issue we have somewhere.
--- gcc/config/i386/i386.c.jj 2019-01-08 22:33:34.605708026 +0100
+++ gcc/config/i386/i386.c 2019-01-09 15:11:35.902663636 +0100
@@ -29679,6 +29679,17 @@ ix86_local_alignment (tree exp, machine_
&& (!type || !TYPE_USER_ALIGN (type))
&& (!decl || !DECL_USER_ALIGN (decl)))
align = 32;
+ /* Similarly, don't do dynamic stack realignment just because
+ we need a BLKmode stack slot and have high BIGGEST_ALIGNMENT.
+ This is what get_stack_local_alignment returns regardless of
+ the actual needs, undo that here. */
+ if (align == BIGGEST_ALIGNMENT
+ && mode == BLKmode
+ && !decl
+ && type
+ && align > TYPE_ALIGN (type)
+ && align > MAX_SUPPORTED_STACK_ALIGNMENT)
+ align = MAX (TYPE_ALIGN (type), MAX_SUPPORTED_STACK_ALIGNMENT);
/* If TYPE is NULL, we are allocating a stack slot for caller-save
register in MODE. We will return the largest alignment of XF
--- gcc/function.c.jj 2019-01-09 11:15:31.539836837 +0100
+++ gcc/function.c 2019-01-09 15:10:52.971371328 +0100
@@ -919,8 +919,10 @@ assign_stack_temp_for_type (machine_mode
So for requests which depended on the rounding of SIZE, we go ahead
and round it now. We also make sure ALIGNMENT is at least
- BIGGEST_ALIGNMENT. */
- gcc_assert (mode != BLKmode || align == BIGGEST_ALIGNMENT);
+ minimum of BIGGEST_ALIGNMENT and MAX_SUPPORTED_STACK_ALIGNMENT. */
+ gcc_assert (mode != BLKmode
+ || align >= MIN (BIGGEST_ALIGNMENT,
+ MAX_SUPPORTED_STACK_ALIGNMENT));
p->slot = assign_stack_local_1 (mode,
(mode == BLKmode
? aligned_upper_bound (size,
>From gcc-bugs-return-628518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:33:49 2019
Return-Path: <gcc-bugs-return-628518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118496 invoked by alias); 9 Jan 2019 14:33: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 118402 invoked by uid 48); 9 Jan 2019 14:33:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Wed, 09 Jan 2019 14:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-r8NsVvkaS7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01327.txt.bz2
Content-length: 1038
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #23 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #22)
> Things we fail to disambiguate are
>
> (mem:TF (pre_dec:SI (reg/f:SI 7 sp)) [0 S16 A8])
> vs.
> (mem/c:TF (plus:SI (reg/f:SI 19 frame)
> (const_int -16 [0xfffffffffffffff0])) [1 S16 A128])
>
> or
>
> (mem:SI (pre_dec:SI (reg/f:SI 7 sp)) [3 S4 A32])
> vs.
> (mem/f/c:SI (symbol_ref:SI ("argv") [flags 0x2] <var_decl 0x7f782d1e6360
> argv>) [2 argv+0 S4 A32])
>
> where I don't find anything besides CSELIB cselib_sp_based_value_p handling
> in find_base_term that could be the one handling it?
>
> I guess we should be able to somehow handle both sp and frame based
> accesses in a more conservative way?
it's really 99% like this which is why eventually that CONST_INT restriction
worked so "well".
Can we easily identify spill slot accesses somehow? The parameter accesses
(frame references?) should simply get appropriate MEM_EXPRs IMHO.
>From gcc-bugs-return-628519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:35:02 2019
Return-Path: <gcc-bugs-return-628519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120824 invoked by alias); 9 Jan 2019 14:35: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 120645 invoked by uid 55); 9 Jan 2019 14:34:54 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-uYRecmKrUg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01328.txt.bz2
Content-length: 4883
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #14 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Wed Jan 9 14:34:20 2019
New Revision: 267771
URL: https://gcc.gnu.org/viewcvs?rev=267771&root=gcc&view=rev
Log:
PR target/84010
* config/sparc/sparc.c (sparc_legitimize_tls_address): Only use Pmode
consistently in TLS address generation and adjust code to the renaming
of patterns. Mark calls to __tls_get_addr as const.
* config/sparc/sparc.md (tgd_hi22): Turn into...
(tgd_hi22<P:mode>): ...this and use Pmode throughout.
(tgd_lo10): Turn into...
(tgd_lo10<P:mode>): ...this and use Pmode throughout.
(tgd_add32): Merge into...
(tgd_add64): Likewise.
(tgd_add<P:mode>): ...this and use Pmode throughout.
(tldm_hi22): Turn into...
(tldm_hi22<P:mode>): ...this and use Pmode throughout.
(tldm_lo10): Turn into...
(tldm_lo10<P:mode>): ...this and use Pmode throughout.
(tldm_add32): Merge into...
(tldm_add64): Likewise.
(tldm_add<P:mode>): ...this and use Pmode throughout.
(tldm_call32): Merge into...
(tldm_call64): Likewise.
(tldm_call<P:mode>): ...this and use Pmode throughout.
(tldo_hix22): Turn into...
(tldo_hix22<P:mode>): ...this and use Pmode throughout.
(tldo_lox10): Turn into...
(tldo_lox10<P:mode>): ...this and use Pmode throughout.
(tldo_add32): Merge into...
(tldo_add64): Likewise.
(tldo_add<P:mode>): ...this and use Pmode throughout.
(tie_hi22): Turn into...
(tie_hi22<P:mode>): ...this and use Pmode throughout.
(tie_lo10): Turn into...
(tie_lo10<P:mode>): ...this and use Pmode throughout.
(tie_ld64): Use DImode throughout.
(tie_add32): Merge into...
(tie_add64): Likewise.
(tie_add<P:mode>): ...this and use Pmode throughout.
(tle_hix22_sp32): Merge into...
(tle_hix22_sp64): Likewise.
(tle_hix22<P:mode>): ...this and use Pmode throughout.
(tle_lox22_sp32): Merge into...
(tle_lox22_sp64): Likewise.
(tle_lox22<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub_sp32): Merge into...
(*tldo_ldub_sp64): Likewise.
(*tldo_ldub<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub1_sp32): Merge into...
(*tldo_ldub1_sp64): Likewise.
(*tldo_ldub1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub2_sp32): Merge into...
(*tldo_ldub2_sp64): Likewise.
(*tldo_ldub2<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsb1_sp32): Merge into...
(*tldo_ldsb1_sp64): Likewise.
(*tldo_ldsb1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsb2_sp32): Merge into...
(*tldo_ldsb2_sp64): Likewise.
(*tldo_ldsb2<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub3_sp64): Use DImode throughout.
(*tldo_ldsb3_sp64): Likewise.
(*tldo_lduh_sp32): Merge into...
(*tldo_lduh_sp64): Likewise.
(*tldo_lduh<P:mode>): ...this and use Pmode throughout.
(*tldo_lduh1_sp32): Merge into...
(*tldo_lduh1_sp64): Likewise.
(*tldo_lduh1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsh1_sp32): Merge into...
(*tldo_ldsh1_sp64): Likewise.
(*tldo_ldsh1<P:mode>): ...this and use Pmode throughout.
(*tldo_lduh2_sp64): Use DImode throughout.
(*tldo_ldsh2_sp64): Likewise.
(*tldo_lduw_sp32): Merge into...
(*tldo_lduw_sp64): Likewise.
(*tldo_lduw<P:mode>): ...this and use Pmode throughout.
(*tldo_lduw1_sp64): Use DImode throughout.
(*tldo_ldsw1_sp64): Likewise.
(*tldo_ldx_sp64): Likewise.
(*tldo_stb_sp32): Merge into...
(*tldo_stb_sp64): Likewise.
(*tldo_stb<P:mode>): ...this and use Pmode throughout.
(*tldo_sth_sp32): Merge into...
(*tldo_sth_sp64): Likewise.
(*tldo_sth<P:mode>): ...this and use Pmode throughout.
(*tldo_stw_sp32): Merge into...
(*tldo_stw_sp64): Likewise.
(*tldo_stw<P:mode>): ...this and use Pmode throughout.
(*tldo_stx_sp64): Use DImode throughout.
Added:
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int16.c
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int32.c
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int64.c
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int8.c
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint16.c
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint32.c
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint8.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/sparc/sparc.c
trunk/gcc/config/sparc/sparc.md
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:39:59 2019
Return-Path: <gcc-bugs-return-628521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11275 invoked by alias); 9 Jan 2019 14:39:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11157 invoked by uid 55); 9 Jan 2019 14:39:53 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-igszxjjMK4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01330.txt.bz2
Content-length: 5697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #15 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Wed Jan 9 14:39:18 2019
New Revision: 267772
URL: https://gcc.gnu.org/viewcvs?rev=267772&root=gcc&view=rev
Log:
PR target/84010
* config/sparc/sparc.c (sparc_legitimize_tls_address): Only use Pmode
consistently in TLS address generation and adjust code to the renaming
of patterns. Mark calls to __tls_get_addr as const.
* config/sparc/sparc.md (tgd_hi22): Turn into...
(tgd_hi22<P:mode>): ...this and use Pmode throughout.
(tgd_lo10): Turn into...
(tgd_lo10<P:mode>): ...this and use Pmode throughout.
(tgd_add32): Merge into...
(tgd_add64): Likewise.
(tgd_add<P:mode>): ...this and use Pmode throughout.
(tldm_hi22): Turn into...
(tldm_hi22<P:mode>): ...this and use Pmode throughout.
(tldm_lo10): Turn into...
(tldm_lo10<P:mode>): ...this and use Pmode throughout.
(tldm_add32): Merge into...
(tldm_add64): Likewise.
(tldm_add<P:mode>): ...this and use Pmode throughout.
(tldm_call32): Merge into...
(tldm_call64): Likewise.
(tldm_call<P:mode>): ...this and use Pmode throughout.
(tldo_hix22): Turn into...
(tldo_hix22<P:mode>): ...this and use Pmode throughout.
(tldo_lox10): Turn into...
(tldo_lox10<P:mode>): ...this and use Pmode throughout.
(tldo_add32): Merge into...
(tldo_add64): Likewise.
(tldo_add<P:mode>): ...this and use Pmode throughout.
(tie_hi22): Turn into...
(tie_hi22<P:mode>): ...this and use Pmode throughout.
(tie_lo10): Turn into...
(tie_lo10<P:mode>): ...this and use Pmode throughout.
(tie_ld64): Use DImode throughout.
(tie_add32): Merge into...
(tie_add64): Likewise.
(tie_add<P:mode>): ...this and use Pmode throughout.
(tle_hix22_sp32): Merge into...
(tle_hix22_sp64): Likewise.
(tle_hix22<P:mode>): ...this and use Pmode throughout.
(tle_lox22_sp32): Merge into...
(tle_lox22_sp64): Likewise.
(tle_lox22<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub_sp32): Merge into...
(*tldo_ldub_sp64): Likewise.
(*tldo_ldub<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub1_sp32): Merge into...
(*tldo_ldub1_sp64): Likewise.
(*tldo_ldub1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub2_sp32): Merge into...
(*tldo_ldub2_sp64): Likewise.
(*tldo_ldub2<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsb1_sp32): Merge into...
(*tldo_ldsb1_sp64): Likewise.
(*tldo_ldsb1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsb2_sp32): Merge into...
(*tldo_ldsb2_sp64): Likewise.
(*tldo_ldsb2<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub3_sp64): Use DImode throughout.
(*tldo_ldsb3_sp64): Likewise.
(*tldo_lduh_sp32): Merge into...
(*tldo_lduh_sp64): Likewise.
(*tldo_lduh<P:mode>): ...this and use Pmode throughout.
(*tldo_lduh1_sp32): Merge into...
(*tldo_lduh1_sp64): Likewise.
(*tldo_lduh1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsh1_sp32): Merge into...
(*tldo_ldsh1_sp64): Likewise.
(*tldo_ldsh1<P:mode>): ...this and use Pmode throughout.
(*tldo_lduh2_sp64): Use DImode throughout.
(*tldo_ldsh2_sp64): Likewise.
(*tldo_lduw_sp32): Merge into...
(*tldo_lduw_sp64): Likewise.
(*tldo_lduw<P:mode>): ...this and use Pmode throughout.
(*tldo_lduw1_sp64): Use DImode throughout.
(*tldo_ldsw1_sp64): Likewise.
(*tldo_ldx_sp64): Likewise.
(*tldo_stb_sp32): Merge into...
(*tldo_stb_sp64): Likewise.
(*tldo_stb<P:mode>): ...this and use Pmode throughout.
(*tldo_sth_sp32): Merge into...
(*tldo_sth_sp64): Likewise.
(*tldo_sth<P:mode>): ...this and use Pmode throughout.
(*tldo_stw_sp32): Merge into...
(*tldo_stw_sp64): Likewise.
(*tldo_stw<P:mode>): ...this and use Pmode throughout.
(*tldo_stx_sp64): Use DImode throughout.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int16.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int16.c
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int32.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int32.c
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int64.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int64.c
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int8.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int8.c
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-uint16.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint16.c
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-uint32.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint32.c
branches/gcc-8-branch/gcc/testsuite/gcc.target/sparc/tls-ld-uint8.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint8.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/sparc/sparc.c
branches/gcc-8-branch/gcc/config/sparc/sparc.md
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:39:24 2019
Return-Path: <gcc-bugs-return-628520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10056 invoked by alias); 9 Jan 2019 14:39: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 9679 invoked by uid 48); 9 Jan 2019 14:39:18 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-dUDRtFIwbO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01329.txt.bz2
Content-length: 2047
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #33 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #32)
> >
> > Index: gcc/expr.c
> > ===================================================================
> > --- gcc/expr.c (revision 267553)
> > +++ gcc/expr.c (working copy)
> > @@ -10562,6 +10562,15 @@ expand_expr_real_1 (tree exp, rtx target
> > infinitely recurse. */
> > gcc_assert (tem != exp);
> >
> > + /* When extracting from non-mode bitsize entities adjust the
> > + bit position for BYTES_BIG_ENDIAN. */
> > + if (INTEGRAL_TYPE_P (TREE_TYPE (tem))
> > + && (TYPE_PRECISION (TREE_TYPE (tem))
> > + < GET_MODE_BITSIZE (as_a <scalar_int_mode> (TYPE_MODE
> > (TREE_TYPE (tem)))))
> > + && BYTES_BIG_ENDIAN)
> > + bitpos += (GET_MODE_BITSIZE (as_a <scalar_int_mode> (TYPE_MODE
> > (TREE_TYPE (tem))))
> > + - TYPE_PRECISION (TREE_TYPE (tem)));
> > +
> > /* If TEM's type is a union of variable size, pass TARGET to the
> > inner
> > computation, since it will need a temporary and TARGET is known
> > to have to do. This occurs in unchecked conversion in Ada. */
>
> Btw, this needs to be amended for WORDS_BIG_ENDIAN of course. I guess
> we might even run into the case that such BIT_FIELD_REF references
> a non-contiguous set of bits... (that's also true for BITS_BIG_ENDIAN !=
> BYTES_BIG_ENDIAN I guess).
Was that meant to be instead or in addition to the tree-ssa-sccvn.c patch? With
both I get:
lsr w20, w1, 2
...
and w1, w20, 65535
With only the expr.c patch it starts to look as expected:
lsr w20, w1, 2
...
lsr w1, w20, 14
And with the latter case the new torture test now passes on big-endian!
>From gcc-bugs-return-628522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:42:33 2019
Return-Path: <gcc-bugs-return-628522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22818 invoked by alias); 9 Jan 2019 14: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 22705 invoked by uid 55); 9 Jan 2019 14:42:27 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-Tbcs96omzd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01331.txt.bz2
Content-length: 5697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #16 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Wed Jan 9 14:41:55 2019
New Revision: 267773
URL: https://gcc.gnu.org/viewcvs?rev=267773&root=gcc&view=rev
Log:
PR target/84010
* config/sparc/sparc.c (sparc_legitimize_tls_address): Only use Pmode
consistently in TLS address generation and adjust code to the renaming
of patterns. Mark calls to __tls_get_addr as const.
* config/sparc/sparc.md (tgd_hi22): Turn into...
(tgd_hi22<P:mode>): ...this and use Pmode throughout.
(tgd_lo10): Turn into...
(tgd_lo10<P:mode>): ...this and use Pmode throughout.
(tgd_add32): Merge into...
(tgd_add64): Likewise.
(tgd_add<P:mode>): ...this and use Pmode throughout.
(tldm_hi22): Turn into...
(tldm_hi22<P:mode>): ...this and use Pmode throughout.
(tldm_lo10): Turn into...
(tldm_lo10<P:mode>): ...this and use Pmode throughout.
(tldm_add32): Merge into...
(tldm_add64): Likewise.
(tldm_add<P:mode>): ...this and use Pmode throughout.
(tldm_call32): Merge into...
(tldm_call64): Likewise.
(tldm_call<P:mode>): ...this and use Pmode throughout.
(tldo_hix22): Turn into...
(tldo_hix22<P:mode>): ...this and use Pmode throughout.
(tldo_lox10): Turn into...
(tldo_lox10<P:mode>): ...this and use Pmode throughout.
(tldo_add32): Merge into...
(tldo_add64): Likewise.
(tldo_add<P:mode>): ...this and use Pmode throughout.
(tie_hi22): Turn into...
(tie_hi22<P:mode>): ...this and use Pmode throughout.
(tie_lo10): Turn into...
(tie_lo10<P:mode>): ...this and use Pmode throughout.
(tie_ld64): Use DImode throughout.
(tie_add32): Merge into...
(tie_add64): Likewise.
(tie_add<P:mode>): ...this and use Pmode throughout.
(tle_hix22_sp32): Merge into...
(tle_hix22_sp64): Likewise.
(tle_hix22<P:mode>): ...this and use Pmode throughout.
(tle_lox22_sp32): Merge into...
(tle_lox22_sp64): Likewise.
(tle_lox22<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub_sp32): Merge into...
(*tldo_ldub_sp64): Likewise.
(*tldo_ldub<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub1_sp32): Merge into...
(*tldo_ldub1_sp64): Likewise.
(*tldo_ldub1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub2_sp32): Merge into...
(*tldo_ldub2_sp64): Likewise.
(*tldo_ldub2<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsb1_sp32): Merge into...
(*tldo_ldsb1_sp64): Likewise.
(*tldo_ldsb1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsb2_sp32): Merge into...
(*tldo_ldsb2_sp64): Likewise.
(*tldo_ldsb2<P:mode>): ...this and use Pmode throughout.
(*tldo_ldub3_sp64): Use DImode throughout.
(*tldo_ldsb3_sp64): Likewise.
(*tldo_lduh_sp32): Merge into...
(*tldo_lduh_sp64): Likewise.
(*tldo_lduh<P:mode>): ...this and use Pmode throughout.
(*tldo_lduh1_sp32): Merge into...
(*tldo_lduh1_sp64): Likewise.
(*tldo_lduh1<P:mode>): ...this and use Pmode throughout.
(*tldo_ldsh1_sp32): Merge into...
(*tldo_ldsh1_sp64): Likewise.
(*tldo_ldsh1<P:mode>): ...this and use Pmode throughout.
(*tldo_lduh2_sp64): Use DImode throughout.
(*tldo_ldsh2_sp64): Likewise.
(*tldo_lduw_sp32): Merge into...
(*tldo_lduw_sp64): Likewise.
(*tldo_lduw<P:mode>): ...this and use Pmode throughout.
(*tldo_lduw1_sp64): Use DImode throughout.
(*tldo_ldsw1_sp64): Likewise.
(*tldo_ldx_sp64): Likewise.
(*tldo_stb_sp32): Merge into...
(*tldo_stb_sp64): Likewise.
(*tldo_stb<P:mode>): ...this and use Pmode throughout.
(*tldo_sth_sp32): Merge into...
(*tldo_sth_sp64): Likewise.
(*tldo_sth<P:mode>): ...this and use Pmode throughout.
(*tldo_stw_sp32): Merge into...
(*tldo_stw_sp64): Likewise.
(*tldo_stw<P:mode>): ...this and use Pmode throughout.
(*tldo_stx_sp64): Use DImode throughout.
Added:
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int16.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int16.c
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int32.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int32.c
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int64.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int64.c
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-int8.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-int8.c
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-uint16.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint16.c
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-uint32.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint32.c
branches/gcc-7-branch/gcc/testsuite/gcc.target/sparc/tls-ld-uint8.c
- copied unchanged from r267771,
trunk/gcc/testsuite/gcc.target/sparc/tls-ld-uint8.c
Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/config/sparc/sparc.c
branches/gcc-7-branch/gcc/config/sparc/sparc.md
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:47:04 2019
Return-Path: <gcc-bugs-return-628523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51006 invoked by alias); 9 Jan 2019 14:47:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50921 invoked by uid 48); 9 Jan 2019 14:46:59 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: jrtc27 at jrtc27 dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-zxDrG7L5sl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01332.txt.bz2
Content-length: 189
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #17 from James Clarke <jrtc27 at jrtc27 dot com> ---
Ah, great, thanks, that's indeed a nicer way of writing the patterns.
>From gcc-bugs-return-628524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:50:38 2019
Return-Path: <gcc-bugs-return-628524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67054 invoked by alias); 9 Jan 2019 14:50:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66978 invoked by uid 48); 9 Jan 2019 14:50:34 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-84010-4-CMIZlasbiz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01333.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Fixed at last in upcoming 7.5, 8.3 and 9.x releases.
>From gcc-bugs-return-628525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:52:30 2019
Return-Path: <gcc-bugs-return-628525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74447 invoked by alias); 9 Jan 2019 14:52: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 74359 invoked by uid 48); 9 Jan 2019 14:52:26 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-rBFtfeIhUd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01334.txt.bz2
Content-length: 278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #19 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Ah, great, thanks, that's indeed a nicer way of writing the patterns.
You're welcome. Don't hesitate to ping next time I drop the ball for so long.
>From gcc-bugs-return-628526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:58:00 2019
Return-Path: <gcc-bugs-return-628526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108049 invoked by alias); 9 Jan 2019 14:57: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 107942 invoked by uid 48); 9 Jan 2019 14:57:54 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84010] problematic TLS code generation on 64-bit SPARC
Date: Wed, 09 Jan 2019 14:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: jrtc27 at jrtc27 dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84010-4-BRNDp88Jbm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01335.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84010
--- Comment #20 from James Clarke <jrtc27 at jrtc27 dot com> ---
(In reply to Eric Botcazou from comment #19)
> > Ah, great, thanks, that's indeed a nicer way of writing the patterns.
>
> You're welcome. Don't hesitate to ping next time I drop the ball for so
> long.
I had forgotten myself that a fix was never committed, probably because I
remembered writing the patch, otherwise I would have pinged it long ago!
>From gcc-bugs-return-628528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:59:04 2019
Return-Path: <gcc-bugs-return-628528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109396 invoked by alias); 9 Jan 2019 14:59:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109180 invoked by uid 48); 9 Jan 2019 14:58:59 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/80042] gcc thinks sin/cos don't set errno
Date: Wed, 09 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: easyhack
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-80042-4-D2RyRk3BOg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80042-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80042-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01337.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80042
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |per at pz dot se
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
*** Bug 88769 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-628527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 14:59:03 2019
Return-Path: <gcc-bugs-return-628527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109273 invoked by alias); 9 Jan 2019 14:59:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109141 invoked by uid 48); 9 Jan 2019 14:58:59 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88769] Call to sin() optimized away, disregarding possible side-effect (errno)
Date: Wed, 09 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-88769-4-CJZBnzpYSN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01336.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88769
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
dup of bug 80042
*** This bug has been marked as a duplicate of bug 80042 ***
>From gcc-bugs-return-628529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 15:07:06 2019
Return-Path: <gcc-bugs-return-628529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30458 invoked by alias); 9 Jan 2019 15:07:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30341 invoked by uid 48); 9 Jan 2019 15:06:57 -0000
From: "gary_mills at fastmail dot fm" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Wed, 09 Jan 2019 15:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary_mills at fastmail dot fm
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-XaaQkMQmkV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01338.txt.bz2
Content-length: 1362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #30 from Gary Mills <gary_mills at fastmail dot fm> ---
A build of gcc-7 on SPARC just completed successfully with a much larger
configuration:
$
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/gcc-7.3.0/configure
CC=/usr/gcc/4.9/bin/gcc CXX=/usr/gcc/4.9/bin/g++
F77=/usr/gcc/4.9/bin/gfortran FC=/usr/gcc/4.9/bin/gfortran CFLAGS=-O2
-mno-app-regs LDFLAGS=-m32 PKG_CONFIG_PATH=/usr/lib/pkgconfig
--prefix=/usr/gcc/7 --mandir=/usr/gcc/7/share/man
--bindir=/usr/gcc/7/bin --sbindir=/usr/gcc/7/bin
--libdir=/usr/gcc/7/lib --libexecdir=/usr/gcc/7/lib
--with-pkgversion=OpenIndiana 7.3.0-OI-0
--with-bugurl=https://bugs.openindiana.org --enable-languages=c,c++
--without-gnu-ld --with-ld=/usr/bin/ld --without-gnu-as
--with-as=/usr/bin/as LDFLAGS=-R/usr/gcc/7/lib
There still was no ICE. I'm going to try an even larger configuration next in
an attempt to identify which configuration setting causes the ICE. I'm
suspicious of these three:
CONFIGURE_OPTIONS+= --host $(GNU_ARCH)
CONFIGURE_OPTIONS+= --build $(GNU_ARCH)
CONFIGURE_OPTIONS+= --target $(GNU_ARCH)
which are part of the OI Makefile. Note the missing equal signs (=). I only
noticed these a few days ago. I'll include these at the very end of my
testing.
>From gcc-bugs-return-628530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 15:26:57 2019
Return-Path: <gcc-bugs-return-628530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94304 invoked by alias); 9 Jan 2019 15:26:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94215 invoked by uid 48); 9 Jan 2019 15:26:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Wed, 09 Jan 2019 15:26: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: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-TSLIm1b1lN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01339.txt.bz2
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Though, the more I look at it, the more I'm for reversion of the patch + deal
with it in the assign_stack_local caller that needs that.
>From gcc-bugs-return-628531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 15:28:18 2019
Return-Path: <gcc-bugs-return-628531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123046 invoked by alias); 9 Jan 2019 15:28: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 121084 invoked by uid 48); 9 Jan 2019 15:28:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Wed, 09 Jan 2019 15:28: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: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88450-4-JzpoBdsjQs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01340.txt.bz2
Content-length: 271
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45391
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45391&action=edit
gcc9-pr88450.patch
Untested patch that does that.
>From gcc-bugs-return-628532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 15:34:12 2019
Return-Path: <gcc-bugs-return-628532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16435 invoked by alias); 9 Jan 2019 15:34:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16334 invoked by uid 48); 9 Jan 2019 15:34:07 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86979] [9 Regression] ICE: in maybe_record_trace_start, at dwarf2cfi.c:2348 with -m32 on darwin
Date: Wed, 09 Jan 2019 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: abel at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86979-4-vDedYWbyTn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86979-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86979-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01341.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86979
--- Comment #10 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
As discussed with Andrew offline, the real problem is creating a path where
stack pointer is decremented twice - that is really not supposed to happen (so
the issue could appear even in absence of REG_ARGS_SIZE notes). We'll be having
another look to find the root cause.
>From gcc-bugs-return-628533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 15:34:33 2019
Return-Path: <gcc-bugs-return-628533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17264 invoked by alias); 9 Jan 2019 15:34: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 17203 invoked by uid 48); 9 Jan 2019 15:34:29 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] Exception handling configured mode does not match the one finally used
Date: Wed, 09 Jan 2019 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88772-4-585ai2yFW8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01342.txt.bz2
Content-length: 765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-09
CC| |ebotcazou at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
What's the result of the configure check of libgcc for SJLJ? It should be
visible in the config.log file in the libgcc build directory:
whether the compiler is configured for setjmp/longjmp exceptions...
>From gcc-bugs-return-628534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 16:06:05 2019
Return-Path: <gcc-bugs-return-628534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58143 invoked by alias); 9 Jan 2019 16:06: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 57972 invoked by uid 48); 9 Jan 2019 16:06:00 -0000
From: "nickc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88539] A memory leak issue was discovered in cplus-dem.c
Date: Wed, 09 Jan 2019 16:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nickc at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-88539-4-ZcVQlLOHoD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88539-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88539-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01343.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88539
Nick Clifton <nickc at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |nickc at gcc dot gnu.org
Resolution|--- |WONTFIX
--- Comment #3 from Nick Clifton <nickc at gcc dot gnu.org> ---
Sorry, but a leak of 10 bytes is just not serious enough to be worth
worrying about. Especially when these programs do not run continuously
but instead terminate shortly after they are invoked.
>From gcc-bugs-return-628535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 16:07:42 2019
Return-Path: <gcc-bugs-return-628535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70847 invoked by alias); 9 Jan 2019 16:07:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70777 invoked by uid 48); 9 Jan 2019 16:07:36 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-sdBQSuXLnh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01344.txt.bz2
Content-length: 767
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning is triggered by the excessive size argument in the strncpy call.
The excessive size makes the call invalid regardless of the values of the two
pointer arguments.
This happens both with the reduced test case in comment #0 and with the
translation unit and -m32. The warning code just looks at the call:
__builtin_strncpy (_65, buf_30, 4294967295);
I don't see much the warning code alone can do to handle this case. We have
talked about at least two approaches to dealing these invalid calls earlier.
Jeff's preference is to replace them with traps. Others have suggested
replacing them with __builtin_unreachable().
>From gcc-bugs-return-628536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 16:08:01 2019
Return-Path: <gcc-bugs-return-628536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71729 invoked by alias); 9 Jan 2019 16:08: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 71622 invoked by uid 48); 9 Jan 2019 16:07:56 -0000
From: "wjwray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88572] error: braces around scalar initializer - should be a warning
Date: Wed, 09 Jan 2019 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wjwray 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-88572-4-mge4WyVkt6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88572-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01345.txt.bz2
Content-length: 864
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88572
--- Comment #13 from Will Wray <wjwray at gmail dot com> ---
Re-reviewing, I notice that the patch I posted in comment #9
now rejects nested empty-brace scalar init:
int i{{}};
which was previously accepted. So we'll need a decision on this too.
Clang rejects with -pedantic-errors or warns otherwise:
pedantic error / warning: too many braces around scalar initializer
MSVC rejects:
error: 'initializing': cannot convert from 'initializer list' to 'int'
note: Too many braces around initializer for 'int'
I reckon that Clang is right to reject under -pedantic, else accept and warn
This Quora post comes to a similar conclusion:
https://www.quora.com/Is-double-braced-scalar-initialization-allowed-by-the-C-standard-int-x
>accepting {{}} for int seems like a harmless language extension.
>From gcc-bugs-return-628537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 16:12:02 2019
Return-Path: <gcc-bugs-return-628537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86624 invoked by alias); 9 Jan 2019 16:12:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86554 invoked by uid 48); 9 Jan 2019 16:11:57 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Wed, 09 Jan 2019 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-KELJCPI8D4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01346.txt.bz2
Content-length: 354
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
That said, the size range in the warning output is wrong. It should be just
4294967295. The warning should probably also be changed to -Wstringop-overflow
which diagnoses both out-of-bounds writes and reads. I can look into that.
>From gcc-bugs-return-628538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 16:58:47 2019
Return-Path: <gcc-bugs-return-628538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7527 invoked by alias); 9 Jan 2019 16:58:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7418 invoked by uid 48); 9 Jan 2019 16:58:41 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Wed, 09 Jan 2019 16:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-TJbfGOGvWK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01347.txt.bz2
Content-length: 901
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Marius Messerschmidt from comment #3)
> Sorry but I do not fully understand what you mean. Do you suggest using
> different command line arguments?
I believe Richard is referring to the internal API used for dumping; right now
it's presumably just writing to a FILE *, and this doesn't show up for
-fopt-info*.
> So far I tried:
>
> -fdump-tree-all
> -fdump-tree-unswitch
>
> and
>
> -fopt-info-all-optall
>
> But none of them told me the all the things that I would wish to know, most
> important the reason why a particular loop was skipped during unswitching
> (e.g. because it is not invariant or so (right now it already reports a few
> things with -fdump-tree-unswitch like too-many-instructions or
> too-many-branches))
Am taking a look.
>From gcc-bugs-return-628539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 16:59:01 2019
Return-Path: <gcc-bugs-return-628539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8291 invoked by alias); 9 Jan 2019 16:59: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 8204 invoked by uid 55); 9 Jan 2019 16:58:57 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88766-4-fmRZO6gm6v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01348.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
--- Comment #2 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Yes, I think that (a) a statement expression is not an lvalue and (b) if
it were (or if the code were changed to move the unary '&' inside the
statement expression), the code would be taking the address of an object
whose lifetime had ended by the time that address is used.
>From gcc-bugs-return-628540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:01:17 2019
Return-Path: <gcc-bugs-return-628540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11369 invoked by alias); 9 Jan 2019 17:01: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 11227 invoked by uid 48); 9 Jan 2019 17:01:07 -0000
From: "ylatuya at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] Exception handling configured mode does not match the one finally used
Date: Wed, 09 Jan 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ylatuya 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-88772-4-rxUPJ4eRAi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01349.txt.bz2
Content-length: 507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
--- Comment #2 from Andoni <ylatuya at gmail dot com> ---
(In reply to Eric Botcazou from comment #1)
> What's the result of the configure check of libgcc for SJLJ? It should be
> visible in the config.log file in the libgcc build directory:
>
> whether the compiler is configured for setjmp/longjmp exceptions...
I just wiped the build to start a clean build from scratch, but I remember
checking this and it was "no". I can confirm it in ~1 hour
>From gcc-bugs-return-628541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:02:08 2019
Return-Path: <gcc-bugs-return-628541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38083 invoked by alias); 9 Jan 2019 17:02:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30633 invoked by uid 55); 9 Jan 2019 17:02:02 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88769] Call to sin() optimized away, disregarding possible side-effect (errno)
Date: Wed, 09 Jan 2019 17:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery 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:
Message-ID: <bug-88769-4-9qmIeI8pdP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01350.txt.bz2
Content-length: 615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88769
--- Comment #4 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Errors for infinite arguments to math.h functions are generally documented
in Annex F; 7.12.1 just says "an implementation may define additional
domain errors, provided that such errors are consistent with the
mathematical definition of the function" with a footnote "In an
implementation that supports infinities, this allows an infinity as an
argument to be a domain error if the mathematical domain of the function
does not include the infinity.".
>From gcc-bugs-return-628542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:12:18 2019
Return-Path: <gcc-bugs-return-628542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6775 invoked by alias); 9 Jan 2019 17:12:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6694 invoked by uid 48); 9 Jan 2019 17:12:13 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 17:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-LRZbElBF4O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01351.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #34 from Wilco <wilco at gcc dot gnu.org> ---
With just the expr.c patch the gcc regression tests all pass on big-endian
AArch64. Interestingly this includes the new torture test, ie. it does not
trigger the union bug.
>From gcc-bugs-return-628543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:17:58 2019
Return-Path: <gcc-bugs-return-628543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112528 invoked by alias); 9 Jan 2019 17:17: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 105397 invoked by uid 48); 9 Jan 2019 17:17:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 17:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88766-4-5UWSV4icfg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01352.txt.bz2
Content-length: 2160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
gpg2 needs to be fixed then.
Looking at the source, they wrap the complit in:
#define DNS_PRAGMA_PUSH _Pragma("GCC diagnostic push")
#define DNS_PRAGMA_QUIET _Pragma("GCC diagnostic ignored \"-Woverride-init\"")
#define DNS_PRAGMA_POP _Pragma("GCC diagnostic pop")
/* GCC parses the _Pragma operator less elegantly than clang. */
#define dns_quietinit(...) \
__extension__ ({ DNS_PRAGMA_PUSH DNS_PRAGMA_QUIET __VA_ARGS__;
DNS_PRAGMA_POP })
while for clang they use
#define dns_quietinit(...) \
DNS_PRAGMA_PUSH DNS_PRAGMA_QUIET __VA_ARGS__ DNS_PRAGMA_POP
Trying:
#define DNS_PRAGMA_PUSH _Pragma("GCC diagnostic push")
#define DNS_PRAGMA_QUIET _Pragma("GCC diagnostic ignored \"-Woverride-init\"")
#define DNS_PRAGMA_POP _Pragma("GCC diagnostic pop")
#define dns_quietinit(...) \
DNS_PRAGMA_PUSH DNS_PRAGMA_QUIET __VA_ARGS__ DNS_PRAGMA_POP
struct S { int a, b; };
void
foo (void)
{
void *p = &(struct S) { .a = 0, .b = 1, .a = 0 };
void *q = &dns_quietinit ((struct S) { .a = 0, .b = 1, .a = 0 });
}
indeed fails to parse:
/tmp/h.c: In function ‘foo’:
/tmp/h.c:13:48: warning: initialized field overwritten [-Woverride-init]
void *p = &(struct S) { .a = 0, .b = 1, .a = 0 };
^
/tmp/h.c:13:48: note: (near initialization for ‘(anonymous).a’)
/tmp/h.c:14:1: error: expected expression before ‘#pragma’
void *q = &dns_quietinit ((struct S) { .a = 0, .b = 1, .a = 0 });
^ ~
(the line 13 warnings are expected and line 14 is their attempt to disable the
warning. We don't really support pragmas in the middle of expressions, but a
compound literal can't be used here.
>From gcc-bugs-return-628544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:25:59 2019
Return-Path: <gcc-bugs-return-628544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43859 invoked by alias); 9 Jan 2019 17:25:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43757 invoked by uid 48); 9 Jan 2019 17:25:54 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 17:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88766-4-OyLN5sWpSs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01353.txt.bz2
Content-length: 1057
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
I don't disagree with the conclusion about the validity of this test case but
there are examples where GCC does treat a statement expression as an lvalue,
such as in the following:
void f (void)
{
int i = 0;
++__extension__({ (int)i; }); // accepted
if (i != 1) // folded to false
__builtin_abort ();
}
Accepting this seems like a bug irrespective of whether statement expressions
themselves are ever lvalues.
GCC of course also accepts ++({ i; }). Joseph's comment #2 suggests this
should be invalid as well but I might be reading too much into it. In any
case, it would be helpful to make this clear in the manual.
>From gcc-bugs-return-628545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:27:35 2019
Return-Path: <gcc-bugs-return-628545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52627 invoked by alias); 9 Jan 2019 17:27: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 52555 invoked by uid 48); 9 Jan 2019 17:27:30 -0000
From: "noloader at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/78782] [x86] _mm_loadu_si64 intrinsic missing
Date: Wed, 09 Jan 2019 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: noloader at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78782-4-k1dgrD8TDV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01354.txt.bz2
Content-length: 320
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78782
--- Comment #1 from Jeffrey Walton <noloader at gmail dot com> ---
Also documented in the Intel Intrinsics Guide at
https://software.intel.com/sites/landingpage/IntrinsicsGuide/#text=_mm_loadu_si64.
According to the guide, the intrinsic is the movq instruction.
>From gcc-bugs-return-628546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:32:50 2019
Return-Path: <gcc-bugs-return-628546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62679 invoked by alias); 9 Jan 2019 17:32:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62602 invoked by uid 55); 9 Jan 2019 17:32:45 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 17:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88766-4-Y7x4xWX9L0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01355.txt.bz2
Content-length: 1145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
--- Comment #5 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 9 Jan 2019, msebor at gcc dot gnu.org wrote:
> I don't disagree with the conclusion about the validity of this test case but
> there are examples where GCC does treat a statement expression as an lvalue,
> such as in the following:
>
> void f (void)
> {
> int i = 0;
> ++__extension__({ (int)i; }); // accepted
> if (i != 1) // folded to false
> __builtin_abort ();
> }
>
> Accepting this seems like a bug irrespective of whether statement expressions
> themselves are ever lvalues.
Indeed. Casts as lvalues were removed a very long time ago.
> GCC of course also accepts ++({ i; }). Joseph's comment #2 suggests this
> should be invalid as well but I might be reading too much into it. In any
> case, it would be helpful to make this clear in the manual.
I think ++({ i; }) should be invalid. (If i is an _Atomic int, it's
already rejected because of the special lvalue-to-rvalue processing
applied for atomics.)
>From gcc-bugs-return-628547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:33:22 2019
Return-Path: <gcc-bugs-return-628547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63664 invoked by alias); 9 Jan 2019 17:33: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 63581 invoked by uid 48); 9 Jan 2019 17:33:12 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 17:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88739-4-mWAwNs66W6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01356.txt.bz2
Content-length: 1766
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
--- Comment #35 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Yeah, the expr.c patch makes the original testcase work, but we still fail for:
#include<stdio.h>
typedef unsigned int U32;
typedef unsigned short U16;
typedef unsigned char U8;
typedef struct MEM_HEAD_4DW
{
/* first word */
U32 b11 : 1;
U32 b12 : 3;
U32 b13 : 3;
U32 b14 : 1;
U32 b15 : 16;
U32 b16 : 8;
/* second word */
U32 b21 : 16;
U32 b22 : 1;
U32 b23 : 4;
U32 b24 : 11;
/* third word */
U32 b31 : 32;
/* fourth word */
U32 b30AddrL : 30;
U32 b2AddrType : 2;
}MEM_REQ_HEAD_4DW;
typedef union HEAD_DW4_UNION
{
MEM_REQ_HEAD_4DW strMemHead;
U32 aulValue[4];
U16 ausValue[8];
U8 aucValue[16];
}HEAD_REQ_DW4_UNION;
U32 Test_func(U32 ulAddr)
{
HEAD_REQ_DW4_UNION unData;
unData.strMemHead.b30AddrL = ulAddr >> 2;
unData.strMemHead.b2AddrType = 0;
printf("unData.ausValue[6]=0x%x\r\n",unData.ausValue[6]); // why get
0x0 instead of 0x1 ?
return 0;
}
int main()
{
Test_func(0x10224);
return 0;
}
Like Wilco says, the torture test seems to pass with an unpatched compiler (but
seems like a good thing to have anyway).
>From gcc-bugs-return-628548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:46:36 2019
Return-Path: <gcc-bugs-return-628548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73988 invoked by alias); 9 Jan 2019 17:46: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 73881 invoked by uid 48); 9 Jan 2019 17:46:31 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 17:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-2NYDGuCb3t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01357.txt.bz2
Content-length: 295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #36 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Like Wilco says, the torture test seems to pass with an unpatched compiler
> (but seems like a good thing to have anyway).
Likewise on SPARC at any optimization level.
>From gcc-bugs-return-628549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 17:58:45 2019
Return-Path: <gcc-bugs-return-628549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108053 invoked by alias); 9 Jan 2019 17:58: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 107943 invoked by uid 48); 9 Jan 2019 17:58:37 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88576] -fno-math-errno causes GCC to consider that malloc does not set errno
Date: Wed, 09 Jan 2019 17:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88576-4-mFhZHHN3GG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01358.txt.bz2
Content-length: 1414
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88576
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #11)
> (In reply to Florian Weimer from comment #6)
> > Has this got to do anything with errno? It seems to me that with
> > -fno-math-errno, GCC assumes that malloc does not set *any* TLS variable.
> > That doesn't look right to me.
>
> GCC assumes that memory allocation does not affect global heap state.
> That's correct unless you compile the memory allocator itself.
>
> Note the original "alias" with -fno-math-errno was probably too lazy but
> allocations being a barrier for any load/store of global memory is quite
> bad for optimization in _fortran_ (which has no business with errno)
> where we (unfortunately) also get everything passed by reference.
>
> I'll introduce -f[no-]alloc-errno, defaulted to the -f[no-]math-errno
> state and enabled at -Ofast (but not with -ffast-math).
Darwin has -fno-math-errno set by default, but its malloc can set errno (to
ENOMEM), so it wouldn't make sense to have -fno-alloc-errno set by
-fno-math-errno on Darwin
>From gcc-bugs-return-628550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:02:44 2019
Return-Path: <gcc-bugs-return-628550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1213 invoked by alias); 9 Jan 2019 18:02: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 1138 invoked by uid 48); 9 Jan 2019 18:02:37 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88773] New: statement expression returning a cast treated as an lvalue
Date: Wed, 09 Jan 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
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-88773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01359.txt.bz2
Content-length: 1386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88773
Bug ID: 88773
Summary: statement expression returning a cast treated as an
lvalue
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
As discussed in bug 88766 comment #4, GCC treats some statement expressions as
lvalues even though their last statement is an rvalue. As noted in the rest of
the discussion a statement expression should evaluate to an rvalue even if it's
last statement is an lvalue.
Besides adjusting GCC to reflect that the manual should be updated to explain
this.
$ cat u.c && gcc -O2 -S -Wall -Wextra -Wpedantic
-fdump-tree-optimized=/dev/stdout u.c
void f (void)
{
int i = 0;
++__extension__ ({ (int)i; }); // accepted (bug)
if (i != 1) // folded to false
__builtin_abort ();
}
int* g (void)
{
int i = 0;
int *p = &++__extension__ ({ (int)i; }); // rejected (good)
return p;
}
u.c: In function ‘g’:
u.c:12:12: error: lvalue required as unary ‘&’ operand
12 | int *p = &++__extension__ ({ (int)i; }); // rejected (good)
| ^
>From gcc-bugs-return-628551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:04:01 2019
Return-Path: <gcc-bugs-return-628551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5381 invoked by alias); 9 Jan 2019 18: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 5190 invoked by uid 48); 9 Jan 2019 18:03:57 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 18:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-88766-4-bZLQKUkLxB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01360.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=88773
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
Okay, I've raised pr88773 for these problems.
>From gcc-bugs-return-628552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:06:43 2019
Return-Path: <gcc-bugs-return-628552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12809 invoked by alias); 9 Jan 2019 18:06:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12720 invoked by uid 48); 9 Jan 2019 18:06:38 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 18:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-2PotjfZYG9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01361.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #37 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to rsandifo@gcc.gnu.org from comment #35)
> Yeah, the expr.c patch makes the original testcase work, but we still fail
> for:
That's the folding in ccp1 after inlining, which will require a similar fix.
There are likely more places that need to be fixed to handle the 'short' bit
types.
>From gcc-bugs-return-628553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:11:01 2019
Return-Path: <gcc-bugs-return-628553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17674 invoked by alias); 9 Jan 2019 18:11: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 17580 invoked by uid 48); 9 Jan 2019 18:10:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 18:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88766-4-roOIuw4wjT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01362.txt.bz2
Content-length: 950
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As for the GCC diagnostic pragma, we need it to be a deferred pragma, have no
idea how else could we handle that when it is not visible in the token stream.
And, if it is visible in the token stream, accepting it everywhere in the
exceptions would be quite hard too, e.g. the C FE normally has only 2 tokens
lookahead, or how would it play in C++ FE with the tentative parsing?
What we could do is accept #pragma GCC diagnostic (and only that?) inside of
the braced initializers (so c_parser_braced_init for C and
cp_parser_braced_list? for C++), before each init elt and after those, perhaps
rejecting it if it appears before a comma. Of course, for gnupg2 they would
need to adjust their macros slightly, because the would need to go inside of
the compound literal braced init rather than around it.
Thoughts on that?
>From gcc-bugs-return-628554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:20:28 2019
Return-Path: <gcc-bugs-return-628554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114635 invoked by alias); 9 Jan 2019 18:20: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 108486 invoked by uid 48); 9 Jan 2019 18:20:22 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88766] [9 Regression] Rejects valid? C code since r259641
Date: Wed, 09 Jan 2019 18:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88766-4-klUqGbHU2d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88766-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01363.txt.bz2
Content-length: 1949
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88766
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
A C proof of concept:
--- gcc/c/c-parser.c.jj 2019-01-07 09:47:33.187515618 +0100
+++ gcc/c/c-parser.c 2019-01-09 19:15:05.216756760 +0100
@@ -4624,6 +4624,11 @@ c_parser_braced_init (c_parser *parser,
}
else
really_start_incremental_init (type);
+
+ /* Accept #pragmas at braced init scope. */
+ while (c_parser_next_token_is (parser, CPP_PRAGMA))
+ c_parser_pragma (parser, pragma_struct, NULL);
+
if (c_parser_next_token_is (parser, CPP_CLOSE_BRACE))
{
pedwarn (brace_loc, OPT_Wpedantic, "ISO C forbids empty initializer
braces");
@@ -4634,6 +4639,10 @@ c_parser_braced_init (c_parser *parser,
comma. */
while (true)
{
+ /* Accept #pragmas at braced init scope. */
+ while (c_parser_next_token_is (parser, CPP_PRAGMA))
+ c_parser_pragma (parser, pragma_struct, NULL);
+
c_parser_initelt (parser, &braced_init_obstack);
if (parser->error)
break;
@@ -4644,10 +4653,20 @@ c_parser_braced_init (c_parser *parser,
}
else
break;
+
+ /* Accept #pragmas at braced init scope. */
+ while (c_parser_next_token_is (parser, CPP_PRAGMA))
+ c_parser_pragma (parser, pragma_struct, NULL);
+
if (c_parser_next_token_is (parser, CPP_CLOSE_BRACE))
break;
}
}
+
+ /* Accept #pragmas at braced init scope. */
+ while (c_parser_next_token_is (parser, CPP_PRAGMA))
+ c_parser_pragma (parser, pragma_struct, NULL);
+
c_token *next_tok = c_parser_peek_token (parser);
if (next_tok->type != CPP_CLOSE_BRACE)
{
Of course, this one parses all pragmas, rather than just GCC diagnostic, and
for most pragmas handling them in this context is undesirable (either
meaningful, or e.g. OpenMP/OpenACC forbids them there).
>From gcc-bugs-return-628555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:29:07 2019
Return-Path: <gcc-bugs-return-628555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53703 invoked by alias); 9 Jan 2019 18:29:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53637 invoked by uid 48); 9 Jan 2019 18:29:02 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88765] powerpc64le-linux-gnu sub-optimal code generation for builtin atomic ops
Date: Wed, 09 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88765-4-HcP9oA4DmA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01364.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88765
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
So in the first example, why is the branch not forwarded already?
>From gcc-bugs-return-628556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:31:14 2019
Return-Path: <gcc-bugs-return-628556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53035 invoked by alias); 9 Jan 2019 18:31: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 23241 invoked by uid 48); 9 Jan 2019 18:30:49 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88727] Diagnostics improvement: Detection of undefined behaviour. Incomplete type in tenative definition with internal linkage. [-Wtentative-definition-incomplete-type]
Date: Wed, 09 Jan 2019 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc see_also blocked short_desc everconfirmed
Message-ID: <bug-88727-4-CY9ZpooHg3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01365.txt.bz2
Content-length: 3206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88727
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=26581
Blocks| |87403
Summary|Diagnostics improvement: |Diagnostics improvement:
|Detection of undefined |Detection of undefined
|behaviour. Incomplete type |behaviour. Incomplete type
|in tenative definition with |in tenative definition with
|internal linkage. |internal linkage.
| |[-Wtentative-definition-inc
| |omplete-type]
Ever confirmed|0 |1
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Anders Granlund from comment #0)
> Test case (prog.c):
>
> static struct S s;
>
> int main()
> {
> }
>
> struct S { int x; };
>
> Compilation command line:
>
> gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
>
> Observed behaviour:
>
> No error messages outputes.
No errors, sure, but I do get a warning from -Wunused-variable:
$ gcc -c -Wall -Wextra -std=c11 -pedantic-errors 88727.c
88727.c:1:17: warning: 's' defined but not used [-Wunused-variable]
static struct S s;
^
$
>
> Possible improvement of behaviour:
>
> Outputing an error message about using an incomplete type in the tenative
> definition static struct S s; .
>
> The program has undefined behaviour becuase of a violation of 6.9.2/2:
>
> "If the declaration of an identifier for an object is a tentative
> definition
> and has internal linkage, the declared type shall not be an incomplete
> type."
>
> GCC detects such undefined behaviour in other cases (for example using the
> incomplete type int []). It would be good if it could also hande the case
> in
> the test case for this bug report.
>
> Note:
>
> Clang detects the undefined behaviour for this program and outputs an error
> message.
Confirmed that clang errors, its output is:
$ clang -c -Wall -Wextra -std=c11 -pedantic-errors 88727.c
88727.c:1:17: error: tentative definition of variable with internal linkage has
incomplete non-array type 'struct S'
[-Werror,-Wtentative-definition-incomplete-type]
static struct S s;
^
88727.c:1:15: note: forward declaration of 'struct S'
static struct S s;
^
1 error generated.
$
Since it's a warning-turned-into-an-error I'm making this block the new-warning
bug.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87403
[Bug 87403] [Meta-bug] Issues that suggest a new warning
>From gcc-bugs-return-628557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:33:50 2019
Return-Path: <gcc-bugs-return-628557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69661 invoked by alias); 9 Jan 2019 18:33:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69576 invoked by uid 48); 9 Jan 2019 18:33:44 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88765] powerpc64le-linux-gnu sub-optimal code generation for builtin atomic ops
Date: Wed, 09 Jan 2019 18:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88765-4-IxIdzB6k6a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01366.txt.bz2
Content-length: 161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88765
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
What exact options are needed here?
>From gcc-bugs-return-628558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:37:36 2019
Return-Path: <gcc-bugs-return-628558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72457 invoked by alias); 9 Jan 2019 18:37:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72373 invoked by uid 48); 9 Jan 2019 18:37:31 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88765] powerpc64le-linux-gnu sub-optimal code generation for builtin atomic ops
Date: Wed, 09 Jan 2019 18:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88765-4-CgutBkAXQ7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01367.txt.bz2
Content-length: 663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88765
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|powerpc64le-linux-gnu |powerpc*-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
Ever confirmed|0 |1
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Ah. I can reproduce this (the first testcase) on trunk only with -Og, but on 8
this happens with -O2, too. Confirmed.
>From gcc-bugs-return-628559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:47:44 2019
Return-Path: <gcc-bugs-return-628559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86213 invoked by alias); 9 Jan 2019 18:47:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86127 invoked by uid 48); 9 Jan 2019 18:47:38 -0000
From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Wed, 09 Jan 2019 18:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mikpelinux at gmail dot com
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-isdUKwZyAO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01368.txt.bz2
Content-length: 2986
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #5 from Mikael Pettersson <mikpelinux at gmail dot com> ---
With -da -fdump-tree-all, stage1 and stage2 output starts to differ in
043t.profile_estimate and then more visibly in 130t.pre:
diff -ru stage1/sort.i.043t.profile_estimate
stage2/sort.i.043t.profile_estimate
--- stage1/sort.i.043t.profile_estimate 2019-01-09 19:39:25.973607372 +0100
+++ stage2/sort.i.043t.profile_estimate 2019-01-09 19:39:40.893537693 +0100
@@ -252,5 +252,5 @@
-;; Combiner totals: 55 attempts, 49 substitutions (22 requiring new space),
+;; Combiner totals: 56 attempts, 49 substitutions (21 requiring new space),
;; 4 successes.
diff -ru stage1/sort.i.130t.pre stage2/sort.i.130t.pre
--- stage1/sort.i.130t.pre 2019-01-09 19:39:24.673613443 +0100
+++ stage2/sort.i.130t.pre 2019-01-09 19:39:39.993541897 +0100
@@ -226,13 +226,12 @@
size_t j;
size_t i;
unsigned int count[256];
- unsigned int prephitmp_1;
- unsigned int pretmp_2;
unsigned int _5;
unsigned char _6;
int _7;
unsigned int _8;
unsigned int _9;
+ unsigned int _11;
unsigned int _12;
sizetype _13;
sizetype _14;
@@ -244,13 +243,11 @@
unsigned int _20;
void * * _21;
void * _22;
- unsigned int prephitmp_36;
unsigned int _53;
- unsigned int pretmp_58;
- unsigned int pretmp_84;
- unsigned int prephitmp_85;
- unsigned int pretmp_86;
- unsigned int prephitmp_87;
+ unsigned int prephitmp_71;
+ unsigned int pretmp_72;
+ unsigned int prephitmp_76;
+ unsigned int pretmp_77;
<bb 2> [local count: 2684354]:
_5 = n_41(D) * 4;
@@ -284,18 +281,16 @@
goto <bb 5>; [11.00%]
<bb 5> [local count: 9556302]:
- pretmp_58 = MEM[(unsigned int *)&count + 4B];
- pretmp_2 = MEM[(unsigned int *)&count];
+ pretmp_77 = MEM[(unsigned int *)&count + 4B];
<bb 6> [local count: 10737418]:
- # prephitmp_1 = PHI <pretmp_58(5), 0(3)>
- # prephitmp_36 = PHI <pretmp_2(5), 0(3)>
+ # prephitmp_76 = PHI <pretmp_77(5), 0(3)>
<bb 7> [local count: 1063004406]:
# countp_30 = PHI <&MEM[(void *)&count + 4B](6), countp_46(8)>
- # prephitmp_85 = PHI <prephitmp_1(6), pretmp_84(8)>
- # prephitmp_87 = PHI <prephitmp_36(6), pretmp_86(8)>
- _12 = prephitmp_85 + prephitmp_87;
+ # prephitmp_71 = PHI <prephitmp_76(6), pretmp_72(8)>
+ _11 = MEM[(unsigned int *)countp_30 + 4294967292B];
+ _12 = _11 + prephitmp_71;
*countp_30 = _12;
countp_46 = countp_30 + 4;
if (&MEM[(void *)&count + 1024B] > countp_46)
@@ -304,8 +299,7 @@
goto <bb 9>; [1.01%]
<bb 8> [local count: 1052266993]:
- pretmp_84 = MEM[(unsigned int *)countp_30 + 4B];
- pretmp_86 = *countp_30;
+ pretmp_72 = MEM[(unsigned int *)countp_30 + 4B];
goto <bb 7>; [100.00%]
<bb 9> [local count: 10737418]:
Subsequent dump files also differ, but seem to mirror the above diffs.
Meanwhile I did a bootstrap without specifying --enable-checking=release, and
that one succeeded.
>From gcc-bugs-return-628560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 18:58:41 2019
Return-Path: <gcc-bugs-return-628560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106565 invoked by alias); 9 Jan 2019 18:58: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 106483 invoked by uid 48); 9 Jan 2019 18:58:36 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Wed, 09 Jan 2019 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88739-4-P07Gm0Tf7H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01369.txt.bz2
Content-length: 1260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #38 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Created attachment 45392
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45392&action=edit
patch that changes get_ref_base_and_extent for bare SSA_NAMEs
(In reply to Wilco from comment #37)
> (In reply to rsandifo@gcc.gnu.org from comment #35)
> > Yeah, the expr.c patch makes the original testcase work, but we still fail
> > for:
>
> That's the folding in ccp1 after inlining, which will require a similar fix.
> There are likely more places that need to be fixed to handle the 'short' bit
> types.
Yeah, seems like a can of worms.
The expr.c approach treats a reference to an N-bit integer in an
M>N-bit mode is relative to M rather than N (i.e. it's relative
to the addressable storage.) So maybe the point this goes wrong
is when we ask for get_ref_base_and_extent on a bare 30-bit SSA_NAME
(no component accesses) and get back an offset of 0. If everything's
relative to the addressable storage then maybe it should be 2 for
big-endian?
The attached patch does that and seems to pass all three tests
in the PR so far. I'll give a spin overnight just in case
it's at least vaguely sensible.
>From gcc-bugs-return-628561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 19:05:26 2019
Return-Path: <gcc-bugs-return-628561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5444 invoked by alias); 9 Jan 2019 19:05:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5428 invoked by uid 89); 9 Jan 2019 19:05:24 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=0.8 required=5.0 testsºYES_50,FILL_THIS_FORM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,T_FILL_THIS_FORM_LONG,UNPARSEABLE_RELAY autolearn=ham version=3.3.2 spammy=helen, Website, Helen, Kindly
X-HELO: mail-yb1-f172.google.com
Received: from mail-yb1-f172.google.com (HELO mail-yb1-f172.google.com) (209.85.219.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 09 Jan 2019 19:05:23 +0000
Received: by mail-yb1-f172.google.com with SMTP id n16so3405149ybg.13 for <gcc-bugs@gcc.gnu.org>; Wed, 09 Jan 2019 11:05:23 -0800 (PST)
Received: from 512512912211 named unknown by gmailapi.google.com with HTTPREST; Wed, 9 Jan 2019 11:05:20 -0800
MIME-Version: 1.0
Sender: helen.aldred@swcenters.com
From: helen.aldred@swcenters.com
Date: Wed, 09 Jan 2019 19:05:00 -0000
Message-ID: <CAOERRMo_UUH-xER75qUBZd_ot6csCFBVhjuLursRnn1kAwbrMg@mail.gmail.com>
Subject: Global accounts of QAD and SAP Users
To: gcc-bugs@gcc.gnu.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2019-01/txt/msg01370.txt.bz2
Content-length: 568
Hi,
How about targeting customer base of QAD and SAP Users for your Marketing
and sales needs? Please let me know.
This file includes– Company name, Website, Contact name (First, Middle,
Last), Title, Direct email address, Phone, Postal address, Industry, SIC
codes, Employee size, Revenue size and technology/application details.
Kindly review and let me know if we can connect and discuss further.
Await your response!
Warm regards,
Helen Adlred
LeadGen Manager
No interest? Kindly reply “no†in the subject line
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-01-01 1:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-88646-4@http.gcc.gnu.org/bugzilla/>
2019-01-01 1:09 ` [Bug c++/88646] Optimizer failure on integer sum overflow cast to bool pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).