public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/90227] [9 Regression] trunk rejects polymake since r269965
[not found] <bug-90227-4@http.gcc.gnu.org/bugzilla/>
@ 2019-04-24 20:38 ` jason at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: jason at gcc dot gnu.org @ 2019-04-24 20:38 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: 575457 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90227
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Wed Apr 24 20:37:30 2019
New Revision: 270556
URL: https://gcc.gnu.org/viewcvs?rev=270556&root=gcc&view=rev
Log:
PR c++/90227 - error with template parameter packs.
If require_all_args, we aren't waiting for more args to be deduced later.
* pt.c (coerce_template_parms): Do add empty pack when
require_all_args.
Added:
trunk/gcc/testsuite/g++.dg/cpp1y/var-templ62.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/pt.c
>From gcc-bugs-return-641751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 20:40:50 2019
Return-Path: <gcc-bugs-return-641751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32604 invoked by alias); 24 Apr 2019 20:40:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32567 invoked by uid 48); 24 Apr 2019 20:40:45 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90236] bogus error with auto non-type template argument
Date: Wed, 24 Apr 2019 20: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.3.1
X-Bugzilla-Keywords: rejects-valid
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90236-4-koj0RT4Nfa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90236-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90236-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02607.txt.bz2
Content-length: 1219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90236
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Clearly it's this hunk:
@@ -6985,27 +7071,10 @@ convert_nontype_argument (tree type, tree expr,
tsubst_flags_t complain)
itself value-dependent, since what we want here is its address. */;
else
{
- if (!DECL_P (expr))
- {
- if (complain & tf_error)
- error ("%qE is not a valid template argument for type %qT "
- "because it is not an object with linkage",
- expr, type);
- return NULL_TREE;
- }
-
- /* DR 1155 allows internal linkage in C++11 and up. */
- linkage_kind linkage = decl_linkage (expr);
- if (linkage < (cxx_dialect >= cxx11 ? lk_internal : lk_external))
- {
- if (complain & tf_error)
- error ("%qE is not a valid template argument for type %qT "
- "because object %qD does not have linkage",
- expr, type, expr);
- return NULL_TREE;
- }
-
expr = build_address (expr);
+
+ if (invalid_tparm_referent_p (type, expr, complain))
+ return NULL_TREE;
}
if (!same_type_p (type, TREE_TYPE (expr)))
>From gcc-bugs-return-641752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 20:56:51 2019
Return-Path: <gcc-bugs-return-641752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49828 invoked by alias); 24 Apr 2019 20:56:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49755 invoked by uid 48); 24 Apr 2019 20:56:45 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/90229] Interaction among -Wl,--as-needed and LTO results in an undefined symbol
Date: Wed, 24 Apr 2019 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
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
Message-ID: <bug-90229-4-AuSXomBF5n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02608.txt.bz2
Content-length: 1515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90229
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
I can't reproduce it with binutils master branch and GCC 9:
[hjl@gnu-cfl-1 pr90229]$ cat x.ii
extern int FLAGS_verbose;
extern "C" void pthread_create(void);
void a(const char *b...) {
if (FLAGS_verbose) {
__builtin_va_list ap;
__builtin_va_start(ap, b);
}
}
void a() { pthread_create(); }
int main() { a(""); return 0; }
[hjl@gnu-cfl-1 pr90229]$ cat lib.ii
int FLAGS_verbose;
[hjl@gnu-cfl-1 pr90229]$ make
/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./ -g
-flto -c -o x.o x.ii
/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./ -g
-c -o lib.o lib.ii
/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./
-shared -g -o libx.so lib.o
/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./
-pthread -g -o x x.o libx.so -Wl,--as-needed
[hjl@gnu-cfl-1 pr90229]$
>From gcc-bugs-return-641753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 21:15:48 2019
Return-Path: <gcc-bugs-return-641753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127947 invoked by alias); 24 Apr 2019 21:15:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123160 invoked by uid 48); 24 Apr 2019 21:15:44 -0000
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90237] New: Bogus warning from -Wdo-subscript
Date: Wed, 24 Apr 2019 21: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: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: townsend at astro dot wisc.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-90237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02609.txt.bz2
Content-length: 1065
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90237
Bug ID: 90237
Summary: Bogus warning from -Wdo-subscript
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: townsend at astro dot wisc.edu
Target Milestone: ---
I'm encountering a bogus subscript-in-loop warning triggered by -Wdo-subscript
Example:
--
program do_subscript_bug
implicit none
real :: a(10)
integer :: i
a = 0.
do i = 1, 10
if (i > 1) then
print *, a(i-1)
endif
end do
end program do_subscript_bug
--
Compiling with -Wdo-subscript gives this error:
do_subscript_bug.f90:12:19:
do_subscript_bug.f90:10:14:
do i = 1, 10
2
do_subscript_bug.f90:12:19:
print *, a(i-1)
1
Warning: Array reference at (1) out of bounds (0 < 1) in loop beginning at (2)
[-Wdo-subscript]
cheers,
Rich
>From gcc-bugs-return-641754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 21:27:20 2019
Return-Path: <gcc-bugs-return-641754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41229 invoked by alias); 24 Apr 2019 21:27: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 39305 invoked by uid 48); 24 Apr 2019 21:27:17 -0000
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90238] New: Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Wed, 24 Apr 2019 21: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.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: townsend at astro dot wisc.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-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02610.txt.bz2
Content-length: 1025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
Bug ID: 90238
Summary: Bogus warning from -Warray-bounds, triggered by
zero-length character literal
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: townsend at astro dot wisc.edu
Target Milestone: ---
The zero-length character literal following example program triggers a bogus
array-bounds warning:
--
program test_str
call foo('bar')
call foo('')
contains
subroutine foo (a)
character(*), intent(in) :: a
print *, a
end subroutine foo
end program test_str
--
Compiling with -O2 -Warray-bounds, the warning is:
test_str.f90:4:0:
call foo('')
Warning: array subscript 1 is above array bounds of 'character(kind=1)[1:0]'
[-Warray-bounds]
Compiling at -O1 or -O0 does not trigger the warning.
cheers,
Rich
>From gcc-bugs-return-641755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 21:28:38 2019
Return-Path: <gcc-bugs-return-641755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44602 invoked by alias); 24 Apr 2019 21:28: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 44553 invoked by uid 55); 24 Apr 2019 21:28:35 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90236] bogus error with auto non-type template argument
Date: Wed, 24 Apr 2019 21:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: rejects-valid
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90236-4-7mb8rgJ2aP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90236-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90236-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02611.txt.bz2
Content-length: 443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90236
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Apr 24 21:28:04 2019
New Revision: 270557
URL: https://gcc.gnu.org/viewcvs?rev=270557&root=gcc&view=rev
Log:
PR c++/90236
* g++.dg/cpp1z/nontype-auto16.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp1z/nontype-auto16.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-641756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 21:29:19 2019
Return-Path: <gcc-bugs-return-641756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48176 invoked by alias); 24 Apr 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 48147 invoked by uid 48); 24 Apr 2019 21:29:16 -0000
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Wed, 24 Apr 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: fortran
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: townsend at astro dot wisc.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-90238-4-s53pKACqnm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02612.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
--- Comment #1 from Rich Townsend <townsend at astro dot wisc.edu> ---
An even-simpler demo:
--
program test_str_2
write(*,*) ''
end program test_str_2
--
Compile with -O2 -Warray-bounds gives
test_str_2.f90:3:0:
write(*,*) ''
Warning: array subscript 1 is above array bounds of 'character(kind=1)[1:0]'
[-Warray-bounds]
cheers,
Rich
>From gcc-bugs-return-641757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 21:33:46 2019
Return-Path: <gcc-bugs-return-641757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117554 invoked by alias); 24 Apr 2019 21:33:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117519 invoked by uid 48); 24 Apr 2019 21:33:43 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90237] Bogus warning from -Wdo-subscript
Date: Wed, 24 Apr 2019 21:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: priority cc bug_severity
Message-ID: <bug-90237-4-NwrfBvV3YY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02613.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90237
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
CC| |kargl at gcc dot gnu.org
Severity|normal |enhancement
>From gcc-bugs-return-641758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 21:46:57 2019
Return-Path: <gcc-bugs-return-641758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55345 invoked by alias); 24 Apr 2019 21: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 55306 invoked by uid 48); 24 Apr 2019 21:46:53 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Wed, 24 Apr 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: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
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: priority cc component bug_severity
Message-ID: <bug-90238-4-qHihwYVOIL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02614.txt.bz2
Content-length: 821
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
CC| |kargl at gcc dot gnu.org
Component|fortran |middle-end
Severity|normal |enhancement
--- Comment #2 from kargl at gcc dot gnu.org ---
-Warray-bounds is a generic GCC option, and is used in the
middle end for reporting warnings. When you use this option
it does not recognize that a Fortran string is not an array.
So, it gleefully reports an array bounds option. In other
words, either ignore the warning or stop using -Warray-bounds.
>From gcc-bugs-return-641759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 22:01:17 2019
Return-Path: <gcc-bugs-return-641759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85704 invoked by alias); 24 Apr 2019 22: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 85585 invoked by uid 48); 24 Apr 2019 22:01:13 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90237] Bogus warning from -Wdo-subscript
Date: Wed, 24 Apr 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: 8.3.0
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: P5
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-90237-4-XglGlEcqko@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02615.txt.bz2
Content-length: 880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90237
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
We should probably rename the option. It works as advertised:
`-Wdo-subscript'
Warn if an array subscript inside a DO loop could lead to an
out-of-bounds access even if the compiler cannot prove that the
statement is actually executed, in cases like
real a(3)
do i=1,4
if (condition(i)) then
a(i) = 1.2
end if
end do
This option is implied by `-Wextra'.
but people keep stumbling over it.
>From gcc-bugs-return-641760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 22:10:19 2019
Return-Path: <gcc-bugs-return-641760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96441 invoked by alias); 24 Apr 2019 22:10:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96369 invoked by uid 48); 24 Apr 2019 22:10:16 -0000
From: "qinzhao at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/47618] Collecting multiple profiles and using all for PGO
Date: Wed, 24 Apr 2019 22:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: qinzhao 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: cc
Message-ID: <bug-47618-4-rzn1tqxU4G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47618-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47618-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02616.txt.bz2
Content-length: 1117
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47618
qinzhao at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |qinzhao at gcc dot gnu.org
--- Comment #23 from qinzhao at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #7)
> Created attachment 27869 [details]
> Patch for adding merge-gcda
>
> here is the patch which adds merge-gcda . I don't add any testcases as it
> is currently designed only for how Cavium's Simple-exec works in that each
> core writes out its own gcda file.
I recently found this bug due to a similar problem. looks like that there are
two parts of work for this problem:
1. GCC's new feature to guarantee that all pre-merged files are saved with
different names for different instances of the same process.
2. a merge tool to merge all the gcda files afterwards.
from my understanding, the patch for the above 1 has been committed into GCC9.
How about the patch for the above 2? has it been committed?
>From gcc-bugs-return-641761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 22:33:55 2019
Return-Path: <gcc-bugs-return-641761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55986 invoked by alias); 24 Apr 2019 22:33:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55944 invoked by uid 55); 24 Apr 2019 22:33:51 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90237] Bogus warning from -Wdo-subscript
Date: Wed, 24 Apr 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: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
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-90237-4-LuZNaMVqqm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02617.txt.bz2
Content-length: 1450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90237
--- Comment #2 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Apr 24, 2019 at 10:01:13PM +0000, tkoenig at gcc dot gnu.org wrote:
> --- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> We should probably rename the option. It works as advertised:
A renaming is probably not needed. A better description including
a clearer statement about false-positives may be helpful.
> `-Wdo-subscript'
> Warn if an array subscript inside a DO loop could lead to an
> out-of-bounds access even if the compiler cannot prove that the
> statement is actually executed, in cases like
> real a(3)
> do i=1,4
> if (condition(i)) then
> a(i) = 1.2
> end if
> end do
> This option is implied by `-Wextra'.
>
>
> but people keep stumbling over it.
>
`-Wdo-subscript'
Warn if an array subscript inside a DO loop could lead to an
out-of-bounds access. This warning currently does not consider
conditional statement that may prevent an out-of-bounds access.
For example, a false-positive will be emitted for
real a(3)
do i=1,4
if (i > 1) then
a(i-1) = 1.2
end if
end do
This option is implied by `-Wextra'. See also the -fcheck=bounds
option.
>From gcc-bugs-return-641763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 22:47:52 2019
Return-Path: <gcc-bugs-return-641763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66206 invoked by alias); 24 Apr 2019 22:47:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66134 invoked by uid 48); 24 Apr 2019 22:47:48 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/90086] libphobos: warning: type and size of dynamic symbol `fiber_switchContext' are not defined
Date: Wed, 24 Apr 2019 22:47: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: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90086-4-JAaJycwWAJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90086-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90086-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02619.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90086
Iain Buclaw <ibuclaw at gdcproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Fixed in r270560.
>From gcc-bugs-return-641762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 22:47:36 2019
Return-Path: <gcc-bugs-return-641762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65505 invoked by alias); 24 Apr 2019 22: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 65459 invoked by uid 55); 24 Apr 2019 22:47:30 -0000
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/90086] libphobos: warning: type and size of dynamic symbol `fiber_switchContext' are not defined
Date: Wed, 24 Apr 2019 22:47: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 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-90086-4-U66mCbkjv2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90086-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90086-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02618.txt.bz2
Content-length: 2674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90086
--- Comment #1 from ibuclaw at gcc dot gnu.org ---
Author: ibuclaw
Date: Wed Apr 24 22:46:59 2019
New Revision: 270560
URL: https://gcc.gnu.org/viewcvs?rev=270560&root=gcc&view=rev
Log:
libphobos: Fix linker warning and SEGV in core.thread tests.
The monolithic core/threadasm.S source has been removed, and split into
multiple parts, one for each intended target CPU/OS.
Added .type and .size directives for all asm implementations of
fiber_switchContent and callWithStackShell where they were missing.
libphobos/ChangeLog:
2019-04-25 Iain Buclaw <ibuclaw@gdcproject.org>
PR d/90086
* m4/druntime/cpu.m4 (DRUNTIME_CPU_SOURCES): New macro.
* configure.ac: Use it.
* configure: Regenerate.
* libdruntime/Makefile.am: Add new config sources to
DRUNTIME_SOURCES_CONFIGURED.
* libdruntime/Makefile.in: Regenerate.
* libdruntime/config/aarch64/switchcontext.S: New file.
* libdruntime/config/arm/switchcontext.S: New file.
* libdruntime/config/common/threadasm.S: New file.
* libdruntime/config/mingw/switchcontext.S: New file.
* libdruntime/config/mips/switchcontext.S: New file.
* libdruntime/config/powerpc/switchcontext.S: New file.
* libdruntime/config/powerpc64/callwithstack.S: New file.
* libdruntime/config/x86/switchcontext.S: New file.
* libdruntime/core/threadasm.S: Remove.
Added:
trunk/libphobos/libdruntime/config/
trunk/libphobos/libdruntime/config/aarch64/
trunk/libphobos/libdruntime/config/aarch64/switchcontext.S
trunk/libphobos/libdruntime/config/arm/
trunk/libphobos/libdruntime/config/arm/switchcontext.S
trunk/libphobos/libdruntime/config/common/
trunk/libphobos/libdruntime/config/common/threadasm.S
trunk/libphobos/libdruntime/config/mingw/
trunk/libphobos/libdruntime/config/mingw/switchcontext.S
trunk/libphobos/libdruntime/config/mips/
trunk/libphobos/libdruntime/config/mips/switchcontext.S
trunk/libphobos/libdruntime/config/powerpc/
trunk/libphobos/libdruntime/config/powerpc/switchcontext.S
trunk/libphobos/libdruntime/config/powerpc64/
trunk/libphobos/libdruntime/config/powerpc64/callwithstack.S
trunk/libphobos/libdruntime/config/x86/
trunk/libphobos/libdruntime/config/x86/switchcontext.S
Removed:
trunk/libphobos/libdruntime/core/threadasm.S
Modified:
trunk/libphobos/ChangeLog
trunk/libphobos/configure
trunk/libphobos/configure.ac
trunk/libphobos/libdruntime/Makefile.am
trunk/libphobos/libdruntime/Makefile.in
trunk/libphobos/m4/druntime/cpu.m4
>From gcc-bugs-return-641764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Apr 24 23:01:02 2019
Return-Path: <gcc-bugs-return-641764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103074 invoked by alias); 24 Apr 2019 23:01: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 102714 invoked by uid 48); 24 Apr 2019 23:00:57 -0000
From: "skpgkp1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90088] 3 ops LEA should be avoided on Intel CPUs
Date: Wed, 24 Apr 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: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: skpgkp1 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-90088-4-LOSQyjzDKm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90088-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90088-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02620.txt.bz2
Content-length: 284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90088
--- Comment #6 from Sunil Pandey <skpgkp1 at gmail dot com> ---
We look into this issue and tested lea vs lea equivalent on following
processor.
On Haswell/Broadwell/Skylake/CoffeeLake processors, lea is faster than
alternative.
>From gcc-bugs-return-641765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 00:41:14 2019
Return-Path: <gcc-bugs-return-641765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100215 invoked by alias); 25 Apr 2019 00: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 100080 invoked by uid 48); 25 Apr 2019 00:41:10 -0000
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Thu, 25 Apr 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: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: townsend at astro dot wisc.edu
X-Bugzilla-Status: UNCONFIRMED
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-90238-4-pmW5NLjeWZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02621.txt.bz2
Content-length: 611
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
--- Comment #3 from Rich Townsend <townsend at astro dot wisc.edu> ---
(In reply to kargl from comment #2)
> -Warray-bounds is a generic GCC option, and is used in the
> middle end for reporting warnings. When you use this option
> it does not recognize that a Fortran string is not an array.
> So, it gleefully reports an array bounds option. In other
> words, either ignore the warning or stop using -Warray-bounds.
Thanks for the quick response, Steve. I think I can figure a workaround that
allows us to continue using -Warray-bounds.
cheers,
Rich
>From gcc-bugs-return-641766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 01:03:58 2019
Return-Path: <gcc-bugs-return-641766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81284 invoked by alias); 25 Apr 2019 01:03:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81245 invoked by uid 55); 25 Apr 2019 01:03:55 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Thu, 25 Apr 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: middle-end
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
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-90238-4-4nhcLW3QAf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02622.txt.bz2
Content-length: 1340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, Apr 25, 2019 at 12:41:10AM +0000, townsend at astro dot wisc.edu wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
>
> --- Comment #3 from Rich Townsend <townsend at astro dot wisc.edu> ---
> (In reply to kargl from comment #2)
> > -Warray-bounds is a generic GCC option, and is used in the
> > middle end for reporting warnings. When you use this option
> > it does not recognize that a Fortran string is not an array.
> > So, it gleefully reports an array bounds option. In other
> > words, either ignore the warning or stop using -Warray-bounds.
>
> Thanks for the quick response, Steve. I think I can figure a workaround that
> allows us to continue using -Warray-bounds.
>
It's certainly confusing. gfortran.info includes
-Warray-bounds as a warning option, but there is no
description for the option. Grepping the gfortran
source code found the error was not coming from the
Fortran frontend. Grepping the GCC source finds
two instances of the warning string tree-vrp.c. I
know nothing of the middle-end code and how Fortran
strings are represented. Hopeefully, one the
middle-end developers can provide a clue to
suppressing the warning for Fortran strings.
>From gcc-bugs-return-641767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 01:08:02 2019
Return-Path: <gcc-bugs-return-641767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84463 invoked by alias); 25 Apr 2019 01:08:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84389 invoked by uid 48); 25 Apr 2019 01:07:59 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/90231] ivopts causes <optimized away> iterator in the loop
Date: Thu, 25 Apr 2019 01:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-90231-4-1IYCnHQwY6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90231-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90231-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02623.txt.bz2
Content-length: 418
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90231
bin cheng <amker at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |amker at gcc dot gnu.org
--- Comment #5 from bin cheng <amker at gcc dot gnu.org> ---
I will try to fix it for GCC10. Thanks
>From gcc-bugs-return-641768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 01:10:05 2019
Return-Path: <gcc-bugs-return-641768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87513 invoked by alias); 25 Apr 2019 01:10: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 87490 invoked by uid 48); 25 Apr 2019 01:10:02 -0000
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Thu, 25 Apr 2019 01: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.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: townsend at astro dot wisc.edu
X-Bugzilla-Status: UNCONFIRMED
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-90238-4-kxaeo07seP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02624.txt.bz2
Content-length: 953
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
--- Comment #5 from Rich Townsend <townsend at astro dot wisc.edu> ---
(In reply to Steve Kargl from comment #4)
> It's certainly confusing. gfortran.info includes
> -Warray-bounds as a warning option, but there is no
> description for the option. Grepping the gfortran
> source code found the error was not coming from the
> Fortran frontend. Grepping the GCC source finds
> two instances of the warning string tree-vrp.c. I
> know nothing of the middle-end code and how Fortran
> strings are represented. Hopeefully, one the
> middle-end developers can provide a clue to
> suppressing the warning for Fortran strings.
That might be nice. In the meantime, the workaround consists of passing blank
strings ' ' instead of zero-length strings '', since the production code
behaves the same either way. And for the write statement,
write(*,*)
does the same as
write(*,*) ''
cheers,
Rich
>From gcc-bugs-return-641769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 02:41:50 2019
Return-Path: <gcc-bugs-return-641769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45974 invoked by alias); 25 Apr 2019 02: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 45947 invoked by uid 48); 25 Apr 2019 02:41:46 -0000
From: "JunMa at linux dot alibaba.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90106] builtin sqrt() ignoring libm's sqrt call result
Date: Thu, 25 Apr 2019 02: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: JunMa at linux dot alibaba.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-90106-4-77Tmbf4VX0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02625.txt.bz2
Content-length: 3297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90106
--- Comment #8 from JunMa <JunMa at linux dot alibaba.com> ---
(In reply to Alexander Monakov from comment #6)
> Reopening and confirming, GCC's code looks less efficient than possible for
> no good reason.
>
> CDCE does
>
> y = sqrt (x);
> ==>
> y = IFN_SQRT (x);
> if (__builtin_isless (x, 0))
> sqrt (x);
>
> but it could do
>
> y = IFN_SQRT (x);
> if (__builtin_isless (x, 0))
> y = sqrt (x);
>
> (note two assignments to y)
>
what is the difference between this and LLVM's approach ?
> or to mimic LLVM's approach:
>
> if (__builtin_isless (x, 0))
> y = sqrt (x);
> else
> y = IFN_SQRT (x);
I have finished a patch which do as same as LLVM in cdce pass, and test with
case below:
#include <math.h>
int main () {
float x = 1.0;
float y;
for (int i=0; i<100000000; i++) {
y += sqrtf (x+i);
}
return y;
}
And I've got, for x86-64 with O2:
# original asm of IFN_SQRT part
.L4:
pxor %xmm0, %xmm0
cvtsi2ssl %ebx, %xmm0
addss %xmm3, %xmm0
ucomiss %xmm0, %xmm4
movaps %xmm0, %xmm2
sqrtss %xmm2, %xmm2
ja .L7
and perf stat :
1,423,652,277 cycles # 2.180 GHz
(83.31%)
1,121,862,980 stalled-cycles-frontend # 78.80% frontend cycles
idle (83.31%)
634,957,413 stalled-cycles-backend # 44.60% backend cycles
idle (66.62%)
1,102,109,423 instructions # 0.77 insn per cycle
# 1.02 stalled cycles per
insn (83.31%)
200,400,940 branches # 306.873 M/sec
(83.44%)
7,734 branch-misses # 0.00% of all branches
(83.44%)
#transformed asm :
.L4:
pxor %xmm0, %xmm0
cvtsi2ssl %ebx, %xmm0
addss %xmm3, %xmm0
ucomiss %xmm0, %xmm2
ja .L8
sqrtss %xmm0, %xmm0
and perf stat:
1,418,560,722 cycles # 2.180 GHz
(83.25%)
1,116,732,674 stalled-cycles-frontend # 78.72% frontend cycles
idle (83.25%)
674,837,417 stalled-cycles-backend # 47.57% backend cycles
idle (66.81%)
1,003,067,037 instructions # 0.71 insn per cycle
# 1.11 stalled cycles per
insn (83.41%)
200,619,151 branches # 308.272 M/sec
(83.40%)
5,637 branch-misses # 0.00% of all branches
(83.28%)
The transformed case has less instructions and gets better performance which
looks good to me. However, one thing that I noticed is the original case gets
less 'stalled-cycles-backend', since its code has better ILP.
I'm not sure which approach is better.
Environment:
gcc version: gcc trunk@270488
OS: centos7.2
HW: Intel(R) Xeon(R) CPU E5-2430 0 @ 2.20GHz
>From gcc-bugs-return-641770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 03:11:49 2019
Return-Path: <gcc-bugs-return-641770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77671 invoked by alias); 25 Apr 2019 03: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 77617 invoked by uid 48); 25 Apr 2019 03:11:45 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85541] ICE with parameterized derived type (PDT) and allocate
Date: Thu, 25 Apr 2019 03:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85541-4-7Si3Lev3wt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85541-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02626.txt.bz2
Content-length: 3445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85541
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asolokha at gmx dot com
--- Comment #2 from Arseny Solokha <asolokha at gmx dot com> ---
I believe the following testcase demonstrates the same issue (I'll file a new
PR if it doesn't):
subroutine uc
type z4(pj)
integer, len :: pj
end type z4
type tp(q6)
integer, len :: q6
type(z4(q6)), pointer :: kz
end type tp
type(tp(:)), allocatable :: ng
end subroutine uc
% powerpc-e300c3-linux-gnu-gfortran-9.0.0-alpha20190421 -c y2s4yo8l.f90
f951: internal compiler error: Segmentation fault
0xd84686 crash_signal
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/toplev.c:326
0x7796dd insert_parameter_exprs
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/decl.c:3488
0x7796dd insert_parameter_exprs
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/decl.c:3468
0x7975c0 gfc_traverse_expr(gfc_expr*, gfc_symbol*, bool (*)(gfc_expr*,
gfc_symbol*, int*), int)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/expr.c:5142
0x77cbdf gfc_get_pdt_instance(gfc_actual_arglist*, gfc_symbol**,
gfc_actual_arglist**)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/decl.c:3907
0x782d25 gfc_match_decl_type_spec(gfc_typespec*, int)
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/decl.c:4129
0x785471 gfc_match_data_decl()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/decl.c:5950
0x7e937b match_word
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:65
0x7e937b decode_statement
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:376
0x7ed141 next_free
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:1241
0x7ed141 next_statement
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:1473
0x7eeaec parse_spec
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:3865
0x7f188f parse_progunit
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:5680
0x7f28eb gfc_parse_file()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/parse.c:6234
0x84064e gfc_be_parse_file
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/fortran/f95-lang.c:204
>From gcc-bugs-return-641771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 03:39:15 2019
Return-Path: <gcc-bugs-return-641771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8942 invoked by alias); 25 Apr 2019 03: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 8877 invoked by uid 48); 25 Apr 2019 03:39:05 -0000
From: "daniel.santos at pobox dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/68931] gccgo fails to build using MUSL libc
Date: Thu, 25 Apr 2019 03:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 5.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daniel.santos at pobox dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-68931-4-9fF3PW2fxV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68931-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02627.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68931
Daniel Santos <daniel.santos at pobox dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daniel.santos at pobox dot com
--- Comment #3 from Daniel Santos <daniel.santos at pobox dot com> ---
Confirmed. Also present with gcc 7.3.0 and musl 1.1.19 (in addition to some
multiply defined structs)
>From gcc-bugs-return-641772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 05:05:49 2019
Return-Path: <gcc-bugs-return-641772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17725 invoked by alias); 25 Apr 2019 05:05:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17699 invoked by uid 48); 25 Apr 2019 05:05:45 -0000
From: "JunMa at linux dot alibaba.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90106] builtin sqrt() ignoring libm's sqrt call result
Date: Thu, 25 Apr 2019 05: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.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: JunMa at linux dot alibaba.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-90106-4-49ZwLQefOj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02628.txt.bz2
Content-length: 1840
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90106
--- Comment #9 from JunMa <JunMa at linux dot alibaba.com> ---
(In reply to JunMa from comment #7)
> yes, the transformation in CDEC prevent the tail call optimization. let's
> check the return stmt in CDEC pass.
Sorry for the confused comment.
As the discussion above, The cdce pass looks for calls to built-in functions
that set errno and whose result is used. It tries to transform these calls into
conditionally executes calls with a simple range check on the arguments which
can detect most cases and the errno does not need to be set. The transform
looks like:
y = sqrt (x);
==>
y = IFN_SQRT (x);
if (__builtin_isless (x, 0))
sqrt (x);
However when the call is in tail position, this transformation breaks tailcall
optimizations, since the conditionally call does not have return value. This is
what this PR tries to explain and fix.
Alexander gives two suggestions:
first:
y = IFN_SQRT (x);
if (__builtin_isless (x, 0))
y = sqrt (x);
second(LLVM's approach):
if (__builtin_isless (x, 0))
y = sqrt (x);
else
y = IFN_SQRT (x);
So what I want to do here is looking for tailcall and transforming as first
one.
I did some hacks locally, but then I found gcc generated even worse code in 'y
= IFN_SQRT' part:
f:
pxor %xmm1, %xmm1
movaps %xmm0, %xmm2
ucomiss %xmm0, %xmm1
sqrtss %xmm2, %xmm2
ja .L4
movaps %xmm2, %xmm0
ret
.L4:
jmp sqrtf
Then I used LLVM's approach no matter call is in tail position or not, and it
gives:
f:
pxor %xmm1, %xmm1
ucomiss %xmm0, %xmm1
ja .L4
sqrtss %xmm0, %xmm0
ret
.L4:
jmp sqrtf
Also in comment 6, I did some test for LLVM's approach.
Sorry for the confused comment again.
>From gcc-bugs-return-641773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 05:26:33 2019
Return-Path: <gcc-bugs-return-641773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38814 invoked by alias); 25 Apr 2019 05:26:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38779 invoked by uid 48); 25 Apr 2019 05:26:29 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/63613] dejagnu.h needs to be fix included
Date: Thu, 25 Apr 2019 05:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-63613-4-9oeyu0y54P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02629.txt.bz2
Content-length: 910
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63613
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bkorb at gnu dot org
--- Comment #13 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #12)
> (In reply to David Malcolm from comment #11)
> > Patch posted as https://gcc.gnu.org/ml/gcc-patches/2014-12/msg00468.html
>
> Does this still apply?
So after reviewing this thread, it looks like Jeff Law approved the patch, but
Bruce Korb requested a minor tweak. It should be pretty easy to make Bruce's
requested change; can you do that and resubmit, David? Or are we assuming that
dejagnu 1.6 has been out long enough now that this bug doesn't really matter
any longer?
>From gcc-bugs-return-641774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 05:35:54 2019
Return-Path: <gcc-bugs-return-641774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66258 invoked by alias); 25 Apr 2019 05:35:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66221 invoked by uid 48); 25 Apr 2019 05:35:51 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/26613] Corner case causes garbage to be output by -aux-info switch.
Date: Thu, 25 Apr 2019 05: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: 4.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-26613-4-EsCWhLBx0x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02630.txt.bz2
Content-length: 573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26613
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Eric Gallager from comment #7)
> > (In reply to Mark F. Haigh from comment #5)
> > > Created attachment 11005 [details]
> > > Fix for trunk (against 2006-03-03 CVS)
> >
> > Could you submit a newer version of this patch to the gcc-patches mailing
> > list please?
>
> I doubt c-aux-info.c has changed in the last 10 years ...
I tried applying it and the second hunk was rejected...
>From gcc-bugs-return-641775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 05:42:10 2019
Return-Path: <gcc-bugs-return-641775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86040 invoked by alias); 25 Apr 2019 05:42: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 85999 invoked by uid 48); 25 Apr 2019 05:42:06 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/37874] gcc sometimes accepts attribute in identifier list
Date: Thu, 25 Apr 2019 05:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: accepts-invalid
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-37874-4-7DLRlDJfTJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37874-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02631.txt.bz2
Content-length: 1753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37874
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #5)
> (In reply to Chris Lattner from comment #0)
> > GCC rejects the former, but not the later.
> >
> > void f2(y, __attribute__(()) x);
> > void f3(__attribute__(()) x, y);
>
> GCC can be made to reject f3() with -Werror:
>
> $ /usr/local/bin/gcc -c -Wall -Wextra -pedantic -Werror 37874.c
> 37874.c:1:12: error: expected ‘)’ before ‘__attribute__’
> void f2(y, __attribute__(()) x);
> ^~~~~~~~~~~~~
> 37874.c:2:1: error: parameter names (without types) in function declaration
> [-Werror]
> void f3(__attribute__(()) x, y);
> ^~~~
> cc1: all warnings being treated as errors
>
> I see you fixed this for f4() at least for clang:
>
> $ /sw/opt/llvm-3.1/bin/clang-3.1 -c 37874.c
> 37874.c:1:12: error: expected identifier
> void f2(y, __attribute__(()) x);
> ^
> 37874.c:2:27: warning: type specifier missing, defaults to 'int'
> [-Wimplicit-int]
> void f3(__attribute__(()) x, y);
> ~~~~~~~~~~~~~ ^
> 37874.c:2:30: warning: type specifier missing, defaults to 'int'
> [-Wimplicit-int]
> void f3(__attribute__(()) x, y);
> ^
> 37874.c:3:9: error: expected parameter declarator
> void f4(__attribute__(()));
> ^
> 2 warnings and 2 errors generated.
Since clang rejects this, I'm making this an accepts-invalid
>From gcc-bugs-return-641776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 05:55:45 2019
Return-Path: <gcc-bugs-return-641776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111926 invoked by alias); 25 Apr 2019 05:55: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 111890 invoked by uid 48); 25 Apr 2019 05:55:41 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89043] strcat (strcpy (d, a), b) not folded to stpcpy (strcpy (d, a), b)
Date: Thu, 25 Apr 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: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
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-89043-4-CPsCUSDQLm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89043-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89043-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02632.txt.bz2
Content-length: 393
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89043
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
Anyways my point about bringing up which standards stpcpy() is in is to remind
people to keep portability concerns in mind when doing this change. Please
check the gnulib docs on stpcpy() for specifics:
https://www.gnu.org/software/gnulib/manual/html_node/stpcpy.html
>From gcc-bugs-return-641777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 06:43:18 2019
Return-Path: <gcc-bugs-return-641777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69020 invoked by alias); 25 Apr 2019 06: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 68786 invoked by uid 48); 25 Apr 2019 06:43:14 -0000
From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90239] New: [C++20] scoped_allocator_adaptor should support nested pair
Date: Thu, 25 Apr 2019 06: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kariya_mitsuru at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02633.txt.bz2
Content-length: 3104
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90239
Bug ID: 90239
Summary: [C++20] scoped_allocator_adaptor should support nested
pair
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: kariya_mitsuru at hotmail dot com
Target Milestone: ---
The current implementation of scoped_allocator_adaptor is not support nested
pair.
=========================== sample code ===========================
#include <iostream>
#include <vector>
#include <utility>
#include <scoped_allocator>
#include <new>
// stateful allocator
template <typename T>
class MyAlloc {
public:
using value_type = T;
T* allocate(std::size_t n) { return static_cast<T*>(::operator
new(sizeof(T) * n)); }
void deallocate(T* p, std::size_t n) { ::operator
delete(static_cast<void*>(p), sizeof(T) * n); }
MyAlloc(int state) noexcept : state(state) {}
template <typename U>
MyAlloc(const MyAlloc<U>& o) noexcept : state(o.state) {}
int state;
};
template <typename T>
bool operator==(const MyAlloc<T>& lhs, const MyAlloc<T>& rhs) noexcept
{
return lhs.state == rhs.state;
}
template <typename T>
bool operator!=(const MyAlloc<T>& lhs, const MyAlloc<T>& rhs) noexcept
{
return lhs.state != rhs.state;
}
// type alias
template <typename T>
using SA = std::scoped_allocator_adaptor<MyAlloc<T>>;
template <typename T>
using VEC = std::vector<T, SA<T>>;
int main()
{
VEC<std::pair<std::pair<VEC<int>, int>, int>> v(SA<int>(1));
v.emplace_back(std::make_pair(VEC<int>{SA<int>(2)}, 1), 2);
v.emplace_back(std::make_pair(VEC<int>{SA<int>(3)}, 3), 4);
std::cout << v.get_allocator().state << ", "
<< v[0].first.first.get_allocator().state << ", "
<< v[1].first.first.get_allocator().state << '\n';
}
=========================== sample code ===========================
=========================== sample output ===========================
1, 2, 3
=========================== sample output ===========================
cf. https://wandbox.org/permlink/mcVJEFjpR2UeyW0O
I think that it should output "1, 1, 1" in c++2a mode.
P0591R4: Utility functions to implement uses-allocator construction
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2018/p0591r4.pdf
C++ 2020 Implementation Status
https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2020
commit for P0591R4
https://github.com/gcc-mirror/gcc/commit/6a9c77f14d18d819dc4b03e1ebc2da4e5f085627
>From gcc-bugs-return-641778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 06:58:40 2019
Return-Path: <gcc-bugs-return-641778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21732 invoked by alias); 25 Apr 2019 06: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 21702 invoked by uid 48); 25 Apr 2019 06:58:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] New: [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 2019 06:58: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 target_milestone
Message-ID: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02634.txt.bz2
Content-length: 2081
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
Bug ID: 90240
Summary: [9 Regression] ICE in try_improve_iv_set, at
tree-ssa-loop-ivopts.c:6694
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
Target Milestone: ---
Probably a GCC 9 regression:
$ cat ice.f
PARAMETER (n=1335, N2=1335)
COMMON a(n,N2), b(n,N2), c(n,N2),
* d(n,N2),
2 e(n,N2), f(n,N2),
* g(n,N2), h(n,N2)
DO 200 j=1,i
DO 200 k=1,l
a(k,j) = c(k,j)*g(k,j)*f(k+1,m)+f(k,m)+f(k,j)
2 +f(k+1,j)*h(k+1,j)
b(k,j+1) = d(k,j+1)*g(k,m)+g(k,j+1)
1 *e(k,m)+e(k,j+1)+e(k,j)+e(k+1,j)
2 *h(k,j+1)-h(k,j)
200 CONTINUE
END
$ /home/marxin/Programming/gcc2/objdir/gcc/xgcc
-B/home/marxin/Programming/gcc2/objdir/gcc/ -floop-nest-optimize -O1 ice.f -c
ice.f:7:72:
7 | DO 200 k=1,l
|
1
Warning: Fortran 2018 deleted feature: Shared DO termination label 200 at (1)
during GIMPLE pass: ivopts
ice.f:14:0:
14 | END
|
internal compiler error: in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
0x13f848a try_improve_iv_set
../../gcc/tree-ssa-loop-ivopts.c:6694
0x13f85aa find_optimal_iv_set_1
../../gcc/tree-ssa-loop-ivopts.c:6724
0x13f8658 find_optimal_iv_set
../../gcc/tree-ssa-loop-ivopts.c:6746
0x13fb851 tree_ssa_iv_optimize_loop
../../gcc/tree-ssa-loop-ivopts.c:7599
0x13fb9aa tree_ssa_iv_optimize()
../../gcc/tree-ssa-loop-ivopts.c:7637
0x142b6d9 execute
../../gcc/tree-ssa-loop.c:513
>From gcc-bugs-return-641779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 06:59:44 2019
Return-Path: <gcc-bugs-return-641779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22947 invoked by alias); 25 Apr 2019 06: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 22907 invoked by uid 48); 25 Apr 2019 06:59:40 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 2019 06: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: 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_reconfirmed_on cc cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-90240-4-83KfsXQu5t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02635.txt.bz2
Content-length: 680
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Last reconfirmed| |2019-4-25
CC| |amker at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Known to work| |8.3.0
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-641780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 07:38:51 2019
Return-Path: <gcc-bugs-return-641780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32455 invoked by alias); 25 Apr 2019 07: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 32414 invoked by uid 48); 25 Apr 2019 07:38:48 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 2019 07:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-90240-4-2Y7h2dsmPG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02636.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
bin cheng <amker at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |amker at gcc dot gnu.org
--- Comment #1 from bin cheng <amker at gcc dot gnu.org> ---
probably something with recent changes on comp_cost::operators
>From gcc-bugs-return-641781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 07:44:11 2019
Return-Path: <gcc-bugs-return-641781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70603 invoked by alias); 25 Apr 2019 07: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 70552 invoked by uid 48); 25 Apr 2019 07:44:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug translation/90119] Merge translation msgids that only differ in placeholders
Date: Thu, 25 Apr 2019 07:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: translation
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90119-4-tbbeIPxd3D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02637.txt.bz2
Content-length: 1765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90119
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Roland Illig from comment #7)
> I didn't want to sound that harsh in my previous comment.
>
> What I wanted to say is: to make the linter reliable and be able to handle
> the full syntax of .po files, it's better to use an exising library that is
> well-tested instead of parsing .po files ad-hoc using regular expressions
> and raw string functions.
I welcome your linter! The one I wrote was just a one time script that I
eventually installed to our contrib scripts.
>
> That way the code of the linter becomes easy to read since it uses the
> standard terminology of the .po structures, and it is easy to access all
> gettext features (such as plurals or other formats) without modifying the
> parser code.
>
> It also becomes easier to add new checks to the linter.
>
> The diagnostics of the linter now follow more closely the GCC Guidelines for
> Diagnostics, by offering guidance and saying what the actual possible
> problem is, instead of only pointing to the problematic message.
>
> This of course requires a bit more code than the current linter.
>
> I have checked that my rewrite preserves all existing features of the
> linter. I don't think adding new features to the current architecture of the
> linter makes sense since it requires more work than absolutely necessary. To
> add a new linter check, it shouldn't be necessary to modify any .po file
> format parser. Therefore I think replacing the current linter with the
> latest suggested code from bug 90176 actually makes sense.
Great, can you please send a patch to gcc-patches and install the new linter to
contrib scripts?
>From gcc-bugs-return-641782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 07:51:08 2019
Return-Path: <gcc-bugs-return-641782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7916 invoked by alias); 25 Apr 2019 07:51: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 7839 invoked by uid 48); 25 Apr 2019 07:51:04 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90241] New: [UBSAN]: in ao_ref_init_from_ptr_and_size
Date: Thu, 25 Apr 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: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90241-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02638.txt.bz2
Content-length: 1611
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90241
Bug ID: 90241
Summary: [UBSAN]: in ao_ref_init_from_ptr_and_size
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Following on from PR 85164, where I tried a UBSAN version
of gcc trunk over the testsuite, for file
c-c++-common/Warray-bounds-2.c, I got:
../../trunk/gcc/poly-int.h:1107:5: runtime error: signed integer overflow: 8 *
-9223372036854775796 cannot be represented in type 'long int'
#0 0x2ddd587 in poly_int<1u, poly_result<if_nonpoly<int, int,
poly_int_traits<int>::is_poly>::type, long,
poly_coeff_pair_traits<if_nonpoly<int, int,
poly_int_traits<int>::is_poly>::type, long>::result_kind>::type> operator*<1u,
int, long>(int const&, poly_int_pod<1u, long> const&)
../../trunk/gcc/poly-int.h:1107
#1 0x2ddd587 in ao_ref_init_from_ptr_and_size(ao_ref*, tree_node*,
tree_node*) ../../trunk/gcc/tree-ssa-alias.c:703
#2 0x2ea1f49 in initialize_ao_ref_for_dse
../../trunk/gcc/tree-ssa-dse.c:106
#3 0x2ea1f49 in initialize_ao_ref_for_dse ../../trunk/gcc/tree-ssa-dse.c:91
#4 0x2ea784b in dse_dom_walker::dse_optimize_stmt(gimple_stmt_iterator*)
../../trunk/gcc/tree-ssa-dse.c:851
#5 0x2eab4ba in dse_dom_walker::before_dom_children(basic_block_def*)
../../trunk/gcc/tree-ssa-dse.c:944
#6 0x4e831f6 in dom_walker::walk(basic_block_def*)
../../trunk/gcc/domwalk.c:312
>From gcc-bugs-return-641783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:00:43 2019
Return-Path: <gcc-bugs-return-641783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92283 invoked by alias); 25 Apr 2019 08:00:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92181 invoked by uid 48); 25 Apr 2019 08:00:34 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90242] New: [UBSAN]: in vn_reference_compute_hash
Date: Thu, 25 Apr 2019 08:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02639.txt.bz2
Content-length: 1392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90242
Bug ID: 90242
Summary: [UBSAN]: in vn_reference_compute_hash
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Following on from PR 85164, where I tried a UBSAN version
of gcc trunk over the testsuite, for file
./c-c++-common/Warray-bounds.c, with flags -g -O3 -march=native -Wall, I got
../../trunk/gcc/poly-int.h:715:21: runtime error: signed integer overflow:
9223372036854775804 + 4 cannot be represented in type 'long int'
#0 0x318ecb2 in poly_int<1u, long>& poly_int<1u,
long>::operator+=<long>(poly_int_pod<1u, long> const&)
../../trunk/gcc/poly-int.h:715
#1 0x318ecb2 in vn_reference_compute_hash
../../trunk/gcc/tree-ssa-sccvn.c:657
#2 0x31b26b5 in vn_reference_lookup(tree_node*, tree_node*, vn_lookup_kind,
vn_reference_s**, bool) ../../trunk/gcc/tree-ssa-sccvn.c:2714
#3 0x31ea070 in visit_reference_op_load
../../trunk/gcc/tree-ssa-sccvn.c:4091
#4 0x31ea070 in visit_stmt ../../trunk/gcc/tree-ssa-sccvn.c:4509
#5 0x31efef6 in process_bb ../../trunk/gcc/tree-ssa-sccvn.c:6130
#6 0x31f9fb0 in do_rpo_vn ../../trunk/gcc/tree-ssa-sccvn.c:6625
>From gcc-bugs-return-641784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:02:31 2019
Return-Path: <gcc-bugs-return-641784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93756 invoked by alias); 25 Apr 2019 08:02: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 93688 invoked by uid 48); 25 Apr 2019 08:02:27 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 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: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90240-4-STZz0gAYsm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02640.txt.bz2
Content-length: 1237
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
--- Comment #2 from bin cheng <amker at gcc dot gnu.org> ---
Also, cost in inner loop is scaled by big number:
Scaling cost based on bb prob by 10000.00: 0 (scratch: 0) -> 0 (10000/1)
Scaling cost based on bb prob by 10000.00: 32 (scratch: 0) -> 320000 (10000/1)
Scaling cost based on bb prob by 10000.00: 41 (scratch: 0) -> 410000 (10000/1)
Scaling cost based on bb prob by 10000.00: 21 (scratch: 0) -> 210000 (10000/1)
Scaling cost based on bb prob by 10000.00: 45 (scratch: 0) -> 450000 (10000/1)
Scaling cost based on bb prob by 10000.00: 21 (scratch: 0) -> 210000 (10000/1)
Scaling cost based on bb prob by 10000.00: 17 (scratch: 0) -> 170000 (10000/1)
Resulting:
Group 19:
cand cost compl. inv.expr. inv.vars
1 410000 0 NIL; 1, 4
2 210000 0 NIL; 4
3 450000 0 NIL; 1, 4
4 210000 0 NIL; 4
5 170000 0 35; NIL;
30 0 0 NIL; NIL;
67 320000 0 NIL; 1, 4
Given we have 70 groups of iv_use, this easily overflow infinite_cost which is
10,000,000.
One thing unclear is the overflow happens in the middle of cost candidate
choosing algorithm.
>From gcc-bugs-return-641785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:10:00 2019
Return-Path: <gcc-bugs-return-641785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118046 invoked by alias); 25 Apr 2019 08:10: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 117997 invoked by uid 48); 25 Apr 2019 08:09:56 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/90229] Interaction among -Wl,--as-needed and LTO results in an undefined symbol
Date: Thu, 25 Apr 2019 08:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-90229-4-JJhpms8BnY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02641.txt.bz2
Content-length: 2204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90229
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #4)
> I can't reproduce it with binutils master branch and GCC 9:
>
> [hjl@gnu-cfl-1 pr90229]$ cat x.ii
> extern int FLAGS_verbose;
> extern "C" void pthread_create(void);
>
> void a(const char *b...) {
> if (FLAGS_verbose) {
> __builtin_va_list ap;
> __builtin_va_start(ap, b);
> }
> }
> void a() { pthread_create(); }
> int main() { a(""); return 0; }
> [hjl@gnu-cfl-1 pr90229]$ cat lib.ii
> int FLAGS_verbose;
> [hjl@gnu-cfl-1 pr90229]$ make
> /export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
> -B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./
> -g -flto -c -o x.o x.ii
> /export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
> -B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./
> -g -c -o lib.o lib.ii
> /export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
> -B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./
> -shared -g -o libx.so lib.o
> /export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/xgcc
> -B/export/build/gnu/tools-build/gcc-wip-debug/build-x86_64-linux/gcc/ -B./
> -pthread -g -o x x.o libx.so -Wl,--as-needed
> [hjl@gnu-cfl-1 pr90229]$
I can confirm that with current trunk of both GCC and bintuils. You used a bit
different
build steps:
1) one needs g++ for: -shared -g -o libx.so lib.o
2) you forgot to add -O and -flto to last command line
So please use following steps:
bash -x ./todo
+ gcc -g -c -o lib.o lib.ii
+ g++ -shared -g -o libx.so lib.o
+ gcc -g -flto -c -o x.o x.ii -O
+ gcc -flto -O -pthread -g -o x x.ii libx.so -Wl,--as-needed
/home/marxin/bin/binutils/bin/ld: /home/marxin/bin/gcc/lib64//libstdc++.so.6:
undefined reference to `pthread_create'
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-641786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:12:44 2019
Return-Path: <gcc-bugs-return-641786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60722 invoked by alias); 25 Apr 2019 08:12:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55982 invoked by uid 48); 25 Apr 2019 08:12:41 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90243] New: diagnostic notes that belong to a suppressed error about an uninitialized variable in a constexpr function are still shown
Date: Thu, 25 Apr 2019 08: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
Message-ID: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02642.txt.bz2
Content-length: 1334
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90243
Bug ID: 90243
Summary: diagnostic notes that belong to a suppressed error
about an uninitialized variable in a constexpr
function are still shown
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: ---
Test case (https://godbolt.org/z/34KB20):
struct Z {
int y;
};
template <class T>
constexpr Z f(const T *data) {
Z z;
__builtin_memcpy(&z, data, sizeof(z));
return z;
}
constexpr Z g(const char *data) { return f(data); }
This prints:
<source>: In instantiation of 'constexpr Z f(const T*) [with T = char]':
<source>:12:48: required from here
<source>:1:8: note: 'struct Z' has no user-provided default constructor
<source>:2:7: note: and the implicitly-defined constructor does not initialize
'int Z::y'
If f is not a template, `Z z;` is an error and the notes explain the error. But
when f is a template the error is suppressed (seems correct). However the notes
that explain the error are still shown. Whether the notes are shown should use
the same condition as the error.
>From gcc-bugs-return-641787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:16:21 2019
Return-Path: <gcc-bugs-return-641787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117298 invoked by alias); 25 Apr 2019 08:16:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117281 invoked by uid 48); 25 Apr 2019 08:16:18 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90243] diagnostic notes that belong to a suppressed error about an uninitialized variable in a constexpr function are still shown
Date: Thu, 25 Apr 2019 08:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-90243-4-wK1YjLlWv8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02643.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90243
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-25
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-641788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:17:26 2019
Return-Path: <gcc-bugs-return-641788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119821 invoked by alias); 25 Apr 2019 08:17:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119777 invoked by uid 48); 25 Apr 2019 08:17:23 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9 Regression] C code is optimized worse than C++
Date: Thu, 25 Apr 2019 08:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-bPs6DFwzrf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02644.txt.bz2
Content-length: 801
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #7 from Hongtao.liu <crazylht at gmail dot com> ---
Yes, C++ with NRV optization, so the alignment of <retval>(res) is 4.
and the alignment of res is 16 in C.
g++/test.i.158t.vect:
../test.i:8:23: note: recording new base alignment for &<retval>
alignment: 4
misalignment: 0
gcc/test.i.158t.vect:
../test.i:8:5: note: recording new base alignment for &res
alignment: 16
misalignment: 0
When alignment of res is 16, that triggers loop peeling of vectorization.
refer to:
/* Function vect_enhance_data_refs_alignment
This pass will use loop versioning and loop peeling in order to enhance
the alignment of data references in the loop.
.........
*/
That's why there are more than 150 lines of assemble.
>From gcc-bugs-return-641789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:21:43 2019
Return-Path: <gcc-bugs-return-641789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 797 invoked by alias); 25 Apr 2019 08:21:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 743 invoked by uid 48); 25 Apr 2019 08:21:40 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9 Regression] C code is optimized worse than C++
Date: Thu, 25 Apr 2019 08:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-4QXrqsfnLu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02645.txt.bz2
Content-length: 243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #8 from Hongtao.liu <crazylht at gmail dot com> ---
Cost_model for Function vect_enhance_data_refs_alignment are quite tunable.
More benchmarks are needed if we want to do so.
>From gcc-bugs-return-641791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:32:50 2019
Return-Path: <gcc-bugs-return-641791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35766 invoked by alias); 25 Apr 2019 08: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 35671 invoked by uid 48); 25 Apr 2019 08:32:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86932] [8 Regression] Empty non-type template parameter pack not considered for SFINAE.
Date: Thu, 25 Apr 2019 08:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: accepts-invalid
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: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86932-4-efwl7YBi2c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86932-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86932-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02647.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86932
Bug 86932 depends on bug 90227, which changed state.
Bug 90227 Summary: [9 Regression] trunk rejects polymake since r269965
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90227
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-641790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:32:50 2019
Return-Path: <gcc-bugs-return-641790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35711 invoked by alias); 25 Apr 2019 08:32: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 35639 invoked by uid 48); 25 Apr 2019 08:32:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90227] [9 Regression] trunk rejects polymake since r269965
Date: Thu, 25 Apr 2019 08:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason 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-90227-4-TOvIKo5zLD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90227-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90227-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02646.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90227
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed, thanks.
>From gcc-bugs-return-641793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:34:50 2019
Return-Path: <gcc-bugs-return-641793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39555 invoked by alias); 25 Apr 2019 08: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 39472 invoked by uid 48); 25 Apr 2019 08:34:47 -0000
From: "jakub 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: Thu, 25 Apr 2019 08: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: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-87763-4-WL6skCDCcz@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-04/txt/msg02649.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P2
--- Comment #55 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This PR had various fixes applied already and the remaining issues don't
warrant a release blocker, so downgrading this to P2.
>From gcc-bugs-return-641792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:34:42 2019
Return-Path: <gcc-bugs-return-641792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38804 invoked by alias); 25 Apr 2019 08:34:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38754 invoked by uid 48); 25 Apr 2019 08:34:38 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/47618] Collecting multiple profiles and using all for PGO
Date: Thu, 25 Apr 2019 08:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
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-47618-4-owHiWt4e0B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47618-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47618-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02648.txt.bz2
Content-length: 1369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47618
--- Comment #24 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to qinzhao from comment #23)
> (In reply to Andrew Pinski from comment #7)
> > Created attachment 27869 [details]
> > Patch for adding merge-gcda
> >
> > here is the patch which adds merge-gcda . I don't add any testcases as it
> > is currently designed only for how Cavium's Simple-exec works in that each
> > core writes out its own gcda file.
>
> I recently found this bug due to a similar problem. looks like that there
> are two parts of work for this problem:
>
> 1. GCC's new feature to guarantee that all pre-merged files are saved with
> different names for different instances of the same process.
> 2. a merge tool to merge all the gcda files afterwards.
>
> from my understanding, the patch for the above 1 has been committed into
> GCC9.
Yes.
> How about the patch for the above 2? has it been committed?
It has been there for a while, please take a look at:
$ gcov-tool merge --help
merge: unrecognized option '--help'
Merge subcomand usage: merge [options] <dir1> <dir2> Merge coverage
file contents
-o, --output <dir> Output directory
-v, --verbose Verbose mode
-w, --weight <w1,w2> Set weights (float point values)
>From gcc-bugs-return-641794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:35:10 2019
Return-Path: <gcc-bugs-return-641794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40396 invoked by alias); 25 Apr 2019 08: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 40304 invoked by uid 48); 25 Apr 2019 08:35:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87871] [9 Regression] testcases fail after r265398 on arm
Date: Thu, 25 Apr 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: rtl-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: P2
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-87871-4-KR9mX9zRvI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02650.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87871
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P2
--- Comment #60 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This PR had various fixes applied already and the remaining issues don't
warrant a release blocker, so downgrading this to P2.
>From gcc-bugs-return-641795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:36:52 2019
Return-Path: <gcc-bugs-return-641795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42036 invoked by alias); 25 Apr 2019 08:36: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 42001 invoked by uid 48); 25 Apr 2019 08:36:49 -0000
From: "tbaeder at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90219] Wrong source location for "cannot convert to a pointer type" warning
Date: Thu, 25 Apr 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: c
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tbaeder at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90219-4-jRXYGv3Y1Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90219-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90219-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02651.txt.bz2
Content-length: 308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90219
--- Comment #2 from Timm Bäder <tbaeder at redhat dot com> ---
(In reply to Jonathan Wakely from comment #1)
> Well if you took the address you wouldn't need to cast it to (float*)
Sure, this was just a dumbed-down version of the original code.
>From gcc-bugs-return-641796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:37:46 2019
Return-Path: <gcc-bugs-return-641796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79505 invoked by alias); 25 Apr 2019 08:37: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 77778 invoked by uid 48); 25 Apr 2019 08:37:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 2019 08:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-90240-4-tysarMILT6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02652.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Graphite, so IMHO not a release blocker.
>From gcc-bugs-return-641797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:38:46 2019
Return-Path: <gcc-bugs-return-641797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80844 invoked by alias); 25 Apr 2019 08:38: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 80790 invoked by uid 48); 25 Apr 2019 08:38:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90172] [8/9 Regression] ICE: Segmentation fault (in contains_struct_check)
Date: Thu, 25 Apr 2019 08:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, 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: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority short_desc
Message-ID: <bug-90172-4-5py5hzLhWQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90172-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90172-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02653.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90172
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Summary|[9 Regression] ICE: |[8/9 Regression] ICE:
|Segmentation fault (in |Segmentation fault (in
|contains_struct_check) |contains_struct_check)
>From gcc-bugs-return-641798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:41:29 2019
Return-Path: <gcc-bugs-return-641798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112955 invoked by alias); 25 Apr 2019 08:41: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 112925 invoked by uid 48); 25 Apr 2019 08:41:25 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90235] Unnecessary save and restore frame pointer with AVX/AVX512 pseudo registers
Date: Thu, 25 Apr 2019 08:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-90235-4-6VNC3BYbUk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90235-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90235-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02654.txt.bz2
Content-length: 3834
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90235
--- Comment #1 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #0)
> From PR 90202:
>
> [hjl@gnu-cfl-1 pr90202]$ cat x.ii
> struct v {
> int val[16];
> };
>
> struct v test(struct v a, struct v b) {
> struct v res;
>
> for (int i = 0; i < 16; i++)
> res.val[i] = a.val[i] + b.val[i];
>
> return res;
> }
> [hjl@gnu-cfl-1 pr90202]$ make CC=gcc
> gcc -O3 -march=skylake -S x.ii
> [hjl@gnu-cfl-1 pr90202]$ cat x.s
> .file "x.ii"
> .text
> .p2align 4,,15
> .globl _Z4test1vS_
> .type _Z4test1vS_, @function
> _Z4test1vS_:
> .LFB0:
> .cfi_startproc
> pushq %rbp
> .cfi_def_cfa_offset 16
> .cfi_offset 6, -16
> movq %rdi, %rax
> movq %rsp, %rbp
> .cfi_def_cfa_register 6
> vmovdqu 16(%rbp), %ymm1
> vmovdqu 48(%rbp), %ymm2
> vpaddd 80(%rbp), %ymm1, %ymm0
> vmovdqu %ymm0, (%rdi)
> vpaddd 112(%rbp), %ymm2, %ymm0
> vmovdqu %ymm0, 32(%rdi)
> vzeroupper
> popq %rbp
> .cfi_def_cfa 7, 8
> ret
> .cfi_endproc
>
> Since there is
>
> rtx
> gen_reg_rtx (machine_mode mode)
> {
> rtx val;
> unsigned int align = GET_MODE_ALIGNMENT (mode);
>
> gcc_assert (can_create_pseudo_p ());
>
> /* If a virtual register with bigger mode alignment is generated,
> increase stack alignment estimation because it might be spilled
> to stack later. */
> if (SUPPORTS_STACK_ALIGNMENT
> && crtl->stack_alignment_estimated < align
> && !crtl->stack_realign_processed)
> {
> unsigned int min_align = MINIMUM_ALIGNMENT (NULL, mode, align);
> if (crtl->stack_alignment_estimated < min_align)
> crtl->stack_alignment_estimated = min_align;
> }
>
> and IRA has
>
> frame_pointer_needed
> = (! flag_omit_frame_pointer
> || (cfun->calls_alloca && EXIT_IGNORE_STACK)
> /* We need the frame pointer to catch stack overflow exceptions if
> the stack pointer is moving (as for the alloca case just above).
> */
> || (STACK_CHECK_MOVING_SP
> && flag_stack_check
> && flag_exceptions
> && cfun->can_throw_non_call_exceptions)
> || crtl->accesses_prior_frames
> || (SUPPORTS_STACK_ALIGNMENT && crtl->stack_realign_needed)
> || targetm.frame_pointer_required ());
>
> generate AVX/AVX512 pseudo registers via gen_reg_rtx will mark frame
> pointer as needed. Stack realignment is needed to
>
> 1. Align the outgoing stack.
> 2. Support aligned spill of AVX/AVX512 registers.
>
> But we won't know if spill is needed before RA. As the result, we
> save and restore frame pointer even if not needed. Since
>
> (define_insn "mov<mode>_internal"
> [(set (match_operand:VMOVE 0 "nonimmediate_operand"
> "=v,v ,v ,m")
> (match_operand:VMOVE 1 "nonimmediate_or_sse_const_operand"
> " C,BC,vm,v"))]
> "TARGET_SSE
> && (register_operand (operands[0], <MODE>mode)
> || register_operand (operands[1], <MODE>mode))"
>
> now supports both aligned and unaligned load/store of AVX/AVX512
> registers, we can change gen_reg_rtx to
>
> /* If a virtual register with bigger mode alignment is generated,
> increase stack alignment estimation because it might be spilled
> to stack later. */
> if (SUPPORTS_STACK_ALIGNMENT
> && !SUPPORTS_MISALIGNED_SPILL
> && crtl->stack_alignment_estimated < align
> && !crtl->stack_realign_processed)
> {
> unsigned int min_align = MINIMUM_ALIGNMENT (NULL, mode, align);
> if (crtl->stack_alignment_estimated < min_align)
> crtl->stack_alignment_estimated = min_align;
> }
Would this generate more unaligned_loads/stores, and does harm to performance?
>From gcc-bugs-return-641799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:43:14 2019
Return-Path: <gcc-bugs-return-641799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37626 invoked by alias); 25 Apr 2019 08: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 36744 invoked by uid 48); 25 Apr 2019 08:43:11 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 2019 08:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-89929-4-lcyyYRkBwR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02655.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|marxin at gcc dot gnu.org |hjl.tools at gmail dot com
--- Comment #21 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm assigning that to H.J. as he provided the final version of the patch.
>From gcc-bugs-return-641800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:48:47 2019
Return-Path: <gcc-bugs-return-641800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109021 invoked by alias); 25 Apr 2019 08:48: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 108944 invoked by uid 48); 25 Apr 2019 08:48:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/89819] [9 Regression] std::variant operators regressed since GCC 8.3
Date: Thu, 25 Apr 2019 08:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-89819-4-PfkPavCy0X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02656.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89819
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
Target Milestone|9.0 |10.0
Ever confirmed|0 |1
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Confirmed, but nothing will happen for GCC 9.1
>From gcc-bugs-return-641801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:50:40 2019
Return-Path: <gcc-bugs-return-641801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111594 invoked by alias); 25 Apr 2019 08: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 111570 invoked by uid 48); 25 Apr 2019 08:50:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/89760] [9 Regression] libstdc++ experimental testsuite failures
Date: Thu, 25 Apr 2019 08:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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: keywords bug_status assigned_to
Message-ID: <bug-89760-4-lpAdl2GMOP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02657.txt.bz2
Content-length: 566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89760
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|rejects-valid |
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This isn't rejects-valid, the code is fine, the tests are the problem.
>From gcc-bugs-return-641802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:54:19 2019
Return-Path: <gcc-bugs-return-641802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115600 invoked by alias); 25 Apr 2019 08: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 115559 invoked by uid 48); 25 Apr 2019 08:54:16 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90241] [UBSAN]: in ao_ref_init_from_ptr_and_size
Date: Thu, 25 Apr 2019 08:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.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-90241-4-FXjjU05BMZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90241-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90241-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02658.txt.bz2
Content-length: 141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90241
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
Flag -O2 required.
>From gcc-bugs-return-641803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:55:04 2019
Return-Path: <gcc-bugs-return-641803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116845 invoked by alias); 25 Apr 2019 08:55:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116587 invoked by uid 48); 25 Apr 2019 08:55:01 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/89819] [9 Regression] std::variant operators regressed since GCC 8.3
Date: Thu, 25 Apr 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: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-89819-4-KmXuFk2XLv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02659.txt.bz2
Content-length: 1257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89819
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|10.0 |9.0
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Ville corrected me, this was already fixed by r270056
Use single-visitation in variant assignment and swap and relops.
Also use indices instead of types when checking whether
variants hold the same thing.
* include/std/variant (__do_visit): Add a template parameter
for index visitation, invoke with indices if index visitation
is used.
(__variant_idx_cookie): New.
(__visit_with_index): Likewise.
(_Copy_assign_base::operator=): Do single-visitation with
an index visitor.
(_Move_assign_base::operator=): Likewise.
(_Extra_visit_slot_needed): Adjust.
(__visit_invoke): Call with indices if it's an index visitor.
(relops): Do single-visitation with an index visitor.
(swap): Likewise.
(__visitor_result_type): New.
>From gcc-bugs-return-641804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:55:46 2019
Return-Path: <gcc-bugs-return-641804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117759 invoked by alias); 25 Apr 2019 08:55:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117734 invoked by uid 48); 25 Apr 2019 08:55:42 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90242] [UBSAN]: in vn_reference_compute_hash
Date: Thu, 25 Apr 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: 9.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-90242-4-b4Mn8HpO51@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02660.txt.bz2
Content-length: 146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90242
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
Only flag -O2 required.
>From gcc-bugs-return-641805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 08:59:40 2019
Return-Path: <gcc-bugs-return-641805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122799 invoked by alias); 25 Apr 2019 08:59: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 122732 invoked by uid 55); 25 Apr 2019 08:59:35 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83118] [7/8/9 Regression] Bad intrinsic assignment of class(*) array component of derived type
Date: Thu, 25 Apr 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: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83118-4-0bKZryMBaH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02661.txt.bz2
Content-length: 692
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118
--- Comment #19 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #18 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> Uni-Bielefeld.DE> ---
[...]
> I've just applied the patch to trunk, rebuilt f951 on
> sparc-sun-solaris2.11 and tested unlimited_polymorphic_30.f03: the test
> now PASSes for both 32 and 64-bit.
>
> I'll include the patch in tonight's bootstrap and let you know if there
> are any problems elsewhere.
There weren't any in last night's sparc-sun-solaris2.11 bootstrap: both
32 and 64-bit unlimited_polymorphic_30.f03 failures are gone.
Thanks.
Rainer
>From gcc-bugs-return-641806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:00:39 2019
Return-Path: <gcc-bugs-return-641806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124507 invoked by alias); 25 Apr 2019 09:00:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124365 invoked by uid 48); 25 Apr 2019 09:00:32 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 2019 09:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90240-4-eoPOCGKSzq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02662.txt.bz2
Content-length: 1373
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
--- Comment #4 from bin cheng <amker at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> Graphite, so IMHO not a release blocker.
but the issue is critical, it could happen with general optimization level for
loop nest with huge scaling factor.
So, find_optimal_iv_set_1 first chooses a candidate set, then makes different
tries to do cost descent by modifying the candidate set. The facts are:
1) algorithm uses a global variable of following structure and keeps track of
cost in place during computation.
struct iv_ca {
//...
comp_cost cand_use_cost;
//...
comp_cost cost;
};
2) algorithm is heuristic, so it's possible to reach an intermediate state
with higher cost.
3) as in previous comment, loop nest with huge scaling factor can easily
result in infinite_cost.
4) once the global variable of iv_ca.{cand_use_cost, cost} reaches
infinite_cost, ICE is the best thing could happen.
We could replace gcc_assert with algorithm failure then give up ivopts, but
IMHO that would miss quite lot of optimizations.
The conclusion, candidate choosing algorithm doesn't work well with
infinite_cost.
I Don't know how to fix this trivially. For now, even restricting scaling
factor is a practical change now. Will give it a try.
>From gcc-bugs-return-641807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:08:35 2019
Return-Path: <gcc-bugs-return-641807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16304 invoked by alias); 25 Apr 2019 09:08: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 12296 invoked by uid 48); 25 Apr 2019 09:08:32 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90244] New: [UBSAN]: in get_object_alignment_2
Date: Thu, 25 Apr 2019 09:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90244-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02663.txt.bz2
Content-length: 1632
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90244
Bug ID: 90244
Summary: [UBSAN]: in get_object_alignment_2
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
Following on from PR 85164, I tried out a UBSAN version of
gcc trunk with test suite file gcc.dg/Warray-bounds-22.c
and flag -O2 and got this:
../../trunk/gcc/poly-int.h:1095:5: runtime error: signed integer overflow:
92233
72036854775807 * 8 cannot be represented in type 'long int'
#0 0xf85e20 in poly_int<1u, poly_result<long, if_nonpoly<int, int,
poly_int_
traits<int>::is_poly>::type, poly_coeff_pair_traits<long, if_nonpoly<int, int,
p
oly_int_traits<int>::is_poly>::type>::result_kind>::type> operator*<1u, long,
in
t>(poly_int_pod<1u, long> const&, int const&) ../../trunk/gcc/poly-int.h:1095
#1 0xf85e20 in get_object_alignment_2 ../../trunk/gcc/builtins.c:344
#2 0xf86d9d in get_object_alignment_1(tree_node*, unsigned int*, unsigned
lo
ng*) ../../trunk/gcc/builtins.c:394
#3 0xf86d9d in get_object_alignment(tree_node*)
../../trunk/gcc/builtins.c:4
05
#4 0x1690d75 in expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expan
d_modifier, rtx_def**, bool) ../../trunk/gcc/expr.c:10343
#5 0x16939b8 in expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expan
d_modifier, rtx_def**, bool) ../../trunk/gcc/expr.c:9947
#6 0x16ecf5c in expand_expr ../../trunk/gcc/expr.h:279
>From gcc-bugs-return-641809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:13:22 2019
Return-Path: <gcc-bugs-return-641809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53338 invoked by alias); 25 Apr 2019 09:13: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 53198 invoked by uid 48); 25 Apr 2019 09:13:19 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/47093] [meta-bug]: broken configurations
Date: Thu, 25 Apr 2019 09:13: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: 4.6.0
X-Bugzilla-Keywords: build, meta-bug
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_status resolution
Message-ID: <bug-47093-4-cGFKV6xxzm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47093-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47093-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02665.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47093
Bug 47093 depends on bug 90045, which changed state.
Bug 90045 Summary: [9 Regression] fails to build a rx-elf cross toolchain with C++ enabled
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90045
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-641808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:13:22 2019
Return-Path: <gcc-bugs-return-641808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53252 invoked by alias); 25 Apr 2019 09:13: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 53158 invoked by uid 48); 25 Apr 2019 09:13:19 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90045] [9 Regression] fails to build a rx-elf cross toolchain with C++ enabled
Date: Thu, 25 Apr 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: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
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-90045-4-BKbrvxZt4e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90045-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90045-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02664.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90045
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Martin Liška <marxin at gcc dot gnu.org> ---
I can confirm it works now.
>From gcc-bugs-return-641810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:18:01 2019
Return-Path: <gcc-bugs-return-641810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101377 invoked by alias); 25 Apr 2019 09:18:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92383 invoked by uid 48); 25 Apr 2019 09:17:50 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85164] poly-int.h:845:5: runtime error: signed integer overflow
Date: Thu, 25 Apr 2019 09:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85164-4-m5Iwh1rCJi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85164-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85164-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02666.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85164
--- Comment #21 from David Binderman <dcb314 at hotmail dot com> ---
(In reply to rsandifo@gcc.gnu.org from comment #20)
> Thanks for the testing.
You are welcome.
> Could you open new PRs for the new backtraces?
Done. Most of them were already mentioned in bugzilla, but for
the rest, I have raised 90241, 90242 and 90244.
> But whether the operation triggers
> UB is usually determined by the operation being done (i.e. by the
> caller) rather than the way poly-int.h implements it.
Thanks for the explanation. It is a lot clearer now.
>From gcc-bugs-return-641811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:20:39 2019
Return-Path: <gcc-bugs-return-641811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38734 invoked by alias); 25 Apr 2019 09:20:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38702 invoked by uid 48); 25 Apr 2019 09:20:35 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90245] New: A data race with a segmentation fault handler
Date: Thu, 25 Apr 2019 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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 attachments.created
Message-ID: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02667.txt.bz2
Content-length: 1773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90245
Bug ID: 90245
Summary: A data race with a segmentation fault handler
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
Target Milestone: ---
Created attachment 46241
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46241&action=edit
test-case
It's follow up of:
https://bugzilla.opensuse.org/show_bug.cgi?id=1133245
For the attached conftest we end up with:
56 /* Check that the handler was called only once. */
57 if (handler_called != 1) <--- problematic condition
58 {
59 __builtin_printf ("handler_called == 1\n");
60 exit (1);
61 }
62 /* Test passed! */
63 return 0;
64 }
$ gcc conftest.c -O2 -S -o/dev/stdout
main:
...
movq page(%rip), %rax
movl $42, 1656(%rax) <--- segfault happens here
cmpl $1, handler_called(%rip) <- comparison after that
jne .L16
While using LTO:
Disassembly of section .text:
0000000000401090 <main>:
...
401118: 83 3d 41 2f 00 00 01 cmpl $0x1,0x2f41(%rip) #
404060 <handler_called>
40111f: c7 83 78 06 00 00 2a movl $0x2a,0x678(%rbx)
401126: 00 00 00
401129: 75 15 jne 401140 <main+0xb0>
So here we first do 'handler_called != 1' comparison and next instruction
triggers the segfault handler. I tried:
--param allow-store-data-races=0, but it does not help.
Solution is to add a barrier I guess. I guess the transformation is valid?
>From gcc-bugs-return-641812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:21:56 2019
Return-Path: <gcc-bugs-return-641812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40631 invoked by alias); 25 Apr 2019 09: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 39852 invoked by uid 48); 25 Apr 2019 09:21:53 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90245] A data race with a segmentation fault handler
Date: Thu, 25 Apr 2019 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: cf_reconfirmed_on cc
Message-ID: <bug-90245-4-u3cNgLkyyB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02668.txt.bz2
Content-length: 806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90245
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2019-4-25
CC| |rguenth at gcc dot gnu.org
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
More clarification:
54 /* The second write access should not invoke the handler. */
55 crasher (page);
56 /* Check that the handler was called only once. */
57 if (handler_called != 1)
58 {
59 __builtin_printf ("handler_called == 1\n");
60 exit (1);
61 }
The segfault happens at line 55.
>From gcc-bugs-return-641813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 09:24:22 2019
Return-Path: <gcc-bugs-return-641813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45192 invoked by alias); 25 Apr 2019 09:24: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 45019 invoked by uid 48); 25 Apr 2019 09:24:02 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9 Regression] C code is optimized worse than C++
Date: Thu, 25 Apr 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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-8m1l01oAiN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02669.txt.bz2
Content-length: 866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
Also what's better between aligned load/store of smaller size VS unaligned
load/store of bigger size?
aligned load/store of smaller size:
movq %rdx, (%rdi)
movq -56(%rsp), %rdx
movq %rdx, 8(%rdi)
movq -48(%rsp), %rdx
movq %rdx, 16(%rdi)
movq -40(%rsp), %rdx
movq %rdx, 24(%rdi)
vmovq %xmm0, 32(%rax)
movq -24(%rsp), %rdx
movq %rdx, 40(%rdi)
movq -16(%rsp), %rdx
movq %rdx, 48(%rdi)
movq -8(%rsp), %rdx
movq %rdx, 56(%rdi)
unaligned load/store of bigger size:
vmovups %xmm2, (%rdi)
vmovups %xmm3, 16(%rdi)
vmovups %xmm4, 32(%rdi)
vmovups %xmm5, 48(%rdi)
>From gcc-bugs-return-641814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 10:09:59 2019
Return-Path: <gcc-bugs-return-641814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115327 invoked by alias); 25 Apr 2019 10:09: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 115256 invoked by uid 48); 25 Apr 2019 10:09:54 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90245] A data race with a segmentation fault handler
Date: Thu, 25 Apr 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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90245-4-cxf76hJQv2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02670.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90245
Florian Weimer <fw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |fw at gcc dot gnu.org
--- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> ---
I think that handler_called should be volatile sig_atomic_t. Or you would have
to add signal fences.
>From gcc-bugs-return-641815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 10:16:09 2019
Return-Path: <gcc-bugs-return-641815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21482 invoked by alias); 25 Apr 2019 10:15:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21255 invoked by uid 48); 25 Apr 2019 10:15:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] New: std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 2019 10:15: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02671.txt.bz2
Content-length: 1833
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
Bug ID: 90246
Summary: std::bad_variant_access messages are not useful
Product: gcc
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
Every exception of type bad_variant_access has the same unhelpful text:
"Unexpected index"
Seeing this in a log file tells you almost nothing. It would be much better to
say:
"std::visit<R> called on valueless variant"
or "std::get<1> called on variant with index 2"
This requires an ABI change, because bad_variant_access currently just stores a
const char* (which is assumed to point to a string with static storage
duration, e.g. a literal).
Something like this would allow us to store a (possibly dynamically allocated)
string in the exception object, so we can provide formatted strings with
additional information:
@@ -1200,13 +1278,21 @@ namespace __variant
{
public:
bad_variant_access() noexcept : _M_reason("Unknown reason") { }
+
const char* what() const noexcept override
- { return _M_reason; }
+ { return _M_reason.get(); }
private:
- bad_variant_access(const char* __reason) : _M_reason(__reason) { }
+ // Must only be called with a string literal
+ bad_variant_access(const char* __reason, nullptr_t)
+ : _M_reason(__reason, [](const char*){})
+ { }
+
+ bad_variant_access(const char* __reason)
+ : _M_reason(std::strdup(__reason), [](const char* __s) { std::free(__s);
})
+ { }
- const char* _M_reason;
+ __shared_ptr<const char[]> _M_reason;
friend void __throw_bad_variant_access(const char* __what);
};
>From gcc-bugs-return-641816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 10:16:14 2019
Return-Path: <gcc-bugs-return-641816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22144 invoked by alias); 25 Apr 2019 10:16:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21581 invoked by uid 48); 25 Apr 2019 10:16:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 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: 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: bug_status cf_reconfirmed_on version everconfirmed
Message-ID: <bug-90246-4-bgiSjD1aDz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02672.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
Version|8.3.1 |9.0
Ever confirmed|0 |1
>From gcc-bugs-return-641817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 10:35:59 2019
Return-Path: <gcc-bugs-return-641817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60320 invoked by alias); 25 Apr 2019 10:35:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60282 invoked by uid 48); 25 Apr 2019 10:35:50 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90247] New: Reconsider OpenACC implicit data attributes for pointers
Date: Thu, 25 Apr 2019 10:35: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: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90247-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02673.txt.bz2
Content-length: 1630
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90247
Bug ID: 90247
Summary: Reconsider OpenACC implicit data attributes for
pointers
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: openacc
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: tschwinge at gcc dot gnu.org
Target Milestone: ---
We've been reading the OpenACC specification such that a pointer variable is a
scalar (not an array), and thus gets an implicit 'firstprivate' clause (not
some kind of 'copy' clause). This is not what users appear to expect:
int *p = (int *) malloc([...})
#pragma acc enter data create (p[0:100])
#pragma acc parallel loop // implicit 'firstprivate(p)'
for ([i])
p[i] = [...]
#pragma acc enter data copyout (p[0:100])
The implicit 'firstprivate' clause will not translate the host 'p' to the
corresponding device 'p' that has been 'create'd above, but will copy the host
pointer value untranslated, leading to run-time failure upon dereferencing the
host 'p' on the device. What users instead would like is what OpenMP calls
"zero-length array section" mapping.
There is discussion that the OpenACC specification is moving into that
direction.
A patch has been proposed,
<http://mid.mail-archive.com/e4c72dcf-95b6-b919-64c6-a3e8c22d74df@codesourcery.com>,
but needs work.
Then, there are similar considerations to be made for other such data mapping
cases/constructs (not listed here now).
>From gcc-bugs-return-641818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 10:39:20 2019
Return-Path: <gcc-bugs-return-641818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103689 invoked by alias); 25 Apr 2019 10:39: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 103161 invoked by uid 48); 25 Apr 2019 10:39:16 -0000
From: "tschwinge at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90247] Reconsider OpenACC implicit data attributes for pointers
Date: Thu, 25 Apr 2019 10:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tschwinge 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 cf_reconfirmed_on everconfirmed
Message-ID: <bug-90247-4-YCnE8ch9Ol@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90247-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90247-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02674.txt.bz2
Content-length: 592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90247
Thomas Schwinge <tschwinge at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |SUSPENDED
Last reconfirmed| |2019-04-25
Ever confirmed|0 |1
--- Comment #1 from Thomas Schwinge <tschwinge at gcc dot gnu.org> ---
Suspended until we get clarification about the (at least future) intention of
the OpenACC specification.
>From gcc-bugs-return-641819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 10:42:42 2019
Return-Path: <gcc-bugs-return-641819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107476 invoked by alias); 25 Apr 2019 10:42: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 106464 invoked by uid 48); 25 Apr 2019 10:42:38 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90245] A data race with a segmentation fault handler
Date: Thu, 25 Apr 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: 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: 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-90245-4-FRKUgBNPVI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90245-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02675.txt.bz2
Content-length: 596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90245
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #2)
> I think that handler_called should be volatile sig_atomic_t. Or you would
> have to add signal fences.
Thanks Florian.
>From gcc-bugs-return-641820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:03:51 2019
Return-Path: <gcc-bugs-return-641820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113307 invoked by alias); 25 Apr 2019 11:03:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113237 invoked by uid 48); 25 Apr 2019 11:03:46 -0000
From: "kau at zurich dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90248] New: larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 2019 11:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kau at zurich dot ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02676.txt.bz2
Content-length: 9494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
Bug ID: 90248
Summary: larger than 0 compare fails with -ffinite-math-only
-funsafe-math-optimizations
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kau at zurich dot ibm.com
Target Milestone: ---
Created attachment 46242
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46242&action=edit
preprocessed minimal example file
Hello,
the following code produces unexpected/different results using gcc 8.2.1 when
compared to gcc 7.3.1
test.cc:
#include <iostream>
int main() {
float a = 0;
std::cout << a << std::endl;
a = (a > 0) ? 1.0 : -1.0;
std::cout << a << std::endl;
return 0;
}
I would expect this code to print
0
-1
with "gcc version 7.3.1 20180130 (Red Hat 7.3.1-2) (GCC)" it does.
with "gcc version 8.2.1 20181215 (Red Hat 8.2.1-6) (GCC)" it prints
0
1
This behavior depends on the combination of two compiler flags. If either one
is missing, the code behaves as expected.
# g++ -Wall -Wextra -ffinite-math-only -funsafe-math-optimizations test.cc -o
test; ./test
0
1
# g++ -Wall -Wextra -funsafe-math-optimizations test.cc -o test; ./test
0
-1
# g++ -Wall -Wextra -ffinite-math-only test.cc -o test; ./test
0
-1
# g++ -Wall -Wextra test.cc -o test; ./test
0
-1
Note that if I replace
a = (a > 0) ? 1.0 : -1.0;
with
if (a > 0) a = 1.0; else a = -1.0;
it also works as expected regardless of the compiler version or flags.
Compiler output
# g++ -v -save-temps -Wall -Wextra -ffinite-math-only
-funsafe-math-optimizations test.cc -o test
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array --with-isl --enable-libmpx
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --enable-cet --with-tune=generic
--with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 8.2.1 20181215 (Red Hat 8.2.1-6) (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-Wall' '-Wextra' '-ffinite-math-only'
'-funsafe-math-optimizations' '-o' 'test' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
/usr/libexec/gcc/x86_64-redhat-linux/8/cc1plus -E -quiet -v -D_GNU_SOURCE
test.cc -mtune=generic -march=x86-64 -Wall -Wextra -ffinite-math-only
-funsafe-math-optimizations -fpch-preprocess -o test.ii
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-redhat-linux/8/include-fixed"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-redhat-linux/8/../../../../x86_64-redhat-linux/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../include/c++/8
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../include/c++/8/x86_64-redhat-linux
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../include/c++/8/backward
/usr/lib/gcc/x86_64-redhat-linux/8/include
/usr/local/include
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-Wall' '-Wextra' '-ffinite-math-only'
'-funsafe-math-optimizations' '-o' 'test' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
/usr/libexec/gcc/x86_64-redhat-linux/8/cc1plus -fpreprocessed test.ii -quiet
-dumpbase test.cc -mtune=generic -march=x86-64 -auxbase test -Wall -Wextra
-version -ffinite-math-only -funsafe-math-optimizations -o test.s
GNU C++14 (GCC) version 8.2.1 20181215 (Red Hat 8.2.1-6) (x86_64-redhat-linux)
compiled by GNU C version 8.2.1 20181215 (Red Hat 8.2.1-6), GMP version
6.1.2, MPFR version 3.1.6-p2, MPC version 1.0.2, isl version isl-0.16.1-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C++14 (GCC) version 8.2.1 20181215 (Red Hat 8.2.1-6) (x86_64-redhat-linux)
compiled by GNU C version 8.2.1 20181215 (Red Hat 8.2.1-6), GMP version
6.1.2, MPFR version 3.1.6-p2, MPC version 1.0.2, isl version isl-0.16.1-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: 2c6c0283460e534bb8025645f70a7cfb
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-Wall' '-Wextra' '-ffinite-math-only'
'-funsafe-math-optimizations' '-o' 'test' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
as -v --64 -o test.o test.s
GNU assembler version 2.29.1 (x86_64-redhat-linux) using BFD version version
2.29.1-23.fc28
COMPILER_PATH=/usr/libexec/gcc/x86_64-redhat-linux/8/:/usr/libexec/gcc/x86_64-redhat-linux/8/:/usr/libexec/gcc/x86_64-redhat-linux/:/usr/lib/gcc/x86_64-redhat-linux/8/:/usr/lib/gcc/x86_64-redhat-linux/
LIBRARY_PATH=/usr/lib/gcc/x86_64-redhat-linux/8/:/usr/lib/gcc/x86_64-redhat-linux/8/../../../../lib64/:/lib/../lib64/:/usr/lib/../lib64/:/usr/lib/gcc/x86_64-redhat-linux/8/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-Wall' '-Wextra' '-ffinite-math-only'
'-funsafe-math-optimizations' '-o' 'test' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
/usr/libexec/gcc/x86_64-redhat-linux/8/collect2 -plugin
/usr/libexec/gcc/x86_64-redhat-linux/8/liblto_plugin.so
-plugin-opt=/usr/libexec/gcc/x86_64-redhat-linux/8/lto-wrapper
-plugin-opt=-fresolution=test.res -plugin-opt=-pass-through=-lgcc_s
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lc
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lgcc --build-id
--no-add-needed --eh-frame-hdr --hash-style=gnu -m elf_x86_64 -dynamic-linker
/lib64/ld-linux-x86-64.so.2 -o test
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../lib64/crt1.o
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../lib64/crti.o
/usr/lib/gcc/x86_64-redhat-linux/8/crtbegin.o
-L/usr/lib/gcc/x86_64-redhat-linux/8
-L/usr/lib/gcc/x86_64-redhat-linux/8/../../../../lib64 -L/lib/../lib64
-L/usr/lib/../lib64 -L/usr/lib/gcc/x86_64-redhat-linux/8/../../.. test.o
-lstdc++ -lm -lgcc_s -lgcc -lc -lgcc_s -lgcc
/usr/lib/gcc/x86_64-redhat-linux/8/crtfastmath.o
/usr/lib/gcc/x86_64-redhat-linux/8/crtend.o
/usr/lib/gcc/x86_64-redhat-linux/8/../../../../lib64/crtn.o
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-Wall' '-Wextra' '-ffinite-math-only'
'-funsafe-math-optimizations' '-o' 'test' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
Compiler version with unexpected behavior:
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,fortran,objc,obj-c++,ada,go,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array --with-isl --enable-libmpx
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --enable-cet --with-tune=generic
--with-arch_32=i686 --build=x86_64-redhat-linux
Thread model: posix
gcc version 8.3.1 20190223 (Red Hat 8.3.1-2) (GCC)
Compiler version with expected behavior regardless of compiler flags or code
changes:
$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/bin/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-redhat-linux
Configured with: ../configure --enable-bootstrap
--enable-languages=c,c++,objc,obj-c++,fortran,ada,go,lto --prefix=/usr
--mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=http://bugzilla.redhat.com/bugzilla --enable-shared
--enable-threads=posix --enable-checking=release --enable-multilib
--with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-gcc-major-version-only --with-linker-hash-style=gnu --enable-plugin
--enable-initfini-array --with-isl --enable-libmpx
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --with-tune=generic --with-arch_32=i686
--build=x86_64-redhat-linux
Thread model: posix
gcc version 7.3.1 20180130 (Red Hat 7.3.1-2) (GCC)
I'm aware that using -ffinite-math-only -funsafe-math-optimizations allows gcc
to divert from the IEEE standard. I am surprised though, that this simple
comparison produces different results depending on the speicifc gcc version and
whe way I code it.
Best regards,
Michael
>From gcc-bugs-return-641821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:14:51 2019
Return-Path: <gcc-bugs-return-641821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20125 invoked by alias); 25 Apr 2019 11:14: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 20084 invoked by uid 48); 25 Apr 2019 11:14:46 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/90194] ICE in expand_debug_expr, at cfgexpand.c:5244
Date: Thu, 25 Apr 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: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_known_to_work cf_known_to_fail
Message-ID: <bug-90194-4-IMQ9GIf8Oy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90194-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90194-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02677.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90194
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Known to work| |9.0
Known to fail|9.0 |
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.
>From gcc-bugs-return-641822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:16:14 2019
Return-Path: <gcc-bugs-return-641822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22106 invoked by alias); 25 Apr 2019 11:16:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22021 invoked by uid 55); 25 Apr 2019 11:16:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/90194] ICE in expand_debug_expr, at cfgexpand.c:5244
Date: Thu, 25 Apr 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: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90194-4-aLRHeBJ41F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90194-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90194-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02678.txt.bz2
Content-length: 633
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90194
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Apr 25 11:15:35 2019
New Revision: 270569
URL: https://gcc.gnu.org/viewcvs?rev=270569&root=gcc&view=rev
Log:
2019-04-25 Richard Biener <rguenther@suse.de>
PR middle-end/90194
* match.pd: Add pattern to simplify view-conversion of an
empty constructor.
* g++.dg/torture/pr90194.C: New testcase.
Added:
trunk/gcc/testsuite/g++.dg/torture/pr90194.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-641823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:17:52 2019
Return-Path: <gcc-bugs-return-641823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60245 invoked by alias); 25 Apr 2019 11: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 59984 invoked by uid 48); 25 Apr 2019 11:17:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90213] UBSAN: signed integer overflow: -5621332293356458048 * 8 cannot be represented in type 'long int'
Date: Thu, 25 Apr 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: 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_known_to_work
Message-ID: <bug-90213-4-0NPxq0E16F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90213-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90213-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02679.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90213
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Known to work| |9.0
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed on trunk sofar.
>From gcc-bugs-return-641824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:18:23 2019
Return-Path: <gcc-bugs-return-641824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61234 invoked by alias); 25 Apr 2019 11:18:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61208 invoked by uid 55); 25 Apr 2019 11:18:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90213] UBSAN: signed integer overflow: -5621332293356458048 * 8 cannot be represented in type 'long int'
Date: Thu, 25 Apr 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: 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-90213-4-h2PSTt6b7u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90213-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90213-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02680.txt.bz2
Content-length: 529
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90213
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Apr 25 11:17:49 2019
New Revision: 270570
URL: https://gcc.gnu.org/viewcvs?rev=270570&root=gcc&view=rev
Log:
2019-04-24 Richard Biener <rguenther@suse.de>
PR middle-end/90213
* gimple-fold.c (fold_const_aggregate_ref_1): Do multiplication
by size and BITS_PER_UNIT on poly-wide-ints.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimple-fold.c
>From gcc-bugs-return-641825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:23:30 2019
Return-Path: <gcc-bugs-return-641825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66069 invoked by alias); 25 Apr 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 66027 invoked by uid 48); 25 Apr 2019 11:23:27 -0000
From: "nheart at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 2019 11:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nheart at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89929-4-abNwmQ6eS7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02681.txt.bz2
Content-length: 705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #22 from Nikolay Bogoychev <nheart at gmail dot com> ---
Hey,
I was reading through the mailing list discussion (
https://gcc.gnu.org/ml/gcc-patches/2019-04/msg00757.html ) and I want to say
that currently code like
void __attribute__ ((target("avx512dq"))) foo ()
Compiles as long as function multi-versioning is not used. Making this syntax
invalid, puts us in a very annoying position, because we can't use the new
recommended syntax due to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90129
That would mean we would have to do some hacky ifdefs to match different
compiler versions.
Is there no other way.
Cheers,
Nick
>From gcc-bugs-return-641826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:26:22 2019
Return-Path: <gcc-bugs-return-641826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72582 invoked by alias); 25 Apr 2019 11: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 72554 invoked by uid 48); 25 Apr 2019 11:26:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/90232] gcc drops top-level dies with -fdebug-types-section
Date: Thu, 25 Apr 2019 11:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-debug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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 cf_known_to_fail
Message-ID: <bug-90232-4-qOH4TtQZHh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90232-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90232-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02682.txt.bz2
Content-length: 797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90232
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-debug
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |4.8.5
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed also with gcc 4.8. -fno-eliminate-unused-debug-types doesn't help
so it's an artifact of the debug-types implementation.
>From gcc-bugs-return-641827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:28:55 2019
Return-Path: <gcc-bugs-return-641827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91459 invoked by alias); 25 Apr 2019 11:28: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 91410 invoked by uid 48); 25 Apr 2019 11:28:51 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90235] Unnecessary save and restore frame pointer with AVX/AVX512 pseudo registers
Date: Thu, 25 Apr 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: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget
Message-ID: <bug-90235-4-tY2kZSoOkF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90235-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90235-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02683.txt.bz2
Content-length: 533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90235
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization, ra
Target| |x86_64-*-* i?86-*-*
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Unaligned spills can indeed be slower (they might cross a cache line boundary).
>From gcc-bugs-return-641828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:31:33 2019
Return-Path: <gcc-bugs-return-641828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5974 invoked by alias); 25 Apr 2019 11:31:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4113 invoked by uid 55); 25 Apr 2019 11:31:29 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9 Regression] C code is optimized worse than C++
Date: Thu, 25 Apr 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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-WaFoIcrRnD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02684.txt.bz2
Content-length: 1387
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #10 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 25 Apr 2019, crazylht at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
>
> --- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
> Also what's better between aligned load/store of smaller size VS unaligned
> load/store of bigger size?
>
> aligned load/store of smaller size:
>
> movq %rdx, (%rdi)
> movq -56(%rsp), %rdx
> movq %rdx, 8(%rdi)
> movq -48(%rsp), %rdx
> movq %rdx, 16(%rdi)
> movq -40(%rsp), %rdx
> movq %rdx, 24(%rdi)
> vmovq %xmm0, 32(%rax)
> movq -24(%rsp), %rdx
> movq %rdx, 40(%rdi)
> movq -16(%rsp), %rdx
> movq %rdx, 48(%rdi)
> movq -8(%rsp), %rdx
> movq %rdx, 56(%rdi)
>
> unaligned load/store of bigger size:
>
> vmovups %xmm2, (%rdi)
> vmovups %xmm3, 16(%rdi)
> vmovups %xmm4, 32(%rdi)
> vmovups %xmm5, 48(%rdi)
bigger stores are almost always a win while bigger loads have
the possibility to run into store-to-load forwarding issues
(and bigger stores eventually mitigate them). Based on
CPU tuning we'd also eventually end up with mov[lh]ps splitting
unaligned loads/stores.
>From gcc-bugs-return-641829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:44:23 2019
Return-Path: <gcc-bugs-return-641829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41909 invoked by alias); 25 Apr 2019 11:44: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 41838 invoked by uid 48); 25 Apr 2019 11:44:19 -0000
From: "rick at snowlight dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/81963] ICE in stage 2 compiler while configuring libgcc in stage2, during GIMPLE pass: cfg
Date: Thu, 25 Apr 2019 11:44: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rick at snowlight dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-81963-4-iwtKiv8DVL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81963-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02685.txt.bz2
Content-length: 660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81963
rick at snowlight dot net changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rick at snowlight dot net
--- Comment #2 from rick at snowlight dot net ---
Created attachment 46243
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46243&action=edit
32-bit libgcc config.log for *86*-sun-solaris2.10
same here on *86*-sun-solaris2.10 during the 32-bit phase of libgcc
configuration, to say nothing of whether the previous bootstrap phases actually
worked (!)
>From gcc-bugs-return-641830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:53:33 2019
Return-Path: <gcc-bugs-return-641830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92754 invoked by alias); 25 Apr 2019 11: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 92721 invoked by uid 48); 25 Apr 2019 11:53:30 -0000
From: "rick at snowlight dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/81963] ICE in stage 2 compiler while configuring libgcc in stage2, during GIMPLE pass: cfg
Date: Thu, 25 Apr 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: bootstrap
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rick at snowlight dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81963-4-vU302sqOn4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81963-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02686.txt.bz2
Content-length: 675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81963
--- Comment #3 from rick at snowlight dot net ---
Comment on attachment 46243
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46243
32-bit libgcc config.log for *86*-sun-solaris2.10
note that this was part of a multi-stage build starting from GCC 3.4.3, to GCC
4.2, then miscompiling v8.3 (the last Solaris 2.10 version), since Sun Studio
12.6, while being _reasonably_ C++98/03-compiliant using either
[RogueWave|Apache]STDCXX v4.2+ or libstdc++ v5.4, is unable to bootstrap this
version of GCC, since GCC uses its own extensions to compile itself. Only other
compiler that can compile GCC is Apple C++.
>From gcc-bugs-return-641831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 11:54:43 2019
Return-Path: <gcc-bugs-return-641831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95593 invoked by alias); 25 Apr 2019 11:54:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95409 invoked by uid 48); 25 Apr 2019 11:54:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90238] Bogus warning from -Warray-bounds, triggered by zero-length character literal
Date: Thu, 25 Apr 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: middle-end
X-Bugzilla-Version: 8.3.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: P5
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 bug_severity
Message-ID: <bug-90238-4-yjAvYyS5N3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90238-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02687.txt.bz2
Content-length: 1332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90238
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-25
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
Severity|enhancement |normal
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well, the warning code is confused by fortran passing &""[1], ignoring
the one-after-the-array case for
/* Empty array. */
if (up_bound && tree_int_cst_equal (low_bound, up_bound_p1))
warned = warning_at (location, OPT_Warray_bounds,
"array subscript %E is above array bounds of %qT",
low_bound, artype);
not sure why this special-case was added here. I think you can't create
this string literal with a C testcase (you always have the null termination).
I've added this check at r222146 possibly to rule out erratic behavior
in the anti-range handling case as part of the PR64277 fix.
>From gcc-bugs-return-641832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:00:42 2019
Return-Path: <gcc-bugs-return-641832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9069 invoked by alias); 25 Apr 2019 12:00: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 8724 invoked by uid 48); 25 Apr 2019 12:00:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 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: 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: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status blocked everconfirmed
Message-ID: <bug-90240-4-nlGjQT0INe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02688.txt.bz2
Content-length: 1104
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P2 |P1
Status|UNCONFIRMED |NEW
Blocks| |90078
Ever confirmed|0 |1
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the bug is probably latent before the PR90078 change with a "proper"
profile?
(the GIMPLE FE will get counter/freq inputs for GCC 10)
Btw, we have precedence of using GMP for niter analysis so we could switch
the cost computation to using GMP avoiding infinity for anything but the
specially marked IVs. Would that be prohibitly expensive?
Can you construct a non-GRAPHITE testcase (just reproduce the GRAPHITE
produced loop nest?)?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90078
[Bug 90078] [7/8 Regression] ICE with deep templates caused by overflow
>From gcc-bugs-return-641833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:02:05 2019
Return-Path: <gcc-bugs-return-641833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10779 invoked by alias); 25 Apr 2019 12: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 10729 invoked by uid 48); 25 Apr 2019 12:02:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 2019 12:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
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: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89929-4-i8Q9aycrwh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02689.txt.bz2
Content-length: 1028
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #23 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Nikolay Bogoychev from comment #22)
> Hey,
>
> I was reading through the mailing list discussion (
> https://gcc.gnu.org/ml/gcc-patches/2019-04/msg00757.html ) and I want to say
> that currently code like
>
> void __attribute__ ((target("avx512dq"))) foo ()
>
> Compiles as long as function multi-versioning is not used. Making this
> syntax invalid, puts us in a very annoying position, because we can't use
> the new recommended syntax due to
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90129
No, this will be working as it is now. Suggested changes will only touch C++
features of target attribute (so having multiple functions of the same name
with a different target attribute) and target_clone attribute.
>
> That would mean we would have to do some hacky ifdefs to match different
> compiler versions.
>
> Is there no other way.
>
> Cheers,
>
> Nick
>From gcc-bugs-return-641834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:03:38 2019
Return-Path: <gcc-bugs-return-641834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12504 invoked by alias); 25 Apr 2019 12:03: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 12480 invoked by uid 48); 25 Apr 2019 12:03:34 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90241] [UBSAN]: in ao_ref_init_from_ptr_and_size
Date: Thu, 25 Apr 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: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-90241-4-fe7w8xyMkB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90241-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90241-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02690.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90241
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
CC| |rguenth at gcc dot gnu.org
Component|c |middle-end
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. All the byte->bit conversions on poly_[u]int64 are suspicious. But
also expensive to fix :/
>From gcc-bugs-return-641835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:04:39 2019
Return-Path: <gcc-bugs-return-641835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13897 invoked by alias); 25 Apr 2019 12:04:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13846 invoked by uid 48); 25 Apr 2019 12:04:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90242] [UBSAN]: in vn_reference_compute_hash
Date: Thu, 25 Apr 2019 12:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: cc component
Message-ID: <bug-90242-4-LbPLxns6uw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02691.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90242
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
Component|c |tree-optimization
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
signed offset vs. unsigned size, but on "invalid" input (too large object).
>From gcc-bugs-return-641836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:06:20 2019
Return-Path: <gcc-bugs-return-641836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43844 invoked by alias); 25 Apr 2019 12:06:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42193 invoked by uid 48); 25 Apr 2019 12:06:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90244] [UBSAN]: in get_object_alignment_2
Date: Thu, 25 Apr 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: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-90244-4-odrj4nKrXb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90244-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90244-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02692.txt.bz2
Content-length: 653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90244
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
CC| |rguenth at gcc dot gnu.org
Component|c |middle-end
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Similar issue, bit position and poly_int64.
>From gcc-bugs-return-641837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:14:47 2019
Return-Path: <gcc-bugs-return-641837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61613 invoked by alias); 25 Apr 2019 12:14:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61564 invoked by uid 48); 25 Apr 2019 12:14:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: middle-end
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: 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: keywords bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-90248-4-nRvPKsh2St@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02693.txt.bz2
Content-length: 1179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-25
Component|c++ |middle-end
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
We should simplify this to
a = copysignf (1.0, a);
I guess.
Confirmed on trunk with a C testcase:
int main() {
float a = 0;
__builtin_printf ("%f\n", a);
a = (a > 0) ? 1.0 : -1.0;
__builtin_printf ("%f\n", a);
return 0;
}
And indeed .original already shows (but only with -ffinite-math-only
because of a being possibly NaN).
float a = 0.0;
__builtin_printf ((const char *) "%f\n", (double) a);
a = __builtin_copysignf (1.0e+0, a);
__builtin_printf ((const char *) "%f\n", (double) a);
wrong sign for the copysign transform for zero.
>From gcc-bugs-return-641838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:18:27 2019
Return-Path: <gcc-bugs-return-641838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106383 invoked by alias); 25 Apr 2019 12:18: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 106337 invoked by uid 48); 25 Apr 2019 12:18:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 2019 12: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: 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: 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 cf_known_to_work cf_known_to_fail
Message-ID: <bug-90248-4-YIfsxPDDdI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02694.txt.bz2
Content-length: 2223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
CC| |pinskia at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Known to work| |7.3.1
Known to fail| |8.1.0, 9.0
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(for cmp (gt ge lt le)
outp (convert convert negate negate)
outn (negate negate convert convert)
/* Transform (X > 0.0 ? 1.0 : -1.0) into copysign(1, X). */
/* Transform (X >= 0.0 ? 1.0 : -1.0) into copysign(1, X). */
/* Transform (X < 0.0 ? 1.0 : -1.0) into copysign(1,-X). */
/* Transform (X <= 0.0 ? 1.0 : -1.0) into copysign(1,-X). */
(simplify
(cond (cmp @0 real_zerop) real_onep@1 real_minus_onep)
(if (!HONOR_NANS (type) && !HONOR_SIGNED_ZEROS (type)
&& types_match (type, TREE_TYPE (@0)))
(switch
(if (types_match (type, float_type_node))
(BUILT_IN_COPYSIGNF @1 (outp @0)))
(if (types_match (type, double_type_node))
(BUILT_IN_COPYSIGN @1 (outp @0)))
(if (types_match (type, long_double_type_node))
(BUILT_IN_COPYSIGNL @1 (outp @0))))))
looks like this one is the culprit. Similar suspicious symmetry with
/* Transform (X > 0.0 ? -1.0 : 1.0) into copysign(1,-X). */
/* Transform (X >= 0.0 ? -1.0 : 1.0) into copysign(1,-X). */
/* Transform (X < 0.0 ? -1.0 : 1.0) into copysign(1,X). */
/* Transform (X <= 0.0 ? -1.0 : 1.0) into copysign(1,X). */
(simplify
(cond (cmp @0 real_zerop) real_minus_onep real_onep@1)
(if (!HONOR_NANS (type) && !HONOR_SIGNED_ZEROS (type)
&& types_match (type, TREE_TYPE (@0)))
(switch
(if (types_match (type, float_type_node))
(BUILT_IN_COPYSIGNF @1 (outn @0)))
(if (types_match (type, double_type_node))
(BUILT_IN_COPYSIGN @1 (outn @0)))
(if (types_match (type, long_double_type_node))
(BUILT_IN_COPYSIGNL @1 (outn @0)))))))
caused by r249704
>From gcc-bugs-return-641839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:18:43 2019
Return-Path: <gcc-bugs-return-641839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107196 invoked by alias); 25 Apr 2019 12:18:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107132 invoked by uid 55); 25 Apr 2019 12:18:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/44648] missing -Wunused warning on a const variable in if statement
Date: Thu, 25 Apr 2019 12:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.4.3
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:
Message-ID: <bug-44648-4-zUaodlrXfZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02695.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44648
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Apr 25 12:18:07 2019
New Revision: 270572
URL: https://gcc.gnu.org/viewcvs?rev=270572&root=gcc&view=rev
Log:
PR c++/44648
* g++.dg/warn/Wunused-var-35.C: Remove xfail.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/warn/Wunused-var-35.C
>From gcc-bugs-return-641840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:29:49 2019
Return-Path: <gcc-bugs-return-641840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104900 invoked by alias); 25 Apr 2019 12:29:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104857 invoked by uid 48); 25 Apr 2019 12:29:46 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: middle-end
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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90248-4-lOCZrMEXU3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02696.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
In fact the copysign transform, for the cases where we negate X _relies_ on
signed zeros...
Only exact
/* Transform (X >= 0.0 ? 1.0 : -1.0) into copysign(1, X). */
and
/* Transform (X < 0.0 ? -1.0 : 1.0) into copysign(1,X). */
look correct to me?
>From gcc-bugs-return-641841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:31:18 2019
Return-Path: <gcc-bugs-return-641841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112633 invoked by alias); 25 Apr 2019 12: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 112573 invoked by uid 48); 25 Apr 2019 12:31:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] [8/9 Regression] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: middle-end
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone short_desc
Message-ID: <bug-90248-4-zJ9rRFO46D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02697.txt.bz2
Content-length: 638
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Target Milestone|--- |8.4
Summary|larger than 0 compare fails |[8/9 Regression] larger
|with -ffinite-math-only |than 0 compare fails with
|-funsafe-math-optimizations |-ffinite-math-only
| |-funsafe-math-optimizations
>From gcc-bugs-return-641842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:31:28 2019
Return-Path: <gcc-bugs-return-641842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113319 invoked by alias); 25 Apr 2019 12: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 113258 invoked by uid 48); 25 Apr 2019 12:31:24 -0000
From: "nheart at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 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: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nheart at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89929-4-k9NAkKKK48@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02698.txt.bz2
Content-length: 1192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #24 from Nikolay Bogoychev <nheart at gmail dot com> ---
(In reply to Martin Liška from comment #23)
> (In reply to Nikolay Bogoychev from comment #22)
> > Hey,
> >
> > I was reading through the mailing list discussion (
> > https://gcc.gnu.org/ml/gcc-patches/2019-04/msg00757.html ) and I want to say
> > that currently code like
> >
> > void __attribute__ ((target("avx512dq"))) foo ()
> >
> > Compiles as long as function multi-versioning is not used. Making this
> > syntax invalid, puts us in a very annoying position, because we can't use
> > the new recommended syntax due to
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90129
>
> No, this will be working as it is now. Suggested changes will only touch C++
> features of target attribute (so having multiple functions of the same name
> with a different target attribute) and target_clone attribute.
>
> >
> > That would mean we would have to do some hacky ifdefs to match different
> > compiler versions.
> >
> > Is there no other way.
> >
> > Cheers,
> >
> > Nick
Ok, thank you for the clarification!
Cheers,
Nick
>From gcc-bugs-return-641843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 12:41:47 2019
Return-Path: <gcc-bugs-return-641843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86881 invoked by alias); 25 Apr 2019 12: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 86761 invoked by uid 48); 25 Apr 2019 12:41:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] [8/9 Regression] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: middle-end
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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90248-4-Iylu16achr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02699.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, all those look quite questionable, -fno-signed-zeros doesn't mean 0.0 or
-0.0 won't appear, just that it shouldn't matter if 0.0 or -0.0 appears.
So the > 0.0 and <= 0.0 cases look completely bogus and the rest too, >= 0.0 or
< 0.0 works regardless of what sign the zero has, while if copysign is used,
then it is significant, and not just in the sign of some zero, but actually
whether the result is -1.0 or 1.0.
>From gcc-bugs-return-641844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:03:37 2019
Return-Path: <gcc-bugs-return-641844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23714 invoked by alias); 25 Apr 2019 13:03: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 23093 invoked by uid 48); 25 Apr 2019 13:03:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/89832] confusing error message when there is a problem with ASAN_OPTIONS "ERROR: expected '='"
Date: Thu, 25 Apr 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: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-89832-4-JLyK38hPtG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02700.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89832
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.0 |10.0
>From gcc-bugs-return-641845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:05:20 2019
Return-Path: <gcc-bugs-return-641845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38441 invoked by alias); 25 Apr 2019 13:05:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29547 invoked by uid 48); 25 Apr 2019 13:05:15 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88277] ASAN stack poisoning is using unaligned stores on e.g. x86_64
Date: Thu, 25 Apr 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: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88277-4-HpF026XbIK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88277-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88277-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02701.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88277
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andi Kleen from comment #2)
> FWIW modern x86 CPUs are fairly good at unaligned accesses, so it might not
> be worth it for performance.
That said, I'm leaving that..
>From gcc-bugs-return-641846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:06:00 2019
Return-Path: <gcc-bugs-return-641846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51736 invoked by alias); 25 Apr 2019 13:06:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51644 invoked by uid 48); 25 Apr 2019 13:05:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] [8/9 Regression] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90248-4-aARVVrqNz9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02702.txt.bz2
Content-length: 794
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #4)
> Yeah, all those look quite questionable, -fno-signed-zeros doesn't mean 0.0
> or -0.0 won't appear, just that it shouldn't matter if 0.0 or -0.0 appears.
Yeah, it means that when a is 0. or -0. the behavior can either
match 0. > 0 ? 1. : -1. or -0. > 0 ? 1. : -1. So probably the
cases where we negate X are OK-ish in that regard?
> So the > 0.0 and <= 0.0 cases look completely bogus and the rest too, >= 0.0
> or
> < 0.0 works regardless of what sign the zero has, while if copysign is used,
> then it is significant, and not just in the sign of some zero, but actually
> whether the result is -1.0 or 1.0.
>From gcc-bugs-return-641847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:20:43 2019
Return-Path: <gcc-bugs-return-641847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43778 invoked by alias); 25 Apr 2019 13:20:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43698 invoked by uid 48); 25 Apr 2019 13:20:38 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90249] New: [9 regression] Code size regression on thumb2 due to sub-optimal register allocation.
Date: Thu, 25 Apr 2019 13:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget attachments.created
Message-ID: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02703.txt.bz2
Content-length: 4181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
Bug ID: 90249
Summary: [9 regression] Code size regression on thumb2 due to
sub-optimal register allocation.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ra
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rearnsha at gcc dot gnu.org
CC: ramana.radhakrishnan at arm dot com, vmakarov at redhat dot com,
wdijkstr at arm dot com
Target Milestone: ---
Target: arm
Created attachment 46244
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46244&action=edit
testcase
GCC 9 has regressed on code size due to some sub-optimal register allocation.
For this example, the only difference in the output is that the assignments for
r7 and r8 have been switched, but the result is significant growth in code size
since r8 requires predominantly 32-bit instructions to be used while r7
requires predominantly 16-bit instructions.
cc1 -fpreprocessed binding2.i -quiet -dumpbase binding2.i -mthumb
-mcpu=cortex-a8 -march=armv7-a -auxbase-strip binding.o -Os -w -version
-fno-short-enums -fgnu89-inline -o binding2.s
In gcc-8 the output was
DefineConnectorBinding:
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 0, uses_anonymous_args = 0
push {r0, r1, r2, r3, r4, r5, r6, r7, r8, lr}
mov r4, r1
mov r8, r0
mov r1, r2
mov r0, r4
mov r5, r2
mov r7, r3
bl LookupBinding
mov r6, r0
cbz r0, .L2
ldr r7, .L5
mov r1, r4
ldr r0, [r7] // 16-bit instruction
bl GetAtomString
mov r1, r5
mov r4, r0
ldr r0, [r7] // 16-bit instruction
bl GetAtomString
ldrh r1, [r6, #8]
mov r5, r0
ldr r0, [r7] // 16-bit instruction
bl GetAtomString
ldrh r3, [r6, #10]
ldr r2, .L5+4
movs r1, #103
str r5, [sp]
strd r0, r3, [sp, #4]
mov r3, r4
mov r0, r8
bl SemanticError
add sp, sp, #16
@ sp needed
pop {r4, r5, r6, r7, r8, pc}
.L2:
mov r3, r7
mov r2, r5
mov r1, r4
mov r0, r8
bl NewConnectorBindingTree
add sp, sp, #16
@ sp needed
pop {r4, r5, r6, r7, r8, lr}
b AddBinding
In gcc-9 we get
DefineConnectorBinding:
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 0, uses_anonymous_args = 0
push {r0, r1, r2, r3, r4, r5, r6, r7, r8, lr}
mov r4, r1
mov r7, r0
mov r1, r2
mov r0, r4
mov r5, r2
mov r8, r3
bl LookupBinding
mov r6, r0
cbz r0, .L2
ldr r8, .L5+4
mov r1, r4
ldr r0, [r8] // 32-bit instruction
bl GetAtomString
mov r1, r5
mov r4, r0
ldr r0, [r8] // 32-bit instruction
bl GetAtomString
ldrh r1, [r6, #8]
mov r5, r0
ldr r0, [r8] // 32-bit instruction
bl GetAtomString
ldrh r3, [r6, #10]
ldr r2, .L5
movs r1, #103
str r5, [sp]
strd r0, r3, [sp, #4]
mov r3, r4
mov r0, r7
bl SemanticError
add sp, sp, #16
@ sp needed
pop {r4, r5, r6, r7, r8, pc}
.L2:
mov r3, r8
mov r2, r5
mov r1, r4
mov r0, r7
bl NewConnectorBindingTree
add sp, sp, #16
@ sp needed
pop {r4, r5, r6, r7, r8, lr}
b AddBinding
R8 is used more often than R7, so it seems odd that it is preferred over the
latter.
>From gcc-bugs-return-641849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:21:51 2019
Return-Path: <gcc-bugs-return-641849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48739 invoked by alias); 25 Apr 2019 13:21:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48657 invoked by uid 48); 25 Apr 2019 13:21:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90249] [9 regression] Code size regression on thumb2 due to sub-optimal register allocation.
Date: Thu, 25 Apr 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: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-90249-4-fIY5He35TT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02705.txt.bz2
Content-length: 362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target Milestone|--- |9.0
>From gcc-bugs-return-641848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:21:04 2019
Return-Path: <gcc-bugs-return-641848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46891 invoked by alias); 25 Apr 2019 13:21:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46357 invoked by uid 48); 25 Apr 2019 13:21:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kelvin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-89765-4-jg98UgmrBR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02704.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
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> ---
Seems to work with a cross (but host headers).
>From gcc-bugs-return-641850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:27:30 2019
Return-Path: <gcc-bugs-return-641850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29434 invoked by alias); 25 Apr 2019 13: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 26174 invoked by uid 48); 25 Apr 2019 13:27:27 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9 Regression] C code is optimized worse than C++
Date: Thu, 25 Apr 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: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-dD7rfhrFiU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02706.txt.bz2
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Hongtao.liu from comment #7)
> Yes, C++ with NRV optization, so the alignment of <retval>(res) is 4.
> and the alignment of res is 16 in C.
>
> g++/test.i.158t.vect:
>
> ../test.i:8:23: note: recording new base alignment for &<retval>
> alignment: 4
> misalignment: 0
>
> gcc/test.i.158t.vect:
>
> ../test.i:8:5: note: recording new base alignment for &res
> alignment: 16
> misalignment: 0
>
> When alignment of res is 16, that triggers loop peeling of vectorization.
>
Why does struct v have different alignments in C and C++?
>From gcc-bugs-return-641851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:29:18 2019
Return-Path: <gcc-bugs-return-641851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113117 invoked by alias); 25 Apr 2019 13:29: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 113067 invoked by uid 48); 25 Apr 2019 13:29:14 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/90250] New: libphobos: segfault in runtime caused by unexpected GC of TLS data.
Date: Thu, 25 Apr 2019 13:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90250-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02707.txt.bz2
Content-length: 1475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90250
Bug ID: 90250
Summary: libphobos: segfault in runtime caused by unexpected GC
of TLS data.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: d
Assignee: ibuclaw at gdcproject dot org
Reporter: ibuclaw at gdcproject dot org
Target Milestone: ---
The crash is only observed on non Linux/glibc systems.
Reason being because glibc puts the TLS area for each new thread at the
beginning of the newly created stack. Due to the way we detect the stack
bottom, we hoover up the TLS data along with what we think the stack is.
This is of course a dirty implementation detail, but explains why things don't
crash on GNU/Linux the way they are.
---
final class Class
{
// This gets triggered although the instance always stays referenced.
~this()
{
import core.stdc.stdlib;
abort();
}
}
Class obj;
static this()
{
obj = new Class;
}
static ~this()
{
// Free without destruction to avoid triggering abort()
import core.memory;
GC.free(cast(void*)obj);
}
void doit()
{
foreach (i; 0 .. 10_000)
new ubyte[](100_000);
}
void main()
{
import core.thread;
auto t = new Thread(&doit);
t.start();
// This triggers the GC that frees the still referenced Class instance.
doit();
}
>From gcc-bugs-return-641852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:30:28 2019
Return-Path: <gcc-bugs-return-641852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114937 invoked by alias); 25 Apr 2019 13:30: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 114724 invoked by uid 55); 25 Apr 2019 13:30:22 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9 Regression] C code is optimized worse than C++
Date: Thu, 25 Apr 2019 13:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-E3sqdgxO95@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02708.txt.bz2
Content-length: 1034
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #12 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 25 Apr 2019, hjl.tools at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
>
> --- Comment #11 from H.J. Lu <hjl.tools at gmail dot com> ---
> (In reply to Hongtao.liu from comment #7)
> > Yes, C++ with NRV optization, so the alignment of <retval>(res) is 4.
> > and the alignment of res is 16 in C.
> >
> > g++/test.i.158t.vect:
> >
> > ../test.i:8:23: note: recording new base alignment for &<retval>
> > alignment: 4
> > misalignment: 0
> >
> > gcc/test.i.158t.vect:
> >
> > ../test.i:8:5: note: recording new base alignment for &res
> > alignment: 16
> > misalignment: 0
> >
> > When alignment of res is 16, that triggers loop peeling of vectorization.
> >
>
> Why does struct v have different alignments in C and C++?
I think we re-align automatic variables but obviously cannot do the
same for incoming DECL_RESULT.
>From gcc-bugs-return-641853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 13:45:30 2019
Return-Path: <gcc-bugs-return-641853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44713 invoked by alias); 25 Apr 2019 13:45: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 44602 invoked by uid 48); 25 Apr 2019 13:45:25 -0000
From: "zbeekman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88154] [F18] ICE: Intrinsic function '_gfortran_caf_get_team' (119) not recognized
Date: Thu, 25 Apr 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: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zbeekman 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-88154-4-5b8pQo7oSd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88154-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88154-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02709.txt.bz2
Content-length: 451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88154
Zaak <zbeekman at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zbeekman at gmail dot com
--- Comment #2 from Zaak <zbeekman at gmail dot com> ---
xref to the OC bug tracker:
https://github.com/sourceryinstitute/OpenCoarrays/issues/545
>From gcc-bugs-return-641854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:04:07 2019
Return-Path: <gcc-bugs-return-641854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96106 invoked by alias); 25 Apr 2019 14:04: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 96054 invoked by uid 48); 25 Apr 2019 14:04:03 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/87338] gcc 8.2 fails to bootstrap on ia64
Date: Thu, 25 Apr 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: bootstrap
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jrtc27 at jrtc27 dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-87338-4-LmOxRZ8lqt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02710.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87338
James Clarke <jrtc27 at jrtc27 dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jrtc27 at jrtc27 dot com
--- Comment #6 from James Clarke <jrtc27 at jrtc27 dot com> ---
Created attachment 46245
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46245&action=edit
Proposed patch
Currently performing a test build with this patch, but applying
`s/^.LBI[0-9]*:$/[&]/g` to the stage2 (the one with debug info enabled)
assembly for one of the differing files fixed the differences to the stage3
file, so I'm confident this will fix it (assuming my change actually compiles).
>From gcc-bugs-return-641855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:17:43 2019
Return-Path: <gcc-bugs-return-641855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50840 invoked by alias); 25 Apr 2019 14: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 50777 invoked by uid 48); 25 Apr 2019 14:17:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 2019 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kelvin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-89765-4-0etpxzTdlx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02711.txt.bz2
Content-length: 3743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The ICE started with r262946. Short testcase reproduceable with a cross to
powerpc64le-linux with -maltivec -mvsx -O1:
typedef unsigned __int128 V __attribute__((vector_size (sizeof (__int128))));
V
foo (unsigned __int128 x, V y, int z)
{
return __builtin_vec_insert (x, y, z);
}
During gimplification, gimplify_expr does:
12577 *expr_p = fold_indirect_ref_loc (input_location, *expr_p);
12578 if (*expr_p != save_expr)
12579 {
12580 ret = GS_OK;
12581 break;
12582 }
12583
12584 ret = gimplify_expr (&TREE_OPERAND (*expr_p, 0), pre_p,
post_p,
12585 is_gimple_reg, fb_rvalue);
12586 if (ret == GS_ERROR)
12587 break;
on *expr_p:
<indirect_ref 0x7fffea99d260
type <integer_type 0x7fffea7f7bd0 __int128 unsigned public unsigned TI
size <integer_cst 0x7fffea805018 constant 128>
unit-size <integer_cst 0x7fffea805030 constant 16>
align:128 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7fffea7f7bd0 precision:128 min <integer_cst 0x7fffea805300 0> max
<integer_cst 0x7fffea806028 0xffffffffffffffffffffffffffffffff>
pointer_to_this <pointer_type 0x7fffea983f18>>
side-effects
arg:0 <nop_expr 0x7fffea99d200
type <pointer_type 0x7fffea983f18 type <integer_type 0x7fffea7f7bd0
__int128 unsigned>
unsigned DI
size <integer_cst 0x7fffea7f4fc0 constant 64>
unit-size <integer_cst 0x7fffea7f4fd8 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7fffea983f18>
side-effects
arg:0 <addr_expr 0x7fffea99d1e0 type <pointer_type 0x7fffea983c78>
side-effects
arg:0 <compound_literal_expr 0x7fffea99d1c0 type <vector_type
0x7fffea983d20 V>
side-effects addressable
arg:0 <decl_expr 0x7fffea99d1a0 type <vector_type
0x7fffea983d20 V>
side-effects arg:0 <var_decl 0x7ffff7ffb3f0 D.2833>
pr89765.i:6:10 start: pr89765.i:6:10 finish:
pr89765.i:6:29>>
pr89765.i:6:10 start: pr89765.i:6:10 finish: pr89765.i:6:29>
pr89765.i:6:10 start: pr89765.i:6:10 finish: pr89765.i:6:29>
pr89765.i:6:10 start: pr89765.i:6:10 finish: pr89765.i:6:29>
fold_indirect_ref_1 has for this:
14205 else if (VECTOR_TYPE_P (optype)
14206 && type == TREE_TYPE (optype))
14207 {
14208 tree part_width = TYPE_SIZE (type);
14209 tree index = bitsize_int (0);
14210 return fold_build3_loc (loc, BIT_FIELD_REF, type, op,
part_width,
14211 index);
14212 }
but match.pd actually folds that into a VIEW_CONVERT_EXPR and we keep it at the
lhs and ICE during checking.
Without the match.pd change, we used to have:
D.2803 = y_2(D);
BIT_FIELD_REF <D.2803, 128, 0> = x_4(D);
_6 = D.2803;
even in ssa pass and only ccp1 changed that into:
_7 = y_2(D);
_8 = BIT_INSERT_EXPR <_7, x_4(D), 0 (128 bits)>;
_6 = _8;
Now we ICE already during gimple pass verification.
Shall we special case VIEW_CONVERT_EXPR on lhs of assignment by moving the VCE
to the rhs instead? Something different?
>From gcc-bugs-return-641856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:17:51 2019
Return-Path: <gcc-bugs-return-641856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51498 invoked by alias); 25 Apr 2019 14: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 51451 invoked by uid 48); 25 Apr 2019 14:17:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/87338] gcc 8.2 fails to bootstrap on ia64
Date: Thu, 25 Apr 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: bootstrap
X-Bugzilla-Version: 8.2.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: 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-87338-4-zIOsg1ImPe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02712.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87338
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu.org
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
CCing ia64 port maintainer
>From gcc-bugs-return-641857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:20:41 2019
Return-Path: <gcc-bugs-return-641857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53701 invoked by alias); 25 Apr 2019 14:20:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53662 invoked by uid 48); 25 Apr 2019 14:20:38 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/87338] gcc 8.2 fails to bootstrap on ia64
Date: Thu, 25 Apr 2019 14:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jrtc27 at jrtc27 dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87338-4-qg7eVB0ByY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02713.txt.bz2
Content-length: 284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87338
--- Comment #8 from James Clarke <jrtc27 at jrtc27 dot com> ---
Oh, and the reason it didn't show up with an older binutils is because it
didn't support dwarf2 debug_view:
> checking assembler for dwarf2 debug_view support... no
>From gcc-bugs-return-641858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:22:24 2019
Return-Path: <gcc-bugs-return-641858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55965 invoked by alias); 25 Apr 2019 14:22: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 55890 invoked by uid 48); 25 Apr 2019 14:22:21 -0000
From: "kelvin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 2019 14:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kelvin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kelvin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89765-4-ObKb2hskrw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02714.txt.bz2
Content-length: 902
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
--- Comment #3 from kelvin at gcc dot gnu.org ---
I have found that removing the pattern in match.pd resolves this issue with no
regressions on various powerpc targets. I have not tested on other platforms.
Index: gcc/match.pd
===================================================================
--- gcc/match.pd (revision 270020)
+++ gcc/match.pd (working copy)
@@ -4963,11 +4963,6 @@ DEFINE_INT_AND_FLOAT_ROUND_FN (RINT)
(BIT_FIELD_REF @0 @1 @2))
(simplify
- (BIT_FIELD_REF @0 @1 integer_zerop)
- (if (tree_int_cst_equal (@1, TYPE_SIZE (TREE_TYPE (@0))))
- (view_convert @0)))
-
-(simplify
(BIT_FIELD_REF @0 @1 @2)
(switch
(if (TREE_CODE (TREE_TYPE (@0)) == COMPLEX_TYPE
>From gcc-bugs-return-641859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:24:49 2019
Return-Path: <gcc-bugs-return-641859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58371 invoked by alias); 25 Apr 2019 14:24:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58291 invoked by uid 48); 25 Apr 2019 14:24:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 2019 14:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kelvin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89765-4-giPWVGdDb8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02715.txt.bz2
Content-length: 383
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That is not the right thing to do.
Anyway, as for the wrong-code, do you see any gcc version where it actually
passes? Tried various versions, e.g. r205000, r235000, r250907 and r268427 and
all of them abort, older versions print more messages than newer ones.
>From gcc-bugs-return-641861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:28:23 2019
Return-Path: <gcc-bugs-return-641861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69819 invoked by alias); 25 Apr 2019 14:28:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69754 invoked by uid 48); 25 Apr 2019 14:28:19 -0000
From: "zbeekman at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88154] [F18] ICE: Intrinsic function '_gfortran_caf_get_team' (119) not recognized
Date: Thu, 25 Apr 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: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zbeekman 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-88154-4-MzhXmrjcjW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88154-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88154-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02717.txt.bz2
Content-length: 1094
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88154
--- Comment #3 from Zaak <zbeekman at gmail dot com> ---
Some additional test cases from the OC bug tracker. These fail using
gfortran -fcoarray=single
and when linking against opencoarrays, so it seems there is an issue on the GCC
side (possibly the OC side too, but let's get -fcoarray=single working first)
-----------------8<----------------------------
I get a compile error when trying to use the get_team() intrinsic:
program test_get_team
use, intrinsic :: iso_fortran_env, only: team_type
type(team_type) :: initial
initial = get_team()
end program test_get_team
Compiling the above, I get:
../get-team.f90:4:13:
initial = get_team()
1
Error: Can't convert INTEGER(4) to TYPE(team_type) at (1)
So, it appears that get_team() returns an integer.
FURTHER...
I then changed the return type to an integer:
program test_get_team
use, intrinsic :: iso_fortran_env, only: team_type
integer :: tn
tn = get_team()
end program test_get_team
I then get a internal compiler error
>From gcc-bugs-return-641860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:28:10 2019
Return-Path: <gcc-bugs-return-641860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69088 invoked by alias); 25 Apr 2019 14: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 69055 invoked by uid 48); 25 Apr 2019 14:28:07 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/90237] Bogus warning from -Wdo-subscript
Date: Thu, 25 Apr 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: fortran
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
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: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-90237-4-flTgplBm5S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90237-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02716.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90237
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-04-25
Ever confirmed|0 |1
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Duplicate of pr85737 and pr87606.
>From gcc-bugs-return-641863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:32:54 2019
Return-Path: <gcc-bugs-return-641863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78456 invoked by alias); 25 Apr 2019 14: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 77920 invoked by uid 55); 25 Apr 2019 14:32:49 -0000
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90037] [9 Regression] -Wnull-dereference false positive after r269302
Date: Thu, 25 Apr 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: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: law at redhat dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90037-4-pnAUr0JktF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90037-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90037-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02719.txt.bz2
Content-length: 1268
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90037
--- Comment #14 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Thu Apr 25 14:32:16 2019
New Revision: 270574
URL: https://gcc.gnu.org/viewcvs?rev=270574&root=gcc&view=rev
Log:
PR tree-optimization/90037
* Makefile.in (OBJS): Remove tree-ssa-phionlycprop.c
* passes.def: Replace all instance of phi-only cprop with the
lattice propagator. Move propagation pass from after erroneous
path isolation to before erroneous path isolation.
* tree-ssa-phionlycprop.c: Remove.
* gcc.dg/tree-ssa/20030710-1.c: Update dump file to scan.
* gcc.dg/isolate-2.c: Likewise.
* gcc.dg/isolate-4.c: Likewise.
* gcc.dg/pr19431.c: Accept either ordering of PHI args.
* gcc.dg/pr90037.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/pr90037.c
Removed:
trunk/gcc/tree-ssa-phionlycprop.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/Makefile.in
trunk/gcc/passes.def
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-ssa/20030710-1.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/isolate-2.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/isolate-4.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr19431.c
>From gcc-bugs-return-641862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:32:24 2019
Return-Path: <gcc-bugs-return-641862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75749 invoked by alias); 25 Apr 2019 14:32:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75670 invoked by uid 48); 25 Apr 2019 14:32:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: kelvin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89765-4-xzsuBNiYtk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02718.txt.bz2
Content-length: 1936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think the issue is that we gimplify
VIEW_CONVERT_EXPR<__int128 unsigned>(<<< Unknown tree: compound_literal_expr
V D.2833 = y; >>>)
via
12399 case VIEW_CONVERT_EXPR:
12400 if (is_gimple_reg_type (TREE_TYPE (*expr_p))
12401 && is_gimple_reg_type (TREE_TYPE (TREE_OPERAND (*expr_p,
0))))
12402 {
12403 ret = gimplify_expr (&TREE_OPERAND (*expr_p, 0), pre_p,
12404 post_p, is_gimple_val, fb_rvalue);
(gdb) l
12405 recalculate_side_effects (*expr_p);
12406 break;
when in gimplify_expr with fallback == fb_lvalue and gimple_test_f ==
is_gimple_lvalue. If we fix that with
Index: gcc/gimplify.c
===================================================================
--- gcc/gimplify.c (revision 270437)
+++ gcc/gimplify.c (working copy)
@@ -12397,7 +12397,8 @@ gimplify_expr (tree *expr_p, gimple_seq
break;
case VIEW_CONVERT_EXPR:
- if (is_gimple_reg_type (TREE_TYPE (*expr_p))
+ if ((fallback & fb_rvalue)
+ && is_gimple_reg_type (TREE_TYPE (*expr_p))
&& is_gimple_reg_type (TREE_TYPE (TREE_OPERAND (*expr_p, 0))))
{
ret = gimplify_expr (&TREE_OPERAND (*expr_p, 0), pre_p,
then we gimplify to the correct
VIEW_CONVERT_EXPR<__int128 unsigned>(D.2833) = x;
and yes, we could move the VIEW_CONVERT_EXPR to the RHS as a trick to make
D.2833 SSA rewritable in update-address-taken.
Have to think whether requiring fallback & fb_rvalue is to be used or
if fallback != fb_lvalue is better. I guess the latter.
>From gcc-bugs-return-641865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:33:36 2019
Return-Path: <gcc-bugs-return-641865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80625 invoked by alias); 25 Apr 2019 14: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 80462 invoked by uid 48); 25 Apr 2019 14:33:33 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86172] [meta-bug] issues with -Wnull-dereference
Date: Thu, 25 Apr 2019 14:33: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: 8.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86172-4-mmuJqojBMf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86172-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86172-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02721.txt.bz2
Content-length: 490
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86172
Bug 86172 depends on bug 90037, which changed state.
Bug 90037 Summary: [9 Regression] -Wnull-dereference false positive after r269302
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90037
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-641864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:33:36 2019
Return-Path: <gcc-bugs-return-641864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80522 invoked by alias); 25 Apr 2019 14: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 80424 invoked by uid 48); 25 Apr 2019 14:33:33 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90037] [9 Regression] -Wnull-dereference false positive after r269302
Date: Thu, 25 Apr 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: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
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-90037-4-zw9hqoqrYu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90037-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90037-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02720.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90037
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Jeffrey A. Law <law at redhat dot com> ---
Fixed on trunk.
>From gcc-bugs-return-641866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:34:17 2019
Return-Path: <gcc-bugs-return-641866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82592 invoked by alias); 25 Apr 2019 14: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 82505 invoked by uid 48); 25 Apr 2019 14:34:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: middle-end
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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on component assigned_to everconfirmed
Message-ID: <bug-89765-4-H6XUPSxsxz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02722.txt.bz2
Content-length: 554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-25
Component|target |middle-end
Assignee|kelvin at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-641867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:35:55 2019
Return-Path: <gcc-bugs-return-641867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84857 invoked by alias); 25 Apr 2019 14: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 84801 invoked by uid 48); 25 Apr 2019 14:35:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89765] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: middle-end
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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89765-4-SiwWqQo324@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02723.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Actually we use is_gimple_val so testing fallback & fb_rvalue.
>From gcc-bugs-return-641868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:40:13 2019
Return-Path: <gcc-bugs-return-641868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4088 invoked by alias); 25 Apr 2019 14: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 3995 invoked by uid 48); 25 Apr 2019 14:40:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89765] [9 Regression] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: middle-end
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: rguenth 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-89765-4-cTHEuLPgFf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02724.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
Summary|Multiple problems with |[9 Regression] Multiple
|vec-insert implementation |problems with vec-insert
|on PowerPC |implementation on PowerPC
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Making this a regression for the ICE, for the wrong-code we don't have a proof
of it being a regression.
>From gcc-bugs-return-641869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 14:54:45 2019
Return-Path: <gcc-bugs-return-641869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100162 invoked by alias); 25 Apr 2019 14: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 99618 invoked by uid 48); 25 Apr 2019 14:54:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89765] [9 Regression] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: middle-end
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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89765-4-VkiIzcnzBP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02725.txt.bz2
Content-length: 1017
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, the C notation
typedef unsigned __int128 V __attribute__((vector_size (sizeof (__int128))));
V
foo (unsigned __int128 x, V y, int z)
{
y[0] = x;
}
on x86_64 prouces
{
VIEW_CONVERT_EXPR<__int128 unsigned[1]>(y)[0] = x;
}
the array-ref prevents the gimplification into SSA. That also works
for variable indices btw. It is eventually turns into
BIT_FIELD_REF <y, 128, 0> = x_2(D);
by gimplification first and then
y_5 = BIT_INSERT_EXPR <y_4(D), x_2(D), 0 (128 bits)>;
by update-address-taken. Not sure why the folding doesn't trigger here
but does for ppc64. The BIT_FIELD_REF is produced by
maybe_canonicalize_mem_ref_addr which uses build3 instead of fold_build3
to build the BIT_FIELD_REF (probably not expecting simplification or
avoding constant folding on the LHS). Indeed using fold_build3 there
gets us
VIEW_CONVERT_EXPR<__int128 unsigned>(y) = x;
>From gcc-bugs-return-641870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 15:12:54 2019
Return-Path: <gcc-bugs-return-641870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18640 invoked by alias); 25 Apr 2019 15: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 18479 invoked by uid 48); 25 Apr 2019 15:12:50 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88809] do not use rep-scasb for inline strlen/memchr
Date: Thu, 25 Apr 2019 15:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88809-4-tCJHZQ6VPI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02726.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88809
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |10.0
>From gcc-bugs-return-641871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 15:32:14 2019
Return-Path: <gcc-bugs-return-641871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107794 invoked by alias); 25 Apr 2019 15:32:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107748 invoked by uid 55); 25 Apr 2019 15:32:10 -0000
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/90250] libphobos: segfault in runtime caused by unexpected GC of TLS data.
Date: Thu, 25 Apr 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: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw 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-90250-4-tPjFzAR1mM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90250-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90250-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02727.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90250
--- Comment #1 from ibuclaw at gcc dot gnu.org ---
Author: ibuclaw
Date: Thu Apr 25 15:31:35 2019
New Revision: 270576
URL: https://gcc.gnu.org/viewcvs?rev=270576&root=gcc&view=rev
Log:
libphobos: Fix segfault in runtime caused by unexpected GC of TLS data.
libphobos/ChangeLog:
2019-04-25 Iain Buclaw <ibuclaw@gdcproject.org>
PR d/90250
* libdruntime/gcc/sections/elf_shared.d (initTLSRanges): Populate
_tlsRanges in every startup thread.
* testsuite/libphobos.thread/thread.exp: Load libphobos-dg.exp.
* testsuite/libphobos.thread/tlsgc_sections.d: New test.
Added:
trunk/libphobos/testsuite/libphobos.thread/tlsgc_sections.d
Modified:
trunk/libphobos/ChangeLog
trunk/libphobos/libdruntime/gcc/sections/elf_shared.d
trunk/libphobos/testsuite/libphobos.thread/thread.exp
>From gcc-bugs-return-641872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 15:32:44 2019
Return-Path: <gcc-bugs-return-641872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108740 invoked by alias); 25 Apr 2019 15:32: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 108710 invoked by uid 48); 25 Apr 2019 15:32:40 -0000
From: "ibuclaw at gdcproject dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/90250] libphobos: segfault in runtime caused by unexpected GC of TLS data.
Date: Thu, 25 Apr 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: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gdcproject dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90250-4-rMjd5OIMzi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90250-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90250-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02728.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90250
Iain Buclaw <ibuclaw at gdcproject dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Iain Buclaw <ibuclaw at gdcproject dot org> ---
Done in r270576.
>From gcc-bugs-return-641873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 15:41:41 2019
Return-Path: <gcc-bugs-return-641873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14529 invoked by alias); 25 Apr 2019 15:41: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 14495 invoked by uid 48); 25 Apr 2019 15:41:38 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90036] [8/9 Regression] false positive: directive argument is null [-Werror=format-overflow=]
Date: Thu, 25 Apr 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-90036-4-BO2ZEytQld@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90036-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90036-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02729.txt.bz2
Content-length: 3207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90036
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
Target Milestone|8.4 |10.0
--- Comment #2 from Jeffrey A. Law <law at redhat dot com> ---
My tester had tripped over this a while back. I'd been meaning to dig into it
since it was clearly a false positive.
With the reduced testcase (I'll attach it shortly) the key path is blocks
2->9->4->6 which have the following contents:
;; basic block 2, loop depth 0
;; pred: ENTRY
_1 = vptr_14(D) == 0;
_2 = ownvptr_15(D) != 0;
_3 = _1 | _2;
if (_3 != 0)
goto <bb 9>; [67.00%]
else
goto <bb 3>; [33.00%]
;; basic block 9, loop depth 0
;; pred: 2
if (vptr_14(D) != 0)
goto <bb 4>; [33.33%]
else
goto <bb 8>; [66.67%]
;; basic block 4, loop depth 0
;; pred: 9
if (ownvptr_15(D) != 0)
goto <bb 5>; [100.00%]
else
goto <bb 6>; [0.00%]
;; basic block 6, loop depth 0
;; pred: 4
;; 3
# definition_36 = PHI <0(4), definition_17(3)>
# vstring_38 = PHI <0B(4), vstring_19(3)>
_5 = strlen (vstring_38);
_6 = _5 + 3;
vtable_21 = xmalloc (_6);
sprintf (vtable_21, "~%%%s", vstring_38);
if (definition_36 != 0)
goto <bb 7>; [97.40%]
else
goto <bb 8>; [2.60%]
We can obviously see the path 2->4->9->6 is not feasible, but DOM isn't going
to be able to make that determination. ie when we traverse 2->4 it knows that
_3 is true, but it doesn't know if that's because _1 is true or because _2 is
true and it's incapable of tracking the relationship between them.
DOM is going to thread the edge 4->6 to target bb8. This will result in the
path morphing a bit into 2->8->4->9. The key blocks look like this after DOM
has completed:
;; basic block 2, loop depth 0
;; pred: ENTRY
_1 = vptr_14(D) == 0;
_2 = ownvptr_15(D) != 0;
_3 = _1 | _2;
if (_3 != 0)
goto <bb 8>; [67.00%]
else
goto <bb 3>; [33.00%]
;; basic block 8, loop depth 0
;; pred: 2
if (vptr_14(D) != 0)
goto <bb 4>; [33.33%]
else
goto <bb 7>; [66.67%]
;; basic block 4, loop depth 0
;; pred: 8
if (_2 != 0)
goto <bb 5>; [100.00%]
else
goto <bb 9>; [0.00%]
;; basic block 9, loop depth 0
;; pred: 4
# definition_37 = PHI <0(4)>
# vstring_11 = PHI <0B(4)>
_33 = strlen (vstring_11);
_35 = _33 + 3;
vtable_31 = xmalloc (_35);
sprintf (vtable_31, "~%%%s", vstring_11);
goto <bb 7>; [100.00%]
bb9 is a clone of what was previously bb6, but it's isolated so that we
threading could change it without affecting the non-threaded path.
But the key issue remains, DOM can't track the relationship between vptr and
ownvptr.
This is actually the kind of thing I'd like to be able to use the predicate
analysis found in tree-ssa-uninit.c to fix.
Anyway, there's very very little chance this will be fixed for gcc-9.
Deferring out.
>From gcc-bugs-return-641874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 15:53:36 2019
Return-Path: <gcc-bugs-return-641874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91402 invoked by alias); 25 Apr 2019 15:53: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 91339 invoked by uid 48); 25 Apr 2019 15:53:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90249] [9 Regression] Code size regression on thumb2 due to sub-optimal register allocation starting with r265398
Date: Thu, 25 Apr 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: rtl-optimization
X-Bugzilla-Version: 9.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc short_desc everconfirmed
Message-ID: <bug-90249-4-qI87lNwQ1B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02730.txt.bz2
Content-length: 1145
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
CC| |jakub at gcc dot gnu.org,
| |segher at gcc dot gnu.org
Summary|[9 regression] Code size |[9 Regression] Code size
|regression on thumb2 due to |regression on thumb2 due to
|sub-optimal register |sub-optimal register
|allocation. |allocation starting with
| |r265398
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r265398. Doesn't look severe enough to block a release at this
point, a lot of code changed with that change.
>From gcc-bugs-return-641875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:02:17 2019
Return-Path: <gcc-bugs-return-641875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43633 invoked by alias); 25 Apr 2019 16:02:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43510 invoked by uid 48); 25 Apr 2019 16:02:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] [8/9 Regression] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: middle-end
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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90248-4-s51JoHYh6o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02731.txt.bz2
Content-length: 1369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
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> ---
(In reply to Richard Biener from comment #5)
> (In reply to Jakub Jelinek from comment #4)
> > Yeah, all those look quite questionable, -fno-signed-zeros doesn't mean 0.0
> > or -0.0 won't appear, just that it shouldn't matter if 0.0 or -0.0 appears.
>
> Yeah, it means that when a is 0. or -0. the behavior can either
> match 0. > 0 ? 1. : -1. or -0. > 0 ? 1. : -1. So probably the
> cases where we negate X are OK-ish in that regard?
Well, AFAIK 0. > 0 is 0 and -0. > 0 is also 0.
And similarly 0.0 >= 0 is 1 and -0.0 >= 0 is also 1. So the a > 0 ? 1.0 : -1.0
expression is completely insensitive to signed zeros and so is a >= 0 ? 1.0 :
-1.0. With the a > 0 ? 1.0 : -1.0 to copysign (1.0, a) transformation it is
also insensitive to sign of zero, but wrong for both -0.0 and 0.0. With the a
>= 0 ? 1.0 : -1.0 to copysign (1.0, a) it is correct for +0.0 and incorrect for
-0.0, so
what has been previously insensitive to the sign of zero is now sensitive to
it.
>From gcc-bugs-return-641876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:13:14 2019
Return-Path: <gcc-bugs-return-641876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77744 invoked by alias); 25 Apr 2019 16:13: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 77731 invoked by uid 89); 25 Apr 2019 16:13:14 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=1.5 required=5.0 testsºYES_50,BODY_8BITS,GARBLED_BODY,GIT_PATCH_2,GIT_PATCH_3,HTML_MESSAGE,MISSING_MID,RCVD_IN_PBL,RCVD_IN_XBL,TVD_SPACE_RATIO_MINFP autolearn=ham version=3.3.1 spammy=H*r:TCP, H*r:Unknown, H*r:183.129.55, H*c:alternative
X-HELO: lgni.com
Received: from Unknown (HELO lgni.com) (183.129.55.233) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Thu, 25 Apr 2019 16:13:13 +0000
Received: from SKY-20150219JSJ ([127.0.0.1]) by localhost via TCP with ESMTPA; Fri, 26 Apr 2019 00:13:06 +0800
MIME-Version: 1.0
From: zbozuh <zbozuh@lgni.com>
Sender: zbozuh <zbozuh@lgni.com>
To: gcc-bugs@gcc.gnu.org
Date: Thu, 25 Apr 2019 16:13:00 -0000
Subject: =?utf-8?B?Z2NjLWJ1Z3NAZ2NjLmdudS5vcmdGcXdwYQ==?Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-SW-Source: 2019-04/txt/msg02732.txt.bz2
Content-length: 350
Z2NjLWJ1Z3MmbmJzcDsmbmJzcDsmbmJzcDsrKysrKysrKysrK2RyTFN6Kysr
KysrKysrKysrDQrlvIDlkITlnLDmraPop4Tmma7pgJrlop7lgLznqI7npajv
vIzngrnkvJjmg6DvvIzljIXnnJ/jgIINCuivpueUte+8mi0t5p2o5bCP5aeQ
LS0tDQrmiYvmnLrvvJoxMzUgMjc2OCAzMDMxDQrkuJrliqFRUe+8mjI0NzU2
MjMxNDMNCisrKysrKysrKysrZHpHdllYRmtCKysrKysrKysrKysrKysrKysr
Kw0KMDoxM+etlueKtjs+UkRY5oeI54S26KqT5pmm5aeL
>From gcc-bugs-return-641877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:18:06 2019
Return-Path: <gcc-bugs-return-641877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 532 invoked by alias); 25 Apr 2019 16:18:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 457 invoked by uid 48); 25 Apr 2019 16:18:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 2019 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-90246-4-B2nRITcghM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02733.txt.bz2
Content-length: 3683
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's too late to change this now, but we could still improve the messages:
--- a/libstdc++-v3/include/std/variant
+++ b/libstdc++-v3/include/std/variant
@@ -1200,10 +1200,12 @@ namespace __variant
{
public:
bad_variant_access() noexcept : _M_reason("Unknown reason") { }
+
const char* what() const noexcept override
{ return _M_reason; }
private:
+ // Must only be called with a string literal
bad_variant_access(const char* __reason) : _M_reason(__reason) { }
const char* _M_reason;
@@ -1211,10 +1213,20 @@ namespace __variant
friend void __throw_bad_variant_access(const char* __what);
};
+ // Must only be called with a string literal
inline void
__throw_bad_variant_access(const char* __what)
{ _GLIBCXX_THROW_OR_ABORT(bad_variant_access(__what)); }
+ inline void
+ __throw_bad_variant_access(bool __valueless)
+ {
+ if (__valueless) [[__unlikely__]]
+ __throw_bad_variant_access("std::get: variant is valueless");
+ else
+ __throw_bad_variant_access("std::get: wrong index for variant");
+ }
+
template<typename... _Types>
class variant
: private __detail::__variant::_Variant_base<_Types...>,
@@ -1584,7 +1596,7 @@ namespace __variant
static_assert(_Np < sizeof...(_Types),
"The index should be in [0, number of alternatives)");
if (__v.index() != _Np)
- __throw_bad_variant_access("Unexpected index");
+ __throw_bad_variant_access(__v.valueless_by_exception());
return __detail::__variant::__get<_Np>(__v);
}
@@ -1595,7 +1607,7 @@ namespace __variant
static_assert(_Np < sizeof...(_Types),
"The index should be in [0, number of alternatives)");
if (__v.index() != _Np)
- __throw_bad_variant_access("Unexpected index");
+ __throw_bad_variant_access(__v.valueless_by_exception());
return __detail::__variant::__get<_Np>(std::move(__v));
}
@@ -1606,7 +1618,7 @@ namespace __variant
static_assert(_Np < sizeof...(_Types),
"The index should be in [0, number of alternatives)");
if (__v.index() != _Np)
- __throw_bad_variant_access("Unexpected index");
+ __throw_bad_variant_access(__v.valueless_by_exception());
return __detail::__variant::__get<_Np>(__v);
}
@@ -1617,7 +1629,7 @@ namespace __variant
static_assert(_Np < sizeof...(_Types),
"The index should be in [0, number of alternatives)");
if (__v.index() != _Np)
- __throw_bad_variant_access("Unexpected index");
+ __throw_bad_variant_access(__v.valueless_by_exception());
return __detail::__variant::__get<_Np>(std::move(__v));
}
@@ -1648,7 +1660,7 @@ namespace __variant
visit(_Visitor&& __visitor, _Variants&&... __variants)
{
if ((__variants.valueless_by_exception() || ...))
- __throw_bad_variant_access("Unexpected index");
+ __throw_bad_variant_access("std::visit: variant is valueless");
return __do_visit(std::forward<_Visitor>(__visitor),
std::forward<_Variants>(__variants)...);
@@ -1660,7 +1672,7 @@ namespace __variant
visit(_Visitor&& __visitor, _Variants&&... __variants)
{
if ((__variants.valueless_by_exception() || ...))
- __throw_bad_variant_access("Unexpected index");
+ __throw_bad_variant_access("std::visit<R>: variant is valueless");
if constexpr (std::is_void_v<_Res>)
(void) __do_visit<false, false>(std::forward<_Visitor>(__visitor),
>From gcc-bugs-return-641878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:23:36 2019
Return-Path: <gcc-bugs-return-641878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29158 invoked by alias); 25 Apr 2019 16:23:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21670 invoked by uid 48); 25 Apr 2019 16:23:32 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/89689] [7/8/9 regression] false warning -Wstringop-overflowDate: Thu, 25 Apr 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: tree-optimization
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-89689-4-sEM9xwjRS9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89689-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89689-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02734.txt.bz2
Content-length: 2158
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89689
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
Target Milestone|7.5 |10.0
--- Comment #3 from Jeffrey A. Law <law at redhat dot com> ---
It's almost certainly the case that we've duplicated the block with the call to
builtin_memcpy_chk so that we can thread jumps and remove the second if (p !=
__sb_slop) test.
In .forwprop2 we have:
;; basic block 4, loop depth 0
;; pred: 2
;; 3
_1 = __builtin_object_size (p_4(D), 0);
__builtin___memcpy_chk (p_4(D), "abcd", 4, _1);
if (p_4(D) != &__sb_slop)
goto <bb 5>; [70.00%]
else
goto <bb 6>; [30.00%]
Which is exactly what we'd expect. Then objsz2 runs resulting in:
;; basic block 4, loop depth 0
;; pred: 2
;; 3
_1 = __builtin_object_size (p_4(D), 0);
__builtin_memcpy (p_4(D), "abcd", 4);
if (p_4(D) != &__sb_slop)
goto <bb 5>; [70.00%]
else
goto <bb 6>; [30.00%]
What's happened here? Well, objsz evaluated the _b_o_s call and determined it
was undeterminable (-1) and transformed the memcpy_chk to a standard memcpy.
The key point is we had an indeterminable size and transformed the _chk into a
standard memcpy.
Jump threading comes along and duplicates the block. As a result on the
duplicated path we'll know that p_4 points to sb_slop and thus has a size of 1.
That causes the memcpy of 4 bytes to trigger the warning.
I would hazard a guess that the original user code didn't have the calls to
_builtin_object_size and __builtin__memcpy_chk, but that those instead came in
via the glibc header files.
This certainly isn't going to be fixed for gcc-9 (possibly ever).
And FWIW, I think marking things with TREE_NO_WARNING at the time we convert
the memcpy_chk to a memcpy would be fundamentally wrong in the case where the
__b_o_s call returned -1 (indeterminate size). It'll hide real bugs.
>From gcc-bugs-return-641879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:27:54 2019
Return-Path: <gcc-bugs-return-641879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40289 invoked by alias); 25 Apr 2019 16:27:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40252 invoked by uid 48); 25 Apr 2019 16:27:51 -0000
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90251] New: missing spaces in string literals
Date: Thu, 25 Apr 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: roland.illig at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-90251-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02735.txt.bz2
Content-length: 3012
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90251
Bug ID: 90251
Summary: missing spaces in string literals
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: roland.illig at gmx dot de
Target Milestone: ---
Created attachment 46246
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46246&action=edit
linter for string literals
From engtype.c:
printf ("\t -D | --debug "
" \t# Give debug output to debug %s itself.\n", progname);
Splitting the string literal in the middle of two spaces looks arbitrary. This
applies to all string literals in print_usage.
From tree-ssa-loop-ch.c:
fprintf (dump_file,
" Not duplicating bb %i: condition based on non-IV loop"
"variant.\n", header->index);
From tree-vect-data-refs.c:
return opt_result::failure_at (stmt_info->stmt,
"not vectorized:"
"not suitable for strided load %G",
stmt_info->stmt);
From locales.c:
"US", "United-States"
"UY", "Uruguay",
The comma is missing at the end of the upper line.
From arc.c:
fprintf (dump_file, ";; loop %d has a control like last insn;"
"add a nop\n",
loop->loop_no);
fprintf (dump_file, ";; loop %d has a label as last insn;"
"add a nop\n",
loop->loop_no);
fprintf (dump_file, ";; loop %d has no fallthru edge jumping"
"into the loop\n",
loop->loop_no);
From rx.c:
warning (0, "unrecognized control register number: %d"
"- using %<psw%>", (int) INTVAL (op));
From decl.c:
error ("too many braces around scalar initializer"
"for type %qT", type);
From parser.c:
pedwarn (DECL_SOURCE_LOCATION (decl), OPT_Wpedantic,
"ISO C++ did not adopt string literal operator templa"
"tes taking an argument pack of characters");
This one is different. There's not really a space missing, but proper line
breaking. Breaking the line in the middle of a word is really ugly.
From parser.h:
} GTY((desc ("(%1.type == CPP_TEMPLATE_ID)"
"|| (%1.type == CPP_NESTED_NAME_SPECIFIER)"
"|| (%1.type == CPP_DECLTYPE)"))) u;
If there's a space after the || operator, there should be one before the
operator, too.
From tree.c:
w = warning_at (loc, OPT_Wabi, "%<-fabi-version=12%> (GCC 8.1) accident"
"ally changes the calling convention for %qT", t);
Nothing missing again, only the line breaking is ugly, as pointed out above.
----
I found all the above issues by manually inspecting the output of the attached
linter. That linter could be placed in the contrib/ folder.
>From gcc-bugs-return-641880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:40:49 2019
Return-Path: <gcc-bugs-return-641880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69303 invoked by alias); 25 Apr 2019 16:40:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69286 invoked by uid 48); 25 Apr 2019 16:40:46 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90251] missing spaces in string literals
Date: Thu, 25 Apr 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: other
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-90251-4-QLc9EXbiij@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90251-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90251-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02736.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90251
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> From parser.h:
} GTY((desc ("(%1.type == CPP_TEMPLATE_ID)"
"|| (%1.type == CPP_NESTED_NAME_SPECIFIER)"
"|| (%1.type == CPP_DECLTYPE)"))) u;
> If there's a space after the || operator, there should be one before the operator, too.
This one does not matter that much. Because it is C code in the end.
>From gcc-bugs-return-641881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:41:04 2019
Return-Path: <gcc-bugs-return-641881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70148 invoked by alias); 25 Apr 2019 16:41:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70090 invoked by uid 48); 25 Apr 2019 16:41:01 -0000
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug translation/90149] diagnostics containing BIT_FIELD_REF don't conform to diagnostics guideline
Date: Thu, 25 Apr 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: translation
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: roland.illig 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:
Message-ID: <bug-90149-4-7qMynLoA7H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90149-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90149-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02737.txt.bz2
Content-length: 540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90149
--- Comment #7 from Roland Illig <roland.illig at gmx dot de> ---
(In reply to Richard Biener from comment #6)
> IMNSHO the IL checker "errors" should continue to use GCC terms since they
> check the GIMPLE intermediate language. They also shouldn't necessarily be
> translated (though they may end up user-facing if they turn on -fchecking).
If you want to join the discussion about whether internal compiler errors
should be translated, I'm happy to invite you to bug 80055. ;)
>From gcc-bugs-return-641882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 16:54:26 2019
Return-Path: <gcc-bugs-return-641882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101128 invoked by alias); 25 Apr 2019 16: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 101074 invoked by uid 48); 25 Apr 2019 16:54:22 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90252] New: PSTL test failures
Date: Thu, 25 Apr 2019 16:54: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: 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-90252-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02738.txt.bz2
Content-length: 5385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90252
Bug ID: 90252
Summary: PSTL test failures
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
On Fedora 29/x86-64, I installed tbb-devel-2018.5-2.fc29.x86_64, but
not tbb-devel-2018.5-2.fc29.i686,
$ make check -j 28 -k RUNTESTFLAGS="--target_board='unix{-m32,}'"
gave
FAIL: 20_util/specialized_algorithms/pstl/uninitialized_construct.cc (test for
e
xcess errors)
FAIL: 20_util/specialized_algorithms/pstl/uninitialized_copy_move.cc (test for
e
xcess errors)
FAIL: 20_util/specialized_algorithms/pstl/uninitialized_fill_destroy.cc (test
fo
r excess errors)
FAIL: 25_algorithms/pstl/alg_merge/inplace_merge.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_merge/merge.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/copy_if.cc (test for excess
er
rors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/copy_move.cc (test for excess
errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/fill.cc (test for excess
error
s)
FAIL: 25_algorithms/pstl/alg_modifying_operations/generate.cc (test for excess
e
rrors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/is_partitioned.cc (test for
ex
cess errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/partition.cc (test for excess
errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/partition_copy.cc (test for
ex
cess errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/remove.cc (test for excess
err
ors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/remove_copy.cc (test for
exces
s errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/replace.cc (test for excess
er
rors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/replace_copy.cc (test for
exce
ss errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/rotate.cc (test for excess
err
ors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/rotate_copy.cc (test for
exces
s errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/swap_ranges.cc (test for
exces
s errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/transform_binary.cc (test for
excess errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/transform_unary.cc (test for
e
xcess errors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/unique.cc (test for excess
err
ors)
FAIL: 25_algorithms/pstl/alg_modifying_operations/unique_copy_equal.cc (test
for
excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/adjacent_find.cc (test for excess
erro
rs)
FAIL: 25_algorithms/pstl/alg_nonmodifying/all_of.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/any_of.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/count.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/equal.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/find.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/find_end.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/find_first_of.cc (test for excess
erro
rs)
FAIL: 25_algorithms/pstl/alg_nonmodifying/find_if.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/for_each.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/mismatch.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/none_of.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/nth_element.cc (test for excess
errors
)
FAIL: 25_algorithms/pstl/alg_nonmodifying/reverse.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_nonmodifying/reverse_copy.cc (test for excess
error
s)
FAIL: 25_algorithms/pstl/alg_nonmodifying/search_n.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/includes.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/is_heap.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/is_sorted.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/lexicographical_compare.cc (test for
excess
errors)
FAIL: 25_algorithms/pstl/alg_sorting/minmax_element.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/partial_sort.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/partial_sort_copy.cc (test for excess
error
s)
FAIL: 25_algorithms/pstl/alg_sorting/set.cc (test for excess errors)
FAIL: 25_algorithms/pstl/alg_sorting/sort.cc (test for excess errors)
FAIL: 26_numerics/pstl/numeric_ops/adjacent_difference.cc (test for excess
error
s)
FAIL: 26_numerics/pstl/numeric_ops/reduce.cc (test for excess errors)
FAIL: 26_numerics/pstl/numeric_ops/scan.cc (test for excess errors)
FAIL: 26_numerics/pstl/numeric_ops/transform_reduce.cc (test for excess errors)
FAIL: 26_numerics/pstl/numeric_ops/transform_scan.cc (test for excess errors)
Since there is no tbb-devel-2018.5-2.fc29.i686, -m32 failed:
/usr/local/bin/ld: cannot find -ltbb^M
collect2: error: ld returned 1 exit status^M
compiler exited with status 1
FAIL: 25_algorithms/pstl/alg_nonmodifying/for_each.cc (test for excess errors)
Excess errors:
/usr/local/bin/ld: cannot find -ltbb
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-641883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:01:26 2019
Return-Path: <gcc-bugs-return-641883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110922 invoked by alias); 25 Apr 2019 17: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 110865 invoked by uid 55); 25 Apr 2019 17:01:18 -0000
From: "hjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89929-4-IDLNNKre42@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02739.txt.bz2
Content-length: 2017
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #25 from hjl at gcc dot gnu.org <hjl at gcc dot gnu.org> ---
Author: hjl
Date: Thu Apr 25 17:00:28 2019
New Revision: 270578
URL: https://gcc.gnu.org/viewcvs?rev=270578&root=gcc&view=rev
Log:
x86: Update message for target_clones and unsupported ISAs
Before AVX512F, processors with the newer ISAs also support the older
ISAs, i.e., AVX2 processors also support AVX and SSE4, SSE4 processors
also support SSSE3, ... After AVX512F, an AVX512XX processor may not
support AVX512YY. It means AVX512XX features, except for AVX512F, can't
be used to decide priority in target_clones.
This patch updates error message for ISAs with P_ZERO priority. It also
merges _feature_list into _isa_names_table and marks ISAs, which have
unknown priority, with P_ZERO so that we only need to update one place
to add a new ISA feature.
gcc/
2019-04-25 H.J. Lu <hongjiu.lu@intel.com>
PR target/89929
* config/i386/i386.c (feature_priority): Moved to file scope.
(processor_features): Likewise.
(processor_model): Likewise.
(_arch_names_table): Likewise.
(arch_names_table): Likewise.
(_feature_list): Removed.
(feature_list): Likewise.
(_isa_names_table): Moved to file scope. Add priority.
(isa_names_table): Likewise.
(get_builtin_code_for_version): Replace feature_list with
isa_names_table. Update error message for P_ZERO priority.
gcc/testsuite/
2019-04-25 Martin Liska <mliska@suse.cz>
H.J. Lu <hongjiu.lu@intel.com>
PR target/89929
* g++.target/i386/mv28.C: New test.
* gcc.target/i386/mvc14.c: Likewise.
* g++.target/i386/pr57362.C: Updated.
Added:
trunk/gcc/testsuite/g++.target/i386/mv28.C
trunk/gcc/testsuite/gcc.target/i386/mvc14.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.target/i386/pr57362.C
>From gcc-bugs-return-641884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:05:22 2019
Return-Path: <gcc-bugs-return-641884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118815 invoked by alias); 25 Apr 2019 17: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 118752 invoked by uid 48); 25 Apr 2019 17:05:17 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90248] [8/9 Regression] larger than 0 compare fails with -ffinite-math-only -funsafe-math-optimizations
Date: Thu, 25 Apr 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: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90248-4-Iwxfl6tvNg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90248-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02740.txt.bz2
Content-length: 257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90248
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Yes it does look like I messed up. I copied an optimization from LLVM so I
think they also mess up a similar way (though differently).
>From gcc-bugs-return-641885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:25:07 2019
Return-Path: <gcc-bugs-return-641885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121066 invoked by alias); 25 Apr 2019 17: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 121019 invoked by uid 48); 25 Apr 2019 17:25:03 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90253] New: no warning for cv-qualified selectors in _Generic
Date: Thu, 25 Apr 2019 17: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: diagnostic
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-90253-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02741.txt.bz2
Content-length: 891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90253
Bug ID: 90253
Summary: no warning for cv-qualified selectors in _Generic
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: amonakov at gcc dot gnu.org
Target Milestone: ---
Controlling expression in _Generic undergoes lvalue conversion, so it will have
const/volatile qualifiers stripped. Therefore, a qualified selector cannot
possibly match, and it might make sense to warn when a user writes one.
In the following example the function returns 0, even though the user might
have expected to distinguish 'char' vs. 'const char':
int f(const char *c)
{
return _Generic(*c, const char: 1, char: 0);
}
>From gcc-bugs-return-641886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:27:21 2019
Return-Path: <gcc-bugs-return-641886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123128 invoked by alias); 25 Apr 2019 17:27: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 123103 invoked by uid 48); 25 Apr 2019 17:27:17 -0000
From: "leni536 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90254] New: ice on aggregate initialization of unmovable base
Date: Thu, 25 Apr 2019 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: leni536 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-90254-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02742.txt.bz2
Content-length: 1502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90254
Bug ID: 90254
Summary: ice on aggregate initialization of unmovable base
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: leni536 at gmail dot com
Target Milestone: ---
The compiler bumps into an internal compiler error on the following, valid
code:
//aggregate base class
struct A1 {
A1() = default;
A1(const A1&) = delete;
A1(A1&&) = delete;
};
//non-aggregate base class
struct A2 {
A2() {};
A2(const A2&) = delete;
A2(A2&&) = delete;
};
//aggregate derived classes
struct B1 : A1 {};
struct B2 : A2 {};
A1 f1() {
return A1();
}
A2 f2() {
return A2();
}
int main() {
A1 a1{f1()}; // OK
B1 b1_1{{}}; // OK
B1 b1_2{A1{}}; // OK
B1 b1_3{A1()}; // OK
B1 b1_4{f1()}; // ICE
A2 a2{f2()}; // OK
B2 b2_1{{}}; // OK
B2 b2_2{A2{}}; // OK
B2 b2_3{A2()}; // OK
B2 b2_4{f2()}; // ICE
}
It is valid because each element of the aggregate is copy-initialized from the
corresponding initializer-clause. If it is a prvalue then no temporary is
materialized.
Some argue that this is a defect in the standard and the code above should be
rejected:
https://bugs.llvm.org/show_bug.cgi?id=34516
>From gcc-bugs-return-641887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:27:32 2019
Return-Path: <gcc-bugs-return-641887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123803 invoked by alias); 25 Apr 2019 17:27:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123778 invoked by uid 48); 25 Apr 2019 17:27:29 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90255] New: [9 regression] r266385 caused code size regressions on Arm, thumb and thumb2
Date: Thu, 25 Apr 2019 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-90255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02743.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90255
Bug ID: 90255
Summary: [9 regression] r266385 caused code size regressions on
Arm, thumb and thumb2
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rearnsha at gcc dot gnu.org
Target Milestone: ---
Created attachment 46247
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46247&action=edit
testcase
Overall r266385 caused
0.16% regression on Arm and thumb1 -Os
0.08% regression on thumb2 -Os.
when building CSiBE
Some non-trivial files, however, regressed significantly, some by over 3%.
For example, teem-1.6.0-src src/dye/test/bow regresses by 3.36% on Arm due to
additional spills and the need for another register to be allocated.
>From gcc-bugs-return-641888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:34:40 2019
Return-Path: <gcc-bugs-return-641888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47192 invoked by alias); 25 Apr 2019 17:34:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35885 invoked by uid 48); 25 Apr 2019 17:34:36 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90255] [9 regression] r266385 caused code size regressions on Arm, thumb and thumb2
Date: Thu, 25 Apr 2019 17:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-90255-4-BRliWlrQh6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02744.txt.bz2
Content-length: 7459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90255
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ramana.radhakrishnan at arm dot co
| |m, vmakarov at redhat dot com,
| |wdijkstr at arm dot com
--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
[committed too early]
It looks like a 64-bit constant 0 is held over a function call when the code
could just initialize the registers directly.
Code before commit:
main:
@ Function supports interworking.
@ args = 0, pretend = 0, frame = 24
@ frame_needed = 0, uses_anonymous_args = 0
push {r4, r5, r6, r7, r8, r9, r10, lr} // 8 registers saved.
ldr r3, [r1]
ldr r5, .L14
cmp r0, #4
mov r4, r1
str r3, [r5]
sub sp, sp, #48 // 48 bytes stack space
blne usage
.L2:
ldmib r4, {r6, r8}
ldr r1, .L14+4
mov r0, r6
add r2, sp, #28
ldr r7, [r4, #12]
bl sscanf
cmp r0, #1
beq .L3
ldr r3, .L14+8
ldr r0, [r3]
mov r3, r6
ldr r2, [r5]
ldr r1, .L14+12
.L12:
ldr r0, [r0, #8]
bl fprintf
mov r0, #1
.L13:
bl exit
.L3:
mov r0, r8
ldr r1, .L14+16
add r2, sp, #44
bl sscanf
cmp r0, #1
beq .L4
ldr r3, .L14+8
ldr r2, [r5]
ldr r0, [r3]
ldr r1, .L14+20
mov r3, r8
b .L12
.L4:
mov r0, r7
ldr r1, .L14+24
bl fopen
subs r4, r0, #0
bne .L5
ldr r3, .L14+8
ldr r2, [r5]
ldr r0, [r3]
ldr r1, .L14+28
mov r3, r7
b .L12
.L5:
mov r1, r4
ldr r0, .L14+32
bl fputs
mov r5, #0
mov r8, #1065353216
ldr r9, .L14+36
.L6:
ldr r10, [sp, #28]
cmp r10, r5
bgt .L7
mov r0, r4
bl fclose
mov r0, #0
b .L13
.L7:
mov r0, r5
bl __aeabi_i2d
mov r6, r0
mov r0, r10
mov r7, r1
bl __aeabi_i2d
mov r2, r0
mov r3, r1
mov r0, r6
mov r1, r7
bl __aeabi_ddiv
mov r2, #0
mov r3, #0
bl __aeabi_dadd
bl __aeabi_d2f
mov r6, r0
mov r3, r0
add r2, sp, #40
add r1, sp, #36
add r0, sp, #32
str r8, [sp, #4] @ float
str r8, [sp] @ float
bl dyeHSVtoRGB
mov r0, r6
bl __aeabi_f2d
ldr r10, [sp, #44] @ float
mov r6, r0
mov r7, r1
mov r0, r10
ldr r1, [sp, #40] @ float
bl __aeabi_fmul
bl __aeabi_f2d
str r0, [sp, #16]
str r1, [sp, #20]
ldr r1, [sp, #36] @ float
mov r0, r10
bl __aeabi_fmul
bl __aeabi_f2d
str r0, [sp, #8]
str r1, [sp, #12]
ldr r1, [sp, #32] @ float
mov r0, r10
bl __aeabi_fmul
bl __aeabi_f2d
mov r2, r6
stm sp, {r0-r1}
mov r3, r7
mov r1, r9
mov r0, r4
bl fprintf
add r5, r5, #1
b .L6
after r 266385
main:
@ Function supports interworking.
@ args = 0, pretend = 0, frame = 32
@ frame_needed = 0, uses_anonymous_args = 0
push {r4, r5, r6, r7, r8, r9, r10, fp, lr} // 9 regs saved
ldr r3, [r1]
ldr r5, .L14
cmp r0, #4
mov r4, r1
str r3, [r5]
sub sp, sp, #60 // 60 bytes stack space
blne usage
.L2:
ldmib r4, {r6, r8}
ldr r1, .L14+4
mov r0, r6
add r2, sp, #36
ldr r7, [r4, #12]
bl sscanf
cmp r0, #1
beq .L3
ldr r3, .L14+8
ldr r0, [r3]
mov r3, r6
ldr r2, [r5]
ldr r1, .L14+12
.L12:
ldr r0, [r0, #8]
bl fprintf
mov r0, #1
.L13:
bl exit
.L3:
mov r0, r8
ldr r1, .L14+16
add r2, sp, #52
bl sscanf
cmp r0, #1
beq .L4
ldr r3, .L14+8
ldr r2, [r5]
ldr r0, [r3]
ldr r1, .L14+20
mov r3, r8
b .L12
.L4:
mov r0, r7
ldr r1, .L14+24
bl fopen
subs r4, r0, #0
bne .L5
ldr r3, .L14+8
ldr r2, [r5]
ldr r0, [r3]
ldr r1, .L14+28
mov r3, r7
b .L12
.L5:
mov r1, r4
ldr r0, .L14+32
bl fputs
mov r5, #0
mov r8, #0 // Additional register initialization
mov r9, #0 // Additional register initialization
mov r10, #1065353216
ldr fp, .L14+36
.L6:
ldr r3, [sp, #36]
cmp r3, r5
bgt .L7
mov r0, r4
bl fclose
mov r0, #0
b .L13
.L7:
mov r0, r5
str r3, [sp, #24]
bl __aeabi_i2d
ldr r3, [sp, #24]
mov r6, r0
mov r0, r3
mov r7, r1
bl __aeabi_i2d
mov r2, r0
mov r3, r1
mov r0, r6
mov r1, r7
bl __aeabi_ddiv
mov r2, r8 // r8,r9 are never changed, and always 0, just use
immediate value
mov r3, r9
bl __aeabi_dadd
bl __aeabi_d2f
mov r6, r0
mov r3, r0
add r2, sp, #48
add r1, sp, #44
add r0, sp, #40
str r10, [sp, #4] @ float
str r10, [sp] @ float
bl dyeHSVtoRGB
mov r0, r6
bl __aeabi_f2d
mov r2, r0
mov r3, r1
ldr r7, [sp, #52] @ float
ldr r1, [sp, #48] @ float
mov r0, r7
str r2, [sp, #24]
str r3, [sp, #28]
bl __aeabi_fmul
bl __aeabi_f2d
str r0, [sp, #16]
str r1, [sp, #20]
ldr r1, [sp, #44] @ float
mov r0, r7
bl __aeabi_fmul
bl __aeabi_f2d
str r0, [sp, #8]
str r1, [sp, #12]
ldr r1, [sp, #40] @ float
mov r0, r7
bl __aeabi_fmul
bl __aeabi_f2d
add r3, sp, #24
ldmia r3, {r2-r3}
stm sp, {r0-r1}
mov r1, fp
mov r0, r4
bl fprintf
add r5, r5, #1
b .L6
>From gcc-bugs-return-641889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:37:22 2019
Return-Path: <gcc-bugs-return-641889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95647 invoked by alias); 25 Apr 2019 17: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 84517 invoked by uid 48); 25 Apr 2019 17:37:18 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90255] [9 regression] r266385 caused code size regressions on Arm, thumb and thumb2
Date: Thu, 25 Apr 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: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90255-4-XDv1Sk2Ovp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02745.txt.bz2
Content-length: 317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90255
--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Command to reproduce
cc1 -fpreprocessed bow.i -quiet -dumpbase bow.i -marm -mcpu=arm7tdmi
-march=armv4t -auxbase-strip test/bow.o -Os -w -version -fno-short-enums
-fgnu89-inline -o bow.s
>From gcc-bugs-return-641890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:45:00 2019
Return-Path: <gcc-bugs-return-641890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2306 invoked by alias); 25 Apr 2019 17:45:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2247 invoked by uid 48); 25 Apr 2019 17:44:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90255] [9 regression] r266385 caused code size regressions on Arm, thumb and thumb2
Date: Thu, 25 Apr 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: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
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 target_milestone
Message-ID: <bug-90255-4-cmvCYcQBC1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02746.txt.bz2
Content-length: 416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90255
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |9.0
>From gcc-bugs-return-641891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:50:50 2019
Return-Path: <gcc-bugs-return-641891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31359 invoked by alias); 25 Apr 2019 17:50:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31301 invoked by uid 48); 25 Apr 2019 17:50:46 -0000
From: "jrtc27 at jrtc27 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/87338] gcc 8.2 fails to bootstrap on ia64
Date: Thu, 25 Apr 2019 17:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jrtc27 at jrtc27 dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87338-4-QVUpJzplQ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87338-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02747.txt.bz2
Content-length: 723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87338
--- Comment #9 from James Clarke <jrtc27 at jrtc27 dot com> ---
(In reply to James Clarke from comment #6)
> Created attachment 46245 [details]
> Proposed patch
>
> Currently performing a test build with this patch, but applying
> `s/^.LBI[0-9]*:$/[&]/g` to the stage2 (the one with debug info enabled)
> assembly for one of the differing files fixed the differences to the stage3
> file, so I'm confident this will fix it (assuming my change actually
> compiles).
Patch confirmed to work locally (also, stage2 and stage3 should be swapped in
the above comment, since stage2 is the one that *disables* debug info). I will
send it to the mailing list shortly.
>From gcc-bugs-return-641892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:56:00 2019
Return-Path: <gcc-bugs-return-641892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39463 invoked by alias); 25 Apr 2019 17: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 39428 invoked by uid 48); 25 Apr 2019 17:55:57 -0000
From: "nulano at nulano dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90256] New: Optimizer with interrupt routines
Date: Thu, 25 Apr 2019 17:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nulano at nulano dot eu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-90256-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02748.txt.bz2
Content-length: 1284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256
Bug ID: 90256
Summary: Optimizer with interrupt routines
Product: gcc
Version: 8.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nulano at nulano dot eu
Target Milestone: ---
Created attachment 46248
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46248&action=edit
verbose compiler output (MSYS2 GCC 8.3.0)
Enabling optimizer (either -Os or -O2) triggers error "interrupt service
routine can't be called directly" when two interrupt routines have identical
code.
Code to reproduce:
int rand();
int x = 0;
__attribute((interrupt)) void isr1(void*) {
for (int i = 0; i < 10; i++)
x ^= rand();
}
// isr2 is identical to isr1
__attribute((interrupt)) void isr2(void*) {
for (int i = 0; i < 10; i++)
x ^= rand();
}
- compile with "g++ -mgeneral-regs-only -S" -> works
- compile with "g++ -mgeneral-regs-only -S -Os" -> error
Tested on:
- Windows 7 64-bit MSYS2-W64-X86_64 GCC 7.3.0
- Windows 7 64-bit MSYS2-W64-X86_64 GCC 8.3.0
- Linux Mint / Ubuntu GCC 7.3.0
>From gcc-bugs-return-641893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:56:51 2019
Return-Path: <gcc-bugs-return-641893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41854 invoked by alias); 25 Apr 2019 17:56:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41818 invoked by uid 48); 25 Apr 2019 17:56:48 -0000
From: "tavianator at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 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: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tavianator 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-90246-4-fUw1ptyM1h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02749.txt.bz2
Content-length: 586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
Tavian Barnes <tavianator at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tavianator at gmail dot com
--- Comment #2 from Tavian Barnes <tavianator at gmail dot com> ---
> It's too late to change this now, but we could still improve the messages
Would it be ABI compatible to make a new exception type that derives from
std::bad_variant_access, and throw that instead?
>From gcc-bugs-return-641894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:57:53 2019
Return-Path: <gcc-bugs-return-641894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58831 invoked by alias); 25 Apr 2019 17:57:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56592 invoked by uid 48); 25 Apr 2019 17:57:49 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90255] [9 regression] r266385 caused code size regressions on Arm, thumb and thumb2
Date: Thu, 25 Apr 2019 17:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-90255-4-ZW6XKqBG0n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90255-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02750.txt.bz2
Content-length: 1566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90255
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization, ra
--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
If the same testcase is compiled with the additional options -mfpu=vfp
-mfloat-abi=softfp then we also see an example of some poor register allocation
leading to additional spills.
Before the patch we have
ldmib r4, {r6, r8} // r6 callee saved, so no need to spill
ldr r1, .L14+12
mov r0, r6
add r2, sp, #28
ldr r7, [r4, #12]
bl sscanf
cmp r0, #1
beq .L3
ldr r3, .L14+16
ldr r0, [r3]
mov r3, r6 // Now we can copy r6 into r3
ldr r2, [r5]
and afterwards
ldmib r4, {r3, r8} // r3 call-clobbered...
ldr r1, .L14+12
mov r0, r3
add r2, sp, #36
ldr r7, [r4, #12]
str r3, [sp, #28] // So must spill here
bl sscanf
cmp r0, #1
beq .L3
ldr r2, .L14+16
ldr r3, [sp, #28] // and reload it again here
ldr r0, [r2]
ldr r1, .L14+20
ldr r2, [r5]
As far as I can see r6 is not live in the new version of the code, so this
looks just like a poor choice of register.
>From gcc-bugs-return-641895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 17:59:31 2019
Return-Path: <gcc-bugs-return-641895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70692 invoked by alias); 25 Apr 2019 17:59: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 70633 invoked by uid 55); 25 Apr 2019 17:59:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89765] [9 Regression] Multiple problems with vec-insert implementation on PowerPC
Date: Thu, 25 Apr 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: middle-end
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: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89765-4-sGkdw2HvZa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02751.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Apr 25 17:58:56 2019
New Revision: 270579
URL: https://gcc.gnu.org/viewcvs?rev=270579&root=gcc&view=rev
Log:
PR middle-end/89765
* gimplify.c (gimplify_expr): Avoid turning a lvalue
VIEW_CONVERT_EXPR into one operating on an rvalue.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/gimplify.c
>From gcc-bugs-return-641896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:08:41 2019
Return-Path: <gcc-bugs-return-641896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32240 invoked by alias); 25 Apr 2019 18:08: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 32189 invoked by uid 48); 25 Apr 2019 18:08:38 -0000
From: "nulano at nulano dot eu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90256] Optimizer with interrupt routines
Date: Thu, 25 Apr 2019 18:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nulano at nulano dot eu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-90256-4-2A3nPorwM5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90256-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90256-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02752.txt.bz2
Content-length: 220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90256
--- Comment #1 from nulano at nulano dot eu ---
Created attachment 46249
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46249&action=edit
code to reproduce
>From gcc-bugs-return-641898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:08:50 2019
Return-Path: <gcc-bugs-return-641898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33058 invoked by alias); 25 Apr 2019 18:08: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 32899 invoked by uid 55); 25 Apr 2019 18:08:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90078] [7/8 Regression] ICE with deep templates caused by overflow
Date: Thu, 25 Apr 2019 18:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90078-4-x4AHEbjKnD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90078-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90078-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02754.txt.bz2
Content-length: 826
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90078
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Apr 25 18:08:14 2019
New Revision: 270583
URL: https://gcc.gnu.org/viewcvs?rev=270583&root=gcc&view=rev
Log:
PR tree-optimization/90240
Revert:
2019-04-23 Bin Cheng <bin.cheng@linux.alibaba.com>
PR tree-optimization/90078
* tree-ssa-loop-ivopts.c (comp_cost::operator +,-,+=,-+,/=,*=): Add
checks for infinite_cost overflow.
* gcc/testsuite/g++.dg/tree-ssa/pr90078.C: New test.
Removed:
branches/gcc-9-branch/gcc/testsuite/g++.dg/tree-ssa/pr90078.C
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/testsuite/ChangeLog
branches/gcc-9-branch/gcc/tree-ssa-loop-ivopts.c
>From gcc-bugs-return-641897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:08:49 2019
Return-Path: <gcc-bugs-return-641897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33003 invoked by alias); 25 Apr 2019 18:08:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32889 invoked by uid 55); 25 Apr 2019 18:08:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [9 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 2019 18:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90240-4-b4XkuqXzJg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02753.txt.bz2
Content-length: 825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Apr 25 18:08:14 2019
New Revision: 270583
URL: https://gcc.gnu.org/viewcvs?rev=270583&root=gcc&view=rev
Log:
PR tree-optimization/90240
Revert:
2019-04-23 Bin Cheng <bin.cheng@linux.alibaba.com>
PR tree-optimization/90078
* tree-ssa-loop-ivopts.c (comp_cost::operator +,-,+=,-+,/=,*=): Add
checks for infinite_cost overflow.
* gcc/testsuite/g++.dg/tree-ssa/pr90078.C: New test.
Removed:
branches/gcc-9-branch/gcc/testsuite/g++.dg/tree-ssa/pr90078.C
Modified:
branches/gcc-9-branch/gcc/ChangeLog
branches/gcc-9-branch/gcc/testsuite/ChangeLog
branches/gcc-9-branch/gcc/tree-ssa-loop-ivopts.c
>From gcc-bugs-return-641899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:20:38 2019
Return-Path: <gcc-bugs-return-641899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58397 invoked by alias); 25 Apr 2019 18:20:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58340 invoked by uid 48); 25 Apr 2019 18:20:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90240] [10 Regression] ICE in try_improve_iv_set, at tree-ssa-loop-ivopts.c:6694
Date: Thu, 25 Apr 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: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: amker at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-90240-4-WXCtfMvj4x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02755.txt.bz2
Content-length: 740
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90240
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.0 |10.0
Summary|[9/10 Regression] ICE in |[10 Regression] ICE in
|try_improve_iv_set, at |try_improve_iv_set, at
|tree-ssa-loop-ivopts.c:6694 |tree-ssa-loop-ivopts.c:6694
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Temporarily handled on gcc-9-branch through reversion. Once fixed for good on
the trunk, the reversion should be undone and proper fix applied on top of
that.
>From gcc-bugs-return-641900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:21:41 2019
Return-Path: <gcc-bugs-return-641900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59681 invoked by alias); 25 Apr 2019 18:21: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 59638 invoked by uid 48); 25 Apr 2019 18:21:37 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90249] [9 Regression] Code size regression on thumb2 due to sub-optimal register allocation starting with r265398
Date: Thu, 25 Apr 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: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-90249-4-CW3ozYVvnH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02756.txt.bz2
Content-length: 876
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[9/10 Regression] Code size |[9 Regression] Code size
|regression on thumb2 due to |regression on thumb2 due to
|sub-optimal register |sub-optimal register
|allocation starting with |allocation starting with
|r265398 |r265398
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
What difference is there on some code of significant size? Do you see
regressions then?
Of course there are some tiny examples where it now does worse, just like
there are examples where it now does better.
>From gcc-bugs-return-641901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:47:40 2019
Return-Path: <gcc-bugs-return-641901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122474 invoked by alias); 25 Apr 2019 18:47: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 122422 invoked by uid 48); 25 Apr 2019 18:47:36 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libobjc/89586] warning: cast between incompatible function types when building libobjc
Date: Thu, 25 Apr 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: libobjc
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: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89586-4-g43VUu0Z9V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89586-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89586-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02757.txt.bz2
Content-length: 313
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89586
--- Comment #5 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Andrew Pinski from comment #3)
> Let me see what I can do this weekend.
The weekend came and went... Is it still possible to fix these annoying new
warnings before the release?
>From gcc-bugs-return-641902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:51:38 2019
Return-Path: <gcc-bugs-return-641902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126603 invoked by alias); 25 Apr 2019 18:51: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 126563 invoked by uid 48); 25 Apr 2019 18:51:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 2019 18:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-90246-4-IDPQy5QRNI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02758.txt.bz2
Content-length: 178
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes. We can do that at some point in the future, not now.
>From gcc-bugs-return-641903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 18:52:01 2019
Return-Path: <gcc-bugs-return-641903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127784 invoked by alias); 25 Apr 2019 18:52:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127312 invoked by uid 48); 25 Apr 2019 18:51:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 2019 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
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: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone bug_severity
Message-ID: <bug-90246-4-icmwfBwcmt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02759.txt.bz2
Content-length: 352
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.2
Severity|normal |enhancement
>From gcc-bugs-return-641904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:07:42 2019
Return-Path: <gcc-bugs-return-641904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92498 invoked by alias); 25 Apr 2019 19: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 92459 invoked by uid 48); 25 Apr 2019 19:07:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90243] diagnostic notes that belong to a suppressed error about an uninitialized variable in a constexpr function are still shown
Date: Thu, 25 Apr 2019 19: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: 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-90243-4-PDpL9biFXm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02760.txt.bz2
Content-length: 318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90243
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Up to GCC 7.2 there's an error for the example, with notes. The error was fixed
by r251429 for PR 80935 (and with r252943 on gcc-7-branch) so from 7.3 the
error isn't given, but the notes remain.
>From gcc-bugs-return-641905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:10:43 2019
Return-Path: <gcc-bugs-return-641905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123274 invoked by alias); 25 Apr 2019 19:10: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 121725 invoked by uid 48); 25 Apr 2019 19:10:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90252] PSTL test failures
Date: Thu, 25 Apr 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: 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-90252-4-2kMzvrzc54@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90252-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90252-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02761.txt.bz2
Content-length: 629
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90252
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
Target Milestone|--- |9.2
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, the tbb effective target needs to do a link test, not just preprocessor
test to look for the headers.
>From gcc-bugs-return-641906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:15:48 2019
Return-Path: <gcc-bugs-return-641906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59623 invoked by alias); 25 Apr 2019 19: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 59593 invoked by uid 48); 25 Apr 2019 19:15:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90239] [C++20] scoped_allocator_adaptor should support nested pair
Date: Thu, 25 Apr 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: 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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-90239-4-SmLdRVS09K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02762.txt.bz2
Content-length: 735
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90239
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-25
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Mitsuru Kariya from comment #0)
> I think that it should output "1, 1, 1" in c++2a mode.
Unless I'm mistaken, P0591R4 was not supposed to change behaviour. It just
simplified the specification by defining it in terms of the new utility
functions.
>From gcc-bugs-return-641907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:20:29 2019
Return-Path: <gcc-bugs-return-641907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69144 invoked by alias); 25 Apr 2019 19:20: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 69084 invoked by uid 48); 25 Apr 2019 19:20:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90239] [C++20] scoped_allocator_adaptor should support nested pair
Date: Thu, 25 Apr 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: 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: 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:
Message-ID: <bug-90239-4-tnvBHNgMQl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02763.txt.bz2
Content-length: 396
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90239
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It appears that I am mistaken, the paper mentions the recursive handling of
std::pair in the abstract. That change in semantics wasn't obvious from the
proposed wording.
So I just need to use the new functions in <scoped_allocator>, and correct the
status docs for GCC 9.1
>From gcc-bugs-return-641908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:34:18 2019
Return-Path: <gcc-bugs-return-641908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49648 invoked by alias); 25 Apr 2019 19: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 49575 invoked by uid 48); 25 Apr 2019 19:34:15 -0000
From: "pthaugen at linux dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] New: 8% degradation on cpu2006 403.gcc starting with revision 270484
Date: Thu, 25 Apr 2019 19:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen at linux dot ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02764.txt.bz2
Content-length: 799
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
Bug ID: 90257
Summary: 8% degradation on cpu2006 403.gcc starting with
revision 270484
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: pthaugen at linux dot ibm.com
CC: dje at gcc dot gnu.org, hjl at gcc dot gnu.org, segher at gcc dot gnu.org,
wschmidt at gcc dot gnu.org
Target Milestone: ---
Host: powerpc64le-unknown-linux-gnu
Target: powerpc64le-unknown-linux-gnu
Build: powerpc64le-unknown-linux-gnu
Will add more detail as I discover it.
>From gcc-bugs-return-641909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:46:10 2019
Return-Path: <gcc-bugs-return-641909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68400 invoked by alias); 25 Apr 2019 19: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 68338 invoked by uid 48); 25 Apr 2019 19:46:06 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Thu, 25 Apr 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: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90257-4-iSynmDsYxM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02765.txt.bz2
Content-length: 223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This patch from a few days ago craters our specint scores by a few percent.
I'm marking this P1.
>From gcc-bugs-return-641910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:46:24 2019
Return-Path: <gcc-bugs-return-641910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69175 invoked by alias); 25 Apr 2019 19:46:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69101 invoked by uid 48); 25 Apr 2019 19:46:21 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Thu, 25 Apr 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: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-90257-4-SaG8XmfEfU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02766.txt.bz2
Content-length: 295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-641911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 19:56:32 2019
Return-Path: <gcc-bugs-return-641911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95314 invoked by alias); 25 Apr 2019 19:56: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 95293 invoked by uid 48); 25 Apr 2019 19:56:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90246] std::bad_variant_access messages are not useful
Date: Thu, 25 Apr 2019 19: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: enhancement
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-90246-4-ljEqRbKT5h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90246-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02767.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90246
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
>From gcc-bugs-return-641912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:06:37 2019
Return-Path: <gcc-bugs-return-641912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109485 invoked by alias); 25 Apr 2019 20:06:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109353 invoked by uid 48); 25 Apr 2019 20:06:33 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90236] bogus error with auto non-type template argument
Date: Thu, 25 Apr 2019 20:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90236-4-P8QOtOYIVV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90236-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90236-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02768.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90236
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Concluded we'll leave 8 as-is. This is not a regression.
>From gcc-bugs-return-641913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:18:51 2019
Return-Path: <gcc-bugs-return-641913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124620 invoked by alias); 25 Apr 2019 20: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 123094 invoked by uid 48); 25 Apr 2019 20:18:47 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90254] ice on aggregate initialization of unmovable base
Date: Thu, 25 Apr 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.3.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-90254-4-kV3DhtFobX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90254-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90254-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02769.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90254
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-04-25
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r247757.
>From gcc-bugs-return-641914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:19:22 2019
Return-Path: <gcc-bugs-return-641914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29493 invoked by alias); 25 Apr 2019 20: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 26272 invoked by uid 48); 25 Apr 2019 20:19:19 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90254] [8/9 Regression] ice on aggregate initialization of unmovable base
Date: Thu, 25 Apr 2019 20: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.3.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority target_milestone short_desc
Message-ID: <bug-90254-4-96vfv3xUpc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90254-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90254-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02770.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90254
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P3 |P2
Target Milestone|--- |8.4
Summary|ice on aggregate |[8/9 Regression] ice on
|initialization of unmovable |aggregate initialization of
|base |unmovable base
>From gcc-bugs-return-641915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:25:45 2019
Return-Path: <gcc-bugs-return-641915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58522 invoked by alias); 25 Apr 2019 20:25: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 58464 invoked by uid 48); 25 Apr 2019 20:25:42 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 2019 20: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.3.1
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: hjl.tools at gmail dot com
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-89929-4-0PbPaCnE25@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02771.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |9.0
Target Milestone|10.0 |9.0
Known to fail|9.0 |
--- Comment #26 from Martin Liška <marxin at gcc dot gnu.org> ---
Are you planning H.J. to backport that?
>From gcc-bugs-return-641916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:28:33 2019
Return-Path: <gcc-bugs-return-641916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60883 invoked by alias); 25 Apr 2019 20: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 60762 invoked by uid 48); 25 Apr 2019 20:28:29 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Thu, 25 Apr 2019 20:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-89929-4-1ORbdCGN2Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02772.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
--- Comment #27 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Martin Liška from comment #26)
> Are you planning H.J. to backport that?
Please feel free to backport it. I have no plan to do it myself.
>From gcc-bugs-return-641917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:32:13 2019
Return-Path: <gcc-bugs-return-641917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66801 invoked by alias); 25 Apr 2019 20:32:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66783 invoked by uid 48); 25 Apr 2019 20:32:10 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/90243] diagnostic notes that belong to a suppressed error about an uninitialized variable in a constexpr function are still shown
Date: Thu, 25 Apr 2019 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 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-90243-4-yKdeeUvPyx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90243-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02773.txt.bz2
Content-length: 193
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90243
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Patch posted to https://gcc.gnu.org/ml/gcc-patches/2019-04/msg01009.html
>From gcc-bugs-return-641918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 20:34:50 2019
Return-Path: <gcc-bugs-return-641918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84527 invoked by alias); 25 Apr 2019 20:34:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84445 invoked by uid 48); 25 Apr 2019 20:34:46 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/90229] Interaction among -Wl,--as-needed and LTO results in an undefined symbol
Date: Thu, 25 Apr 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: lto
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: MOVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status see_also resolution
Message-ID: <bug-90229-4-pUQwe8cFOQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02774.txt.bz2
Content-length: 627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90229
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=24486
Resolution|--- |MOVED
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
See:
https://sourceware.org/bugzilla/show_bug.cgi?id=24486
>From gcc-bugs-return-641919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 21:27:27 2019
Return-Path: <gcc-bugs-return-641919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4321 invoked by alias); 25 Apr 2019 21:27: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 4288 invoked by uid 48); 25 Apr 2019 21:27:23 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61414] enum class bitfield size-checking needs a separate warning flag controlling it
Date: Thu, 25 Apr 2019 21:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic, patch
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-61414-4-7YDhlbsqOU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61414-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61414-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02775.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61414
Barry Revzin <barry.revzin at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #17 from Barry Revzin <barry.revzin at gmail dot com> ---
Hi, it's me, another programmer who would love to use enum classes in bitfields
instead of having to static_cast back and forth :-) Can anybody fixup Sam's
patch?
>From gcc-bugs-return-641920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 21:50:30 2019
Return-Path: <gcc-bugs-return-641920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43609 invoked by alias); 25 Apr 2019 21:50: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 43585 invoked by uid 55); 25 Apr 2019 21:50:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90239] [C++20] scoped_allocator_adaptor should support nested pair
Date: Thu, 25 Apr 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: 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: 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:
Message-ID: <bug-90239-4-7WIXZeg8XO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02776.txt.bz2
Content-length: 657
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90239
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Apr 25 21:49:54 2019
New Revision: 270587
URL: https://gcc.gnu.org/viewcvs?rev=270587&root=gcc&view=rev
Log:
PR libstdc++/90239 Fix status of P0591R4 in C++2a support table
PR libstdc++/90239
* doc/xml/manual/status_cxx2020.xml: Correct status of P0591R4.
* doc/html/*: Regenerate.
Modified:
branches/gcc-9-branch/libstdc++-v3/ChangeLog
branches/gcc-9-branch/libstdc++-v3/doc/html/manual/status.html
branches/gcc-9-branch/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
>From gcc-bugs-return-641921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 22:43:50 2019
Return-Path: <gcc-bugs-return-641921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87142 invoked by alias); 25 Apr 2019 22:43:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87122 invoked by uid 55); 25 Apr 2019 22:43:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90239] [C++20] scoped_allocator_adaptor should support nested pair
Date: Thu, 25 Apr 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: 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: 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:
Message-ID: <bug-90239-4-ojb4PqSE6j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02777.txt.bz2
Content-length: 1102
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90239
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Apr 25 22:43:15 2019
New Revision: 270588
URL: https://gcc.gnu.org/viewcvs?rev=270588&root=gcc&view=rev
Log:
PR libstdc++/90239 use uses_allocator_construction_args in <scoped_allocator>
PR libstdc++/90239
* doc/xml/manual/status_cxx2020.xml: Amend P0591R4 status.
* include/std/scoped_allocator [__cplusplus > 201703L]
(scoped_allocator_adaptor::construct): Define in terms of
uses_allocator_construction_args, as per P0591R4.
* testsuite/20_util/scoped_allocator/construct_pair_c++2a.cc: New test.
* testsuite/util/testsuite_allocator.h: Remove name of unused
parameter.
Added:
trunk/libstdc++-v3/testsuite/20_util/scoped_allocator/construct_pair_c++2a.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/doc/xml/manual/status_cxx2020.xml
trunk/libstdc++-v3/include/std/scoped_allocator
trunk/libstdc++-v3/testsuite/util/testsuite_allocator.h
>From gcc-bugs-return-641922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 22:44:50 2019
Return-Path: <gcc-bugs-return-641922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89293 invoked by alias); 25 Apr 2019 22:44:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89253 invoked by uid 48); 25 Apr 2019 22:44:46 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/90239] [C++20] scoped_allocator_adaptor should support nested pair
Date: Thu, 25 Apr 2019 22:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone
Message-ID: <bug-90239-4-II574fHTEM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90239-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02778.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90239
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |10.0
Target Milestone|--- |9.2
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk. I'll backport this to gcc-9-branch after the 9.1.0 release.
>From gcc-bugs-return-641923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Apr 25 23:35:32 2019
Return-Path: <gcc-bugs-return-641923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57299 invoked by alias); 25 Apr 2019 23:35: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 57239 invoked by uid 48); 25 Apr 2019 23:35:28 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Thu, 25 Apr 2019 23: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: 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: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90257-4-2iXSqT6HAK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02779.txt.bz2
Content-length: 196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
We didn't see any performance changes in 502.gcc_r from SPEC CPU 2017
on x86-64.
>From gcc-bugs-return-641924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 01:40:36 2019
Return-Path: <gcc-bugs-return-641924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15880 invoked by alias); 26 Apr 2019 01:40: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 15828 invoked by uid 48); 26 Apr 2019 01:40:32 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9/10 Regression] C code is optimized worse than C++
Date: Fri, 26 Apr 2019 01:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-1NO9iiJqU2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02780.txt.bz2
Content-length: 1947
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #13 from Hongtao.liu <crazylht at gmail dot com> ---
(In reply to rguenther@suse.de from comment #10)
> On Thu, 25 Apr 2019, crazylht at gmail dot com wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
> >
> > --- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
> > Also what's better between aligned load/store of smaller size VS unaligned
> > load/store of bigger size?
> >
> > aligned load/store of smaller size:
> >
> > movq %rdx, (%rdi)
> > movq -56(%rsp), %rdx
> > movq %rdx, 8(%rdi)
> > movq -48(%rsp), %rdx
> > movq %rdx, 16(%rdi)
> > movq -40(%rsp), %rdx
> > movq %rdx, 24(%rdi)
> > vmovq %xmm0, 32(%rax)
> > movq -24(%rsp), %rdx
> > movq %rdx, 40(%rdi)
> > movq -16(%rsp), %rdx
> > movq %rdx, 48(%rdi)
> > movq -8(%rsp), %rdx
> > movq %rdx, 56(%rdi)
> >
> > unaligned load/store of bigger size:
> >
> > vmovups %xmm2, (%rdi)
> > vmovups %xmm3, 16(%rdi)
> > vmovups %xmm4, 32(%rdi)
> > vmovups %xmm5, 48(%rdi)
>
> bigger stores are almost always a win while bigger loads have
> the possibility to run into store-to-load forwarding issues
> (and bigger stores eventually mitigate them). Based on
> CPU tuning we'd also eventually end up with mov[lh]ps splitting
> unaligned loads/stores.
From
https://software.intel.com/en-us/download/intel-64-and-ia-32-architectures-optimization-reference-manual
14.6.3 Prefer Aligned Stores Over Aligned Loads
Unaligned stores are likely to cause greater performance degradation than
unaligned loads, since there
is a very high penalty on stores to a split cache-line that crosses pages. This
penalty is estimated at 150
cycles. Loads that cross a page boundary are executed at retirement.
>From gcc-bugs-return-641925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 04:52:14 2019
Return-Path: <gcc-bugs-return-641925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27854 invoked by alias); 26 Apr 2019 04: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 27798 invoked by uid 48); 26 Apr 2019 04:52:07 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90191] [9/10 regression] incorrect -Wformat-overflow with --param max-jump-thread-duplication-stmts\x17
Date: Fri, 26 Apr 2019 04:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat 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: bug_status cc resolution
Message-ID: <bug-90191-4-LmmxBLAOjb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90191-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90191-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02781.txt.bz2
Content-length: 7193
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90191
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |law at redhat dot com
Resolution|--- |INVALID
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> ---
Actually I think the warning is valid. Ramping up the aggressiveness of the
threader is what ultimately exposes it.
This code...
m = a ? t::u() : 0;
n.l = m;
Note how we can store 0 into "m" and we then store that into n.l. Which is
then read by these statements:
char &e = d[0];
printf("%s = %s\n", &r, &e);
And thus we have a path where e can potentially be NULL.
This can be seen in the IPA inlining pass:
<bb 2> [local count: 1073741824]:
MEM[(struct &)&d] ={v} {CLOBBER};
_6 = x::y ();
MEM[(struct &)&d] ={v} {CLOBBER};
if (_6 != 0)
goto <bb 3>; [33.00%]
else
goto <bb 4>; [67.00%]
<bb 3> [local count: 354334802]:
_7 = t::u ();
<bb 4> [local count: 1073741824]:
# iftmp.1_8 = PHI <0B(2), _7(3)>
m = iftmp.1_8;
MEM[(struct v *)&d].n.l = iftmp.1_8;
s.0_9 = s;
ad<int, int, int, i> (0, 0, s.0_9, D.2603);
goto <bb 8>; [100.00%]
<bb 5> [count: 0]:
<L2>:
c_10 = MEM[(struct v *)&d].n.l;
if (c_10 != 0B)
goto <bb 6>; [0.00%]
else
goto <bb 7>; [0.00%]
<bb 6> [count: 0]:
*c_10 ={v} {CLOBBER};
operator delete (c_10, 1);
<bb 7> [count: 0]:
MEM[(struct &)&d] ={v} {CLOBBER};
resx 2
<bb 8> [local count: 1073741824]:
_3 = MEM[(char * *)&d];
printf ("%s = %s\n", &r, _3);
See how bb4 stores iftmp.1_8 into d.n.l. iftmp.1_8 when reached from block 2
has the value NULL.
Then in bb8 we read that value and pass it to printf.
Of course in the form above, the warning isn't going to fire.
In .mergephi2 we have (unnecessary stuff skipped):
;; basic block 2, loop depth 0
;; pred: ENTRY
MEM[(struct &)&d] ={v} {CLOBBER};
_6 = x::y ();
MEM[(struct &)&d] ={v} {CLOBBER};
if (_6 != 0)
goto <bb 3>; [33.00%]
else
goto <bb 4>; [67.00%]
;; succ: 3
;; 4
;; basic block 3, loop depth 0
;; pred: 2
_7 = t::u ();
;; succ: 4
;; basic block 4, loop depth 0
;; pred: 2
;; 3
# iftmp.1_8 = PHI <0B(2), _7(3)>
m = iftmp.1_8;
MEM[(struct v *)&d].n.l = iftmp.1_8;
s.0_9 = s;
ad<int, int, int, i> (0, 0, s.0_9, D.2603);
goto <bb 8>; [100.00%]
;; succ: 8
;; 5
;; basic block 5, loop depth 0
;; pred: 4
<L2>:
if (iftmp.1_8 != 0B)
goto <bb 6>; [0.00%]
else
goto <bb 7>; [0.00%]
;; succ: 6
;; 7
;; basic block 6, loop depth 0
;; pred: 5
*iftmp.1_8 ={v} {CLOBBER};
operator delete (iftmp.1_8, 1);
;; succ: 7
;; basic block 7, loop depth 0
;; pred: 5
;; 6
MEM[(struct &)&d] ={v} {CLOBBER};
resx 2
Note carefully we have an EH edge (4,5).
The threader sees that the path 2->4->5 will always transfer control to bb7.
So it's going to isolate path that by copying bb4.
THe block #s change a lot, but after ethread1 the relevant blocks:
;; basic block 2, loop depth 0
;; pred: ENTRY
MEM[(struct &)&d] ={v} {CLOBBER};
_6 = x::y ();
MEM[(struct &)&d] ={v} {CLOBBER};
if (_6 != 0)
goto <bb 5>; [33.00%]
else
goto <bb 3>; [67.00%]
;; succ: 5
;; 3
;; basic block 3, loop depth 0
;; pred: 2
# iftmp.1_10 = PHI <0B(2)>
m = iftmp.1_10;
MEM[(struct v *)&d].n.l = iftmp.1_10;
s.0_30 = s;
ad<int, int, int, i> (0, 0, s.0_30, D.2603);
goto <bb 9>; [100.00%]
;; succ: 9
;; 4
;; basic block 4, loop depth 0
;; pred: 3
<L3>:
goto <bb 8>; [100.00%]
;; succ: 8
;; basic block 5, loop depth 0
;; pred: 2
_7 = t::u ();
m = _7;
MEM[(struct v *)&d].n.l = _7;
s.0_9 = s;
ad<int, int, int, i> (0, 0, s.0_9, D.2603);
goto <bb 9>; [100.00%]
;; succ: 9
;; 6
[ ... ]
;; basic block 9, loop depth 0
;; pred: 5
;; 3
# iftmp.1_31 = PHI <_7(5), iftmp.1_10(3)>
printf ("%s = %s\n", &r, iftmp.1_31);
Note how bb3 and bb5 have the same tail statements. But they feed values into
the printf in bb9, in particular a NULL value for the path 2->3->9. It becomes
more obvious after the VRP constant propagation:
;; basic block 2, loop depth 0
;; pred: ENTRY
MEM[(struct &)&d] ={v} {CLOBBER};
_6 = x::y ();
MEM[(struct &)&d] ={v} {CLOBBER};
if (_6 != 0)
goto <bb 5>; [33.00%]
else
goto <bb 3>; [67.00%]
;; succ: 5
;; 3
;; basic block 3, loop depth 0
;; pred: 2
m = 0B;
MEM[(struct v *)&d].n.l = 0B;
s.0_30 = s;
ad<int, int, int, i> (0, 0, s.0_30, D.2603);
goto <bb 9>; [100.00%]
;; succ: 9
;; 4
;; basic block 4, loop depth 0
;; pred: 3
<L3>:
goto <bb 8>; [100.00%]
;; succ: 8
;; basic block 5, loop depth 0
;; pred: 2
_7 = t::u ();
m = _7;
MEM[(struct v *)&d].n.l = _7;
s.0_9 = s;
ad<int, int, int, i> (0, 0, s.0_9, D.2603);
goto <bb 9>; [100.00%]
;; succ: 9
;; 6
;; basic block 6, loop depth 0
;; pred: 5
<L2>:
if (_7 != 0B)
goto <bb 7>; [0.00%]
else
goto <bb 8>; [0.00%]
;; succ: 7
;; 8
;; basic block 7, loop depth 0
;; pred: 6
*_7 ={v} {CLOBBER};
operator delete (_7, 1);
;; succ: 8
;; basic block 8, loop depth 0
;; pred: 6
;; 7
;; 4
MEM[(struct &)&d] ={v} {CLOBBER};
resx 2
;; succ:
;; basic block 9, loop depth 0
;; pred: 5
;; 3
# iftmp.1_31 = PHI <_7(5), 0B(3)>
printf ("%s = %s\n", &r, iftmp.1_31);
;; succ: 10
;; 13
;; basic block 10, loop depth 0
;; pred: 9
if (iftmp.1_31 != 0B)
goto <bb 11>; [53.47%]
else
goto <bb 12>; [46.53%]
Note I've included bb10. An astute observer would now realize that we've
exposed a secondary jump threading opportunity. That's going to result in bb9
getting duplicated so that we can optimize away the test in bb10.
The key blocks in .thread2:
;; basic block 9, loop depth 0
;; pred: 3
# iftmp.1_19 = PHI <0B(3)>
printf ("%s = %s\n", &r, iftmp.1_19);
goto <bb 13>; [100.00%]
;; succ: 13
;; 14
;; basic block 10, loop depth 0
;; pred: 5
# iftmp.1_31 = PHI <_7(5)>
printf ("%s = %s\n", &r, iftmp.1_31);
;; succ: 11
;; 15
bb9 being the one that's going to trigger the warning later.
But AFAICT the warning is 100% totally valid. You just have to turn up the
optimizer thresholds to expose it.
>From gcc-bugs-return-641926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:04:22 2019
Return-Path: <gcc-bugs-return-641926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30432 invoked by alias); 26 Apr 2019 07:04: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 30357 invoked by uid 48); 26 Apr 2019 07:04:19 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] [9/10 Regression] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Fri, 26 Apr 2019 07:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: blocked target_milestone short_desc
Message-ID: <bug-90257-4-sUrRdpeKtO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02782.txt.bz2
Content-length: 768
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |26163
Target Milestone|--- |9.2
Summary|8% degradation on cpu2006 |[9/10 Regression] 8%
|403.gcc starting with |degradation on cpu2006
|r270484 |403.gcc starting with
| |r270484
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
>From gcc-bugs-return-641927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:07:56 2019
Return-Path: <gcc-bugs-return-641927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33872 invoked by alias); 26 Apr 2019 07:07: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 33811 invoked by uid 48); 26 Apr 2019 07:07:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/89765] [9/10 Regression] Multiple problems with vec-insert implementation on PowerPC
Date: Fri, 26 Apr 2019 07: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: 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status assigned_to
Message-ID: <bug-89765-4-KROISXo7BR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02783.txt.bz2
Content-length: 526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89765
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|ASSIGNED |NEW
Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Not mine for the rest.
>From gcc-bugs-return-641928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:13:33 2019
Return-Path: <gcc-bugs-return-641928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38898 invoked by alias); 26 Apr 2019 07: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 38819 invoked by uid 55); 26 Apr 2019 07:13:28 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90204] [8/9/10 Regression] C code is optimized worse than C++
Date: Fri, 26 Apr 2019 07:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90204-4-4EicmWbD4d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90204-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02784.txt.bz2
Content-length: 2469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 26 Apr 2019, crazylht at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
>
> --- Comment #13 from Hongtao.liu <crazylht at gmail dot com> ---
> (In reply to rguenther@suse.de from comment #10)
> > On Thu, 25 Apr 2019, crazylht at gmail dot com wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90204
> > >
> > > --- Comment #9 from Hongtao.liu <crazylht at gmail dot com> ---
> > > Also what's better between aligned load/store of smaller size VS unaligned
> > > load/store of bigger size?
> > >
> > > aligned load/store of smaller size:
> > >
> > > movq %rdx, (%rdi)
> > > movq -56(%rsp), %rdx
> > > movq %rdx, 8(%rdi)
> > > movq -48(%rsp), %rdx
> > > movq %rdx, 16(%rdi)
> > > movq -40(%rsp), %rdx
> > > movq %rdx, 24(%rdi)
> > > vmovq %xmm0, 32(%rax)
> > > movq -24(%rsp), %rdx
> > > movq %rdx, 40(%rdi)
> > > movq -16(%rsp), %rdx
> > > movq %rdx, 48(%rdi)
> > > movq -8(%rsp), %rdx
> > > movq %rdx, 56(%rdi)
> > >
> > > unaligned load/store of bigger size:
> > >
> > > vmovups %xmm2, (%rdi)
> > > vmovups %xmm3, 16(%rdi)
> > > vmovups %xmm4, 32(%rdi)
> > > vmovups %xmm5, 48(%rdi)
> >
> > bigger stores are almost always a win while bigger loads have
> > the possibility to run into store-to-load forwarding issues
> > (and bigger stores eventually mitigate them). Based on
> > CPU tuning we'd also eventually end up with mov[lh]ps splitting
> > unaligned loads/stores.
>
> From
> https://software.intel.com/en-us/download/intel-64-and-ia-32-architectures-optimization-reference-manual
>
> 14.6.3 Prefer Aligned Stores Over Aligned Loads
>
> Unaligned stores are likely to cause greater performance degradation than
> unaligned loads, since there
> is a very high penalty on stores to a split cache-line that crosses pages. This
> penalty is estimated at 150
> cycles. Loads that cross a page boundary are executed at retirement.
That's a thing to keep in mind when peeling for alignment, but as
a general rule for straight-line code the possibility of hitting
a page boundary with an unaligned store is small while hitting
STLF failure is more likely.
>From gcc-bugs-return-641929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:21:44 2019
Return-Path: <gcc-bugs-return-641929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55974 invoked by alias); 26 Apr 2019 07:21:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55866 invoked by uid 48); 26 Apr 2019 07:21:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9/10 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Fri, 26 Apr 2019 07:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 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: 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-88879-4-dPUlDHAxXW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02785.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wilson at gcc dot gnu.org
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Almost all SPEC 2000 tests still fail to build.
Time to retire the IA64 port.
>From gcc-bugs-return-641930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:33:09 2019
Return-Path: <gcc-bugs-return-641930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114138 invoked by alias); 26 Apr 2019 07:33: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 114097 invoked by uid 48); 26 Apr 2019 07:33:06 -0000
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90242] [UBSAN]: in vn_reference_compute_hash
Date: Fri, 26 Apr 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: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zeccav 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-90242-4-dOCUx6ourM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90242-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02786.txt.bz2
Content-length: 946
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90242
Vittorio Zecca <zeccav at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zeccav at gmail dot com
--- Comment #3 from Vittorio Zecca <zeccav at gmail dot com> ---
On this input file I got this one and two more undefined
~/local/gcc-270309-undefined/bin/gcc c-c++-common/Warray-bounds.c -S -O
../../gcc/gcc/poly-int.h:715:21: runtime error: signed integer overflow:
9223372036854775804 + 4 cannot be represented in type 'long int'
../../gcc/gcc/poly-int.h:753:21: runtime error: signed integer overflow:
-9223372036854775807 * 8 cannot be represented in type 'long int'
../../gcc/gcc/cse.c:2215:34: runtime error: signed integer overflow: 0 -
-9223372036854775808 cannot be represented in type 'long int'
Optimization -O would do.
>From gcc-bugs-return-641931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:33:59 2019
Return-Path: <gcc-bugs-return-641931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115308 invoked by alias); 26 Apr 2019 07:33:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115210 invoked by uid 48); 26 Apr 2019 07:33:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] [9/10 Regression] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Fri, 26 Apr 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: other
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-90257-4-dPJkLfNVhy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02787.txt.bz2
Content-length: 277
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 46250
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46250&action=edit
run_fast_dce also for LRA
Sth like this could fix it.
>From gcc-bugs-return-641932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:36:22 2019
Return-Path: <gcc-bugs-return-641932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117862 invoked by alias); 26 Apr 2019 07: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 117810 invoked by uid 48); 26 Apr 2019 07:36:18 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89929] __attribute__((target("avx512bw"))) doesn't work on non avx512bw systems
Date: Fri, 26 Apr 2019 07:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89929-4-jnVu774b7v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02788.txt.bz2
Content-length: 511
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89929
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #28 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm fine with having that in GCC 9.1 which will be released soon. Thus closing
..
>From gcc-bugs-return-641933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:41:01 2019
Return-Path: <gcc-bugs-return-641933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125307 invoked by alias); 26 Apr 2019 07:41: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 125213 invoked by uid 48); 26 Apr 2019 07:40:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] [9/10 Regression] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Fri, 26 Apr 2019 07:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90257-4-ElpFpBr9Ja@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02789.txt.bz2
Content-length: 259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Let's revert the offending commit on the branch but keep it on trunk for
further investigation. PR90178 was only a missed optimization.
>From gcc-bugs-return-641934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:51:40 2019
Return-Path: <gcc-bugs-return-641934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9178 invoked by alias); 26 Apr 2019 07:51:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9105 invoked by uid 48); 26 Apr 2019 07:51:36 -0000
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/89504] Checking ICE in 'gcc.dg/rtl/x86_64/pro_and_epilogue.c'
Date: Fri, 26 Apr 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: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zeccav 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-89504-4-5soNl42pNm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89504-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89504-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02790.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89504
Vittorio Zecca <zeccav at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |zeccav at gmail dot com
--- Comment #2 from Vittorio Zecca <zeccav at gmail dot com> ---
Is this one a duplicate of 79688 ?
>From gcc-bugs-return-641935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:54:53 2019
Return-Path: <gcc-bugs-return-641935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60272 invoked by alias); 26 Apr 2019 07:54: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 57650 invoked by uid 48); 26 Apr 2019 07:54:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] [9/10 Regression] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Fri, 26 Apr 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: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90257-4-K1RlLO0UZe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02791.txt.bz2
Content-length: 317
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
So - is the regression of 8% compared to GCC 8? If only to some development
branch revision then it doesn't count. As I read it the removed code in
question only got added during GCC 9 stage3?
>From gcc-bugs-return-641936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:55:56 2019
Return-Path: <gcc-bugs-return-641936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67987 invoked by alias); 26 Apr 2019 07:55: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 67899 invoked by uid 48); 26 Apr 2019 07:55:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] [9/10 Regression] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Fri, 26 Apr 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: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-90257-4-0Zhy3oPeZC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02792.txt.bz2
Content-length: 837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-04-26
Ever confirmed|0 |1
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Thus, ppc folks - did you see a 8% peformance increase at the
2018-11-21 Uros Bizjak <ubizjak@gmail.com>
Revert the revert:
2013-10-26 Vladimir Makarov <vmakarov@redhat.com>
Revert:
2013-10-25 Vladimir Makarov <vmakarov@redhat.com>
* lra-spills.c (lra_final_code_change): Remove useless move insns.
revision?
>From gcc-bugs-return-641937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 07:57:36 2019
Return-Path: <gcc-bugs-return-641937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36179 invoked by alias); 26 Apr 2019 07:57: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 32284 invoked by uid 48); 26 Apr 2019 07:57:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90257] [9/10 Regression] 8% degradation on cpu2006 403.gcc starting with r270484
Date: Fri, 26 Apr 2019 07:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-90257-4-6E820Cy8QW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02793.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90257
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P2
>From gcc-bugs-return-641939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 09:33:37 2019
Return-Path: <gcc-bugs-return-641939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78281 invoked by alias); 26 Apr 2019 09:33:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78222 invoked by uid 48); 26 Apr 2019 09:33:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90258] [9 Regression] Missing completion for a target option since r264052
Date: Fri, 26 Apr 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: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-90258-4-xXHOpTcun4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02795.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90258
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-04-26
Known to work| |8.3.0
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
Known to fail| |9.0
>From gcc-bugs-return-641938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 09:33:05 2019
Return-Path: <gcc-bugs-return-641938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77374 invoked by alias); 26 Apr 2019 09: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 77291 invoked by uid 48); 26 Apr 2019 09:33:01 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90258] New: [9 Regression] Missing completion for a target option since r264052
Date: Fri, 26 Apr 2019 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-90258-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02794.txt.bz2
Content-length: 763
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90258
Bug ID: 90258
Summary: [9 Regression] Missing completion for a target option
since r264052
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Caused by my commit:
$ gcc -mandroida /tmp/main.c
gcc: error: unrecognized command line option ‘-mandroida’
While we should print:
$ gcc -mandroida /tmp/main.c
gcc: error: unrecognized command line option ‘-mandroida’; did you mean
‘-mandroid’?
>From gcc-bugs-return-641940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 09:54:45 2019
Return-Path: <gcc-bugs-return-641940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80335 invoked by alias); 26 Apr 2019 09:54: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 80320 invoked by uid 48); 26 Apr 2019 09:54:41 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90258] [9 Regression] Missing completion for a target option since r264052
Date: Fri, 26 Apr 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: 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: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-90258-4-A9vQQPGRTe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02796.txt.bz2
Content-length: 416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90258
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|target |middle-end
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
It's a generic issue, not target specific.
>From gcc-bugs-return-641941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 10:16:02 2019
Return-Path: <gcc-bugs-return-641941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115527 invoked by alias); 26 Apr 2019 10:16:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115440 invoked by uid 48); 26 Apr 2019 10:15:57 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90259] New: ICE: verify_flow_info failed (error: missing REG_EH_REGION note at the end of bb 4)
Date: Fri, 26 Apr 2019 10:16: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: EH, ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget attachments.created
Message-ID: <bug-90259-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02797.txt.bz2
Content-length: 2004
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90259
Bug ID: 90259
Summary: ICE: verify_flow_info failed (error: missing
REG_EH_REGION note at the end of bb 4)
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: EH, ice-checking, ice-on-valid-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Target: powerpc-e300c3-linux-gnu
Created attachment 46251
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=46251&action=edit
Testcase
g++-9.0.0-alpha20190421 snapshot (r270485) ICEs when compiling the attached
testcase w/ -O1 (-O2, -O3, -Os) -ffloat-store -fgcse -fnon-call-exceptions
-fno-forward-propagate -fno-omit-frame-pointer:
% powerpc-e300c3-linux-gnu-g++-9.0.0-alpha20190421 -m32 -O1 -ffloat-store
-fgcse -fnon-call-exceptions -fno-forward-propagate -fno-omit-frame-pointer -c
svj3x11t.cc
svj3x11t.cc: In static member function 'static ar p<ar(j ...), i>::as(const
int&, j ...) [with ar = void; i = q::r; j = {o}]':
svj3x11t.cc:30:65: error: missing REG_EH_REGION note at the end of bb 4
30 | static ar as(const int &p1, j...) { (*ao<i>::ap(p1))(j()...); }
| ^
during RTL pass: cprop_hardreg
svj3x11t.cc:30:65: internal compiler error: verify_flow_info failed
0xb0808c verify_flow_info()
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/cfghooks.c:265
0xe76ac2 execute_function_todo
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/passes.c:1989
0xe7743a execute_todo
/var/tmp/portage/cross-powerpc-e300c3-linux-gnu/gcc-9.0.0_alpha20190421/work/gcc-9-20190421/gcc/passes.c:2031
>From gcc-bugs-return-641942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 10:33:31 2019
Return-Path: <gcc-bugs-return-641942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109766 invoked by alias); 26 Apr 2019 10:33:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109700 invoked by uid 48); 26 Apr 2019 10:33:27 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/90249] [9/10 Regression] Code size regression on thumb2 due to sub-optimal register allocation starting with r265398
Date: Fri, 26 Apr 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: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90249-4-rcgIfIM9lJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90249-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02798.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90249
--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #2)
> What difference is there on some code of significant size? Do you see
> regressions then?
>
> Of course there are some tiny examples where it now does worse, just like
> there are examples where it now does better.
Across the entirety of CSiBE thumb2 regresses by 0.05% (tested by effectively
disabling r265398 on tip of tree).
It seems to be specific to Thumb2 code, though. Thumb1 and Arm code now get
worse when that specific patch is disabled. Though all three are still worse
than gcc-8 overall.
>From gcc-bugs-return-641944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 11:05:44 2019
Return-Path: <gcc-bugs-return-641944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70865 invoked by alias); 26 Apr 2019 11:05: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 70786 invoked by uid 48); 26 Apr 2019 11:05:40 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90258] [9 Regression] Missing completion for a target option since r264052
Date: Fri, 26 Apr 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: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc keywords
Message-ID: <bug-90258-4-aFXxBFpC0e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02800.txt.bz2
Content-length: 1133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90258
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
Summary|[9 Regression] Missing |[9/10 Regression] Missing
|completion for a target |completion for a target
|option since r264052 |option since r264052
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Summary|[9/10 Regression] Missing |[9 Regression] Missing
|completion for a target |completion for a target
|option since r264052 |option since r264052
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Patch candidate:
https://gcc.gnu.org/ml/gcc-patches/2019-04/msg01032.html
>From gcc-bugs-return-641943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 11:05:44 2019
Return-Path: <gcc-bugs-return-641943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70858 invoked by alias); 26 Apr 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 70779 invoked by uid 48); 26 Apr 2019 11:05:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/90258] [9 Regression] Missing completion for a target option since r264052
Date: Fri, 26 Apr 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: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc keywords
Message-ID: <bug-90258-4-HpPAAO5I8O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90258-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02799.txt.bz2
Content-length: 1133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90258
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
Summary|[9 Regression] Missing |[9/10 Regression] Missing
|completion for a target |completion for a target
|option since r264052 |option since r264052
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Summary|[9/10 Regression] Missing |[9 Regression] Missing
|completion for a target |completion for a target
|option since r264052 |option since r264052
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Patch candidate:
https://gcc.gnu.org/ml/gcc-patches/2019-04/msg01032.html
>From gcc-bugs-return-641945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 11:16:43 2019
Return-Path: <gcc-bugs-return-641945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65324 invoked by alias); 26 Apr 2019 11:16:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65285 invoked by uid 48); 26 Apr 2019 11:16:39 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90253] no warning for cv-qualified selectors in _Generic
Date: Fri, 26 Apr 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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90253-4-zo00xQudRb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90253-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90253-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02801.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90253
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 think there was another bug about this w.r.t. -Wignored-qualifiers and/or
whether or not typeof should strip qualifiers; can't find it right now
though...
>From gcc-bugs-return-641946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 11:22:04 2019
Return-Path: <gcc-bugs-return-641946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73243 invoked by alias); 26 Apr 2019 11:22:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73166 invoked by uid 55); 26 Apr 2019 11:22:00 -0000
From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83118] [7/8/9/10 Regression] Bad intrinsic assignment of class(*) array component of derived type
Date: Fri, 26 Apr 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: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paul.richard.thomas at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83118-4-YJGAxLqLgC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83118-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-04/txt/msg02802.txt.bz2
Content-length: 1197
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118
--- Comment #20 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Hi Rainer,
Thanks a million. Unfortunately, we just missed the 9.1 release.
Cheers
Paul
On Thu, 25 Apr 2019 at 09:59, ro at CeBiTec dot Uni-Bielefeld.DE
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83118
>
> --- Comment #19 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> > --- Comment #18 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot
> > Uni-Bielefeld.DE> ---
> [...]
> > I've just applied the patch to trunk, rebuilt f951 on
> > sparc-sun-solaris2.11 and tested unlimited_polymorphic_30.f03: the test
> > now PASSes for both 32 and 64-bit.
> >
> > I'll include the patch in tonight's bootstrap and let you know if there
> > are any problems elsewhere.
>
> There weren't any in last night's sparc-sun-solaris2.11 bootstrap: both
> 32 and 64-bit unlimited_polymorphic_30.f03 failures are gone.
>
> Thanks.
> Rainer
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.
>From gcc-bugs-return-641947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Apr 26 12:22:16 2019
Return-Path: <gcc-bugs-return-641947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107941 invoked by alias); 26 Apr 2019 12:22: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 107825 invoked by uid 89); 26 Apr 2019 12:22:14 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=2.6 required=5.0 tests=AWL,BAYES_60,HTML_MESSAGE,RCVD_IN_RP_RNBL,UNPARSEABLE_RELAY autolearn=no version=3.3.1 spammy=oil, Oil, african, African
X-HELO: omx-44.mx.ning.com
Received: from omx-44.mx.ning.at (HELO omx-44.mx.ning.com) (208.82.17.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 26 Apr 2019 12:22:13 +0000
Received: from z023510.ningops.com (unknown [10.11.32.5]) by m191045.ningops.com (Postfix) with ESMTP id CF878EC96F9 for <gcc-bugs@gcc.gnu.org>; Fri, 26 Apr 2019 12:22:11 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=ning.com; sÞfault; t\x1556281331; bh=ELyuMVpal8sC5/UyMTc6eq1WcAb3dZ/kdTwoNNO2KjE=; hÚte:From:Reply-To:To:Subject:From; b=uG77xgWLIfLV6F5k/jUU7xShJrv1vyyoHorEb01Ac2IZCHXDULUpkhrnB5LpQXQ3P o93pGLYGSXOrDeKytwGWvAFmzMqkeyJZdbXa9RHRiD7DLs3gS/64EMDbTxxf61YvK6 aK5m7DP0abiWU41OmpxR3rLkWc+DHRvN/Bb7pX+UReceived: from localhost (10.11.16.4 [/10.11.16.4]) by z023510.ningops.com with SMTP; Fri, 26 04 2019 12:22:11 +0000 (GMT)
Date: Fri, 26 Apr 2019 12:22:00 -0000
From: Kamran Hedayat <invitations@africaoil.ning.com>
Reply-To: do-not-reply@africaoil.ning.com
To: "gcc-bugs@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Message-ID: <570955115.77066593.1556281331849.JavaMail.xncore@z023510.ningops.com>
Subject: Come join me on Africa Oil & Gas Industry
MIME-Version: 1.0
X-XN-MessageType: MSG_INVITE_NET
X-XN_SECURITY_TOKEN: SYLfz*y*3J5Zf8vcUfXj8urWbk04XIWY0ZSrZ1Mtw7yNZshqeDNjr4sizDKFZWr7MfoTaRYFiSNP7KsDeBqW9JlxUQeKWoaTfK1Ke1tB85bucxER5DkOBr-mEwpnZXuwig3ImxDTUoQtdDHL3yCUhSckCp6SORi9
X-XN-UUID: f42c7e85-ab40-4371-a8c3-1c2ac57e95c0
X-XN-Super-Happy-Header: zlfXMN9Z9we-ct0kOsVXhEebjzMag1sUZ*hAbdNPSRvtDiQbYj1sHE1Xcem9DmAhhg*9GkMM3E14d7SwicUd5ODaTwaoqifZI27*Z6mAVJCPJdkIoqzXXi*A4uVp0uNgQmDZhek*2llwcViut3tU1QGe34gWQRKvlPjUszZKyYvR8gVC0farQpvjuI7ymVbPHbjs*Q4gN97IqagbDztw4fOIByitBD7bNFC9bdmC6TnX8747tcAOU5ckGSG9*veLRNsqOEEyCtk1*NeNwJ8IwYd1IM9WPvK2EByhM3*3Okbke5Ej6bAa3spJvLJHX730
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-SW-Source: 2019-04/txt/msg02803.txt.bz2
Content-length: 1055
Africa Oil & Gas Industry: An Africa Business Community
--------------------
Hi,
Short term business collaboration. Let me know if you have some time to connect for more details. Contact email: kamhed44@gmail.com.
Skype: live:kamhed44.
Regards,
Kamran Hedayat.
Click the link below to Join:
http://africaoil.ning.com/?xgiXmuZSRPXC7Hxz&xg_source=msg_invite_net
If your email program doesn't recognize the web address above as an active link,
please copy and paste it into your web browser
--------------------
Members already on Africa Oil & Gas Industry
Bas Vlugt, Olamide Jegede, Glenn Labhart, Dakota Muscle, Ray Miles
--------------------
About Africa Oil & Gas Industry
A networking community for people who are professionally involved in the African Oil & Gas Industry
1374 members
96 Events
392 blog posts
--------------------
To control which emails you receive on Africa Oil & Gas Industry, or to opt-out, go to:
http://africaoil.ning.com/?xgo=ShMVpgcsGWQLZy60QH/ni-HeV8E45PCbijHN32es2NC9iKrJ11YG2z5nE/Z46JW3&xg_source=msg_invite_net
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-04-24 20:38 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-90227-4@http.gcc.gnu.org/bugzilla/>
2019-04-24 20:38 ` [Bug c++/90227] [9 Regression] trunk rejects polymake since r269965 jason 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).