public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug tree-optimization/93084] [10 regression] Infinite loop in ipa-cp when building clang with LTO+PGO
[not found] <bug-93084-4@http.gcc.gnu.org/bugzilla/>
@ 2019-12-30 11:02 ` hubicka at ucw dot cz
2020-01-02 10:16 ` hubicka at ucw dot cz
1 sibling, 0 replies; 2+ messages in thread
From: hubicka at ucw dot cz @ 2019-12-30 11:02 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93084
--- Comment #7 from Jan Hubicka <hubicka at ucw dot cz> ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93084
>
> --- Comment #6 from fxue at gcc dot gnu.org ---
> Could you share how you build clang with PGO, and train workload?
It needs a lot of patience. If you have patch I can try it since I
still have the train data and corresponding gcc tree.
I do the following. Pretty much imitating what
utils/collect_and_build_with_pgo.py does.
First I build instrumented compiler and train it on testsuite (it takes
a long time and probably could be omitted)
cmake -G Ninja /aux/hubicka/llvm \
-DCLANG_TABLEGEN=/aux/hubicka/llvm/out/stage1/bin/clang-tblgen \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_CXX_COMPILER=/aux/hubicka/trunk-install/bin/g++ \
-DCMAKE_C_COMPILER=/aux/hubicka/trunk-install/bin/gcc \
-DCMAKE_INSTALL_PREFIX=/aux/hubicka/llvm10-install-gccfdolto \
-DLLVM_BINUTILS_INCDIR=/aux/hubicka/binutils-install/include/ \
-DLLVM_BUILD_RUNTIME=No \
-DLLVM_TABLEGEN=/aux/hubicka/llvm/out/stage1/bin/llvm-tblgen \
-DLLVM_TARGETS_TO_BUILD=X86 \
-DCMAKE_RANLIB=/aux/hubicka/trunk-install/bin/gcc-ranlib \
-DCMAKE_AR=/aux/hubicka/trunk-install/bin/gcc-ar \
-DCMAKE_C_FLAGS="-O2 -flto=auto -flifetime-dse=1 -fno-semantic-interposition
-fprofile-generate" \
-DCMAKE_CXX_FLAGS="-O2 -flto=auto -flifetime-dse=1
-fno-semantic-interposition -fprofile-generate" \
-DLLVM_PARALLEL_LINK_JOBS=1
ninja clang lld
ninja check-llvm check-clang
next I do train build in new directory.
cmake -G Ninja /aux/hubicka/llvm \
-DCMAKE_BUILD_TYPE=Release \
-DCMAKE_CXX_COMPILER=/aux/hubicka/llvm/out/instrumented-gcc/bin/clang++ \
-DCMAKE_C_COMPILER=/aux/hubicka/llvm/out/instrumented-gcc/bin/clang
ninja all
then I tar gcda files collected in the first build directory
cd /aux/hubicka/llvm/instrumented-gcc/
tar czvf ../clang-profile.tgz `find . -name "*.gcda"`
and do final build supplying the gcda files.
tar xzvf ../clang-profile.tgz
cmake -G Ninja /aux/hubicka/llvm \
-DCLANG_TABLEGEN=/aux/hubicka/llvm/out/stage1/bin/clang-tblgen \
-DCMAKE_BUILD_TYPE=Release -DCMAKE_C_FLAGS=-Wno-backend-plugin \
-DLLVM_TABLEGEN=/aux/hubicka/llvm/out/stage1/bin/llvm-tblgen \
-DCMAKE_RANLIB=/aux/hubicka/trunk-install/bin/gcc-ranlib \
-DCMAKE_AR=/aux/hubicka/trunk-install/bin/gcc-ar \
-DCMAKE_C_FLAGS="-O2 -fno-semantic-interposition -fprofile-use
-Wno-missing-profile -flto=auto -flifetime-dse=1 -fprofile-correction
-Wno-error" \
-DCMAKE_CXX_FLAGS="-O2 -fno-semantic-interposition -fprofile-use
-Wno-missing-profile -flifetime-dse=1 -flto=auto -fprofile-correction
-Wno-error" \
-DLLVM_TARGETS_TO_BUILD=X86 \
-DCMAKE_CXX_COMPILER=/aux/hubicka/trunk-install/bin/g++ \
-DCMAKE_C_COMPILER=/aux/hubicka/trunk-install/bin/gcc \
-DLLVM_BINUTILS_INCDIR=/aux/hubicka/binutils-install/include/ \
-DLLVM_PARALLEL_LINK_JOBS=1
ninja all
>From gcc-bugs-return-664196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 11:03:37 2019
Return-Path: <gcc-bugs-return-664196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93791 invoked by alias); 30 Dec 2019 11:03:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93733 invoked by uid 48); 30 Dec 2019 11:03:33 -0000
From: "zhongyunde at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93102] New: [optimization] is it legal to avoid accessing const local array from stack ?
Date: Mon, 30 Dec 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: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zhongyunde at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02266.txt.bz2
Content-length: 1192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93102
Bug ID: 93102
Summary: [optimization] is it legal to avoid accessing const
local array from stack ?
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: zhongyunde at huawei dot com
Target Milestone: ---
test code:
int foo (int m, int n)
{
const int C00002029[10] = {0,1,2,3,2,3,0,1,2,3};
int index, sum = 0;
for (index=m; index<n; index ++)
sum += C00002029[index];
return sum;
}
in general, we may store the const value {0,1,2,3,2,3,0,1,2,3} in rodata
section, then use memcpy to assign the local array C00002029.
But as we known, in above code, the array is only accessed one time, so can we
optimize it such as following logic? this can avoid initialization, and the
performance can be better.
const int C00002029_xxx[10] = {0,1,2,3,2,3,0,1,2,3};
int foo (int m, int n)
{
int index, sum = 0;
for (index=m; index<n; index ++)
sum += C00002029_xxx[index];
return sum;
}
>From gcc-bugs-return-664197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 11:18:42 2019
Return-Path: <gcc-bugs-return-664197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80811 invoked by alias); 30 Dec 2019 11:18:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80771 invoked by uid 48); 30 Dec 2019 11:18:37 -0000
From: "keremkat+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] ice for broken C code
Date: Mon, 30 Dec 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: keremkat+gcc at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92833-4-hqBplGaOgC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02267.txt.bz2
Content-length: 1951
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
Kerem Kat <keremkat+gcc at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |keremkat+gcc at gmail dot com
--- Comment #3 from Kerem Kat <keremkat+gcc at gmail dot com> ---
This is caused by c_parser_peek_conflict_marker peeking into 4 tokens at once
whereas c_parser_consume_token expects a maximum of 3 tokens to be peeked.
In this case, last token is EOF and it is swallowed by c_parser_consume_token,
leading to ICE within the next c_parser_skip_to_end_of_block_or_statement
invocation which tries to read pfile->buffer that was popped to become empty
via _cpp_pop_buffer.
Minimal test case is six less than signs:
<<<<<<
Full stack trace:
92833-ice.c:1:1: error: expected identifier or ‘(’ before ‘<<’ token
1 | <<<<<<
| ^~
92833-ice.c:1:1: internal compiler error: Segmentation fault
0xe150f3 crash_signal
dir/gcc/toplev.c:328
0x187c684 _cpp_lex_direct
dir/libcpp/lex.c:2725
0x187c3e4 _cpp_lex_token
dir/libcpp/lex.c:2608
0x1886d77 cpp_get_token_1
dir/libcpp/macro.c:2707
0x8ef0e5 c_lex_with_flags(tree_node**, unsigned int*, unsigned char*, int)
dir/gcc/c-family/c-lex.c:458
0x8426b5 c_lex_one_token
dir/gcc/c/c-parser.c:270
0x842bbe c_parser_peek_token(c_parser*)
dir/gcc/c/c-parser.c:474
0x843ffd c_parser_skip_to_end_of_block_or_statement
dir/gcc/c/c-parser.c:1322
0x8455bd c_parser_declaration_or_fndef
dir/gcc/c/c-parser.c:2123
0x844a1d c_parser_external_declaration
dir/gcc/c/c-parser.c:1742
0x844566 c_parser_translation_unit
dir/gcc/c/c-parser.c:1615
0x884ed7 c_parse_file()
dir/gcc/c/c-parser.c:21704
0x8f9b43 c_common_parse_file()
dir/gcc/c-family/c-opts.c:1186
>From gcc-bugs-return-664198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 11:24:02 2019
Return-Path: <gcc-bugs-return-664198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122567 invoked by alias); 30 Dec 2019 11:24:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122488 invoked by uid 48); 30 Dec 2019 11:23:57 -0000
From: "keremkat+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] ice for broken C code
Date: Mon, 30 Dec 2019 11:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: keremkat+gcc at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92833-4-Msu9jUVp7y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02268.txt.bz2
Content-length: 141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
--- Comment #4 from Kerem Kat <keremkat+gcc at gmail dot com> ---
Please assign to me.
>From gcc-bugs-return-664199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 11:35:57 2019
Return-Path: <gcc-bugs-return-664199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14668 invoked by alias); 30 Dec 2019 11:35: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 14644 invoked by uid 48); 30 Dec 2019 11:35:53 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93102] [optimization] is it legal to avoid accessing const local array from stack ?
Date: Mon, 30 Dec 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on component everconfirmed bug_severity
Message-ID: <bug-93102-4-59EXr4p5dP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02269.txt.bz2
Content-length: 931
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93102
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-12-30
Component|c |tree-optimization
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So yes it is valid in some cases, but not all. There is another bug report for
this too but I can't find it right now.
basically what needs to happen is that C00002029 cannot have its address taken;
right now it is marked as been taken due to the index'ed.
>From gcc-bugs-return-664200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 11:48:49 2019
Return-Path: <gcc-bugs-return-664200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29112 invoked by alias); 30 Dec 2019 11:48:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29072 invoked by uid 48); 30 Dec 2019 11:48:45 -0000
From: "mateusz.pusz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93103] New: Generic function syntax does not check return concept
Date: Mon, 30 Dec 2019 11:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mateusz.pusz 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-93103-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02270.txt.bz2
Content-length: 941
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93103
Bug ID: 93103
Summary: Generic function syntax does not check return concept
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mateusz.pusz at gmail dot com
Target Milestone: ---
In the example below `foo` correctly fails the concept check while `boo`
ignores the constraints of the return type:
```
#include <type_traits>
template<typename T>
concept SomeConcept = true;
template<typename T>
concept Integral = std::is_integral_v<T>;
template<SomeConcept T>
Integral auto foo(T t) { return t; }
Integral auto boo(SomeConcept auto t) { return t; }
int main()
{
auto x1 = foo(3.14);
auto x2 = boo(3.14);
}
```
Compiler Explorer link: https://godbolt.org/z/-K39X7.
>From gcc-bugs-return-664201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:14:38 2019
Return-Path: <gcc-bugs-return-664201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66148 invoked by alias); 30 Dec 2019 12:14:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66075 invoked by uid 48); 30 Dec 2019 12:14:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91541] [C++17] Exception specification of operator= of node-based containers may be broken
Date: Mon, 30 Dec 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: libstdc++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91541-4-Oba7gbtoPZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91541-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02271.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91541
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #12)
> (In reply to Thomas Koenig from comment #11)
>
> *sigh* corrected in the original PR.
Please add a 'fixup' to the bugdb.py file in the gcc-conversion repo, so this
can be fixed in the Git conversion (I already did this for several of your
commits with wrong PR numbers).
>From gcc-bugs-return-664202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:16:26 2019
Return-Path: <gcc-bugs-return-664202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10137 invoked by alias); 30 Dec 2019 12:16:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4204 invoked by uid 48); 30 Dec 2019 12:16:20 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91541] [C++17] Exception specification of operator= of node-based containers may be broken
Date: Mon, 30 Dec 2019 12:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91541-4-GWjlzITbD1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91541-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02272.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91541
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
And please also fix the comment in the new test.
>From gcc-bugs-return-664203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:27:57 2019
Return-Path: <gcc-bugs-return-664203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62511 invoked by alias); 30 Dec 2019 12:27:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62428 invoked by uid 48); 30 Dec 2019 12:27:47 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93104] New: [8/10 Regression] Current trunk can not build gcc 8
Date: Mon, 30 Dec 2019 12:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02273.txt.bz2
Content-length: 78444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
Bug ID: 93104
Summary: [8/10 Regression] Current trunk can not build gcc 8
Product: gcc
Version: 8.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
Created attachment 47567
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47567&action=edit
config.log
Not sure if this is a gcc 8 or a trunk issue.
With trunk r279765 as the bootstrapping compiler, r279759 of gcc-8 fails
bootstrap. Configure line was
../gcc-8/configure --prefix=$HOME --enable-languages=c,c++,fortran && make -j7
where the build directory was 8-bin (separate from the source directory).
In Datei, eingebunden von config.h:8,
von insn-output.c:5:
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:57:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
57 | ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:59:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
59 | ATTRIBUTE_GCC_DIAG(1,2) ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:61:46: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
61 | extern bool warning (int, const char *, ...) ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:64:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
64 | ATTRIBUTE_GCC_DIAG(4,6) ATTRIBUTE_GCC_DIAG(5,6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:64:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
64 | ATTRIBUTE_GCC_DIAG(4,6) ATTRIBUTE_GCC_DIAG(5,6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:67:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
67 | ATTRIBUTE_GCC_DIAG(4, 6) ATTRIBUTE_GCC_DIAG(5, 6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:67:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
67 | ATTRIBUTE_GCC_DIAG(4, 6) ATTRIBUTE_GCC_DIAG(5, 6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:69:5: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
69 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:71:5: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
71 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:72:39: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
72 | extern void error (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:75:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
75 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:75:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
75 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:76:54: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
76 | extern void error_at (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:78:3: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
78 | ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:80:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
80 | ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:83:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
83 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:85:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
85 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:86:55: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
86 | extern bool permerror (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
|
^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:88:13: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
88 | ...) ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:89:39: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
89 | extern void sorry (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:90:52: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
90 | extern void inform (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:91:57: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
91 | extern void inform (rich_location *, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
|
^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:94:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
94 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:94:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
94 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:95:42: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
95 | extern void verbatim (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:97:28: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
97 | const char *, ...) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:99:20: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
99 | va_list *) ATTRIBUTE_GCC_DIAG (4,0);
| ^~~~~~~~~~~~~~~~~~
g++ -std=gnu++98 -fno-PIE -c -g -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-format -Wmissing-format-attribute -Woverloaded-virtual
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-fno-common -DHAVE_CONFIG_H -I. -I. -I../../gcc-8/gcc -I../../gcc-8/gcc/.
-I../../gcc-8/gcc/../include -I../../gcc-8/gcc/../libcpp/include
-I/home/ig25/Gcc/8-bin/./gmp -I/home/ig25/Gcc/gcc-8/gmp
-I/home/ig25/Gcc/8-bin/./mpfr/src -I/home/ig25/Gcc/gcc-8/mpfr/src
-I/home/ig25/Gcc/gcc-8/mpc/src -I../../gcc-8/gcc/../libdecnumber
-I../../gcc-8/gcc/../libdecnumber/bid -I../libdecnumber
-I../../gcc-8/gcc/../libbacktrace -I/home/ig25/Gcc/8-bin/./isl/include
-I/home/ig25/Gcc/gcc-8/isl/include -o ggc-page.o -MT ggc-page.o -MMD -MP -MF
./.deps/ggc-page.TPo ../../gcc-8/gcc/ggc-page.c
g++ -std=gnu++98 -fno-PIE -c -g -DIN_GCC -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wno-format -Wmissing-format-attribute -Woverloaded-virtual
-pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings
-fno-common -DHAVE_CONFIG_H -I. -I. -I../../gcc-8/gcc -I../../gcc-8/gcc/.
-I../../gcc-8/gcc/../include -I../../gcc-8/gcc/../libcpp/include
-I/home/ig25/Gcc/8-bin/./gmp -I/home/ig25/Gcc/gcc-8/gmp
-I/home/ig25/Gcc/8-bin/./mpfr/src -I/home/ig25/Gcc/gcc-8/mpfr/src
-I/home/ig25/Gcc/gcc-8/mpc/src -I../../gcc-8/gcc/../libdecnumber
-I../../gcc-8/gcc/../libdecnumber/bid -I../libdecnumber
-I../../gcc-8/gcc/../libbacktrace -I/home/ig25/Gcc/8-bin/./isl/include
-I/home/ig25/Gcc/gcc-8/isl/include -o alias.o -MT alias.o -MMD -MP -MF
./.deps/alias.TPo ../../gcc-8/gcc/alias.c
In Datei, eingebunden von config.h:8,
von insn-preds.c:5:
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:57:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
57 | ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:59:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
59 | ATTRIBUTE_GCC_DIAG(1,2) ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:61:46: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
61 | extern bool warning (int, const char *, ...) ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:64:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
64 | ATTRIBUTE_GCC_DIAG(4,6) ATTRIBUTE_GCC_DIAG(5,6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:64:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
64 | ATTRIBUTE_GCC_DIAG(4,6) ATTRIBUTE_GCC_DIAG(5,6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:67:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
67 | ATTRIBUTE_GCC_DIAG(4, 6) ATTRIBUTE_GCC_DIAG(5, 6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:67:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
67 | ATTRIBUTE_GCC_DIAG(4, 6) ATTRIBUTE_GCC_DIAG(5, 6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:69:5: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
69 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:71:5: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
71 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:72:39: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
72 | extern void error (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:75:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
75 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:75:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
75 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:76:54: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
76 | extern void error_at (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:78:3: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
78 | ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:80:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
80 | ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:83:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
83 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:85:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
85 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:86:55: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
86 | extern bool permerror (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
|
^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:88:13: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
88 | ...) ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:89:39: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
89 | extern void sorry (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:90:52: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
90 | extern void inform (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:91:57: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
91 | extern void inform (rich_location *, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
|
^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:94:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
94 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:94:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
94 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:95:42: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
95 | extern void verbatim (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:97:28: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
97 | const char *, ...) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:99:20: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
99 | va_list *) ATTRIBUTE_GCC_DIAG (4,0);
| ^~~~~~~~~~~~~~~~~~
make[3]: *** [Makefile:1110: insn-preds.o] Fehler 1
make[3]: *** Es wird auf noch nicht beendete Prozesse gewartet....
In Datei, eingebunden von ./config.h:8,
von ../../gcc-8/gcc/ggc-page.c:20:
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:57:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
57 | ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:59:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
59 | ATTRIBUTE_GCC_DIAG(1,2) ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:61:46: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
61 | extern bool warning (int, const char *, ...) ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:64:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
64 | ATTRIBUTE_GCC_DIAG(4,6) ATTRIBUTE_GCC_DIAG(5,6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:64:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
64 | ATTRIBUTE_GCC_DIAG(4,6) ATTRIBUTE_GCC_DIAG(5,6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:67:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
67 | ATTRIBUTE_GCC_DIAG(4, 6) ATTRIBUTE_GCC_DIAG(5, 6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:67:30: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
67 | ATTRIBUTE_GCC_DIAG(4, 6) ATTRIBUTE_GCC_DIAG(5, 6);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:69:5: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
69 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:71:5: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
71 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:72:39: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
72 | extern void error (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:75:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
75 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:75:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
75 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:76:54: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
76 | extern void error_at (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:78:3: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
78 | ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:163:57: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
163 | #define ATTRIBUTE_NORETURN __attribute__ ((__noreturn__))
| ^
../../gcc-8/gcc/diagnostic-core.h:80:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NORETURN«
80 | ATTRIBUTE_NORETURN;
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:83:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
83 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:85:6: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
85 | ATTRIBUTE_GCC_DIAG(3,4);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:86:55: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
86 | extern bool permerror (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
|
^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:88:13: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
88 | ...) ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:89:39: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
89 | extern void sorry (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:90:52: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
90 | extern void inform (location_t, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:91:57: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
91 | extern void inform (rich_location *, const char *, ...)
ATTRIBUTE_GCC_DIAG(2,3);
|
^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:94:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
94 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:94:29: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
94 | ATTRIBUTE_GCC_DIAG(3,5) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:95:42: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
95 | extern void verbatim (const char *, ...) ATTRIBUTE_GCC_DIAG(1,2);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:97:28: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
97 | const char *, ...) ATTRIBUTE_GCC_DIAG(4,5);
| ^~~~~~~~~~~~~~~~~~
../../gcc-8/gcc/../include/ansidecl.h:169:64: Fehler: »cgraph_node« ist nicht
als ein Typ definiert
169 | # define ATTRIBUTE_NONNULL(m) __attribute__ ((__nonnull__ (m)))
| ^
../../gcc-8/gcc/diagnostic-core.h:52:86: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_NONNULL«
52 | #define ATTRIBUTE_GCC_DIAG(m, n) __attribute__ ((__format__
(GCC_DIAG_STYLE, m, n))) ATTRIBUTE_NONNULL(m)
|
^~~~~~~~~~~~~~~~~
../../gcc-8/gcc/diagnostic-core.h:99:20: Anmerkung: bei Substitution des Makros
»ATTRIBUTE_GCC_DIAG«
99 | va_list *) ATTRIBUTE_GCC_DIAG (4,0);
| ^~~~~~~~~~~~~~~~~~
make[3]: *** [Makefile:1110: ggc-page.o] Fehler 1
make[3]: *** [Makefile:1110: insn-output.o] Fehler 1
/bin/sh ../../gcc-8/gcc/../move-if-change tmp-attrtab.c insn-attrtab.c
/bin/sh ../../gcc-8/gcc/../move-if-change tmp-dfatab.c insn-dfatab.c
/bin/sh ../../gcc-8/gcc/../move-if-change tmp-latencytab.c insn-latencytab.c
echo timestamp > s-attrtab
/bin/sh ../../gcc-8/gcc/../move-if-change tmp-automata.c insn-automata.c
echo timestamp > s-automata
make[3]: Verzeichnis „/home/ig25/Gcc/8-bin/gcc“ wird verlassen
make[2]: *** [Makefile:4626: all-stage1-gcc] Fehler 2
make[2]: Verzeichnis „/home/ig25/Gcc/8-bin“ wird verlassen
make[1]: *** [Makefile:27532: stage1-bubble] Fehler 2
make[1]: Verzeichnis „/home/ig25/Gcc/8-bin“ wird verlassen
make: *** [Makefile:953: all] Fehler 2
>From gcc-bugs-return-664204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:32:00 2019
Return-Path: <gcc-bugs-return-664204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67199 invoked by alias); 30 Dec 2019 12:31:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67148 invoked by uid 48); 30 Dec 2019 12:31:55 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/91541] [C++17] Exception specification of operator= of node-based containers may be broken
Date: Mon, 30 Dec 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91541-4-YksiffHiAS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91541-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91541-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02274.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91541
--- Comment #15 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #14)
> And please also fix the comment in the new test.
(In reply to Jonathan Wakely from comment #13)
> (In reply to Thomas Koenig from comment #12)
> > (In reply to Thomas Koenig from comment #11)
> >
> > *sigh* corrected in the original PR.
>
> Please add a 'fixup' to the bugdb.py file in the gcc-conversion repo, so
> this can be fixed in the Git conversion
How? I know nothing about git.
>From gcc-bugs-return-664205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:35:42 2019
Return-Path: <gcc-bugs-return-664205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70257 invoked by alias); 30 Dec 2019 12:35: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 70220 invoked by uid 55); 30 Dec 2019 12:35:37 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91651] [F03] Implement KIND argument for INDEX
Date: Mon, 30 Dec 2019 12:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91651-4-WYCDL9Aa7I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02275.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91651
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Mon Dec 30 12:35:05 2019
New Revision: 279766
URL: https://gcc.gnu.org/viewcvs?rev=279766&root=gcc&view=rev
Log:
2019-12-30 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/91651
* gfortran.dg/index_3.f90: Fix PR number.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/index_3.f90
>From gcc-bugs-return-664206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:43:31 2019
Return-Path: <gcc-bugs-return-664206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89159 invoked by alias); 30 Dec 2019 12:43:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89086 invoked by uid 48); 30 Dec 2019 12:43:25 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Mon, 30 Dec 2019 12:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-iU2PwXsfDE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02276.txt.bz2
Content-length: 1023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #28 from Alexander Cherepanov <ch3root at openwall dot com> ---
I see the same even with pure pointers. I guess RTL doesn't care about such
differences but it means the problem could bite a relatively innocent code.
----------------------------------------------------------------------
#include <stdio.h>
__attribute__((noipa)) // imagine it in a separate TU
static int *opaque(int *p) { return p; }
int main()
{
static int x, y;
int *r = opaque(&x) + (opaque(&y) - &y);
x = 1;
*r = 2;
printf("x = %d\n", x);
}
----------------------------------------------------------------------
$ gcc -std=c11 -pedantic -Wall -Wextra test.c && ./a.out
x = 2
$ gcc -std=c11 -pedantic -Wall -Wextra -O3 test.c && ./a.out
x = 1
----------------------------------------------------------------------
gcc x86-64 version: gcc (GCC) 10.0.0 20191230 (experimental)
----------------------------------------------------------------------
>From gcc-bugs-return-664207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:54:01 2019
Return-Path: <gcc-bugs-return-664207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96633 invoked by alias); 30 Dec 2019 12:54: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 96584 invoked by uid 48); 30 Dec 2019 12:53:56 -0000
From: "zhongyunde at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93102] [optimization] is it legal to avoid accessing const local array from stack ?
Date: Mon, 30 Dec 2019 12:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: zhongyunde at huawei 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-93102-4-mX0eBNAG9P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93102-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93102-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02277.txt.bz2
Content-length: 304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93102
--- Comment #2 from vfdff <zhongyunde at huawei dot com> ---
do you mean the optimization memtioned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47980
Yes, it can be with optimized option '-fmerge-all-constants', but it doesn't
active in default.
>From gcc-bugs-return-664208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 12:55:49 2019
Return-Path: <gcc-bugs-return-664208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99439 invoked by alias); 30 Dec 2019 12:55: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 99355 invoked by uid 48); 30 Dec 2019 12:55:44 -0000
From: "keremkat+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/79412] [8/9/10 Regression] ICE in fold_convert_loc, at fold-const.c:2239
Date: Mon, 30 Dec 2019 12:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: keremkat+gcc at gmail 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-79412-4-Ac9O0N8Rzf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79412-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02278.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79412
Kerem Kat <keremkat+gcc at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |keremkat+gcc at gmail dot com
--- Comment #7 from Kerem Kat <keremkat+gcc at gmail dot com> ---
Not reproducible on trunk (10).
$ gcc z1.c
z1.c:6:5: error: conflicting types for ‘a’
6 | int a[] = {2};
| ^
z1.c:1:5: note: previous declaration of ‘a’ was here
1 | int a;
| ^
z1.c:4: confused by earlier errors, bailing out
>From gcc-bugs-return-664209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:02:19 2019
Return-Path: <gcc-bugs-return-664209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89618 invoked by alias); 30 Dec 2019 13:02:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78557 invoked by uid 48); 30 Dec 2019 13:02:14 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Mon, 30 Dec 2019 13:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-A8ofPt5XY9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02279.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #29 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Alexander Cherepanov from comment #28)
> I see the same even with pure pointers. I guess RTL doesn't care about such
> differences but it means the problem could bite a relatively innocent code.
Can you please open a separate bugreport for this and reference the new bug #
here? It's a separate issue, and it's also a regression, gcc-4.7 did not
miscompile this. The responsible pass seems to be RTL DSE.
>From gcc-bugs-return-664210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:11:13 2019
Return-Path: <gcc-bugs-return-664210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88616 invoked by alias); 30 Dec 2019 13:11:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88548 invoked by uid 55); 30 Dec 2019 13:11:08 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92961] [8/9 Regression] ICE in gfc_zero_size_array, at fortran/arith.c:1680
Date: Mon, 30 Dec 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92961-4-JNqLG55QtH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02280.txt.bz2
Content-length: 1151
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92961
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Mon Dec 30 13:10:37 2019
New Revision: 279767
URL: https://gcc.gnu.org/viewcvs?rev=279767&root=gcc&view=rev
Log:
Catch division by zero errors in array sizes.
2019-12-30 Thomas Koenig <tkoenig@gcc.gnu.org>
Backport from trunk
PR fortran/92961
* gfortran.h (gfc_seen_div0): Add declaration.
* arith.h (gfc_seen_div0): Add definition.
(eval_intrinsic): For integer division by zero, set gfc_seen_div0.
* decl.c (variable_decl): If resolution resp. simplification
fails for array spec and a division of zero error has been
seen, return MATCH_ERROR.
2019-12-30 Thomas Koenig <tkoenig@gcc.gnu.org>
Backport from trunk
PR fortran/92961
* gfortran.dg/arith_divide_2.f90: New test.
Added:
branches/gcc-9-branch/gcc/testsuite/gfortran.dg/arith_divide_2.f90
Modified:
branches/gcc-9-branch/gcc/fortran/arith.c
branches/gcc-9-branch/gcc/fortran/decl.c
branches/gcc-9-branch/gcc/fortran/gfortran.h
>From gcc-bugs-return-664212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:12:48 2019
Return-Path: <gcc-bugs-return-664212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90631 invoked by alias); 30 Dec 2019 13:12:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90582 invoked by uid 48); 30 Dec 2019 13:12:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] ice for broken C code
Date: Mon, 30 Dec 2019 13:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: keremkat+gcc at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-92833-4-qIci3PWxPI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02282.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |tkoenig at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |keremkat+gcc at gmail dot com
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Kerem Kat from comment #4)
> Please assign to me.
Happy to oblige.
>From gcc-bugs-return-664211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:12:12 2019
Return-Path: <gcc-bugs-return-664211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89760 invoked by alias); 30 Dec 2019 13:12:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89708 invoked by uid 48); 30 Dec 2019 13:12:08 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93010] Wrong optimization: provenance affects comparison of saved bits of addresses of dead auto variables
Date: Mon, 30 Dec 2019 13:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93010-4-VvruqvQTUs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93010-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93010-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02281.txt.bz2
Content-length: 923
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93010
--- Comment #2 from Alexander Cherepanov <ch3root at openwall dot com> ---
But gcc seems to be better than clang in arranging compound literals in memory
so here is a gcc-only testcase with them:
----------------------------------------------------------------------
#include <stdio.h>
int main()
{
unsigned long u, v;
{
u = (unsigned long)&(int){0};
}
{
v = (unsigned long)&(int){0};
}
printf("diff = %lu\n", u - v);
printf("eq = %d\n", u == v);
}
----------------------------------------------------------------------
$ gcc -std=c11 -pedantic -Wall -Wextra -O3 test.c && ./a.out
diff = 0
eq = 0
----------------------------------------------------------------------
gcc x86-64 version: gcc (GCC) 10.0.0 20191230 (experimental)
----------------------------------------------------------------------
>From gcc-bugs-return-664213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:15:25 2019
Return-Path: <gcc-bugs-return-664213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93739 invoked by alias); 30 Dec 2019 13:15:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93471 invoked by uid 48); 30 Dec 2019 13:15:00 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92961] [8 Regression] ICE in gfc_zero_size_array, at fortran/arith.c:1680
Date: Mon, 30 Dec 2019 13:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: dependson target_milestone short_desc
Message-ID: <bug-92961-4-KbmH0bT0G6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02283.txt.bz2
Content-length: 806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92961
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |93104
Target Milestone|--- |8.4
Summary|[8/9 Regression] ICE in |[8 Regression] ICE in
|gfc_zero_size_array, at |gfc_zero_size_array, at
|fortran/arith.c:1680 |fortran/arith.c:1680
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Commit to 8-branch held up by PR 93104.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
[Bug 93104] [8/10 Regression] Current trunk can not build gcc 8
>From gcc-bugs-return-664214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:20:04 2019
Return-Path: <gcc-bugs-return-664214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98422 invoked by alias); 30 Dec 2019 13:20:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94147 invoked by uid 48); 30 Dec 2019 13:19:59 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92993] [8/9/10 Regression] ICE in maybe_canonicalize_comparison_1, at fold-const.c:8845
Date: Mon, 30 Dec 2019 13:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
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-92993-4-Vb36r8zlOD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92993-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92993-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02284.txt.bz2
Content-length: 786
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92993
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> There is a warning about interface mismatch, but probably the FE should on
> interface mismatch just use an DECL_EXTERNAL decl from the interface rather
> than the actual definition.
Or issue an error, I think this would be preferable.
Trying to fix up broken code so that it compiles, but will
probably generate wrong results at runtime, seems wrong.
>From gcc-bugs-return-664215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 13:59:25 2019
Return-Path: <gcc-bugs-return-664215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64648 invoked by alias); 30 Dec 2019 13:59:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64593 invoked by uid 48); 30 Dec 2019 13:59:21 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93105] New: Wrong optimization for pointers: provenance of `p + (q1 - q2)` is treated as `q` when the provenance of `p` is unknown
Date: Mon, 30 Dec 2019 13:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93105-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02285.txt.bz2
Content-length: 1804
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93105
Bug ID: 93105
Summary: Wrong optimization for pointers: provenance of `p +
(q1 - q2)` is treated as `q` when the provenance of
`p` is unknown
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ch3root at openwall dot com
Target Milestone: ---
gcc seems to wrongly infer provenance of a pointer expression of the form `p +
(q1 - q2)` when the following conditions hold:
- the provenance of the pointer `p` couldn't be tracked;
- the provenance of `q1` or `q2` is known;
- `q1 - q2` couldn't be simplified to get rid of pointers.
----------------------------------------------------------------------
#include <stdio.h>
__attribute__((noipa)) // imagine it in a separate TU
static int *opaque(int *p) { return p; }
int main()
{
static int x, y;
int *r = opaque(&x) + (opaque(&y) - &y);
x = 1;
*r = 2;
printf("x = %d\n", x);
}
----------------------------------------------------------------------
$ gcc -std=c11 -pedantic -Wall -Wextra test.c && ./a.out
x = 2
$ gcc -std=c11 -pedantic -Wall -Wextra -O3 test.c && ./a.out
x = 1
----------------------------------------------------------------------
gcc x86-64 version: gcc (GCC) 10.0.0 20191230 (experimental)
----------------------------------------------------------------------
The problem is similar to pr49330. Analysis by Alexander Monakov via bug 49330,
comment 29:
"It's a separate issue, and it's also a regression, gcc-4.7 did not miscompile
this. The responsible pass seems to be RTL DSE."
>From gcc-bugs-return-664216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:01:03 2019
Return-Path: <gcc-bugs-return-664216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66501 invoked by alias); 30 Dec 2019 14:01:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66417 invoked by uid 48); 30 Dec 2019 14:00:59 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Mon, 30 Dec 2019 14:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-OSH5FB63K1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02286.txt.bz2
Content-length: 181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #30 from Alexander Cherepanov <ch3root at openwall dot com> ---
Sure, I've filed pr93105. Thanks for the analysis!
>From gcc-bugs-return-664217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:14:47 2019
Return-Path: <gcc-bugs-return-664217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94849 invoked by alias); 30 Dec 2019 14:14:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94821 invoked by uid 48); 30 Dec 2019 14:14:43 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93104] [8/10 Regression] Current trunk can not build gcc 8
Date: Mon, 30 Dec 2019 14:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-93104-4-LO0rQLiT97@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02287.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.4
>From gcc-bugs-return-664218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:23:02 2019
Return-Path: <gcc-bugs-return-664218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110938 invoked by alias); 30 Dec 2019 14:23: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 110883 invoked by uid 48); 30 Dec 2019 14:22:58 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93104] [10 Regression] Current trunk can not build gcc 8
Date: Mon, 30 Dec 2019 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-93104-4-riAvv4sy1f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02288.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/10 Regression] Current |[10 Regression] Current
|trunk can not build gcc 8 |trunk can not build gcc 8
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Same error occurs with gcc 8.3.0 release.
So, this is a trunk problem.
>From gcc-bugs-return-664219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:31:05 2019
Return-Path: <gcc-bugs-return-664219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70384 invoked by alias); 30 Dec 2019 14:31:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63376 invoked by uid 48); 30 Dec 2019 14:31:00 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93104] [9/10 Regression] Current trunk can not build gcc 8
Date: Mon, 30 Dec 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also short_desc
Message-ID: <bug-93104-4-Tsc0bqR8Aw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02289.txt.bz2
Content-length: 760
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=90677
Summary|[10 Regression] Current |[9/10 Regression] Current
|trunk can not build gcc 8 |trunk can not build gcc 8
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Also happens with gcc 9.
Related to / fallout from / duplicate of PR 90677?
>From gcc-bugs-return-664220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:48:40 2019
Return-Path: <gcc-bugs-return-664220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24516 invoked by alias); 30 Dec 2019 14:48:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24391 invoked by uid 48); 30 Dec 2019 14:48:35 -0000
From: "ph3rin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93106] New: [c++2a] Deleted move constructor is not selected when returning an automatic variable
Date: Mon, 30 Dec 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ph3rin 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-93106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02290.txt.bz2
Content-length: 1101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93106
Bug ID: 93106
Summary: [c++2a] Deleted move constructor is not selected when
returning an automatic variable
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ph3rin at gmail dot com
Target Milestone: ---
According to the c++ standard (draft n4835) the following code should not
compile because it references a deleted function:
struct not_movable {
not_movable() = default;
not_movable(not_movable const&) = default;
not_movable(not_movable&&) = delete;
};
not_movable foo() {
not_movable obj;
return obj;
}
When returning obj, the overload resolution should successfully select the
deleted move constructor, therefore resulting in a compiler error.
The code has been tested under gcc 9.2 with compiler flags -std=c++2a.
Quotes from the standard: http://eel.is/c++draft/class.copy.elision#3
>From gcc-bugs-return-664221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:51:16 2019
Return-Path: <gcc-bugs-return-664221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47351 invoked by alias); 30 Dec 2019 14:51:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45941 invoked by uid 48); 30 Dec 2019 14:51:12 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93107] New: unable to deduce initializer_list<auto> from function template
Date: Mon, 30 Dec 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93107-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02291.txt.bz2
Content-length: 1091
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93107
Bug ID: 93107
Summary: unable to deduce initializer_list<auto> from function
template
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: barry.revzin at gmail dot com
Target Milestone: ---
Reduced from StackOverflow:
#include <initializer_list>
template<typename T>
void Task() {}
auto a = &Task<int>;
auto b = { &Task<int> };
std::initializer_list<void(*)()> c = { &Task<int> };
auto d = { static_cast<void(*)()>(&Task<int>) };
The declarations for 'a', 'c', and 'd' all compile. But the declaration for 'b'
is rejected with:
<source>:7:23: error: unable to deduce 'std::initializer_list<auto>' from '{(&
Task<int>)}'
7 | auto b = { &Task<int> };
| ^
<source>:7:23: note: couldn't deduce template parameter 'auto'
Compiler returned: 1
All four compile on clang.
>From gcc-bugs-return-664222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:51:37 2019
Return-Path: <gcc-bugs-return-664222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48126 invoked by alias); 30 Dec 2019 14:51: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 48079 invoked by uid 48); 30 Dec 2019 14:51:32 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93107] unable to deduce initializer_list<auto> from function template
Date: Mon, 30 Dec 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93107-4-AeT56hgSd8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93107-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93107-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02292.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93107
--- Comment #1 from Barry Revzin <barry.revzin at gmail dot com> ---
Meant to add the StackOverflow link:
https://stackoverflow.com/q/59517774/2069064
>From gcc-bugs-return-664223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 14:55:04 2019
Return-Path: <gcc-bugs-return-664223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63764 invoked by alias); 30 Dec 2019 14:55:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63498 invoked by uid 48); 30 Dec 2019 14:54:58 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93101] [regression] ICE - aggregate initialization of base
Date: Mon, 30 Dec 2019 14:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-93101-4-7BBIU4ZT71@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02293.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93101
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
93101.C: In function ‘foo create()’:
93101.C:15:5: error: incorrect sharing of tree nodes
15 | foo create()
| ^~~~~~
*<retval>
<retval>->a = _1;
during GIMPLE pass: cfg
almost surely a dup of the existing "incorrect sharing of tree nodes" PR.
>From gcc-bugs-return-664224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 15:21:31 2019
Return-Path: <gcc-bugs-return-664224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76811 invoked by alias); 30 Dec 2019 15:21:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76769 invoked by uid 48); 30 Dec 2019 15:21:27 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92961] [8 Regression] ICE in gfc_zero_size_array, at fortran/arith.c:1680
Date: Mon, 30 Dec 2019 15:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: dependson
Message-ID: <bug-92961-4-T1K7MjxiHq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02294.txt.bz2
Content-length: 622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92961
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on|93104 |
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Boostrapping gcc 8 with the system compiler (gcc 7.4.1) worked, so
I can regression-test the fix 93104. Unsetting "Depends on".
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
[Bug 93104] [9/10 Regression] Current trunk can not build gcc 8
>From gcc-bugs-return-664225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 15:23:05 2019
Return-Path: <gcc-bugs-return-664225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78186 invoked by alias); 30 Dec 2019 15:23:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78128 invoked by uid 48); 30 Dec 2019 15:23:01 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92896] [10 Regression] [DEC] ICE in reduce_unary, at fortran/arith.c:1283
Date: Mon, 30 Dec 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-92896-4-pU8Dp3EN9X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92896-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92896-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02295.txt.bz2
Content-length: 714
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92896
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |tkoenig at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to MarkEggleston from comment #6)
> This has been fixed, see comment 5.
>
> I do not have permission to changes the status so somebody that does will
> need to do so.
Fixing, then.
Thanks for the patch!
>From gcc-bugs-return-664226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 15:27:43 2019
Return-Path: <gcc-bugs-return-664226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84255 invoked by alias); 30 Dec 2019 15:27: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 84213 invoked by uid 55); 30 Dec 2019 15:27:39 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92961] [8 Regression] ICE in gfc_zero_size_array, at fortran/arith.c:1680
Date: Mon, 30 Dec 2019 15:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92961-4-3y0VKEdigG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02296.txt.bz2
Content-length: 549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92961
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Mon Dec 30 15:27:08 2019
New Revision: 279769
URL: https://gcc.gnu.org/viewcvs?rev=279769&root=gcc&view=rev
Log:
2019-12-30 Thomas Koenig <tkoenig@gcc.gnu.org>
Backport from trunk
PR fortran/92961
* fortran/ChangeLog: Added entry.
* testsuite/ChangeLog: Added entry.
Modified:
branches/gcc-9-branch/gcc/fortran/ChangeLog
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 15:30:19 2019
Return-Path: <gcc-bugs-return-664227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98997 invoked by alias); 30 Dec 2019 15:30: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 98847 invoked by uid 55); 30 Dec 2019 15:30:02 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92961] [8 Regression] ICE in gfc_zero_size_array, at fortran/arith.c:1680
Date: Mon, 30 Dec 2019 15:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92961-4-gym8kSKaRd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02297.txt.bz2
Content-length: 1249
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92961
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Mon Dec 30 15:29:30 2019
New Revision: 279770
URL: https://gcc.gnu.org/viewcvs?rev=279770&root=gcc&view=rev
Log:
Catch division by zero errors in array sizes.
2019-12-30 Thomas Koenig <tkoenig@gcc.gnu.org>
Backport from trunk
PR fortran/92961
* gfortran.h (gfc_seen_div0): Add declaration.
* arith.h (gfc_seen_div0): Add definition.
(eval_intrinsic): For integer division by zero, set gfc_seen_div0.
* decl.c (variable_decl): If resolution resp. simplification
fails for array spec and a division of zero error has been
seen, return MATCH_ERROR.
2019-12-30 Thomas Koenig <tkoenig@gcc.gnu.org>
Backport from trunk
PR fortran/92961
* gfortran.dg/arith_divide_2.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/arith_divide_2.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/arith.c
branches/gcc-8-branch/gcc/fortran/decl.c
branches/gcc-8-branch/gcc/fortran/gfortran.h
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 15:31:24 2019
Return-Path: <gcc-bugs-return-664228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101520 invoked by alias); 30 Dec 2019 15:31:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100985 invoked by uid 48); 30 Dec 2019 15:31:19 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92961] [8 Regression] ICE in gfc_zero_size_array, at fortran/arith.c:1680
Date: Mon, 30 Dec 2019 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92961-4-rke8p1X0uV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92961-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02298.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92961
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on all open branches.
Thanks for the bug report!
>From gcc-bugs-return-664229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 15:55:46 2019
Return-Path: <gcc-bugs-return-664229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50766 invoked by alias); 30 Dec 2019 15:55: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 50698 invoked by uid 48); 30 Dec 2019 15:55:41 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31016] Use __buildin_memcpy and __memcpy for array assignment
Date: Mon, 30 Dec 2019 15:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-31016-4-vj1T5asetV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-31016-4@http.gcc.gnu.org/bugzilla/>
References: <bug-31016-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02299.txt.bz2
Content-length: 315
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31016
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Excellent news: The __builtin_memcpy cases have been fixed in the
meantime, and using __builtin_memset for values of more than one
byte doesn't work.
I will commit a test case and then close.
>From gcc-bugs-return-664230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 16:10:49 2019
Return-Path: <gcc-bugs-return-664230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105654 invoked by alias); 30 Dec 2019 16:10: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 105582 invoked by uid 48); 30 Dec 2019 16:10:46 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31016] Use __buildin_memcpy and __memcpy for array assignment
Date: Mon, 30 Dec 2019 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-31016-4-RIqE8v4gio@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-31016-4@http.gcc.gnu.org/bugzilla/>
References: <bug-31016-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02300.txt.bz2
Content-length: 226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31016
--- Comment #11 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Correction: The rank-1 copying cases are now handled by the middle end,
the two-dimensional case isn't.
>From gcc-bugs-return-664231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 17:04:07 2019
Return-Path: <gcc-bugs-return-664231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5614 invoked by alias); 30 Dec 2019 17:04:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5516 invoked by uid 48); 30 Dec 2019 17:04:03 -0000
From: "anlauf at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93091] [OOP] Apparent bugs in "sizeof" and "transfer" intrinsic functions
Date: Mon, 30 Dec 2019 17:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component short_desc
Message-ID: <bug-93091-4-9CDFo92p2A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02301.txt.bz2
Content-length: 1175
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93091
anlauf at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|libfortran |fortran
Summary|Apparent bugs in "sizeof" |[OOP] Apparent bugs in
|and "transfer" intrinsic |"sizeof" and "transfer"
|functions |intrinsic functions
--- Comment #1 from anlauf at gcc dot gnu.org ---
If I add the following to poly/poly1, I get correct results:
select type (obj)
type is (character(*))
print "('Sizeof: ',i0)", sizeof(obj)
print "('Transfer: ',i0)",
size(transfer(obj,[0_c_int8_t]),kind=c_size_t)
type is (integer)
print "('Sizeof: ',i0)", sizeof(obj)
print "('Transfer: ',i0)",
size(transfer(obj,[0_c_int8_t]),kind=c_size_t)
end select
This will print:
Character
DIRECT-C
sizeof: 80
transfer: 80
POLY
sizeof: 1
transfer: 1
Sizeof: 80
Transfer: 80
etc.
Apparently OOP-related. Not sure if the bug is in the source code or
in the compiler handling polymorphism.
>From gcc-bugs-return-664232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 17:38:15 2019
Return-Path: <gcc-bugs-return-664232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58590 invoked by alias); 30 Dec 2019 17:38:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58471 invoked by uid 48); 30 Dec 2019 17:38:10 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90677] [9 Regression] gcc-9.1.0 fails to build __gcc_diag__ souce: error: 'cgraph_node' is not defined as a type
Date: Mon, 30 Dec 2019 17:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-90677-4-827zquAjJz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02302.txt.bz2
Content-length: 266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90677
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47568
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47568&action=edit
gcc10-pr90677-2.patch
Untested fix for that.
>From gcc-bugs-return-664233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 17:42:05 2019
Return-Path: <gcc-bugs-return-664233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61036 invoked by alias); 30 Dec 2019 17:42:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60988 invoked by uid 48); 30 Dec 2019 17:42:01 -0000
From: "keremkat+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92833] ice for broken C code
Date: Mon, 30 Dec 2019 17:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: keremkat+gcc at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: keremkat+gcc at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92833-4-3CVppznNyp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02303.txt.bz2
Content-length: 375
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92833
--- Comment #6 from Kerem Kat <keremkat+gcc at gmail dot com> ---
Created attachment 47569
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47569&action=edit
fix ice
PR c/92833
* parser.c (c_parser_consume_token): Fix peeked
token stack pop to support 4 available tokens.
* c-c++-common/pr92833-*.c: New tests.
>From gcc-bugs-return-664235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 18:12:51 2019
Return-Path: <gcc-bugs-return-664235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123235 invoked by alias); 30 Dec 2019 18:12:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117091 invoked by uid 48); 30 Dec 2019 18:12:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/93104] [9/10 Regression] Current trunk can not build gcc 8
Date: Mon, 30 Dec 2019 18:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93104-4-NGRKNq0H4j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93104-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02305.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93104
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yes.
*** This bug has been marked as a duplicate of bug 90677 ***
>From gcc-bugs-return-664234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 18:12:51 2019
Return-Path: <gcc-bugs-return-664234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123085 invoked by alias); 30 Dec 2019 18:12:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117578 invoked by uid 48); 30 Dec 2019 18:12:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90677] [9 Regression] gcc-9.1.0 fails to build __gcc_diag__ souce: error: 'cgraph_node' is not defined as a type
Date: Mon, 30 Dec 2019 18:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90677-4-q45G1n4w66@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02304.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90677
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
*** Bug 93104 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-664236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 19:13:04 2019
Return-Path: <gcc-bugs-return-664236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73669 invoked by alias); 30 Dec 2019 19:13: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 73572 invoked by uid 48); 30 Dec 2019 19:13:00 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Mon, 30 Dec 2019 19:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93059-4-Bzdrg04EWq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02306.txt.bz2
Content-length: 2385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #28 from fdlbxtqi <euloanty at live dot com> ---
Created attachment 47570
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47570&action=edit
Testsuite
Testsuite :
cqwrteur@DESKTOP-7H7UHQ9:~/libstdcpp_testsuite$ runtest --tool libstdc++
Using ../gcc/libstdc++-v3/testsuite/lib/libstdc++.exp as tool init file.
Test run by cqwrteur on Mon Dec 30 05:14:00 2019
Schedule of variations:
unix
Running target unix
Running ../gcc/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ..
.
=== libstdc++ Summary ===
# of expected passes 12982
# of unexpected failures 6
# of expected failures 92
# of unsupported tests 614
After patch:
cqwrteur@DESKTOP-7H7UHQ9:~/libstdcpp_testsuite$ runtest --tool libstdc++
--srcdir=../gcc/libstdc++-v3/testsuite
Using ../gcc/libstdc++-v3/testsuite/lib/libstdc++.exp as tool init file.
Test run by cqwrteur on Mon Dec 30 09:58:12 2019
Native configuration is x86_64-pc-linux-gnu
=== libstdc++ tests ===
Schedule of variations:
unix
Running target unix
Using /usr/share/dejagnu/baseboards/unix.exp as board description file for
target.
Using /usr/share/dejagnu/config/unix.exp as generic interface file for target.
Using ../gcc/libstdc++-v3/testsuite/config/default.exp as
tool-and-target-specific interface file.
Running ../gcc/libstdc++-v3/testsuite/libstdc++-abi/abi.exp ...
Running ../gcc/libstdc++-v3/testsuite/libstdc++-dg/conformance.exp ...
FAIL: 18_support/set_terminate.cc execution test
FAIL: 18_support/set_unexpected.cc execution test
FAIL: 20_util/bind/ref_neg.cc (test for excess errors)
FAIL: 27_io/filesystem/path/concat/92853.cc execution test
FAIL: 27_io/filesystem/path/concat/path.cc execution test
FAIL: experimental/net/internet/resolver/ops/lookup.cc execution test
Running
../gcc/libstdc++-v3/testsuite/libstdc++-prettyprinters/prettyprinters.exp ...
Running ../gcc/libstdc++-v3/testsuite/libstdc++-xmethods/xmethods.exp ...
=== libstdc++ Summary ===
# of expected passes 12982
# of unexpected failures 6
# of expected failures 92
# of unsupported tests 614
cqwrteur@DESKTOP-7H7UHQ9:~/libstdcpp_testsuite$
>From gcc-bugs-return-664237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 19:15:59 2019
Return-Path: <gcc-bugs-return-664237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84092 invoked by alias); 30 Dec 2019 19:15:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84039 invoked by uid 48); 30 Dec 2019 19:15:53 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Mon, 30 Dec 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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93059-4-BwGFUCCNTO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02307.txt.bz2
Content-length: 699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #29 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Marc Glisse from comment #17)
> (In reply to fdlbxtqi from comment #15)
> > What I am worried about is that whether revamping these functions would be a new wave of ABI breaking.
>
> I don't foresee any ABI issue here. Do make sure your code doesn't break
> with -std=c++03, and run the testsuite before submitting it.
I think the test suite has passed. However, I am not sure since I have never
used dejagnu before.
It looks like these test suites will fail in some cases even without my patch.
(filesystem, network ts for example)
I need you to check them.
>From gcc-bugs-return-664238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 19:23:40 2019
Return-Path: <gcc-bugs-return-664238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101571 invoked by alias); 30 Dec 2019 19:23:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101529 invoked by uid 48); 30 Dec 2019 19:23:36 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Mon, 30 Dec 2019 19:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93059-4-JQlImz04GM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02308.txt.bz2
Content-length: 344
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #30 from fdlbxtqi <euloanty at live dot com> ---
Created attachment 47571
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47571&action=edit
Here is my stl_algobase.h after patch. You can try it directly.
Here is my stl_algobase.h after patch. You can try it directly.
>From gcc-bugs-return-664239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 19:25:29 2019
Return-Path: <gcc-bugs-return-664239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103362 invoked by alias); 30 Dec 2019 19:25:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103321 invoked by uid 48); 30 Dec 2019 19:25:23 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Mon, 30 Dec 2019 19:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93059-4-KOGxQEe65P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02309.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #31 from Bernd Edlinger <bernd.edlinger at hotmail dot de> ---
Yes, you usually need to make a full bootstrap / make check twice
which the same svn revision one with and one without your patch.
You also should make sure that the test case actually is able to fail
before your patch.
You run "$(srcdir)/contrib/test_summary -t" each time and
compare the output.
>From gcc-bugs-return-664240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 19:36:03 2019
Return-Path: <gcc-bugs-return-664240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110770 invoked by alias); 30 Dec 2019 19:36: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 110709 invoked by uid 48); 30 Dec 2019 19:35:59 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/61502] == comparison on "one-past" pointer gives wrong result
Date: Mon, 30 Dec 2019 19:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
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:
Message-ID: <bug-61502-4-tlraoFBjwg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61502-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61502-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02310.txt.bz2
Content-length: 806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61502
--- Comment #37 from Alexander Cherepanov <ch3root at openwall dot com> ---
On 30/12/2019 10.51, rguenther at suse dot de wrote:
>> Obviously, it could be used to fold `a + i == b` to `0` if `a` and `b`
>> are two different known arrays and `i` is unknown
>
> That's indeed the main thing. Basically it allows points-to analysis work at
> all in the presence of non-constant offsets.
But what is PTA used for? Examples that I've seen all deal with dereferenceable
pointers. And current gcc behaviour is just fine in that case. The problem is
with non-dereferenceable pointers. So is PTA important for cases where
dereferenceability is unknown (or known to be false) or it's just too
complicated to take dereferenceability into account?
>From gcc-bugs-return-664241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 20:24:04 2019
Return-Path: <gcc-bugs-return-664241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25493 invoked by alias); 30 Dec 2019 20:24:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25362 invoked by uid 55); 30 Dec 2019 20:23:58 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92923] __builtin_vec_xor() causes subregs to be used when not using V4SImode vectors
Date: Mon, 30 Dec 2019 20:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92923-4-nANkr7cXDv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02311.txt.bz2
Content-length: 7355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92923
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
Author: bergner
Date: Mon Dec 30 20:23:25 2019
New Revision: 279772
URL: https://gcc.gnu.org/viewcvs?rev=279772&root=gcc&view=rev
Log:
Fix builtin functions needlessly using VIEW_CONVERT_EXPRs on their operands.
gcc/
PR target/92923
* config/rs6000/rs6000-builtin.def (VAND, VANDC, VNOR, VOR, VXOR):
Delete.
(EQV_V16QI_UNS, EQV_V8HI_UNS, EQV_V4SI_UNS, EQV_V2DI_UNS, EQV_V1TI_UNS,
NAND_V16QI_UNS, NAND_V8HI_UNS, NAND_V4SI_UNS, NAND_V2DI_UNS,
NAND_V1TI_UNS, ORC_V16QI_UNS, ORC_V8HI_UNS, ORC_V4SI_UNS, ORC_V2DI_UNS,
ORC_V1TI_UNS, VAND_V16QI_UNS, VAND_V16QI, VAND_V8HI_UNS, VAND_V8HI,
VAND_V4SI_UNS, VAND_V4SI, VAND_V2DI_UNS, VAND_V2DI, VAND_V4SF,
VAND_V2DF, VANDC_V16QI_UNS, VANDC_V16QI, VANDC_V8HI_UNS, VANDC_V8HI,
VANDC_V4SI_UNS, VANDC_V4SI, VANDC_V2DI_UNS, VANDC_V2DI, VANDC_V4SF,
VANDC_V2DF, VNOR_V16QI_UNS, VNOR_V16QI, VNOR_V8HI_UNS, VNOR_V8HI,
VNOR_V4SI_UNS, VNOR_V4SI, VNOR_V2DI_UNS, VNOR_V2DI, VNOR_V4SF,
VNOR_V2DF, VOR_V16QI_UNS, VOR_V16QI, VOR_V8HI_UNS, VOR_V8HI,
VOR_V4SI_UNS, VOR_V4SI, VOR_V2DI_UNS, VOR_V2DI, VOR_V4SF, VOR_V2DF,
VXOR_V16QI_UNS, VXOR_V16QI, VXOR_V8HI_UNS, VXOR_V8HI,
VXOR_V4SI_UNS, VXOR_V4SI, VXOR_V2DI_UNS, VXOR_V2DI, VXOR_V4SF,
VXOR_V2DF): Add definitions.
* config/rs6000/rs6000-call.c (altivec_overloaded_builtins)
<ALTIVEC_BUILTIN_VAND, ALTIVEC_BUILTIN_VANDC, ALTIVEC_BUILTIN_VNOR,
ALTIVEC_BUILTIN_VOR, ALTIVEC_BUILTIN_VXOR>: Remove.
<ALTIVEC_BUILTIN_VAND_V4SF, ALTIVEC_BUILTIN_VAND_V2DF,
ALTIVEC_BUILTIN_VAND_V2DI, ALTIVEC_BUILTIN_VAND_V2DI_UNS,
ALTIVEC_BUILTIN_VAND_V4SI_UNS, ALTIVEC_BUILTIN_VAND_V4SI,
ALTIVEC_BUILTIN_VAND_V8HI_UNS, ALTIVEC_BUILTIN_VAND_V8HI,
ALTIVEC_BUILTIN_VAND_V16QI, ALTIVEC_BUILTIN_VAND_V16QI_UNS,
ALTIVEC_BUILTIN_VANDC_V4SF, ALTIVEC_BUILTIN_VANDC_V2DF,
ALTIVEC_BUILTIN_VANDC_V2DI, ALTIVEC_BUILTIN_VANDC_V2DI_UNS,
ALTIVEC_BUILTIN_VANDC_V4SI_UNS, ALTIVEC_BUILTIN_VANDC_V4SI,
ALTIVEC_BUILTIN_VANDC_V8HI_UNS, ALTIVEC_BUILTIN_VANDC_V8HI,
ALTIVEC_BUILTIN_VANDC_V16QI, ALTIVEC_BUILTIN_VANDC_V16QI_UNS,
ALTIVEC_BUILTIN_VNOR_V4SF, ALTIVEC_BUILTIN_VNOR_V2DF,
ALTIVEC_BUILTIN_VNOR_V2DI, ALTIVEC_BUILTIN_VNOR_V2DI_UNS,
ALTIVEC_BUILTIN_VNOR_V4SI, ALTIVEC_BUILTIN_VNOR_V4SI_UNS,
ALTIVEC_BUILTIN_VNOR_V8HI, ALTIVEC_BUILTIN_VNOR_V8HI_UNS,
ALTIVEC_BUILTIN_VNOR_V16QI, ALTIVEC_BUILTIN_VNOR_V16QI_UNS,
ALTIVEC_BUILTIN_VOR_V4SF, ALTIVEC_BUILTIN_VOR_V2DF,
ALTIVEC_BUILTIN_VOR_V2DI, ALTIVEC_BUILTIN_VOR_V2DI_UNS,
ALTIVEC_BUILTIN_VOR_V4SI_UNS, ALTIVEC_BUILTIN_VOR_V4SI,
ALTIVEC_BUILTIN_VOR_V8HI_UNS, ALTIVEC_BUILTIN_VOR_V8HI,
ALTIVEC_BUILTIN_VOR_V16QI, ALTIVEC_BUILTIN_VOR_V16QI_UNS,
ALTIVEC_BUILTIN_VXOR_V4SF, ALTIVEC_BUILTIN_VXOR_V2DF,
ALTIVEC_BUILTIN_VXOR_V2DI, ALTIVEC_BUILTIN_VXOR_V2DI_UNS,
ALTIVEC_BUILTIN_VXOR_V4SI_UNS, ALTIVEC_BUILTIN_VXOR_V4SI,
ALTIVEC_BUILTIN_VXOR_V8HI, ALTIVEC_BUILTIN_VXOR_V8HI_UNS,
ALTIVEC_BUILTIN_VXOR_V16QI, ALTIVEC_BUILTIN_VXOR_V16QI_UNS>: Add
definitions.
<P8V_BUILTIN_EQV_V16QI, P8V_BUILTIN_EQV_V8HI, P8V_BUILTIN_EQV_V4SI,
P8V_BUILTIN_EQV_V2DI, P8V_BUILTIN_NAND_V16QI, P8V_BUILTIN_NAND_V8HI,
P8V_BUILTIN_NAND_V4SI, P8V_BUILTIN_NAND_V2DI, P8V_BUILTIN_ORC_V16QI,
P8V_BUILTIN_ORC_V8HI, P8V_BUILTIN_ORC_V4SI,
P8V_BUILTIN_ORC_V2DI>: Change unsigned usages to use the new *_UNS
definition names.
(rs6000_gimple_fold_builtin) <ALTIVEC_BUILTIN_VAND_V16QI_UNS,
ALTIVEC_BUILTIN_VAND_V16QI, ALTIVEC_BUILTIN_VAND_V8HI_UNS,
ALTIVEC_BUILTIN_VAND_V8HI, ALTIVEC_BUILTIN_VAND_V4SI_UNS,
ALTIVEC_BUILTIN_VAND_V4SI, ALTIVEC_BUILTIN_VAND_V2DI_UNS,
ALTIVEC_BUILTIN_VAND_V2DI, ALTIVEC_BUILTIN_VAND_V4SF,
ALTIVEC_BUILTIN_VAND_V2DF, ALTIVEC_BUILTIN_VANDC_V16QI_UNS,
ALTIVEC_BUILTIN_VANDC_V16QI, ALTIVEC_BUILTIN_VANDC_V8HI_UNS,
ALTIVEC_BUILTIN_VANDC_V8HI, ALTIVEC_BUILTIN_VANDC_V4SI_UNS,
ALTIVEC_BUILTIN_VANDC_V4SI, ALTIVEC_BUILTIN_VANDC_V2DI_UNS,
ALTIVEC_BUILTIN_VANDC_V2DI, ALTIVEC_BUILTIN_VANDC_V4SF,
ALTIVEC_BUILTIN_VANDC_V2DF, P8V_BUILTIN_NAND_V16QI_UNS,
P8V_BUILTIN_NAND_V8HI_UNS, P8V_BUILTIN_NAND_V4SI_UNS,
P8V_BUILTIN_NAND_V2DI_UNS, P8V_BUILTIN_NAND_V2DI,
ALTIVEC_BUILTIN_VOR_V16QI_UNS, ALTIVEC_BUILTIN_VOR_V16QI,
ALTIVEC_BUILTIN_VOR_V8HI_UNS, ALTIVEC_BUILTIN_VOR_V8HI,
ALTIVEC_BUILTIN_VOR_V4SI_UNS, ALTIVEC_BUILTIN_VOR_V4SI,
ALTIVEC_BUILTIN_VOR_V2DI_UNS, ALTIVEC_BUILTIN_VOR_V2DI,
ALTIVEC_BUILTIN_VOR_V4SF, ALTIVEC_BUILTIN_VOR_V2DF,
P8V_BUILTIN_ORC_V16QI_UNS, P8V_BUILTIN_ORC_V8HI_UNS,
P8V_BUILTIN_ORC_V4SI_UNS, P8V_BUILTIN_ORC_V2DI_UNS,
P8V_BUILTIN_ORC_V2DI, ALTIVEC_BUILTIN_VXOR_V16QI_UNS,
ALTIVEC_BUILTIN_VXOR_V16QI, ALTIVEC_BUILTIN_VXOR_V8HI_UNS,
ALTIVEC_BUILTIN_VXOR_V8HI, ALTIVEC_BUILTIN_VXOR_V4SI_UNS,
ALTIVEC_BUILTIN_VXOR_V4SI, ALTIVEC_BUILTIN_VXOR_V2DI_UNS,
ALTIVEC_BUILTIN_VXOR_V2DI, ALTIVEC_BUILTIN_VXOR_V4SF,
ALTIVEC_BUILTIN_VXOR_V2DF, ALTIVEC_BUILTIN_VNOR_V16QI_UNS,
ALTIVEC_BUILTIN_VNOR_V16QI, ALTIVEC_BUILTIN_VNOR_V8HI_UNS,
ALTIVEC_BUILTIN_VNOR_V8HI, ALTIVEC_BUILTIN_VNOR_V4SI_UNS,
ALTIVEC_BUILTIN_VNOR_V4SI, ALTIVEC_BUILTIN_VNOR_V2DI_UNS,
ALTIVEC_BUILTIN_VNOR_V2DI, ALTIVEC_BUILTIN_VNOR_V4SF,
ALTIVEC_BUILTIN_VNOR_V2DF>: Use new definition names.
(builtin_function_type) <ALTIVEC_BUILTIN_VAND_V16QI_UNS,
ALTIVEC_BUILTIN_VAND_V8HI_UNS, ALTIVEC_BUILTIN_VAND_V4SI_UNS,
ALTIVEC_BUILTIN_VAND_V2DI_UNS, ALTIVEC_BUILTIN_VANDC_V16QI_UNS,
ALTIVEC_BUILTIN_VANDC_V8HI_UNS, ALTIVEC_BUILTIN_VANDC_V4SI_UNS,
ALTIVEC_BUILTIN_VANDC_V2DI_UNS, ALTIVEC_BUILTIN_VNOR_V16QI_UNS,
ALTIVEC_BUILTIN_VNOR_V8HI_UNS, ALTIVEC_BUILTIN_VNOR_V4SI_UNS,
ALTIVEC_BUILTIN_VNOR_V2DI_UNS, ALTIVEC_BUILTIN_VOR_V16QI_UNS,
ALTIVEC_BUILTIN_VOR_V8HI_UNS, ALTIVEC_BUILTIN_VOR_V4SI_UNS,
ALTIVEC_BUILTIN_VOR_V2DI_UNS, ALTIVEC_BUILTIN_VXOR_V16QI_UNS,
ALTIVEC_BUILTIN_VXOR_V8HI_UNS, ALTIVEC_BUILTIN_VXOR_V4SI_UNS,
ALTIVEC_BUILTIN_VXOR_V2DI_UNS, P8V_BUILTIN_EQV_V16QI_UNS,
P8V_BUILTIN_EQV_V8HI_UNS, P8V_BUILTIN_EQV_V4SI_UNS,
P8V_BUILTIN_EQV_V2DI_UNS, P8V_BUILTIN_EQV_V1TI_UNS,
P8V_BUILTIN_NAND_V16QI_UNS, P8V_BUILTIN_NAND_V8HI_UNS,
P8V_BUILTIN_NAND_V4SI_UNS, P8V_BUILTIN_NAND_V2DI_UNS,
P8V_BUILTIN_NAND_V1TI_UNS, P8V_BUILTIN_ORC_V16QI_UNS,
P8V_BUILTIN_ORC_V8HI_UNS, P8V_BUILTIN_ORC_V4SI_UNS,
P8V_BUILTIN_ORC_V2DI_UNS, P8V_BUILTIN_ORC_V1TI_UNS>: Handle unsigned
builtins.
gcc/testsuite/
PR target/92923
* gcc.target/powerpc/pr92923-1.c: New test.
* gcc.target/powerpc/pr92923-2.c: Likewise.
Added:
trunk/gcc/testsuite/gcc.target/powerpc/pr92923-1.c
trunk/gcc/testsuite/gcc.target/powerpc/pr92923-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/rs6000/rs6000-builtin.def
trunk/gcc/config/rs6000/rs6000-call.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 20:31:33 2019
Return-Path: <gcc-bugs-return-664242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25098 invoked by alias); 30 Dec 2019 20: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 25048 invoked by uid 48); 30 Dec 2019 20:31:28 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92923] __builtin_vec_xor() causes subregs to be used when not using V4SImode vectors
Date: Mon, 30 Dec 2019 20:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to target_milestone
Message-ID: <bug-92923-4-xajy5OyJ9G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02312.txt.bz2
Content-length: 897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92923
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #4 from Peter Bergner <bergner at gcc dot gnu.org> ---
Fixed on trunk. This technically is also a bug on the release branches, but
given the size of the patch, I do not recommend backporting this to those
branches. A better solution is to not use the __builtin_vec_<OP> builtin at
all and instead use the C operator on the arguments (eg, use "a & b" rather
than "__builtin_vec_and (a, b)").
>From gcc-bugs-return-664243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 20:33:53 2019
Return-Path: <gcc-bugs-return-664243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43328 invoked by alias); 30 Dec 2019 20:33:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43283 invoked by uid 55); 30 Dec 2019 20:33:49 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/93066] libgomp/target.c:525:46: error: expected expression before ')' token
Date: Mon, 30 Dec 2019 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93066-4-5cJLz31nVu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93066-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93066-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02313.txt.bz2
Content-length: 665
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93066
--- Comment #5 from John David Anglin <danglin at gcc dot gnu.org> ---
Author: danglin
Date: Mon Dec 30 20:33:17 2019
New Revision: 279773
URL: https://gcc.gnu.org/viewcvs?rev=279773&root=gcc&view=rev
Log:
PR libgomp/93066
* inclhack.def (hpux_c99_inttypes3): Fix defines for INTPTR_MAX
and UINTPTR_MAX, and missing define for SIZE_MAX.
* fixincl.x: Regenerate.
* tests/base/inttypes.h: Update for above fix.
Modified:
trunk/fixincludes/ChangeLog
trunk/fixincludes/fixincl.x
trunk/fixincludes/inclhack.def
trunk/fixincludes/tests/base/inttypes.h
>From gcc-bugs-return-664244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 21:44:04 2019
Return-Path: <gcc-bugs-return-664244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120755 invoked by alias); 30 Dec 2019 21:44:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120719 invoked by uid 48); 30 Dec 2019 21:44:00 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93108] New: mmix generates invalid assembly on newlib (-fstack-protector-strong -ffunction-sections): internal error: fixup not contained within frag
Date: Mon, 30 Dec 2019 21:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02314.txt.bz2
Content-length: 1487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93108
Bug ID: 93108
Summary: mmix generates invalid assembly on newlib
(-fstack-protector-strong -ffunction-sections):
internal error: fixup not contained within frag
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: slyfox at inbox dot ru
Target Milestone: ---
Created attachment 47572
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47572&action=edit
bug.c
Attached example is a self-contained preprocessed version of
newlib-3.1.0/newlib/libc/stdio/vfprintf.c
The crash looks like that:
$ ./xgcc -B. -fstack-protector-strong -ffunction-sections -c bug.c -o bug.o
bug.c: Assembler messages:
bug.c:3419: Error: internal error: fixup not contained within frag
$ ./xgcc -B. -v
Reading specs from ./specs
COLLECT_GCC=./xgcc
COLLECT_LTO_WRAPPER=./lto-wrapper
Target: mmix
Configured with: ../gcc/configure --target=mmix
--prefix=/home/slyfox/dev/git/gcc-mmix/../gcc-mmix-installed
--with-sysroot=/usr/mmix --disable-bootstrap --enable-languages=c --disable-nls
--with-native-system-header-dir=/include CFLAGS=-O0 CXXFLAGS=-O0
Thread model: single
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.0 20191230 (experimental) (GCC)
>From gcc-bugs-return-664245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 22:00:54 2019
Return-Path: <gcc-bugs-return-664245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52723 invoked by alias); 30 Dec 2019 22:00: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 52642 invoked by uid 48); 30 Dec 2019 22:00:50 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93108] mmix generates invalid assembly on newlib (-fstack-protector-strong -ffunction-sections): internal error: fixup not contained within frag
Date: Mon, 30 Dec 2019 22:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93108-4-nYmb62H3i2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02315.txt.bz2
Content-length: 1196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93108
--- Comment #1 from Sergei Trofimovich <slyfox at inbox dot ru> ---
Created attachment 47573
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47573&action=edit
min-bug.c
The bug initially discovered on gcc-9.2.0. creduce managed to shrink it down to
min-bug.c.
On it the error and generated file look like:
$ ./xgcc -B. -fstack-protector-strong -c min-bug.c -o min-bug.o -save-temps
min-bug.c: Assembler messages:
min-bug.c:430: Error: internal error: fixup not contained within frag
$ nl -ha min-bug.s
426 BZ $0,L:4
427 SLU $0,$2,32
428 SR $0,$0,32
429 CMP $0,$0,0
430 BZ $0,L:4
431 GETA $2,LC:0
432 STOU $2,h
433 L:4 IS @
434 SUBU $0,$253,16
435 LDO $1,$0,0
436 LDO $0,__stack_chk_guard
437 CMP $0,$1,$0
438 BZ $0,L:28
439 PUSHJ $8,__stack_chk_fail
440 L:28 IS @
441 SET $0,$2
442 INCL $254,#190
443 LDO $253,$254,0
444 ADDU $254,$254,8
445 POP 1,0
446 .data ! mmixal:= 8H LOC 9B
>From gcc-bugs-return-664246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 22:10:10 2019
Return-Path: <gcc-bugs-return-664246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81019 invoked by alias); 30 Dec 2019 22:10: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 80941 invoked by uid 48); 30 Dec 2019 22:10:06 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93108] mmix generates invalid assembly on newlib (-fstack-protector-strong -ffunction-sections): internal error: fixup not contained within frag
Date: Mon, 30 Dec 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: c
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93108-4-1fmIXE6C2Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02316.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93108
--- Comment #2 from Sergei Trofimovich <slyfox at inbox dot ru> ---
Commenting out 'GETA $2,LC:0' makes assembler get past the error.
'LC:0' is defined in '.rodata'. If I change '.rodata' manually to '.text'
assembler can assemble ELF file from modified source.
I guess 'fixup not contained within frag' is an equivalent of 'relocation
points outside current ELF section'.
>From gcc-bugs-return-664247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 22:11:42 2019
Return-Path: <gcc-bugs-return-664247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83964 invoked by alias); 30 Dec 2019 22:11: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 83862 invoked by uid 48); 30 Dec 2019 22:11:35 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93059] char and char8_t does not talk with each other with memcpy. std::copy std::copy_n, std::fill, std::fill_n, std::uninitialized_copy std::uninitialized_copy_n, std::fill, std::uninitialized_fill_n fails to convert to memxxx functions
Date: Mon, 30 Dec 2019 22:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93059-4-kv7Csvz8ND@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93059-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02317.txt.bz2
Content-length: 565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93059
--- Comment #32 from fdlbxtqi <euloanty at live dot com> ---
(In reply to Bernd Edlinger from comment #31)
> Yes, you usually need to make a full bootstrap / make check twice
> which the same svn revision one with and one without your patch.
> You also should make sure that the test case actually is able to fail
> before your patch.
> You run "$(srcdir)/contrib/test_summary -t" each time and
> compare the output.
I am going to bootstrap a new GCC version on my friend's new machine installed
with CentOS
>From gcc-bugs-return-664248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 22:33:58 2019
Return-Path: <gcc-bugs-return-664248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120149 invoked by alias); 30 Dec 2019 22:33: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 120053 invoked by uid 48); 30 Dec 2019 22:33:53 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/93066] libgomp/target.c:525:46: error: expected expression before ')' token
Date: Mon, 30 Dec 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: libgomp
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93066-4-WzjTYqmIuq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93066-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93066-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02318.txt.bz2
Content-length: 444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93066
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from John David Anglin <danglin at gcc dot gnu.org> ---
Fixed on trunk.
>From gcc-bugs-return-664249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Dec 30 23:59:20 2019
Return-Path: <gcc-bugs-return-664249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16150 invoked by alias); 30 Dec 2019 23:59: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 16115 invoked by uid 48); 30 Dec 2019 23:59:16 -0000
From: "euloanty at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTMwOTVdIEJ1aWxkIExhdGVzdCBHQ0MgZmFpbCAuLi8uLi9n?= =?UTF-8?B?Y2MvZ2NjL2dpbXBsZS1mb2xkLmM6NDE0Njo4OiBlcnJvcjogZXhwZWN0ZWQg?= =?UTF-8?B?dW5xdWFsaWZpZWQtaWQgYmVmb3JlIOKAmHRocm93c+KAmQ==?Date: Mon, 30 Dec 2019 23:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: euloanty at live dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93095-4-BR5jc7hJVH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93095-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93095-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02319.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93095
fdlbxtqi <euloanty at live dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-664250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 31 00:42:20 2019
Return-Path: <gcc-bugs-return-664250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82800 invoked by alias); 31 Dec 2019 00:42: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 82749 invoked by uid 48); 31 Dec 2019 00:42:16 -0000
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93108] mmix generates invalid assembly on newlib (-fstack-protector-strong -ffunction-sections): internal error: fixup not contained within frag
Date: Tue, 31 Dec 2019 00:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hp at gcc dot gnu.org
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 cc resolution
Message-ID: <bug-93108-4-uRDFutvylS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93108-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02320.txt.bz2
Content-length: 946
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93108
Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC|hp at bitrange dot com |hp at gcc dot gnu.org
Resolution|--- |MOVED
--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Thanks for the report. This is a binutils bug; a bug in the assembler, so I'm
"resolving" this one the way such bugs are usually handled, when reported to
the wrong bug-tracker. Those are supposed to be reported to
https://sourceware.org/bugzilla/ so if you want, you can report it there
instead. I know of this one, though but thanks for the test-case; it's
probably shorter than the one I have (that doesn't use
-fstack-protector-strong).
>From gcc-bugs-return-664251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 31 00:56:21 2019
Return-Path: <gcc-bugs-return-664251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98142 invoked by alias); 31 Dec 2019 00:56: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 97387 invoked by uid 48); 31 Dec 2019 00:56:16 -0000
From: "keremkat+gcc at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/79412] [8/9/10 Regression] ICE in fold_convert_loc, at fold-const.c:2239
Date: Tue, 31 Dec 2019 00:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: keremkat+gcc at gmail 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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79412-4-v4M0tZdmiL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79412-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79412-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-12/txt/msg02321.txt.bz2
Content-length: 1682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79412
--- Comment #8 from Kerem Kat <keremkat+gcc at gmail dot com> ---
^ correction> not reproducible with 9.2.1, reproducible with gcc-10 trunk as:
$ gcc z1.c
79412-ice.c:6:5: error: conflicting types for ‘a’
6 | int a[] = {2};
| ^
79412-ice.c:1:5: note: previous declaration of ‘a’ was here
1 | int a;
| ^
79412-ice.c: In function ‘fn1’:
79412-ice.c:4:4: internal compiler error: in fold_convert_loc, at
fold-const.c:2435
4 | a++;
| ~^~
0x61908f fold_convert_loc(unsigned int, tree_node*, tree_node*)
../../gcc/gcc/fold-const.c:2435
0xb29b8e gimplify_self_mod_expr(tree_node**, gimple**, gimple**, bool,
tree_node*)
../../gcc/gcc/gimplify.c:3178
0xb2305f gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
../../gcc/gcc/gimplify.c:13496
0xb26e5a gimplify_stmt(tree_node**, gimple**)
../../gcc/gcc/gimplify.c:6814
0xb27c5e gimplify_bind_expr
../../gcc/gcc/gimplify.c:1424
0xb24569 gimplify_expr(tree_node**, gimple**, gimple**, bool (*)(tree_node*),
int)
../../gcc/gcc/gimplify.c:13767
0xb26e5a gimplify_stmt(tree_node**, gimple**)
../../gcc/gcc/gimplify.c:6814
0xb289de gimplify_body(tree_node*, bool)
../../gcc/gcc/gimplify.c:14814
0xb28dd7 gimplify_function_tree(tree_node*)
../../gcc/gcc/gimplify.c:14958
0x984337 cgraph_node::analyze()
../../gcc/gcc/cgraphunit.c:669
0x987266 analyze_functions
../../gcc/gcc/cgraphunit.c:1212
0x987eb6 symbol_table::finalize_compilation_unit()
../../gcc/gcc/cgraphunit.c:2958
>From gcc-bugs-return-664252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 31 03:42:54 2019
Return-Path: <gcc-bugs-return-664252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21460 invoked by alias); 31 Dec 2019 03:42:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21447 invoked by uid 89); 31 Dec 2019 03:42:53 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-26.9 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_0,GIT_PATCH_1,GIT_PATCH_2,GIT_PATCH_3,KAM_SHORT,SPF_HELO_PASS,SPF_PASS autolearn=ham version=3.3.1 spammy=HTo:U*rth, env, keys, HX-Spam-Relays-External:sk:mailout
X-HELO: mailout3.samsung.com
Received: from mailout3.samsung.com (HELO mailout3.samsung.com) (203.254.224.33) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 31 Dec 2019 03:42:51 +0000
Received: from epcas5p3.samsung.com (unknown [182.195.41.41]) by mailout3.samsung.com (KnoxPortal) with ESMTP id 20191231034247epoutp033e8ba7b871102ba47e51667c632e8995~lV8ltrNNg2512825128epoutp03h for <gcc-bugs@gcc.gnu.org>; Tue, 31 Dec 2019 03:42:47 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 mailout3.samsung.com 20191231034247epoutp033e8ba7b871102ba47e51667c632e8995~lV8ltrNNg2512825128epoutp03h
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=samsung.com; s=mail20170921; t\x1577763767; bh xJ6Y5GSao8IPFmk502i94jaAN8JtLgkrO/7bR/eAs=; h=From:To:Cc:Subject:Date:References:From; b=OGfc+bCn8q8FaFbrn8KM1EZh6SAYdFzuafa7DWb+QCGd2eCPMvhBecBJztH5d6Tbs 9JjVLw7aCeQ6qznry6sGu6y5ug+lHXP3/D6C1exK9CRPkX9YsfUW5W+OzmU9tPSxQT RkWadKzwpm7u9DCn0Bu3eYlnTr1Bqk6DM70L5W14Received: from epsmges5p3new.samsung.com (unknown [182.195.42.75]) by epcas5p1.samsung.com (KnoxPortal) with ESMTP id 20191231034246epcas5p1b5da4383583461f4d99b45e4f37bf35d~lV8lMa4nw1201112011epcas5p1f; Tue, 31 Dec 2019 03:42:46 +0000 (GMT)
Received: from epcas5p3.samsung.com ( [182.195.41.41]) by epsmges5p3new.samsung.com (Symantec Messaging Gateway) with SMTP id 48.D4.19629.6B3CA0E5; Tue, 31 Dec 2019 12:42:46 +0900 (KST)
Received: from epsmtrp1.samsung.com (unknown [182.195.40.13]) by epcas5p1.samsung.com (KnoxPortal) with ESMTPA id 20191230141205epcas5p10746a819f7b169270122c56bf3309e18~lK4wbw9ty2639926399epcas5p1H; Mon, 30 Dec 2019 14:12:05 +0000 (GMT)
Received: from epsmgms1p1new.samsung.com (unknown [182.195.42.41]) by epsmtrp1.samsung.com (KnoxPortal) with ESMTP id 20191230141205epsmtrp1495d20403c984546da852c33257025cc~lK4wbFRRY0626906269epsmtrp15; Mon, 30 Dec 2019 14:12:05 +0000 (GMT)
Received: from epsmtip2.samsung.com ( [182.195.34.31]) by epsmgms1p1new.samsung.com (Symantec Messaging Gateway) with SMTP id 75.A3.10238.5B50A0E5; Mon, 30 Dec 2019 23:12:05 +0900 (KST)
Received: from localhost.localdomain (unknown [107.108.92.210]) by epsmtip2.samsung.com (KnoxPortal) with ESMTPA id 20191230141203epsmtip2cbdb63147619bb88abe311dba1a5d19a~lK4uvNgey0969409694epsmtip2P; Mon, 30 Dec 2019 14:12:03 +0000 (GMT)
From: Ayush Mittal <ayush.m@samsung.com>
To: gcc-bugs@gcc.gnu.org, rth@redhat.com, jakub@gcc.gnu.org, jakub@redhat.com
Cc: avnish.jain@samsung.com, a.sahrawat@samsung.com, v.narang@samsung.com, maninder1.s@samsung.com, akhilesh.k@samsung.com, Ayush Mittal <ayush.m@samsung.com>
Subject: [v2] libgomp: Add destructor to delete runtime env keys
Date: Tue, 31 Dec 2019 03:42:00 -0000
Message-Id: <1577714048-1939-1-git-send-email-ayush.m@samsung.com>
X-CMS-MailID: 20191230141205epcas5p10746a819f7b169270122c56bf3309e18
X-Msg-Generator: CA
Content-Type: text/plain; charset="utf-8"
X-Sendblock-Type: REQ_APPROVE
CMS-TYPE: 105P
X-CMS-RootMailID: 20191230141205epcas5p10746a819f7b169270122c56bf3309e18
References: <CGME20191230141205epcas5p10746a819f7b169270122c56bf3309e18@epcas5p1.samsung.com>
X-SW-Source: 2019-12/txt/msg02322.txt.bz2
Content-length: 1822
[BUG: 93065] libgomp: destructor missing to delete goacc_cleanup_key
libgomp constructor creates goacc_cleanup_key on dlopen but doesn't delete key on dlclose.
dlopen and dlclose of libgomp.so exhausts pthread keys, which results in pthread_key_create failure.
pthread_key_delete needs to be called by libgomp destructor.
Signed-off-by: Vaneet Narang <v.narang@samsung.com>
Signed-off-by: Ayush Mittal <ayush.m@samsung.com>
---
[v1 patch] https://gcc.gnu.org/ml/gcc-bugs/2019-12/msg02132.html
[v1] -> [v2]
* Adding ChangeLog entry.
* Instead of adding a destructor function in one file and then calling goacc_runtime_deinitialize function in another file,
making goacc_runtime_deinitialize as desctrutor function.
* Making goacc_runtime_deinitialize as static function so no entry
needed in header file.
* Not removing extra form feed character alredy present.
ChangeLog | 4 ++++
libgomp/oacc-init.c | 9 +++++++++
2 files changed, 13 insertions(+)
diff --git a/ChangeLog b/ChangeLog
index f64cf381655..24778a27f9f 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,7 @@
+2019-12-30 Ayush Mittal <ayush.m@samsung.com>
+
+ * libgomp: Add destructor to delete runtime env keys
+
2019-12-20 Jerome Lambourg <lambourg@adacore.com>
* MAINTAINERS (write_after_approval): Add myself.
diff --git a/libgomp/oacc-init.c b/libgomp/oacc-init.c
index 487a2cca61f..6aa5fd297d6 100644
--- a/libgomp/oacc-init.c
+++ b/libgomp/oacc-init.c
@@ -858,6 +858,15 @@ goacc_runtime_initialize (void)
goacc_host_init ();
}
+static void __attribute__((destructor))
+goacc_runtime_deinitialize (void)
+{
+#if !(defined HAVE_TLS || defined USE_EMUTLS)
+ pthread_key_delete (goacc_tls_key);
+#endif
+ pthread_key_delete (goacc_cleanup_key);
+}
+
/* Compiler helper functions */
attribute_hidden void
--
2.17.1
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug tree-optimization/93084] [10 regression] Infinite loop in ipa-cp when building clang with LTO+PGO
[not found] <bug-93084-4@http.gcc.gnu.org/bugzilla/>
2019-12-30 11:02 ` [Bug tree-optimization/93084] [10 regression] Infinite loop in ipa-cp when building clang with LTO+PGO hubicka at ucw dot cz
@ 2020-01-02 10:16 ` hubicka at ucw dot cz
1 sibling, 0 replies; 2+ messages in thread
From: hubicka at ucw dot cz @ 2020-01-02 10:16 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93084
--- Comment #11 from Jan Hubicka <hubicka at ucw dot cz> ---
> xxx.localalias is gcc-generated as a noninterposable alias to xxx. But I guess
> target node returned by xxx.localalias->function_symbol() is not xxx. A simple
that ought to return xxx unless the target of localalias is thunk that
is not recursive.
> thing we can do is to write a simple case to force generation of .localalias
> and test that.
To do that you can probably write simple C++ self-recursive inline
function and compile with -fpic.
Honza
>From gcc-bugs-return-664355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:21:55 2020
Return-Path: <gcc-bugs-return-664355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64991 invoked by alias); 2 Jan 2020 10:21:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64927 invoked by uid 48); 2 Jan 2020 10:21:49 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] [8/9/10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Thu, 02 Jan 2020 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92860-4-3BxEdtkNNc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00081.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
@Richi:
About the param_max_fields_for_field_sensitive:
Do I understand it correctly that the param is used in IPA PTA for global
variables? If so, we can't easily use Optimization keyword as the param value
will not make sense to be different for different functions.
>From gcc-bugs-return-664356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:40:34 2020
Return-Path: <gcc-bugs-return-664356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96636 invoked by alias); 2 Jan 2020 10:40: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 96556 invoked by uid 48); 2 Jan 2020 10:40:24 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] New: ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == *
Date: Thu, 02 Jan 2020 10:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00082.txt.bz2
Content-length: 668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
Bug ID: 93131
Summary: ((a&8) == 8) && ((a&2) == 2) is not optimized to
(a&(8|2)) == *
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
int f(int a)
{
char b = (a&8) == 8;
char c = (a&2) == 2;
char d = (a&4) == 4;
return b&c&d;
}
int f1(int a)
{
return (a&(8|2|4)) == (8|2|4);
}
>From gcc-bugs-return-664357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:42:22 2020
Return-Path: <gcc-bugs-return-664357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98351 invoked by alias); 2 Jan 2020 10:42:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98319 invoked by uid 48); 2 Jan 2020 10:42:18 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: 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 short_desc everconfirmed
Message-ID: <bug-93131-4-sKgN1WaaOc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00083.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-02
Summary|((a&8) == 8) && ((a&2) == |((a&8) == 8) && ((a&2) ==
|2) is not optimized to |2) is not optimized to
|(a&(8|2)) == * |(a&(8|2)) == (8|2)
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I have this for GCC 11.
I noticed this while working on lowering bit-fields and seeing if we implement
an optimization from fold-const.c to later on.
>From gcc-bugs-return-664358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:51:02 2020
Return-Path: <gcc-bugs-return-664358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115689 invoked by alias); 2 Jan 2020 10:51:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115645 invoked by uid 48); 2 Jan 2020 10:50:57 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-XFOlv7NnLS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00084.txt.bz2
Content-length: 911
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Something like:
(for bitop (bit_and bit_ior)
cmp (eq ne)
(simplify
(bitop:c
(cmp (bit_and @0 INTEGER_CST@mask1) INTEGER_CST@CST1)
(cmp (bit_and @0 INTEGER_CST@mask2) INTEGER_CST@CST2))
(with
{
tree type1 = TREE_TYPE (@0);
wide_int mask1 = wi::to_wide (@mask1);
wide_int mask2 = wi::to_wide (@mask2);
tree mask = wide_int_to_tree (type1, mask1 | mask2);
}
(switch
(if (bitop == BIT_AND_EXPR
&& operand_equal_p (@mask1, @CST1, OEP_ONLY_CONST)
&& operand_equal_p (@mask1, @CST1, OEP_ONLY_CONST))
(cmp (bit_and @0 { mask; } ) { mask; } ))
(if (bitop == BIT_IOR_EXPR
&& integer_onep (@CST1)
&& integer_onep (@CST2))
(cmp (bit_and @0 { mask; } ) @CST1 )))))
>From gcc-bugs-return-664359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:55:39 2020
Return-Path: <gcc-bugs-return-664359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121729 invoked by alias); 2 Jan 2020 10:55: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 121692 invoked by uid 48); 2 Jan 2020 10:55:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93126] PPC altivec -Wunused-but-set-variable false positive
Date: Thu, 02 Jan 2020 10:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93126-4-EW4LojMJZp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93126-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93126-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00085.txt.bz2
Content-length: 805
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93126
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Can't reproduce with powerpc64-linux, though I see much more severe issue,
vec_promote just completely ignores the second argument and so if it e.g. has
side-effects, those are ignored. Consider vec_promote (a, bar ()) where int
bar (); isn't const or pure.
With C++ a and b are reported with -Wunused-but-set-parameter, which means
nothing in the end calls mark_exp_read on those (converts those from lvalues to
rvalues).
>From gcc-bugs-return-664360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:57:06 2020
Return-Path: <gcc-bugs-return-664360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123936 invoked by alias); 2 Jan 2020 10:57: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 123842 invoked by uid 48); 2 Jan 2020 10:57:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93125] ICE in insert_regs, at cse.c:1128
Date: Thu, 02 Jan 2020 10:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93125-4-smwEuS9zHX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93125-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93125-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00086.txt.bz2
Content-length: 469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93125
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Maybe dup of PR90275 ? I've given up on that one, needs somebody more familiar
with CSE.
>From gcc-bugs-return-664361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 10:57:17 2020
Return-Path: <gcc-bugs-return-664361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124681 invoked by alias); 2 Jan 2020 10:57:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124585 invoked by uid 48); 2 Jan 2020 10:57:13 -0000
From: "pexu@gcc-bugzilla.mail.kapsi.fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93132] New: bogus `attribute((access))' warning when size-index is specified
Date: Thu, 02 Jan 2020 10:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pexu@gcc-bugzilla.mail.kapsi.fi
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-93132-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00087.txt.bz2
Content-length: 1355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93132
Bug ID: 93132
Summary: bogus `attribute((access))' warning when size-index is
specified
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: pexu@gcc-bugzilla.mail.kapsi.fi
Target Milestone: ---
Created attachment 47580
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47580&action=edit
Use formatted attribute specifier `attrspec', not the input one
Hi.
`append_access_attrs' at `gcc/c-family/c-attribs.c' has a slight issue when it
tries to match the size-index parameter:
3973 if (n2 && strncmp (attrstr + n1 + 1, pos + n1, n2))
The problem is that `attrstr' is the input / human-readable attribute string
(e.g. `attribute((__read_only__, 1, 2))' and not the formatted one (denoted by
`attrspec', e.g. `r0\01'). The corresponding warning message has this typo,
too, and it uses `atoi (attrstr + n1 + 1)' while it should of course use
`attrspec'.
Attached a proposed patch. As a side note, it's possibly a bit misleading that
the values in the warning message are one less than the given inputs; Perhaps
`atoi()' values should be incremented by one.
>From gcc-bugs-return-664362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 11:21:20 2020
Return-Path: <gcc-bugs-return-664362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37153 invoked by alias); 2 Jan 2020 11:21:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37116 invoked by uid 48); 2 Jan 2020 11:21:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 11:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93131-4-lMD4yTT84s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00088.txt.bz2
Content-length: 986
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We are still in stage3, why not do it now?
I don't see the point in handling &/== and |/!= in the same simplification when
you do something completely different for those.
Why not e.g.
(simplify
(bit_and:c
(eq (bit_and @0 INTEGER_CST@1) @1)
(eq (bit_and @0 INTEGER_CST@2) @2))
(eq (bit_and @0 (bit_ior @1 @2)) (bit_ior @1 @2)))
and something with integer_onep@2 for the bit_ior/ne?
Also, why do you treat &/== and |/!= differently?
I mean, if ((x&7)==7)&((x&13)==13) can be optimized into (x&15)==15, why can't
you optimize ((x&7)!=7)|((x&13)!=13) into (x&15)!=15?
>From gcc-bugs-return-664363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 11:33:35 2020
Return-Path: <gcc-bugs-return-664363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46534 invoked by alias); 2 Jan 2020 11:33:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46470 invoked by uid 48); 2 Jan 2020 11:33:30 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 11: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: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-ESjloDOZRl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00089.txt.bz2
Content-length: 1147
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #3)
> We are still in stage3, why not do it now?
> I don't see the point in handling &/== and |/!= in the same simplification
> when you do something completely different for those.
> Why not e.g.
> (simplify
> (bit_and:c
> (eq (bit_and @0 INTEGER_CST@1) @1)
> (eq (bit_and @0 INTEGER_CST@2) @2))
> (eq (bit_and @0 (bit_ior @1 @2)) (bit_ior @1 @2)))
> and something with integer_onep@2 for the bit_ior/ne?
> Also, why do you treat &/== and |/!= differently?
> I mean, if ((x&7)==7)&((x&13)==13) can be optimized into (x&15)==15, why
> can't you optimize ((x&7)!=7)|((x&13)!=13) into (x&15)!=15?
integer_onep should have been integer_zerop :) I had a few typos anyways.
I have to think this through really; that is why not for stage3; also I am
working on other things at this point. This was a side part of the what was I
working on doing.
Also we change (x&7)==7 to (x&7)!=0 before hand which means we need to match
that also.
>From gcc-bugs-return-664364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 11:37:07 2020
Return-Path: <gcc-bugs-return-664364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60037 invoked by alias); 2 Jan 2020 11:37:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59982 invoked by uid 48); 2 Jan 2020 11:37:02 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 11:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-vs2TGTtzPv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00090.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So ((a&8) != 0 ) | ((a&2) != 0 ) is already handled by the generic "(x != 0 | y
!= 0) -> (x | typeof(x)(y)) != 0".
Anyways this is for tomorrow.
>From gcc-bugs-return-664365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 12:13:40 2020
Return-Path: <gcc-bugs-return-664365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68422 invoked by alias); 2 Jan 2020 12:13:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68342 invoked by uid 48); 2 Jan 2020 12:13:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93122] ICE in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1668
Date: Thu, 02 Jan 2020 12:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93122-4-iQxfPGtMzv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00091.txt.bz2
Content-length: 855
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93122
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47581
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47581&action=edit
gcc10-pr93122.patch
Untested fix. With additional -fno-asynchronous-unwind-tables, it doesn't ICE,
but just emit wrong-code, the stack clash protection code expects r12 to be r1
+ stack offset, but it is not initialized to anything at all.
The bug seems to be that add<mode>3 expander uses reg_or_add_cint_operand
predicate for the last operand and if that isn't satisfied, gen_add3_insn
simply doesn't emit anything. On top of that, I think we want to use
add_operand as before too, because otherwise gen_add3_insn can emit multiple
instructions and in that case we really need to describe the effect to
dwarf2frame.c properly.
>From gcc-bugs-return-664366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 12:31:10 2020
Return-Path: <gcc-bugs-return-664366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120604 invoked by alias); 2 Jan 2020 12:31:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120308 invoked by uid 48); 2 Jan 2020 12:31:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93123] Lacking basic optimization around __int128 bitwise operations against constants
Date: Thu, 02 Jan 2020 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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93123-4-kuOWfpg0bU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93123-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93123-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00092.txt.bz2
Content-length: 1124
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93123
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |segher at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Similarly on x86_64:
movq %rdi, %rax
movq %rsi, %rdx
andq $-16, %rax
The problem on the rs6000 side is that it has andti3 instruction that is split
quite late (post reload in split2) and that instruction enforces the immediate
into register, even if e.g. both halves of it are suitable constants for having
the immediate in it. E.g. the define_insn could be allowed some selected
immediates in one of the operands and told RA that either it needs to be forced
into a v register if the other registers are v too, or it can stay as immediate
otherwise and then be split + handle the splitting e.g. with the & -1 special
cases.
>From gcc-bugs-return-664367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 13:40:57 2020
Return-Path: <gcc-bugs-return-664367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119134 invoked by alias); 2 Jan 2020 13:40:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119086 invoked by uid 48); 2 Jan 2020 13:40:51 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93133] New: __builtin_isgreater emits trapping compare instruction
Date: Thu, 02 Jan 2020 13:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-93133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00093.txt.bz2
Content-length: 1011
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93133
Bug ID: 93133
Summary: __builtin_isgreater emits trapping compare instruction
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Target: aarch64-*-*
Compile the following test case for aarch64 with -O2:
#include <cfenv>
int f(float x, float y)
{
std::feclearexcept(FE_ALL_EXCEPT);
int r = -__builtin_isgreater(x, y);
if (std::fetestexcept(FE_ALL_EXCEPT) != 0)
__builtin_abort();
return r;
}
int main()
{
float x = 0.f;
return f(x / x, 1.f);
}
The __builtin_isgreater call is turned into a trapping fcmgt instruction. The
negation is necessary to trigger this issue. The same issue seems to exists for
all non-trapping compare functions.
>From gcc-bugs-return-664368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 14:04:31 2020
Return-Path: <gcc-bugs-return-664368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128382 invoked by alias); 2 Jan 2020 14:04:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128282 invoked by uid 55); 2 Jan 2020 14:04:25 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] [8/9/10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Thu, 02 Jan 2020 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92860-4-mb8xuiN1JX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00094.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
--- Comment #8 from Jan Hubicka <hubicka at ucw dot cz> ---
> @Richi:
>
> About the param_max_fields_for_field_sensitive:
> Do I understand it correctly that the param is used in IPA PTA for global
> variables? If so, we can't easily use Optimization keyword as the param value
> will not make sense to be different for different functions.
There is global var use_field_sensitive which IMO needs to go but
otherwise I think PTA should always analyze an assignment that is
withing some function. So it can always query the OPTIMIZATION node of
the function the statement lives in.
Honza
>From gcc-bugs-return-664369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 14:21:39 2020
Return-Path: <gcc-bugs-return-664369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30700 invoked by alias); 2 Jan 2020 14:21: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 30622 invoked by uid 48); 2 Jan 2020 14:21:34 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92994] [10 Regression] ICE on invalid in gfc_get_class_from_expr, at fortran/trans-expr.c:486
Date: Thu, 02 Jan 2020 14:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92994-4-eC24q2vAYh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00095.txt.bz2
Content-length: 1088
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92994
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Not crashing but giving an odd error message is the following (for 'g'):
program m
implicit none
print *, f(3)
print *, g(3)
contains
recursive integer function f(n)
integer, value :: n
if (n == 0) then
f = 1
else
f = n * f (n-1) ! Error: … name of a recursive function and so refers to
the result variable.
end if
end function f
recursive integer function f(n)
integer, value :: n
if (n == 0) then
f = 1
else
associate (x => f(n-1))
f = n * x ! Error: Operands of binary numeric operator ‘*’ at (1) are
INTEGER(4)/PROCEDURE
end associate
end if
end function f
end program m
>From gcc-bugs-return-664370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 14:39:45 2020
Return-Path: <gcc-bugs-return-664370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96925 invoked by alias); 2 Jan 2020 14:39:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96887 invoked by uid 48); 2 Jan 2020 14:39:40 -0000
From: "drfiemost at email dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93134] New: [graphite] ICE: Segmentation fault in ISL
Date: Thu, 02 Jan 2020 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: drfiemost at email dot it
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00096.txt.bz2
Content-length: 4060
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93134
Bug ID: 93134
Summary: [graphite] ICE: Segmentation fault in ISL
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: drfiemost at email dot it
Target Milestone: ---
Getting a crash with snapshots gcc-9-20191221/gcc-8-20191220 and isl-0.22 on
x86_64-linux compiling the following reduced code using "-O2 -floop-block"
flags:
typedef struct {
int a[128]
} b;
b c;
d, e, f, g;
h() {
int i;
for (; g < e; g++) {
i = 1;
for (; i < d; i++)
c.a[f + i * 16 + g] = c.a[6 + g];
}
}
root [ /mnt/devel/build/gcc/gcc-9-20191221/build ]# LANG=C gcc/cc1 -O2
-floop-block /usr/src/gcc_ice.c
/usr/src/gcc_ice.c:3:1: warning: no semicolon at end of struct or union
3 | } b;
| ^
/usr/src/gcc_ice.c:5:1: warning: data definition has no type or storage class
5 | d, e, f, g;
| ^
/usr/src/gcc_ice.c:5:1: warning: type defaults to 'int' in declaration of 'd'
[-Wimplicit-int]
/usr/src/gcc_ice.c:5:4: warning: type defaults to 'int' in declaration of 'e'
[-Wimplicit-int]
5 | d, e, f, g;
| ^
/usr/src/gcc_ice.c:5:7: warning: type defaults to 'int' in declaration of 'f'
[-Wimplicit-int]
5 | d, e, f, g;
| ^
/usr/src/gcc_ice.c:5:10: warning: type defaults to 'int' in declaration of 'g'
[-Wimplicit-int]
5 | d, e, f, g;
| ^
h
/usr/src/gcc_ice.c:6:1: warning: return type defaults to 'int' [-Wimplicit-int]
6 | h() {
| ^
Analyzing compilation unit
Performing interprocedural optimizations
<*free_lang_data> <visibility> <build_ssa_passes> <opt_local_passes>
<remove_symbols> <targetclone> <free-fnsummary>Streaming LTO
<whole-program> <profile_estimate> <icf> <devirt> <cp> <fnsummary> <inline>
<pure-const> <free-fnsummary> <static-var> <single-use> <comdats>Assembling
functions:
<materialize-all-clones> <simdclone> hduring GIMPLE pass: graphite
/usr/src/gcc_ice.c: In function 'h':
/usr/src/gcc_ice.c:6:1: internal compiler error: Segmentation fault
0x1128de4 crash_signal
../../gcc/toplev.c:326
0x7f9145e857bf ???
/mnt/devel/build/glibc/glibc-2.30/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x21433a8 isl_basic_map_underlying_set
../../isl/isl_map.c:5515
0x20ec8ea equalities_in_underlying_set
../../isl/isl_affine_hull.c:860
0x20ecae4 isl_basic_map_detect_equalities
../../isl/isl_affine_hull.c:919
0x20ecc9b isl_basic_set_detect_equalities
../../isl/isl_affine_hull.c:952
0x21611ff uset_gist
../../isl/isl_map_simplify.c:2702
0x2162008 isl_basic_map_gist
../../isl/isl_map_simplify.c:3176
0x21622d1 isl_map_gist_basic_map
../../isl/isl_map_simplify.c:3234
0x2162dca map_gist
../../isl/isl_map_simplify.c:3601
0x2139072 isl_map_align_params_map_map_and
../../isl/isl_map.c:1531
0x2162e20 isl_map_gist
../../isl/isl_map_simplify.c:3611
0x2162ffe isl_map_gist_domain
../../isl/isl_map_simplify.c:3661
0x21ed605 bin_add_pair
../../isl/isl_union_map.c:872
0x21ed88e gen_bin_entry
../../isl/isl_union_map.c:957
0x2125f7e isl_hash_table_foreach
../../isl/isl_hash.c:207
0x21ed985 gen_bin_op
../../isl/isl_union_map.c:982
0x21ee560 union_map_gist_domain
../../isl/isl_union_map.c:1390
0x21ee5aa isl_union_map_gist_domain
../../isl/isl_union_map.c:1403
0x1e77f5a optimize_isl
../../gcc/graphite-optimize-isl.c:128
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
The original non-reduced code crashes only on gcc 9 with the same backtrace and
not on gcc 8, can add the preprocessed source if required.
Maybe related to bug 90004
>From gcc-bugs-return-664371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 14:46:47 2020
Return-Path: <gcc-bugs-return-664371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114220 invoked by alias); 2 Jan 2020 14:46:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113960 invoked by uid 48); 2 Jan 2020 14:46:42 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68950] [fortran] gfc_format_decoder cannot handle %qE
Date: Thu, 02 Jan 2020 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: minor
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-68950-4-n12jcdpzWu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00097.txt.bz2
Content-length: 1230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68950
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |burnus at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #13 from Tobias Burnus <burnus at gcc dot gnu.org> ---
I believe this has been fixed properly by the patch for PR fortran/79886 in
r246203 by adding the following to gcc/fortran/error.c's gfc_format_decoder:
default:
- return false;
+ /* Fall through info the middle-end decoder, as e.g. stor-layout.c
+ etc. diagnostics can use the FE printer while the FE is still
+ active. */
+ return default_tree_printer (pp, text, spec, precision, wide,
+ set_locus, hash);
HENCE: Closed as FIXED.
@Tom: Sorry for now following up to your RFC patch of 2015 and two-follow-up
pings in 2016 and 2018. — I strongly believe the mentioned patch by Jakub fixes
the issue properly; if you disagree, feel free to reopen this PR.
>From gcc-bugs-return-664372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:04:16 2020
Return-Path: <gcc-bugs-return-664372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95482 invoked by alias); 2 Jan 2020 15:04:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95307 invoked by uid 48); 2 Jan 2020 15:04:10 -0000
From: "clyon at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93135] New: g++.dg/cpp0x/initlist118.C fails on aarch64
Date: Thu, 02 Jan 2020 15:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: clyon at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93135-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00098.txt.bz2
Content-length: 1374
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93135
Bug ID: 93135
Summary: g++.dg/cpp0x/initlist118.C fails on aarch64
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: clyon at gcc dot gnu.org
Target Milestone: ---
The test fails on aarch64:
g++.dg/cpp0x/initlist118.C -std=c++14 (internal compiler error)
g++.dg/cpp0x/initlist118.C -std=c++14 (test for excess errors)
g++.dg/cpp0x/initlist118.C -std=c++17 (internal compiler error)
g++.dg/cpp0x/initlist118.C -std=c++17 (test for excess errors)
g++.dg/cpp0x/initlist118.C -std=c++2a (internal compiler error)
g++.dg/cpp0x/initlist118.C -std=c++2a (test for excess errors)
The log says:
during RTL pass: reload
/gcc/testsuite/g++.dg/cpp0x/initlist118.C: In function 'array<__vector(4)
float,
4> transpose(array<__vector(4) float, 4>)':
/gcc/testsuite/g++.dg/cpp0x/initlist118.C:25:1: internal compiler error:
maximum
number of generated reload insns per insn achieved (90)
0xd7686f lra_constraints(bool)
/gcc/lra-constraints.c:4946
0xd5d834 lra(_IO_FILE*)
/gcc/lra.c:2437
0xd10209 do_reload
/gcc/ira.c:5526
0xd10209 execute
/gcc/ira.c:5712
>From gcc-bugs-return-664373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:09:22 2020
Return-Path: <gcc-bugs-return-664373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36748 invoked by alias); 2 Jan 2020 15:09: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 36677 invoked by uid 48); 2 Jan 2020 15:09:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93133] __builtin_isgreater emits trapping compare instruction
Date: Thu, 02 Jan 2020 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93133-4-8nhgTPVuEM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93133-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93133-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00099.txt.bz2
Content-length: 1623
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93133
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |ktkachov at gcc dot gnu.org,
| |rearnsha at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
This happens during combine. If whether the comparison raises exception or not
is distinguished on aarch64 with CCFPEmode vs. CCFPmode, then guess the problem
is when that distinction gets ignored (unless in fast-math mode) or when it
goes away completely.
So, either the
Trying 11 -> 12:
11: r102:SI=cc:CCFP>0
REG_DEAD cc:CCFP
12: r98:SI=-r102:SI
REG_DEAD r102:SI
Successfully matched this instruction:
(set (reg:SI 98)
(neg:SI (gt:SI (reg:CCFP 66 cc)
(const_int 0 [0]))))
transformation is wrong (at least I don't see the new insn doing something
different for CCFP vs. CCFPE modes), or the further one:
Trying 7 -> 12:
7: cc:CCFP=cmp(r103:SF,r104:SF)
REG_DEAD r104:SF
REG_DEAD r103:SF
12: r98:SI=-cc:CCFP>0
REG_DEAD cc:CCFP
Successfully matched this instruction:
(set (reg:SI 98)
(neg:SI (gt:SI (reg:SF 103)
(reg:SF 104))))
where the CCFP vs. CCFPE mode goes away completely and is signalling always? in
that case.
>From gcc-bugs-return-664374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:40:26 2020
Return-Path: <gcc-bugs-return-664374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24702 invoked by alias); 2 Jan 2020 15:40:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24650 invoked by uid 48); 2 Jan 2020 15:40:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93124] [10 Regression] ICE in df_install_refs at df-scan.c:2376
Date: Thu, 02 Jan 2020 15: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone short_desc
Message-ID: <bug-93124-4-SwvSJ784A5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93124-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93124-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00100.txt.bz2
Content-length: 1474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93124
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
Target Milestone|--- |10.0
Summary|ICE in df_install_refs at |[10 Regression] ICE in
|df-scan.c:2376 |df_install_refs at
| |df-scan.c:2376
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r276318.
Slightly tweaked testcase (e.g. no need for unsigned a[a];), still needs the
uninitialized b variable used in one of the variable length structures:
int x;
void fn2 ();
void fn3 ();
void fn4 ();
void fn5 ();
void fn6 ();
void
fn1 (void)
{
int n;
for (n = 0;; ++n) {
{
struct { char a[n]; } s;
fn2 (s);
}
struct { unsigned a[x]; } s;
int i, b;
for (i = 0; i < n; ++i)
;
fn2 (s);
{
struct { char a[n]; } s;
int i;
for (i = 0; i < n; ++i)
s.a[i] = i;
fn3 (s, s);
}
fn4 ();
{
struct { unsigned a[n]; } s;
fn5 (s);
}
{
struct { char a[b]; } s;
for (; i < n;)
s.a[i] = i;
fn6 (s);
}
}
}
>From gcc-bugs-return-664375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:41:28 2020
Return-Path: <gcc-bugs-return-664375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25974 invoked by alias); 2 Jan 2020 15:41: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 25919 invoked by uid 55); 2 Jan 2020 15:41:23 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68020] Issue with implied-shape array parameter of rank > 2
Date: Thu, 02 Jan 2020 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68020-4-0nY55p5rPY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00101.txt.bz2
Content-length: 792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68020
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Thu Jan 2 15:40:51 2020
New Revision: 279835
URL: https://gcc.gnu.org/viewcvs?rev=279835&root=gcc&view=rev
Log:
Fortran] PR68020 – Fix implied-shape handling for rank > 2
PR fortran/68020
* array.c (gfc_match_array_spec): Fix implied-type matching
for rank > 2.
PR fortran/68020
* gfortran.dg/implied_shape_4.f90: New.
* gfortran.dg/implied_shape_5.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/implied_shape_4.f90
trunk/gcc/testsuite/gfortran.dg/implied_shape_5.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:42:46 2020
Return-Path: <gcc-bugs-return-664376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27301 invoked by alias); 2 Jan 2020 15:42: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 27266 invoked by uid 48); 2 Jan 2020 15:42:41 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93136] New: [10 regression] gcc.dg/vmx/ops.c and several other test break after r279772
Date: Thu, 02 Jan 2020 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00102.txt.bz2
Content-length: 3878
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93136
Bug ID: 93136
Summary: [10 regression] gcc.dg/vmx/ops.c and several other
test break after r279772
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
This is the list for powerpc64 BE on a power 8.
> FAIL: gcc.dg/vmx/ops.c -O0 (test for excess errors)
> FAIL: gcc.dg/vmx/ops.c -O1 (test for excess errors)
> FAIL: gcc.dg/vmx/ops.c -O2 (test for excess errors)
> FAIL: gcc.dg/vmx/ops.c -O2 -flto -fno-use-linker-plugin -flto-partition=none (test for excess errors)
> FAIL: gcc.dg/vmx/ops.c -O2 -flto -fuse-linker-plugin -fno-fat-lto-objects (test for excess errors)
> FAIL: gcc.dg/vmx/ops.c -O3 -g (test for excess errors)
> FAIL: gcc.dg/vmx/ops.c -Os (test for excess errors)
> FAIL: gcc.target/powerpc/vsx-vector-6.p7.c scan-assembler-times xxland 13
> FAIL: gcc.target/powerpc/vsx-vector-6.p7.c scan-assembler-times xxlxor 2
> FAIL: gcc.target/powerpc/vsx-vector-6.p8.c scan-assembler-times \\mxvcmpeqdp\\.\\s 5
> FAIL: gcc.target/powerpc/vsx-vector-6.p8.c scan-assembler-times \\mxvcmpgtdp\\.\\s 6
> FAIL: gcc.target/powerpc/vsx-vector-6.p8.c scan-assembler-times xxland 13
> FAIL: gcc.target/powerpc/vsx-vector-6.p8.c scan-assembler-times xxlxor 2
> FAIL: gcc.target/powerpc/vsx-vector-6.p9.c scan-assembler-times xxland 13
The vsx-vector-6.xx test failures vary depending on BE versus LE but the ops.c
test fails everywhere.
Executing on host: /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O0 -maltivec
-mabi=altivec -std=gnu99 -mno-vsx -Wno-deprecated -S -o ops.s (timeout =
300)
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-test2/gcc/xgcc
-B/home/seurer/gcc/build/gcc-test2/gcc/
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O0 -maltivec -mabi=altivec
-std=gnu99 -mno-vsx -Wno-deprecated -S -o ops.s
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c: In function 'f19':
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c:1670:3: note: use
'-flax-vector-conversions' to permit conversions between vectors with differing
element types or numbers of subparts
In file included from
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c:3:
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c:1670:19: error:
incompatible types when assigning to type '__vector signed char' {aka
'__vector(16) signed char'} from type '__vector __bool char' {aka '__vector(16)
__bool char'}
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c:1673:19: error:
incompatible types when assigning to type '__vector signed char' {aka
'__vector(16) signed char'} from type '__vector __bool char' {aka '__vector(16)
__bool char'}
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c: In function 'f28':
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c:2390:19: error:
incompatible types when assigning to type '__vector unsigned char' {aka
'__vector(16) unsigned char'} from type '__vector __bool char' {aka
'__vector(16) __bool char'}
/home/seurer/gcc/gcc-test2/gcc/testsuite/gcc.dg/vmx/ops.c:2393:19: error:
incompatible types when assigning to type '__vector unsigned char' {aka
'__vector(16) unsigned char'} from type '__vector __bool char' {aka
'__vector(16) __bool char'}
compiler exited with status 1
>From gcc-bugs-return-664377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:46:16 2020
Return-Path: <gcc-bugs-return-664377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31750 invoked by alias); 2 Jan 2020 15:46:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31631 invoked by uid 48); 2 Jan 2020 15:46:10 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68020] Issue with implied-shape array parameter of rank > 2
Date: Thu, 02 Jan 2020 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-68020-4-tTIe4BoujQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00103.txt.bz2
Content-length: 663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68020
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |burnus at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Thanks for the bug report – and sorry for fixing it more than 4 years later.
See also: https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00024.html
Close as FIXED
>From gcc-bugs-return-664378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 15:57:24 2020
Return-Path: <gcc-bugs-return-664378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39842 invoked by alias); 2 Jan 2020 15:57: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 39801 invoked by uid 48); 2 Jan 2020 15:57:19 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93115] gcc fails to emit inline function on llvm-roc project: -O1 -fPIC -fdevirtualize -fdevirtualize-speculatively -fipa-cp -fipa-cp-clone -fvisibility-inlines-hidden
Date: Thu, 02 Jan 2020 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93115-4-BGPRjCdzEC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00104.txt.bz2
Content-length: 2008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93115
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
The problem here is that we produce ipa-cp clone to devirtualize v::av which
also lead to devirtualization of m::av, but we miss this optimization. After
inlining we remove m::av and while producing the ipa-cp clone we devirtualize
to it which elads to undefined reference.
I am testing the following:
Index: ipa.c
===================================================================
--- ipa.c (revision 279810)
+++ ipa.c (working copy)
@@ -187,6 +187,7 @@ walk_polymorphic_call_targets (hash_set<
for (i = 0; i < targets.length (); i++)
{
struct cgraph_node *n = targets[i];
+ bool added = false;
/* Do not bother to mark virtual methods in anonymous namespace;
either we will find use of virtual table defining it, or it is
@@ -212,11 +213,18 @@ walk_polymorphic_call_targets (hash_set<
&& symtab->state < IPA_SSA_AFTER_INLINING)
reachable->add (body);
reachable->add (n);
+ added = true;
}
/* Even after inlining we want to keep the possible targets in the
boundary, so late passes can still produce direct call even if
- the chance for inlining is lost. */
- enqueue_node (n, first, reachable);
+ the chance for inlining is lost.
+ Do not keep references to comdat groups - removing their
definition
+ first and adding references later is going to give undefined
+ reference errors. */
+ if (added || (!DECL_COMDAT (n->decl)
+ || DECL_EXTERNAL (n->decl)
+ || !TREE_PUBLIC (n->decl)))
+ enqueue_node (n, first, reachable);
}
}
>From gcc-bugs-return-664379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 16:08:36 2020
Return-Path: <gcc-bugs-return-664379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64879 invoked by alias); 2 Jan 2020 16:08:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64804 invoked by uid 48); 2 Jan 2020 16:08:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93106] [c++2a] Deleted move constructor is not selected when returning an automatic variable
Date: Thu, 02 Jan 2020 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93106-4-SfXSNKlnyV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00105.txt.bz2
Content-length: 1059
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93106
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
What you cite doesn't say anything that would make the testcase invalid.
The standard says that for an implicitly movable entity seen in return
statement shall first perform overload resolution for the copy constructor as
if it was an rvalue, which in this case fails because the move ctor is deleted.
And in that case, another overload resolution is performed, this time
considering the implicitly movable entity as lvalue, and that succeeds. So, if
copy-ellision wouldn't be performed, not_movable::not_movable(not_movable
const&) would be invoked, but in this case copy-ellision is invoked and thus it
is default constructed into the return value object in the caller.
>From gcc-bugs-return-664380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 16:13:45 2020
Return-Path: <gcc-bugs-return-664380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68969 invoked by alias); 2 Jan 2020 16:13: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 68910 invoked by uid 48); 2 Jan 2020 16:13:39 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93136] [10 regression] gcc.dg/vmx/ops.c and several other test break after r279772
Date: Thu, 02 Jan 2020 16:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-93136-4-UzamLL29Qs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00106.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93136
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-02
Assignee|unassigned at gcc dot gnu.org |bergner at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Peter Bergner <bergner at gcc dot gnu.org> ---
Mine. Strange, I did BE testing on POWER8 and didn't see these.
>From gcc-bugs-return-664381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 16:14:51 2020
Return-Path: <gcc-bugs-return-664381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70147 invoked by alias); 2 Jan 2020 16:14: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 70043 invoked by uid 48); 2 Jan 2020 16:14:45 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93136] [10 regression] gcc.dg/vmx/ops.c and several other test break after r279772
Date: Thu, 02 Jan 2020 16:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone
Message-ID: <bug-93136-4-s8zxS8Ut58@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00107.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93136
Peter Bergner <bergner at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |segher at gcc dot gnu.org,
| |wschmidt at gcc dot gnu.org
Target Milestone|--- |10.0
>From gcc-bugs-return-664382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 16:17:14 2020
Return-Path: <gcc-bugs-return-664382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75849 invoked by alias); 2 Jan 2020 16:17:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75791 invoked by uid 48); 2 Jan 2020 16:17:08 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/91579] tailr1 pass creates redundant phi nodes
Date: Thu, 02 Jan 2020 16:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91579-4-8kIjtFVUn6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91579-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91579-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00108.txt.bz2
Content-length: 1400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91579
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> ---
This has been fixed with the following, sorry about messing up the ChangeLog PR
reference:
Author: jamborm
Date: Fri Aug 30 08:08:42 2019
New Revision: 275062
URL: https://gcc.gnu.org/viewcvs?rev=275062&root=gcc&view=rev
Log:
[PR 91579] Avoid creating redundant PHI nodes in tail-call pass
2019-08-30 Martin Jambor <mjambor@suse.cz>
tree-optimization/91579
* tree-tailcall.c (tailr_arg_needs_copy): New variable.
(find_tail_calls): Allocate tailr_arg_needs_copy and set its bits as
appropriate.
(arg_needs_copy_p): Removed.
(eliminate_tail_call): Test tailr_arg_needs_copy instead of calling
arg_needs_copy_p.
(tree_optimize_tail_calls_1): Likewise. Free tailr_arg_needs_copy.
testsuite/
* gcc.dg/tree-ssa/pr91579.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr91579.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-tailcall.c
>From gcc-bugs-return-664383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 16:30:51 2020
Return-Path: <gcc-bugs-return-664383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102903 invoked by alias); 2 Jan 2020 16:30: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 101875 invoked by uid 48); 2 Jan 2020 16:30:37 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93115] gcc fails to emit inline function on llvm-roc project: -O1 -fPIC -fdevirtualize -fdevirtualize-speculatively -fipa-cp -fipa-cp-clone -fvisibility-inlines-hidden
Date: Thu, 02 Jan 2020 16:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93115-4-wefrKUOYYv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93115-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93115-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00109.txt.bz2
Content-length: 4027
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93115
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mjambor at suse dot cz
--- Comment #5 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
OK, the missed optimization follows from the following:
1) ipa-cp creates specialized node for o. It is called only once from fn3
p calls unspecialized o. I wonder why this happens since both calls in p and
fn3 leads to devirtualization.
2) inliner inlines k to o. This does not enable devirtualization because o is
not specialized.
3) at the end of inlining remove_unreachable_nodes removes the offiline copy of
m::av
4) we inline o to p enabling devirtualization but it is too late.
Adding inline keyword to p makes inliner to inline it early but we still miss
the devirutalization. So we have two issues
a) for some reason ipa-cp rules out reasonable specialization
I it is decided here:
Evaluating opportunities for void o(j&)/11.
- considering value &g for param #0 p1 (caller_count: 1)
good_cloning_opportunity_p (time: 1, size: 36, freq_sum: 1000) ->
evaluation: 27, threshold: 500
good_cloning_opportunity_p (time: 199, size: 120, freq_sum: 1000) ->
evaluation: 1658, threshold: 500
Creating a specialized node of void o(j&)/11.
the new node is o.constprop/37.
known ctx 0 is Outer type:struct j offset 0
- considering value &e.D.2397 for param #0 p1 (caller_count: 1)
good_cloning_opportunity_p (time: 1, size: 36, freq_sum: 202) ->
evaluation: 5, threshold: 500
good_cloning_opportunity_p (time: 103, size: 120, freq_sum: 202) ->
evaluation: 173, threshold: 500
I assume it is because freq_sum is 202 instead of 1000 because call is
conditional, but that is really way too strict... 20% is outcome of:
Predictions for bb 2
DS theory heuristics: 20.24%
combined heuristics: 20.24%
call heuristics of edge 2->3: 33.00%
early return (on trees) heuristics of edge 2->3: 34.00%
Predictions for bb 3
which seems reasonable.
b) we do not devirtualize after inlining. We combine context correctly:
Polymorphic call context combine: Speculative outer type:struct j (or a
derived type) at offset 0
With context: Outer type:struct m offset 0
Updated as: Outer type:struct m offset 0 Speculative
outer type:struct j (or a derived type) at offset 0
but I am not sure why it does not trigger devirt at this stage. We also do not
need to have speculative outer type when we know outer type precisely, but it
is cosmetic issue.
>From gcc-bugs-return-664384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 16:55:45 2020
Return-Path: <gcc-bugs-return-664384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10759 invoked by alias); 2 Jan 2020 16: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 10716 invoked by uid 48); 2 Jan 2020 16:55:40 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92929] OpenACC/OpenMP 'target' 'exit data'/'update' optimizations
Date: Thu, 02 Jan 2020 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92929-4-VJ6Ys1rt8L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92929-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92929-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00110.txt.bz2
Content-length: 1278
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92929
--- Comment #6 from jules at gcc dot gnu.org ---
Apologies for breakage. This part of the patch was originally from the og9
patch supporting Fortran polymorphic class pointers posted at
https://gcc.gnu.org/ml/gcc-patches/2019-07/msg00752.html. The rationale was as
follows:
[...] OpenACC "enter data" and "exit data" now have GOMP_MAP_POINTER and
GOMP_MAP_PSET mappings removed during gimplification. In some
circumstances, passing an array to a function/subroutine and then doing
an "enter data" on it could leave dangling references to the function's
stack, although the actual array data is defined outside the function.
In any case, the pointer/pointer-set mappings don't seem to be
necessary for OpenACC "enter data".
I observed the described problem with a large test program, and unfortunately
did not manage to come up with a minimised test case at the time. Someone more
familiar with Fortran might be able to do so more easily than me!
In terms of backwards compatibility, we can't do anything about the "parasitic
binding" to a function's expired stack frame as generated by an older version
of the compiler in this case, I don't think. That's most likely going to
manifest as an intermittent crash.
>From gcc-bugs-return-664386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:01:48 2020
Return-Path: <gcc-bugs-return-664386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17106 invoked by alias); 2 Jan 2020 17:01:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17035 invoked by uid 48); 2 Jan 2020 17:01:28 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93088] [10 Regression] Compile time hog on gcc/testsuite/gcc.target/i386/pr56348.c w/ -O3 -funroll-loops -fno-tree-dominator-opts -fno-tree-vrp
Date: Thu, 02 Jan 2020 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93088-4-99Nx4UeoMR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93088-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93088-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00112.txt.bz2
Content-length: 1598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93088
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The problem is that pend is uninitialized in the testcase and we end up with:
(insn 6 70 71 14 (set (reg/v:DI 90 [ pend ])
(reg/v:DI 89 [ p ])) "pr56348.c":29:5 66 {*movdi_internal}
(nil))
and
(insn 9 88 63 12 (set (reg/v:DI 89 [ p ])
(reg/v:DI 90 [ pend ])) "pr56348.c":28:3 66 {*movdi_internal}
(nil))
as the only setters of the two pseudos (reg:DI 89 and reg:DI 90) and on that
kind of thing find_single_def_src just loops forever, alternating between the
two.
Hangs since r277923, but I think has been latent since r146700 aka
https://gcc.gnu.org/ml/gcc-patches/2009-04/msg00246.html
Guess a fix could be either to add some counter and punt after following e.g.
128 single definition pseudos with REG_P SET_SRCs, or add a hash_set or bitmap
or whatever to record pseudos we've seen already and punt when we notice a
loop, or combine both ways, start with handling a few without a bitmap/hash_set
and only after certain amount keep track on what we've seen and punt when we
see something again.
Though, even with a hash_set/bitmap, having unbounded search might result in
bad compilation complexity, if we have many loops with similar pseudos that
require extremely deep searches.
>From gcc-bugs-return-664385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:01:06 2020
Return-Path: <gcc-bugs-return-664385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16139 invoked by alias); 2 Jan 2020 17:01:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15961 invoked by uid 48); 2 Jan 2020 17:00:59 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJnb21wLzkzMDMwXSBbT3BlbkFDQ10gbGliZ29tcC5vYWNjLWMt?= =?UTF-8?B?YysrLWNvbW1vbi9kZWVwLWNvcHktMTAuYyBGQUlMUyBvbiBBTURHQ04g4oCT?= =?UTF-8?B?IGludmFsaWQgJ2FzeW5jJyB1c2FnZT8=?Date: Thu, 02 Jan 2020 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93030-4-EEStHHVnw3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93030-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00111.txt.bz2
Content-length: 413
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93030
--- Comment #1 from jules at gcc dot gnu.org ---
Thanks for the report -- there's a fix for this on the og9 branch, but I'm not
sure if I've posted that upstream (the GCN worker-partitioning patches were
separated out from the deep-copy patches, so fixes around the intersection of
those two features are easy to overlook).
I'll dig that up and post it.
>From gcc-bugs-return-664387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:12:21 2020
Return-Path: <gcc-bugs-return-664387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36889 invoked by alias); 2 Jan 2020 17:12: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 36849 invoked by uid 48); 2 Jan 2020 17:12:16 -0000
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93110] [10 Regression] grub-2.04/grub-core/lib/division.c:28:1: internal compiler error: in extract_insn, at recog.c:2294
Date: Thu, 02 Jan 2020 17:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: raj.khem at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93110-4-GDNArx5b8k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93110-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00113.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93110
--- Comment #3 from Khem Raj <raj.khem at gmail dot com> ---
(In reply to Jakub Jelinek from comment #2)
> Created attachment 47579 [details]
> gcc10-pr93110.patch
>
> Untested fix.
Thanks, I tried it out and it fixes the syslinux and grub failures on x86_64
that I was observing, I will give it a try for whole ycoto distro build tonight
and see if it caused any other build regressions. But so far it looks okay
>From gcc-bugs-return-664388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:31:26 2020
Return-Path: <gcc-bugs-return-664388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66617 invoked by alias); 2 Jan 2020 17:31:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66494 invoked by uid 55); 2 Jan 2020 17:31:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90677] [9 Regression] gcc-9.1.0 fails to build __gcc_diag__ souce: error: 'cgraph_node' is not defined as a type
Date: Thu, 02 Jan 2020 17:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90677-4-nEaDMnWStA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00114.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90677
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 2 17:29:59 2020
New Revision: 279840
URL: https://gcc.gnu.org/viewcvs?rev=279840&root=gcc&view=rev
Log:
PR c/90677
* cp-objcp-common.c (identifier_global_tag): Return NULL_TREE if name
has not been found, rather than error_mark_node.
* c-c++-common/pr90677-2.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/pr90677-2.c
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-objcp-common.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:37:26 2020
Return-Path: <gcc-bugs-return-664389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124400 invoked by alias); 2 Jan 2020 17:37:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124259 invoked by uid 55); 2 Jan 2020 17:37:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90677] [9 Regression] gcc-9.1.0 fails to build __gcc_diag__ souce: error: 'cgraph_node' is not defined as a type
Date: Thu, 02 Jan 2020 17:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90677-4-Ubh1zViIVJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00115.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90677
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 2 17:36:50 2020
New Revision: 279841
URL: https://gcc.gnu.org/viewcvs?rev=279841&root=gcc&view=rev
Log:
PR c/90677
* cp-objcp-common.c (identifier_global_tag): Return NULL_TREE if name
has not been found, rather than error_mark_node.
* c-c++-common/pr90677-2.c: New test.
Added:
branches/gcc-9-branch/gcc/testsuite/c-c++-common/pr90677-2.c
Modified:
branches/gcc-9-branch/gcc/cp/ChangeLog
branches/gcc-9-branch/gcc/cp/cp-objcp-common.c
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:37:54 2020
Return-Path: <gcc-bugs-return-664390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128022 invoked by alias); 2 Jan 2020 17:37:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127964 invoked by uid 48); 2 Jan 2020 17:37:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/90677] [9 Regression] gcc-9.1.0 fails to build __gcc_diag__ souce: error: 'cgraph_node' is not defined as a type
Date: Thu, 02 Jan 2020 17:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.1.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: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-90677-4-S0FzauAFAz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90677-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00116.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90677
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9.3, 10.1 and later.
>From gcc-bugs-return-664391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 17:58:14 2020
Return-Path: <gcc-bugs-return-664391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82287 invoked by alias); 2 Jan 2020 17:58:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82245 invoked by uid 48); 2 Jan 2020 17:58:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93135] [10 Regression] g++.dg/cpp0x/initlist118.C fails on aarch64
Date: Thu, 02 Jan 2020 17:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone short_desc
Message-ID: <bug-93135-4-d6jbEU4znm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93135-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93135-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00117.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93135
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Target Milestone|--- |10.0
Summary|g++.dg/cpp0x/initlist118.C |[10 Regression]
|fails on aarch64 |g++.dg/cpp0x/initlist118.C
| |fails on aarch64
>From gcc-bugs-return-664392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 18:08:54 2020
Return-Path: <gcc-bugs-return-664392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96401 invoked by alias); 2 Jan 2020 18:08: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 90960 invoked by uid 48); 2 Jan 2020 18:08:48 -0000
From: "joel at airwebreathe dot org.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93005] Redundant NEON loads/stores from stack are not eliminated
Date: Thu, 02 Jan 2020 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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel at airwebreathe dot org.uk
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93005-4-qiOYonnCjv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00118.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93005
--- Comment #2 from Joel Holdsworth <joel at airwebreathe dot org.uk> ---
Are you saying that if the GIMPLE were defined for the intrinsics, then the
optimizer would eliminate them automatically? Or is there more to it?
>From gcc-bugs-return-664393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 20:20:02 2020
Return-Path: <gcc-bugs-return-664393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96685 invoked by alias); 2 Jan 2020 20:20: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 96583 invoked by uid 48); 2 Jan 2020 20:19:58 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65428] ICE on nest array constructor
Date: Thu, 02 Jan 2020 20:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-65428-4-c80bPV9etW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65428-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65428-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00119.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65428
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |tkoenig at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
>From gcc-bugs-return-664394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:03:03 2020
Return-Path: <gcc-bugs-return-664394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17410 invoked by alias); 2 Jan 2020 21:03: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 17297 invoked by uid 48); 2 Jan 2020 21:02:57 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 21:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-9w9Gr1QiAd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00120.txt.bz2
Content-length: 288
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note the generic version of this is:
((A & N) == CST1) & ((A & M) == CST2)
if (N&M)&CST1 == (N&M)&CST2, then
(A&(N|M)) == (CST1|CST2)
else
false
>From gcc-bugs-return-664395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:18:07 2020
Return-Path: <gcc-bugs-return-664395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19010 invoked by alias); 2 Jan 2020 21:18:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18900 invoked by uid 48); 2 Jan 2020 21:17:57 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 21:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-r5ErgsSSFL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00121.txt.bz2
Content-length: 1119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #6)
> Note the generic version of this is:
> ((A & N) == CST1) & ((A & M) == CST2)
>
> if (N&M)&CST1 == (N&M)&CST2, then
> (A&(N|M)) == (CST1|CST2)
> else
> false
And now for the !=/| case:
((A & N) != CST1) | ((A & M) != CST2)
if (N&M)&CST1 == (N&M)&CST2, then
(A&(N|M)) != (CST1|CST2)
else
true
so something like:
(for bitop (bit_and bit_ior)
cmp (eq ne)
(simplify
(bitop
(cmp (bit_and @0 INTEGER_CST@mask1) INTEGER_CST@CST1)
(cmp (bit_and @0 INTEGER_CST@mask2) INTEGER_CST@CST2))
(with
{
tree type1 = TREE_TYPE (@0);
wide_int mask = wi::to_wide(@mask1) | wi::to_wide(@mask2);
wide_int cst1 = wi::to_wide(@cst1);
wide_int cst2 = wi::to_wide(@cst2);
}
(if (wi::eq(mask & cst1,mask & cst2))
(cmp (bit_and @0 {wide_int_to_tree (type1, mask); } ) { wide_int_to_tree
(cst1|cst2, mask); } )
{ constant_boolean_node (cmp == EQ_EXPR, type); }))))
>From gcc-bugs-return-664396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:19:49 2020
Return-Path: <gcc-bugs-return-664396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21087 invoked by alias); 2 Jan 2020 21:19:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20308 invoked by uid 48); 2 Jan 2020 21:19:44 -0000
From: "sss@li-snyder.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93137] New: [10 regression] ICE in refs_may_alias_p_2
Date: Thu, 02 Jan 2020 21:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sss@li-snyder.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93137-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00122.txt.bz2
Content-length: 3250
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93137
Bug ID: 93137
Summary: [10 regression] ICE in refs_may_alias_p_2
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: sss@li-snyder.org
Target Milestone: ---
hi -
With this version of gcc10 (svn rev 279832):
gcc version 10.0.0 20200102 (experimental) (GCC)
this source gives an ICE when compiled with -O:
-- x.cc -----------------------------------------------------
#include <string>
void foo (const std::string& s)
{
struct GCCLibSuffix {
std::string LibSuffix;
bool Active;
}
Suffixes[] =
{
{"/gcc/" + s, true}
};
}
-------------------------------------------------------------
$ g++ -std=c++17 -O -c x.cc
during IPA pass: fnsummary
x.cc: In function ‘void foo(const string&)’:
x.cc:13:1: internal compiler error: Segmentation fault
13 | }
| ^
0xc1467f crash_signal
/home/sss/gcc/gcc/gcc/toplev.c:328
0xcdb7c4 refs_may_alias_p_2
/home/sss/gcc/gcc/gcc/tree-ssa-alias.c:2190
0xcdc736 refs_may_alias_p_1(ao_ref*, ao_ref*, bool)
/home/sss/gcc/gcc/gcc/tree-ssa-alias.c:2227
0xcdc736 stmt_may_clobber_ref_p_1(gimple*, ao_ref*, bool)
/home/sss/gcc/gcc/gcc/tree-ssa-alias.c:3001
0xcdcdc0 walk_aliased_vdefs_1
/home/sss/gcc/gcc/gcc/tree-ssa-alias.c:3656
0xcdcf0f walk_aliased_vdefs(ao_ref*, tree_node*, bool (*)(ao_ref*, tree_node*,
void*), void*, bitmap_head**, bool*, unsigned int)
/home/sss/gcc/gcc/gcc/tree-ssa-alias.c:3679
0xa4cda2 parm_ref_data_pass_through_p
/home/sss/gcc/gcc/gcc/ipa-prop.c:1052
0xa58c39 ipa_compute_jump_functions_for_edge
/home/sss/gcc/gcc/gcc/ipa-prop.c:2237
0xa59cca ipa_compute_jump_functions_for_bb
/home/sss/gcc/gcc/gcc/ipa-prop.c:2297
0xa59cca analysis_dom_walker::before_dom_children(basic_block_def*)
/home/sss/gcc/gcc/gcc/ipa-prop.c:2823
0x137e977 dom_walker::walk(basic_block_def*)
/home/sss/gcc/gcc/gcc/domwalk.c:309
0xa5495d ipa_analyze_node(cgraph_node*)
/home/sss/gcc/gcc/gcc/ipa-prop.c:2893
0xa3c4df inline_indirect_intraprocedural_analysis
/home/sss/gcc/gcc/gcc/ipa-fnsummary.c:4020
0xa3c4df inline_analyze_function(cgraph_node*)
/home/sss/gcc/gcc/gcc/ipa-fnsummary.c:4040
0xa3c653 ipa_fn_summary_generate
/home/sss/gcc/gcc/gcc/ipa-fnsummary.c:4084
0xb5848b execute_ipa_summary_passes(ipa_opt_pass_d*)
/home/sss/gcc/gcc/gcc/passes.c:2189
0x86564d ipa_passes
/home/sss/gcc/gcc/gcc/cgraphunit.c:2629
0x86564d symbol_table::compile()
/home/sss/gcc/gcc/gcc/cgraphunit.c:2739
0x86712c symbol_table::compile()
/home/sss/gcc/gcc/gcc/cgraphunit.c:2719
0x86712c symbol_table::finalize_compilation_unit()
/home/sss/gcc/gcc/gcc/cgraphunit.c:2986
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$
Compiles OK with gcc 9.2.1.
The source from which this was reduced also built ok with gcc trunk
10.0.0 20191202.
>From gcc-bugs-return-664397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:26:31 2020
Return-Path: <gcc-bugs-return-664397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30252 invoked by alias); 2 Jan 2020 21:26: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 30153 invoked by uid 48); 2 Jan 2020 21:26:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 21:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93131-4-8W1GdQ650f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00123.txt.bz2
Content-length: 1083
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #7)
> so something like:
> (for bitop (bit_and bit_ior)
> cmp (eq ne)
> (simplify
> (bitop
> (cmp (bit_and @0 INTEGER_CST@mask1) INTEGER_CST@CST1)
> (cmp (bit_and @0 INTEGER_CST@mask2) INTEGER_CST@CST2))
> (with
> {
> tree type1 = TREE_TYPE (@0);
> wide_int mask = wi::to_wide(@mask1) | wi::to_wide(@mask2);
> wide_int cst1 = wi::to_wide(@cst1);
> wide_int cst2 = wi::to_wide(@cst2);
Formatting, s/(/ (/g
> }
> (if (wi::eq(mask & cst1,mask & cst2))
Ditto, also add space before ,
> (cmp (bit_and @0 {wide_int_to_tree (type1, mask); } ) { wide_int_to_tree
And here add space before wide_int_to_tree.
> (cst1|cst2, mask); } )
And these arguments need to be (type1, cst1 | cst2), right?
The line is too long, so maybe put the second { wide_int... on another line
indented below (bit_and ?
> { constant_boolean_node (cmp == EQ_EXPR, type); }))))
>From gcc-bugs-return-664398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:30:55 2020
Return-Path: <gcc-bugs-return-664398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50851 invoked by alias); 2 Jan 2020 21:30: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 50539 invoked by uid 48); 2 Jan 2020 21:30:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 21:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-G2aHoyb65z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00124.txt.bz2
Content-length: 871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #9 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #8)
>
> Formatting, s/(/ (/g
>
> > }
> > (if (wi::eq(mask & cst1,mask & cst2))
>
> Ditto, also add space before ,
>
> > (cmp (bit_and @0 {wide_int_to_tree (type1, mask); } ) { wide_int_to_tree
>
> And here add space before wide_int_to_tree.
>
> > (cst1|cst2, mask); } )
>
> And these arguments need to be (type1, cst1 | cst2), right?
> The line is too long, so maybe put the second { wide_int... on another line
> indented below (bit_and ?
>
> > { constant_boolean_node (cmp == EQ_EXPR, type); }))))
I wrote that directly in the bug report :). Yes I Know the formating is wrong.
and looks like I messed up the arguments to the second wide_int_to_tree too
:).
>From gcc-bugs-return-664399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:43:01 2020
Return-Path: <gcc-bugs-return-664399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76727 invoked by alias); 2 Jan 2020 21:43: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 72000 invoked by uid 48); 2 Jan 2020 21:42:56 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93122] ICE in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1668
Date: Thu, 02 Jan 2020 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93122-4-akSuqtOLuj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00125.txt.bz2
Content-length: 1023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93122
--- Comment #2 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> Created attachment 47581 [details]
> gcc10-pr93122.patch
>
> Untested fix. With additional -fno-asynchronous-unwind-tables, it doesn't
> ICE, but just emit wrong-code, the stack clash protection code expects r12
> to be r1 + stack offset, but it is not initialized to anything at all.
> The bug seems to be that add<mode>3 expander uses reg_or_add_cint_operand
> predicate for the last operand and if that isn't satisfied, gen_add3_insn
> simply doesn't emit anything.
Yeah, gen_add3_insn needs to be fixed; it shouldn't silently generate bad code.
This may not be so easy though?
> On top of that, I think we want to use
> add_operand as before too, because otherwise gen_add3_insn can emit multiple
> instructions and in that case we really need to describe the effect to
> dwarf2frame.c properly.
Does that not happen automatically here?
>From gcc-bugs-return-664401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:47:40 2020
Return-Path: <gcc-bugs-return-664401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127727 invoked by alias); 2 Jan 2020 21: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 127676 invoked by uid 48); 2 Jan 2020 21:47:35 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Thu, 02 Jan 2020 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93131-4-i9HUNDw8Xv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00127.txt.bz2
Content-length: 1051
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Oh, and there is another case I'm worried about. While match.pd has the
/* X == C (or X & Z == Y | C) is impossible if ~nonzero(X) & C != 0. */
(for cmp (eq ne)
(simplify
(cmp:c (with_possible_nonzero_bits2 @0) (with_certain_nonzero_bits2 @1))
(if (wi::bit_and_not (wi::to_wide (@1), get_nonzero_bits (@0)) != 0)
{ constant_boolean_node (cmp == NE_EXPR, type); })))
optimization, not sure if we can rely on that one happening always before this
one, and if it doesn't, e.g.
((x & 6) == 5) & ((x & 15) == 13)
where the precondition ((6 & 15) & 5) == ((6 & 15) & 13) is true we would
incorrectly transform it into (x & 15) == 13, even when it should be false.
So, shouldn't the precondition be (N&M)&CST1 == (N&M)&CST2 && (CST1&~N) == 0 &&
(CST2&~M) == 0?
Especially when get_nonzero_bits will not really do anything until ccp or other
optimization determines those.
>From gcc-bugs-return-664400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 21:47:19 2020
Return-Path: <gcc-bugs-return-664400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126981 invoked by alias); 2 Jan 2020 21:47:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126948 invoked by uid 48); 2 Jan 2020 21:47:14 -0000
From: "sss@li-snyder.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93138] New: [10 regression] elaborated type specifier visibility check problem
Date: Thu, 02 Jan 2020 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sss@li-snyder.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93138-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00126.txt.bz2
Content-length: 1242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93138
Bug ID: 93138
Summary: [10 regression] elaborated type specifier visibility
check problem
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: sss@li-snyder.org
Target Milestone: ---
hi -
With this version of gcc10 (svn rev 279832):
gcc version 10.0.0 20200102 (experimental) (GCC)
This source does not compile:
-- x.cc -----------------------------------------------------
struct Foo
{
enum Kind { a };
private:
Kind Kind;
};
enum Foo::Kind foo();
-------------------------------------------------------------
$ g++ -std=c++17 -c x.cc
x.cc: In function ‘Foo::Kind foo()’:
x.cc:9:11: error: ‘Foo::Kind Foo::Kind’ is private within this context
9 | enum Foo::Kind foo();
| ^~~~
x.cc:6:8: note: declared private here
6 | Kind Kind;
| ^~~~
$
This does compile OK with gcc 9.2.1 and with clang 8.0.0
The source from which this was reduced also built ok with gcc trunk
10.0.0 20191202.
>From gcc-bugs-return-664402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 22:01:14 2020
Return-Path: <gcc-bugs-return-664402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19901 invoked by alias); 2 Jan 2020 22:01: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 19508 invoked by uid 48); 2 Jan 2020 22:00:44 -0000
From: "phdofthehouse at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93093] __builtin_source_location reports values for default arguments not aligned with the Standard
Date: Thu, 02 Jan 2020 22:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: phdofthehouse 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-93093-4-4PWaGg3nS6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93093-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93093-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00128.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93093
--- Comment #4 from JeanHeyd Meneide <phdofthehouse at gmail dot com> ---
I changed the library test cases, but maybe there needs to be something that
helps the library developers tag a constant evaluation function as something
that should be ran later / deferred. I don't have any good ideas, just
spitballing.
Either way, the new patch passes by not testing for some of the cases similar
to what's in the Standard passage in [support.srcloc]:
https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00036.html
>From gcc-bugs-return-664403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 22:13:44 2020
Return-Path: <gcc-bugs-return-664403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33765 invoked by alias); 2 Jan 2020 22:13:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33684 invoked by uid 48); 2 Jan 2020 22:13:39 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93122] ICE in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1668
Date: Thu, 02 Jan 2020 22:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93122-4-2WgCdFOtsZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00129.txt.bz2
Content-length: 217
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93122
--- Comment #3 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Alternatively, we should generate the patterns we have by name, not indirectly
like this.
>From gcc-bugs-return-664404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 22:17:46 2020
Return-Path: <gcc-bugs-return-664404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46207 invoked by alias); 2 Jan 2020 22:17:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46125 invoked by uid 48); 2 Jan 2020 22:17:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93120] gcc-9 complains fails to see that switch handles all enum values, and still complains ' "control reaches end of non-void function" when there is no return after the switch
Date: Thu, 02 Jan 2020 22:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93120-4-eKCE1jrK3D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93120-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93120-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00130.txt.bz2
Content-length: 248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93120
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Also this is not a valid bug report. https://gcc.gnu.org/bugs clearly says we
need you to provide the actual code, not a URL.
>From gcc-bugs-return-664405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 22:32:07 2020
Return-Path: <gcc-bugs-return-664405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74877 invoked by alias); 2 Jan 2020 22:32: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 74796 invoked by uid 48); 2 Jan 2020 22:32:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93121] std::bit_cast missing
Date: Thu, 02 Jan 2020 22:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93121-4-iqk6qJ2fKk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93121-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93121-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00131.txt.bz2
Content-length: 236
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93121
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Not really a bug - C++20 isn't final yet, and we don't claim full support for
the current draft (not even close).
>From gcc-bugs-return-664406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 23:54:28 2020
Return-Path: <gcc-bugs-return-664406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12210 invoked by alias); 2 Jan 2020 23:54:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12147 invoked by uid 48); 2 Jan 2020 23:54:24 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93139] New: new test case gfortran.dg/implied_shape_5.f90 fails
Date: Thu, 02 Jan 2020 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93139-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00132.txt.bz2
Content-length: 4163
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93139
Bug ID: 93139
Summary: new test case gfortran.dg/implied_shape_5.f90 fails
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libgfortran/
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O0 -pedantic-errors
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libgfortran/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libgfortran/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libgfortran/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libatomic/.libs
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libquadmath/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libquadmath/.libs
-L/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libquadmath/.libs
-lm -o ./implied_shape_5.exe
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90:10:31:
Error: Bad specification for deferred shape array at (1)
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90:15:38:
Error: Bad specification for assumed size array at (1)
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90:16:34:
Error: Bad specification for assumed size array at (1)
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90:21:50:
Error: Bad array specification for implied-shape array at (1)
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90:22:48:
Error: Bad array specification for implied-shape array at (1)
/home/seurer/gcc/gcc-test/gcc/testsuite/gfortran.dg/implied_shape_5.f90:9:38:
Error: Assumed size array at (1) must be a dummy argument
compiler exited with status 1
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for errors, line 9)
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for errors, line 10)
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for errors, line 15)
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for errors, line 16)
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for errors, line 21)
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for errors, line 22)
Executing on host:
/home/seurer/gcc/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libgfortran/
exceptions_enabled119839.c -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -S -o exceptions_enabled119839.s (timeout = 300)
spawn -ignore SIGHUP
/home/seurer/gcc/build/gcc-test/gcc/testsuite/gfortran/../../gfortran
-B/home/seurer/gcc/build/gcc-test/gcc/testsuite/gfortran/../../
-B/home/seurer/gcc/build/gcc-test/powerpc64-unknown-linux-gnu/./libgfortran/
exceptions_enabled119839.c -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-color=never
-fdiagnostics-urls=never -S -o exceptions_enabled119839.s
exceptions_enabled119839.c: In function 'foo':
exceptions_enabled119839.c:4:7: error: 'throw' undeclared (first use in this
function)
exceptions_enabled119839.c:4:7: note: each undeclared identifier is reported
only once for each function it appears in
exceptions_enabled119839.c:4:12: error: expected ';' before numeric constant
compiler exited with status 1
PASS: gfortran.dg/implied_shape_5.f90 -O0 (test for excess errors)
UNRESOLVED: gfortran.dg/implied_shape_5.f90 -O0 compilation failed to
produce executable
>From gcc-bugs-return-664407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 23:56:14 2020
Return-Path: <gcc-bugs-return-664407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14035 invoked by alias); 2 Jan 2020 23:56: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 13963 invoked by uid 48); 2 Jan 2020 23:56:09 -0000
From: "dominik.b.czarnota+bugzilla at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/55820] cpp: unterminated argument list invoking macro "BAR" for #include in macro
Date: Thu, 02 Jan 2020 23:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.b.czarnota+bugzilla 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-55820-4-KaJdYqhe7f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00133.txt.bz2
Content-length: 1208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55820
Dominik Czarnota <dominik.b.czarnota+bugzilla at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dominik.b.czarnota+bugzilla
| |@gmail.com
--- Comment #2 from Dominik Czarnota <dominik.b.czarnota+bugzilla at gmail dot com> ---
Six years later this is still unconfirmed :(.
>(In reply to Andrew Pinski from comment #1)
> yes this code is undefined at compile time. GCC used to reject #define in a
> macro usage but it was decided we will accept that. I can find the old bugs
> if needed.
Shall this be then changed to WONTFIX (or INVALID)? It would be nice if someone
provide some C standard reference if there is something regarding to this.
Just for reference, I stumbled across this when analysing a CTF challenge
solution (https://twitter.com/disconnect3d_pl/status/1212880292593229825) and
wanted to do:
#define TOSTR(a) #a
#define hxp TOSTR(
#include "flag"
);
where the `flag` file contained: `hxp{flag}` (without backticks).
>From gcc-bugs-return-664408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 02 23:59:12 2020
Return-Path: <gcc-bugs-return-664408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16387 invoked by alias); 2 Jan 2020 23:59:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16337 invoked by uid 55); 2 Jan 2020 23:59:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68020] Issue with implied-shape array parameter of rank > 2
Date: Thu, 02 Jan 2020 23: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: 5.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68020-4-zFixAdkU27@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68020-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68020-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00134.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68020
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 2 23:58:35 2020
New Revision: 279849
URL: https://gcc.gnu.org/viewcvs?rev=279849&root=gcc&view=rev
Log:
PR fortran/68020
* gfortran.dg/impled_shape_5.f90: Use dg-do compile rather than dg-do
run.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/implied_shape_5.f90
>From gcc-bugs-return-664409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 00:01:11 2020
Return-Path: <gcc-bugs-return-664409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18454 invoked by alias); 3 Jan 2020 00:00: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 17535 invoked by uid 48); 3 Jan 2020 00:00:02 -0000
From: "dominik.b.czarnota+bugzilla at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/55820] cpp: unterminated argument list invoking macro "BAR" for #include in macro
Date: Fri, 03 Jan 2020 00:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.b.czarnota+bugzilla 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-55820-4-lNKmy9Ro1P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00135.txt.bz2
Content-length: 270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55820
--- Comment #3 from Dominik Czarnota <dominik.b.czarnota+bugzilla at gmail dot com> ---
(In reply to Dominik Czarnota from comment #2)
> Six years later this is still unconfirmed :(.
Seven*. Oh those off by ones.
>From gcc-bugs-return-664410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 00:31:50 2020
Return-Path: <gcc-bugs-return-664410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67941 invoked by alias); 3 Jan 2020 00:31:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67885 invoked by uid 48); 3 Jan 2020 00:31:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93138] [10 regression] elaborated type specifier visibility check problem
Date: Fri, 03 Jan 2020 00:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-93138-4-VXPOctzsY4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00136.txt.bz2
Content-length: 617
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93138
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r279480.
>From gcc-bugs-return-664411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 01:16:47 2020
Return-Path: <gcc-bugs-return-664411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112876 invoked by alias); 3 Jan 2020 01:16:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112811 invoked by uid 48); 3 Jan 2020 01:16:41 -0000
From: "pengliren at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC
Date: Fri, 03 Jan 2020 01:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pengliren at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93119-4-gQ5yVT7Irt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00137.txt.bz2
Content-length: 2239
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119
--- Comment #1 from Peakulorain <pengliren at huawei dot com> ---
Here is my patch to fix this program.
diff -Nurp a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
--- a/gcc/config/aarch64/aarch64.md 2019-12-20 03:16:50.706754343 +0800
+++ b/gcc/config/aarch64/aarch64.md 2019-12-31 04:33:11.229005263 +0800
@@ -5288,20 +5288,41 @@
;; The TLS ABI specifically requires that the compiler does not schedule
;; instructions in the TLS stubs, in order to enable linker relaxation.
;; Therefore we treat the stubs as an atomic sequence.
-(define_expand "tlsgd_small_<mode>"
+(define_expand "tlsgd_small_si"
[(parallel [(set (match_operand 0 "register_operand" "")
(call (mem:DI (match_dup 2)) (const_int 1)))
- (unspec:DI [(match_operand:PTR 1 "aarch64_valid_symref" "")]
UNSPEC_GOTSMALLTLS)
+ (unspec:DI [(match_operand:SI 1 "aarch64_valid_symref" "")]
UNSPEC_GOTSMALLTLS)
(clobber (reg:DI LR_REGNUM))])]
""
{
operands[2] = aarch64_tls_get_addr ();
})
-(define_insn "*tlsgd_small_<mode>"
+(define_expand "tlsgd_small_di"
+ [(parallel [(set (match_operand 0 "register_operand" "")
+ (call (mem:DI (match_dup 2)) (const_int 1)))
+ (unspec:DI [(match_operand:DI 1 "aarch64_valid_symref" "")]
UNSPEC_GOTSMALLTLS)
+ (clobber (reg:DI LR_REGNUM))])]
+ ""
+{
+ operands[2] = aarch64_tls_get_addr ();
+})
+
+(define_insn "*tlsgd_small_si"
[(set (match_operand 0 "register_operand" "")
(call (mem:DI (match_operand:DI 2 "" "")) (const_int 1)))
- (unspec:DI [(match_operand:PTR 1 "aarch64_valid_symref" "S")]
UNSPEC_GOTSMALLTLS)
+ (unspec:DI [(match_operand:SI 1 "aarch64_valid_symref" "S")]
UNSPEC_GOTSMALLTLS)
+ (clobber (reg:DI LR_REGNUM))
+ ]
+ ""
+ "adrp\\tx0, %A1\;add\\tx0, x0, %L1\;bl\\t%2\;nop"
+ [(set_attr "type" "call")
+ (set_attr "length" "16")])
+
+(define_insn "*tlsgd_small_di"
+ [(set (match_operand 0 "register_operand" "")
+ (call (mem:DI (match_operand:DI 2 "" "")) (const_int 1)))
+ (unspec:DI [(match_operand:DI 1 "aarch64_valid_symref" "S")]
UNSPEC_GOTSMALLTLS)
(clobber (reg:DI LR_REGNUM))
]
""
>From gcc-bugs-return-664412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 01:23:07 2020
Return-Path: <gcc-bugs-return-664412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125278 invoked by alias); 3 Jan 2020 01:23:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125193 invoked by uid 48); 3 Jan 2020 01:23:02 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC
Date: Fri, 03 Jan 2020 01:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-93119-4-dNURh3r1Uy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00138.txt.bz2
Content-length: 1685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
Assignee|unassigned at gcc dot gnu.org |pinskia at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Simplier patch, change PTR to P instead. Mine then.
That is:
diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
index f114f85..dd10ec5 100644
--- a/gcc/config/aarch64/aarch64.md
+++ b/gcc/config/aarch64/aarch64.md
@@ -6725,7 +6725,7 @@
[(parallel [(set (match_operand 0 "register_operand")
(call (mem:DI (match_dup 2)) (const_int 1)))
(unspec:DI [(const_int 0)] UNSPEC_CALLEE_ABI)
- (unspec:DI [(match_operand:PTR 1 "aarch64_valid_symref")]
UNSPEC_GOTSMALLTLS)
+ (unspec:DI [(match_operand:P 1 "aarch64_valid_symref")]
UNSPEC_GOTSMALLTLS)
(clobber (reg:DI LR_REGNUM))])]
""
{
@@ -6736,7 +6736,7 @@
[(set (match_operand 0 "register_operand" "")
(call (mem:DI (match_operand:DI 2 "" "")) (const_int 1)))
(unspec:DI [(const_int 0)] UNSPEC_CALLEE_ABI)
- (unspec:DI [(match_operand:PTR 1 "aarch64_valid_symref" "S")]
UNSPEC_GOTSMALLTLS)
+ (unspec:DI [(match_operand:P 1 "aarch64_valid_symref" "S")]
UNSPEC_GOTSMALLTLS)
(clobber (reg:DI LR_REGNUM))
]
""
>From gcc-bugs-return-664413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 01:49:09 2020
Return-Path: <gcc-bugs-return-664413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40598 invoked by alias); 3 Jan 2020 01:48:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40317 invoked by uid 48); 3 Jan 2020 01:48:37 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Fri, 03 Jan 2020 01:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-aCkIb3scxv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00139.txt.bz2
Content-length: 1257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #10)
> Oh, and there is another case I'm worried about. While match.pd has the
> /* X == C (or X & Z == Y | C) is impossible if ~nonzero(X) & C != 0. */
> (for cmp (eq ne)
> (simplify
> (cmp:c (with_possible_nonzero_bits2 @0) (with_certain_nonzero_bits2 @1))
> (if (wi::bit_and_not (wi::to_wide (@1), get_nonzero_bits (@0)) != 0)
> { constant_boolean_node (cmp == NE_EXPR, type); })))
> optimization, not sure if we can rely on that one happening always before
> this one, and if it doesn't, e.g.
> ((x & 6) == 5) & ((x & 15) == 13)
> where the precondition ((6 & 15) & 5) == ((6 & 15) & 13) is true we would
> incorrectly transform it into (x & 15) == 13, even when it should be false.
> So, shouldn't the precondition be (N&M)&CST1 == (N&M)&CST2 && (CST1&~N) == 0
> && (CST2&~M) == 0?
> Especially when get_nonzero_bits will not really do anything until ccp or
> other optimization determines those.
Yes I agree. Let me add those conditions too. Especially when it comes to
generic version, rather than just the gimple version.
>From gcc-bugs-return-664414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 07:49:37 2020
Return-Path: <gcc-bugs-return-664414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116905 invoked by alias); 3 Jan 2020 07:49: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 116835 invoked by uid 48); 3 Jan 2020 07:49:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Fri, 03 Jan 2020 07:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93131-4-dZ9jsmWlzZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00140.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Otherwise it LGTM, so please post it this week, I'd really like to see it in
GCC 10.
>From gcc-bugs-return-664415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 07:59:50 2020
Return-Path: <gcc-bugs-return-664415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29999 invoked by alias); 3 Jan 2020 07:59: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 29875 invoked by uid 48); 3 Jan 2020 07:59:45 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93139] new test case gfortran.dg/implied_shape_5.f90 fails
Date: Fri, 03 Jan 2020 07:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93139-4-NIO96JtnNP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93139-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93139-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00141.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93139
--- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Sorry, I do not see any FAILs in your description – if you mean:
UNRESOLVED: gfortran.dg/implied_shape_5.f90 -O0 compilation failed to
produce executable
please state so. If this is the issue, it has been fixed by the commit r279849
– cf. https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00044.html
>From gcc-bugs-return-664416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 08:09:09 2020
Return-Path: <gcc-bugs-return-664416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44564 invoked by alias); 3 Jan 2020 08:09: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 44472 invoked by uid 55); 3 Jan 2020 08:09:03 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92994] [10 Regression] ICE on invalid in gfc_get_class_from_expr, at fortran/trans-expr.c:486
Date: Fri, 03 Jan 2020 08:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92994-4-ogXXYVrcWE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00142.txt.bz2
Content-length: 908
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92994
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Fri Jan 3 08:08:30 2020
New Revision: 279853
URL: https://gcc.gnu.org/viewcvs?rev=279853&root=gcc&view=rev
Log:
Fortran] PR 92994 – add more ASSOCIATE checks
PR fortran/92994
* primary.c (gfc_match_rvalue): Add some flavor checks
gfc_matching_procptr_assignment.
* resolve.c (resolve_assoc_var): Add more checks for invalid targets.
PR fortran/92994
* gfortran.dg/associate_50.f90: Update dg-error.
* gfortran.dg/associate_51.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/associate_51.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/primary.c
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/associate_50.f90
>From gcc-bugs-return-664417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 08:40:57 2020
Return-Path: <gcc-bugs-return-664417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125445 invoked by alias); 3 Jan 2020 08:40: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 125284 invoked by uid 48); 3 Jan 2020 08:40:52 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/93139] new test case gfortran.dg/implied_shape_5.f90 fails
Date: Fri, 03 Jan 2020 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93139-4-TYsA8NVduw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93139-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93139-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00143.txt.bz2
Content-length: 787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93139
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #1)
> UNRESOLVED: gfortran.dg/implied_shape_5.f90 -O0 compilation failed to
> produce executable
> fixed by the commit r279849
> cf. https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00044.html
Assuming that was the issue and it has been fixed by the commit, close as FIXED
– please re-open if there is still an issue.
>From gcc-bugs-return-664418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 09:06:00 2020
Return-Path: <gcc-bugs-return-664418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25481 invoked by alias); 3 Jan 2020 09:05:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25371 invoked by uid 48); 3 Jan 2020 09:05:55 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92994] [10 Regression] ICE on invalid in gfc_get_class_from_expr, at fortran/trans-expr.c:486
Date: Fri, 03 Jan 2020 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92994-4-Qun7aiyfAh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92994-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92994-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00144.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92994
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Should now be FIXED on the GCC 10 trunk.
Thanks for all the testcases!
>From gcc-bugs-return-664419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 09:10:50 2020
Return-Path: <gcc-bugs-return-664419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38636 invoked by alias); 3 Jan 2020 09:10: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 38572 invoked by uid 55); 3 Jan 2020 09:10:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93088] [10 Regression] Compile time hog on gcc/testsuite/gcc.target/i386/pr56348.c w/ -O3 -funroll-loops -fno-tree-dominator-opts -fno-tree-vrp
Date: Fri, 03 Jan 2020 09:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93088-4-cKQzCud5M9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93088-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93088-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00145.txt.bz2
Content-length: 659
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93088
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 3 09:10:13 2020
New Revision: 279854
URL: https://gcc.gnu.org/viewcvs?rev=279854&root=gcc&view=rev
Log:
PR rtl-optimization/93088
* loop-iv.c (find_single_def_src): Punt after looking through
128 reg copies for regs with single definitions. Move definitions
to first uses.
* gcc.target/i386/pr93088.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr93088.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/loop-iv.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 09:17:52 2020
Return-Path: <gcc-bugs-return-664420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58211 invoked by alias); 3 Jan 2020 09: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 58149 invoked by uid 48); 3 Jan 2020 09:17:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93088] [10 Regression] Compile time hog on gcc/testsuite/gcc.target/i386/pr56348.c w/ -O3 -funroll-loops -fno-tree-dominator-opts -fno-tree-vrp
Date: Fri, 03 Jan 2020 09:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-93088-4-6qpqsaZLRy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93088-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93088-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00146.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93088
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk, latent on branches.
>From gcc-bugs-return-664421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 09:31:06 2020
Return-Path: <gcc-bugs-return-664421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73142 invoked by alias); 3 Jan 2020 09:31:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72656 invoked by uid 48); 3 Jan 2020 09:31:00 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/89047] [OpenACC] ICE in mark_scope_block_unused, at tree-ssa-live.c:391
Date: Fri, 03 Jan 2020 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89047-4-SsOPNE2OCp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00147.txt.bz2
Content-length: 978
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89047
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to G. Steinmetz from comment #0)
> With option -fopenacc, down to at least version 5 :
> real function f()
> !$acc update device (f)
> end
This now compiles and the dump (-fdump-tree-omplower) looks fine:
.omp_data_arr.1.__result_p = &__result_f;
#pragma omp target oacc_update map(force_to:__result_f [len: 4])
Namely, the result variable "f" (internally: "__result_f") is used.
Close as FIXED – even without knowing which commit it did fix.
[I have not added it as test case, though one could argue, one should.]
>From gcc-bugs-return-664422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 09:52:44 2020
Return-Path: <gcc-bugs-return-664422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126355 invoked by alias); 3 Jan 2020 09:52:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126228 invoked by uid 48); 3 Jan 2020 09:52:39 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/72715] [OpenACC] ICE in gfc_trans_omp_do, at fortran/trans-openmp.c:3164
Date: Fri, 03 Jan 2020 09:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: openacc, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tschwinge at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-72715-4-7I6yxmViWX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-72715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-72715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00148.txt.bz2
Content-length: 1369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72715
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to anlauf from comment #6)
> Code is still rejected with current 10-trunk:
>
> 4 | do concurrent (i=1:3)
> | 1
> Error: !$ACC LOOP cannot be a DO CONCURRENT loop at (1)
In OpenMP up to 5.0 and TR8 (= draft 5.1), DO CONCURRENT is an unsupported
Fortran 2008 feature ("unspecified behaviour", cf. "1.7 Normative
References").
The reason is that DO CONCURRENT can become rather complex due to MASK etc.,
cf. PR 60127 comment 3 )
In OpenACC, 2.7 only supports Fortran 2003 (see "1.6. References"), which does
not have "do concurrent". And while OpenACC 3.0 does support Fortran 2008, it
also lists "DO CONCURRENT" as unspecified behaviour.
Since r239845 (gomp-4_0-branch) and r268875 (for GCC 9 trunk), the ICE is gone
and has been replaced by an error message.
I believe the current implementation in GCC is fine – and as the ICE has been
fixed, this PR can be closed as: FIXED.
>From gcc-bugs-return-664423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:06:30 2020
Return-Path: <gcc-bugs-return-664423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81781 invoked by alias); 3 Jan 2020 10:06:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81656 invoked by uid 48); 3 Jan 2020 10:06:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93138] [10 regression] elaborated type specifier visibility check problem
Date: Fri, 03 Jan 2020 10:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-93138-4-osXW4Ph94T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00149.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93138
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47582
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47582&action=edit
gcc10-pr93138.patch
Untested fix.
>From gcc-bugs-return-664424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:11:55 2020
Return-Path: <gcc-bugs-return-664424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90888 invoked by alias); 3 Jan 2020 10:11: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 90831 invoked by uid 55); 3 Jan 2020 10:11:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93110] [10 Regression] grub-2.04/grub-core/lib/division.c:28:1: internal compiler error: in extract_insn, at recog.c:2294
Date: Fri, 03 Jan 2020 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93110-4-qoWLpM94M1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93110-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00150.txt.bz2
Content-length: 709
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93110
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 3 10:11:17 2020
New Revision: 279855
URL: https://gcc.gnu.org/viewcvs?rev=279855&root=gcc&view=rev
Log:
PR target/93110
* config/i386/i386.md (abs<mode>2): Use expand_simple_binop instead of
emitting ASHIFTRT, XOR and MINUS by hand. Use gen_int_mode with QImode
instead of gen_int_shift_amount + convert_modes.
* gcc.dg/torture/pr93110.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr93110.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:13:49 2020
Return-Path: <gcc-bugs-return-664426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93958 invoked by alias); 3 Jan 2020 10:13: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 93915 invoked by uid 48); 3 Jan 2020 10:13:44 -0000
From: "fxue at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93084] [10 regression] Infinite loop in ipa-cp when building clang with LTO+PGO
Date: Fri, 03 Jan 2020 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fxue at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93084-4-0XTyUp6c0A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93084-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93084-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00152.txt.bz2
Content-length: 160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93084
--- Comment #12 from fxue at gcc dot gnu.org ---
Identified the cause, it's my bug, will give a fix soon.
>From gcc-bugs-return-664425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:13:08 2020
Return-Path: <gcc-bugs-return-664425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92939 invoked by alias); 3 Jan 2020 10:13: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 92873 invoked by uid 55); 3 Jan 2020 10:13:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93089] Force mprefer-vector-widthQ2 in 'e' simd clones
Date: Fri, 03 Jan 2020 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93089-4-tLA6wOXGUP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00151.txt.bz2
Content-length: 1332
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93089
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 3 10:12:31 2020
New Revision: 279856
URL: https://gcc.gnu.org/viewcvs?rev=279856&root=gcc&view=rev
Log:
PR target/93089
* config/i386/i386.opt (x_prefer_vector_width_type): Remove TargetSave
entry.
(mprefer-vector-width=): Add Save.
* config/i386/i386-options.c (ix86_target_string): Add PVW argument,
print
-mprefer-vector-width= if non-zero. Fix up -mfpmath= comment.
(ix86_debug_options, ix86_function_specific_print): Adjust
ix86_target_string callers.
(ix86_valid_target_attribute_inner_p): Handle prefer-vector-width=.
(ix86_valid_target_attribute_tree): Likewise.
* config/i386/i386-options.h (ix86_target_string): Add PVW argument.
* config/i386/i386-expand.c (ix86_expand_builtin): Adjust
ix86_target_string caller.
* gcc.target/i386/pr93089-1.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr93089-1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386-expand.c
trunk/gcc/config/i386/i386-options.c
trunk/gcc/config/i386/i386-options.h
trunk/gcc/config/i386/i386.opt
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:14:42 2020
Return-Path: <gcc-bugs-return-664427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95277 invoked by alias); 3 Jan 2020 10:14:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95236 invoked by uid 55); 3 Jan 2020 10:14:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93089] Force mprefer-vector-widthQ2 in 'e' simd clones
Date: Fri, 03 Jan 2020 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93089-4-G5crlZzGTj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00153.txt.bz2
Content-length: 851
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93089
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 3 10:14:03 2020
New Revision: 279857
URL: https://gcc.gnu.org/viewcvs?rev=279857&root=gcc&view=rev
Log:
PR target/93089
* config/i386/i386-options.c (ix86_simd_clone_adjust): If
TARGET_PREFER_AVX128, use prefer-vector-width=256 for 'c' and 'd'
simd clones. If TARGET_PREFER_AVX256, use prefer-vector-width=512
for 'e' simd clones.
* gcc.target/i386/pr93089-2.c: New test.
* gcc.target/i386/pr93089-3.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr93089-2.c
trunk/gcc/testsuite/gcc.target/i386/pr93089-3.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386-options.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:15:51 2020
Return-Path: <gcc-bugs-return-664428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96782 invoked by alias); 3 Jan 2020 10:15:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96523 invoked by uid 48); 3 Jan 2020 10:15:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93110] [10 Regression] grub-2.04/grub-core/lib/division.c:28:1: internal compiler error: in extract_insn, at recog.c:2294
Date: Fri, 03 Jan 2020 10:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93110-4-VnV0TM2o4J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93110-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93110-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00154.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93110
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-664429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:15:57 2020
Return-Path: <gcc-bugs-return-664429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97220 invoked by alias); 3 Jan 2020 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 96762 invoked by uid 48); 3 Jan 2020 10:15:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93089] Force mprefer-vector-widthQ2 in 'e' simd clones
Date: Fri, 03 Jan 2020 10:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93089-4-VsLOLiMGYU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00155.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93089
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-664430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:37:48 2020
Return-Path: <gcc-bugs-return-664430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9023 invoked by alias); 3 Jan 2020 10:37:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8940 invoked by uid 48); 3 Jan 2020 10:37:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/55820] cpp: unterminated argument list invoking macro "BAR" for #include in macro
Date: Fri, 03 Jan 2020 10:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-55820-4-JYOpESWyCP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00156.txt.bz2
Content-length: 803
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55820
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
See e.g. ISO C99, 6.10.3/11, last sentence:
"If there are sequences of preprocessing tokens within the list of arguments
that would otherwise act as preprocessing directives, the behavior is
undefined."
Similarly for C++, see e.g. http://eel.is/c++draft/cpp.replace#11
So, the compiler can do anything with it.
>From gcc-bugs-return-664431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:42:22 2020
Return-Path: <gcc-bugs-return-664431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13462 invoked by alias); 3 Jan 2020 10:42:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13407 invoked by uid 48); 3 Jan 2020 10:42:17 -0000
From: "gcc at lxlz dot space" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] New: Segfault in cc1plus on incorrect decltype among function args
Date: Fri, 03 Jan 2020 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc at lxlz dot space
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00157.txt.bz2
Content-length: 727
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
Bug ID: 93140
Summary: Segfault in cc1plus on incorrect decltype among
function args
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at lxlz dot space
Target Milestone: ---
Created attachment 47583
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47583&action=edit
mcve
Failure happens when variadic template function args used inside decltype.
Minimal example is in attachment. Failure happens whether function Bar declared
or not.
>From gcc-bugs-return-664432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:43:42 2020
Return-Path: <gcc-bugs-return-664432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17931 invoked by alias); 3 Jan 2020 10:43:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17882 invoked by uid 48); 3 Jan 2020 10:43:37 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC
Date: Fri, 03 Jan 2020 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93119-4-rME0j5RHNP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00158.txt.bz2
Content-length: 1403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119
--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> Simplier patch, change PTR to P instead. Mine then.
>
> That is:
> diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
> index f114f85..dd10ec5 100644
> --- a/gcc/config/aarch64/aarch64.md
> +++ b/gcc/config/aarch64/aarch64.md
> @@ -6725,7 +6725,7 @@
> [(parallel [(set (match_operand 0 "register_operand")
> (call (mem:DI (match_dup 2)) (const_int 1)))
> (unspec:DI [(const_int 0)] UNSPEC_CALLEE_ABI)
> - (unspec:DI [(match_operand:PTR 1 "aarch64_valid_symref")]
> UNSPEC_GOTSMALLTLS)
> + (unspec:DI [(match_operand:P 1 "aarch64_valid_symref")]
> UNSPEC_GOTSMALLTLS)
> (clobber (reg:DI LR_REGNUM))])]
> ""
> {
> @@ -6736,7 +6736,7 @@
> [(set (match_operand 0 "register_operand" "")
> (call (mem:DI (match_operand:DI 2 "" "")) (const_int 1)))
> (unspec:DI [(const_int 0)] UNSPEC_CALLEE_ABI)
> - (unspec:DI [(match_operand:PTR 1 "aarch64_valid_symref" "S")]
> UNSPEC_GOTSMALLTLS)
> + (unspec:DI [(match_operand:P 1 "aarch64_valid_symref" "S")]
> UNSPEC_GOTSMALLTLS)
> (clobber (reg:DI LR_REGNUM))
> ]
> ""
I don't think that's right either. These are supposed to be machine addresses,
not C pointers.
>From gcc-bugs-return-664433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:44:28 2020
Return-Path: <gcc-bugs-return-664433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18978 invoked by alias); 3 Jan 2020 10:44:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18877 invoked by uid 48); 3 Jan 2020 10:44:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93137] [10 regression] ICE in refs_may_alias_p_2
Date: Fri, 03 Jan 2020 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed target_milestone cf_known_to_fail
Message-ID: <bug-93137-4-qGxhHslAvd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93137-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93137-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00159.txt.bz2
Content-length: 890
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93137
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Known to work| |9.2.0
Keywords| |ice-on-valid-code
Last reconfirmed| |2020-01-03
CC| |jason at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
Target Milestone|--- |10.0
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r279576.
>From gcc-bugs-return-664434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:46:13 2020
Return-Path: <gcc-bugs-return-664434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40873 invoked by alias); 3 Jan 2020 10:46:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40815 invoked by uid 48); 3 Jan 2020 10:46:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93046] [10 Regression] ICE in cp_gimplify_init_expr
Date: Fri, 03 Jan 2020 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-93046-4-ZmPJbfi2ui@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00160.txt.bz2
Content-length: 801
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93046
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
CC| |jason at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-664435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:47:35 2020
Return-Path: <gcc-bugs-return-664435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42172 invoked by alias); 3 Jan 2020 10:47:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42140 invoked by uid 48); 3 Jan 2020 10:47:30 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] Segfault in cc1plus on incorrect decltype among function args
Date: Fri, 03 Jan 2020 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-93140-4-Oe3aPmaniE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00161.txt.bz2
Content-length: 592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2020-01-03
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Is the code snippet invalid, right?
>From gcc-bugs-return-664436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 10:54:50 2020
Return-Path: <gcc-bugs-return-664436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20925 invoked by alias); 3 Jan 2020 10:54:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20886 invoked by uid 48); 3 Jan 2020 10:54:45 -0000
From: "gcc at lxlz dot space" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] Segfault in cc1plus on incorrect decltype among function args
Date: Fri, 03 Jan 2020 10:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc at lxlz dot space
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93140-4-X5gxQmcjo0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00162.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
--- Comment #2 from Denis Sheremet <gcc at lxlz dot space> ---
(In reply to Martin Liška from comment #1)
> Is the code snippet invalid, right?
It was invalid on real-life example I caught, but it could be valid if `Bar`
function is defined and takes no arguments, like that:
int Bar(){return 42;}
At least this way it compiles on clang. gcc fails either way.
>From gcc-bugs-return-664437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 11:01:32 2020
Return-Path: <gcc-bugs-return-664437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33838 invoked by alias); 3 Jan 2020 11:01:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33778 invoked by uid 48); 3 Jan 2020 11:01:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93134] [graphite] ICE: Segmentation fault in ISL
Date: Fri, 03 Jan 2020 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-93134-4-RnlcFZHXxF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00163.txt.bz2
Content-length: 848
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93134
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
CC| |marxin at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed with current trunk and isl-0.22. Apparently, isl-0.20 is fine.
@Richi: Can you please take a look? There's updated isl:
https://build.opensuse.org/package/show/home:marxin:branches:devel:libraries:c_c++/isl
>From gcc-bugs-return-664438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 11:05:25 2020
Return-Path: <gcc-bugs-return-664438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38349 invoked by alias); 3 Jan 2020 11:05:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38282 invoked by uid 48); 3 Jan 2020 11:05:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/93122] ICE in dwarf2out_frame_debug_expr, at dwarf2cfi.c:1668
Date: Fri, 03 Jan 2020 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93122-4-3fceEU1yd8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93122-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00164.txt.bz2
Content-length: 2257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93122
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #2)
> (In reply to Jakub Jelinek from comment #1)
> > Created attachment 47581 [details]
> > gcc10-pr93122.patch
> >
> > Untested fix. With additional -fno-asynchronous-unwind-tables, it doesn't
> > ICE, but just emit wrong-code, the stack clash protection code expects r12
> > to be r1 + stack offset, but it is not initialized to anything at all.
> > The bug seems to be that add<mode>3 expander uses reg_or_add_cint_operand
> > predicate for the last operand and if that isn't satisfied, gen_add3_insn
> > simply doesn't emit anything.
>
> Yeah, gen_add3_insn needs to be fixed; it shouldn't silently generate bad
> code.
I don't think there is anything wrong on gen_add3_insn, like many other
expander functions e.g. for optabs that can FAIL (or in this particular case
also fail because of unmatched predicates) it signals to the caller a failure
through returning NULL and it is up to the caller to handle it.
So, rs6000-logue.c could also just gen_add3_insn and if it returns NULL, fall
back to what it emits in the else block.
> > On top of that, I think we want to use
> > add_operand as before too, because otherwise gen_add3_insn can emit multiple
> > instructions and in that case we really need to describe the effect to
> > dwarf2frame.c properly.
>
> Does that not happen automatically here?
No. First of all, the caller here marks just a single instruction with
RTX_FRAME_RELATED_P, so if gen_add3_insn emits e.g. two instructions, it will
mark the last instruction that way. That wouldn't be necessarily wrong, but in
that case dwarf2cfi.c needs to be able to understand what the instruction does
or it needs e.g. REG_FRAME_RELATED_EXPR note (or some other CFI note) that will
tell dwarf2cfi.c what the instruction does in a way that it can understand the
effects of that for unwind info.
So, either we do what the patch does, or e.g. without any predicates try to
gen_add3_insn, if it succeeds and returns more than one insn, force
REG_FRAME_RELATED_EXPR to the last insn, and if it returns NULL, do what we do
ATM in the else block.
>From gcc-bugs-return-664439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 11:14:14 2020
Return-Path: <gcc-bugs-return-664439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65522 invoked by alias); 3 Jan 2020 11:14: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 65464 invoked by uid 48); 3 Jan 2020 11:14:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] Segfault in cc1plus on incorrect decltype among function args
Date: Fri, 03 Jan 2020 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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 cc
Message-ID: <bug-93140-4-vj2xdtqkcE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00165.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|WAITING |NEW
CC| |jason at gcc dot gnu.org
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Good, then it's likely ICE on valid code.
Fails with at least GCC 4.8.0.
>From gcc-bugs-return-664440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 11:22:07 2020
Return-Path: <gcc-bugs-return-664440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109870 invoked by alias); 3 Jan 2020 11:22:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109780 invoked by uid 48); 3 Jan 2020 11:22:01 -0000
From: "TonyELewis at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92552] [10 Regression] internal compiler error: in lazily_declare_fn, at cp/method.c:3045 with -fconcepts
Date: Fri, 03 Jan 2020 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: TonyELewis at hotmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92552-4-mNE1e3NoOb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00166.txt.bz2
Content-length: 1090
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92552
Tony E Lewis <TonyELewis at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |TonyELewis at hotmail dot com
--- Comment #3 from Tony E Lewis <TonyELewis at hotmail dot com> ---
I've seen an ICE which looks likely to be a duplicate of this one. I'll put it
here so it can be retested when this one is fixed to confirm it's also fixed.
My ICE can be seen here: https://godbolt.org/z/R6MgH9
It involves compiling the following code with GCC trunk (20200102) with
`-std=c++2a` with range-v3 0.10.0.
#include <string>
#include <vector>
#include <range/v3/range/conversion.hpp>
#include <range/v3/view/join.hpp>
auto f() {
const std::vector<std::string> the_strings = { "a", "b" };
return the_strings
| ranges::views::join( "," )
| ranges::to<std::string>;
}
I can reduce this testcase if its ICE persists after the original ICE is fixed.
>From gcc-bugs-return-664441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 11:24:06 2020
Return-Path: <gcc-bugs-return-664441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114984 invoked by alias); 3 Jan 2020 11:24:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114820 invoked by uid 48); 3 Jan 2020 11:23:59 -0000
From: "TonyELewis at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92552] [10 Regression] internal compiler error: in lazily_declare_fn, at cp/method.c:3045 with -fconcepts
Date: Fri, 03 Jan 2020 11:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: TonyELewis at hotmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92552-4-mo8nUHotEr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00167.txt.bz2
Content-length: 4276
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92552
--- Comment #4 from Tony E Lewis <TonyELewis at hotmail dot com> ---
Sorry - forgot to include the compiler output...
In file included from
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/iterator/reverse_iterator.hpp:20,
from
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/range/access.hpp:31,
from
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/range/concepts.hpp:30,
from
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/action/concepts.hpp:23,
from
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/range/conversion.hpp:21,
from <source>:4:
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/iterator/basic_iterator.hpp:
In instantiation of 'struct
ranges::detail::iterator_associated_types_base_<ranges::join_with_view<ranges::ref_view<const
std::vector<std::__cxx11::basic_string<char> > >, ranges::ref_view<const char
[2]> >::cursor, true>':
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/iterator/basic_iterator.hpp:492:31:
required from 'struct
ranges::basic_iterator<ranges::join_with_view<ranges::ref_view<const
std::vector<std::__cxx11::basic_string<char> > >, ranges::ref_view<const char
[2]> >::cursor>'
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/range/access.hpp:75:13:
required from 'constexpr auto ranges::_begin_::fn::operator()(R&&) const
requires (_safe_range<R>) && ((has_member_begin<R>) ||
(has_non_member_begin<R>)) [with R =
ranges::join_with_view<ranges::ref_view<const
std::vector<std::__cxx11::basic_string<char> > >, ranges::ref_view<const char
[2]> >&]'
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/range/concepts.hpp:80:9:
required from 'ranges::detail::to_container::container_t<MetaFn, Rng>
ranges::detail::to_container::fn<MetaFn>::operator()(Rng&&) const requires
(input_range<Rng>) && (convertible_to_cont_cont<Rng, typename Pred::invoke>)
[with Rng = ranges::join_with_view<ranges::ref_view<const
std::vector<std::__cxx11::basic_string<char> > >, ranges::ref_view<const char
[2]> >; MetaFn = meta::id<std::__cxx11::basic_string<char> >;
ranges::detail::to_container::container_t<MetaFn, Rng> =
std::__cxx11::basic_string<char>]'
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/functional/invoke.hpp:134:34:
required by substitution of 'template<class F, class ... Args> constexpr
decltype ((F&&)(f)((Args&(ranges::invoke_fn::operator()::args))...))
ranges::invoke_fn::operator()(F&&, Args&& ...) const [with F =
ranges::detail::to_container::fn<meta::id<std::__cxx11::basic_string<char> > >;
Args = {ranges::join_with_view<ranges::ref_view<const
std::vector<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > > >, ranges::ref_view<const
char [2]> >}]'
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/functional/concepts.hpp:31:9:
required by substitution of 'template<class Rng, class MetaFn>
concepts::return_t<typename MetaFn::invoke<Rng>, typename
std::enable_if<(invocable<ranges::detail::to_container::fn<MetaFn>, Rng> &&
concepts::detail::CPP_true(concepts::detail::Nil{})), void>::type>
ranges::detail::operator|(Rng&&, ranges::detail::to_container::closure<MetaFn,
ranges::detail::to_container::fn<MetaFn> > (*)(ranges::detail::to_container))
[with Rng = ranges::join_with_view<ranges::ref_view<const
std::vector<std::__cxx11::basic_string<char> > >, ranges::ref_view<const char
[2]> >; MetaFn = meta::id<std::__cxx11::basic_string<char> >]'
<source>:11:19: required from here
/opt/compiler-explorer/libs/rangesv3/0.10.0/include/range/v3/iterator/basic_iterator.hpp:456:23:
internal compiler error: in lazily_declare_fn, at cp/method.c:3066
456 | Cur>::readable_iterator_associated_types_base;
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1
>From gcc-bugs-return-664442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 11:58:50 2020
Return-Path: <gcc-bugs-return-664442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2628 invoked by alias); 3 Jan 2020 11:58: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 130749 invoked by uid 48); 3 Jan 2020 11:58:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] [8/9/10 Regression] Segfault in cc1plus on incorrect decltype among function args
Date: Fri, 03 Jan 2020 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc target_milestone short_desc
Message-ID: <bug-93140-4-Twjii5dxXp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00168.txt.bz2
Content-length: 1037
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |8.4
Summary|Segfault in cc1plus on |[8/9/10 Regression]
|incorrect decltype among |Segfault in cc1plus on
|function args |incorrect decltype among
| |function args
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
int
bar ()
{
return 42;
}
template <typename... R>
void foo (R... r, decltype (bar (r...)) x = 0) {}
int
main ()
{
foo (3);
}
ICEs starting with r140120.
Note, clang emits there a mangled name that c++filt can't demangle:
_Z3fooIJEEvDpT_DTcl3barspfL0p_EE
which llvm-cxxfilt demangles as void foo<>(decltype(bar(fp...)))
>From gcc-bugs-return-664443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:03:11 2020
Return-Path: <gcc-bugs-return-664443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13435 invoked by alias); 3 Jan 2020 12:03: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 13354 invoked by uid 48); 3 Jan 2020 12:03:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93140] [8/9/10 Regression] Segfault in cc1plus on incorrect decltype among function args
Date: Fri, 03 Jan 2020 12:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-93140-4-vzGOH97koZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00169.txt.bz2
Content-length: 7572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93140
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems mutual infinite recursion:
...
#101 0x0000000000b83f51 in tsubst_decl (t=<parm_decl 0x7fffea81d180 x>,
args=<tree_vec 0x7fffea94e7a0>, complain=0) at ../../gcc/cp/pt.c:14083
#102 0x0000000000b87bc3 in tsubst (t=<parm_decl 0x7fffea81d180 x>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:14930
#103 0x0000000000b83d4b in tsubst_decl (t=<parm_decl 0x7fffea81d100 r>,
args=<tree_vec 0x7fffea94e7a0>, complain=0) at ../../gcc/cp/pt.c:14048
#104 0x0000000000b7a102 in tsubst_pack_expansion (t=<expr_pack_expansion
0x7fffea9603f0>, args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:12749
#105 0x0000000000ba05e8 in tsubst_copy_and_build (t=<call_expr 0x7fffea800118>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>, function_p=false,
integral_constant_expression_p=false) at ../../gcc/cp/pt.c:19438
#106 0x0000000000b8b312 in tsubst (t=<decltype_type 0x7fffea966000>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:15688
#107 0x0000000000b83f51 in tsubst_decl (t=<parm_decl 0x7fffea81d180 x>,
args=<tree_vec 0x7fffea94e7a0>, complain=0) at ../../gcc/cp/pt.c:14083
#108 0x0000000000b87bc3 in tsubst (t=<parm_decl 0x7fffea81d180 x>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:14930
#109 0x0000000000b83d4b in tsubst_decl (t=<parm_decl 0x7fffea81d100 r>,
args=<tree_vec 0x7fffea94e7a0>, complain=0) at ../../gcc/cp/pt.c:14048
#110 0x0000000000b7a102 in tsubst_pack_expansion (t=<expr_pack_expansion
0x7fffea9603f0>, args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:12749
#111 0x0000000000ba05e8 in tsubst_copy_and_build (t=<call_expr 0x7fffea800118>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>, function_p=false,
integral_constant_expression_p=false) at ../../gcc/cp/pt.c:19438
#112 0x0000000000b8b312 in tsubst (t=<decltype_type 0x7fffea966000>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:15688
#113 0x0000000000b83f51 in tsubst_decl (t=<parm_decl 0x7fffea81d180 x>,
args=<tree_vec 0x7fffea94e7a0>, complain=0) at ../../gcc/cp/pt.c:14083
#114 0x0000000000b87bc3 in tsubst (t=<parm_decl 0x7fffea81d180 x>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<parm_decl 0x7fffea81d180 x>) at ../../gcc/cp/pt.c:14930
#115 0x0000000000b83d4b in tsubst_decl (t=<parm_decl 0x7fffea81d100 r>,
args=<tree_vec 0x7fffea94e7a0>, complain=0) at ../../gcc/cp/pt.c:14048
#116 0x0000000000b7a102 in tsubst_pack_expansion (t=<expr_pack_expansion
0x7fffea9603f0>, args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>) at ../../gcc/cp/pt.c:12749
#117 0x0000000000ba05e8 in tsubst_copy_and_build (t=<call_expr 0x7fffea800118>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>, function_p=false,
integral_constant_expression_p=false) at ../../gcc/cp/pt.c:19438
#118 0x0000000000b8b312 in tsubst (t=<decltype_type 0x7fffea966000>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>) at ../../gcc/cp/pt.c:15688
#119 0x0000000000b86bdb in tsubst_arg_types (arg_types=<tree_list
0x7fffea965190>, args=<tree_vec 0x7fffea94e7a0>, end=<tree 0x0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>) at ../../gcc/cp/pt.c:14600
#120 0x0000000000b86a43 in tsubst_arg_types (arg_types=<tree_list
0x7fffea965168>, args=<tree_vec 0x7fffea94e7a0>, end=<tree 0x0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>) at ../../gcc/cp/pt.c:14569
#121 0x0000000000b871fa in tsubst_function_type (t=<function_type
0x7fffea9660a8>, args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>) at ../../gcc/cp/pt.c:14742
#122 0x0000000000b8a4e2 in tsubst (t=<function_type 0x7fffea9660a8>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<function_decl 0x7fffea951f00 foo>) at ../../gcc/cp/pt.c:15495
#123 0x0000000000b7eb2d in tsubst_function_decl (t=<function_decl
0x7fffea951f00 foo>, args=<tree_vec 0x7fffea94e7a0>, complain=0,
lambda_fntype=<tree 0x0>) at ../../gcc/cp/pt.c:13575
#124 0x0000000000b83afd in tsubst_decl (t=<function_decl 0x7fffea951f00 foo>,
args=<tree_vec 0x7fffea94e7a0>, complain=0)
at ../../gcc/cp/pt.c:14013
#125 0x0000000000b87bc3 in tsubst (t=<function_decl 0x7fffea951f00 foo>,
args=<tree_vec 0x7fffea94e7a0>, complain=0,
in_decl=<template_decl 0x7fffea81d200 foo>) at ../../gcc/cp/pt.c:14930
#126 0x0000000000ba61d7 in instantiate_template_1 (tmpl=<template_decl
0x7fffea81d200 foo>, orig_args=<tree_vec 0x7fffea94e7a0>, complain=0)
at ../../gcc/cp/pt.c:20468
#127 0x0000000000ba68aa in instantiate_template (tmpl=<template_decl
0x7fffea81d200 foo>, orig_args=<tree_vec 0x7fffea94e7a0>, complain=0)
at ../../gcc/cp/pt.c:20525
#128 0x0000000000ba7f71 in fn_type_unification (fn=<template_decl
0x7fffea81d200 foo>, explicit_targs=<tree 0x0>,
targs=<tree_vec 0x7fffea94e7a0>, args=0x7fffffffbc00, nargs=1,
return_type=<tree 0x0>, strict=DEDUCE_CALL, flags=1, convs=0x3595320,
explain_p=false, decltype_p=false) at ../../gcc/cp/pt.c:20969
#129 0x00000000008e9a4d in add_template_candidate_real
(candidates=0x7fffffffbf30, tmpl=<template_decl 0x7fffea81d200 foo>,
ctype=<tree 0x0>,
explicit_targs=<tree 0x0>, first_arg=<tree 0x0>, arglist=0x7fffea965078,
return_type=<tree 0x0>, access_path=<tree 0x0>,
conversion_path=<tree 0x0>, flags=1, obj=<tree 0x0>, strict=DEDUCE_CALL,
complain=3) at ../../gcc/cp/call.c:3394
#130 0x00000000008e9fc0 in add_template_candidate (candidates=0x7fffffffbf30,
tmpl=<template_decl 0x7fffea81d200 foo>, ctype=<tree 0x0>,
explicit_targs=<tree 0x0>, first_arg=<tree 0x0>, arglist=0x7fffea965078,
return_type=<tree 0x0>, access_path=<tree 0x0>,
conversion_path=<tree 0x0>, flags=1, strict=DEDUCE_CALL, complain=3) at
../../gcc/cp/call.c:3479
#131 0x00000000008f27a1 in add_candidates (fns=<overload 0x7fffea94e720>,
first_arg=<tree 0x0>, args=0x7fffea965078, return_type=<tree 0x0>,
explicit_targs=<tree 0x0>, template_only=false, conversion_path=<tree 0x0>,
access_path=<tree 0x0>, flags=1, candidates=0x7fffffffbf30,
complain=3) at ../../gcc/cp/call.c:5805
#132 0x00000000008ed261 in perform_overload_resolution (fn=<overload
0x7fffea94e720>, args=0x7fffea965078, candidates=0x7fffffffbf30,
any_viable_p=0x7fffffffbf2f, complain=3) at ../../gcc/cp/call.c:4481
#133 0x00000000008ed4d8 in build_new_function_call (fn=<overload
0x7fffea94e720>, args=0x7fffffffc0d0 = {...}, complain=3)
at ../../gcc/cp/call.c:4555
#134 0x0000000000bf02aa in finish_call_expr (fn=<overload 0x7fffea94e720>,
args=0x7fffffffc0d0 = {...}, disallow_virtual=false, koenig_p=true,
complain=3) at ../../gcc/cp/semantics.c:2669
...
>From gcc-bugs-return-664444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:12:14 2020
Return-Path: <gcc-bugs-return-664444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20323 invoked by alias); 3 Jan 2020 12:12:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20244 invoked by uid 48); 3 Jan 2020 12:12:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93046] [10 Regression] ICE in cp_gimplify_init_expr
Date: Fri, 03 Jan 2020 12:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93046-4-nP5XFTuVKl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00170.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93046
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> ---
Indeed, started with r279576.
>From gcc-bugs-return-664445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:27:30 2020
Return-Path: <gcc-bugs-return-664445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20584 invoked by alias); 3 Jan 2020 12: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 19931 invoked by uid 48); 3 Jan 2020 12:26:16 -0000
From: "madhur4127 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93141] New: Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 12:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: madhur4127 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00171.txt.bz2
Content-length: 2400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
Bug ID: 93141
Summary: Missed optimization : Use of adc when checking
overflow
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: madhur4127 at gmail dot com
Target Milestone: ---
Created attachment 47584
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47584&action=edit
Complete code for computing dot product (same as the godbolt link)
Consider emulating 192-bit integer using a 128-bit integer and a 64-bit
integer. In the code sample this emulated integer is used to compute dot
product of two uint64_t vectors of length N.
// function to compute dot product of two vectors
using u128 = unsigned __int128;
const int N = 2048;
uint64_t a[N], b[N];
u128 sum = 0;
uint64_t overflow = 0;
for(int i=0;i<N;++i){
u128 prod = (u128) a[i] * (u128) b[i];
sum += prod;
// gcc branches, clang just uses: adc overflow, 0
overflow += sum<prod;
}
To check for overflow in 128-bit addition a branch statement is produced in
assembly while it can be substituted with `adc`. This idiom of manual checking
of Carry Flag works with clang.
Thus a branch statement can be eliminated in this case.
g++ 9.2.0 with -O3 -Wall -Wextra -march=broadwell -fno-unroll-loops produces:
.L3:
mov rdx, QWORD PTR [rdi+rcx]
mulx r9, r8, QWORD PTR [rsi+rcx]
add r14, r8
adc r15, r9
cmp r14, r8 <----- branch because of : overflow += sum < prod;
mov rax, r15
sbb rax, r9
adc r10, 0
add rcx, 8
cmp rcx, 16384
jne .L3
whereas clang++ 9.0.0 with -O3 -Wall -Wextra -march=broadwell -fno-unroll-loops
produces:
.LBB0_1:
mov rax, qword ptr [rsi + 8*rcx]
mul qword ptr [rdi + 8*rcx]
add r10, rax
adc r9, rdx
adc r11, 0 <------- branch eliminated in clang
inc rcx
cmp rcx, 2048
jne .LBB0_1
For complete source code please visit: https://godbolt.org/z/ktdA4b
>From gcc-bugs-return-664446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:29:17 2020
Return-Path: <gcc-bugs-return-664446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25706 invoked by alias); 3 Jan 2020 12:29:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24918 invoked by uid 48); 3 Jan 2020 12:29:11 -0000
From: "madhur4127 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93142] New: Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: madhur4127 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-93142-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00172.txt.bz2
Content-length: 2400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93142
Bug ID: 93142
Summary: Missed optimization : Use of adc when checking
overflow
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: madhur4127 at gmail dot com
Target Milestone: ---
Created attachment 47585
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47585&action=edit
Complete code for computing dot product (same as the godbolt link)
Consider emulating 192-bit integer using a 128-bit integer and a 64-bit
integer. In the code sample this emulated integer is used to compute dot
product of two uint64_t vectors of length N.
// function to compute dot product of two vectors
using u128 = unsigned __int128;
const int N = 2048;
uint64_t a[N], b[N];
u128 sum = 0;
uint64_t overflow = 0;
for(int i=0;i<N;++i){
u128 prod = (u128) a[i] * (u128) b[i];
sum += prod;
// gcc branches, clang just uses: adc overflow, 0
overflow += sum<prod;
}
To check for overflow in 128-bit addition a branch statement is produced in
assembly while it can be substituted with `adc`. This idiom of manual checking
of Carry Flag works with clang.
Thus a branch statement can be eliminated in this case.
g++ 9.2.0 with -O3 -Wall -Wextra -march=broadwell -fno-unroll-loops produces:
.L3:
mov rdx, QWORD PTR [rdi+rcx]
mulx r9, r8, QWORD PTR [rsi+rcx]
add r14, r8
adc r15, r9
cmp r14, r8 <----- branch because of : overflow += sum < prod;
mov rax, r15
sbb rax, r9
adc r10, 0
add rcx, 8
cmp rcx, 16384
jne .L3
whereas clang++ 9.0.0 with -O3 -Wall -Wextra -march=broadwell -fno-unroll-loops
produces:
.LBB0_1:
mov rax, qword ptr [rsi + 8*rcx]
mul qword ptr [rdi + 8*rcx]
add r10, rax
adc r9, rdx
adc r11, 0 <------- branch eliminated in clang
inc rcx
cmp rcx, 2048
jne .LBB0_1
For complete source code please visit: https://godbolt.org/z/ktdA4b
>From gcc-bugs-return-664447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:32:08 2020
Return-Path: <gcc-bugs-return-664447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36737 invoked by alias); 3 Jan 2020 12:32:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36458 invoked by uid 48); 3 Jan 2020 12:32:04 -0000
From: "larsbj at gullik dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93143] New: Multiple calls to static constexpr member function gives wrong code
Date: Fri, 03 Jan 2020 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: larsbj at gullik dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-93143-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00173.txt.bz2
Content-length: 951
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93143
Bug ID: 93143
Summary: Multiple calls to static constexpr member function
gives wrong code
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: larsbj at gullik dot net
Target Milestone: ---
Created attachment 47586
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47586&action=edit
Source showing problem.
This is with g++ (GCC) 10.0.0 20200102 (experimental), on x86_64.
Compile the attached source with:
g++ -std=gnu++17 v8.cpp
When running it aborts, but should not.
(it is the second abort that triggers.)
If the single line in v6_type() is commented out, the example program stops
aborting.
Seems to be some interaction compile time/run time wrt constexpr.
>From gcc-bugs-return-664448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:32:22 2020
Return-Path: <gcc-bugs-return-664448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37511 invoked by alias); 3 Jan 2020 12:32: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 37425 invoked by uid 48); 3 Jan 2020 12:32:15 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77371] [8/9/10 Regression][OpenACC] ICE in force_constant_size, at gimplify.c:671 (... and others)
Date: Fri, 03 Jan 2020 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: chunglin.tang at gmail dot com
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-77371-4-bSCzvppTvE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77371-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77371-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00174.txt.bz2
Content-length: 4866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77371
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #11 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Gerhard Steinmetz from comment #0)
> Some snippets with allocatable scalars (valid code) combined with
> OpenACC. Similar issue for "pointer" instead of "allocatable".
>
> $ cat z1.f90
> program p
> character(:), allocatable :: z
> !$acc parallel
> z = 'abc'
> !$acc end parallel
> print *, z
> end
ZERO-TH ISSUE (OpenACC and OpenMP): I think with 'pointer', there are
additional issues:
– A pointer can be undefined (garbage address) besides not associated (NULL)
and associated.
– Depending on implicit vs. explicit mapping, OpenMP vs. OpenACC and the spec
version, the pointer target may or may not be mapped
– Changing the pointer address on the device is not permitted [except
intermittently] (OpenACC: "Data Structures with Pointers"; OpenMP 5.0, "map
clause", p. 317, ll. 22-25)
FIRST ISSUE (OpenACC only): 'firstprivate' of 'z'
Pre-remark:
* GCC -fopenacc: For "len=3" and "len=n" strings (dummy arg or stack alloc),
OpenACC uses in the dump "map(tofrom:str [len: 3])" etc.
* GCC -fopenmp uses map(tofrom: for all variants, including the test case
above.
GCC 10 dump shows:
#pragma omp target oacc_parallel firstprivate(z) firstprivate(.z)
The firstprivate is odd; I think it should also an implicit 'copy(z)' [alias
"map(tofrom:" as shown in the dump].
I think (cf. second issue) firstprivate(.z) is fine as modifying the pointer
target is not permitted in OpenACC (cf. "Data Structures with Pointers").
In any case, the OpenACC spec is also bad. (I have filled OpenACC Issue 254 for
this.) It has:
"an array or composite variable referenced in the parallel construct that does
not appear in a data clause for the construct or any enclosing data construct
will be treated as if it appeared in a copy clause for the parallel construct"
[…]
"A scalar variable referenced in the parallel construct that does not appear in
a data clause for the construct or any enclosing data construct will be treated
as if it appeared in a firstprivate clause"
Here, "z" is clearly not a scalar (see OpenACC Glossary) as it is of character
type. It is an aggregated variable (which encompasses nonscalar types). –
However, it is neither an array (Fortran sense as not in the glossary) nor a
composite type (as defined in the glossary); in particular, it is not a
'composite variable' as the latter requires nonallocatable/nonpointer
variables.
Side note: pointers will have additional issues, thus a spec fix probably
should distinguish between pointers and allocatables. In any case, current spec
already has problems without allocatable/pointer.
* * *
SECOND ISSUE: 'firstprivate' of DECL_ARTIFICIAL string-length variable
OpenACC *and* OpenMP: occurs with implicit mapping in OpenMP – and with an
explicit "copy(z)" / "map(tofrom:"
The dump shows:
map(tofrom:*z [len: SAVE_EXPR <.z.5>]) map(alloc:z [pointer assign, bias: 0])
firstprivate(.z)
Here ".z" is an artificial variable generated by the compiler and storing the
string length of the variable.
That mapping is fine unless one does (re)allocations within the target/parallel
region – in particular, those which modify the string-length and, hence, the
artificial variable.
I am not sure whether (re)allocating within an omp target/acc parallel/acc
kernels section is permitted. [If one has unified-shared memory, it will work,
except for the firstprivate(.z).]
*In OpenMP 5.0,* I find the restriction (2.12.5 target Construct):
"An attached pointer that is associated with a given pointer target must not
become associated with a different pointer target in a target region."
Which implies that re-allocation is permitted for 'allocatable' (as in the test
case, assuming 'omp target' instead of 'acc parallel').
In OpenACC 2.7 + 3.0, "Data Structures with Pointers", I only find:
"When the device pointer target is deallocated, the pointer in device memory
should be restored to the host value, so it can be safely copied back to host
memory"
This does not talk about re-allocation but could be read such that
(re)allocation on the device is not permitted.
HENCE, if I read the specs correctly, there are the following bugs:
* OpenACC in GCC: should use "copy(z)" for the test case
* OpenACC as spec: needs to be fixed/clarified
* OpenMP in GCC: assuming (re)allocation of 'allocatables' is permitted,
firstprivate(.z) should be a 'map(tofrom:'.
>From gcc-bugs-return-664449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 12:53:54 2020
Return-Path: <gcc-bugs-return-664449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105245 invoked by alias); 3 Jan 2020 12:53:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105125 invoked by uid 48); 3 Jan 2020 12:53:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93046] [10 Regression] ICE in cp_gimplify_init_expr
Date: Fri, 03 Jan 2020 12:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-93046-4-x26sRSHoQa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00175.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93046
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47587
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47587&action=edit
gcc10-pr93046.patch
Untested fix.
>From gcc-bugs-return-664450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:04:14 2020
Return-Path: <gcc-bugs-return-664450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3040 invoked by alias); 3 Jan 2020 13:04:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2945 invoked by uid 48); 3 Jan 2020 13:04:10 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93144] New: [10 Regression] 459.GemsFDTD debug info size increase by 50% since r279563
Date: Fri, 03 Jan 2020 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc blocked target_milestone
Message-ID: <bug-93144-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00176.txt.bz2
Content-length: 841
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93144
Bug ID: 93144
Summary: [10 Regression] 459.GemsFDTD debug info size increase
by 50% since r279563
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org
Blocks: 26163
Target Milestone: ---
Since the revision I see the following regression:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=289.195.4
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-664451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:05:27 2020
Return-Path: <gcc-bugs-return-664451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5193 invoked by alias); 3 Jan 2020 13:05: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 5169 invoked by uid 48); 3 Jan 2020 13:05:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93144] [10 Regression] 459.GemsFDTD debug info size increase by 50% since r279563
Date: Fri, 03 Jan 2020 13:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-93144-4-ppT4ZOQVwF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93144-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93144-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00177.txt.bz2
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93144
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
There's a longer history for -march=znver1 machine:
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=4.195.4
>From gcc-bugs-return-664452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:09:09 2020
Return-Path: <gcc-bugs-return-664452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25444 invoked by alias); 3 Jan 2020 13:09:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24741 invoked by uid 48); 3 Jan 2020 13:09:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93137] [10 regression] ICE in refs_may_alias_p_2
Date: Fri, 03 Jan 2020 13:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93137-4-tgha1OeTpk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93137-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93137-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00178.txt.bz2
Content-length: 951
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93137
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> ---
I'm actually getting here
pr93137.C: In function ‘void foo(const string&)’:
pr93137.C:3:6: error: incorrect sharing of tree nodes
3 | void foo (const std::string& s)
| ^~~
*D.30380
D.30380->LibSuffix = std::operator+<char, std::char_traits<char>,
std::allocator<char> > ("/gcc/", s); [return slot optimization]
during GIMPLE pass: cfg
pr93137.C:3:6: internal compiler error: verify_gimple failed
0x158d570 verify_gimple_in_cfg(function*, bool)
../../gcc/tree-cfg.c:5445
so it looks like a dup of the other C++ tree node sharing PRs.
>From gcc-bugs-return-664453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:41:17 2020
Return-Path: <gcc-bugs-return-664453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69059 invoked by alias); 3 Jan 2020 13:41: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 69011 invoked by uid 48); 3 Jan 2020 13:41:13 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77371] [8/9/10 Regression][OpenACC] ICE in force_constant_size, at gimplify.c:671 (... and others)
Date: Fri, 03 Jan 2020 13:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: chunglin.tang at gmail dot com
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77371-4-z9bGnBUOxU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77371-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77371-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00179.txt.bz2
Content-length: 640
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77371
--- Comment #12 from Tobias Burnus <burnus at gcc dot gnu.org> ---
[OpenACC]
The following patch fixes the "firstprivate(z)" issue – but it also assumes
that a pointer variable is not undefined (only null/not associated or
associated is fine); interestingly, it also yields "copy(.z)" – not only
"copy(z)".
--- a/gcc/gimplify.c
+++ b/gcc/gimplify.c
@@ -7311 +7311 @@ oacc_default_clause (struct gimplify_omp_ctx *ctx, tree decl,
unsigned flags)
- else if (AGGREGATE_TYPE_P (type))
+ else if (AGGREGATE_TYPE_P (type) || omp_is_allocatable_or_ptr (decl))
>From gcc-bugs-return-664454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:43:22 2020
Return-Path: <gcc-bugs-return-664454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71215 invoked by alias); 3 Jan 2020 13:43:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71118 invoked by uid 48); 3 Jan 2020 13:43:17 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93033] [10 Regression] error: incorrect sharing of tree nodes
Date: Fri, 03 Jan 2020 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93033-4-7RU84mU0Cv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00180.txt.bz2
Content-length: 636
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase from PR93137:
template <typename, typename = int>
struct A {
A ();
~A ();
};
template <typename T, typename U, typename V>
A<T> operator+(const T *, A<U, V>);
void
foo ()
{
A<char> f;
struct { A<char> g; bool h; } i[] {"" + f};
}
>From gcc-bugs-return-664455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:44:00 2020
Return-Path: <gcc-bugs-return-664455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72574 invoked by alias); 3 Jan 2020 13:44: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 72466 invoked by uid 48); 3 Jan 2020 13:43:55 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/93015] [10 Regression] Segmentation fault (ipcp_store_vr_results(void))
Date: Fri, 03 Jan 2020 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93015-4-QEr8qP0mB4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00181.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93015
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Should be fixed now.
>From gcc-bugs-return-664456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:44:07 2020
Return-Path: <gcc-bugs-return-664456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73266 invoked by alias); 3 Jan 2020 13:44:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72674 invoked by uid 48); 3 Jan 2020 13:44:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93137] [10 regression] ICE in refs_may_alias_p_2
Date: Fri, 03 Jan 2020 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93137-4-MNBp7KMfWD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93137-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93137-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00182.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93137
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe it is a dup.
*** This bug has been marked as a duplicate of bug 93033 ***
>From gcc-bugs-return-664457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:44:10 2020
Return-Path: <gcc-bugs-return-664457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73557 invoked by alias); 3 Jan 2020 13:44:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72967 invoked by uid 48); 3 Jan 2020 13:44:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93033] [10 Regression] error: incorrect sharing of tree nodes
Date: Fri, 03 Jan 2020 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93033-4-Ad2XarpoPj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00183.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sss@li-snyder.org
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
*** Bug 93137 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-664458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:53:14 2020
Return-Path: <gcc-bugs-return-664458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97881 invoked by alias); 3 Jan 2020 13:53: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 97822 invoked by uid 55); 3 Jan 2020 13:53:09 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92917] [10 Regression] ICE in print_all_lattices at gcc/ipa-cp.c:547 since r278016.
Date: Fri, 03 Jan 2020 13:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92917-4-nawRCfDaho@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92917-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92917-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00184.txt.bz2
Content-length: 541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92917
--- Comment #2 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Fri Jan 3 13:52:38 2020
New Revision: 279859
URL: https://gcc.gnu.org/viewcvs?rev=279859&root=gcc&view=rev
Log:
Avoid segfault when dumping IPA-CP lattices for unoptimized functions (PR
92917)
2020-01-03 Martin Jambor <mjambor@suse.cz>
PR ipa/92917
* ipa-cp.c (print_all_lattices): Skip functions without info.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-cp.c
>From gcc-bugs-return-664459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:54:04 2020
Return-Path: <gcc-bugs-return-664459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130170 invoked by alias); 3 Jan 2020 13:54:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130107 invoked by uid 48); 3 Jan 2020 13:54:00 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92917] [10 Regression] ICE in print_all_lattices at gcc/ipa-cp.c:547 since r278016.
Date: Fri, 03 Jan 2020 13:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92917-4-3ACvFbhR9X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92917-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92917-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00185.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92917
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed with https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00060.html
>From gcc-bugs-return-664460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 13:59:25 2020
Return-Path: <gcc-bugs-return-664460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14251 invoked by alias); 3 Jan 2020 13:59:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14174 invoked by uid 48); 3 Jan 2020 13:59:20 -0000
From: "madhur4127 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 13:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: madhur4127 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-93141-4-WxCUQe6EOA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00186.txt.bz2
Content-length: 322
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
--- Comment #1 from Madhur Chauhan <madhur4127 at gmail dot com> ---
The source of this bug is the stackoverflow Q&A:
https://stackoverflow.com/questions/59575408/fastest-way-to-sum-dot-product-of-vector-of-unsigned-64-bit-integers-using-192-2/59579310#59579310
>From gcc-bugs-return-664461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 14:08:22 2020
Return-Path: <gcc-bugs-return-664461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44601 invoked by alias); 3 Jan 2020 14:08: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 44557 invoked by uid 48); 3 Jan 2020 14:08:17 -0000
From: "peter at cordes dot ca" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: peter at cordes dot ca
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93141-4-32bjovSdlX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00187.txt.bz2
Content-length: 1204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
Peter Cordes <peter at cordes dot ca> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |peter at cordes dot ca
--- Comment #2 from Peter Cordes <peter at cordes dot ca> ---
gcc doesn't actually *branch* unless you use an if(), it just uses cmp/sbb to
do a 128-bit compare. CMP is like a SUB that only sets flags. The CF result
of SBB is used as an input for ADC.
https://godbolt.org/z/64C4R- of a testcase
GCC also wastes a varying number of MOV instructions beyond the minimum one to
make cmp/sbb work, depending on BMI2 MULX or not, and how the sum is written.
u128 prod = a[i] * (unsigned __int128) b[i];
#if 1
sum += prod;
//if(sum<prod) overflow++; // gcc branches on mov/cmp/sbb
overflow += sum<prod; // gcc uses adc after a mov/cmp/sbb
#else
overflow += __builtin_add_overflow(sum, prod, &sum); // gcc less bad,
fewer MOV
#endif
clang makes efficient asm for all 3 ways, if you stop it from unrolling and
using setc/movzx/add.
>From gcc-bugs-return-664462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 14:33:50 2020
Return-Path: <gcc-bugs-return-664462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15777 invoked by alias); 3 Jan 2020 14:33:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15726 invoked by uid 48); 3 Jan 2020 14:33:46 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Fri, 03 Jan 2020 14:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91369-4-QCNe6G8h5I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00188.txt.bz2
Content-length: 641
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
--- Comment #25 from Toni Neubert <lutztonineubert at gmail dot com> ---
I get: "deallocation of already deallocated storage" for test2() but compiling
just test1() or test2() is just fine.
struct a {
constexpr a(int* i) : i{i} {
}
constexpr ~a() {
delete[] i;
}
int* i;
};
constexpr a make_a(int size) {
return {new int[size]()};
}
constexpr bool test1() {
make_a(1);
return true;
}
constexpr bool test2() {
make_a(1);
return true;
}
static_assert(test1());
static_assert(test2());
>From gcc-bugs-return-664463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 15:02:51 2020
Return-Path: <gcc-bugs-return-664463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5740 invoked by alias); 3 Jan 2020 15:02: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 5292 invoked by uid 48); 3 Jan 2020 15:02:46 -0000
From: "gcc at gmch dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/93145] New: strerror_r() and INT_MIN returns "Unknown error -18446744071562067968" (for x86_64)
Date: Fri, 03 Jan 2020 15:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc at gmch dot uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93145-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00189.txt.bz2
Content-length: 1936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93145
Bug ID: 93145
Summary: strerror_r() and INT_MIN returns "Unknown error
-18446744071562067968" (for x86_64)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: gcc at gmch dot uk
Target Milestone: ---
For unknown errors __strerror_r() does:
p = _itoa_word (abs (errnum), &numbuf[20], 10, 0);
where abs(INT_MIN) is undefined. As it happens, on x86_64 abs(INT_MIN) returns
INT_MIN, which is widened to unsigned long long int -- hence the silly result.
I guess absll(errnum) would fix the error where long long int is bigger than
int.
Otherwise, I dunno what hoops the library should be jumping through to allow
for not-2's-complement.
FWIW: the man-page mentions EINVAL and ERANGE errors, but is silent on whether
the GNU strerror_r() returns errors. The implementation clearly does not
return any errors -- not even for buflen == 0 (with or without buf == NULL).
[buf == NULL with buflen != 0 gives a SEGV -- duh.]
Also FWIW: the man-page, in general, talks of known/unknown error numbers and
valid/invalid error numbers, but does not say how or whether those are
different. This is also true of POSIX.1 which is not a miracle of precision
either. The glibc POSIX/XSI implementation clearly does not distinguish known
and valid, and 0 is known -- the function returns EINVAL for unknown error
numbers, as well as setting a string. (Incidentally, if EINVAL is returned
that takes precedence over ERANGE, but that's also a secret.)
It would be nice to have a function to map an error number to its macro-name,
returning a constant string (for known) or NULL (for unknown) errors. But
that's another story.
Chris
>From gcc-bugs-return-664464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 15:04:13 2020
Return-Path: <gcc-bugs-return-664464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14759 invoked by alias); 3 Jan 2020 15:04:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14662 invoked by uid 48); 3 Jan 2020 15:04:08 -0000
From: "ph3rin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93106] [c++2a] Deleted move constructor is not selected when returning an automatic variable
Date: Fri, 03 Jan 2020 15:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ph3rin 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-93106-4-3VPOCCalDq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00190.txt.bz2
Content-length: 1103
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93106
--- Comment #2 from Yunrui Wang <ph3rin at gmail dot com> ---
(In reply to Jakub Jelinek from comment #1)
> What you cite doesn't say anything that would make the testcase invalid.
> The standard says that for an implicitly movable entity seen in return
> statement shall first perform overload resolution for the copy constructor
> as if it was an rvalue, which in this case fails because the move ctor is
> deleted. And in that case, another overload resolution is performed, this
> time considering the implicitly movable entity as lvalue, and that succeeds.
> So, if copy-ellision wouldn't be performed,
> not_movable::not_movable(not_movable const&) would be invoked, but in this
> case copy-ellision is invoked and thus it is default constructed into the
> return value object in the caller.
The first overload resolution should succeed by selecting the deleted move
constructors. Deleted functions are defined and are considered for overload
resolution (unless otherwise specified - there are some edge cases, but not in
this example).
>From gcc-bugs-return-664465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 15:24:54 2020
Return-Path: <gcc-bugs-return-664465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79665 invoked by alias); 3 Jan 2020 15:24: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 79592 invoked by uid 48); 3 Jan 2020 15:24:50 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93033] [10 Regression] error: incorrect sharing of tree nodes
Date: Fri, 03 Jan 2020 15:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-93033-4-ZGbpQWPMr2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00191.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
>From gcc-bugs-return-664466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:21:07 2020
Return-Path: <gcc-bugs-return-664466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56091 invoked by alias); 3 Jan 2020 16:21:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56020 invoked by uid 48); 3 Jan 2020 16:21:02 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91640] [9/10 Regression] ICE: gimplification failed (contiguous expr)
Date: Fri, 03 Jan 2020 16:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91640-4-SJ9vjg0kpm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00192.txt.bz2
Content-length: 1033
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91640
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> Note gimplification fails because we are evaluating in an lvalue context but
> got -_7 in the end. In the past we've hacked around Fortran oddities by
> doing tem = -_7
Doing "tem = -_7" automatically would paper about a FE bug which is surely the
wrong approach!
For this ICE, gfortran is doing a copy-in/copy-out if the argument is not known
to be contiguous (i.e. not simply contiguous). — The copy-in ("tmp = -z") is
fine.
But if it is not a variable, copying-back does not make sense ("-z = tmp").
* * *
Patch: https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00070.html
>From gcc-bugs-return-664467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:28:06 2020
Return-Path: <gcc-bugs-return-664467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111654 invoked by alias); 3 Jan 2020 16:28: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 105036 invoked by uid 48); 3 Jan 2020 16:28:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93141-4-e0MUdN9vgb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00193.txt.bz2
Content-length: 3650
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Untested fix, though this is just about double-word uaddv4, would be good to
handle double-word usubv4, addv4 and subv4 similarly.
--- gcc/config/i386/i386.md.jj 2020-01-03 11:10:43.839511446 +0100
+++ gcc/config/i386/i386.md 2020-01-03 17:05:51.435808734 +0100
@@ -1036,6 +1036,9 @@
(define_mode_iterator DWI [(DI "!TARGET_64BIT")
(TI "TARGET_64BIT")])
+;; SWI and DWI together.
+(define_mode_iterator SWIDWI [QI HI SI DI (TI "TARGET_64BIT")])
+
;; GET_MODE_SIZE for selected modes. As GET_MODE_SIZE is not
;; compile time constant, it is faster to use <MODE_SIZE> than
;; GET_MODE_SIZE (<MODE>mode). For XFmode which depends on
@@ -6121,12 +6124,12 @@
(define_expand "uaddv<mode>4"
[(parallel [(set (reg:CCC FLAGS_REG)
(compare:CCC
- (plus:SWI
- (match_operand:SWI 1 "nonimmediate_operand")
- (match_operand:SWI 2 "<general_operand>"))
+ (plus:SWIDWI
+ (match_operand:SWIDWI 1 "nonimmediate_operand")
+ (match_operand:SWIDWI 2 "<general_operand>"))
(match_dup 1)))
- (set (match_operand:SWI 0 "register_operand")
- (plus:SWI (match_dup 1) (match_dup 2)))])
+ (set (match_operand:SWIDWI 0 "register_operand")
+ (plus:SWIDWI (match_dup 1) (match_dup 2)))])
(set (pc) (if_then_else
(ltu (reg:CCC FLAGS_REG) (const_int 0))
(label_ref (match_operand 3))
@@ -6885,6 +6888,49 @@
[(set_attr "type" "alu")
(set_attr "mode" "SI")])
+(define_insn_and_split "*add<dwi>3_doubleword_cc_overflow_1"
+ [(set (reg:CCC FLAGS_REG)
+ (compare:CCC
+ (plus:<DWI>
+ (match_operand:<DWI> 1 "nonimmediate_operand" "%0,0")
+ (match_operand:<DWI> 2 "x86_64_hilo_general_operand" "r<di>,o"))
+ (match_dup 1)))
+ (set (match_operand:<DWI> 0 "nonimmediate_operand" "=ro,r")
+ (plus:<DWI> (match_dup 1) (match_dup 2)))]
+ "ix86_binary_operator_ok (PLUS, <DWI>mode, operands)"
+ "#"
+ "reload_completed"
+ [(parallel [(set (reg:CCC FLAGS_REG)
+ (compare:CCC
+ (plus:DWIH (match_dup 1) (match_dup 2))
+ (match_dup 1)))
+ (set (match_dup 0)
+ (plus:DWIH (match_dup 1) (match_dup 2)))])
+ (parallel [(set (reg:CCC FLAGS_REG)
+ (compare:CCC
+ (zero_extend:<DWI>
+ (plus:DWIH
+ (plus:DWIH
+ (ltu:DWIH (reg:CC FLAGS_REG) (const_int 0))
+ (match_dup 4))
+ (match_dup 5)))
+ (plus:<DWI>
+ (zero_extend:<DWI> (match_dup 5))
+ (ltu:<DWI> (reg:CC FLAGS_REG) (const_int 0)))))
+ (set (match_dup 3)
+ (plus:DWIH
+ (plus:DWIH (ltu:DWIH (reg:CC FLAGS_REG) (const_int 0))
+ (match_dup 4))
+ (match_dup 5)))])]
+{
+ split_double_mode (<DWI>mode, &operands[0], 3, &operands[0], &operands[3]);
+ if (operands[2] == const0_rtx)
+ {
+ emit_insn (gen_addcarry<mode>_0 (operands[3], operands[4],
operands[5]));
+ DONE;
+ }
+})
+
;; x == 0 with zero flag test can be done also as x < 1U with carry flag
;; test, where the latter is preferrable if we have some carry consuming
;; instruction.
>From gcc-bugs-return-664468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:29:02 2020
Return-Path: <gcc-bugs-return-664468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126351 invoked by alias); 3 Jan 2020 16:29:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126300 invoked by uid 48); 3 Jan 2020 16:28:57 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91648] [9/10 Regression] ICE in generate_finalization_wrapper, at fortran/class.c:2009
Date: Fri, 03 Jan 2020 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-91648-4-bYCIy5lkeo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00194.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91648
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |tkoenig at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
>From gcc-bugs-return-664469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:31:38 2020
Return-Path: <gcc-bugs-return-664469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49418 invoked by alias); 3 Jan 2020 16:31: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 49368 invoked by uid 48); 3 Jan 2020 16:31:33 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91648] [9/10 Regression] ICE in generate_finalization_wrapper, at fortran/class.c:2009
Date: Fri, 03 Jan 2020 16:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-91648-4-yuXZs4DLBt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00195.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91648
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|tkoenig at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Wrong bug
>From gcc-bugs-return-664470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:35:14 2020
Return-Path: <gcc-bugs-return-664470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54918 invoked by alias); 3 Jan 2020 16:35: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 54848 invoked by uid 48); 3 Jan 2020 16:35:09 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93146] New: TLS init function not generated on AIX
Date: Fri, 03 Jan 2020 16:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-93146-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00196.txt.bz2
Content-length: 2784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93146
Bug ID: 93146
Summary: TLS init function not generated on AIX
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: dje at gcc dot gnu.org
Target Milestone: ---
Target: powerpc-ibm-aix*
SYMPTOM:
On AIX, TLS init elicits linker errors such as
TLS init fuction for thread_local_seg_handler
or
__tls_init
An example C++ program is
$ cat a.cc
#include <atomic>
struct Test {std::atomic<int> x; };
thread_local Test t;
$ cat main.cc
#include <atomic>
struct Test {std::atomic<int> x; };
extern thread_local Test t;
int main () {
return t.x.load();
}
$ g++ -std=c++14 -pthread a.cc main.cc
ld: 0711-317 ERROR: Undefined symbol: __tls_init
BACKGROUND:
AIX XCOFF symbol aliases do not function the same as ELF symbols aliases: XCOFF
generates "hard aliases" (like hard links) with only one definition and the
attributes are shared / overwritten, instead of a "symbolic" reference to the
other definition with its own attributes. Because of this
gcc/config/rs6000/xcoff.h defines:
/* This is how we tell the assembler to equate two values.
The semantic of AIX assembler's .set do not correspond to middle-end
expectat
ions.
We output aliases as alternative symbols in the front of the definition
via DECLARE_FUNCTION_NAME and DECLARE_OBJECT_NAME.
We still need to define this macro to let middle-end know that aliases are
supported.
*/
#define ASM_OUTPUT_DEF(FILE,LABEL1,LABEL2) do { } while (0)
Honza generously provided other AIX-specific code for function aliases that
generate alternative labels in front of the definition.
Because of this, GCC internals consider AIX as TARGET_SUPPORTS_ALIASES. Note
that the above macro will not output anything for an alias.
AIX also support TLS.
These two features / behaviors collide for TLS init functions. gcc/cp/decl2.c
get_tls_init_fn() and handle_tls_init() depend upon TARGET_SUPPORTS_ALIASES,
e.g.,
if (TARGET_SUPPORTS_ALIASES && TREE_PUBLIC (var))
{
tree single_init_fn = get_tls_init_fn (var);
if (single_init_fn == NULL_TREE)
continue;
cgraph_node *alias
= cgraph_node::get_create (fn)->create_same_body_alias
(single_init_fn, fn);
gcc_assert (alias != NULL);
}
Disabling TARGET_SUPPORTS_ALIASES within cp/decl2.c does not generate correct
code (it switches from a mangled TLS init function to __tls_init).
How can G++ be coerced to generate TLS init functions for AIX?
>From gcc-bugs-return-664471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:36:19 2020
Return-Path: <gcc-bugs-return-664471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59643 invoked by alias); 3 Jan 2020 16:36: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 59593 invoked by uid 48); 3 Jan 2020 16:36:16 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93146] C++ TLS init function not generated on AIX
Date: Fri, 03 Jan 2020 16:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-93146-4-63SVxt9HZH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93146-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93146-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00197.txt.bz2
Content-length: 627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93146
David Edelsohn <dje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
CC| |hubicka at gcc dot gnu.org,
| |jason at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from David Edelsohn <dje at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-664472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 16:46:06 2020
Return-Path: <gcc-bugs-return-664472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12876 invoked by alias); 3 Jan 2020 16:46:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12779 invoked by uid 48); 3 Jan 2020 16:45:53 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93136] [10 regression] gcc.dg/vmx/ops.c and several other test break after r279772
Date: Fri, 03 Jan 2020 16:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93136-4-oI01CGDb23@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00198.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93136
--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
So the vmx/ops.c test just needs -flax-vector-conversions to quiet the
warnings.
The vsx-vector-6-p*.c tests actually have some differences in the number of
xxand, etc. insn counts. I'll find out why they've changed.
>From gcc-bugs-return-664473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 17:14:45 2020
Return-Path: <gcc-bugs-return-664473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18364 invoked by alias); 3 Jan 2020 17:14:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18300 invoked by uid 48); 3 Jan 2020 17:14:41 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91640] [9/10 Regression] ICE: gimplification failed (contiguous expr)
Date: Fri, 03 Jan 2020 17:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-91640-4-4xKAw6Bj9g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00199.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91640
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Should be rather simple to fix.
>From gcc-bugs-return-664474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 17:48:35 2020
Return-Path: <gcc-bugs-return-664474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105749 invoked by alias); 3 Jan 2020 17:48: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 105561 invoked by uid 48); 3 Jan 2020 17:48:13 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91648] [9/10 Regression] ICE in generate_finalization_wrapper, at fortran/class.c:2009
Date: Fri, 03 Jan 2020 17:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-91648-4-ojaRIVfsyA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00200.txt.bz2
Content-length: 1785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91648
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |burnus at gcc dot gnu.org
--- Comment #3 from Tobias Burnus <burnus at gcc dot gnu.org> ---
During resolution, one has the call tree:
gfc_resolve (ns) -> resolve_types -> gfc_traverse_ns (ns, resolve_symbol) ->
resolve_fl_derived -> gfc_resolve_finalizers
And generate_finalization_wrapper assumes that:
gcc_assert (fini->proc_tree); /* Should have been set in
gfc_resolve_finalizers. */
However, for the test case, one has:
#0 generate_finalization_wrapper (vtab_final=<optimized out>,
vtab_final=<optimized out>, tname=0x7fffffffd450 "m_T", ns=<optimized out>,
derived=<optimized out>) at ../../repos/gcc/gcc/fortran/class.c:2009
#1 gfc_find_derived_vtab (derived=<optimized out>) at
../../repos/gcc/gcc/fortran/class.c:2487
#2 0x0000000000836611 in gfc_find_vtab (ts=0x24f98d8) at
../../repos/gcc/gcc/fortran/class.c:2865
#3 0x0000000000885de3 in gfc_match_assignment () at
../../repos/gcc/gcc/fortran/match.c:1375
Namely, generate_finalization_wrapper is already called during parsing.
Side note: "s" is called recursively – without being marked 'recursive'.
Additionally, at the end of 's', s(y) is called, which calls s(y) etc. –
something which will never finish ...
Better variant – same ICE but avoids this problem:
module m
type t
contains
final :: s
end type
contains
subroutine g(x)
type(t) :: x
class(*), allocatable :: y
y = x
end
subroutine s(x)
type(t) :: x
end
end
>From gcc-bugs-return-664475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 18:34:12 2020
Return-Path: <gcc-bugs-return-664475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8153 invoked by alias); 3 Jan 2020 18:34: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 8122 invoked by uid 48); 3 Jan 2020 18:34:07 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93147] New: std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 18:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00201.txt.bz2
Content-length: 2063
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
Bug ID: 93147
Summary: std::tuple of empty structs with member equality
operators has ambiguous equality operator
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kholdstare0.0 at gmail dot com
Target Milestone: ---
The following code:
#include <tuple>
struct A {
bool operator == (A) const { return true; }
};
struct B {
bool operator == (B) const { return true; }
};
using Tuple = std::tuple<A, B>;
bool example(Tuple a, Tuple b)
{
return a == b;
}
Results in an error:
<source>: In function 'bool example(Tuple, Tuple)':
<source>:18:21: error: request for member 'operator==' is ambiguous
18 | return a == b;
| ^
<source>:4:14: note: candidates are: 'bool A::operator==(A) const'
4 | bool operator == (A) const { return true; }
| ^~~~~~~~
<source>:8:14: note: 'bool B::operator==(B) const'
8 | bool operator == (B) const { return true; }
| ^~~~~~~~
Compiler returned: 1
Here is the godbolt link, with the preprocessor output on the side:
https://godbolt.org/z/a4TuB3
Some things to note:
- This compiles fine with Clang
- If the structs are non-empty, this also compiles fine
- If the comparison operators are non-members this also compiles fine
- The failure is exactly the same going back all the way to gcc 4
My suspicion is that tuple indirectly inherits the types `A` and `B`, and even
though it may be private inheritance, the compiler still finds both comparison
operators and considers them ambiguous. GCC tries to implicitly convert
`std::tuple<A, B>` into `A` and `B` to call `operator ==`.
>From gcc-bugs-return-664476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 18:39:30 2020
Return-Path: <gcc-bugs-return-664476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14718 invoked by alias); 3 Jan 2020 18:39:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14682 invoked by uid 48); 3 Jan 2020 18:39:25 -0000
From: "joel at airwebreathe dot org.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93005] Redundant NEON loads/stores from stack are not eliminated
Date: Fri, 03 Jan 2020 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel at airwebreathe dot org.uk
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93005-4-idped2uLI3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00202.txt.bz2
Content-length: 859
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93005
--- Comment #3 from Joel Holdsworth <joel at airwebreathe dot org.uk> ---
Interesting. Comparing the implementation of _mm_store_si128 to vst1q_s32:
emminitrin.h
extern __inline void __attribute__((__gnu_inline__, __always_inline__,
__artificial__))
_mm_store_si128 (__m128i *__P, __m128i __B)
{
*__P = __B;
}
arm_neon.h
__extension__ extern __inline void
__attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
vst1q_s32 (int32_t * __a, int32x4_t __b)
{
__builtin_neon_vst1v4si ((__builtin_neon_si *) __a, __b);
}
So why is one implemented with a built-in, and the other with a pointer
dereference?
Is there a way of making the optimizer see through __builtin_neon_vst1v4si with
GIMPLE? Where would the code be implemented? Where is it implemented for other
architectures?
>From gcc-bugs-return-664477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 18:41:57 2020
Return-Path: <gcc-bugs-return-664477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29469 invoked by alias); 3 Jan 2020 18:41: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 29368 invoked by uid 48); 3 Jan 2020 18:41:53 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93136] [10 regression] gcc.dg/vmx/ops.c and several other test break after r279772
Date: Fri, 03 Jan 2020 18:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bergner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93136-4-WHrYbPMz3u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00203.txt.bz2
Content-length: 220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93136
--- Comment #3 from Peter Bergner <bergner at gcc dot gnu.org> ---
So the vsx-vector-6.p*.c FAILs are due to sloppy insn counting in the test
cases. I have a patch.
>From gcc-bugs-return-664478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 18:42:48 2020
Return-Path: <gcc-bugs-return-664478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30836 invoked by alias); 3 Jan 2020 18:42:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30788 invoked by uid 48); 3 Jan 2020 18:42:44 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-93147-4-fA9Mqzo428@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00204.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c++ |libstdc++
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
> - This compiles fine with Clang
Is that with GCC's libstdc++ or LLVM's stdc++? Both can be used and that is
why I am asking.
>From gcc-bugs-return-664479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 18:46:27 2020
Return-Path: <gcc-bugs-return-664479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36356 invoked by alias); 3 Jan 2020 18:46:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36199 invoked by uid 48); 3 Jan 2020 18:46:22 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-jt0RpTZW2N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00205.txt.bz2
Content-length: 250
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #2 from Alexander Kondratskiy <kholdstare0.0 at gmail dot com> ---
Hi, it compiles fine with both.
See godbolt link for Clang using GCC's libstdc++ : https://godbolt.org/z/iFHemn
>From gcc-bugs-return-664480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 18:51:09 2020
Return-Path: <gcc-bugs-return-664480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43475 invoked by alias); 3 Jan 2020 18:51: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 43302 invoked by uid 48); 3 Jan 2020 18:51:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/93145] strerror_r() and INT_MIN returns "Unknown error -18446744071562067968" (for x86_64)
Date: Fri, 03 Jan 2020 18:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
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 resolution
Message-ID: <bug-93145-4-9AnwgzhqPf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93145-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93145-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00206.txt.bz2
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93145
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |MOVED
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
You want to file it against glibc; https://sourceware.org/bugzilla .
glibc has the implementation of strerror_r/_itoa_word .
>From gcc-bugs-return-664481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 19:12:53 2020
Return-Path: <gcc-bugs-return-664481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99894 invoked by alias); 3 Jan 2020 19: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 99846 invoked by uid 48); 3 Jan 2020 19:12:48 -0000
From: "gcc at gmch dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/93145] strerror_r() and INT_MIN returns "Unknown error -18446744071562067968" (for x86_64)
Date: Fri, 03 Jan 2020 19:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gcc at gmch dot uk
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:
Message-ID: <bug-93145-4-pz3LuTY1pU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93145-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93145-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00207.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93145
--- Comment #2 from Chris Hall <gcc at gmch dot uk> ---
(In reply to Andrew Pinski from comment #1)
> You want to file it against glibc; https://sourceware.org/bugzilla .
> glibc has the implementation of strerror_r/_itoa_word .
Ooops. I thought this would be the right place to report glibc issues. Sorry
for the noise. Thanks for the pointer -- have filed against glibc.
Chris
>From gcc-bugs-return-664482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 19:40:45 2020
Return-Path: <gcc-bugs-return-664482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99245 invoked by alias); 3 Jan 2020 19:40: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 99197 invoked by uid 48); 3 Jan 2020 19:40:40 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBmb3J0cmFuLzkzMTQ4XSBOZXc6IFBvaW50ZXItZnVuY3Rpb24tcmVz?= =?UTF-8?B?dWx0IGFzIExWQUxVRSB2YXJpYWJsZSDigJMgZnVuY3Rpb24gY2FsbGVkIG11?= =?UTF-8?B?bHRpcGxlIHRpbWVzIHdpdGggY29weS1pbi9vdXQ=?Date: Fri, 03 Jan 2020 19:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-93148-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00208.txt.bz2
Content-length: 1148
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93148
Bug ID: 93148
Summary: Pointer-function-result as LVALUE variable – function
called multiple times with copy-in/out
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: tkoenig at gcc dot gnu.org
Target Milestone: ---
Created attachment 47588
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47588&action=edit
Test case – compile & run
Found when looking at PR91640, cf.
https://gcc.gnu.org/ml/gcc-patches/2020-01/threads.html#00070
If one uses:
call foo(f())
where foo takes a nonpointer dummy argument and f returns a pointer, the
pointer result is regarded as normal variable. (= gfc_is_variable == true).
Unfortunately, "f()" is called twice: once for the copy in and once for the
copy out.
Expected: It is only called once. See attached test case.
>From gcc-bugs-return-664483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 19:41:22 2020
Return-Path: <gcc-bugs-return-664483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100161 invoked by alias); 3 Jan 2020 19:41: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 100086 invoked by uid 48); 3 Jan 2020 19:41:17 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 19:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-7hgBMQ9ZtH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00209.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Alexander Kondratskiy from comment #0)
> My suspicion is that tuple indirectly inherits the types `A` and `B`, and
> even though it may be private inheritance, the compiler still finds both
> comparison operators and considers them ambiguous. GCC tries to implicitly
> convert `std::tuple<A, B>` into `A` and `B` to call `operator ==`.
Yes, there were plans to use [[unique_address]] instead, but either noone had
time to implement it, or they found an issue with this plan.
The difference of behavior with clang seems worth investigating though.
>From gcc-bugs-return-664484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 19:44:17 2020
Return-Path: <gcc-bugs-return-664484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102744 invoked by alias); 3 Jan 2020 19:44:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102694 invoked by uid 48); 3 Jan 2020 19:44:13 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93119] [ICE] The traditional TLS support of aarch64-ilp32 target may be not perfect while enable fPIC
Date: Fri, 03 Jan 2020 19:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pinskia at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93119-4-bcHZ5rm5IA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93119-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00210.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93119
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Earnshaw from comment #3)
> I don't think that's right either. These are supposed to be machine
> addresses, not C pointers.
HMm, you might be right. I will take a look over the weekend to see what can
be done ...
>From gcc-bugs-return-664485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 20:05:23 2020
Return-Path: <gcc-bugs-return-664485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50924 invoked by alias); 3 Jan 2020 20: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 50879 invoked by uid 48); 3 Jan 2020 20:05:18 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93149] New: -fno-concepts silently ignored in c++2a mode
Date: Fri, 03 Jan 2020 20:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93149-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00211.txt.bz2
Content-length: 1095
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93149
Bug ID: 93149
Summary: -fno-concepts silently ignored in c++2a mode
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nathan at gcc dot gnu.org
Target Milestone: ---
In testing something out, I discovered that '-std=c++2a -fno-concepts' is
concept-enabled.
template<typename T>
requires (sizeof (T) > 1)
void frob (T);
nathans@devvm2772:306>./cc1plus conc.cc -quiet -std=c++2a
nathans@devvm2772:307>./cc1plus conc.cc -quiet -std=c++2a -fno-concepts
nathans@devvm2772:308>./cc1plus conc.cc -quiet -std=c++17 -fno-concepts
conc.cc:2:10: error: expected constructor, destructor, or type conversion
before '(' token
2 | requires (sizeof (T) > 1)
| ^
I expected either:
1) a warning telling me -fno-concepts had no effect with -std=c++2a
2) concepts disabled, in a similar manner to -fno-rtti and -fno-exceptions
>From gcc-bugs-return-664486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 20:12:37 2020
Return-Path: <gcc-bugs-return-664486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120401 invoked by alias); 3 Jan 2020 20:12: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 120319 invoked by uid 48); 3 Jan 2020 20:12:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 20: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.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed attachments.created
Message-ID: <bug-93141-4-xFjCYmVDhp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00212.txt.bz2
Content-length: 825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-03
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47589
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47589&action=edit
gcc10-pr93141.patch
Untested patch that improves double-word __builtin_add_overflow and thus also
the original testcase too. __builtin_sub_overflow is for next week.
>From gcc-bugs-return-664487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 20:27:20 2020
Return-Path: <gcc-bugs-return-664487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71408 invoked by alias); 3 Jan 2020 20: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 71358 invoked by uid 48); 3 Jan 2020 20:27:16 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Fri, 03 Jan 2020 20: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.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93141-4-FIX4sX4TB1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00213.txt.bz2
Content-length: 620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Just for reference here is aarch64 assembly for the loop:
.L4:
ldr x4, [x9, x5]
ldr x3, [x8, x5]
add x5, x5, 8
mul x6, x4, x3
umulh x3, x4, x3
adds x0, x6, x0
adcs x1, x3, x1
cinc x7, x7, cs
cmp x5, 16384
bne .L4
--- CUT ----
addcs might be faster than cinc on some cores but the difference is 1 cycle vs
2 cycles plus the latency would be hidden so it might not matter in the end.
>From gcc-bugs-return-664488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 20:40:03 2020
Return-Path: <gcc-bugs-return-664488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83000 invoked by alias); 3 Jan 2020 20:40: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 82862 invoked by uid 48); 3 Jan 2020 20:39:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 20:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93147-4-gFR3dEI1Z5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00214.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
Ever confirmed|0 |1
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Reduced:
struct A {
bool operator == (A) const { return true; }
};
struct B {
bool operator == (B) const { return true; }
};
struct Tuple_base : private A { };
struct Tuple_impl : Tuple_base, private B { };
struct Tuple : Tuple_impl { };
bool operator==(Tuple, Tuple) { return true; }
bool example(Tuple a, Tuple b)
{
return a == b;
}
>From gcc-bugs-return-664489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 20:41:41 2020
Return-Path: <gcc-bugs-return-664489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85248 invoked by alias); 3 Jan 2020 20: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 85181 invoked by uid 48); 3 Jan 2020 20:41:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-PDcRX1XtGb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00215.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Further reduced:
struct A {
bool operator == (A) const { return true; }
};
struct B {
bool operator == (B) const { return true; }
};
struct Tuple : private A, private B { };
bool operator==(Tuple, Tuple) { return true; }
bool example(Tuple a, Tuple b)
{
return a == b;
}
Clang does accept this, but EDG rejects it the same way as GCC:
"pr93147.cc", line 15: error: more than one operator "==" matches these
operands:
"Tuple::operator==" (ambiguous by inheritance)
operand types are: Tuple == Tuple
return a == b;
^
1 error detected in the compilation of "pr93147.cc".
>From gcc-bugs-return-664490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 20:45:38 2020
Return-Path: <gcc-bugs-return-664490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89489 invoked by alias); 3 Jan 2020 20:45: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 89439 invoked by uid 48); 3 Jan 2020 20:45:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93149] -fno-concepts silently ignored in c++2a mode
Date: Fri, 03 Jan 2020 20:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93149-4-LSbB4Q6DgW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93149-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93149-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00216.txt.bz2
Content-length: 856
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93149
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-03
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Since concepts have no runtime overhead I don't see any advantage to being able
to disable them.
Arguably, since the option is documented as enabling the Concepts TS, we could
claim that -fno-concepts disables the TS, but leaves C++20 concepts enabled :-)
A warning saying it has no effect would make sense though.
>From gcc-bugs-return-664491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 21:28:45 2020
Return-Path: <gcc-bugs-return-664491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39662 invoked by alias); 3 Jan 2020 21:28: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 39592 invoked by uid 48); 3 Jan 2020 21:28:41 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 21:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-MXf0adciJz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00217.txt.bz2
Content-length: 652
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #6 from Alexander Kondratskiy <kholdstare0.0 at gmail dot com> ---
Interesting. Some thoughts I had -
- If this is the correct behavior given the C++ standard, then that means the
tuple implementation in the library has to be fixed.
- If this is incorrect behavior, then something in the frontend needs to be
fixed regarding member function lookup. What's strange here is that if one of
the structs isn't empty, the problem goes away - it's more subtle than "the
compiler sees the equality operators". Could the empty-base optimization play a
role? Common initial sequence?
>From gcc-bugs-return-664492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 21:41:18 2020
Return-Path: <gcc-bugs-return-664492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75782 invoked by alias); 3 Jan 2020 21:41:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75727 invoked by uid 48); 3 Jan 2020 21:41:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-H9ZxWH43sJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00218.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Alexander Kondratskiy from comment #6)
> What's strange here is that if one
> of the structs isn't empty, the problem goes away - it's more subtle than
> "the compiler sees the equality operators". Could the empty-base
> optimization play a role? Common initial sequence?
That's not surprising at all. We only use derivation for tuple elements that
are empty types, otherwise they're just data members.
>From gcc-bugs-return-664493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 21:43:02 2020
Return-Path: <gcc-bugs-return-664493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77912 invoked by alias); 3 Jan 2020 21:43:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77846 invoked by uid 48); 3 Jan 2020 21:42:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 21:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-rq1wDW3pcu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00219.txt.bz2
Content-length: 828
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #7)
> (In reply to Alexander Kondratskiy from comment #6)
> > What's strange here is that if one
> > of the structs isn't empty, the problem goes away - it's more subtle than
> > "the compiler sees the equality operators". Could the empty-base
> > optimization play a role? Common initial sequence?
>
> That's not surprising at all. We only use derivation for tuple elements that
> are empty types, otherwise they're just data members.
i.e. it *is* as simple as "the compiler sees the equality operators". If the
elements are not empty, then the compiler doesn't see the operators, because
name lookup doesn't find members of members, only members of bases.
>From gcc-bugs-return-664494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 21:47:20 2020
Return-Path: <gcc-bugs-return-664494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80901 invoked by alias); 3 Jan 2020 21:47:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80848 invoked by uid 48); 3 Jan 2020 21:47:14 -0000
From: "kholdstare0.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93147] std::tuple of empty structs with member equality operators has ambiguous equality operator
Date: Fri, 03 Jan 2020 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kholdstare0.0 at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93147-4-fqwIgVUnCO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93147-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00220.txt.bz2
Content-length: 191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93147
--- Comment #9 from Alexander Kondratskiy <kholdstare0.0 at gmail dot com> ---
Ah, that explains everything. Thank you for clarifying.
>From gcc-bugs-return-664495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 22:11:34 2020
Return-Path: <gcc-bugs-return-664495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13909 invoked by alias); 3 Jan 2020 22:11:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13843 invoked by uid 55); 3 Jan 2020 22:11:30 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93033] [10 Regression] error: incorrect sharing of tree nodes
Date: Fri, 03 Jan 2020 22:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93033-4-QHTmHZjKg2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00221.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
--- Comment #11 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Fri Jan 3 22:10:56 2020
New Revision: 279871
URL: https://gcc.gnu.org/viewcvs?rev=279871&root=gcc&view=rev
Log:
PR c++/93033 - incorrect tree node sharing with array init.
The split_nonconstant_init piece is the only one necessary to fix the
testcase, but it occurred to me that we might as well not split when
-fno-exceptions.
* typeck2.c (split_nonconstant_init): Unshare non-decl.
* cp-gimplify.c (cp_gimplify_init_expr): Only split if -fexceptions.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/initlist-array9.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-gimplify.c
trunk/gcc/cp/typeck2.c
>From gcc-bugs-return-664496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 03 22:46:59 2020
Return-Path: <gcc-bugs-return-664496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83427 invoked by alias); 3 Jan 2020 22:46:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83335 invoked by uid 48); 3 Jan 2020 22:46:54 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93131] ((a&8) == 8) && ((a&2) == 2) is not optimized to (a&(8|2)) == (8|2)
Date: Fri, 03 Jan 2020 22:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-93131-4-8stJNt2ANi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93131-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00222.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93131
--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> Otherwise it LGTM, so please post it this week, I'd really like to see it in
> GCC 10.
I writing the testcases right now. There will be at least 25 of them. One
executable. Writing testcases take longer than writing the original patch due
to all of the combos that need to be tested (using macros to simplify things
though).
>From gcc-bugs-return-664497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 08:20:28 2020
Return-Path: <gcc-bugs-return-664497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12605 invoked by alias); 4 Jan 2020 08:20: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 12552 invoked by uid 55); 4 Jan 2020 08:20:23 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91640] [9/10 Regression] ICE: gimplification failed (contiguous expr)
Date: Sat, 04 Jan 2020 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91640-4-d1vUk4ILj2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00223.txt.bz2
Content-length: 765
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91640
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Sat Jan 4 08:19:51 2020
New Revision: 279879
URL: https://gcc.gnu.org/viewcvs?rev=279879&root=gcc&view=rev
Log:
Fortran] PR91640 – Fix call to contiguous dummy
PR fortran/91640
* trans-expr.c (gfc_conv_procedure_call): Avoid copy-out for
nonvariable
arguments to contiguous dummy args. Avoid re-checking whether fsym is
NULL.
PR fortran/91640
* gfortran.dg/contiguous_10.f90: New.
Added:
trunk/gcc/testsuite/gfortran.dg/contiguous_10.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-expr.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 08:30:16 2020
Return-Path: <gcc-bugs-return-664498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26680 invoked by alias); 4 Jan 2020 08:30: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 22209 invoked by uid 48); 4 Jan 2020 08:30:01 -0000
From: "fanael4 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87455] sse_packed_single_insn_optimal is suboptimal on Zen
Date: Sat, 04 Jan 2020 08: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: fanael4 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-87455-4-gQYJ54u4H0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87455-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87455-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00224.txt.bz2
Content-length: 247
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87455
--- Comment #6 from Fanael <fanael4 at gmail dot com> ---
Any hope of getting this fixed in GCC 10? It should just be a matter of
removing Zen[12] from X86_TUNE_SSE_PACKED_SINGLE_INSN_OPTIMAL.
>From gcc-bugs-return-664499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 09:36:36 2020
Return-Path: <gcc-bugs-return-664499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65199 invoked by alias); 4 Jan 2020 09:36:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65170 invoked by uid 48); 4 Jan 2020 09:36:32 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93150] New: (A&N) == CST1 &( ((A&M)==CST2) | ((A&O)==CST3) ) is not simplified
Date: Sat, 04 Jan 2020 09:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93150-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00225.txt.bz2
Content-length: 1033
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93150
Bug ID: 93150
Summary: (A&N) == CST1 &( ((A&M)==CST2) | ((A&O)==CST3) ) is
not simplified
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
(x&N) == CST1 & ( ((x&M)==CST2) | ((x&O)==CST3) )
Should be simplified into:
((x&(N|M)) == (CST1|CST2)) | ((x&(N|O)==(CST1|CST3))
Note this can be done for all &/| and ==/!= .
That is:
(for bitop1 (bit_and bit_or)
bitop2 (bit_or bit_and)
(for cmp (eq ne)
(simplify
(bitop1:c
(cmp (bit_and @0 INTEGER_CST@N) INTEGER_CST@CST1)
(bitop2
(cmp (bit_and @0 INTEGER_CST@N) INTEGER_CST@CST2)
(cmp (bit_and @0 INTEGER_CST@N) INTEGER_CST@CST3)))
....
>From gcc-bugs-return-664500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 10:12:28 2020
Return-Path: <gcc-bugs-return-664500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117899 invoked by alias); 4 Jan 2020 10:12:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117849 invoked by uid 48); 4 Jan 2020 10:12:23 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68950] [fortran] gfc_format_decoder cannot handle %qE
Date: Sat, 04 Jan 2020 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: minor
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68950-4-zQTjyFOeSH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00226.txt.bz2
Content-length: 977
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68950
--- Comment #14 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #13)
> I believe this has been fixed properly by the patch for PR fortran/79886 in
> r246203 by adding the following to gcc/fortran/error.c's gfc_format_decoder:
>
> default:
> - return false;
> + /* Fall through info the middle-end decoder, as e.g. stor-layout.c
> + etc. diagnostics can use the FE printer while the FE is still
> + active. */
> + return default_tree_printer (pp, text, spec, precision, wide,
> + set_locus, hash);
>
> HENCE: Closed as FIXED.
>
> @Tom: Sorry for now following up to your RFC patch of 2015 and two-follow-up
> pings in 2016 and 2018. — I strongly believe the mentioned patch by Jakub
> fixes the issue properly; if you disagree, feel free to reopen this PR.
Ack, thanks for following up :)
>From gcc-bugs-return-664503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 10:33:21 2020
Return-Path: <gcc-bugs-return-664503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18865 invoked by alias); 4 Jan 2020 10:33:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18563 invoked by uid 48); 4 Jan 2020 10:33:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88323] implement C++20 language features.
Date: Sat, 04 Jan 2020 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88323-4-5roHB4KoMl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00229.txt.bz2
Content-length: 456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
Bug 88323 depends on bug 91369, which changed state.
Bug 91369 Summary: Implement P0784R7: constexpr new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
>From gcc-bugs-return-664502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 10:33:21 2020
Return-Path: <gcc-bugs-return-664502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18803 invoked by alias); 4 Jan 2020 10:33:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18537 invoked by uid 48); 4 Jan 2020 10:33:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/55004] [meta-bug] constexpr issues
Date: Sat, 04 Jan 2020 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-55004-4-twlUJXOaCY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-55004-4@http.gcc.gnu.org/bugzilla/>
References: <bug-55004-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00228.txt.bz2
Content-length: 456
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=55004
Bug 55004 depends on bug 91369, which changed state.
Bug 91369 Summary: Implement P0784R7: constexpr new
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
>From gcc-bugs-return-664501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 10:33:19 2020
Return-Path: <gcc-bugs-return-664501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18610 invoked by alias); 4 Jan 2020 10:33: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 18476 invoked by uid 48); 4 Jan 2020 10:33:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Sat, 04 Jan 2020 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
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 resolution
Message-ID: <bug-91369-4-p4qCU6cj4u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00227.txt.bz2
Content-length: 1863
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #26 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The problem is the constexpr call cache we have, disabling it altogether like:
--- gcc/cp/constexpr.c 2020-01-04 11:19:50.585697766 +0100
+++ gcc/cp/constexpr.c 2020-01-04 11:18:42.000000000 +0100
@@ -2426,7 +2426,7 @@ cxx_eval_call_expression (const constexp
else if (!result)
result = void_node;
if (entry)
- entry->result = result;
+ entry->result = /*result*/error_mark_node;
}
/* The result of a constexpr function must be completely initialized.
fixes it.
Before the introduction of constexpr new/delete it was just fine to cache calls
that way, a constexpr call of the same constexpr function with the same
constant arguments with the same state of manifestly constant evaluation could
be reused.
I'm afraid that is no longer the case with constexpr new/delete, so I think we
need to avoid the caching if the call allocates something and doesn't
deallocate it before returning, or if it deallocates something it hasn't
allocated, because the call in that case isn't really stateless for the
constexpr evaluation.
Checking for the former could be easy, remember before the call how the length
of ctx->global->heap_vars and after the call, for any newly added elts verify
if they were all deallocated. To detect the deallocation without allocation
inside of the call we could perhaps add a counter for the deallocations and
compare that counter to the number of the allocations.
>From gcc-bugs-return-664504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 10:40:24 2020
Return-Path: <gcc-bugs-return-664504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49437 invoked by alias); 4 Jan 2020 10:40: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 49382 invoked by uid 48); 4 Jan 2020 10:40:19 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91640] [9/10 Regression] ICE: gimplification failed (contiguous expr)
Date: Sat, 04 Jan 2020 10:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-91640-4-G9fwhkb6l2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00230.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91640
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|tkoenig at gcc dot gnu.org |unassigned at gcc dot gnu.org
>From gcc-bugs-return-664505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 11:40:36 2020
Return-Path: <gcc-bugs-return-664505-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124263 invoked by alias); 4 Jan 2020 11: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 124209 invoked by uid 48); 4 Jan 2020 11:40:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Sat, 04 Jan 2020 11: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-91369-4-bBaexjFxoZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00231.txt.bz2
Content-length: 259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
--- Comment #27 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47590
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47590&action=edit
gcc10-pr91369-2.patch
Untested patch.
>From gcc-bugs-return-664506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 12:16:09 2020
Return-Path: <gcc-bugs-return-664506-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43486 invoked by alias); 4 Jan 2020 12: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 43360 invoked by uid 48); 4 Jan 2020 12:16:03 -0000
From: "karen.arutyunov at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93151] New: system_error header fails to compile with -D_XOPEN_SOURCE`0
Date: Sat, 04 Jan 2020 12:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: karen.arutyunov 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-93151-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00232.txt.bz2
Content-length: 2446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93151
Bug ID: 93151
Summary: system_error header fails to compile with
-D_XOPEN_SOURCE=600
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: karen.arutyunov at gmail dot com
Target Milestone: ---
Trying to build ICU 65.1 on macOS 10.15.2 with g++ 9.2.0 (Homebrew GCC 9.2.0_2)
ends up with the error:
In file included from
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/system_error:39,
from
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/bits/std_mutex.h:39,
from
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/condition_variable:39,
from ../../common/umutex.h:24,
from ../../common/putil.cpp:68:
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/x86_64-apple-darwin19/bits/error_constants.h:135:24:
error: 'EOWNERDEAD' was not declared in this scope
135 | owner_dead = EOWNERDEAD,
| ^~~~~~~~~~
/usr/local/Cellar/gcc/9.2.0_1/include/c++/9.2.0/x86_64-apple-darwin19/bits/error_constants.h:151:34:
error: 'ENOTRECOVERABLE' was not declared in this scope
151 | state_not_recoverable = ENOTRECOVERABLE,
| ^~~~~~~~~~~~~~~
The issue seems to relate to libstdc++ headers and pops up if a program defines
_XOPEN_SOURCE as 600 and includes the system_error header. It can be reproduced
with the following commands:
% cat <<EOF >test.cxx
#include <system_error>
int main (int argc, char* argv[])
{
}
EOF
% g++-9 test.cxx
% g++-9 -D_XOPEN_SOURCE=600 test.cxx
In file included from
/usr/local/Cellar/gcc/9.2.0_2/include/c++/9.2.0/system_error:39,
from test.cxx:1:
/usr/local/Cellar/gcc/9.2.0_2/include/c++/9.2.0/x86_64-apple-darwin19/bits/error_constants.h:135:24:
error: 'EOWNERDEAD' was not declared in this scope
135 | owner_dead = EOWNERDEAD,
| ^~~~~~~~~~
/usr/local/Cellar/gcc/9.2.0_2/include/c++/9.2.0/x86_64-apple-darwin19/bits/error_constants.h:151:34:
error: 'ENOTRECOVERABLE' was not declared in this scope
151 | state_not_recoverable = ENOTRECOVERABLE,
| ^~~~~~~~~~~~~~~
>From gcc-bugs-return-664507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 12:17:27 2020
Return-Path: <gcc-bugs-return-664507-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45935 invoked by alias); 4 Jan 2020 12:17: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 45878 invoked by uid 48); 4 Jan 2020 12:17:23 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44960] non-array used as an array, identified as an external function
Date: Sat, 04 Jan 2020 12:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-44960-4-geHrSJlfxy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00233.txt.bz2
Content-length: 382
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44960
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
>From gcc-bugs-return-664508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 13:57:31 2020
Return-Path: <gcc-bugs-return-664508-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78939 invoked by alias); 4 Jan 2020 13:57:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74142 invoked by uid 48); 4 Jan 2020 13:57:27 -0000
From: "js at alien8 dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92086] Provide way to avoid saving callee-saved registers in functions without callers
Date: Sat, 04 Jan 2020 13:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: js at alien8 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: cc
Message-ID: <bug-92086-4-Cbl6RCtfYY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92086-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92086-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00234.txt.bz2
Content-length: 693
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92086
Julian Stecklina <js at alien8 dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |js at alien8 dot de
--- Comment #6 from Julian Stecklina <js at alien8 dot de> ---
I also see this suboptimal behavior in my C++ RISC-V embedded program with
functions marked [[noreturn]] (and compiling with -fno-exceptions). The
prologue saves callee-saved registers even though this will never be useful.
This both wastes precious stack and ROM space.
I'd love to have a compiler option to turn this off.
>From gcc-bugs-return-664509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:16:45 2020
Return-Path: <gcc-bugs-return-664509-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93803 invoked by alias); 4 Jan 2020 17:16: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 93780 invoked by uid 48); 4 Jan 2020 17:16:40 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93152] New: Order of template args in decl makes std::invocable fail
Date: Sat, 04 Jan 2020 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00235.txt.bz2
Content-length: 6038
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
Bug ID: 93152
Summary: Order of template args in decl makes std::invocable
fail
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: db0451 at gmail dot com
Target Milestone: ---
This is as far as I've yet reduced this from my own project, compiling with
`g++-10 (Debian 10-20191217-1) 10.0.0 20191217 (experimental) [trunk revision
279456]`
From the comments below:
// Putting Result as 1st template argument makes derived_from<WeirdBase> fail,
// but putting derived_from<WeirdBase> 1st lets it compile without problem!
// If you [constrain via static_assert] instead, both template arg orders
work!!
The failure occurs like so; it seems that somehow g++ concludes the wrong base
for derived_from, and as mentioned that seems to be caused by template arg
order
>>>
test3.cpp: In function ‘int main()’:
test3.cpp:48:33: error: no match for call to ‘(const
make_lambda(MemFun<WeirdSub1, Result, Args ...>) [with Result = void; WeirdSub1
= WeirdSub; Args = {}; MemFun<WeirdSub1, Result, Args ...> = void
(WeirdSub::*)()]::<lambda(auto:1&&, auto:2&&)>) (WeirdSub, OtherSub)’
48 | lambda( WeirdSub{}, OtherSub{} );
| ^
test3.cpp:28:9: note: candidate: ‘make_lambda(MemFun<WeirdSub1, Result, Args
...>) [with Result = void; WeirdSub1 = WeirdSub; Args = {}; MemFun<WeirdSub1,
Result, Args ...> = void (WeirdSub::*)()]::<lambda(auto:1&&, auto:2&&)> [with
auto:1 = WeirdSub; auto:2 = OtherSub]’
28 | return []
| ^
test3.cpp:28:9: note: constraints not satisfied
In file included from test3.cpp:1:
/usr/include/c++/10/concepts: In instantiation of
‘make_lambda(MemFun<WeirdSub1, Result, Args ...>) [with Result = void;
WeirdSub1 = WeirdSub; Args = {}; MemFun<WeirdSub1, Result, Args ...> = void
(WeirdSub::*)()]::<lambda(auto:1&&, auto:2&&)> [with auto:1 = WeirdSub; auto:2
= OtherSub]’:
test3.cpp:48:33: required from here
/usr/include/c++/10/concepts:67:13: required for the satisfaction of
‘derived_from<auto:1, OtherSub>’
/usr/include/c++/10/concepts:67:28: note: ‘OtherSub’ is not a base of
‘WeirdSub’
67 | concept derived_from = __is_base_of(_Base, _Derived)
>>>
Additionally, if you make the lambda instead take only derived_from<WeirdSub1>,
and dutifully pass only that... then an ICE occurs instead. I'll probably file
a 2nd, simpler MCVE for that - unless it turns out to have the same root cause.
>>>
test3.cpp: In function ‘int main()’:
test3.cpp:48:21: internal compiler error: Segmentation fault
48 | lambda( WeirdSub{} );//, OtherSub{} );
| ^
0xbecf3f crash_signal
../../src/gcc/toplev.c:328
0x7fb9a36f30ff ???
/build/glibc-dEjGnz/glibc-2.29/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x703e96 tsubst(tree_node*, tree_node*, int, tree_node*)
../../src/gcc/cp/pt.c:15083
0x707ac6 tsubst_template_args(tree_node*, tree_node*, int, tree_node*)
../../src/gcc/cp/pt.c:13099
0x625fa5 normalize_concept_check
../../src/gcc/cp/constraint.cc:685
0x625fa5 normalize_atom
../../src/gcc/cp/constraint.cc:719
0x625fa5 normalize_expression
../../src/gcc/cp/constraint.cc:748
0x6263da get_normalized_constraints
../../src/gcc/cp/constraint.cc:760
0x6263da get_normalized_constraints_from_info
../../src/gcc/cp/constraint.cc:778
0x629dfd get_normalized_constraints_from_decl
../../src/gcc/cp/constraint.cc:841
0x62a23a satisfy_declaration_constraints
../../src/gcc/cp/constraint.cc:880
0x62a578 constraint_satisfaction_value
../../src/gcc/cp/constraint.cc:2709
0x62a578 constraints_satisfied_p(tree_node*)
../../src/gcc/cp/constraint.cc:2730
0x5f7f11 add_function_candidate
../../src/gcc/cp/call.c:2280
0x5fa28d add_template_candidate_real
../../src/gcc/cp/call.c:3438
0x5fa7c4 add_template_candidate
../../src/gcc/cp/call.c:3479
0x5fa7c4 add_candidates
../../src/gcc/cp/call.c:5805
0x5ff654 add_candidates
../../src/gcc/cp/call.c:5720
0x5ff654 build_op_call_1
../../src/gcc/cp/call.c:4768
0x5ff654 build_op_call(tree_node*, vec<tree_node*, va_gc, vl_embed>**, int)
../../src/gcc/cp/call.c:4864
>>>
***
```
#include <concepts>
#include <type_traits>
struct WeirdBase {};
struct WeirdSub: WeirdBase {
void mem_fun() {}
};
struct OtherBase {};
struct OtherSub: OtherBase {};
template <typename Object, typename Result, typename... Args>
using MemFun = Result (Object::*)(Args...);
// Putting Result as 1st template argument makes derived_from<WeirdBase> fail,
#if 1
template <typename Result, std::derived_from<WeirdBase> WeirdSub1,
typename... Args>
// but putting derived_from<WeirdBase> 1st lets it compile without problem!
#else
template <std::derived_from<WeirdBase> WeirdSub1,
typename Result, typename... Args>
#endif
auto
make_lambda( MemFun<WeirdSub1, Result, Args...> )
{
return []
#if 1
(std::derived_from<WeirdSub1> auto&&,
std::derived_from<OtherBase> auto&&)
{
// If you do the following instead, both template arg orders work!!
#else
(std::derived_from<WeirdBase> auto&& weird,
std::derived_from<OtherBase> auto&&)
{
using WeirdSub2 = std::remove_reference_t< decltype(weird) >;
static_assert( std::derived_from<WeirdSub2, WeirdSub1> );
#endif
};
}
auto
main() -> int
{
auto const lambda = make_lambda(&WeirdSub::mem_fun);
lambda( WeirdSub{}, OtherSub{} );
return 0;
}
```
>From gcc-bugs-return-664510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:22:07 2020
Return-Path: <gcc-bugs-return-664510-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98014 invoked by alias); 4 Jan 2020 17:22:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97912 invoked by uid 48); 4 Jan 2020 17:22:02 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93152] Order of template arguments in declaration makes std::derived_from fail due to expecting wrong base class
Date: Sat, 04 Jan 2020 17:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93152-4-HnFmAs6zG1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00236.txt.bz2
Content-length: 1138
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
--- Comment #1 from DB <db0451 at gmail dot com> ---
I believe this is also probably related to the fact that the WeirdSub1 template
argument is coming via a pointer-to-member function, although I haven't 100%
narrowed that down yet, I don't think.
The mentioned ICE can be minimised further, but this again works if the
template argument orders are swapped, so I think/hope it might have the same
root cause.
```#include <concepts>
struct WeirdBase {};
struct WeirdSub: WeirdBase {
void mem_fun() {}
};
template <typename Object, typename Result, typename... Args>
using MemFun = Result (Object::*)(Args...);
#if 1 // fails
template <typename Result, std::derived_from<WeirdBase> WeirdSub1,
#else // works
template <std::derived_from<WeirdBase> WeirdSub1, typename Result,
#endif
typename... Args>
auto
make_lambda( MemFun<WeirdSub1, Result, Args...> )
{
return [](std::derived_from<WeirdSub1> auto&&){};
}
auto
main() -> int
{
auto const lambda = make_lambda(&WeirdSub::mem_fun);
lambda( WeirdSub{} );
return 0;
}
```
>From gcc-bugs-return-664511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:24:56 2020
Return-Path: <gcc-bugs-return-664511-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100037 invoked by alias); 4 Jan 2020 17:24: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 99985 invoked by uid 48); 4 Jan 2020 17:24:48 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93152] Order of template args in decl makes derived_from expect wrong base / causes ICE
Date: Sat, 04 Jan 2020 17:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93152-4-pTKND7o4Qg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00237.txt.bz2
Content-length: 270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
--- Comment #2 from DB <db0451 at gmail dot com> ---
another reduction: the Args... are not required in the templates (since the
member function takes none), and the same failure/success patterns occur either
way.
>From gcc-bugs-return-664512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:29:52 2020
Return-Path: <gcc-bugs-return-664512-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103018 invoked by alias); 4 Jan 2020 17:29:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102978 invoked by uid 48); 4 Jan 2020 17:29:47 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93153] New: Wrong optimization while devirtualizing after placement new over local var
Date: Sat, 04 Jan 2020 17:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93153-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00238.txt.bz2
Content-length: 1378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93153
Bug ID: 93153
Summary: Wrong optimization while devirtualizing after
placement new over local var
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ch3root at openwall dot com
Target Milestone: ---
It seems gcc doesn't account for a possible type change of local variables due
to storage reuse while devirtualizing method calls (seems to happen in ccp1):
----------------------------------------------------------------------
#include <stdio.h>
#include <new>
struct Y {
virtual void foo() { puts("Y"); }
};
struct X : Y {
virtual void foo() { puts("X"); }
};
static_assert(sizeof(X) == sizeof(Y));
int main()
{
Y y;
Y *p = new (&y) X;
p->foo();
}
----------------------------------------------------------------------
$ g++ -std=c++2a -pedantic -Wall -Wextra test.cc && ./a.out
X
$ g++ -std=c++2a -pedantic -Wall -Wextra -O3 test.cc && ./a.out
Y
----------------------------------------------------------------------
gcc x86-64 version: g++ (GCC) 10.0.0 20200104 (experimental)
----------------------------------------------------------------------
>From gcc-bugs-return-664513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:32:28 2020
Return-Path: <gcc-bugs-return-664513-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105165 invoked by alias); 4 Jan 2020 17:32:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105114 invoked by uid 48); 4 Jan 2020 17:32:24 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93050] throw within constructor initialisation list causes invalid free in destructor
Date: Sat, 04 Jan 2020 17:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93050-4-16r1axF1C1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93050-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93050-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00239.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93050
--- Comment #1 from DB <db0451 at gmail dot com> ---
This bug does not seem to occur with
g++ (Debian 9.2.1-21) 9.2.1 20191130
so either it was fixed between 9.2.0 and 9.2.1, or something peculiar to
MSYS2/MinGW64/Windows is causing it.
>From gcc-bugs-return-664514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:39:19 2020
Return-Path: <gcc-bugs-return-664514-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111218 invoked by alias); 4 Jan 2020 17:39:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110498 invoked by uid 48); 4 Jan 2020 17:39:13 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93152] Order of template args in decl makes derived_from expect wrong base / causes ICE
Date: Sat, 04 Jan 2020 17:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93152-4-Kr2wCBxctw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00240.txt.bz2
Content-length: 2705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
--- Comment #3 from DB <db0451 at gmail dot com> ---
The pointer-to-member-function and template argument deduction through it is
not required; rather, simply the presence of any other template argument in the
1st position is sufficient:
```
#include <concepts>
#include <type_traits>
struct WeirdBase {};
struct WeirdSub: WeirdBase {};
struct OtherBase {};
struct OtherSub: OtherBase {};
// Putting Result as 1st template argument makes derived_from<WeirdBase> fail,
#if 1
template <typename Foo, std::derived_from<WeirdBase> WeirdSub1>
// but putting derived_from<WeirdBase> 1st lets it compile without problem!
#else
template <std::derived_from<WeirdBase> WeirdSub1, typename Result>
#endif
auto
make_lambda()
{
return []
#if 1
(std::derived_from<WeirdSub1> auto&&,
std::derived_from<OtherBase> auto&&)
{
// If you do the following instead, both template arg orders work!!
#else
(std::derived_from<WeirdBase> auto&& weird,
std::derived_from<OtherBase> auto&&)
{
using WeirdSub2 = std::remove_reference_t< decltype(weird) >;
static_assert( std::derived_from<WeirdSub2, WeirdSub1> );
#endif
};
}
auto
main() -> int
{
#if 1
auto const lambda = make_lambda<int, WeirdSub>();
#else
auto const lambda = make_lambda<WeirdSub, int>();
#endif
lambda( WeirdSub{}, OtherSub{} );
return 0;
}
```
>>>
test3.cpp: In function ‘int main()’:
test3.cpp:44:33: error: no match for call to ‘(const make_lambda() [with Foo =
int; WeirdSub1 = WeirdSub]::<lambda(auto:1&&, auto:2&&)>) (WeirdSub, OtherSub)’
44 | lambda( WeirdSub{}, OtherSub{} );
| ^
test3.cpp:20:9: note: candidate: ‘make_lambda() [with Foo = int; WeirdSub1 =
WeirdSub]::<lambda(auto:1&&, auto:2&&)> [with auto:1 = WeirdSub; auto:2 =
OtherSub]’
20 | return []
| ^
test3.cpp:20:9: note: constraints not satisfied
In file included from test3.cpp:1:
/usr/include/c++/10/concepts: In instantiation of ‘make_lambda() [with Foo =
int; WeirdSub1 = WeirdSub]::<lambda(auto:1&&, auto:2&&)> [with auto:1 =
WeirdSub; auto:2 = OtherSub]’:
test3.cpp:44:33: required from here
/usr/include/c++/10/concepts:67:13: required for the satisfaction of
‘derived_from<auto:1, OtherSub>’
/usr/include/c++/10/concepts:67:28: note: ‘OtherSub’ is not a base of
‘WeirdSub’
67 | concept derived_from = __is_base_of(_Base, _Derived)
>>>
>From gcc-bugs-return-664515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 17:41:19 2020
Return-Path: <gcc-bugs-return-664515-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112827 invoked by alias); 4 Jan 2020 17:41: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 112795 invoked by uid 48); 4 Jan 2020 17:41:14 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93152] Order of template args in decl makes derived_from expect wrong base / causes ICE
Date: Sat, 04 Jan 2020 17:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93152-4-lHYOgzHSQy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00241.txt.bz2
Content-length: 2400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
--- Comment #4 from DB <db0451 at gmail dot com> ---
Simplifying further, by getting rid of the Other structs/arguments, we get:
```
#include <concepts>
#include <type_traits>
struct WeirdBase {};
struct WeirdSub: WeirdBase {};
template <typename Foo, std::derived_from<WeirdBase> WeirdSub1>
auto
make_lambda()
{
return [](std::derived_from<WeirdSub1> auto&&){};
}
auto
main() -> int
{
auto const lambda = make_lambda<int, WeirdSub>();
lambda( WeirdSub{} );
return 0;
}
```
...which again gives...
>>>
test3.cpp: In function ‘int main()’:
test3.cpp:18:21: internal compiler error: Segmentation fault
18 | lambda( WeirdSub{} );
| ^
0xbecf3f crash_signal
../../src/gcc/toplev.c:328
0x7efcb8d0c0ff ???
/build/glibc-dEjGnz/glibc-2.29/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x703e96 tsubst(tree_node*, tree_node*, int, tree_node*)
../../src/gcc/cp/pt.c:15083
0x707ac6 tsubst_template_args(tree_node*, tree_node*, int, tree_node*)
../../src/gcc/cp/pt.c:13099
0x625fa5 normalize_concept_check
../../src/gcc/cp/constraint.cc:685
0x625fa5 normalize_atom
../../src/gcc/cp/constraint.cc:719
0x625fa5 normalize_expression
../../src/gcc/cp/constraint.cc:748
0x6263da get_normalized_constraints
../../src/gcc/cp/constraint.cc:760
0x6263da get_normalized_constraints_from_info
../../src/gcc/cp/constraint.cc:778
0x629dfd get_normalized_constraints_from_decl
../../src/gcc/cp/constraint.cc:841
0x62a23a satisfy_declaration_constraints
../../src/gcc/cp/constraint.cc:880
0x62a578 constraint_satisfaction_value
../../src/gcc/cp/constraint.cc:2709
0x62a578 constraints_satisfied_p(tree_node*)
../../src/gcc/cp/constraint.cc:2730
0x5f7f11 add_function_candidate
../../src/gcc/cp/call.c:2280
0x5fa28d add_template_candidate_real
../../src/gcc/cp/call.c:3438
0x5fa7c4 add_template_candidate
../../src/gcc/cp/call.c:3479
0x5fa7c4 add_candidates
../../src/gcc/cp/call.c:5805
0x5ff654 add_candidates
../../src/gcc/cp/call.c:5720
0x5ff654 build_op_call_1
../../src/gcc/cp/call.c:4768
0x5ff654 build_op_call(tree_node*, vec<tree_node*, va_gc, vl_embed>**, int)
../../src/gcc/cp/call.c:4864
>>>
>From gcc-bugs-return-664516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 19:07:31 2020
Return-Path: <gcc-bugs-return-664516-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35215 invoked by alias); 4 Jan 2020 19:07:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35165 invoked by uid 48); 4 Jan 2020 19:07:26 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93154] New: can't constrain captured functions to be invocable with lambda arg - unknown "constraints not satisfied"
Date: Sat, 04 Jan 2020 19:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93154-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00242.txt.bz2
Content-length: 1878
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93154
Bug ID: 93154
Summary: can't constrain captured functions to be invocable
with lambda arg - unknown "constraints not satisfied"
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: db0451 at gmail dot com
Target Milestone: ---
Surely the below should work? I'm currently trying to go overboard with
declaring constraints, and that `requires` clause - while perhaps a bit
superfluous - seems totally correct... right?
However, it doesn't compile, citing "constraints not satisfied" - and yet
notably not bothering to mention WHICH constraint supposedly has the problem!
g++-10 (Debian 10-20191217-1) 10.0.0 20191217 (experimental) [trunk revision
279456]
```
#include <concepts>
void f1(int) {}
template <typename... Fs> requires (sizeof...(Fs) > 0)
auto
make_lambda(Fs... fs)
{
return [fs...]
<typename Arg>
requires (std::invocable<Fs, Arg> && ...)
(Arg a)
{
(fs(a), ...);
};
}
auto
main() -> int
{
auto const lambda = make_lambda(&f1);
lambda(42);
return 0;
}
```
...results in the error:
>>>
test5.cpp: In function ‘int main()’:
test5.cpp:22:11: error: no match for call to ‘(const make_lambda(Fs ...) [with
Fs = {void (*)(int)}]::<lambda(Arg)>) (int)’
22 | lambda(42);
| ^
test5.cpp:9:9: note: candidate: ‘make_lambda(Fs ...) [with Fs = {void
(*)(int)}]::<lambda(Arg)> [with Arg = int]’
9 | return [fs...]
| ^
test5.cpp:9:9: note: constraints not satisfied
>>>
preprocessed source:
>From gcc-bugs-return-664517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 19:08:20 2020
Return-Path: <gcc-bugs-return-664517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36130 invoked by alias); 4 Jan 2020 19:08: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 36103 invoked by uid 48); 4 Jan 2020 19:08:16 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93154] can't constrain captured functions to be invocable with lambda arg - unknown "constraints not satisfied"
Date: Sat, 04 Jan 2020 19:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93154-4-3dRhM4ORcR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93154-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93154-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00243.txt.bz2
Content-length: 248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93154
--- Comment #1 from DB <db0451 at gmail dot com> ---
> preprocessed source:
Ah, whoops. It's not interesting anyway, but maybe I just don't remember how to
do it right... I just passed `-E`.
>From gcc-bugs-return-664518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 19:17:48 2020
Return-Path: <gcc-bugs-return-664518-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43897 invoked by alias); 4 Jan 2020 19:17:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43859 invoked by uid 48); 4 Jan 2020 19:17:43 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93154] can't constrain captured functions to be invocable with lambda arg - unknown "constraints not satisfied"
Date: Sat, 04 Jan 2020 19:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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-93154-4-bk8tSLLvFT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93154-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93154-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00244.txt.bz2
Content-length: 1863
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93154
--- Comment #2 from DB <db0451 at gmail dot com> ---
A reduced version, without a variadic pack of functions...
```
#include <concepts>
void f1(int) {}
template <typename F>
auto
make_lambda(F f)
{
return [f] <typename Arg>
requires std::invocable<F, Arg>
(Arg a)
{
f(a);
};
}
auto
main() -> int
{
auto const lambda = make_lambda(&f1);
lambda(42);
return 0;
}
```
...gives an error that is now specific, but which still seems clearly wrong:
>>>
test5.cpp: In function ‘int main()’:
test5.cpp:19:11: error: no match for call to ‘(const make_lambda(F) [with F =
void (*)(int)]::<lambda(Arg)>) (int)’
19 | lambda(42);
| ^
test5.cpp:9:9: note: candidate: ‘make_lambda(F) [with F = void
(*)(int)]::<lambda(Arg)> [with Arg = int]’
9 | return [f] <typename Arg> requires std::invocable<F, Arg> (Arg a)
| ^
test5.cpp:9:9: note: constraints not satisfied
In file included from test5.cpp:1:
/usr/include/c++/10/concepts: In instantiation of ‘make_lambda(F) [with F =
void (*)(int)]::<lambda(Arg)> [with Arg = int]’:
test5.cpp:19:11: required from here
/usr/include/c++/10/concepts:344:13: required for the satisfaction of
‘invocable<int, Arg>’
/usr/include/c++/10/concepts:344:25: note: the expression ‘is_invocable_v<_Fn,
_Args ...>’ evaluated to ‘false’
344 | concept invocable = is_invocable_v<_Fn, _Args...>;
>>>
It looks like the compiler is mixing up the template arguments of the outer
function and the inner lambda.
In that sense, this might have the same root cause as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
>From gcc-bugs-return-664519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 19:20:22 2020
Return-Path: <gcc-bugs-return-664519-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46047 invoked by alias); 4 Jan 2020 19:20: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 45983 invoked by uid 48); 4 Jan 2020 19:20:17 -0000
From: "db0451 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93152] Order of template args in decl makes derived_from expect wrong base / causes ICE
Date: Sat, 04 Jan 2020 19:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: db0451 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: see_also
Message-ID: <bug-93152-4-9n6FrKvPYD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93152-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00245.txt.bz2
Content-length: 2287
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93152
DB <db0451 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=93154
--- Comment #5 from DB <db0451 at gmail dot com> ---
This might have the same root cause as 93154, as in both cases, it looks like
the compiler is mixing up the template arguments of the outer function and the
inner lambda.
Here, we are told that "‘OtherSub’ is not a base of ‘WeirdSub’", despite that
we never asked the compiler to make that constraint.
and from 93154:
```
#include <concepts>
void f1(int) {}
template <typename F>
auto
make_lambda(F f)
{
return [f] <typename Arg>
requires std::invocable<F, Arg>
(Arg a)
{
f(a);
};
}
auto
main() -> int
{
auto const lambda = make_lambda(&f1);
lambda(42);
return 0;
}
```
...which somehow ends up with the compiler trying to check whether `int` is
`std::invocable`!
>>>
test5.cpp: In function ‘int main()’:
test5.cpp:19:11: error: no match for call to ‘(const make_lambda(F) [with F =
void (*)(int)]::<lambda(Arg)>) (int)’
19 | lambda(42);
| ^
test5.cpp:9:9: note: candidate: ‘make_lambda(F) [with F = void
(*)(int)]::<lambda(Arg)> [with Arg = int]’
9 | return [f] <typename Arg> requires std::invocable<F, Arg> (Arg a)
| ^
test5.cpp:9:9: note: constraints not satisfied
In file included from test5.cpp:1:
/usr/include/c++/10/concepts: In instantiation of ‘make_lambda(F) [with F =
void (*)(int)]::<lambda(Arg)> [with Arg = int]’:
test5.cpp:19:11: required from here
/usr/include/c++/10/concepts:344:13: required for the satisfaction of
‘invocable<int, Arg>’
/usr/include/c++/10/concepts:344:25: note: the expression ‘is_invocable_v<_Fn,
_Args ...>’ evaluated to ‘false’
344 | concept invocable = is_invocable_v<_Fn, _Args...>;
>>>
>From gcc-bugs-return-664520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 19:44:06 2020
Return-Path: <gcc-bugs-return-664520-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17137 invoked by alias); 4 Jan 2020 19:44:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17089 invoked by uid 48); 4 Jan 2020 19:44:00 -0000
From: "tobias.loew at steag dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93155] New: Error when compiling Boost MP11 mp_similar
Date: Sat, 04 Jan 2020 19:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tobias.loew at steag dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93155-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00246.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93155
Bug ID: 93155
Summary: Error when compiling Boost MP11 mp_similar
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: tobias.loew at steag dot com
Target Milestone: ---
The following code results in an ambiguity-error:
#include <list>
#include <boost/mp11.hpp>
int main(){
static constexpr bool b = boost::mp11::mp_similar<std::list<int>,
std::list<int>>::value;
}
Please find here an example:
https://godbolt.org/z/Wzaa6_
>From gcc-bugs-return-664521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 19:52:07 2020
Return-Path: <gcc-bugs-return-664521-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35587 invoked by alias); 4 Jan 2020 19:52:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35546 invoked by uid 48); 4 Jan 2020 19:52:03 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93155] Error when compiling Boost MP11 mp_similar
Date: Sat, 04 Jan 2020 19:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-93155-4-K0lwOrTBSx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00247.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93155
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2020-01-04
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you attach the preprocessed source?
>From gcc-bugs-return-664523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 20:03:40 2020
Return-Path: <gcc-bugs-return-664523-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44857 invoked by alias); 4 Jan 2020 20:03: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 44788 invoked by uid 48); 4 Jan 2020 20:03:35 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45734] [DR 1116] Devirtualization results in wrong-code
Date: Sat, 04 Jan 2020 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: SUSPENDED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-45734-4-RLqLwGSrDd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00249.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45734
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ch3root at openwall dot com
--- Comment #7 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 93153 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-664522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 20:03:39 2020
Return-Path: <gcc-bugs-return-664522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44843 invoked by alias); 4 Jan 2020 20:03: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 44757 invoked by uid 48); 4 Jan 2020 20:03:35 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93153] Wrong optimization while devirtualizing after placement new over local var
Date: Sat, 04 Jan 2020 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93153-4-L099YDJngt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93153-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93153-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00248.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93153
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Actually there is a C++ defect report about this specific testcase and the
committee had decided it was undefined.
THis is an exact dup of bug 45734.
*** This bug has been marked as a duplicate of bug 45734 ***
>From gcc-bugs-return-664524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 20:06:14 2020
Return-Path: <gcc-bugs-return-664524-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48229 invoked by alias); 4 Jan 2020 20:06: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 48148 invoked by uid 48); 4 Jan 2020 20:06:09 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45734] [DR 1116] Devirtualization results in wrong-code
Date: Sat, 04 Jan 2020 20:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-45734-4-an6SdGZmrS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00250.txt.bz2
Content-length: 591
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45734
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|SUSPENDED |RESOLVED
Resolution|--- |INVALID
--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The C++ defect has been resolved now:
http://www.open-std.org/JTC1/SC22/WG21/docs/cwg_defects.html#1116
So closing as invalid as the behavior was decided as undefined.
>From gcc-bugs-return-664525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 20:10:41 2020
Return-Path: <gcc-bugs-return-664525-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51232 invoked by alias); 4 Jan 2020 20:10: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 51196 invoked by uid 48); 4 Jan 2020 20:10:31 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/82224] Strict-aliasing not noticing valid aliasing of two unions with active members
Date: Sat, 04 Jan 2020 20:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia 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-82224-4-vIJSagGJdl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82224-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82224-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00251.txt.bz2
Content-length: 244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82224
--- Comment #13 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
See
http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_236.htm
http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1409.htm
>From gcc-bugs-return-664526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 22:45:37 2020
Return-Path: <gcc-bugs-return-664526-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50330 invoked by alias); 4 Jan 2020 22:45: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 49007 invoked by uid 48); 4 Jan 2020 22:45:17 -0000
From: "jim at meyering dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] New: abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sat, 04 Jan 2020 22:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jim at meyering dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00252.txt.bz2
Content-length: 2367
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
Bug ID: 93156
Summary: abused nonnull attribute evokes new segfault in gcc 10
since Nov 4 commit, 0fb958ab8aa
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jim at meyering dot net
Target Milestone: ---
First clue: the following (derived from a gnulib test) segfaults with -O1, but
not with -O0. I build gcc from master ~daily, so could conveniently "bisect" to
around Nov 4 or 5. Before then, this program would exit zero. Since then, it
segfaults.
$ gcc -O0 -ggdb3 k.c && ./a.out; echo $?
0
$ gcc -O1 -ggdb3 k.c && ./a.out
zsh: segmentation fault (core dumped) ./a.out
[Exit 139 (SEGV)]
$ gdb a.out
Reading symbols from a.out...
(gdb) r
Starting program: /home/j/w/co/sed/gnulib-tests/a.out
warning: Loadable section ".note.gnu.property" outside of ELF segments
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7e15107 in __GI___realpath (name=name@entry=0xffffffffffffffff
<error: Cannot access memory at address 0xffffffffffffffff>,
resolved=resolved@entry=0x0) at canonicalize.c:50
50 if (name == NULL)
$ cat k.c
extern char *canonicalize_file_name (const char *__name) __attribute__
((__nonnull__ (1)));
extern int rand (void);
/* Return NULL.
Usual compilers are not able to infer something about the return value. */
static void *
null_ptr (void)
{
unsigned int x = rand ();
unsigned int y = x * x;
if (y & 2)
return (void *) -1;
else
return (void *) 0;
}
int
main (void)
{
return !!canonicalize_file_name (null_ptr ());
}
I bisected to this commit:
--------------
commit 0fb958ab8aadda977333cd8a5fbd349babd2807c
Author: aldyh <aldyh@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Mon Nov 4 22:05:26 2019 +0000
Remove handle_pointers argument from all the vrp_val*{min,max} functions.
Always
assume pointers should be handled.
git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@277796
138bc75d-0d04-0410-961f-82ee72b054a4
gcc/ChangeLog | 23 +++++++++++++++++++
gcc/tree-vrp.c | 70 ++++++++++++++++++++++++++++------------------------------
gcc/tree-vrp.h | 10 ++++-----
>From gcc-bugs-return-664527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 23:18:54 2020
Return-Path: <gcc-bugs-return-664527-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90146 invoked by alias); 4 Jan 2020 23:18:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90053 invoked by uid 48); 4 Jan 2020 23:18:48 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sat, 04 Jan 2020 23:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93156-4-D0diBKtXUj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00253.txt.bz2
Content-length: 1182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
It is not about null_ptr cannot return null. But rather canonicalize_file_name
cannot take a null pointer.
If you don't want null_ptr to be inlined into main and not optimized into -1,
then add noipa or noclone/noinline to that function.
DOM changes it:
Visiting statement:
_2 = canonicalize_file_name (_14);
Intersecting
void * [1B, +INF] EQUIVALENCES: { _14 } (1 elements)
and
void * ~[1B, -2B]
to
void * [-1B, +INF] EQUIVALENCES: { _14 } (1 elements)
pushing new range for _14: void * [-1B, +INF] EQUIVALENCES: { _14 } (1
elements)
Optimizing statement _2 = canonicalize_file_name (_14);
Replaced '_14' with constant '-1B'
Because 0 is not a valid input to canonicalize_file_name.
That is the test in gnulib is broken and undefined.
>From gcc-bugs-return-664528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 23:23:43 2020
Return-Path: <gcc-bugs-return-664528-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93029 invoked by alias); 4 Jan 2020 23:23: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 92969 invoked by uid 48); 4 Jan 2020 23:23:39 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sat, 04 Jan 2020 23:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93156-4-ZKCCOPGGPs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00254.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Note the best way to implement null_ptr really (without the need for the
attribute is the following):
/* Return NULL.
Usual compilers are not able to infer something about the return value. */
static void *
null_ptr (void)
{
typedef void *voidptr;
volatile voidptr n = 0;
return n;
}
NOTE also:
unsigned int y = x * x;
if (y & 2)
Is always false even for overflow case so even then it will return null always
and if it gets inlined, then GCC is not assuming anything about the return
value.
>From gcc-bugs-return-664529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 23:36:00 2020
Return-Path: <gcc-bugs-return-664529-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123782 invoked by alias); 4 Jan 2020 23:35:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123729 invoked by uid 48); 4 Jan 2020 23:35:55 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92086] Provide way to avoid saving callee-saved registers in functions without callers
Date: Sat, 04 Jan 2020 23:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92086-4-UcCQ8i4AS5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92086-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92086-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00255.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92086
--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
This is related to the compiler saving the return address for noreturn
sibcalls, like in
void g(void) __attribute__((noreturn));
void f(void) { g(); }
Maybe we should have an option like "-fimprove-debugging-experience" that
defaults to true only for -O0 and -Og (and maybe -O1)?
>From gcc-bugs-return-664530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 23:39:03 2020
Return-Path: <gcc-bugs-return-664530-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127651 invoked by alias); 4 Jan 2020 23:39: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 127602 invoked by uid 48); 4 Jan 2020 23:38:58 -0000
From: "jim at meyering dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sat, 04 Jan 2020 23:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jim at meyering dot net
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93156-4-S03DJkO8Fw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00256.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
--- Comment #3 from jim at meyering dot net ---
Hi Andrew, thank you for the prompt investigation.
I'm probably just being dense, but how can the compiler ever generate code for
that null_ptr function that results in -1?
Your comment shows you know this already, but for others, here's a comment from
the sources in gnulib:
/* If you want to know why this always returns NULL, read
https://en.wikipedia.org/wiki/Quadratic_residue#Prime_power_modulus . */
Note that at least some versions of canonicalize_file_name *can* take a NULL
argument, so the use of the nonnull attribute in that declaration is wrong.
I did notice that removing it in this reproducer and in the original makes the
problem go away.
>From gcc-bugs-return-664531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 04 23:59:55 2020
Return-Path: <gcc-bugs-return-664531-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7531 invoked by alias); 4 Jan 2020 23:59: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 7482 invoked by uid 48); 4 Jan 2020 23:59:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sat, 04 Jan 2020 23:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93156-4-1crd2W6Ayi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00257.txt.bz2
Content-length: 1519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to jim from comment #3)
> Hi Andrew, thank you for the prompt investigation.
> I'm probably just being dense, but how can the compiler ever generate code
> for that null_ptr function that results in -1?
It is not that null_ptr can result in -1 directly but rather if it is inlined
and then later on passed to a non-null function, it will change it to be the
non-null case.
>
> Your comment shows you know this already, but for others, here's a comment
> from the sources in gnulib:
>
> /* If you want to know why this always returns NULL, read
> https://en.wikipedia.org/wiki/Quadratic_residue#Prime_power_modulus . */
>
I am saying that is not the best way of getting the compiler not to notice it
as being a choice between a non-null and a null pointer. Using a volatile
variable makes the compiler NOT do any optimization and will not see the
non-null pointer choice.
> Note that at least some versions of canonicalize_file_name *can* take a NULL
> argument, so the use of the nonnull attribute in that declaration is wrong.
The question comes, where is the nonnull attribute coming from? But I don't
think it matters here.
Using:
static void *
null_ptr (void)
{
typedef void *voidptr;
volatile voidptr n = 0;
return n;
}
Will allow all compilers not to optimize anything to be known about null_ptr()
function even with inlining being involved.
>From gcc-bugs-return-664532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 00:49:50 2020
Return-Path: <gcc-bugs-return-664532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67973 invoked by alias); 5 Jan 2020 00:49:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66557 invoked by uid 55); 5 Jan 2020 00:49:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93046] [10 Regression] ICE in cp_gimplify_init_expr
Date: Sun, 05 Jan 2020 00:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93046-4-R4vueQzdKa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00258.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93046
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sun Jan 5 00:49:14 2020
New Revision: 279884
URL: https://gcc.gnu.org/viewcvs?rev=279884&root=gcc&view=rev
Log:
PR c++/93046
* cp-gimplify.c (cp_gimplify_init_expr): Don't look through
TARGET_EXPR if it has been gimplified already.
* g++.dg/ext/cond4.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ext/cond4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-gimplify.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 00:51:55 2020
Return-Path: <gcc-bugs-return-664533-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77880 invoked by alias); 5 Jan 2020 00:51: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 77807 invoked by uid 48); 5 Jan 2020 00:51:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93046] [10 Regression] ICE in cp_gimplify_init_expr
Date: Sun, 05 Jan 2020 00:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93046-4-jr23GJIN7z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00259.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93046
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-664534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 01:30:54 2020
Return-Path: <gcc-bugs-return-664534-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108400 invoked by alias); 5 Jan 2020 01:30:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108354 invoked by uid 48); 5 Jan 2020 01:30:50 -0000
From: "jim at meyering dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sun, 05 Jan 2020 01:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jim at meyering dot net
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93156-4-EOGM5sxjpn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00260.txt.bz2
Content-length: 648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
--- Comment #5 from jim at meyering dot net ---
(In reply to Andrew Pinski from comment #4)
> (In reply to jim from comment #3)
> > Hi Andrew, thank you for the prompt investigation.
> > I'm probably just being dense, but how can the compiler ever generate code
> > for that null_ptr function that results in -1?
>
> It is not that null_ptr can result in -1 directly but rather if it is
> inlined and then later on passed to a non-null function, it will change it
> to be the non-null case.
Let me rephrase: how can a transformation that makes it look like null_ptr
returned -1 be valid?
>From gcc-bugs-return-664535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 01:37:02 2020
Return-Path: <gcc-bugs-return-664535-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113314 invoked by alias); 5 Jan 2020 01:37:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113267 invoked by uid 48); 5 Jan 2020 01:36:57 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sun, 05 Jan 2020 01:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93156-4-PPDoe9TTgs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00261.txt.bz2
Content-length: 894
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to jim from comment #5)
> (In reply to Andrew Pinski from comment #4)
> > (In reply to jim from comment #3)
> > > Hi Andrew, thank you for the prompt investigation.
> > > I'm probably just being dense, but how can the compiler ever generate code
> > > for that null_ptr function that results in -1?
> >
> > It is not that null_ptr can result in -1 directly but rather if it is
> > inlined and then later on passed to a non-null function, it will change it
> > to be the non-null case.
>
> Let me rephrase: how can a transformation that makes it look like null_ptr
> returned -1 be valid?
Because it would be undefined code if it returned NULL.
That is:
a?-1:0 is transformed into -1 before we figure out that a is always true; an
ordering difference.
>From gcc-bugs-return-664536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 05:03:03 2020
Return-Path: <gcc-bugs-return-664536-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65184 invoked by alias); 5 Jan 2020 05:03:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57496 invoked by uid 48); 5 Jan 2020 05:02:59 -0000
From: "gyakovlev at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93157] New: gcc should use -mabi=elfv2 on powerpc64-*-linux-*musl* target by default.
Date: Sun, 05 Jan 2020 05:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gyakovlev at gentoo 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-93157-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00262.txt.bz2
Content-length: 1565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93157
Bug ID: 93157
Summary: gcc should use -mabi=elfv2 on powerpc64-*-linux-*musl*
target by default.
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: gyakovlev at gentoo dot org
Target Milestone: ---
encountered with 9.2.0 but I think all versions affected.
By default at configuration time gcc assumes that powerpc64-*-linux-* (big
endian ppc64) targets use ELFv1 ABI, and ELFv2 abi on little-endian.
But musl libc does not support ELFv1 at all on either endian ppc64.
Their INSTALL file clearly mentions:
* PowerPC64
* Both little and big endian variants are supported
* Compiler toolchain must provide 64-bit long double, not IBM
double-double or IEEE quad
* Compiler toolchain must use the new (ELFv2) ABI regardless of
whether it is for little or big endian
I think gcc configuration should default to --with-abi=elfv2 on
powerpc64-*-linux-*musl* target.
* Configuring GCC with:
* --host=powerpc64-unknown-linux-gnu
* --target=powerpc64-unknown-linux-musl
* --build=powerpc64-unknown-linux-gnu
after that musl fails
checking whether linker accepts -lgcc_eh... yes
using compiler runtime libraries: -lgcc -lgcc_eh
checking preprocessor condition _CALL_ELF == 2... false
./configure: error: unsupported powerpc64 ABI
>From gcc-bugs-return-664537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 06:09:10 2020
Return-Path: <gcc-bugs-return-664537-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33408 invoked by alias); 5 Jan 2020 06:09:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33353 invoked by uid 48); 5 Jan 2020 06:09:05 -0000
From: "madhur4127 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Sun, 05 Jan 2020 06:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: madhur4127 at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93141-4-1MASPVic53@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00263.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
--- Comment #6 from Madhur Chauhan <madhur4127 at gmail dot com> ---
As far as I can tell optimal asm generated should be like:
mov-load from on array
mul or preferably mulx with a memory source from the other array
add + adc into 128-bit answer register
adc reg, 0 to accumulate the carry-out.
This optimization could help many big integer libraries as this lies in most
critical section.
>From gcc-bugs-return-664538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 06:09:56 2020
Return-Path: <gcc-bugs-return-664538-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34625 invoked by alias); 5 Jan 2020 06:09:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34379 invoked by uid 48); 5 Jan 2020 06:09:51 -0000
From: "madhur4127 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Sun, 05 Jan 2020 06:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: madhur4127 at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93141-4-AeoFW1GZmn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00264.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
--- Comment #7 from Madhur Chauhan <madhur4127 at gmail dot com> ---
As far as I can tell optimal asm generated should be like:
mov-load from on array
mul or preferably mulx with a memory source from the other array
add + adc into 128-bit answer register
adc reg, 0 to accumulate the carry-out.
This optimization could help many big integer libraries as this lies in most
critical section.
>From gcc-bugs-return-664539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 07:32:34 2020
Return-Path: <gcc-bugs-return-664539-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63628 invoked by alias); 5 Jan 2020 07:32:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63585 invoked by uid 48); 5 Jan 2020 07:32:30 -0000
From: "damian at sourceryinstitute dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93158] New: Coarray ICE when module and submodule are in separate files
Date: Sun, 05 Jan 2020 07:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: damian at sourceryinstitute 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-93158-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00265.txt.bz2
Content-length: 2524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93158
Bug ID: 93158
Summary: Coarray ICE when module and submodule are in separate
files
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: damian at sourceryinstitute dot org
Target Milestone: ---
The ICE demonstrated below disappears if any one of the following is true:
1. The module and submodule are in the same file, or
2. The coarray is moved from the submodule to the module, or
3. The halo_data component is non-polymorphic.
$ cat surfaces_interface.f90
module surfaces_interface
type package
end type
type surfaces
class(package), allocatable :: halo_data
end type
interface
module subroutine set_halo_data()
end subroutine
end interface
end module
$ cat surfaces_implementation.f90
submodule(surfaces_interface) surfaces_implementation
type(surfaces) singleton[*]
contains
module procedure set_halo_data
end procedure
end submodule
$ gfortran -fcoarray=single -c surfaces_interface.f90
surfaces_implementation.f90
f951: internal compiler error: in gfc_get_derived_type, at
fortran/trans-types.c:2843
libbacktrace could not find executable to open
$ gfortran --version
GNU Fortran (GCC) 10.0.0 20190926 (experimental)
However, even with fixes 2 and 3 above, an ICE still occurs if all of the
following are true:
1. The halo_data component is made polymorphic, and
2. The subroutine allocates or assigns to the component, and
3. The module and submodule are in a separate file.
$ cat surfaces_interface.f90
module surfaces_interface
type package
end type
type surfaces
class(package), allocatable :: halo_data
end type
type(surfaces) singleton[*]
interface
module subroutine set_halo_data()
end subroutine
end interface
end module
$ cat surfaces_implementation.f90
submodule(surfaces_interface) surfaces_implementation
contains
module procedure set_halo_data
allocate(package::singleton%halo_data)
end procedure
end submodule
$ gfortran -fcoarray=single -c surfaces_interface.f90
surfaces_implementation.f90
surfaces_implementation.f90:4:0:
4 | allocate(package::singleton%halo_data)
|
internal compiler error: in gfc_get_derived_type, at fortran/trans-types.c:2843
Issues with file scope appear to be the unifying theme.
>From gcc-bugs-return-664540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 09:32:50 2020
Return-Path: <gcc-bugs-return-664540-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68284 invoked by alias); 5 Jan 2020 09: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 68222 invoked by uid 48); 5 Jan 2020 09:32:46 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93159] New: [10 Regression] ICE (segfault) during RTL pass on arm-linux-gnueabihf
Date: Sun, 05 Jan 2020 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93159-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00266.txt.bz2
Content-length: 2886
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93159
Bug ID: 93159
Summary: [10 Regression] ICE (segfault) during RTL pass on
arm-linux-gnueabihf
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
seen with trunk 20192018 and 20200104 with a jit build, on arm-linux-gnueabihf.
the jit build is done with the just (successfully) built native build.
during RTL pass: reload
../../src/gcc/genrecog.c: In function 'state* match_pattern_2(state*,
md_rtx_info*, position*, rtx)':
../../src/gcc/genrecog.c:4183:1: internal compiler error: Segmentation fault
4183 | }
| ^
0x5b08df crash_signal
../../src/gcc/toplev.c:328
0x4a94df add_regs_to_insn_regno_info
../../src/gcc/lra.c:1509
0x4a95d3 add_regs_to_insn_regno_info
../../src/gcc/lra.c:1531
0x4a95d3 add_regs_to_insn_regno_info
../../src/gcc/lra.c:1531
0x4aa67d lra_update_insn_regno_info(rtx_insn*)
../../src/gcc/lra.c:1624
0x4aa7cd lra_update_insn_regno_info(rtx_insn*)
../../src/gcc/lra.c:1617
0x4aa7cd lra_push_insn_1
../../src/gcc/lra.c:1774
0x4c29eb spill_pseudos
../../src/gcc/lra-spills.c:523
0x4c29eb lra_spill()
../../src/gcc/lra-spills.c:636
0x4ab8db lra(_IO_FILE*)
../../src/gcc/lra.c:2554
0x47d329 do_reload
../../src/gcc/ira.c:5526
0x47d329 execute
../../src/gcc/ira.c:5712
Please submit a full bug report,
with preprocessed source if appropriate.
The bug is not reproducible, so it is likely a hardware or OS problem.
make[4]: *** [Makefile:2674: build/genrecog.o] Error 1
make[4]: *** Waiting for unfinished jobs....
this is with a compiler configure with enabled hardening defaults, on top of
configure --with-gcc-major-version-only --program-suffix=-10
--program-prefix=arm-linux-gnueabihf- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libs
tdcxx-time=yes --with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-libitm --disable-libquadmath --disable-libquadmath-s
upport --enable-plugin --enable-default-pie --with-system-zlib
--with-target-system-zlib=auto --enable-objc-gc=auto --enable-multiarch --
enable-multilib --disable-sjlj-exceptions --with-arch=armv7-a
--with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --disable-werror -
-enable-multilib --enable-checking=release --build=arm-linux-gnueabihf
--host=arm-linux-gnueabihf --target=arm-linux-gnueabihf --enable-l
anguages=c++,jit --enable-host-shared --disable-bootstrap
>From gcc-bugs-return-664541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 09:54:40 2020
Return-Path: <gcc-bugs-return-664541-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88062 invoked by alias); 5 Jan 2020 09:54:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87950 invoked by uid 48); 5 Jan 2020 09:54:36 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/45596] Implement simple static points-to analysis in Fortran FE
Date: Sun, 05 Jan 2020 09:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also blocked
Message-ID: <bug-45596-4-fzcZDX3x2G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45596-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45596-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00267.txt.bz2
Content-length: 844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45596
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=92087
Blocks| |36854, 26163
--- Comment #12 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Maybe it's time to revisit this, not for gcc 10, but for gcc 11.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36854
[Bug 36854] [meta-bug] fortran front-end optimization
>From gcc-bugs-return-664542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 10:22:01 2020
Return-Path: <gcc-bugs-return-664542-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106536 invoked by alias); 5 Jan 2020 10:22:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106463 invoked by uid 48); 5 Jan 2020 10:21:56 -0000
From: "tobias.loew at steag dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93155] Error when compiling Boost MP11 mp_similar
Date: Sun, 05 Jan 2020 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tobias.loew at steag dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93155-4-5ECH86LAnx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00268.txt.bz2
Content-length: 602
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93155
--- Comment #2 from Tobias Loew <tobias.loew at steag dot com> ---
// here is a minimal example (extracted from boost/mp11/function.hpp)
template<class T>
struct s{};
template<class... T> struct mp_similar_impl;
template<class T> struct mp_similar_impl<T, T>
{
using type = int;
};
// commenting the following specialization removes the error
template<template<class...> class L, class... T1, class... T2> struct
mp_similar_impl<L<T1...>, L<T2...>>
{
using type = int;
};
int main(){
mp_similar_impl<s<int>, s<int>>::type v;
}
>From gcc-bugs-return-664543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 10:57:30 2020
Return-Path: <gcc-bugs-return-664543-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57367 invoked by alias); 5 Jan 2020 10:57:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57330 invoked by uid 48); 5 Jan 2020 10:57:26 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87797] Enhancement: Warning for potential name clash of variables/intrinsics...
Date: Sun, 05 Jan 2020 10:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87797-4-UZbnAnubnL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00269.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87797
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Could be made an addition to -Wintrinsic-shadow.
>From gcc-bugs-return-664544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 11:05:00 2020
Return-Path: <gcc-bugs-return-664544-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63475 invoked by alias); 5 Jan 2020 11:05: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 63428 invoked by uid 48); 5 Jan 2020 11:04:56 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91782] Accepts invalid array constructor with character parameter
Date: Sun, 05 Jan 2020 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-91782-4-Uje6sPP2Ke@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00270.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91782
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-05
CC| |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-664545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 11:09:02 2020
Return-Path: <gcc-bugs-return-664545-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68568 invoked by alias); 5 Jan 2020 11:09:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68524 invoked by uid 48); 5 Jan 2020 11:08:58 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91728] Accepts array with wrong shape in a structure constructor
Date: Sun, 05 Jan 2020 11:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-91728-4-Ilhk7l7PzV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91728-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91728-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00271.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91728
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-05
CC| |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-664546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 11:15:30 2020
Return-Path: <gcc-bugs-return-664546-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72788 invoked by alias); 5 Jan 2020 11:15: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 72640 invoked by uid 48); 5 Jan 2020 11:15:03 -0000
From: "arnd at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92657] High stack usage due ftree-ch
Date: Sun, 05 Jan 2020 11:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: arnd at linaro dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92657-4-HRy6XfLEzq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00272.txt.bz2
Content-length: 531
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92657
Arnd Bergmann <arnd at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |arnd at linaro dot org
--- Comment #5 from Arnd Bergmann <arnd at linaro dot org> ---
Submitted a workaround for the warning that triggered this bug report in the
linux kernel:
https://lore.kernel.org/lkml/20200104215156.689245-1-arnd@arndb.de/
>From gcc-bugs-return-664547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 11:17:25 2020
Return-Path: <gcc-bugs-return-664547-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77200 invoked by alias); 5 Jan 2020 11:17:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77132 invoked by uid 48); 5 Jan 2020 11:17:20 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/46244] gfc_compare_derived_types is buggy
Date: Sun, 05 Jan 2020 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: ice-on-valid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mikael at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-46244-4-2MlTkgFTjj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46244-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46244-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00273.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=46244
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #20 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Mikael, are you still planning to work on this?
>From gcc-bugs-return-664548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 11:59:40 2020
Return-Path: <gcc-bugs-return-664548-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112799 invoked by alias); 5 Jan 2020 11: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 112782 invoked by uid 48); 5 Jan 2020 11:59:36 -0000
From: "tobias.loew at steag dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93155] Error when compiling Boost MP11 mp_similar
Date: Sun, 05 Jan 2020 11:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tobias.loew at steag dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93155-4-JqRzpwOzfz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00274.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93155
--- Comment #3 from Tobias Loew <tobias.loew at steag dot com> ---
After reading the standard carefully, I figured out that this is not an error
since the rewrite as function templates is ambiguous:
template<class... T> struct mp_similar_impl {};
template<class T>
void f(mp_similar_impl<T, T>) {}
template<template<class...> class L, class... T1, class... T2>
void f(mp_similar_impl<L<T1...>, L<T2...>>) {}
int main() {
f(mp_similar_impl<std::list<int>, std::list<int>>{}); // error ambiguous
}
>From gcc-bugs-return-664549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 12:51:17 2020
Return-Path: <gcc-bugs-return-664549-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44427 invoked by alias); 5 Jan 2020 12:51: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 44389 invoked by uid 55); 5 Jan 2020 12:51:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93138] [10 regression] elaborated type specifier visibility check problem
Date: Sun, 05 Jan 2020 12:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93138-4-xEKcyBS9Bt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00275.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93138
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sun Jan 5 12:50:40 2020
New Revision: 279886
URL: https://gcc.gnu.org/viewcvs?rev=279886&root=gcc&view=rev
Log:
PR c++/93138
* parser.c (cp_parser_check_class_key): Disable access checks for the
simple name lookup.
(cp_parser_maybe_warn_enum_key): Likewise. Return early if
!warn_redundant_tags.
* g++.dg/warn/Wredundant-tags-2.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/warn/Wredundant-tags-2.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/parser.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-664550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 12:53:02 2020
Return-Path: <gcc-bugs-return-664550-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45801 invoked by alias); 5 Jan 2020 12:53:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45725 invoked by uid 55); 5 Jan 2020 12:52:57 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93141] Missed optimization : Use of adc when checking overflow
Date: Sun, 05 Jan 2020 12:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93141-4-UT81CDru7K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93141-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00276.txt.bz2
Content-length: 1446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93141
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sun Jan 5 12:52:24 2020
New Revision: 279887
URL: https://gcc.gnu.org/viewcvs?rev=279887&root=gcc&view=rev
Log:
PR target/93141
* config/i386/i386.md (SWIDWI): New mode iterator.
(DWI, dwi): Add TImode variants.
(addv<mode>4): Use SWIDWI iterator instead of SWI. Use
<general_hilo_operand> instead of <general_operand>. Use
CONST_SCALAR_INT_P instead of CONST_INT_P.
(*addv<mode>4_1): Rename to ...
(addv<mode>4_1): ... this.
(QWI): New mode attribute.
(*addv<dwi>4_doubleword, *addv<dwi>4_doubleword_1): New
define_insn_and_split patterns.
(*addv<mode>4_overflow_1, *addv<mode>4_overflow_2): New define_insn
patterns.
(uaddv<mode>4): Use SWIDWI iterator instead of SWI. Use
<general_hilo_operand> instead of <general_operand>.
(*addcarry<mode>_1): New define_insn.
(*add<dwi>3_doubleword_cc_overflow_1): New define_insn_and_split.
* gcc.target/i386/pr93141-1.c: New test.
* gcc.dg/pr67089-6.c: Expect 16 ADD_OVERFLOW calls even on ia32.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr93141-1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.md
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/pr67089-6.c
>From gcc-bugs-return-664551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 14:46:27 2020
Return-Path: <gcc-bugs-return-664551-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50366 invoked by alias); 5 Jan 2020 14:46:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50322 invoked by uid 48); 5 Jan 2020 14:46:21 -0000
From: "anbu1024.me at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/93160] New: ICE: in expand_expr_addr_expr_1, at expr.c:8070
Date: Sun, 05 Jan 2020 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anbu1024.me 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-93160-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00277.txt.bz2
Content-length: 2730
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93160
Bug ID: 93160
Summary: ICE: in expand_expr_addr_expr_1, at expr.c:8070
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: inline-asm
Assignee: unassigned at gcc dot gnu.org
Reporter: anbu1024.me at gmail dot com
Target Milestone: ---
$ cat test.c
extern long unsigned int sub_0 ( const char * ) ;
extern void * sub_1 ( long unsigned int ) ;
extern int var_0 ;
void * var_1 = & var_0 ;
register int var_0 asm ( "%ecx" ) ;
--------------------------------------------------------------------------------
$ gcc-snapshot10 --versiongcc (GCC) 10.0.0 20191229 (experimental)
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
--------------------------------------------------------------------------------
$ gcc-snapshot10 test.c
test.c:10:14: warning: call-clobbered register used for global register
variable
10 | register int var_0 asm ( "%ecx" ) ;
| ^~~~~
test.c:10:1: internal compiler error: in expand_expr_addr_expr_1, at
expr.c:8070
10 | register int var_0 asm ( "%ecx" ) ;
| ^~~~~~~~
0x633aab expand_expr_addr_expr_1
../../gcc-10-20191229/gcc/expr.c:8070
0xa1b8f9 expand_expr_addr_expr
../../gcc-10-20191229/gcc/expr.c:8183
0xa1b8f9 expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../gcc-10-20191229/gcc/expr.c:11358
0x105d9ab expand_expr
../../gcc-10-20191229/gcc/expr.h:282
0x105d9ab output_constant
../../gcc-10-20191229/gcc/varasm.c:4993
0x105e274 output_constant
../../gcc-10-20191229/gcc/varasm.c:4901
0x105e274 assemble_variable_contents
../../gcc-10-20191229/gcc/varasm.c:2148
0x10636ba assemble_variable(tree_node*, int, int, int)
../../gcc-10-20191229/gcc/varasm.c:2327
0x1066f29 varpool_node::assemble_decl()
../../gcc-10-20191229/gcc/varpool.c:586
0x938c1c output_in_order
../../gcc-10-20191229/gcc/cgraphunit.c:2566
0x938c1c symbol_table::compile()
../../gcc-10-20191229/gcc/cgraphunit.c:2803
0x93ae8c symbol_table::compile()
../../gcc-10-20191229/gcc/cgraphunit.c:2719
0x93ae8c symbol_table::finalize_compilation_unit()
../../gcc-10-20191229/gcc/cgraphunit.c:2986
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-664552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 14:58:36 2020
Return-Path: <gcc-bugs-return-664552-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65647 invoked by alias); 5 Jan 2020 14:58: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 65620 invoked by uid 48); 5 Jan 2020 14:58:32 -0000
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90142] contrib/download_prerequisites uses test =Date: Sun, 05 Jan 2020 14:58: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: 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:
Message-ID: <bug-90142-4-sIgvt3fNRB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00278.txt.bz2
Content-length: 241
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90142
--- Comment #2 from Roland Illig <roland.illig at gmx dot de> ---
Please just ignore the patch, if that's easier.
Portable shell programs should not use the == operator for test(1).
>From gcc-bugs-return-664553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 15:36:03 2020
Return-Path: <gcc-bugs-return-664553-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42153 invoked by alias); 5 Jan 2020 15:36: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 42075 invoked by uid 48); 5 Jan 2020 15:35:58 -0000
From: "ch3root at openwall dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45734] [DR 1116] Devirtualization results in wrong-code
Date: Sun, 05 Jan 2020 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ch3root at openwall dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-45734-4-y8eTs1jklM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00279.txt.bz2
Content-length: 1094
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45734
--- Comment #9 from Alexander Cherepanov <ch3root at openwall dot com> ---
DR 1116 is said to be resolved by P0137R1[1]. By looking through it, I don't
see how it covers testcases from this pr where "right" pointer is used (like
the example in comment 0). And it even introduces std::launder for using
"wrong" pointers.
Even better, the C++ standard contains a whole paragraph ([basic.life]p9 -- see
[2]) describing finer details of killing non-dynamic variables. And the example
there features exactly placement new over a local variable:
----------------------------------------------------------------------
class T { };
struct B {
~B();
};
void h() {
B b;
new (&b) T;
} // undefined behavior at block exit
----------------------------------------------------------------------
The examples in this pr don't have classes with non-trivial destructors so they
don't hit such UB.
[1] http://open-std.org/JTC1/SC22/WG21/docs/papers/2016/p0137r1.html
[2] https://eel.is/c++draft/basic.life#9
>From gcc-bugs-return-664554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 16:04:56 2020
Return-Path: <gcc-bugs-return-664554-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81828 invoked by alias); 5 Jan 2020 16:04:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81772 invoked by uid 48); 5 Jan 2020 16:04:50 -0000
From: "wezrule at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93161] New: Remove extra operator== for comparison categories in <compare> not in standard
Date: Sun, 05 Jan 2020 16:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wezrule 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-93161-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00280.txt.bz2
Content-length: 1371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93161
Bug ID: 93161
Summary: Remove extra operator== for comparison categories in
<compare> not in standard
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: wezrule at hotmail dot com
Target Milestone: ---
The following compiles fine with gcc (on godbolt gcc trunk):
int x{2};
int y{2};
auto s = x <=> y;
s == std::strong_ordering::equal; // fails with MSVC
https://godbolt.org/z/baRNF6
However the last line fails to compile with MSVC. After checking the standards
library support document operator==(strong_ordering, strong_ordering) is not
mentioned:
http://wg21.link/p0768
On the gcc master branch it can be located here (same exists for weak_ordering
and other comparison categories):
https://github.com/wezrule/gcc/blob/master/libstdc%2B%2B-v3/libsupc%2B%2B/compare#L299
Even worse is that value types are not even standardised for comparison
operators! (thanks Bo Persson):
http://wg21.link/P1946
I think these should just be removed, it's recommended to compare against 0 and
would be good to not have further inconsistencies in implementations.
Cheers,
Wesley
>From gcc-bugs-return-664555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 18:19:30 2020
Return-Path: <gcc-bugs-return-664555-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79725 invoked by alias); 5 Jan 2020 18:19:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79656 invoked by uid 48); 5 Jan 2020 18:19:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93162] New: [10 Regression] gcc/fortran/trans-openmp.c:2469:50: runtime error: load of value 145992800, which is not a valid value for type 'ar_type' since r279628
Date: Sun, 05 Jan 2020 18:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter blocked target_milestone
Message-ID: <bug-93162-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00281.txt.bz2
Content-length: 2398
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93162
Bug ID: 93162
Summary: [10 Regression] gcc/fortran/trans-openmp.c:2469:50:
runtime error: load of value 145992800, which is not a
valid value for type 'ar_type' since r279628
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Blocks: 63426
Target Milestone: ---
Starting from the revision, I see the following run-time error:
$ ./xgcc -B.
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-ubsan/build/gcc/testsuite/gfortran.dg/goacc/derived-types-3.f90
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fdiagnostics-color=never -fdiagnostics-urls=never -O -fopenacc -S -o
derived-types-3.s
../../gcc/fortran/trans-openmp.c:2469:50: runtime error: load of value
176162128, which is not a valid value for type 'ar_type'
#0 0xeac9fb in gfc_trans_omp_clauses ../../gcc/fortran/trans-openmp.c:2469
#1 0xeb93d6 in gfc_trans_oacc_executable_directive
../../gcc/fortran/trans-openmp.c:3662
#2 0xec9df5 in gfc_trans_oacc_directive(gfc_code*)
../../gcc/fortran/trans-openmp.c:5696
#3 0xcd1af6 in trans_code ../../gcc/fortran/trans.c:2158
#4 0xcd1de9 in gfc_trans_code(gfc_code*) ../../gcc/fortran/trans.c:2197
#5 0xd9ddfa in gfc_generate_function_code(gfc_namespace*)
../../gcc/fortran/trans-decl.c:6823
#6 0xcd1e74 in gfc_generate_code(gfc_namespace*)
../../gcc/fortran/trans.c:2214
#7 0xb22c54 in translate_all_program_units ../../gcc/fortran/parse.c:6302
#8 0xb23ac0 in gfc_parse_file() ../../gcc/fortran/parse.c:6541
#9 0xc923b0 in gfc_be_parse_file ../../gcc/fortran/f95-lang.c:210
#10 0x244f0fb in compile_file ../../gcc/toplev.c:458
#11 0x2457af0 in do_compile ../../gcc/toplev.c:2269
#12 0x2458124 in toplev::main(int, char**) ../../gcc/toplev.c:2408
#13 0x4a32e40 in main ../../gcc/main.c:39
#14 0x7fadf0750e0a in __libc_start_main ../csu/libc-start.c:308
#15 0x8ad1f9 in _start
(/home/marxin/Programming/gcc2/objdir/gcc/f951+0x8ad1f9)
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63426
[Bug 63426] [meta-bug] Issues found with -fsanitize=undefined
>From gcc-bugs-return-664556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 18:19:50 2020
Return-Path: <gcc-bugs-return-664556-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80464 invoked by alias); 5 Jan 2020 18:19: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 80426 invoked by uid 48); 5 Jan 2020 18:19:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93162] [10 Regression] gcc/fortran/trans-openmp.c:2469:50: runtime error: load of value 145992800, which is not a valid value for type 'ar_type' since r279628
Date: Sun, 05 Jan 2020 18:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work version target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-93162-4-v1ptFk5B9c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93162-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93162-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00282.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93162
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-05
CC| |jules at gcc dot gnu.org
Known to work| |9.2.0
Version|9.0 |10.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-664557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 18:53:32 2020
Return-Path: <gcc-bugs-return-664557-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31606 invoked by alias); 5 Jan 2020 18:53: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 31569 invoked by uid 48); 5 Jan 2020 18:53:28 -0000
From: "bruno at clisp dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sun, 05 Jan 2020 18:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bruno at clisp dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93156-4-89I2Uvn92b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00283.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
Bruno Haible <bruno at clisp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bruno at clisp dot org
--- Comment #7 from Bruno Haible <bruno at clisp dot org> ---
There is more discussion on this issue in bug #36166.
>From gcc-bugs-return-664558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 20:44:10 2020
Return-Path: <gcc-bugs-return-664558-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125494 invoked by alias); 5 Jan 2020 20:44: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 125450 invoked by uid 48); 5 Jan 2020 20:44:04 -0000
From: "bruno at clisp dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Sun, 05 Jan 2020 20:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bruno at clisp dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93156-4-fkhzod5byP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00284.txt.bz2
Content-length: 2799
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
--- Comment #8 from Bruno Haible <bruno at clisp dot org> ---
(In reply to Andrew Pinski from comment #6)
> a?-1:0 is transformed into -1 before we figure out that a is always true; an
> ordering difference.
Fortunately the GCC optimization affects only the return value of null_ptr().
It does not cause side effects to occur that shouldn't occur.
Test case:
=========================================================================
extern char *canonicalize_file_name (const char *__name)
__attribute__ ((__nonnull__ (1)));
extern int rand (void);
extern void brick_the_hard_disk (void);
/* Return NULL. */
static void *
null_ptr (void)
{
unsigned int x = rand ();
unsigned int y = x * x;
/* The following statement is equivalent to if (false),
since a square is always congruent to 0 or 1 mod 4. */
if (y & 2) {
brick_the_hard_disk ();
return (void *) -1;
} else
return (void *) 0;
}
int
main (void)
{
return !!canonicalize_file_name (null_ptr ());
}
=========================================================================
Compiled with gcc -O6 -S foo.c from a recent GCC 10 snapshot:
=========================================================================
.file "foo.c"
.text
.section .text.startup,"ax",@progbits
.p2align 4
.globl main
.type main, @function
main:
.LFB1:
.cfi_startproc
subq $8, %rsp
.cfi_def_cfa_offset 16
call rand
imull %eax, %eax
testb $2, %al
je .L2
call brick_the_hard_disk
.L2:
movq $-1, %rdi
call canonicalize_file_name
testq %rax, %rax
setne %al
addq $8, %rsp
.cfi_def_cfa_offset 8
movzbl %al, %eax
ret
.cfi_endproc
.LFE1:
.size main, .-main
.ident "GCC: (GNU) 10.0.0 20191229 (experimental)"
.section .note.GNU-stack,"",@progbits
=========================================================================
As you can see, it still performs the (y & 2) and will thus never execute
brick_the_hard_disk().
>From gcc-bugs-return-664559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 20:57:59 2020
Return-Path: <gcc-bugs-return-664559-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3780 invoked by alias); 5 Jan 2020 20:57: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 3715 invoked by uid 48); 5 Jan 2020 20:57:54 -0000
From: "roland.illig at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/64271] Minimal patches to bootstrap on NetBSD
Date: Sun, 05 Jan 2020 20:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
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: cc
Message-ID: <bug-64271-4-evkBfQVeS6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64271-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64271-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00285.txt.bz2
Content-length: 1235
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64271
Roland Illig <roland.illig at gmx dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |roland.illig at gmx dot de
--- Comment #12 from Roland Illig <roland.illig at gmx dot de> ---
(In reply to Richard Biener from comment #7)
> Please submit them by posting them to gcc-patches@gcc.gnu.org.
I experienced the same reasoning in bug 90142. This reasoning feels to me as if
the GCC project would prefer bug reports without patches to bug reports
containing patches, which sounds weird.
After all, these patches are only a suggestion how GCC _might_ be fixed.
There's quite some paperwork involved to get patches submitted, therefore bug
reports like these are meant to help the GCC developers reproduce the issues.
It should not be the job of a bug reporter to understand all the internal
workflows and actually commit the patches in the end.
Could someone perhaps check these patches and apply them as far as they make
sense? At least the ctype_base patches are still required for making GCC 9.2.0
compile on x86_64--netbsd.
>From gcc-bugs-return-664560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 21:55:08 2020
Return-Path: <gcc-bugs-return-664560-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107092 invoked by alias); 5 Jan 2020 21:55:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107038 invoked by uid 48); 5 Jan 2020 21:55:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/64271] Minimal patches to bootstrap on NetBSD
Date: Sun, 05 Jan 2020 21:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64271-4-stnmS7vgZw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64271-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64271-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00286.txt.bz2
Content-length: 1144
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64271
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Roland Illig from comment #12)
> It should not be the job of a bug reporter to understand all the
> internal workflows and actually commit the patches in the end.
"Send the patch to the mailing list" does not mean "understand all the internal
workfloats and actually commit the patches in the end", where do you get that
idea?
Patch review (and discussion, approval etc.) happens on the mailing lists, not
in bugzilla. Reviewers do not scour bugzilla looking for patch submissions,
they expect patches to be submitted to the mailing lists.
That doesn't mean we don't want patches. It means we want patches to be
submitted to one place (not bugzilla, not twitter, not reddit, not github).
> Could someone perhaps check these patches and apply them as far as they make
> sense? At least the ctype_base patches are still required for making GCC
> 9.2.0 compile on x86_64--netbsd.
Again, they should be sent to the relevant mailing lists. For libstdc++ patches
that means gcc-patches and libstdc++.
>From gcc-bugs-return-664561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 21:57:18 2020
Return-Path: <gcc-bugs-return-664561-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122025 invoked by alias); 5 Jan 2020 21:57:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121999 invoked by uid 48); 5 Jan 2020 21:57:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93161] Remove extra operator== for comparison categories in <compare> not in standard
Date: Sun, 05 Jan 2020 21:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on component assigned_to everconfirmed
Message-ID: <bug-93161-4-4aMT3ADlQY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00287.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93161
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-05
Component|c++ |libstdc++
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-664562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 21:58:36 2020
Return-Path: <gcc-bugs-return-664562-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126439 invoked by alias); 5 Jan 2020 21:58: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 126369 invoked by uid 48); 5 Jan 2020 21:58:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93151] system_error header fails to compile with -D_XOPEN_SOURCE`0
Date: Sun, 05 Jan 2020 21:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-93151-4-Rcqg1fmap8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93151-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93151-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00288.txt.bz2
Content-length: 552
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93151
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-05
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-664563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 22:09:08 2020
Return-Path: <gcc-bugs-return-664563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17732 invoked by alias); 5 Jan 2020 22:09: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 17676 invoked by uid 48); 5 Jan 2020 22:09:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/64271] Minimal patches to bootstrap on NetBSD
Date: Sun, 05 Jan 2020 22:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64271-4-A7txn8TduQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64271-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64271-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00289.txt.bz2
Content-length: 662
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64271
--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Roland Illig from comment #12)
> After all, these patches are only a suggestion how GCC _might_ be fixed.
Which is exactly why patches should go to the mailing lists. The reviewer might
request changes to the patch, so the submitter will be asked to make changes
and re-test the patch to ensure it still works and fixes the problem. The
reviewer doesn't necessarily have access to the right systems to test the patch
themselves. That process of iteratively refining the patch belongs on the
mailing lists, not in bugzilla.
>From gcc-bugs-return-664565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 22:11:22 2020
Return-Path: <gcc-bugs-return-664565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20359 invoked by alias); 5 Jan 2020 22:11:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20314 invoked by uid 48); 5 Jan 2020 22:11:18 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90142] contrib/download_prerequisites uses test =Date: Sun, 05 Jan 2020 22:11: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: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-90142-4-TDnRjLo1LR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00291.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90142
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-05
Ever confirmed|0 |1
>From gcc-bugs-return-664564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 22:11:07 2020
Return-Path: <gcc-bugs-return-664564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19458 invoked by alias); 5 Jan 2020 22:11: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 19427 invoked by uid 48); 5 Jan 2020 22:11:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90142] contrib/download_prerequisites uses test =Date: Sun, 05 Jan 2020 22:11: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: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90142-4-TfWdSvdFp7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00290.txt.bz2
Content-length: 331
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90142
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
If you don't want the patch ignored, follow the procedure for submitting
patches.
If you refuse to do that, don't blame other people for not dealing with the
patch.
https://gcc.gnu.org/contribute.html#patches
>From gcc-bugs-return-664566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 22:14:34 2020
Return-Path: <gcc-bugs-return-664566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36295 invoked by alias); 5 Jan 2020 22:14:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36245 invoked by uid 48); 5 Jan 2020 22:14:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/90142] contrib/download_prerequisites uses test =Date: Sun, 05 Jan 2020 22:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
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-90142-4-JKgWCyjf6a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90142-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00292.txt.bz2
Content-length: 462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90142
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
P.S. I asked you to follow the correct procedure because I can't approve that
patch myself, and the people who can approve it expect patches on the mailing
lists, not here.
If you want the right people to see it, send it to the mailing list.
Don't complain that somebody who can't approve the patch tried to help you get
it reviewed.
>From gcc-bugs-return-664567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 23:36:22 2020
Return-Path: <gcc-bugs-return-664567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60385 invoked by alias); 5 Jan 2020 23: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 52410 invoked by uid 48); 5 Jan 2020 23:36:17 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93076] [10 Regression] internal compiler error: Segmentation fault during GIMPLE pass: cddce
Date: Sun, 05 Jan 2020 23:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc everconfirmed
Message-ID: <bug-93076-4-q8y3OVHwxf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93076-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93076-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00293.txt.bz2
Content-length: 872
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93076
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-05
CC| |law at redhat dot com
Summary|internal compiler error: |[10 Regression] internal
|Segmentation fault during |compiler error:
|GIMPLE pass: cddce |Segmentation fault during
| |GIMPLE pass: cddce
Ever confirmed|0 |1
--- Comment #1 from Jeffrey A. Law <law at redhat dot com> ---
My tester has tripped over a ton of these. Confirming.
>From gcc-bugs-return-664568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 05 23:37:38 2020
Return-Path: <gcc-bugs-return-664568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91642 invoked by alias); 5 Jan 2020 23:37:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91609 invoked by uid 48); 5 Jan 2020 23:37:34 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93077] [10 Regression] internal compiler error: in hash_operand during GIMPLE pass: fre
Date: Sun, 05 Jan 2020 23:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc short_desc everconfirmed
Message-ID: <bug-93077-4-EbRglFkySv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00294.txt.bz2
Content-length: 971
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93077
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-05
CC| |law at redhat dot com
Summary|internal compiler error: in |[10 Regression] internal
|hash_operand during GIMPLE |compiler error: in
|pass: fre |hash_operand during GIMPLE
| |pass: fre
Ever confirmed|0 |1
--- Comment #3 from Jeffrey A. Law <law at redhat dot com> ---
My tester is tripping over this as well building speedcrunch from Fedora with
-flto. Thus confirmed and a regression since this worked a couple weeks ago.
>From gcc-bugs-return-664569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:16:29 2020
Return-Path: <gcc-bugs-return-664569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41502 invoked by alias); 6 Jan 2020 00:16: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 41360 invoked by uid 48); 6 Jan 2020 00:16:24 -0000
From: "jiangning.liu at amperecomputing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93163] New: internal compiler error: verify_gimple failed
Date: Mon, 06 Jan 2020 00:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jiangning.liu at amperecomputing dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-93163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00295.txt.bz2
Content-length: 2688
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93163
Bug ID: 93163
Summary: internal compiler error: verify_gimple failed
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jiangning.liu at amperecomputing dot com
Target Milestone: ---
LLVM trunk build with gcc trunk exposed failure "internal compiler error:
verify_gimple failed".
$ g++ -O3 -c bad.cpp
bad.cpp: In constructor
‘{anonymous}::AArch64SIMDInstrOpt::AArch64SIMDInstrOpt()’:
bad.cpp:140602:3: error: incorrect sharing of tree nodes
140602 | AArch64SIMDInstrOpt() : MachineFunctionPass(ID) {
| ^~~~~~~~~~~~~~~~~~~
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR64RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR64RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR64RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR64RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR64RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR128RegClass;
bad.cpp:140602:3: error: incorrect sharing of tree nodes
*D.397057
D.397057->RC = FPR64RegClass;
during GIMPLE pass: cfg
bad.cpp:140602:3: internal compiler error: verify_gimple failed
0x100bbff verify_gimple_in_cfg(function*, bool)
../../gcc/gcc/tree-cfg.c:5445
0xebad33 execute_function_todo
../../gcc/gcc/passes.c:1983
0xebbc4b execute_todo
../../gcc/gcc/passes.c:2037
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
Bisect run shows the failure is related to commit
https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=279576
>From gcc-bugs-return-664570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:18:40 2020
Return-Path: <gcc-bugs-return-664570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48581 invoked by alias); 6 Jan 2020 00:18: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 48546 invoked by uid 48); 6 Jan 2020 00:18:37 -0000
From: "jiangning.liu at amperecomputing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/93163] internal compiler error: verify_gimple failed
Date: Mon, 06 Jan 2020 00:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jiangning.liu at amperecomputing dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-93163-4-rJe8JEYSXM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00296.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93163
--- Comment #1 from Jiangning Liu <jiangning.liu at amperecomputing dot com> ---
Created attachment 47591
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47591&action=edit
bad case from llvm build
>From gcc-bugs-return-664571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:23:18 2020
Return-Path: <gcc-bugs-return-664571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56609 invoked by alias); 6 Jan 2020 00:23:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53205 invoked by uid 48); 6 Jan 2020 00:23:14 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93163] internal compiler error: verify_gimple failed
Date: Mon, 06 Jan 2020 00:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: dependson
Message-ID: <bug-93163-4-W14jZPYV18@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00297.txt.bz2
Content-length: 534
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93163
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |93033
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Most likely a dup of bug 93033.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
[Bug 93033] [10 Regression] error: incorrect sharing of tree nodes
>From gcc-bugs-return-664572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:24:50 2020
Return-Path: <gcc-bugs-return-664572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58385 invoked by alias); 6 Jan 2020 00:24:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58129 invoked by uid 48); 6 Jan 2020 00:24:36 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93076] [10 Regression] internal compiler error: Segmentation fault during GIMPLE pass: cddce
Date: Mon, 06 Jan 2020 00:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: dependson
Message-ID: <bug-93076-4-JTeCMvVx1b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93076-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93076-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00298.txt.bz2
Content-length: 535
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93076
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |93033
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
My bet it is a dup of bug 93033.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
[Bug 93033] [10 Regression] error: incorrect sharing of tree nodes
>From gcc-bugs-return-664573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:26:24 2020
Return-Path: <gcc-bugs-return-664573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60115 invoked by alias); 6 Jan 2020 00:26:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60072 invoked by uid 48); 6 Jan 2020 00:26:20 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93077] [10 Regression] internal compiler error: in hash_operand during GIMPLE pass: fre
Date: Mon, 06 Jan 2020 00:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93077-4-XpmBVCd5JV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00299.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93077
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> ---
Yea. And note that Jason has committed a fix for 93033. I'll be spinning up
builds with today's snapshot in a few hours -- starting with all the stuff
that's currently failing. So we should know fairly quickly if this (and the
segfault in CDDCE) are DUPs.
>From gcc-bugs-return-664574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:48:04 2020
Return-Path: <gcc-bugs-return-664574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64491 invoked by alias); 6 Jan 2020 00:48:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57484 invoked by uid 48); 6 Jan 2020 00:47:59 -0000
From: "davidfink314 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93164] New: variadic template function passed an initializer list fails with argument count mismatch error rather than expected "couldn't deduce template parameter" error
Date: Mon, 06 Jan 2020 00:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davidfink314 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-93164-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00300.txt.bz2
Content-length: 2132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93164
Bug ID: 93164
Summary: variadic template function passed an initializer list
fails with argument count mismatch error rather than
expected "couldn't deduce template parameter" error
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: davidfink314 at gmail dot com
Target Milestone: ---
foo({x});
An initializer list passed to a template function can be a non-deduced context,
which can result in template argument deduction failing.
https://stackoverflow.com/questions/52924740/stdinitializer-list-braced-initialization-and-header
When this is a regular template argument, the error message is OK (mentions
template deduction failed with the template parameter name).
When this is a variadic template argument, errors about the number of arguments
are thrown instead, which are wrong and don't help the user correct their code.
Use gcc 9.2 -std=c++17 -Wall -Werror on godbolt, with the code below:
#include <initializer_list>
struct X {
template <class... Args>
X(Args&&... args) {
}
template<class... Args>
X& operator=(Args&&... args) {
return *this;
}
};
template<class... T> void variadic(T&&...) {}
template<class T> void single(T&&) {}
int main() {
X x;
// Expected error: no matching function for call to ... couldn't deduce
variadic template parameter 'T'
// Actual error: 'X& X::operator=()' must have exactly one argument
x = {0};
// Expected error: no matching function for call to ... couldn't deduce
variadic template parameter 'T'
// Actual error: too many arguments to function 'void variadic(T&& ...)
[with T = {}]'
variadic({0});
// Good error: error: no matching function for call to
'single(<brace-enclosed initializer list>)
// ... couldn't deduce template parameter 'T'
single({0});
return 0;
}
>From gcc-bugs-return-664575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 00:59:08 2020
Return-Path: <gcc-bugs-return-664575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15909 invoked by alias); 6 Jan 2020 00:59: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 15865 invoked by uid 48); 6 Jan 2020 00:59:04 -0000
From: "davidfink314 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93164] variadic template function passed an initializer list fails with argument count mismatch error rather than expected "couldn't deduce template parameter" error
Date: Mon, 06 Jan 2020 00:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: davidfink314 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-93164-4-NhC4PrucjR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93164-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93164-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00301.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93164
--- Comment #1 from David Fink <davidfink314 at gmail dot com> ---
Also reported to clang:
https://bugs.llvm.org/show_bug.cgi?id=43944
>From gcc-bugs-return-664576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 02:19:30 2020
Return-Path: <gcc-bugs-return-664576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93356 invoked by alias); 6 Jan 2020 02:19:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93304 invoked by uid 48); 6 Jan 2020 02:19:26 -0000
From: "redboltz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92156] Cannot in-place construct std::any with std::any
Date: Mon, 06 Jan 2020 02:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redboltz 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-92156-4-AC977cxwWW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00302.txt.bz2
Content-length: 737
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92156
Takatoshi Kondo <redboltz at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |redboltz at gmail dot com
--- Comment #1 from Takatoshi Kondo <redboltz at gmail dot com> ---
I've got a similar error on the following code:
[begin code]
#include <tuple>
#include <any>
int main() {
// std::pair : OK
std::any p = std::pair<std::any, std::any>(1, 1);
(void)p;
// std::tuple : ill formed
std::any t = std::tuple<std::any>(1);
(void)t;
}
[end code]
On Compiler Explorer: https://godbolt.org/z/gEHRmA
>From gcc-bugs-return-664577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 02:25:21 2020
Return-Path: <gcc-bugs-return-664577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98771 invoked by alias); 6 Jan 2020 02:25:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98716 invoked by uid 48); 6 Jan 2020 02:25:17 -0000
From: "jiangning.liu at amperecomputing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93163] internal compiler error: verify_gimple failed
Date: Mon, 06 Jan 2020 02:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jiangning.liu at amperecomputing dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93163-4-CG3cuNVPBR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00303.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93163
Jiangning Liu <jiangning.liu at amperecomputing dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jiangning Liu <jiangning.liu at amperecomputing dot com> ---
Confirmed that the issue has been fixed on trunk.
>From gcc-bugs-return-664578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 04:10:03 2020
Return-Path: <gcc-bugs-return-664578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70034 invoked by alias); 6 Jan 2020 04:10:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69926 invoked by uid 48); 6 Jan 2020 04:09:59 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/69047] memcpy is not as optimized as union is
Date: Mon, 06 Jan 2020 04:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-69047-4-v52SFdovGf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69047-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69047-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00304.txt.bz2
Content-length: 339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69047
--- Comment #11 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
Note I think this introduced a small optimization issue. I have a patch but I
have not been able to find a testcase which shows this issue without an
modified compiler.
>From gcc-bugs-return-664579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 06:43:40 2020
Return-Path: <gcc-bugs-return-664579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94832 invoked by alias); 6 Jan 2020 06:43:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94783 invoked by uid 48); 6 Jan 2020 06:43:36 -0000
From: "ncm at cantrip dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93165] New: avoidable 2x penalty on unpredicted overwrite
Date: Mon, 06 Jan 2020 06:43: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ncm at cantrip 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-93165-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00305.txt.bz2
Content-length: 4758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93165
Bug ID: 93165
Summary: avoidable 2x penalty on unpredicted overwrite
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ncm at cantrip dot org
Target Milestone: ---
=== Abstract:
In important cases where using a "conditional move" instruction would provide a
2x performance improvement, Gcc fails to generate the instruction. In testing,
a random field is sorted by the simplest possible Quicksort algorithm, varying
only the method for conditionally swapping values, with widely varying
runtimes, many substantially faster than `std::sort`. The 2x result is
obtainable only with Clang, which for amd64 generates cmov instructions.
A simple testing apparatus may be found at https://github.com/ncm/sortfast/
that depends only on shell tools.
=== Details:
The basic sort is:
```
int* partition(int* begin, int* end) {
int pivot = end[-1];
int* left = begin;
for (int* right = begin; right < end - 1; ++right) {
if (*right <= pivot) {
std::swap(*left, *right);
++left;
}
}
int tmp = *left; *left = end[-1], end[-1] = tmp;
return left;
}
void quicksort(int* begin, int* end) {
while (end - begin > 1) {
int* mid = partition(begin, end);
quicksort(begin, mid);
begin = mid + 1;
} }
```
which runs about as fast as `std::sort`, on truly random input.
Replacing the body of the loop in `partition()` above with
```
left += swap_if(*right <= pivot, *left, *right);
```
where `swap_if` is defined
```
inline bool swap_if(bool c, int& a, int& b) {
int ta = a, mask = -c;
a = (b & mask) | (ta & ~mask);
b = (ta & mask) | (b & ~mask);
return c;
}
```
the sort is substantially faster than `std::sort` compiled with Gcc. Compiled
with Clang 8 or later, it runs fully 2x as fast as `std::sort`. Clang
recognizes the pattern and substitutes `cmov` instructions. (Clang also unrolls
the loop, which helps a little.) Another formulation,
```
inline bool swap_if(bool c, int& a, int& b) {
int ta = a, tb = b;
a = c ? tb : ta;
b = c ? ta : tb;
return c;
}
```
also results in the same object code, with Clang, but is 2x slower compiled
with Gcc, which generates a branch. A third formulation,
```
inline bool swap_if(bool c, int& a, int& b) {
int v[2] = { a, b };
b = v[1-c], a = v[c];
return c;
}
```
is much faster than `std::sort` compiled by both Gcc and Clang, but detours
values through L1 cache, at some cost, so is slower than the `cmov` version. A
fourth version,
```
inline bool swap_if(bool c, int& a, int& b) {
int v[2] = { a, b };
a = v[c], b = v[!c];
return c;
}
```
is about the same speed as the third when built with Clang, but with Gcc is
quite a lot slower than `std::sort`. Order matters, somehow, as does the choice
of operator. (I don't know how to express a bug report for this last case.
Advice welcome.)
In
```
inline bool swap_if(bool c, int& a, int& b) {
int ta = a, tb = b;
a = c ? tb : ta;
// b = c ? ta : tb;
return c;
}
```
(at least when it is not inlined) Gcc seems happy to generate the `cmov`
instruction. Apparently the optimization code is very jealous about what else
is allowed in the basic block where a `cmov` is considered.
Finally, even with
```
inline bool swap_if(bool c, int& a, int& b) {
int ta = a, tb = b;
a = __builtin_expect_with_probability(c, 0, 0.5) ? tb : ta;
b = __builtin_expect_with_probability(c, 0, 0.5) ? ta : tb;
return c;
}
```
Gcc still will not generate the `cmov` instructions.
=== Discussion:
Replacing a branch with `cmov` may result in slower code, particularly on older
CPU targets. However, when the programmer provides direct information that the
branch is unpredictable, it seems like the compiler should be willing to act on
that expectation.
In that light, Clang's conversion of "`(mask & a)|(~mask & b)`" to `cmov` seems
to be universally correct. It is a portable formula that gives better results
than the branching version even without specific optimization, but may easily
be rewritten using `cmov` for even better results.
In addition, when `__builtin_expect_with_probability` is used to indicate
unpredictability, there seems to be no defensible reason not to rewrite the
expression to use `cmov`.
Finally, the indexed form of `swap_if` may be recognized and turned into `cmov`
instructions without worry that a predictable branch has been replaced,
avoiding the unnecessary detour through memory.
>From gcc-bugs-return-664580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 06:46:19 2020
Return-Path: <gcc-bugs-return-664580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96655 invoked by alias); 6 Jan 2020 06:46:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96622 invoked by uid 48); 6 Jan 2020 06:46:14 -0000
From: "ncm at cantrip dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93165] avoidable 2x penalty on unpredicted overwrite
Date: Mon, 06 Jan 2020 06:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ncm at cantrip dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93165-4-p48cEAHilB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00306.txt.bz2
Content-length: 232
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93165
--- Comment #1 from ncm at cantrip dot org ---
Created attachment 47592
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47592&action=edit
code demonstrating the failure
>From gcc-bugs-return-664581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 06:48:37 2020
Return-Path: <gcc-bugs-return-664581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14258 invoked by alias); 6 Jan 2020 06:48: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 14082 invoked by uid 48); 6 Jan 2020 06:48:23 -0000
From: "ncm at cantrip dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93165] avoidable 2x penalty on unpredicted overwrite
Date: Mon, 06 Jan 2020 06:48: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ncm at cantrip dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-93165-4-1sg0E0fLPQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00307.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93165
--- Comment #2 from ncm at cantrip dot org ---
Created attachment 47593
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47593&action=edit
a makefile
This duplicates code found on the linked archive.
E.g.:
make all
make CC=g++-9 INDEXED
make CC=clang++-9 ANDANDOR
make CC=clang++-9 INDEXED_PESSIMAL_ON_GCC
make CC=g++-9 CHECK=CHECK BOG
>From gcc-bugs-return-664582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:02:53 2020
Return-Path: <gcc-bugs-return-664582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127970 invoked by alias); 6 Jan 2020 08:02:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127925 invoked by uid 48); 6 Jan 2020 08:02:49 -0000
From: "tobias.loew at steag dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93155] Error when compiling Boost MP11 mp_similar
Date: Mon, 06 Jan 2020 08:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tobias.loew at steag dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93155-4-VXZVYdlPhZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93155-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00308.txt.bz2
Content-length: 354
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93155
Tobias Loew <tobias.loew at steag dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-664583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:12:22 2020
Return-Path: <gcc-bugs-return-664583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60845 invoked by alias); 6 Jan 2020 08:12:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60792 invoked by uid 48); 6 Jan 2020 08:12:18 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93166] New: [10 Regression] ICE in get_info_about_necessary_edges, at ipa-cp.c:4137 since r278893
Date: Mon, 06 Jan 2020 08:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-93166-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00309.txt.bz2
Content-length: 1805
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93166
Bug ID: 93166
Summary: [10 Regression] ICE in get_info_about_necessary_edges,
at ipa-cp.c:4137 since r278893
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: fxue at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Created attachment 47594
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47594&action=edit
Reduced test-case
Following is causing ICE:
$ c++ -shared k*.ii -flto -O2 -fPIC -fvisibility=hidden
during IPA pass: cp
lto1: internal compiler error: in get_info_about_necessary_edges, at
ipa-cp.c:4137
0x7b1f23 get_info_about_necessary_edges<ipa_polymorphic_call_context>
/home/marxin/Programming/gcc/gcc/ipa-cp.c:4137
0x7b1f23 decide_about_value<ipa_polymorphic_call_context>
/home/marxin/Programming/gcc/gcc/ipa-cp.c:5387
0x7b1f23 decide_whether_version_node
/home/marxin/Programming/gcc/gcc/ipa-cp.c:5496
0x7b1f23 ipcp_decision_stage
/home/marxin/Programming/gcc/gcc/ipa-cp.c:5633
0x7b1f23 ipcp_driver
/home/marxin/Programming/gcc/gcc/ipa-cp.c:5816
0x7b1f23 execute
/home/marxin/Programming/gcc/gcc/ipa-cp.c:5907
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
lto-wrapper: fatal error: c++ returned 1 exit status
compilation terminated.
/usr/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-664584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:12:53 2020
Return-Path: <gcc-bugs-return-664584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61808 invoked by alias); 6 Jan 2020 08:12:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61731 invoked by uid 48); 6 Jan 2020 08:12:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/93166] [10 Regression] ICE in get_info_about_necessary_edges, at ipa-cp.c:4137 since r278893
Date: Mon, 06 Jan 2020 08:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-93166-4-Y6JVSKgRAY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93166-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93166-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00310.txt.bz2
Content-length: 774
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93166
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-06
CC| |hubicka at gcc dot gnu.org,
| |jamborm at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
Known to fail| |10.0
>From gcc-bugs-return-664585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:20:52 2020
Return-Path: <gcc-bugs-return-664585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119523 invoked by alias); 6 Jan 2020 08:20:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119443 invoked by uid 48); 6 Jan 2020 08:20:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93134] [graphite] ICE: Segmentation fault in ISL
Date: Mon, 06 Jan 2020 08: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.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93134-4-JmDtIR8M6F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00311.txt.bz2
Content-length: 1422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93134
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
One another ICE for existing test-suite:
$ gfortran
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/dependency_58.f90 -O3
-fwrapv -floop-nest-optimize
during GIMPLE pass: graphite
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/dependency_58.f90:4:0:
4 | program main
|
internal compiler error: Segmentation fault
0xe5fa6f crash_signal
/home/marxin/Programming/gcc/gcc/toplev.c:328
0x7f6551d1a14f ???
/usr/src/debug/glibc-2.30-2.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x173e44e scop_get_dependences(scop*)
/home/marxin/Programming/gcc/gcc/graphite-dependences.c:316
0x173e937 optimize_isl
/home/marxin/Programming/gcc/gcc/graphite-optimize-isl.c:125
0x173e937 apply_poly_transforms(scop*)
/home/marxin/Programming/gcc/gcc/graphite-optimize-isl.c:211
0x1739140 graphite_transform_loops()
/home/marxin/Programming/gcc/gcc/graphite.c:467
0x1739670 graphite_transforms
/home/marxin/Programming/gcc/gcc/graphite.c:537
0x1739670 execute
/home/marxin/Programming/gcc/gcc/graphite.c:614
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-664586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:24:43 2020
Return-Path: <gcc-bugs-return-664586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123714 invoked by alias); 6 Jan 2020 08:24:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123119 invoked by uid 48); 6 Jan 2020 08:24:38 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93167] New: [graphite] One another ICE with isl-0.22
Date: Mon, 06 Jan 2020 08:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-93167-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00312.txt.bz2
Content-length: 1933
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93167
Bug ID: 93167
Summary: [graphite] One another ICE with isl-0.22
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
One another ICE:
$ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/torture/pr68955.c
-floop-parallelize-all -Ofast -c
during GIMPLE pass: graphite
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/torture/pr68955.c: In
function ‘main’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.dg/torture/pr68955.c:36:1:
internal compiler error: Segmentation fault
36 | main ()
| ^~~~
0xdef32f crash_signal
/home/marxin/Programming/gcc/gcc/toplev.c:328
0x7f520f25714f ???
/usr/src/debug/glibc-2.30-2.1.x86_64/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x16cc2ba scop_get_dependences(scop*)
/home/marxin/Programming/gcc/gcc/graphite-dependences.c:320
0x16c9a3f translate_isl_ast_to_gimple::scop_to_isl_ast(scop*)
/home/marxin/Programming/gcc/gcc/graphite-isl-ast-to-gimple.c:1399
0x16cb231 graphite_regenerate_ast_isl(scop*)
/home/marxin/Programming/gcc/gcc/graphite-isl-ast-to-gimple.c:1479
0x16c6f93 graphite_transform_loops()
/home/marxin/Programming/gcc/gcc/graphite.c:471
0x16c74b0 graphite_transforms
/home/marxin/Programming/gcc/gcc/graphite.c:537
0x16c74b0 execute
/home/marxin/Programming/gcc/gcc/graphite.c:614
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-664587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:25:00 2020
Return-Path: <gcc-bugs-return-664587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125333 invoked by alias); 6 Jan 2020 08:25:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125232 invoked by uid 48); 6 Jan 2020 08:24:56 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93167] [graphite] One another ICE with isl-0.22
Date: Mon, 06 Jan 2020 08:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: 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 see_also target_milestone everconfirmed
Message-ID: <bug-93167-4-pGB3ntXQlH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93167-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93167-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00313.txt.bz2
Content-length: 612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93167
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-06
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=93134
Target Milestone|--- |10.0
Ever confirmed|0 |1
>From gcc-bugs-return-664588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:38:28 2020
Return-Path: <gcc-bugs-return-664588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9014 invoked by alias); 6 Jan 2020 08:38:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8952 invoked by uid 48); 6 Jan 2020 08:38:23 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93033] [10 Regression] error: incorrect sharing of tree nodes
Date: Mon, 06 Jan 2020 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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93033-4-ojfxvng7MR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00314.txt.bz2
Content-length: 157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
--- Comment #12 from Arseny Solokha <asolokha at gmx dot com> ---
I believe this PR can be closed now.
>From gcc-bugs-return-664589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:55:06 2020
Return-Path: <gcc-bugs-return-664589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59652 invoked by alias); 6 Jan 2020 08:55:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59591 invoked by uid 48); 6 Jan 2020 08:55:02 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93168] New: Error messages are full of control code garbage
Date: Mon, 06 Jan 2020 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93168-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00315.txt.bz2
Content-length: 755
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93168
Bug ID: 93168
Summary: Error messages are full of control code garbage
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: segher at gcc dot gnu.org
Target Milestone: ---
For example,
nestfunc-1.c: In function 'f':
nestfunc-1.c:22:1: warning: control reaches end of non-void function
[]8;;https://gcc.gnu.org/onlinedocs/gcc/Warning-Options.html#index-Wreturn-type-Wreturn-type]8;;]
(and it doesn't show the warning option, either, any more).
This stuff should not be enabled by default.
>From gcc-bugs-return-664590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 08:59:39 2020
Return-Path: <gcc-bugs-return-664590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62703 invoked by alias); 6 Jan 2020 08:59: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 62652 invoked by uid 48); 6 Jan 2020 08:59:35 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93168] Error messages are full of control code garbage
Date: Mon, 06 Jan 2020 08:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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-93168-4-0DKJTXFAXJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93168-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93168-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00316.txt.bz2
Content-length: 371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93168
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
The actual control stuff is eaten by bugzilla, but it makes just as little
sense like this. There is an escape before the ] I think, but it messes up
the display (in different and interesting ways depending on terminal), so
not completely sure.
>From gcc-bugs-return-664591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 09:04:53 2020
Return-Path: <gcc-bugs-return-664591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47582 invoked by alias); 6 Jan 2020 09:04: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 47512 invoked by uid 48); 6 Jan 2020 09:04:49 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/93168] Error messages are full of control code garbage
Date: Mon, 06 Jan 2020 09: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: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc component
Message-ID: <bug-93168-4-fPWFom0erx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93168-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93168-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00317.txt.bz2
Content-length: 863
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93168
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
CC| |dmalcolm at gcc dot gnu.org,
| |pinskia at gcc dot gnu.org
Component|middle-end |other
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Currently -fdiagnostics-urls is enabled to auto but it seems like for some
terminals, it detects the wrong thing.
Which terminal are you using, and what version?
See https://gcc.gnu.org/ml/gcc-patches/2019-12/msg01409.html also. Though
--with-diagnostics-urls has not gone in yet.
>From gcc-bugs-return-664592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 09:05:32 2020
Return-Path: <gcc-bugs-return-664592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53986 invoked by alias); 6 Jan 2020 09:05: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 53936 invoked by uid 48); 6 Jan 2020 09:05:28 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93165] avoidable 2x penalty on unpredicted overwrite
Date: Mon, 06 Jan 2020 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93165-4-vhjfwdp6eh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00318.txt.bz2
Content-length: 1222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93165
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
The compiler has no way of knowing ahead of time that you will be evaluating
the result on random data; for mostly-sorted arrays branching is arguably
preferable.
__builtin_expect_with_probability is a poor proxy for unpredictability: a
condition that is true every other time leads to a branch that is both very
predictable and has probability 0.5.
I think what you really need is a way to express branchless selection in the
source code when you know you need it but the compiler cannot see that on its
own. Other algorithms like constant-time checks for security-sensitive
applications probably also need such computational primitive.
So perhaps an unpopular opinion, but I'd say a __builtin_branchless_select(c,
a, b) (guaranteed to live throughout optimization pipeline as a non-branchy
COND_EXPR) is badly missing.
>From gcc-bugs-return-664593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 09:09:10 2020
Return-Path: <gcc-bugs-return-664593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56951 invoked by alias); 6 Jan 2020 09:09:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56893 invoked by uid 48); 6 Jan 2020 09:09:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93156] abused nonnull attribute evokes new segfault in gcc 10 since Nov 4 commit, 0fb958ab8aa
Date: Mon, 06 Jan 2020 09: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93156-4-ZdVbWYmN8O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93156-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00319.txt.bz2
Content-length: 2564
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93156
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Bruno Haible from comment #8)
> (In reply to Andrew Pinski from comment #6)
> > a?-1:0 is transformed into -1 before we figure out that a is always true; an
> > ordering difference.
>
> Fortunately the GCC optimization affects only the return value of
> null_ptr(). It does not cause side effects to occur that shouldn't occur.
>
> Test case:
> =========================================================================
> extern char *canonicalize_file_name (const char *__name)
> __attribute__ ((__nonnull__ (1)));
> extern int rand (void);
> extern void brick_the_hard_disk (void);
>
> /* Return NULL. */
> static void *
> null_ptr (void)
> {
> unsigned int x = rand ();
> unsigned int y = x * x;
> /* The following statement is equivalent to if (false),
> since a square is always congruent to 0 or 1 mod 4. */
> if (y & 2) {
> brick_the_hard_disk ();
> return (void *) -1;
> } else
> return (void *) 0;
> }
>
> int
> main (void)
> {
> return !!canonicalize_file_name (null_ptr ());
> }
An optimizing compiler optimizes the assumption that UB doesn't occur, because
when it occurs, anything can happen. The above testcase has an unconditional
UB when passing NULL to function argument that requires NULL is not passed to
it
and thus the compiler when seeing that a value outside the range [(void *)1,
(void *) -2] (i.e. either NULL or (void *) -1) is passed to it and the
requirement for nonnull is that it is not NULL figures out that the range must
be [(void *) -1, (void *) -1] and replaces it with the constant all ones
pointer.
If say y & 4 was used instead of y & 2, the UB would be only conditional, and
in any case, the compiler can't call brick_the_hard_disk before reaching the
UB, but once invoking UB, it can call anything, format the disk in other ways
and perform anything else.
So the only thing we should take from the above for the compiler is optimize in
ccp that x*x has the second least significant bit clear. Will handle that
today.
>From gcc-bugs-return-664594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 09:13:52 2020
Return-Path: <gcc-bugs-return-664594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66956 invoked by alias); 6 Jan 2020 09:13:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64614 invoked by uid 55); 6 Jan 2020 09:13:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92860] [8/9/10 regression] Global flags affected by -O settings are clobbered by optimize attribute
Date: Mon, 06 Jan 2020 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92860-4-35pd3FyJsz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00320.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92860
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Mon Jan 6 09:13:15 2020
New Revision: 279895
URL: https://gcc.gnu.org/viewcvs?rev=279895&root=gcc&view=rev
Log:
Mark param_max_combine_insns with Optimization keyword.
PR tree-optimization/92860
* params.opt: Mark param_max_combine_insns with Optimization
keyword.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/params.opt
>From gcc-bugs-return-664595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 09:14:10 2020
Return-Path: <gcc-bugs-return-664595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75303 invoked by alias); 6 Jan 2020 09:14: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 75243 invoked by uid 48); 6 Jan 2020 09:14:06 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93165] avoidable 2x penalty on unpredicted overwrite
Date: Mon, 06 Jan 2020 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93165-4-NAnBveiARO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00321.txt.bz2
Content-length: 1042
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93165
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #3)
> So perhaps an unpopular opinion, but I'd say a
> __builtin_branchless_select(c, a, b) (guaranteed to live throughout
> optimization pipeline as a non-branchy COND_EXPR) is badly missing.
I am going to say otherwise. Many of the time conditional move is faster than
using a branch; even if the branch is predictable (there are a few exceptions)
on most non-Intel/AMD targets. This is because the conditional move is just
one cycle and only a "predictable" branch is one cyle too.
It is even worse when doing things like:
if (a && b)
where on aarch64, this can be done using only one cmp followed by one ccmp.
NOTE on PowerPC, you could use in theory crand/cror (though this is not done
currently and I don't know if they are profitable in any recent design).
Plus aarch64 has conditional add and a few other things which improve the idea
of a conditional move.
>From gcc-bugs-return-664597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:06:41 2020
Return-Path: <gcc-bugs-return-664597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65805 invoked by alias); 6 Jan 2020 10:06: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 65727 invoked by uid 48); 6 Jan 2020 10:06:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/83411] function multiversioning should clone the entire sub-callgraph
Date: Mon, 06 Jan 2020 10:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83411-4-OhrVvTzNkS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83411-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83411-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00323.txt.bz2
Content-length: 664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83411
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Yury Gribov from comment #5)
> (In reply to Martin Liška from comment #4)
> > So finding
> > a point like your 'loop' and using flatten attribute can guarantee the
> > call-chain is fully optimized. Would be interesting to come up with more
> > examples from real applications.
>
> As this is not immediately obvious and/or googleable, perhaps we could add a
> note to docs for pragma target and target/target_clones attributes?
Sure, I've just sent a patch:
https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00107.html
>From gcc-bugs-return-664596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:06:32 2020
Return-Path: <gcc-bugs-return-664596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65067 invoked by alias); 6 Jan 2020 10:06: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 64984 invoked by uid 48); 6 Jan 2020 10:06:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93161] Remove extra operator== for comparison categories in <compare> not in standard
Date: Mon, 06 Jan 2020 10:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93161-4-wVmiPwxc8E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00322.txt.bz2
Content-length: 1153
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93161
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |INVALID
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Wesley Shillingford from comment #0)
> However the last line fails to compile with MSVC. After checking the
> standards library support document operator==(strong_ordering,
> strong_ordering) is not mentioned:
> http://wg21.link/p0768
That paper is more than two years old. The current working draft does specify
the equality operators, e.g. [cmp.strongord]
friend constexpr
bool operator==(strong_ordering v, strong_ordering w) noexcept = default;
> Even worse is that value types are not even standardised for comparison
> operators! (thanks Bo Persson):
> http://wg21.link/P1946
That paper was approved two months ago and is part of the current working
draft.
I don't see a libstdc++ bug here.
>From gcc-bugs-return-664598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:19:56 2020
Return-Path: <gcc-bugs-return-664598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98267 invoked by alias); 6 Jan 2020 10:19:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98198 invoked by uid 48); 6 Jan 2020 10:19:51 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] New: [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00324.txt.bz2
Content-length: 2219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
Bug ID: 93169
Summary: [10 regression] Variable incorrectly put into readonly
section.
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
This is testcase by Mark Williams who also bisected it
template <typename a> class b {
struct c {
a h;
constexpr c() {}
~c() {}
} d;
};
struct e {
int g;
e() { g = 2; }
};
main() { static const b<e> f; }
$ /aux/hubicka/trunk-install/bin/g++ -O2 t.C
t.C:12:1: warning: ISO C++ forbids declaration of ‘main’ with no type
[-Wreturn-type]
12 | main() { static const b<e> f; }
| ^~~~
$ ./a.out
Segmentation fault
$ /aux/hubicka/9-install/bin/g++ -O2 t.C
At.C:12:6: warning: ISO C++ forbids declaration of ‘main’ with no type
[-Wreturn-type]
12 | main() { static const b<e> f; }
| ^
$ ./a.out
It is caused by
commit 88bbd5a94e06eb42a5ed84a3ff6da498bea229e9 (HEAD, refs/bisect/bad)
Author: mpolacek <mpolacek@138bc75d-0d04-0410-961f-82ee72b054a4>
AuthorDate: Mon Aug 19 13:59:13 2019 +0000
Commit: mpolacek <mpolacek@138bc75d-0d04-0410-961f-82ee72b054a4>
CommitDate: Mon Aug 19 13:59:13 2019 +0000
PR c++/91264 - detect modifying const objects in constexpr.
* constexpr.c (modifying_const_object_error): New function.
(cxx_eval_call_expression): Set TREE_READONLY on a CONSTRUCTOR of
a const-qualified object after it's been fully constructed.
(modifying_const_object_p): New function.
(cxx_eval_store_expression): Detect modifying a const object
during constant expression evaluation.
(cxx_eval_increment_expression): Use a better location when
building
up the store.
(cxx_eval_constant_expression) <case DECL_EXPR>: Mark a constant
object's constructor TREE_READONLY.
and goes away after reverting the cxx_eval_call_expression hunk.
>From gcc-bugs-return-664599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:22:28 2020
Return-Path: <gcc-bugs-return-664599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100718 invoked by alias); 6 Jan 2020 10:22:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100651 invoked by uid 48); 6 Jan 2020 10:22:24 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-93169-4-5RIFhsOpd9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00325.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-06
CC| |polacek at redhat dot com
Ever confirmed|0 |1
>From gcc-bugs-return-664600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:25:14 2020
Return-Path: <gcc-bugs-return-664600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103090 invoked by alias); 6 Jan 2020 10:25:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103045 invoked by uid 48); 6 Jan 2020 10:25:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-93169-4-VmK1VeVsxL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00326.txt.bz2
Content-length: 353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Target Milestone|--- |10.0
>From gcc-bugs-return-664601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:28:05 2020
Return-Path: <gcc-bugs-return-664601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107571 invoked by alias); 6 Jan 2020 10:28: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 107471 invoked by uid 48); 6 Jan 2020 10:28:01 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93169-4-yuiYr2crB5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00327.txt.bz2
Content-length: 301
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I want to say b<e>::c::c is not a valid constexpr constructor. Because
b<e>::c's field h's constructor is not constexr. If that is the case, then
should be accepts invalid code.
>From gcc-bugs-return-664602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:40:37 2020
Return-Path: <gcc-bugs-return-664602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125718 invoked by alias); 6 Jan 2020 10:40: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 125679 invoked by uid 48); 6 Jan 2020 10:40:33 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93169-4-G9byrpT6ST@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00328.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> I want to say b<e>::c::c is not a valid constexpr constructor. Because
> b<e>::c's field h's constructor is not constexr. If that is the case, then
> should be accepts invalid code.
Or maybe I don't understand constexpr that well :). e::e() is definitely not a
valid constexpr though :).
>From gcc-bugs-return-664603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:47:35 2020
Return-Path: <gcc-bugs-return-664603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130803 invoked by alias); 6 Jan 2020 10:47:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130732 invoked by uid 48); 6 Jan 2020 10:47:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93169-4-dWWoAF0WVz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00329.txt.bz2
Content-length: 726
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > I want to say b<e>::c::c is not a valid constexpr constructor. Because
> > b<e>::c's field h's constructor is not constexr. If that is the case, then
> > should be accepts invalid code.
It's a template. If the constructor doesn't meet the requirements of a
constexpr constructor, then the constexpr specifier is just ignored. So it's
not invalid.
> Or maybe I don't understand constexpr that well :). e::e() is definitely
> not a valid constexpr though :).
Which is OK because it's not marked constexpr.
>From gcc-bugs-return-664604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 10:52:14 2020
Return-Path: <gcc-bugs-return-664604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7547 invoked by alias); 6 Jan 2020 10:52: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 7501 invoked by uid 48); 6 Jan 2020 10:52:10 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 10:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93169-4-H2B8mM1YpE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00330.txt.bz2
Content-length: 768
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to Andrew Pinski from comment #2)
> > (In reply to Andrew Pinski from comment #1)
> > > I want to say b<e>::c::c is not a valid constexpr constructor. Because
> > > b<e>::c's field h's constructor is not constexr. If that is the case, then
> > > should be accepts invalid code.
>
> It's a template. If the constructor doesn't meet the requirements of a
> constexpr constructor, then the constexpr specifier is just ignored. So it's
> not invalid.
Oh, ok. I should really get familiar with all of the newer C++ features; I
have not learned enough about anything past C++03 :).
>From gcc-bugs-return-664605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 11:07:56 2020
Return-Path: <gcc-bugs-return-664605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116499 invoked by alias); 6 Jan 2020 11:07:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107950 invoked by uid 48); 6 Jan 2020 11:07:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 11: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: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93169-4-ZkFXpWV5BC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00331.txt.bz2
Content-length: 228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The relevant rule is http://eel.is/c++draft/dcl.constexpr#7 but that whole
subclause is new since C++03 :-)
>From gcc-bugs-return-664606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 11:16:21 2020
Return-Path: <gcc-bugs-return-664606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7522 invoked by alias); 6 Jan 2020 11: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 7457 invoked by uid 48); 6 Jan 2020 11:16:12 -0000
From: "wezrule at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93161] Remove extra operator== for comparison categories in <compare> not in standard
Date: Mon, 06 Jan 2020 11: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: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wezrule at hotmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-93161-4-LcLwy06sHD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00332.txt.bz2
Content-length: 848
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93161
--- Comment #2 from Wesley Shillingford <wezrule at hotmail dot com> ---
Thanks for the swift reply.
(In reply to Jonathan Wakely from comment #1)
> That paper is more than two years old. The current working draft does
> specify the equality operators, e.g. [cmp.strongord]
I didn't realise those papers are not revised if there are changes, noted for
the future thanks.
> > http://wg21.link/P1946
> That paper was approved two months ago and is part of the current working
> draft.
You are correct, I've now the mailings list, which lists it as approved.
Perhaps I misinterpreted Bo Persson's comment.
> I don't see a libstdc++ bug here.
Yep seems so, I will inform MSVC if this is not fixed next preview (P1946 does
not currently appear on their conformance list yet), many thanks!
>From gcc-bugs-return-664607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 11:42:50 2020
Return-Path: <gcc-bugs-return-664607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80874 invoked by alias); 6 Jan 2020 11:42:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80729 invoked by uid 48); 6 Jan 2020 11:42:45 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92924] [10 regression] reproducible indirect call profile merging causes 80% slowdown in Firefox pref-reftest-singletons id-getter microbenchmarks
Date: Mon, 06 Jan 2020 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 11.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92924-4-uegFhx4Ud4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92924-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92924-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00333.txt.bz2
Content-length: 758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92924
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
>
> So the histogram of destinations is indeed greatly dominated by one
> estination but there are very many others (not all are listed since I
> started dropping them).
>
> One way to make reproducible merging better is to drop destinations with
> small trip counts before merging, but I am not sure it would help everywhere.
Yes, that makes sense. We should do it both during merging and during
instrumentation. If we choose a drop level equal to 10^2 or 10^3 we should not
probably introduce a divergence.
One solution could be to interpret a profile when it's read and make a decision
about validity and invalidity.
>From gcc-bugs-return-664608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 11:45:32 2020
Return-Path: <gcc-bugs-return-664608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90482 invoked by alias); 6 Jan 2020 11:45:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90324 invoked by uid 48); 6 Jan 2020 11:45:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92924] [10 regression] reproducible indirect call profile merging causes 80% slowdown in Firefox pref-reftest-singletons id-getter microbenchmarks
Date: Mon, 06 Jan 2020 11:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
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: 11.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92924-4-9VMHFa1fVM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92924-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92924-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00334.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92924
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
> Yes, that makes sense. We should do it both during merging and during
> instrumentation. If we choose a drop level equal to 10^2 or 10^3 we should
> not probably introduce a divergence.
Instrumentation is resolved fine.
>From gcc-bugs-return-664609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 11:52:45 2020
Return-Path: <gcc-bugs-return-664609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98978 invoked by alias); 6 Jan 2020 11:52:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98943 invoked by uid 48); 6 Jan 2020 11:52:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93161] Remove extra operator== for comparison categories in <compare> not in standard
Date: Mon, 06 Jan 2020 11:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-93161-4-EY7XY8fpd4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00335.txt.bz2
Content-length: 363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93161
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Once a proposal is approved for inclusion in the working draft any further
changes are made to the content in the draft, not the proposal. The original
proposal is of historical interest only, what matters is the content of the
working draft.
>From gcc-bugs-return-664610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 12:04:08 2020
Return-Path: <gcc-bugs-return-664610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19075 invoked by alias); 6 Jan 2020 12:04: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 18985 invoked by uid 48); 6 Jan 2020 12:04:04 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9/10 Regression] aarch64 target testcases fail after r265398
Date: Mon, 06 Jan 2020 12:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-bmYq2hYp6p@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: 2020-01/txt/msg00336.txt.bz2
Content-length: 942
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
--- Comment #58 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jeffrey A. Law from comment #39)
> We've actually got an RMW insn when combine starts. But...
> Trying 17, 7 -> 13:
> 17: r92:DI=r95:DI
> REG_DEAD r95:DI
> 7: zero_extract(r92:DI,0x8,0)=r93:DI
> REG_DEAD r93:DI
> 13: x0:DI=r92:DI
> REG_DEAD r92:DI
> Failed to match this instruction:
> (set (reg/i:DI 0 x0)
> (ior:DI (and:DI (reg:DI 95)
> (const_int -256 [0xffffffffffffff00]))
> (reg:DI 93)))
>
> We've torn the damn thing apart via expand_field_assignment. Worse yet,
> that naturally splits and results in:
I have been thinking about how to fix this for the last 6 years :). It would
be useful if we could produce the following two instructions:
zero_extract(r95:DI,0x8,0)=r93
x0=r95
But I have not figured out how to produce that.
>From gcc-bugs-return-664611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 12:11:24 2020
Return-Path: <gcc-bugs-return-664611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31050 invoked by alias); 6 Jan 2020 12:11:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30949 invoked by uid 48); 6 Jan 2020 12:11:16 -0000
From: "wezrule at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/93161] Remove extra operator== for comparison categories in <compare> not in standard
Date: Mon, 06 Jan 2020 12:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wezrule at hotmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
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-93161-4-iR026y2lTu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93161-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00337.txt.bz2
Content-length: 162
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93161
--- Comment #4 from Wesley Shillingford <wezrule at hotmail dot com> ---
Great, thanks for the confirmation
>From gcc-bugs-return-664612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 12:21:52 2020
Return-Path: <gcc-bugs-return-664612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44657 invoked by alias); 6 Jan 2020 12: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 44626 invoked by uid 48); 6 Jan 2020 12:21:47 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93170] New: [10 Regression] wrong code due to use of a call-clobbered register
Date: Mon, 06 Jan 2020 12:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget attachments.created
Message-ID: <bug-93170-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00338.txt.bz2
Content-length: 2563
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93170
Bug ID: 93170
Summary: [10 Regression] wrong code due to use of a
call-clobbered register
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Created attachment 47595
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47595&action=edit
reduced testcase
Output:
$ x86_64-pc-linux-gnu-gcc -O2 -frename-registers -fno-tree-forwprop
-fno-tree-fre -fira-algorithm=priority -mstringop-strategy=loop
--param=hot-bb-frequency-fraction=0 testcase.c -Wno-psabi
$ ./a.out
Aborted
In the assembly output:
...
# testcase.c:17: d = __builtin_popcountll (-((v64u8) i)[0]);
movsx rdi, esi # tmp233, tmp232
mov QWORD PTR [rsp+32], r10 # %sfp, _70
mov QWORD PTR [rsp+40], r11 # %sfp, _70
mov QWORD PTR [rsp+16], rbx # %sfp, _67
call __popcountdi2 #
...
# testcase.c:16: j >>= ((v64u128) h <= j);
shrd r12, rsi, cl # tmp254,, tmp253
xor ebx, ebx #
# testcase.c:18: return a + g + j;
mov QWORD PTR [rsp+128], rax #, tmp251
# testcase.c:16: j >>= ((v64u128) h <= j);
shr rsi, cl #, tmp253
...
The __popcountdi2 call clobbers rsi, and the caller uses the clobbered value.
$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-279889-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/10.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-279889-checking-yes-rtl-df-extra-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 10.0.0 20200105 (experimental) (GCC)
>From gcc-bugs-return-664613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 12:26:07 2020
Return-Path: <gcc-bugs-return-664613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51727 invoked by alias); 6 Jan 2020 12:26:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51089 invoked by uid 48); 6 Jan 2020 12:26:02 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9/10 Regression] aarch64 target testcases fail after r265398
Date: Mon, 06 Jan 2020 12:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-h7c4yRhaj3@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: 2020-01/txt/msg00339.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
--- Comment #59 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #58)
> (In reply to Jeffrey A. Law from comment #39)
> > Failed to match this instruction:
> > (set (reg/i:DI 0 x0)
> > (ior:DI (and:DI (reg:DI 95)
> > (const_int -256 [0xffffffffffffff00]))
> > (reg:DI 93)))
> I have been thinking about how to fix this for the last 6 years :). It
> would be useful if we could produce the following two instructions:
> zero_extract(r95:DI,0x8,0)=r93
> x0=r95
>
> But I have not figured out how to produce that.
You either do a define_split (splitting the above ior thing into the two
insns you want, during combine itself), or you do a define_insn_and_split,
allowing this whole thing as a single rtl insn (perhaps only before split1,
or whatever works best).
>From gcc-bugs-return-664614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 12:48:56 2020
Return-Path: <gcc-bugs-return-664614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82128 invoked by alias); 6 Jan 2020 12: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 81424 invoked by uid 48); 6 Jan 2020 12:48:21 -0000
From: "ncm at cantrip dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93165] avoidable 2x penalty on unpredicted overwrite
Date: Mon, 06 Jan 2020 12:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ncm at cantrip dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93165-4-iWxR6cPdSa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93165-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00340.txt.bz2
Content-length: 1613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93165
--- Comment #5 from ncm at cantrip dot org ---
(In reply to Alexander Monakov from comment #3)
> The compiler has no way of knowing ahead of time that you will be evaluating
> the result on random data; for mostly-sorted arrays branching is arguably
> preferable.
>
> __builtin_expect_with_probability is a poor proxy for unpredictability: a
> condition that is true every other time leads to a branch that is both very
> predictable and has probability 0.5.
If putting it in made my code slower, I would take it back out. The only value
it has is if it changes something. If it doesn't improve matters, I need to try
something else. For it to do nothing helps nobody.
> I think what you really need is a way to express branchless selection in the
> source code when you know you need it but the compiler cannot see that on
> its own. Other algorithms like constant-time checks for security-sensitive
> applications probably also need such computational primitive.
>
> So perhaps an unpopular opinion, but I'd say a
> __builtin_branchless_select(c, a, b) (guaranteed to live throughout
> optimization pipeline as a non-branchy COND_EXPR) is badly missing.
We can quibble over whether the name of the intrinsic means anything with a
value of 0.5, but no other meaning would be useful.
But in general I would rather write portable code to get the semantics I need.
I don't have a preference between the AND/OR notation and the indexing version,
except that the former seems like a more generally useful optimization. Best
would be both.
>From gcc-bugs-return-664615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 13:08:49 2020
Return-Path: <gcc-bugs-return-664615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8777 invoked by alias); 6 Jan 2020 13: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 8119 invoked by uid 48); 6 Jan 2020 13:08:42 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9/10 Regression] aarch64 target testcases fail after r265398
Date: Mon, 06 Jan 2020 13:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-89gkSA46QH@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: 2020-01/txt/msg00341.txt.bz2
Content-length: 1265
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
--- Comment #60 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #59)
> You either do a define_split (splitting the above ior thing into the two
> insns you want, during combine itself), or you do a define_insn_and_split,
> allowing this whole thing as a single rtl insn (perhaps only before split1,
> or whatever works best).
That won't work for the above folding as you need to know the non-zero bits of
r93 match up with the constant to the "and" (-256).
Also this really should be a generic as I originally saw this issue on MIPS :).
Here is a testcase which you will see the same issue as insv_1.c on
powerpc64-linux-gnu (for little-endian just swap around the fields of the
struct):
typedef struct bitfield
{
unsigned short eight1: 8;
unsigned short eight: 8;
} bitfield;
bitfield
bfi1 (bitfield a, unsigned *b)
{
a.eight = *b;
return a;
}
bitfield
bfi1_1 (bitfield a, unsigned b)
{
a.eight = b;
return a;
}
NOTICE how bfi1_1 uses one rlwimi while bfi1 has rlwinm followed by or but
could just used rlwimi . This is a generic problem of combine wanting to use
nonzerobits but that sometimes can remove "important" information.
>From gcc-bugs-return-664616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 13:55:36 2020
Return-Path: <gcc-bugs-return-664616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64199 invoked by alias); 6 Jan 2020 13:55:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64120 invoked by uid 48); 6 Jan 2020 13:55:32 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93171] New: rldimi is sometimes not produced because combine gets in the way
Date: Mon, 06 Jan 2020 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-93171-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00342.txt.bz2
Content-length: 2010
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93171
Bug ID: 93171
Summary: rldimi is sometimes not produced because combine gets
in the way
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: pinskia at gcc dot gnu.org
Target Milestone: ---
Target: powerpc64-linux-gnu
Take:
typedef unsigned long long uint64_t;
typedef uint64_t cvmx_pow_tag_type_t;
typedef uint64_t cvmx_pow_tag_op_t;
typedef union
{
uint64_t u64;
struct
{
uint64_t no_sched : 1;
uint64_t unused : 2;
uint64_t index :13;
cvmx_pow_tag_op_t op : 4;
uint64_t unused2 : 2;
uint64_t qos : 3;
uint64_t grp : 4;
cvmx_pow_tag_type_t type : 3;
uint64_t tag :32;
} s_cn38xx;
struct {
uint64_t no_sched : 1;
cvmx_pow_tag_op_t op : 4;
uint64_t unused1 : 16;
uint64_t grp : 6;
uint64_t unused3 : 3;
cvmx_pow_tag_type_t type : 2;
uint64_t tag :32;
} s_cn68xx_other;
} cvmx_pow_tag_req_t;
int c;
#define CVMX_POW_TAG_OP_SWTAG 0
void f(uint64_t *a, int tag, int tag_type)
{
cvmx_pow_tag_req_t tag_req;
tag_req.u64 = 0;
if (c)
{
tag_req.s_cn68xx_other.op = 0;
tag_req.s_cn68xx_other.tag = tag;
asm("":"+r"(tag_req.u64));
tag_req.s_cn68xx_other.type = tag_type;
}
else
{
tag_req.s_cn38xx.op = 0;
tag_req.s_cn38xx.tag = tag;
// asm("":"+r"(tag_req.u64));
tag_req.s_cn38xx.type = tag_type;
}
*a = tag_req.u64;
}
--- CUT ---
On the path which contains the asm, we get:
rldimi 4,5,32,30
While on the other path, we get:
rldic 5,5,32,29
or 4,4,5
NOTE the asm is just there to force combine not to happen :).
>From gcc-bugs-return-664617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 13:59:45 2020
Return-Path: <gcc-bugs-return-664617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86608 invoked by alias); 6 Jan 2020 13:59: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 83056 invoked by uid 48); 6 Jan 2020 13:59:41 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87763] [9/10 Regression] aarch64 target testcases fail after r265398
Date: Mon, 06 Jan 2020 13:59: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: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87763-4-3ZMj9dMk13@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: 2020-01/txt/msg00343.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87763
--- Comment #61 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #60)
> NOTICE how bfi1_1 uses one rlwimi while bfi1 has rlwinm followed by or but
> could just used rlwimi . This is a generic problem of combine wanting to
> use nonzerobits but that sometimes can remove "important" information.
Actually it is worse because I had it backwards (due to me lowering bit-field
accesses on the tree level and producing BIT_INSERT_EXPR which just happen to
produce better code for bfi1 but worse code for bfi1_1), without my lowering
bfi1 uses three instructions to do the insert.
Also I filed PR 93171 (for a powerpc64 case) to show what is going on and
without the side comments. The code from PR 93171 came from an inner kernel of
the network forwarding code on Octeon (MIPS) processor.
>From gcc-bugs-return-664618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 14:07:02 2020
Return-Path: <gcc-bugs-return-664618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6998 invoked by alias); 6 Jan 2020 14:07: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 6774 invoked by uid 48); 6 Jan 2020 14:06:58 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93172] New: with AVX512 masked mov assigning zero can use {z}
Date: Mon, 06 Jan 2020 14:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-93172-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00344.txt.bz2
Content-length: 1290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93172
Bug ID: 93172
Summary: with AVX512 masked mov assigning zero can use {z}
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
Testcase (cf. https://godbolt.org/z/DMQf9-):
#include <x86intrin.h>
// missed optimization:
__m512 f(__m512 x, __mmask16 k) {
return _mm512_mask_mov_ps(x, _knot_mask16(k), __m512());
}
// f should be translated like this:
__m512 g(__m512 x, __mmask16 k) {
return _mm512_maskz_mov_ps(k, x);
}
GCC translates f to:
vxorps xmm1, xmm1, xmm1
kmovw k1, edi
vmovaps zmm0{k1}, zmm1
. It could use:
kmovd k0, edi
knotw k1, k0
vmovaps zmm0 {k1} {z}, zmm0
like g does. I.e. whenever a constant zero is assigned under a negated
write-mask, the {z} variant of vmovaps should be used.
Clang even uses {z} for `_mm512_mask_mov_ps(x, k, __m512())` (i.e. without
negation of the mask), which is unclear whether that's actually a
pessimization: https://godbolt.org/z/Nn4qXz
>From gcc-bugs-return-664619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 14:09:38 2020
Return-Path: <gcc-bugs-return-664619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33817 invoked by alias); 6 Jan 2020 14:09: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 27789 invoked by uid 48); 6 Jan 2020 14:09:34 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/93170] [10 Regression] wrong code due to use of a call-clobbered register
Date: Mon, 06 Jan 2020 14:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work target_milestone everconfirmed
Message-ID: <bug-93170-4-vBLeN5eDXg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93170-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93170-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00345.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93170
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-06
CC| |marxin at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
Known to work| |9.2.0
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r276318.
>From gcc-bugs-return-664620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 14:27:49 2020
Return-Path: <gcc-bugs-return-664620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62093 invoked by alias); 6 Jan 2020 14:27: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 62039 invoked by uid 48); 6 Jan 2020 14:27:45 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93169] [10 regression] Variable incorrectly put into readonly section.
Date: Mon, 06 Jan 2020 14: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: 10.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-93169-4-Z7EpWNYRMl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00346.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93169
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
>From gcc-bugs-return-664621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 15:22:37 2020
Return-Path: <gcc-bugs-return-664621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74157 invoked by alias); 6 Jan 2020 15:22:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74043 invoked by uid 55); 6 Jan 2020 15:22:33 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79592] incomplete diagnostic "is not usable as a constexpr function because:"
Date: Mon, 06 Jan 2020 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79592-4-zJwNnqB6qn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00347.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79592
--- Comment #7 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Author: nathan
Date: Mon Jan 6 15:22:02 2020
New Revision: 279902
URL: https://gcc.gnu.org/viewcvs?rev=279902&root=gcc&view=rev
Log:
PR c++/79592 adjust testcase
https://gcc.gnu.org/ml/gcc-patches/2020-01/msg00127.html
* g++.dg/ubsan/vptr-4.C: Add expected error.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/ubsan/vptr-4.C
>From gcc-bugs-return-664622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 15:23:31 2020
Return-Path: <gcc-bugs-return-664622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94907 invoked by alias); 6 Jan 2020 15:23:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94825 invoked by uid 55); 6 Jan 2020 15:23:26 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79592] incomplete diagnostic "is not usable as a constexpr function because:"
Date: Mon, 06 Jan 2020 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-79592-4-bwdyfHccRM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00348.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79592
--- Comment #8 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Author: nathan
Date: Mon Jan 6 15:22:54 2020
New Revision: 279903
URL: https://gcc.gnu.org/viewcvs?rev=279903&root=gcc&view=rev
Log:
PR c++/79592
* g++.dg/ubsan/vptr-4.C: Add expected error.
Modified:
branches/c++-modules/gcc/testsuite/g++.dg/ubsan/vptr-4.C
>From gcc-bugs-return-664623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 15:31:47 2020
Return-Path: <gcc-bugs-return-664623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65331 invoked by alias); 6 Jan 2020 15:31: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 64848 invoked by uid 48); 6 Jan 2020 15:31:41 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93138] [10 regression] elaborated type specifier visibility check problem
Date: Mon, 06 Jan 2020 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93138-4-JMAQNFtI1G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93138-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00349.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93138
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-664626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 15:47:57 2020
Return-Path: <gcc-bugs-return-664626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65534 invoked by alias); 6 Jan 2020 15:47: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 65214 invoked by uid 48); 6 Jan 2020 15:47:52 -0000
From: "lutztonineubert at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91369] Implement P0784R7: constexpr new
Date: Mon, 06 Jan 2020 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lutztonineubert at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91369-4-eyDg0Fwruc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91369-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00352.txt.bz2
Content-length: 907
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91369
--- Comment #28 from Toni Neubert <lutztonineubert at gmail dot com> ---
Thank you very much again for your fast help. Your patch works for this test
case.
I have another test case which fails. (Maybe more..., I am sorry).
//main.cpp: in ‘constexpr’ expansion of ‘test3()’
//main.cpp: in ‘constexpr’ expansion of ‘(& b)->bar::~bar()’
//main.cpp: in ‘constexpr’ expansion of ‘(&((bar*)this)->bar::f)->foo::~foo()’
//main.cpp error: deallocation of already deallocated storage
struct foo {
constexpr foo(int* i) : ptr{i} {}
constexpr ~foo() {
delete ptr;
}
int* ptr;
};
struct bar {
foo f{new int};
};
constexpr auto test3() {
bar b;
return true;
}
static_assert(test3());
>From gcc-bugs-return-664624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 15:47:03 2020
Return-Path: <gcc-bugs-return-664624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61833 invoked by alias); 6 Jan 2020 15:47: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 61743 invoked by uid 48); 6 Jan 2020 15:46:57 -0000
From: "joel at airwebreathe dot org.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93005] Redundant NEON loads/stores from stack are not eliminated
Date: Mon, 06 Jan 2020 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel at airwebreathe dot org.uk
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93005-4-5vrDZZbSxV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00350.txt.bz2
Content-length: 562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93005
--- Comment #4 from Joel Holdsworth <joel at airwebreathe dot org.uk> ---
Results for clang and MSVC are similar:
clang trunk:
foo(__simd128_int32_t):
push {r11, lr}
mov r11, sp
sub sp, sp, #24
bfc sp, #0, #4
mov r0, sp
vst1.32 {d0, d1}, [r0]
vld1.64 {d0, d1}, [r0:128]
mov sp, r11
pop {r11, pc}
...but even though these other compilers don't do any better on ARM, I still
think my original point stands.
>From gcc-bugs-return-664625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 15:47:33 2020
Return-Path: <gcc-bugs-return-664625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64233 invoked by alias); 6 Jan 2020 15:47:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64177 invoked by uid 48); 6 Jan 2020 15:47:29 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/92991] [10 regression] g++.dg/ubsan/vptr-4.C fails starting with r279473
Date: Mon, 06 Jan 2020 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-92991-4-6BTutOdEWT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92991-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92991-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00351.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92991
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |nathan at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #1 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
Fixed by r279902. Sorry, didn't know this PR had been filed.
>From gcc-bugs-return-664627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:10:10 2020
Return-Path: <gcc-bugs-return-664627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38551 invoked by alias); 6 Jan 2020 16:10: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 38337 invoked by uid 48); 6 Jan 2020 16:10:05 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/93162] [10 Regression] gcc/fortran/trans-openmp.c:2469:50: runtime error: load of value 145992800, which is not a valid value for type 'ar_type' since r279628
Date: Mon, 06 Jan 2020 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-93162-4-XGUhqod38h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93162-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93162-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00353.txt.bz2
Content-length: 710
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93162
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47596
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47596&action=edit
gcc10-pr93162.patch
Untested fix.
When the code has been added, components weren't allowed in map clause or the
OpenACC clauses, so it didn't check for REF_ARRAY.
>From gcc-bugs-return-664630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:18:28 2020
Return-Path: <gcc-bugs-return-664630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69944 invoked by alias); 6 Jan 2020 16:18:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69610 invoked by uid 48); 6 Jan 2020 16:18:24 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/70928] Load simple float constants via VSX operations on PowerPC
Date: Mon, 06 Jan 2020 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-70928-4-CiTZfJ6Se5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70928-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70928-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00356.txt.bz2
Content-length: 451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70928
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jens.seifert at de dot ibm.com
--- Comment #3 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
*** Bug 93128 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-664629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:18:28 2020
Return-Path: <gcc-bugs-return-664629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69886 invoked by alias); 6 Jan 2020 16:18:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69563 invoked by uid 48); 6 Jan 2020 16:18:23 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93128] PPC small floating point constants can be constructed using vector operations
Date: Mon, 06 Jan 2020 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-93128-4-OYFO0RHtQ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93128-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93128-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00355.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93128
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |wschmidt at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
This is a duplicate of PR70928.
*** This bug has been marked as a duplicate of bug 70928 ***
>From gcc-bugs-return-664628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:18:17 2020
Return-Path: <gcc-bugs-return-664628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68934 invoked by alias); 6 Jan 2020 16:18: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 68191 invoked by uid 48); 6 Jan 2020 16:18:12 -0000
From: "sbergman at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93173] New: "error: incorrect sharing of tree nodes" and "internal compiler error: verify_gimple failed"
Date: Mon, 06 Jan 2020 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sbergman at redhat dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-93173-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00354.txt.bz2
Content-length: 1869
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93173
Bug ID: 93173
Summary: "error: incorrect sharing of tree nodes" and "internal
compiler error: verify_gimple failed"
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: sbergman at redhat dot com
Target Milestone: ---
I think this only started recently on GCC trunk, I observe it at least with a
build based on today's 62a72308e1c5479bb3a9e8cacd45d49db219aaec "New bitfield
testcases":
> $ cat test.cc
> template<typename> struct S1 {
> S1(S1 &);
> ~S1();
> };
> struct S2 {
> S1<void> x;
> int y;
> int z;
> };
> void f(S1<void> x, int y, int z) { new S2{x, y, z}; }
> $ g++ -c test.cc
> test.cc: In function ‘void f(S1<void>, int, int)’:
> test.cc:10:6: error: incorrect sharing of tree nodes
> 10 | void f(S1<void> x, int y, int z) { new S2{x, y, z}; }
> | ^
> MEM[(struct S2 *)D.2374]
> MEM[(struct S2 *)D.2374].z = z;
> during GIMPLE pass: cfg
> test.cc:10:6: internal compiler error: verify_gimple failed
> 0xfda96a verify_gimple_in_cfg(function*, bool)
> ../../src/gcc/tree-cfg.c:5445
> 0xec1caf execute_function_todo
> ../../src/gcc/passes.c:1983
> 0xec2aec do_per_function
> ../../src/gcc/passes.c:1638
> 0xec2aec execute_todo
> ../../src/gcc/passes.c:2037
> Please submit a full bug report,
> with preprocessed source if appropriate.
> Please include the complete backtrace with any bug report.
> See <https://gcc.gnu.org/bugs/> for instructions.
(I assume this is a different issue than open issue 93033, given my build
includes b5cabe5e4b2778223d7a910ac3a5bbd61bff007c "PR c++/93033 - incorrect
tree node sharing with array init.")
>From gcc-bugs-return-664633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:39:41 2020
Return-Path: <gcc-bugs-return-664633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89918 invoked by alias); 6 Jan 2020 16:39: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 89836 invoked by uid 48); 6 Jan 2020 16:39:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93106] [c++2a] Deleted move constructor is not selected when returning an automatic variable
Date: Mon, 06 Jan 2020 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-93106-4-1EBBaIBz6P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00359.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93106
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2020-01-06
CC| |jason at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-664632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:39:30 2020
Return-Path: <gcc-bugs-return-664632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89204 invoked by alias); 6 Jan 2020 16:39:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89113 invoked by uid 48); 6 Jan 2020 16:39:26 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93106] [c++2a] Deleted move constructor is not selected when returning an automatic variable
Date: Mon, 06 Jan 2020 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93106-4-odhIjkJmin@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93106-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00358.txt.bz2
Content-length: 245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93106
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Confirmed. check_return_expr can't use convert_for_initialization to test
whether to treat the returned lvalue as an rvalue.
>From gcc-bugs-return-664631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:39:12 2020
Return-Path: <gcc-bugs-return-664631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88181 invoked by alias); 6 Jan 2020 16:39:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88142 invoked by uid 48); 6 Jan 2020 16:39:08 -0000
From: "acsawdey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93130] PPC simple memset not inlined
Date: Mon, 06 Jan 2020 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: acsawdey at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: acsawdey at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-93130-4-J1l6ROxpjz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93130-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93130-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00357.txt.bz2
Content-length: 556
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93130
acsawdey at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-06
CC| |acsawdey at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |acsawdey at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-664634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:39:42 2020
Return-Path: <gcc-bugs-return-664634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89975 invoked by alias); 6 Jan 2020 16:39:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89843 invoked by uid 48); 6 Jan 2020 16:39:38 -0000
From: "acsawdey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93129] PPC memset not using vector instruction on >= Power8
Date: Mon, 06 Jan 2020 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: acsawdey at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: acsawdey at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-93129-4-9x4XShTVm5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93129-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93129-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00360.txt.bz2
Content-length: 556
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93129
acsawdey at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2020-01-06
CC| |acsawdey at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |acsawdey at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-664637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:40:22 2020
Return-Path: <gcc-bugs-return-664637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92170 invoked by alias); 6 Jan 2020 16:40: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 91973 invoked by uid 48); 6 Jan 2020 16:40:18 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93077] [10 Regression] internal compiler error: in hash_operand during GIMPLE pass: fre
Date: Mon, 06 Jan 2020 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93077-4-KX1KU68rtp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93077-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93077-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00363.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93077
Bug 93077 depends on bug 93033, which changed state.
Bug 93033 Summary: [10 Regression] error: incorrect sharing of tree nodes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-664636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:40:22 2020
Return-Path: <gcc-bugs-return-664636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92098 invoked by alias); 6 Jan 2020 16:40: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 91956 invoked by uid 48); 6 Jan 2020 16:40:18 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/93076] [10 Regression] internal compiler error: Segmentation fault during GIMPLE pass: cddce
Date: Mon, 06 Jan 2020 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93076-4-J0cmg386UX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93076-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93076-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00362.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93076
Bug 93076 depends on bug 93033, which changed state.
Bug 93033 Summary: [10 Regression] error: incorrect sharing of tree nodes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-664638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:40:22 2020
Return-Path: <gcc-bugs-return-664638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92251 invoked by alias); 6 Jan 2020 16:40: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 92000 invoked by uid 48); 6 Jan 2020 16:40:18 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93163] internal compiler error: verify_gimple failed
Date: Mon, 06 Jan 2020 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93163-4-g8CNM5qm7L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00364.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93163
Bug 93163 depends on bug 93033, which changed state.
Bug 93033 Summary: [10 Regression] error: incorrect sharing of tree nodes
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-664635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:40:21 2020
Return-Path: <gcc-bugs-return-664635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92029 invoked by alias); 6 Jan 2020 16:40:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91905 invoked by uid 48); 6 Jan 2020 16:40:17 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/93033] [10 Regression] error: incorrect sharing of tree nodes
Date: Mon, 06 Jan 2020 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-93033-4-LPaoDjvVvb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93033-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00361.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93033
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-664639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:43:58 2020
Return-Path: <gcc-bugs-return-664639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124094 invoked by alias); 6 Jan 2020 16:43: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 123885 invoked by uid 48); 6 Jan 2020 16:43:53 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/12333] [DR 272] Explicit call to MyClass::~MyClass() not allowed
Date: Mon, 06 Jan 2020 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 3.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-12333-4-9k4VK2gpQQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-12333-4@http.gcc.gnu.org/bugzilla/>
References: <bug-12333-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00365.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12333
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #20 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-664640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:43:58 2020
Return-Path: <gcc-bugs-return-664640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124175 invoked by alias); 6 Jan 2020 16:43: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 123956 invoked by uid 48); 6 Jan 2020 16:43:53 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/23287] [4.2 regression] Explicitly invoking destructor of template class in a template and is dependent
Date: Mon, 06 Jan 2020 16:43: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: 3.4.4
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.2.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-23287-4-0nGyzLzj2a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-23287-4@http.gcc.gnu.org/bugzilla/>
References: <bug-23287-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00366.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23287
Bug 23287 depends on bug 12333, which changed state.
Bug 12333 Summary: [DR 272] Explicit call to MyClass::~MyClass() not allowed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12333
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-664641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:43:58 2020
Return-Path: <gcc-bugs-return-664641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124257 invoked by alias); 6 Jan 2020 16:43: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 124001 invoked by uid 48); 6 Jan 2020 16:43:54 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/29843] [meta-bug] C++98 standard conformance issues
Date: Mon, 06 Jan 2020 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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-29843-4-IiEjeejlUS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-29843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00367.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29843
Bug 29843 depends on bug 12333, which changed state.
Bug 12333 Summary: [DR 272] Explicit call to MyClass::~MyClass() not allowed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=12333
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-664642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 16:53:41 2020
Return-Path: <gcc-bugs-return-664642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9404 invoked by alias); 6 Jan 2020 16:53:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9329 invoked by uid 48); 6 Jan 2020 16:53:36 -0000
From: "joel at airwebreathe dot org.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93005] Redundant NEON loads/stores from stack are not eliminated
Date: Mon, 06 Jan 2020 16:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel at airwebreathe dot org.uk
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93005-4-HHkvdRohH3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00368.txt.bz2
Content-length: 2627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93005
--- Comment #5 from Joel Holdsworth <joel at airwebreathe dot org.uk> ---
I found that if I make modified versions of the intrinsics in arm_neon.h that
are designed more along the lines of the x86_64 SSE intrinsics defined with a
simple pointer dereference, then gcc does the right thing [1].
#include <arm_neon.h>
__extension__ extern __inline void
__attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
vst1q_s32_fixed (int32_t * __a, int32x4_t __b)
{
*(int32x4_t*)__a = __b;
}
__extension__ extern __inline int32x4_t
__attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
vld1q_s32_fixed (const int32_t * __a)
{
return *(const int32x4_t*)__a;
}
int32x4_t foo(int32x4_t a)
{
int32_t temp[4];
vst1q_s32_fixed(temp, a);
return vld1q_s32_fixed(temp);
}
...compiles to:
foo(long __vector(4)):
bx lr
Is there any reason not to simply redefine vst1q_s32, vld1q_s32 and friends to
stop using builtins?
[1]https://godbolt.org/#g:!((g:!((g:!((h:codeEditor,i:(fontScale:14,j:2,lang:c%2B%2B,selection:(endColumn:2,endLineNumber:22,positionColumn:1,positionLineNumber:1,selectionStartColumn:2,selectionStartLineNumber:22,startColumn:1,startLineNumber:1),source:'%23include+%3Carm_neon.h%3E%0A%0A__extension__+extern+__inline+void%0A__attribute__++((__always_inline__,+__gnu_inline__,+__artificial__))%0Avst1q_s32_fixed+(int32_t+*+__a,+int32x4_t+__b)%0A%7B%0A++*(int32x4_t*)__a+%3D+__b%3B%0A%7D%0A%0A__extension__+extern+__inline+int32x4_t%0A__attribute__++((__always_inline__,+__gnu_inline__,+__artificial__))%0Avld1q_s32_fixed+(const+int32_t+*+__a)%0A%7B%0A++return+*(const+int32x4_t*)__a%3B%0A%7D%0A%0Aint32x4_t+foo(int32x4_t+a)%0A%7B%0A++++int32_t+temp%5B4%5D%3B%0A++++vst1q_s32_fixed(temp,+a)%3B%0A++++return+vld1q_s32_fixed(temp)%3B%0A%7D'),l:'5',n:'0',o:'C%2B%2B+source+%232',t:'0')),header:(),k:49.54010711093072,l:'4',m:50,n:'0',o:'',s:0,t:'0'),(g:!((h:compiler,i:(compiler:arm831,filters:(b:'0',binary:'1',commentOnly:'0',demangle:'0',directives:'0',execute:'1',intel:'0',libraryCode:'1',trim:'1'),fontScale:14,j:2,lang:c%2B%2B,libs:!(),options:'-O2+-march%3Darmv7-a+-mtune%3Dcortex-a8+-mfpu%3Dneon+-mfloat-abi%3Dhard',selection:(endColumn:1,endLineNumber:1,positionColumn:1,positionLineNumber:1,selectionStartColumn:1,selectionStartLineNumber:1,startColumn:1,startLineNumber:1),source:2),l:'5',n:'0',o:'ARM+gcc+8.3.1+(none)+(Editor+%232,+Compiler+%232)+C%2B%2B',t:'0')),header:(),l:'4',m:50,n:'0',o:'',s:0,t:'0')),k:100,l:'3',n:'0',o:'',t:'0')),version:4
>From gcc-bugs-return-664643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 17:01:59 2020
Return-Path: <gcc-bugs-return-664643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11583 invoked by alias); 6 Jan 2020 17:01:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10695 invoked by uid 48); 6 Jan 2020 17:01:54 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93005] Redundant NEON loads/stores from stack are not eliminated
Date: Mon, 06 Jan 2020 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: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93005-4-DribYcrzVl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00369.txt.bz2
Content-length: 1205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93005
--- Comment #6 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to Joel Holdsworth from comment #5)
> I found that if I make modified versions of the intrinsics in arm_neon.h
> that are designed more along the lines of the x86_64 SSE intrinsics defined
> with a simple pointer dereference, then gcc does the right thing [1].
>
>
> #include <arm_neon.h>
>
> __extension__ extern __inline void
> __attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
> vst1q_s32_fixed (int32_t * __a, int32x4_t __b)
> {
> *(int32x4_t*)__a = __b;
> }
>
> __extension__ extern __inline int32x4_t
> __attribute__ ((__always_inline__, __gnu_inline__, __artificial__))
> vld1q_s32_fixed (const int32_t * __a)
> {
> return *(const int32x4_t*)__a;
> }
>
> int32x4_t foo(int32x4_t a)
> {
> int32_t temp[4];
> vst1q_s32_fixed(temp, a);
> return vld1q_s32_fixed(temp);
> }
>
>
>
> ...compiles to:
>
> foo(long __vector(4)):
> bx lr
>
>
> Is there any reason not to simply redefine vst1q_s32, vld1q_s32 and friends
> to stop using builtins?
>
Did you test it with big-endian?
>From gcc-bugs-return-664644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 17:09:29 2020
Return-Path: <gcc-bugs-return-664644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68426 invoked by alias); 6 Jan 2020 17:09:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68406 invoked by uid 48); 6 Jan 2020 17:09:25 -0000
From: "joel at airwebreathe dot org.uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/93005] Redundant NEON loads/stores from stack are not eliminated
Date: Mon, 06 Jan 2020 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joel at airwebreathe dot org.uk
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-93005-4-tEG3J4PstM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93005-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00370.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93005
--- Comment #7 from Joel Holdsworth <joel at airwebreathe dot org.uk> ---
> Did you test it with big-endian?
Good question. It seems to do the right thing in both cases:
https://godbolt.org/z/7rDzAm
>From gcc-bugs-return-664645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 17:12:40 2020
Return-Path: <gcc-bugs-return-664645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77756 invoked by alias); 6 Jan 2020 17:12:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77712 invoked by uid 48); 6 Jan 2020 17:12:36 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/93134] [graphite] ICE: Segmentation fault in ISL
Date: Mon, 06 Jan 2020 17:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-93134-4-FyWW3fBzmc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93134-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2020-01/txt/msg00371.txt.bz2
Content-length: 553
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93134
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asolokha at gmx dot com
--- Comment #3 from Arseny Solokha <asolokha at gmx dot com> ---
(In reply to Martin Liška from comment #1)
> Confirmed with current trunk and isl-0.22. Apparently, isl-0.20 is fine.
Please at least add PR90004 to the See Also section.
>From gcc-bugs-return-664646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 06 18:06:39 2020
Return-Path: <gcc-bugs-return-664646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124883 invoked by alias); 6 Jan 2020 18:06: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 124872 invoked by uid 89); 6 Jan 2020 18:06:37 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=1.3 required=5.0 tests=AWL,BAYES_50,HTML_IMAGE_RATIO_04,HTML_MESSAGE,KAM_ADVERT2,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 spammy=unsub.php, UD:unsub.php, unsubphp, newsletter
X-HELO: expresspostermachine.com
Received: from expresspostermachine.com (HELO expresspostermachine.com) (74.208.26.91) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 06 Jan 2020 18:06:35 +0000
Received: from postermakerstudio.com (unknown [74.208.87.98]) by localhost.localdomain (Postfix) with ESMTPSA id 0A44619E854 for <gcc-bugs@gcc.gnu.org>; Mon, 6 Jan 2020 18:06:22 +0000 (UTC)
Date: Mon, 06 Jan 2020 18:06:00 -0000
To: gcc-bugs@gcc.gnu.org
From: Poster Studio <schools@expresspostermachine.com>
Reply-To: Poster Studio <schools@expresspostermachine.com>
Subject: A Poster Maker For Your School
Message-ID: <m0bbmRrJBXGmqmPYrxCT0rKsfkGfXxGcsp2k9aHkxc@postermakerstudio.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
X-SW-Source: 2020-01/txt/msg00372.txt.bz2
Content-length: 6295
Can't see this email?. View in browser
Make Giant School PostersWith One Button!
True, Full Color Letter-To-Poster!
With the Poster Studio Express, you can quickly and easily create giant posters by scanning letter sized originals and pressing one button!
Poster Makers Available In 13", 24", 36" 44" and 60" Sizes!
With the Poster Studio Express, any teacher or staff member can create wildly elaborate and engaging posters by simply pressing one button!No more expensive trips to your local printing store!
With Our Poster Templates,
Creativity Is Included.
The Poster Studio Express includes 100's of templates, 1,000's of fonts, and 100's of thousands of images! All making up the easiest and most complete way to quickly and easily produce economical, engaging and captivating classroom visuals that last!
Read More
We have packages available to suit any budget!
Visit Our Website For More Information
You are receiving this email because you have visited our site or asked us about the regular newsletter. This is a commercial email sent by Red Circle Solutions LLC. Poster Studio Express is a registered trademark of Red Circle Solutions. © 2019 Red Circle Solutions. 103 Godwin Ave, PMB 255, Midland Park, NJ 07432. 877-798-8951
Unsubscribe
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2020-01-02 10:16 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-93084-4@http.gcc.gnu.org/bugzilla/>
2019-12-30 11:02 ` [Bug tree-optimization/93084] [10 regression] Infinite loop in ipa-cp when building clang with LTO+PGO hubicka at ucw dot cz
2020-01-02 10:16 ` hubicka at ucw dot cz
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).