public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug fortran/92639] New: Error: Integer too big for its kind at (1)
@ 2019-11-23 17:11 gsocshubham at gmail dot com
2023-03-01 17:51 ` [Bug fortran/92639] " cessenat at gmail dot com
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: gsocshubham at gmail dot com @ 2019-11-23 17:11 UTC (permalink / raw)
To: gcc-bugs
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 430973 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639
Bug ID: 92639
Summary: Error: Integer too big for its kind at (1)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: gsocshubham at gmail dot com
Target Milestone: ---
For below testcase, I ran on godbolt.org GFORTRAN trunk. Here are some
observations -
gfortran throws an error for BGE intrinsic when the value of one of parameter
is -2147483648 which should not be according to permissible range of BGE, the
maximum range for default kind is (-2147483648, 2147483647)
derived as -2^31 to 2^31 - 1
whereas x86-64 ifort 19.0.0 (Intel's fortran compiler) gives output without
error.
--------------------------------TESTCASE-----------------------------------
subroutine print_pass_fail(expected, actual)
implicit none
logical :: actual, expected
if ( actual .eqv. expected )then
print *, "PASS"
else
print *, "FAIL"
end if
end subroutine print_pass_fail
program bge_test_base
implicit none
logical :: index
index = BGE(127, -2147483648);
!print *, index
call print_pass_fail (.true.,index)
end program
>From gcc-bugs-return-661111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 17:16:20 2019
Return-Path: <gcc-bugs-return-661111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49446 invoked by alias); 23 Nov 2019 17:16: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 49367 invoked by uid 48); 23 Nov 2019 17:16:13 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92639] Error: Integer too big for its kind at (1)
Date: Sat, 23 Nov 2019 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl 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-92639-4-zp5BVaFfYl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92639-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92639-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02905.txt.bz2
Content-length: 1676
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |kargl at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to Shubham Narlawar from comment #0)
> For below testcase, I ran on godbolt.org GFORTRAN trunk. Here are some
> observations -
>
> gfortran throws an error for BGE intrinsic when the value of one of
> parameter is -2147483648 which should not be according to permissible range
> of BGE, the maximum range for default kind is (-2147483648, 2147483647)
>
> derived as -2^31 to 2^31 - 1
>
> whereas x86-64 ifort 19.0.0 (Intel's fortran compiler) gives output without
> error.
>
>
> --------------------------------TESTCASE-----------------------------------
>
> subroutine print_pass_fail(expected, actual)
> implicit none
> logical :: actual, expected
> if ( actual .eqv. expected )then
> print *, "PASS"
> else
> print *, "FAIL"
> end if
> end subroutine print_pass_fail
> program bge_test_base
> implicit none
> logical :: index
> index = BGE(127, -2147483648);
> !print *, index
> call print_pass_fail (.true.,index)
> end program
There are no negative integers. There are integers and unary minus operator.
This means that "-2147483648" is parse as "unary minus 2147483648". 2147483648
is too big for its kind.
>From gcc-bugs-return-661112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 19:01:08 2019
Return-Path: <gcc-bugs-return-661112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109102 invoked by alias); 23 Nov 2019 19:01:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109017 invoked by uid 48); 23 Nov 2019 19:01:03 -0000
From: "jorrit at jorrit dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92640] New: Incorrect warning: exception of type 'const derived&' will be caught by earlier handler for 'const base&'
Date: Sat, 23 Nov 2019 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jorrit at jorrit dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92640-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02906.txt.bz2
Content-length: 1868
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92640
Bug ID: 92640
Summary: Incorrect warning: exception of type 'const derived&'
will be caught by earlier handler for 'const base&'
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jorrit at jorrit dot de
Target Milestone: ---
In the following program, the catch-clause for `derived` is taken, since
`derived` is derived privately from `base`. However, the compiler still emits
a warning that the catch clause for `derived` will nether be taken.
Compiled without any particular options.
> struct base {};
> class derived : base {};
>
> template<class>
> int check()
> {
> try {
> throw derived();
> }
> catch(const base &) { return 0; }
> catch(const derived &) { return 1; }
> }
>
> int main()
> {
> return check<int>();
> }
Compiler stderr
> <source>: In function 'int check()':
> <source>:11:3: warning: exception of type 'const derived&' will be caught
> 11 | catch(const derived &) { return 1; }
> | ^~~~~
> <source>:10:3: warning: by earlier handler for 'const base&'
> 10 | catch(const base &) { return 0; }
> | ^~~~~
The program exits with 1 when run, contradicting the compiler warning.
Could reproduce with the following version on godbolt,
https://godbolt.org/z/jerjHS:
- current trunk: g++ (Compiler-Explorer-Build) 10.0.0 20191122 (experimental)
- g++ (Compiler-Explorer-Build) 9.2.0
- g++ (Compiler-Explorer-Build) 8.3.0
- g++ (Compiler-Explorer-Build) 7.5.0
Note: this may or may not be a dup of Bug 69373. Though here it is not
(function) pointers, and only happens with the catch clauses inside a template
function.
>From gcc-bugs-return-661113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 19:06:42 2019
Return-Path: <gcc-bugs-return-661113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113175 invoked by alias); 23 Nov 2019 19:06:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113117 invoked by uid 48); 23 Nov 2019 19:06:38 -0000
From: "jorrit at jorrit dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvNjkzNzNdIEdDQyBlbWl0cyBpbmNvcnJlY3Qgd2FybmluZyB0?= =?UTF-8?B?aGF0ICJleGNlcHRpb24gb2YgdHlwZSDigJh2b2lkICgqKSgp4oCZIHdpbGwg?= =?UTF-8?B?YmUgY2F1Z2h0IGJ5IGVhcmxpZXIgaGFuZGxlciBmb3IgJ3ZvaWQqJyI=?Date: Sat, 23 Nov 2019 19: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: 6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jorrit at jorrit 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-69373-4-E5LUAUGWZN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69373-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69373-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02907.txt.bz2
Content-length: 574
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69373
Jö <jorrit at jorrit dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jorrit at jorrit dot de
--- Comment #1 from Jö <jorrit at jorrit dot de> ---
Came across this bug while filing a similar problem. Checked that this bug
still occurs with current trunk on godbolt (g++ (Compiler-Explorer-Build)
10.0.0 20191122 (experimental)). It does indeed still occur.
>From gcc-bugs-return-661114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 19:33:23 2019
Return-Path: <gcc-bugs-return-661114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4518 invoked by alias); 23 Nov 2019 19:33: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 4434 invoked by uid 48); 23 Nov 2019 19:33:19 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/91832] [10 Regression] ICE in scan_expr_access, at ipa-sra.c:1695 since r275982
Date: Sat, 23 Nov 2019 19:33: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: ice-on-valid-code
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-91832-4-NQSYVUwtwT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02908.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91832
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Yes, I believe it is.
>From gcc-bugs-return-661115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 19:55:40 2019
Return-Path: <gcc-bugs-return-661115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14744 invoked by alias); 23 Nov 2019 19:55:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14705 invoked by uid 48); 23 Nov 2019 19:55:36 -0000
From: "kokuam at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61414] enum class bitfield size-checking needs a separate warning flag controlling it
Date: Sat, 23 Nov 2019 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kokuam at hotmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-61414-4-p0gu66DvR3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61414-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61414-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02909.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61414
Alexander Kokushkin <kokuam at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kokuam at hotmail dot com
--- Comment #20 from Alexander Kokushkin <kokuam at hotmail dot com> ---
Unfortunately, it's still present in 9.2.0 and quite painful.
>From gcc-bugs-return-661116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 21:50:16 2019
Return-Path: <gcc-bugs-return-661116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88033 invoked by alias); 23 Nov 2019 21:50: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 87998 invoked by uid 48); 23 Nov 2019 21:50:12 -0000
From: "sagebar at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/92641] New: Function called from dead branch
Date: Sat, 23 Nov 2019 21:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sagebar at web dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-92641-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02910.txt.bz2
Content-length: 2206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92641
Bug ID: 92641
Summary: Function called from dead branch
Product: gcc
Version: 9.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: sagebar at web dot de
Target Milestone: ---
Created attachment 47339
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47339&action=edit
Listing of problematic code, and similar code that works correctly
Given something like this:```
extern unsigned int get_vla_size(void);
```
This is ok:```
if (0) {
(void)(int(*)[get_vla_size()])0;
} else {
(void)get_vla_size();
}
```
asm:```
call _Z12get_vla_sizev
```
However, re-writing this code to use the ?-operator causes `get_vla_size()` to
be called twice:```
0 ? (
(void)(int(*)[get_vla_size()])0
) : (
(void)get_vla_size()
);
```
asm:```
call _Z12get_vla_sizev
call _Z12get_vla_sizev
```
Note that the first call to `get_vla_size()` happens from within a dead branch,
meaning that the call should have been fully removed, or at the very least have
been skipped by an unconditional jump.
When the first branch is wrapped in statement-expressions, code once again
function as expected:```
0 ? ({
(void)(int(*)[get_vla_size()])0;
}) : (
(void)get_vla_size()
);
```
asm:```
call _Z12get_vla_sizev
```
This problem consistently appears when compiling for c++, regardless of
optimization level, and if I had to guess, it's probably related to the scope
in which some given type is declared, where `type-expr` in `{ int x; 0 ?
(type-expr)expr : expr; }` is declared in the same scope as `x`, and thereby
unconditionally initialized.
The problem can be reproduced using:```
g++ -S attached-file.cc && cat attached-file.s
```
and inspecting the produced output
Note: I hope that `middle-end` was the correct place to report this, and I'm
sorry if it isn't.
>From gcc-bugs-return-661117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 21:59:12 2019
Return-Path: <gcc-bugs-return-661117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93866 invoked by alias); 23 Nov 2019 21: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 93823 invoked by uid 48); 23 Nov 2019 21:59:08 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92641] VLA type finalized at the beginging of the statement rather at the point of use
Date: Sat, 23 Nov 2019 21:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.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 short_desc
Message-ID: <bug-92641-4-fT6LSfAL36@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92641-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92641-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02911.txt.bz2
Content-length: 983
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92641
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|middle-end |c++
Summary|Function called from dead |VLA type finalized at the
|branch |beginging of the statement
| |rather at the point of use
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The big question comes, where should the VLA type be finalized, at the use or
at the beginning of the statement.
Statement expressions create a new statement so you are seeing that.
I don't know the correct answer. Since VLA types are not part of the C++
standard, what GCC does currently might be considered the correct answer (and
most likely could not be implemented different either).
>From gcc-bugs-return-661118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 22:05:20 2019
Return-Path: <gcc-bugs-return-661118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98496 invoked by alias); 23 Nov 2019 22:05:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98437 invoked by uid 48); 23 Nov 2019 22:05:15 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92569] [8/9/10 Regression] gfortran read with end directive does not trigger with -ffrontend-optimize
Date: Sat, 23 Nov 2019 22:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92569-4-kWzJs8ULE6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92569-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92569-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02912.txt.bz2
Content-length: 281
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92569
--- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #8)
> Hope you don't mind if I take this.
Hi Thomas, just noticed this one. I can review for you when you are ready.
>From gcc-bugs-return-661119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Nov 23 22:28:41 2019
Return-Path: <gcc-bugs-return-661119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114941 invoked by alias); 23 Nov 2019 22:28: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 114916 invoked by uid 48); 23 Nov 2019 22:28:37 -0000
From: "sagebar at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92641] VLA type finalized at the beginging of the statement rather at the point of use
Date: Sat, 23 Nov 2019 22:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sagebar at web 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-92641-4-40fL4Jlcce@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92641-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92641-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02913.txt.bz2
Content-length: 1705
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92641
--- Comment #2 from sagebar at web dot de ---
(In reply to Andrew Pinski from comment #1)
> The big question comes, where should the VLA type be finalized, at the use
> or at the beginning of the statement.
>
> Statement expressions create a new statement so you are seeing that.
>
> I don't know the correct answer. Since VLA types are not part of the C++
> standard, what GCC does currently might be considered the correct answer
> (and most likely could not be implemented different either).
That may be so, however I find it extremely disconcerting that it is possible
to have the contents of a compile-time dead branch be able to affect the
generated assembly in ways that can cause some very real side-effects (function
calls) at runtime.
When I write a macro like `#define ifelse(c, tt, ff) ((c) ? (tt) : (ff))`, then
I really _have_ to be able to rely on the fact that whatever happens, and
whatever it is passed, _only_ 1 of `tt` or `ff` get evaluated at runtime, no
matter what happens between me invoking g++, and eventually running the
produced binary.
To answer the question as to when finalization of the type should happen: the
naive (and probably most comprehensible) answer would be at the end of the dead
?-branch, though I can see how that might be difficult since that branch
doesn't have its own scope.
I sadly don't know enough of how gcc in particular generates assembly, however
I do know how a generic compiler works, so one solution might be to compile `0
? vla-expr : other-expr' as `jmp 1f; vla-expr; jmp 2f; 1: other-expr; 2:` and
use peephole optimization to transform this into `other-expr;`
>From gcc-bugs-return-661120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 01:14:31 2019
Return-Path: <gcc-bugs-return-661120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70422 invoked by alias); 24 Nov 2019 01:14: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 70357 invoked by uid 48); 24 Nov 2019 01:14:22 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92642] New: Enhance shift-count-overflow output
Date: Sun, 24 Nov 2019 01:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02914.txt.bz2
Content-length: 1058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92642
Bug ID: 92642
Summary: Enhance shift-count-overflow output
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jg at jguk dot org
Target Milestone: ---
Could g++ enhance this warning ?
Suggestion:
A) Include the number of bits being shifted
B) Include the type of the value being shifted.
C) Include the size in bits of the type in (B).
#1 with x86-64 gcc (trunk)
<source>:2:15: warning: left shift count >= width of type
[-Wshift-count-overflow]
2 | size_t big = 1<<41;
| ~^~~~
Compiler returned: 0
Suggestion:
#1 with x86-64 gcc (trunk)
<source>:2:15: warning: left shift count '41' >= width of type 'int' (32bit)
[-Wshift-count-overflow]
2 | size_t big = 1<<41;
| ~^~~~
Compiler returned: 0
Code:
#include <stdio.h>
size_t big = 1<<41;
>From gcc-bugs-return-661121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 03:50:22 2019
Return-Path: <gcc-bugs-return-661121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82574 invoked by alias); 24 Nov 2019 03:50:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82547 invoked by uid 48); 24 Nov 2019 03:50:17 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92643] New: ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Date: Sun, 24 Nov 2019 03:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02915.txt.bz2
Content-length: 1425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
Bug ID: 92643
Summary: ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
% gmake check-fortran RUNTESTFLAGS="dg.exp=ISO_Fortran_binding_15.f90"
Running /usr/home/kargl/gcc/gcc/gcc/testsuite/gfortran.dg/dg.exp ...
FAIL: gfortran.dg/ISO_Fortran_binding_15.f90 -O0 execution test
FAIL: gfortran.dg/ISO_Fortran_binding_15.f90 -O1 execution test
FAIL: gfortran.dg/ISO_Fortran_binding_15.f90 -O2 execution test
FAIL: gfortran.dg/ISO_Fortran_binding_15.f90 -O3 -fomit-frame-pointer
-funroll-loops -fpeel-loops -ftracer -finline-functions execution test
FAIL: gfortran.dg/ISO_Fortran_binding_15.f90 -O3 -g execution test
FAIL: gfortran.dg/ISO_Fortran_binding_15.f90 -Os execution test
=== gfortran Summary ===
# of expected passes 6
# of unexpected failures 6
% svn info
Path: .
Working Copy Root Path: /usr/home/kargl/gcc/gcc
URL: svn://gcc.gnu.org/svn/gcc/trunk
Relative URL: ^/trunk
Repository Root: svn://gcc.gnu.org/svn/gcc
Repository UUID: 138bc75d-0d04-0410-961f-82ee72b054a4
Revision: 278648
>From gcc-bugs-return-661122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 03:59:46 2019
Return-Path: <gcc-bugs-return-661122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86941 invoked by alias); 24 Nov 2019 03: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 86915 invoked by uid 48); 24 Nov 2019 03:59:41 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92643] ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Date: Sun, 24 Nov 2019 03: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92643-4-8b2XLrH18b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02916.txt.bz2
Content-length: 792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
--- Comment #1 from kargl at gcc dot gnu.org ---
Copying ISO_Fortran_binding_15.c and ISO_Fortran_binding_15.f90 to /tmp.
Edit ISO_Fortran_binding_15.c to find the header file.
% ~/work/bin/gcc -c ISO_Fortran_binding_15.c
% gfcx -o z ISO_Fortran_binding_15.f90 ISO_Fortran_binding_15.o
% ./z
Segmentation fault (core dumped)
% ~/work/bin/gcc -c -g -o a.o ISO_Fortran_binding_15.c
% gfcx -o z -g ISO_Fortran_binding_15.f90 a.o
% ./z
Segmentation fault (core dumped)
% gdb831 ./z
(gdb) run
Starting program: /usr/home/kargl/tmp/z
Program received signal SIGSEGV, Segmentation fault.
main () at ISO_Fortran_binding_15.c:29
29 if (*(int *)dat.base_addr != 42)
I think that there is a 32-bit vs 64-bit problem with pointers.
>From gcc-bugs-return-661123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 04:12:05 2019
Return-Path: <gcc-bugs-return-661123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92996 invoked by alias); 24 Nov 2019 04:12: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 92956 invoked by uid 48); 24 Nov 2019 04:12:00 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92644] New: [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530
Date: Sun, 24 Nov 2019 04:12: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: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02917.txt.bz2
Content-length: 1345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92644
Bug ID: 92644
Summary: [9/10 Regression] ICE in wide_int_to_tree_1, at
tree.c:1530
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
g++-10.0.0-alpha20191117 snapshot (r278376) and 9.2.0 ICE when compiling the
following testcase w/ -O1 -fno-early-inlining:
int
x8 ()
{
return ([rn = nullptr] () { return rn; } ()) ? 1 : 0;
}
% g++-10.0.0-alpha20191117 -O1 -fno-early-inlining -c hfy7acky.C
during GIMPLE pass: phiopt
hfy7acky.C: In function 'int x8()':
hfy7acky.C:5:1: internal compiler error: in wide_int_to_tree_1, at tree.c:1530
5 | }
| ^
0x7ae494 wide_int_to_tree_1
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191117/work/gcc-10-20191117/gcc/tree.c:1530
0x10b76d4 minmax_replacement
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191117/work/gcc-10-20191117/gcc/tree-ssa-phiopt.c:1389
0x10bb49b tree_ssa_phiopt_worker
/var/tmp/portage/sys-devel/gcc-10.0.0_alpha20191117/work/gcc-10-20191117/gcc/tree-ssa-phiopt.c:348
>From gcc-bugs-return-661124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 05:11:56 2019
Return-Path: <gcc-bugs-return-661124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11832 invoked by alias); 24 Nov 2019 05:11: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 11767 invoked by uid 48); 24 Nov 2019 05:11:52 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69864] Fix various Wnarrowing minor issues
Date: Sun, 24 Nov 2019 05: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: 5.3.0
X-Bugzilla-Keywords: diagnostic, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-69864-4-ujPGTrfmY3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02918.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69864
--- Comment #15 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Manuel López-Ibáñez from comment #8)
[...snip...]
> and replace the kludge in cp/typeck2.c with it (possibly fixing PR69872
> along the way). Document when some warnings might be errors (like we have
> precise definitions for permerror/pedwarn).
(note that bug 69872 has since been fixed)
>From gcc-bugs-return-661125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 06:59:56 2019
Return-Path: <gcc-bugs-return-661125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8437 invoked by alias); 24 Nov 2019 06:59: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 8379 invoked by uid 48); 24 Nov 2019 06:59:51 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92100] Formatted stream IO irreproducible read with binary data in file
Date: Sun, 24 Nov 2019 06:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-92100-4-4KD1sOtOTX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02919.txt.bz2
Content-length: 1158
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92100
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org
--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Patch:
diff --git a/libgfortran/io/transfer.c b/libgfortran/io/transfer.c
index 6382d0dad09..bb104db3584 100644
--- a/libgfortran/io/transfer.c
+++ b/libgfortran/io/transfer.c
@@ -3273,8 +3273,9 @@ data_transfer_init_worker (st_parameter_dt *dtp, int
read_flag)
if (dtp->pos != dtp->u.p.current_unit->strm_pos)
{
- fbuf_flush (dtp->u.p.current_unit, dtp->u.p.mode);
- if (sseek (dtp->u.p.current_unit->s, dtp->pos - 1, SEEK_SET) <
0)
+ fbuf_reset (dtp->u.p.current_unit);
+ if (sseek (dtp->u.p.current_unit->s, dtp->pos - 1,
+ SEEK_SET) < 0)
{
generate_error (&dtp->common, LIBERROR_OS, NULL);
return;
>From gcc-bugs-return-661126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 09:17:34 2019
Return-Path: <gcc-bugs-return-661126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76403 invoked by alias); 24 Nov 2019 09:17:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76357 invoked by uid 48); 24 Nov 2019 09:17:30 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92643] ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Date: Sun, 24 Nov 2019 09: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92643-4-sNNyEmE7OE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02920.txt.bz2
Content-length: 172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
It also fails on aarch64-*-linux, both ILP32 and LP64.
>From gcc-bugs-return-661127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 09:47:26 2019
Return-Path: <gcc-bugs-return-661127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89488 invoked by alias); 24 Nov 2019 09:47:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89446 invoked by uid 48); 24 Nov 2019 09:47:20 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] New: Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Sun, 24 Nov 2019 09:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02921.txt.bz2
Content-length: 9893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
Bug ID: 92645
Summary: Hand written vector code is 450 times slower when
compiled with GCC compared to Clang
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hubicka at gcc dot gnu.org
Target Milestone: ---
Hi,
the attached are preprocessed files for Skia where Clang ifdefs was removed so
we get roughly same file for GCC and Clang. The internal loop of
_ZN3hsw16blit_row_color32EPjPKjij, _ZN3hsw16blit_row_color32EPjPKjij,
_ZN3hsw16blit_row_color32EPjPKjij and _ZN3hsw16blit_row_color32EPjPKjij
looks a lot worse when compiled by GCC then by clang.
I also added flatten to eliminate the inlining difference. Clang has heuristics
that makes functions with hand written vector code hot.
GCC code packs via stack:
0.43 â mov %ax,0xae(%rsp)
0.03 â movzbl 0x78(%rsp),%eax
0.02 â mov %cx,0xd8(%rsp)
0.02 â mov %ax,0xb0(%rsp)
0.54 â vpextrb $0x9,%xmm5,%eax
0.16 â mov %ax,0xb2(%rsp)
0.51 â vpextrb $0xa,%xmm5,%eax
0.21 â mov %ax,0xb4(%rsp)
0.16 â vpextrb $0xb,%xmm5,%eax
0.46 â mov %ax,0xb6(%rsp)
0.24 â vpextrb $0xc,%xmm5,%eax
0.28 â mov %ax,0xb8(%rsp)
0.41 â vpextrb $0xd,%xmm5,%eax
0.20 â mov %ax,0xba(%rsp)
0.47 â vpextrb $0xe,%xmm5,%eax
0.92 â mov %ax,0xbc(%rsp)
0.72 â vpextrb $0xf,%xmm5,%eax
1.24 â mov %ax,0xbe(%rsp)
10.94 â vmovdqa 0xa0(%rsp),%ymm4
0.02 â mov %cx,0xda(%rsp)
0.00 â mov %cx,0xdc(%rsp)
â mov %cx,0xde(%rsp)
10.34 â vpmullw 0xc0(%rsp),%ymm4,%ymm0
2.05 â vpaddw %ymm1,%ymm0,%ymm0
0.50 â vpaddw %ymm3,%ymm0,%ymm0
0.00 â mov %r9,0x58(%rsp)
0.52 â vpsrlw $0x8,%ymm0,%ymm0
0.39 â vpextrw $0x0,%xmm0,%eax
0.69 â mov %al,%r8b
0.17 â vpextrw $0x1,%xmm0,%eax
0.51 â mov %r8,0x50(%rsp)
6.87 â vmovdqa 0x50(%rsp),%xmm5
1.08 â vpinsrb $0x1,%eax,%xmm5,%xmm1
0.00 â vpextrw $0x2,%xmm0,%eax
0.73 â vpinsrb $0x2,%eax,%xmm1,%xmm1
0.02 â vpextrw $0x3,%xmm0,%eax
0.75 â vpinsrb $0x3,%eax,%xmm1,%xmm1
0.10 â vpextrw $0x4,%xmm0,%eax
0.98 â vpinsrb $0x4,%eax,%xmm1,%xmm1
0.16 â vpextrw $0x5,%xmm0,%eax
1.00 â vpinsrb $0x5,%eax,%xmm1,%xmm1
0.22 â vpextrw $0x6,%xmm0,%eax
1.10 â vpinsrb $0x6,%eax,%xmm1,%xmm1
0.30 â vpextrw $0x7,%xmm0,%eax
0.31 â vextracti128 $0x1,%ymm0,%xmm0
0.90 â vpinsrb $0x7,%eax,%xmm1,%xmm6
0.21 â vpextrw $0x0,%xmm0,%eax
0.35 â vmovaps %xmm6,0x50(%rsp)
1.15 â mov 0x58(%rsp),%r9
0.13 â mov 0x50(%rsp),%r8
0.29 â mov %al,%r9b
0.49 â mov %r8,0x50(%rsp)
0.07 â vpextrw $0x1,%xmm0,%eax
0.45 â mov %r9,0x58(%rsp)
7.08 â vmovdqa 0x50(%rsp),%xmm7
1.19 â vpinsrb $0x9,%eax,%xmm7,%xmm1
0.00 â vpextrw $0x2,%xmm0,%eax
0.78 â vpinsrb $0xa,%eax,%xmm1,%xmm1
0.00 â vpextrw $0x3,%xmm0,%eax
0.77 â vpinsrb $0xb,%eax,%xmm1,%xmm1
0.01 â vpextrw $0x4,%xmm0,%eax
0.86 â vpinsrb $0xc,%eax,%xmm1,%xmm1
0.03 â vpextrw $0x5,%xmm0,%eax
0.88 â vpinsrb $0xd,%eax,%xmm1,%xmm1
0.04 â vpextrw $0x6,%xmm0,%eax
0.97 â vpinsrb $0xe,%eax,%xmm1,%xmm1
0.08 â vpextrw $0x7,%xmm0,%eax
1.44 â vpinsrb $0xf,%eax,%xmm1,%xmm0
1.37 â vpextrd $0x1,%xmm0,%eax
0.13 â vinsertps $0xe,%xmm0,%xmm0,%xmm1
0.02 â vmovaps %xmm0,0x50(%rsp)
2.17 â vpinsrd $0x1,%eax,%xmm1,%xmm1
....
Clang code:
Percentâ vpmullw %ymm0,%ymm2,%ymm2
â vpaddw %ymm1,%ymm2,%ymm2
â vpsrlw $0x8,%ymm2,%ymm2
â vextracti128 $0x1,%ymm2,%xmm3
â vpackuswb %xmm3,%xmm2,%xmm2
â vmovdqu %xmm2,(%rdi)
â add $0x10,%rsi
â add $0x10,%rdi
â mov %r9d,%eax
â cmp $0x4,%r9d
â â jae 39179b0 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0xa0>
â â jmp 3917a02 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0xf2>
â mov %edx,%eax
0.29 â cmp $0x4,%r9d
0.00 â â jb 3917a02 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0xf2>
0.07 â nop
3.95 â vpmovzxbw (%rsi),%ymm2
13.41 â vpmullw %ymm0,%ymm2,%ymm2
13.87 â vpaddw %ymm1,%ymm2,%ymm2
2.93 â vpsrlw $0x8,%ymm2,%ymm2
0.84 â vextracti128 $0x1,%ymm2,%xmm3
9.98 â vpackuswb %xmm3,%xmm2,%xmm2
6.89 â vmovdqu %xmm2,(%rdi)
0.57 â vpmovzxbw 0x10(%rsi),%ymm2
4.02 â vpmullw %ymm0,%ymm2,%ymm2
12.15 â vpaddw %ymm1,%ymm2,%ymm2
2.02 â vpsrlw $0x8,%ymm2,%ymm2
1.22 â vextracti128 $0x1,%ymm2,%xmm3
8.04 â vpackuswb %xmm3,%xmm2,%xmm2
7.09 â vmovdqu %xmm2,0x10(%rdi)
0.19 â add $0x20,%rsi
0.19 â add $0x20,%rdi
0.57 â add $0xfffffff8,%eax
7.26 â cmp $0x3,%eax
0.29 â â jg 39179b0 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0xa0>
0.02 â and $0x3,%edx
Percentâ test %edx,%edx
0.04 â â jle 3917af1 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0x1e1>
â mov %ecx,%eax
â shr $0x18,%eax
â shr $0x1f,%ecx
â add %eax,%ecx
â vmovd %ecx,%xmm0
â vpbroadcastb %xmm0,%xmm0
â mov %r8,%rax
â shl $0x20,%rax
â or %r8,%rax
â vmovq %rax,%xmm1
â vpbroadcastq %xmm1,%xmm1
â vpmovzxbw %xmm1,%ymm1
â vpmovzxbw %xmm0,%ymm0
â vpsllw $0x8,%ymm1,%ymm1
â vpor 0x1f3eb35(%rip),%ymm1,%ymm1 # 5856580
<SkNamedGamut::kAdobeRGB+0x858>
â test $0x1,%dl
â â jne 3917a5c <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0x14c>
â mov %edx,%eax
â cmp $0x1,%edx
â â jne 3917a90 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0x180>
â â jmpq 3917af1 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0x1e1>
â lea -0x1(%rdx),%eax
â mov (%rsi),%ecx
â add $0x4,%rsi
â vmovq %rcx,%xmm2
â vpmovzxbw %xmm2,%xmm2
â vpmullw %xmm0,%xmm2,%xmm2
â vpaddw %xmm1,%xmm2,%xmm2
â vpsrlw $0x8,%xmm2,%xmm2
â vpackuswb %xmm0,%xmm2,%xmm2
â vmovq %xmm2,%rcx
â mov %ecx,(%rdi)
â add $0x4,%rdi
â cmp $0x1,%edx
â xor %ecx,%ecx
â nop
â nop
â mov (%rsi,%rcx,1),%edx
â vmovq %rdx,%xmm2
â vpmovzxbw %xmm2,%xmm2
â vpmullw %xmm0,%xmm2,%xmm2
â vpaddw %xmm1,%xmm2,%xmm2
â vpsrlw $0x8,%xmm2,%xmm2
â vpackuswb %xmm0,%xmm2,%xmm2
â vmovd %xmm2,(%rdi,%rcx,1)
â mov 0x4(%rsi,%rcx,1),%edx
â vmovq %rdx,%xmm2
â vpmovzxbw %xmm2,%xmm2
â vpmullw %xmm0,%xmm2,%xmm2
â vpaddw %xmm1,%xmm2,%xmm2
â vpsrlw $0x8,%xmm2,%xmm2
â vpackuswb %xmm0,%xmm2,%xmm2
â vmovd %xmm2,0x4(%rdi,%rcx,1)
â add $0x8,%rcx
â add $0xfffffffe,%eax
â â jg 3917aa0 <hsw::blit_row_color32(unsigned int*,
unsigned int const*, int, unsigned int)+0x190>
0.38 â vzeroupper
0.26 â â retq
>From gcc-bugs-return-661128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 09:48:46 2019
Return-Path: <gcc-bugs-return-661128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90796 invoked by alias); 24 Nov 2019 09: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 90588 invoked by uid 48); 24 Nov 2019 09:48:06 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Sun, 24 Nov 2019 09: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92645-4-HRMFedQ4IA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02922.txt.bz2
Content-length: 232
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 47340
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47340&action=edit
Clang source
>From gcc-bugs-return-661129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 09:49:35 2019
Return-Path: <gcc-bugs-return-661129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91959 invoked by alias); 24 Nov 2019 09:49:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91905 invoked by uid 48); 24 Nov 2019 09:49:30 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Sun, 24 Nov 2019 09:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92645-4-nYNcUTAcvV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02923.txt.bz2
Content-length: 261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #2 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 47341
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47341&action=edit
clang output with -O2 -mavx2 -mf16c -mfma
>From gcc-bugs-return-661130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 09:50:04 2019
Return-Path: <gcc-bugs-return-661130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92975 invoked by alias); 24 Nov 2019 09:50: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 92887 invoked by uid 48); 24 Nov 2019 09:49:59 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Sun, 24 Nov 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92645-4-OG5lwQoGQh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02924.txt.bz2
Content-length: 230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #3 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 47342
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47342&action=edit
GCC source
>From gcc-bugs-return-661131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 09:50:39 2019
Return-Path: <gcc-bugs-return-661131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93848 invoked by alias); 24 Nov 2019 09:50:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93816 invoked by uid 48); 24 Nov 2019 09:50:35 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Sun, 24 Nov 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92645-4-XXKLikV0oj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02925.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #4 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Created attachment 47343
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47343&action=edit
GCC 10 output
>From gcc-bugs-return-661132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 12:09:46 2019
Return-Path: <gcc-bugs-return-661132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23958 invoked by alias); 24 Nov 2019 12:09: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 23904 invoked by uid 48); 24 Nov 2019 12:09:42 -0000
From: "samyavrillon at netcourrier dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92646] New: Compilation fails on armv7l with sys/cdefs.h: No such file or directory
Date: Sun, 24 Nov 2019 12:09: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samyavrillon at netcourrier 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-92646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02926.txt.bz2
Content-length: 2293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92646
Bug ID: 92646
Summary: Compilation fails on armv7l with sys/cdefs.h: No such
file or directory
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: samyavrillon at netcourrier dot com
Target Milestone: ---
I am using the source version of gcc 9.2.0
I tried to compile gcc on my OrangePi PC with
./configure --with-mpc=/home/bernard/building/mpc-1.1.0
--with-gmp=/home/bernard/building/gmp-6.1.2
--with-mpfr=/home/bernard/building/mpfr-4.0.2
I didn't gave any more options as I have no idea of what i should add
The error happens during the make process
Here is the error:
/home/bernard/building/gcc-9.2.0/host-armv7l-unknown-linux-gnueabihf/gcc/xgcc
-B/home/bernard/building/gcc-9.2.0/host-armv7l-unknown-linux-gnueabihf/gcc/
-B/usr/local/armv7l-unknown-linux-gnueabihf/bin/
-B/usr/local/armv7l-unknown-linux-gnueabihf/lib/ -isystem
/usr/local/armv7l-unknown-linux-gnueabihf/include -isystem
/usr/local/armv7l-unknown-linux-gnueabihf/sys-include -fno-checking -g -O2
-O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fPIC -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -fPIC -fno-inline -I. -I.
-I../../host-armv7l-unknown-linux-gnueabihf/gcc -I../.././libgcc
-I../.././libgcc/. -I../.././libgcc/../gcc -I../.././libgcc/../include
-DHAVE_CC_TLS -o _muldi3.o -MT _muldi3.o -MD -MP -MF _muldi3.dep -DL_muldi3 -c
../.././libgcc/libgcc2.c -fvisibility=hidden -DHIDE_EXPORTS
In file included from /usr/include/stdio.h:27,
from ../.././libgcc/../gcc/tsystem.h:87,
from ../.././libgcc/libgcc2.c:27:
/usr/include/features.h:364:12: fatal error: sys/cdefs.h: No such file or
directory
364 | # include <sys/cdefs.h>
| ^~~~~~~~~~~~~
compilation terminated.
I have to install the latest gcc beccause i only have gcc6 installed on my
computer and cannot compile recent g++ programs.
Thanks in advance.
>From gcc-bugs-return-661133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 12:37:48 2019
Return-Path: <gcc-bugs-return-661133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43687 invoked by alias); 24 Nov 2019 12:37: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 43647 invoked by uid 48); 24 Nov 2019 12:37:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24878] subroutine getting called illegally as a function
Date: Sun, 24 Nov 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.1.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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-24878-4-XUzawelue3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-24878-4@http.gcc.gnu.org/bugzilla/>
References: <bug-24878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02927.txt.bz2
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=24878
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2018-01-05 00:00:00 |2019-11-24
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Just taking a look at this again.
There are two points where an error could be issued.
First,
INTEGER X, Y, SUBA
EXTERNAL SUBA
clashes with
SUBROUTINE SUBA(X)
so we could flag this going through the global list
of symbols.
Second,
EXTERNAL SUBA
CALL ANY (FNC, X, Y)
INTEGER FNC
should also clash with
SUBROUTINE SUBA(X)
but that is much harder, because we would then have to check
for the argument that is passed to ANY.
>From gcc-bugs-return-661134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 12:44:17 2019
Return-Path: <gcc-bugs-return-661134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47351 invoked by alias); 24 Nov 2019 12: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 47303 invoked by uid 48); 24 Nov 2019 12:44:14 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33097] Function decl trees without proper argument list
Date: Sun, 24 Nov 2019 12:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.2.1
X-Bugzilla-Keywords: FIXME
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-33097-4-HviGYdWL7j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-33097-4@http.gcc.gnu.org/bugzilla/>
References: <bug-33097-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02928.txt.bz2
Content-length: 555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33097
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #22 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I think this should be fixed now, because we now generate
argument lists from actual arcuments if none are present.
Can somebody confirm that this is the case? I don't speak
TREE too well.
>From gcc-bugs-return-661135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 12:51:36 2019
Return-Path: <gcc-bugs-return-661135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51519 invoked by alias); 24 Nov 2019 12:51: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 51437 invoked by uid 48); 24 Nov 2019 12:51:32 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42118] Slow forall
Date: Sun, 24 Nov 2019 12:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.2
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
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 cc resolution
Message-ID: <bug-42118-4-R4U8XeGn8U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-42118-4@http.gcc.gnu.org/bugzilla/>
References: <bug-42118-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02929.txt.bz2
Content-length: 1025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42118
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |tkoenig at gcc dot gnu.org
Resolution|--- |WONTFIX
--- Comment #11 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Lionel GUEZ from comment #10)
> (In reply to kargl from comment #9)
> > Fortran 2018 has declared FORALL to be an obsolescent feature.
> > I doubt that anyone will ever try to improve the performance
> > of FORALL, because the next standard is likely to delete it.
> >
> > I think that this bug can be closed with WONTFIX or WORKSFORME.
>
> OK for me.
We have had forall loop interchange for quite some time now, and that
is all the effort that people are likely to put into this.
So, closing as WONTFIX.
>From gcc-bugs-return-661136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 13:19:27 2019
Return-Path: <gcc-bugs-return-661136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73663 invoked by alias); 24 Nov 2019 13:19: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 73632 invoked by uid 48); 24 Nov 2019 13:19:23 -0000
From: "pashev.igor at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug modula2/92647] New: Internal enum may conflict with the time() function
Date: Sun, 24 Nov 2019 13:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: modula2
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pashev.igor 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-92647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02930.txt.bz2
Content-length: 917
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92647
Bug ID: 92647
Summary: Internal enum may conflict with the time() function
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: modula2
Assignee: unassigned at gcc dot gnu.org
Reporter: pashev.igor at gmail dot com
Target Milestone: ---
Created attachment 47344
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47344&action=edit
Rename "time" to "tiempo"
In the `gm2/mc-boot/GRTint.c` file there is an enum `typedef enum {input,
output, time} VectorType;` which may conflict with the `time()` function that
could be brought in the scope by accident. It happened to me when building for
Dyson [1] since it not using GNU libc. I had to rename "time" to "tiempo" to
fix that :)
[1] https://www.osdyson.org
>From gcc-bugs-return-661137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 14:23:24 2019
Return-Path: <gcc-bugs-return-661137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115680 invoked by alias); 24 Nov 2019 14:23:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115638 invoked by uid 48); 24 Nov 2019 14:23:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92644] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530
Date: Sun, 24 Nov 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: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed
Message-ID: <bug-92644-4-w8omao38jf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02931.txt.bz2
Content-length: 1061
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92644
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-11-24
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Target Milestone|--- |9.3
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r265909.
NULLPTR_TYPE only allows value 0, so doing
rhs = wide_int_to_tree (TREE_TYPE (rhs),
wi::min_value (TREE_TYPE (rhs)) + 1);
for it ICEs.
I'd say we should guard that only for INTEGRAL_TYPE_P types and perhaps
pointer/reference types too, though transformation of == NULL to < (void *) 1
looks really weird.
>From gcc-bugs-return-661138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 16:27:10 2019
Return-Path: <gcc-bugs-return-661138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42413 invoked by alias); 24 Nov 2019 16:27:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42367 invoked by uid 55); 24 Nov 2019 16:27:05 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92643] ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Date: Sun, 24 Nov 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92643-4-54VQur0Lf6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02932.txt.bz2
Content-length: 1513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
--- Comment #3 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Nov 24, 2019 at 03:59:41AM +0000, kargl at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
>
> --- Comment #1 from kargl at gcc dot gnu.org ---
> % gdb831 ./z
> (gdb) run
> Starting program: /usr/home/kargl/tmp/z
>
> Program received signal SIGSEGV, Segmentation fault.
> main () at ISO_Fortran_binding_15.c:29
> 29 if (*(int *)dat.base_addr != 42)
>
>
> I think that there is a 32-bit vs 64-bit problem with pointers.
>
A little more debugging,
(gdb) b ISO_Fortran_binding_15.c:29
Breakpoint 1 at 0x804898d: file ISO_Fortran_binding_15.c, line 29.
(gdb) run ./z
Starting program: /usr/home/kargl/tmp/z ./z
Breakpoint 1, main () at ISO_Fortran_binding_15.c:29
29 if (*(int *)dat.base_addr != 42)
(gdb) p dat
$1 = {base_addr = 0x0, elem_len = 4, version = 1, rank = 0 '\000',
attribute = 1 '\001', type = 1025, dim = {{lower_bound = -4200908,
extent = 677138155, sm = 1}}}
So, we find
typedef struct CFI_cdesc_t
{
void *base_addr;
size_t elem_len;
int version;
CFI_rank_t rank;
CFI_attribute_t attribute;
CFI_type_t type;
CFI_dim_t dim[];
}
CFI_cdesc_t;
Whoops that 'void *' is likely the problem. sizeof(void *)
on i586-*-freebsd is 4; while it is 8 on x86_64-*-amd64. I
suspect a missing a "fold_convert(pvoid_type_node,...)"
>From gcc-bugs-return-661139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 17:10:19 2019
Return-Path: <gcc-bugs-return-661139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74363 invoked by alias); 24 Nov 2019 17:10:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74310 invoked by uid 48); 24 Nov 2019 17:10:14 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91783] [10 Regression] ICE in gfc_dep_resolver, at fortran/dependency.c:2111
Date: Sun, 24 Nov 2019 17:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-91783-4-vSVqu85Ehr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02933.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91783
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-11-24
CC| |tkoenig at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-661140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 17:20:13 2019
Return-Path: <gcc-bugs-return-661140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82753 invoked by alias); 24 Nov 2019 17:20:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82413 invoked by uid 48); 24 Nov 2019 17:20:09 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/91800] ICE in gfc_code2string(): Bad code
Date: Sun, 24 Nov 2019 17:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-91800-4-o6hgR2EMsm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02934.txt.bz2
Content-length: 686
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91800
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-24
CC| |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Maybe "bad code" isn't such a bad description of this...
I wonder if people would complain if we just rejected a
Hollerith constant here?
>From gcc-bugs-return-661141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 17:59:52 2019
Return-Path: <gcc-bugs-return-661141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118601 invoked by alias); 24 Nov 2019 17:59:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118537 invoked by uid 48); 24 Nov 2019 17:59:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92644] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530
Date: Sun, 24 Nov 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92644-4-lED1hwPINY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02935.txt.bz2
Content-length: 2477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92644
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
For pointers, it boils down whether say
void *
foo (void *p)
{
return p ? p : (void *) 1;
}
optimization into MAX_EXPR <1B, p> is valid or not. The original code doesn't
involve any non-equality comparisons, while MAX_EXPR is a non-equality
comparison which ought to be valid only as long as the two pointers are
pointing into the same object. Another possibility would be for pointers to do
this optimization, but perform the MIN_EXPR/MAX_EXPR in pointer sized ints
instead.
So, the fix can be either NULLPTR_TYPE specific, like:
--- gcc/tree-ssa-phiopt.c 2019-11-20 09:25:42.552157763 +0100
+++ gcc/tree-ssa-phiopt.c 2019-11-24 18:56:50.657172109 +0100
@@ -1381,7 +1381,8 @@ minmax_replacement (basic_block cond_bb,
/* Turn EQ/NE of extreme values to order comparisons. */
if ((cmp == NE_EXPR || cmp == EQ_EXPR)
- && TREE_CODE (rhs) == INTEGER_CST)
+ && TREE_CODE (rhs) == INTEGER_CST
+ && TREE_CODE (TREE_TYPE (rhs)) != NULLPTR_TYPE)
{
if (wi::eq_p (wi::to_wide (rhs), wi::min_value (TREE_TYPE (rhs))))
{
@@ -1407,7 +1408,8 @@ minmax_replacement (basic_block cond_bb,
larger = rhs;
/* If we have smaller < CST it is equivalent to smaller <= CST-1.
Likewise smaller <= CST is equivalent to smaller < CST+1. */
- if (TREE_CODE (larger) == INTEGER_CST)
+ if (TREE_CODE (larger) == INTEGER_CST
+ && TREE_CODE (TREE_TYPE (larger)) != NULLPTR_TYPE)
{
if (cmp == LT_EXPR)
{
@@ -1435,7 +1437,8 @@ minmax_replacement (basic_block cond_bb,
larger = gimple_cond_lhs (cond);
/* If we have larger > CST it is equivalent to larger >= CST+1.
Likewise larger >= CST is equivalent to larger > CST-1. */
- if (TREE_CODE (smaller) == INTEGER_CST)
+ if (TREE_CODE (smaller) == INTEGER_CST
+ && TREE_CODE (TREE_TYPE (larger)) != NULLPTR_TYPE)
{
wi::overflow_type overflow;
if (cmp == GT_EXPR)
or instead of it say && (INTEGRAL_TYPE_P (TREE_TYPE (rhs)) || POINTER_TYPE_P
(TREE_TYPE (rhs))), or just && INTEGRAL_TYPE_P (TREE_TYPE (rhs)), and if
allowing POINTER_TYPE_P, we can also special case
new_stmt = gimple_build_assign (result, minmax, arg0, arg1);
for pointers by casting to integers and back.
Thoughts?
>From gcc-bugs-return-661142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 18:07:25 2019
Return-Path: <gcc-bugs-return-661142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123534 invoked by alias); 24 Nov 2019 18:07: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 123479 invoked by uid 48); 24 Nov 2019 18:07:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92643] ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Date: Sun, 24 Nov 2019 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-92643-4-oGurY1VKGN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02936.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123#c5 ?
>From gcc-bugs-return-661143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 18:45:30 2019
Return-Path: <gcc-bugs-return-661143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26214 invoked by alias); 24 Nov 2019 18:45: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 26021 invoked by uid 55); 24 Nov 2019 18:45:18 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92643] ISO_Fortran_binding_15.f90 failure on i586-*-freebsd
Date: Sun, 24 Nov 2019 18:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92643-4-gVgXhoujDL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02937.txt.bz2
Content-length: 817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, Nov 24, 2019 at 06:07:20PM +0000, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92643
>
> Jakub Jelinek <jakub at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |jakub at gcc dot gnu.org
>
> --- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123#c5 ?
>
Yes, your comment #5 in that PR matches what I'm reporting.
Do you want me to close this as a duplicate or set the
"Depends on:" field?
>From gcc-bugs-return-661144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 19:16:07 2019
Return-Path: <gcc-bugs-return-661144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59579 invoked by alias); 24 Nov 2019 19:16: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 59543 invoked by uid 48); 24 Nov 2019 19:16:03 -0000
From: "arieltorti14 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92229] Optimization makes it impossible to read overflow flag
Date: Sun, 24 Nov 2019 19:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: arieltorti14 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92229-4-uRaxQBsJYJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02938.txt.bz2
Content-length: 1426
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92229
Ariel Torti <arieltorti14 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from Ariel Torti <arieltorti14 at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #4)
> On Sat, 26 Oct 2019, arieltorti14 at gmail dot com wrote:
>
> You can write an asm to access a flag, it will just be whatever value the
> flag has for whatever code the compiler found matched the language-level
> semantics of your code, which may have nothing to do with your notion of
> what the flag "should" be.
>
> Language semantics are only matched to processor features at ABI
> boundaries, not within functions (and not across calls to inline / static
> functions etc. either, because those aren't ABI boundaries; any good
> language feature in this area also needs to work in the presence of
> multiple functions, and of inlining and similar transformations, not just
> where the arithmetic is in the same function as the code that cares about
> whether it overflowed).
Fair point, I can see why it would be very problematic, didn't really knew the
full scope when I considered the issue.
>From gcc-bugs-return-661145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 19:16:59 2019
Return-Path: <gcc-bugs-return-661145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60878 invoked by alias); 24 Nov 2019 19:16:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60809 invoked by uid 55); 24 Nov 2019 19:16:55 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92569] [8/9/10 Regression] gfortran read with end directive does not trigger with -ffrontend-optimize
Date: Sun, 24 Nov 2019 19:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92569-4-8u75vxxBT7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92569-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92569-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02939.txt.bz2
Content-length: 860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92569
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Nov 24 19:16:23 2019
New Revision: 278659
URL: https://gcc.gnu.org/viewcvs?rev=278659&root=gcc&view=rev
Log:
Fix EOF handling for arrays.
2019-11-23 Thomas Koenig <tkoenig@gcc.gnu.org>
Harald Anlauf <anlauf@gmx.de>
PR fortran/92569
* io/transfer.c (transfer_array_inner): If position is
at AFTER_ENDFILE in current unit, return from data loop.
2019-11-23 Thomas Koenig <tkoenig@gcc.gnu.org>
Harald Anlauf <anlauf@gmx.de>
PR fortran/92569
* gfortran.dg/eof_6.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/eof_6.f90
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/transfer.c
>From gcc-bugs-return-661146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 19:18:44 2019
Return-Path: <gcc-bugs-return-661146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62640 invoked by alias); 24 Nov 2019 19:18:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62570 invoked by uid 48); 24 Nov 2019 19:18:40 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92569] [8/9 Regression] gfortran read with end directive does not trigger with -ffrontend-optimize
Date: Sun, 24 Nov 2019 19:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-92569-4-SpNcJVztpz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92569-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92569-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02940.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92569
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|10.0 |8.4
Summary|[8/9/10 Regression] |[8/9 Regression] gfortran
|gfortran read with end |read with end directive
|directive does not trigger |does not trigger with
|with -ffrontend-optimize |-ffrontend-optimize
>From gcc-bugs-return-661147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 19:39:46 2019
Return-Path: <gcc-bugs-return-661147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77117 invoked by alias); 24 Nov 2019 19:39: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 77086 invoked by uid 48); 24 Nov 2019 19:39:43 -0000
From: "epagone at email dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92586] ICE in gimplify_expr, at gimplify.c:13479 with nested allocatable derived types
Date: Sun, 24 Nov 2019 19:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: epagone at email dot it
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-92586-4-alI0yeozA0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92586-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92586-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02941.txt.bz2
Content-length: 519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92586
epagone <epagone at email dot it> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #47303|0 |1
is obsolete| |
--- Comment #1 from epagone <epagone at email dot it> ---
Created attachment 47345
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47345&action=edit
MWE without external library
>From gcc-bugs-return-661148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 19:45:40 2019
Return-Path: <gcc-bugs-return-661148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82124 invoked by alias); 24 Nov 2019 19:45: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 82044 invoked by uid 48); 24 Nov 2019 19:45:35 -0000
From: "epagone at email dot it" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92586] ICE in gimplify_expr, at gimplify.c:13479 with nested allocatable derived types
Date: Sun, 24 Nov 2019 19:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: epagone at email dot it
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92586-4-R3NTsFJwXx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92586-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92586-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02942.txt.bz2
Content-length: 1535
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92586
--- Comment #2 from epagone <epagone at email dot it> ---
I managed to produce a test case that does not require any external library
(much easier to test). Please find it attached in my previous comment.
I was able then to test it easily with all the versions of gfortran available
on my machine. Here are the results.
$ gfortran-9 bug_gimplify.f90
bug_gimplify.f90:34:0:
34 | data_get_foo_s = self%foo(ith)%get_s()
|
internal compiler error: in gimplify_expr, at gimplify.c:13479
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-9/README.Bugs> for instructions.
$ gfortran-9 --version
GNU Fortran (Ubuntu 9.2.1-17ubuntu1~18.04.1) 9.2.1 20191102
$ gfortran-8 bug_gimplify.f90
bug_gimplify.f90:34:0:
data_get_foo_s = self%foo(ith)%get_s()
internal compiler error: in gimplify_expr, at gimplify.c:12492
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-8/README.Bugs> for instructions.
$ gfortran-8 --version
GNU Fortran (Ubuntu 8.3.0-6ubuntu1~18.04.1) 8.3.0
$ gfortran-7 bug_gimplify.f90
bug_gimplify.f90:34:0:
data_get_foo_s = self%foo(ith)%get_s()
internal compiler error: in gimplify_expr, at gimplify.c:12247
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-7/README.Bugs> for instructions.
$ gfortran-7 --version
GNU Fortran (Ubuntu 7.4.0-1ubuntu1~18.04.1) 7.4.0
>From gcc-bugs-return-661149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 20:18:42 2019
Return-Path: <gcc-bugs-return-661149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111690 invoked by alias); 24 Nov 2019 20: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 111653 invoked by uid 48); 24 Nov 2019 20:18:39 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92445] gcc bootstrap fails on Darwin 19.0.0 in stage 1
Date: Sun, 24 Nov 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92445-4-KNiAuQ9SRK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92445-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92445-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02943.txt.bz2
Content-length: 220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92445
--- Comment #1 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Did anybody look into this one here? At the moment, I cannot build gcc on
MACOSX Catalina.
>From gcc-bugs-return-661150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Nov 24 22:15:40 2019
Return-Path: <gcc-bugs-return-661150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48072 invoked by alias); 24 Nov 2019 22:15: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 47964 invoked by uid 55); 24 Nov 2019 22:15:32 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92100] Formatted stream IO irreproducible read with binary data in file
Date: Sun, 24 Nov 2019 22:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92100-4-hHg0RLEdPb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02944.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92100
--- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Sun Nov 24 22:14:59 2019
New Revision: 278660
URL: https://gcc.gnu.org/viewcvs?rev=278660&root=gcc&view=rev
Log:
2019-11-24 Jerry DeLisle <jvdelisle@gcc.ngu.org>
PR fortran/92100
io/transfer.c (data_transfer_init_worker): Use fbuf_reset
instead of fbuf_flush before the seek. Note that fbuf_reset
calls fbuf_flush and adjusts fbuf pointers.
Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/transfer.c
>From gcc-bugs-return-661151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 00:01:27 2019
Return-Path: <gcc-bugs-return-661151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119115 invoked by alias); 25 Nov 2019 00:01:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118831 invoked by uid 48); 25 Nov 2019 00:01:23 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Mon, 25 Nov 2019 00:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92499-4-vdiwqOfU4j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02945.txt.bz2
Content-length: 2156
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #5 from sandra at gcc dot gnu.org ---
Richard Sandiford complained that my patch to not put objects containing
flexible arrays in small data was an ABI change for references across
compilation units, so I've been taking another look at this to see if I can
find a different solution.
The thing that triggered the link error reported in GLIBC is that the nios2
back end generates uses gp-relative addressing for a locally declared object of
such a type, but was inconsistently placing the (zero-initialized) object in
.bss instead of .sbss. I spent some time in the debugger on this one -- the
problem is that get_variable_section returns lcomm_section in this instance,
without checking whether the object is "small", or deferring to the backend to
choose a section. Eventually in the nios2 back end the
ASM_OUTPUT_ALIGNED_LOCAL hook looks at the size to decide whether to emit the
local in .sbss or .bss, but the size it has at that point is the size of the
initializer, not the declared size of the type. Local objects with nonzero
initializers are placed in .sdata and objects with external linkage are also
placed in .sdata/.sbss consistently with the use of gp-relative addressing.
The MIPS back end has the same issue; it puts the zero-initialized local object
in .comm, while the other cases end up in .sdata/.sbss. I also observed that
the MIPS backend is emitting an incorrect .size directive (using the size of
the non-flexible part of the object instead of the size of the initializer) for
the cases it does put in .sdata/.sbss. I don't know if that is actually used
by the assembler in a way that is harmful, though.
So I think we could fix this without changing the ABI by fixing
get_variable_section not to short-circuit the criteria the rest of the compiler
uses to decide whether an object belongs in a small data section. That could
optionally be combined with target-specific changes not to consider
flexibly-sized objects with internal linkage not to be "small" for the purposes
of either section placement or gp-relative addressing.
>From gcc-bugs-return-661152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 00:03:57 2019
Return-Path: <gcc-bugs-return-661152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121512 invoked by alias); 25 Nov 2019 00:03:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121460 invoked by uid 48); 25 Nov 2019 00:03:53 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Mon, 25 Nov 2019 00:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92499-4-mPiztrupfQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02946.txt.bz2
Content-length: 267
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #6 from sandra at gcc dot gnu.org ---
Created attachment 47346
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47346&action=edit
improved test case with global/external cases as well as local
>From gcc-bugs-return-661153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 00:05:22 2019
Return-Path: <gcc-bugs-return-661153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123000 invoked by alias); 25 Nov 2019 00: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 122958 invoked by uid 48); 25 Nov 2019 00:05:18 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Mon, 25 Nov 2019 00:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92499-4-pM5DzduXd2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02947.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #7 from sandra at gcc dot gnu.org ---
Created attachment 47347
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47347&action=edit
nios2 output for improved test case, -O2 -mgpopt=global
>From gcc-bugs-return-661154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 00:06:18 2019
Return-Path: <gcc-bugs-return-661154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124434 invoked by alias); 25 Nov 2019 00:06: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 124332 invoked by uid 48); 25 Nov 2019 00:06:14 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92499] nios2 backend needs to consider allocated object size, not C object size for gprel optimization
Date: Mon, 25 Nov 2019 00:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-92499-4-h3fhxdA78J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02948.txt.bz2
Content-length: 244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92499
--- Comment #8 from sandra at gcc dot gnu.org ---
Created attachment 47348
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47348&action=edit
mips output for improved test case, -O2
>From gcc-bugs-return-661155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 00:14:54 2019
Return-Path: <gcc-bugs-return-661155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 333 invoked by alias); 25 Nov 2019 00:14:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 131046 invoked by uid 48); 25 Nov 2019 00:14:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92648] New: Handling of unknown attributes
Date: Mon, 25 Nov 2019 00:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02949.txt.bz2
Content-length: 2525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92648
Bug ID: 92648
Summary: Handling of unknown attributes
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
It is still unclear how exactly OpenMP attributes will look like (at least most
of them), but it seems the C++ FE (unlike the C FE) attempts to parse the
arguments as expression list instead of skipping it.
Consider:
void
foo (int x, int y, int z, int u)
{
[[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
}
ud.C:4:26: error: expected ‘)’ before ‘:’ token
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ~ ^
| )
ud.C:4:15: error: ‘linear’ was not declared in this scope
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ^~~~~~
ud.C:4:32: error: expected primary-expression before ‘private’
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ^~~~~~~
ud.C:4:55: error: expected primary-expression before ‘:’ token
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ^
ud.C:4:44: error: ‘reduction’ was not declared in this scope
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ^~~~~~~~~
ud.C:4:3: warning: attributes at the beginning of statement are ignored
[-Wattributes]
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Compare that to C:
ud.C: In function ‘foo’:
ud.C:4:3: warning: ‘for’ attribute ignored [-Wattributes]
4 | [[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
| ^
or clang++:
ud.C:4:5: warning: unknown attribute 'for' ignored [-Wunknown-attributes]
[[omp::for (linear(x, y: 2), private(z), reduction(+:u))]];
^
1 warning generated.
I think the syntax just says that the arguments are balanced token sequences,
but if the compiler doesn't know the attribute, it can't assume anything
further.
>From gcc-bugs-return-661156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 02:25:37 2019
Return-Path: <gcc-bugs-return-661156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107245 invoked by alias); 25 Nov 2019 02:25:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107161 invoked by uid 55); 25 Nov 2019 02:25:28 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/92100] Formatted stream IO irreproducible read with binary data in file
Date: Mon, 25 Nov 2019 02:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92100-4-OSXwqljgQM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92100-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92100-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02950.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92100
--- Comment #10 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Mon Nov 25 02:24:55 2019
New Revision: 278664
URL: https://gcc.gnu.org/viewcvs?rev=278664&root=gcc&view=rev
Log:
2019-11-24 Jerry DeLisle <jvdelisle@gcc.ngu.org>
PR fortran/92100
gfortran.dg/streamio_18.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/streamio_18.f90
Modified:
trunk/gcc/ChangeLog
>From gcc-bugs-return-661157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 02:28:21 2019
Return-Path: <gcc-bugs-return-661157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110181 invoked by alias); 25 Nov 2019 02:28: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 110098 invoked by uid 48); 25 Nov 2019 02:28:17 -0000
From: "jiangning.liu at amperecomputing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92649] New: dead store elimination
Date: Mon, 25 Nov 2019 02:28: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: 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-92649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02951.txt.bz2
Content-length: 959
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92649
Bug ID: 92649
Summary: dead store elimination
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jiangning.liu at amperecomputing dot com
Target Milestone: ---
For this small case,
int f(void)
{
int i, a[1024];
for (i=0; i<1024; i++)
a[i] = 5;
return a[0];
}
"gcc -O3" can't figure out the memory stores from a[1] to a[1023] all can be
eliminated. The assembly code for aarch64 is as below.
movi v0.4s, 0x5
sub sp, sp, #4096
mov x0, sp
add x1, sp, 4096
.L2:
str q0, [x0], 16
cmp x0, x1
bne .L2
ldr w0, [sp]
add sp, sp, 4096
ret
>From gcc-bugs-return-661158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 05:02:00 2019
Return-Path: <gcc-bugs-return-661158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31192 invoked by alias); 25 Nov 2019 05: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 31175 invoked by uid 48); 25 Nov 2019 05:01:55 -0000
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92650] New: internal compiler error: canonical types differ for identical types
Date: Mon, 25 Nov 2019 05:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ldalessandro 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-92650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02952.txt.bz2
Content-length: 1068
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92650
Bug ID: 92650
Summary: internal compiler error: canonical types differ for
identical types
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ldalessandro at gmail dot com
Target Milestone: ---
Created attachment 47349
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47349&action=edit
test case
Following code triggers ICE on (godbolt) trunk only. See
https://godbolt.org/z/q4CrvX.
It's hard for me to disambiguate from other reports with the same error
message, but it seems new.
#include <range/v3/all.hpp>
struct Wrapper {
int a[1];
constexpr operator int() const { return a[0]; }
};
int main() {
std::vector<int> a;
auto all = ranges::views::all(a);
auto zip = ranges::views::zip(a);
Wrapper b;
*all.begin() = b;
*zip.begin() = b;
}
>From gcc-bugs-return-661159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 05:04:28 2019
Return-Path: <gcc-bugs-return-661159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33385 invoked by alias); 25 Nov 2019 05:04:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33325 invoked by uid 48); 25 Nov 2019 05:04:23 -0000
From: "ldalessandro at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92650] internal compiler error: canonical types differ for identical types
Date: Mon, 25 Nov 2019 05:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ldalessandro 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-92650-4-ApEI8mM4Dh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92650-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92650-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02953.txt.bz2
Content-length: 4572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92650
--- Comment #1 from Luke Dalessandro <ldalessandro at gmail dot com> ---
<Compilation failed>
x86-64 gcc (trunk) - cached
#1 with x86-64 gcc (trunk)
In file included from
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/action/action.hpp:19,
from
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/action.hpp:17,
from
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/all.hpp:17,
from <source>:1:
/opt/compiler-explorer/libs/rangesv3/trunk/include/meta/meta.hpp: In
substitution of 'template<bool If, class ... Args> using if_c =
meta::_t<meta::detail::_if_<meta::list<std::integral_constant<bool, __v>, Args
...> > > [with bool If = std::integral_constant<bool,
and_v<__is_constructible(Ts)...> >::value; Args = {}]':
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/utility/common_tuple.hpp:65:13:
required from 'struct ranges::detail::args_<1, const int&>'
/opt/compiler-explorer/libs/rangesv3/trunk/include/concepts/concepts.hpp:1107:13:
required from 'constexpr const bool
concepts::defs::constructible_from<ranges::detail::args_<1, int&>,
ranges::detail::args_<1, const int&> >'
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/utility/common_tuple.hpp:136:9:
required by substitution of 'template<class ... Us>
ranges::common_tuple<int&>::common_tuple(const std::tuple<_Tps ...>&,
std::enable_if_t<(constructible_from<ranges::detail::args_<1, int&>,
ranges::detail::args_<sizeof... (const Ts), const Ts& ...> > &&
concepts::detail::CPP_true(concepts::detail::Nil{})), concepts::detail::Nil>)
[with Us = {int}]'
/opt/compiler-explorer/libs/rangesv3/trunk/include/concepts/type_traits.hpp:92:41:
required by substitution of 'template<class T, class U> struct
concepts::detail::_builtin_common_2<T, U, meta::void_<decltype ((true ?
declval<T>() : declval<U>()))> > [with T = ranges::common_tuple<int&>; U =
std::tuple<int>&]'
/opt/compiler-explorer/libs/rangesv3/trunk/include/concepts/type_traits.hpp:365:12:
recursively required by substitution of 'template<class T, class U> struct
concepts::detail::_common_reference2<T, U, typename
concepts::detail::if_<std::is_reference<typename
concepts::detail::_builtin_common<T, U>::type>::value>::invoke<void> > [with T
= ranges::common_tuple<int&>; U = std::tuple<int>&]'
/opt/compiler-explorer/libs/rangesv3/trunk/include/concepts/type_traits.hpp:365:12:
required from 'struct concepts::common_reference<ranges::common_tuple<int&>,
std::tuple<int>&>'
/opt/compiler-explorer/libs/rangesv3/trunk/include/concepts/type_traits.hpp:370:11:
required by substitution of 'template<class ... Ts> using common_reference_t
= typename concepts::common_reference::type [with Ts =
{ranges::common_tuple<int&>, std::tuple<int>&}]'
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/utility/common_type.hpp:58:11:
required by substitution of 'template<class ... Ts> using common_reference_t
= concepts::common_reference_t<Ts ...> [with Ts =
{ranges::detail::if_then<false>::apply<ranges::detail::basic_proxy_reference_<const
ranges::iter_zip_with_view<ranges::detail::indirect_zip_fn_,
ranges::ref_view<std::vector<int, std::allocator<int> > > >::cursor<false>,
true>, ranges::common_tuple<int&> >, meta::id<std::tuple<int> >::type&}]'
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/iterator/basic_iterator.hpp:453:19:
required from 'struct
ranges::detail::iterator_associated_types_base_<ranges::iter_zip_with_view<ranges::detail::indirect_zip_fn_,
ranges::ref_view<std::vector<int, std::allocator<int> > > >::cursor<false>,
true>'
/opt/compiler-explorer/libs/rangesv3/trunk/include/range/v3/iterator/basic_iterator.hpp:492:31:
required from 'struct
ranges::basic_iterator<ranges::iter_zip_with_view<ranges::detail::indirect_zip_fn_,
ranges::ref_view<std::vector<int, std::allocator<int> > > >::cursor<false> >'
<source>:17:16: required from here
/opt/compiler-explorer/libs/rangesv3/trunk/include/meta/meta.hpp:1222:11:
internal compiler error: canonical types differ for identical types
'std::integral_constant<bool, and_v<__is_constructible(Ts)...> >' and
'std::integral_constant<bool, and_v<__is_constructible(Ts)...> >'
1222 | using if_c = _t<detail::_if_<list<bool_<If>, Args...>>>;
| ^~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-661160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 05:36:28 2019
Return-Path: <gcc-bugs-return-661160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66960 invoked by alias); 25 Nov 2019 05:36:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66906 invoked by uid 48); 25 Nov 2019 05:36:24 -0000
From: "wwwhhhyyy333 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92651] New: [10 Regression] Unnecessary stv transform in some x86 backend
Date: Mon, 25 Nov 2019 05:36: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: wwwhhhyyy333 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-92651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02954.txt.bz2
Content-length: 1951
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92651
Bug ID: 92651
Summary: [10 Regression] Unnecessary stv transform in some x86
backend
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: wwwhhhyyy333 at gmail dot com
CC: rguenther at suse dot de
Target Milestone: ---
For test case
#include <math.h>
int foo(unsigned char a, unsigned char b)
{
int isum=abs(a - b);
return isum;
}
Using -O2 -march=corei7 GCC generates:
movzx edi, dil
movzx esi, sil
movd xmm1, edi
movd xmm0, esi
movdqa xmm3, xmm1
psubd xmm3, xmm0
psubd xmm0, xmm1
pmaxsd xmm0, xmm3
movd eax, xmm0
ret
while on -O2 -march=x86-64 it will be:
movzx eax, dil
movzx esi, sil
sub eax, esi
cdq
xor eax, edx
sub eax, edx
ret
On other case using -O2 -march=corei7 -mtune=generic:
movzx edi, dil
movzx esi, sil
mov eax, edi
sub eax, esi
sub esi, edi
cmp eax, esi
cmovl eax, esi
ret
This happens since r277481. (Refers to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91154). In STV2 the transform was
executed since the sse_to_integer RTL cost for corei7 is 2, which made the
conversion worthwhile for some cmove instructions. I think it affects most IA
processors with such kind of cost.
The stv conversion results in about 7% regression on 525.x264_r. I wonder if
the conversion is designed on purpose to handle cmove, if not I think it is
better to adjust sse_to_integer RTL cost to avoid such issue. According to my
experiment, 6 would be a proper value.
>From gcc-bugs-return-661161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 06:13:02 2019
Return-Path: <gcc-bugs-return-661161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92703 invoked by alias); 25 Nov 2019 06:13: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 92644 invoked by uid 48); 25 Nov 2019 06:12:58 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92646] Compilation fails on armv7l with sys/cdefs.h: No such file or directory
Date: Mon, 25 Nov 2019 06:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92646-4-MaXDFz0yr6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02955.txt.bz2
Content-length: 555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92646
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-11-25
Ever confirmed|0 |1
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
What distro is this?
And what happens if you build not in the source directory?
>From gcc-bugs-return-661162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 07:02:39 2019
Return-Path: <gcc-bugs-return-661162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122535 invoked by alias); 25 Nov 2019 07:02:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122488 invoked by uid 48); 25 Nov 2019 07:02:35 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92649] dead store elimination
Date: Mon, 25 Nov 2019 07:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92649-4-6m9IxfdCaa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02956.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92649
prathamesh3492 at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |prathamesh3492 at gcc dot gnu.org
--- Comment #1 from prathamesh3492 at gcc dot gnu.org ---
This is likely dup of PR89332.
Thanks,
Prathamesh
>From gcc-bugs-return-661163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 07:36:56 2019
Return-Path: <gcc-bugs-return-661163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27560 invoked by alias); 25 Nov 2019 07:36:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27111 invoked by uid 48); 25 Nov 2019 07:36:49 -0000
From: "boostcpp at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92652] New: function call to lambda expression that return true does not satisfy the constraint in requires-clause
Date: Mon, 25 Nov 2019 07:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: boostcpp 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-92652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02957.txt.bz2
Content-length: 1225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92652
Bug ID: 92652
Summary: function call to lambda expression that return true
does not satisfy the constraint in requires-clause
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: boostcpp at gmail dot com
Target Milestone: ---
Following code has unsatisfied constraint with error messages
prog.cc:15:25: error: could not convert 'true' from 'bool' to 'auto'
prog.cc: In lambda function:
prog.cc:15:25: error: invalid use of 'auto'
template < typename T >
requires ([]{return true ;}())
void h() { }
int main()
{
h() ; // unsatisfied constraint
}
if require-clause is like: requires(yes()), with the yes was defined like this.
constexpr auto yes(){ return true ; }
It satisfy the constraint.
As well as : requires( []()->bool{return true; }() )
but requires( []{return true;}() ) does not satisfy the constraint which I
believe it satisfy the constraint.
The entire code example.
https://wandbox.org/permlink/tlkVJFEp3LbSWqhf
>From gcc-bugs-return-661164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:21:25 2019
Return-Path: <gcc-bugs-return-661164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71828 invoked by alias); 25 Nov 2019 08:21:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71758 invoked by uid 48); 25 Nov 2019 08:21:21 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/90576] [10 regression] SPEC CPU2006 450.soplex miscompiled with -Os -flto after r271413
Date: Mon, 25 Nov 2019 08:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90576-4-tawW0orn8v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90576-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02958.txt.bz2
Content-length: 158
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90576
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
@Maxim: Can you please retest it?
>From gcc-bugs-return-661165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:25:43 2019
Return-Path: <gcc-bugs-return-661165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75393 invoked by alias); 25 Nov 2019 08:25:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75319 invoked by uid 48); 25 Nov 2019 08:25:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92653] New: [10 Regression] PGO bootstrap is broken with --with-build-config=bootstrap-lto-lean
Date: Mon, 25 Nov 2019 08:25: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: 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-92653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02959.txt.bz2
Content-length: 3922
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92653
Bug ID: 92653
Summary: [10 Regression] PGO bootstrap is broken with
--with-build-config=bootstrap-lto-lean
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Target Milestone: ---
I see the following ICE:
[11752s]
/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/./prev-gcc/xg++
-B/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/./prev-gcc/
-B/usr/x86_64-suse-linux/bin/ -nostdinc++
-B/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/src/.libs
-B/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/libsupc++/.libs
-I/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/include/x86_64-suse-linux
-I/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/include
-I/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/libstdc++-v3/libsupc++
-L/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/src/.libs
-L/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/prev-x86_64-suse-linux/libstdc++-v3/libsupc++/.libs
-no-pie -O2 -D_FORTIFY_SOURCE=2 -funwind-tables -fasynchronous-unwind-tables
-fstack-clash-protection -Werror=return-type -U_FORTIFY_SOURCE -fprofile-use
-flto=jobserver -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables
-W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wno-error=format-diag
-Wmissing-format-attribute -Woverloaded-virtual -pedantic -Wno-long-long
-Wno-variadic-macros -Wno-overlength-strings -fno-common -DHAVE_CONFIG_H
-static-libstdc++ -static-libgcc -o f951 fortran/arith.o fortran/array.o
fortran/bbt.o fortran/check.o fortran/class.o fortran/constructor.o
fortran/cpp.o fortran/data.o fortran/decl.o fortran/dump-parse-tree.o
fortran/error.o fortran/expr.o fortran/interface.o fortran/intrinsic.o
fortran/io.o fortran/iresolve.o fortran/match.o fortran/matchexp.o
fortran/misc.o fortran/module.o fortran/openmp.o fortran/options.o
fortran/parse.o fortran/primary.o fortran/resolve.o fortran/scanner.o
fortran/simplify.o fortran/st.o fortran/symbol.o fortran/target-memory.o
fortran/convert.o fortran/dependency.o fortran/f95-lang.o fortran/trans.o
fortran/trans-array.o fortran/trans-common.o fortran/trans-const.o
fortran/trans-decl.o fortran/trans-expr.o fortran/trans-intrinsic.o
fortran/trans-io.o fortran/trans-openmp.o fortran/trans-stmt.o
fortran/trans-types.o fortran/frontend-passes.o libbackend.a main.o
libcommon-target.a libcommon.a ../libcpp/libcpp.a
../libdecnumber/libdecnumber.a -lz libcommon.a ../libcpp/libcpp.a
../libbacktrace/.libs/libbacktrace.a ../libiberty/libiberty.a
../libdecnumber/libdecnumber.a attribs.o -lisl -lmpc -lmpfr -lgmp -rdynamic
-ldl -lz -lzstd
[11805s] during IPA pass: inline
[11805s] lto1: internal compiler error: in account_size_time, at
ipa-fnsummary.c:230
[11805s] 0x761409 ???
[11805s] ../sysdeps/x86_64/start.S:120
[11805s] Please submit a full bug report,
[11805s] with preprocessed source if appropriate.
[11805s] Please include the complete backtrace with any bug report.
[11805s] See <https://bugs.opensuse.org/> for instructions.
[11806s] lto-wrapper: fatal error:
/home/abuild/rpmbuild/BUILD/gcc-10.0.0+r278624/obj-x86_64-suse-linux/./prev-gcc/xg++
returned 1 exit status
[11806s] compilation terminated.
[11806s] /usr/x86_64-suse-linux/bin/ld: error: lto-wrapper failed
>From gcc-bugs-return-661166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:26:02 2019
Return-Path: <gcc-bugs-return-661166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76256 invoked by alias); 25 Nov 2019 08:26: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 76151 invoked by uid 48); 25 Nov 2019 08:25:58 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92653] [10 Regression] PGO bootstrap is broken with --with-build-config=bootstrap-lto-lean
Date: Mon, 25 Nov 2019 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed bug_severity
Message-ID: <bug-92653-4-RmF22s6ZV0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02960.txt.bz2
Content-length: 659
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92653
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-11-25
Assignee|unassigned at gcc dot gnu.org |hubicka at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
Severity|normal |blocker
>From gcc-bugs-return-661167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:33:50 2019
Return-Path: <gcc-bugs-return-661167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85040 invoked by alias); 25 Nov 2019 08: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 84946 invoked by uid 48); 25 Nov 2019 08:33:46 -0000
From: "franz.flasch at gmx dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92484] In tree build of ISL 0.22 fails: requires C++11
Date: Mon, 25 Nov 2019 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: franz.flasch at gmx dot at
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-92484-4-wwLbJXHyvp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92484-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92484-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02961.txt.bz2
Content-length: 964
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92484
franz <franz.flasch at gmx dot at> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |franz.flasch at gmx dot at
--- Comment #4 from franz <franz.flasch at gmx dot at> ---
It seems this issue only occurs if the host machine and the target machine are
identical, as it does not occur when crosscompilers are built.
E.g. when building a crosscompiler for arm isl builds just fine. I checked the
config.status and it seems that the c++11 compiler flag is not being set in
case of a crosscompiler build:
CXX variable for arm crosscompiler build in config.log:
CXX='g++'
CXX variable for x86_64 native compiler build in config.log:
CXX='g++ -std=gnu++98 -std=c++11'
Is there any way of telling the buildprocess to not use those c++11 compiler
flag for isl?
>From gcc-bugs-return-661168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:36:57 2019
Return-Path: <gcc-bugs-return-661168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88981 invoked by alias); 25 Nov 2019 08:36:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88939 invoked by uid 48); 25 Nov 2019 08:36:52 -0000
From: "anthony.ajw at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92616] Inconsistency in time between system_clock::now() and time(nullptr)
Date: Mon, 25 Nov 2019 08:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anthony.ajw 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-92616-4-jeIZC0C3Ub@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92616-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02962.txt.bz2
Content-length: 222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92616
--- Comment #7 from Anthony Williams <anthony.ajw at gmail dot com> ---
Reported as ubuntu bug:
https://bugs.launchpad.net/ubuntu/+source/linux-signed-oem/+bug/1853807
>From gcc-bugs-return-661169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:40:13 2019
Return-Path: <gcc-bugs-return-661169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91464 invoked by alias); 25 Nov 2019 08:40: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 91360 invoked by uid 48); 25 Nov 2019 08:40:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92632] Calculix regression
Date: Mon, 25 Nov 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-92632-4-or7ceZrHxt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92632-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92632-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02963.txt.bz2
Content-length: 572
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92632
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |marxin at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Dup.
*** This bug has been marked as a duplicate of bug 92584 ***
>From gcc-bugs-return-661170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:40:13 2019
Return-Path: <gcc-bugs-return-661170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91476 invoked by alias); 25 Nov 2019 08:40: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 91384 invoked by uid 48); 25 Nov 2019 08:40:08 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92584] A 454.calculix optimization opportunity
Date: Mon, 25 Nov 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92584-4-jY8ZCMqBtK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92584-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92584-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02964.txt.bz2
Content-length: 451
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92584
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
*** Bug 92632 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-661171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:59:43 2019
Return-Path: <gcc-bugs-return-661171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108348 invoked by alias); 25 Nov 2019 08:59:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108257 invoked by uid 55); 25 Nov 2019 08:59:38 -0000
From: "gjl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92055] [avr] Support 64-bit double
Date: Mon, 25 Nov 2019 08:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: gjl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: gjl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92055-4-ewpBWqUA19@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92055-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92055-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02965.txt.bz2
Content-length: 967
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92055
--- Comment #10 from Georg-Johann Lay <gjl at gcc dot gnu.org> ---
Author: gjl
Date: Mon Nov 25 08:59:06 2019
New Revision: 278668
URL: https://gcc.gnu.org/viewcvs?rev=278668&root=gcc&view=rev
Log:
gcc/
Build double32 / long-double32 multilibs if needed.
PR target/92055
* config/avr/t-avr:
(HAVE_DOUBLE_MULTILIB, HAVE_LONG_DOUBLE_MULTILIB): Remove vars.
(HAVE_DOUBLE32, HAVE_LONG_DOUBLE32, WITH_LONG_DOUBLE)
(HAVE_DOUBLE64, HAVE_LONG_DOUBLE64, WITH_DOUBLE): Set from
tm_defines and pass to genmultilib.awk.
* config/avr/genmultilib.awk: Use these variables to add double32
and / or long-double32 multilib(s) as needed.
* config/avr/driver-avr.c (avr_double_lib): Adjust comment.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/avr/driver-avr.c
trunk/gcc/config/avr/genmultilib.awk
trunk/gcc/config/avr/t-avr
>From gcc-bugs-return-661172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 08:59:53 2019
Return-Path: <gcc-bugs-return-661172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109114 invoked by alias); 25 Nov 2019 08:59: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 109063 invoked by uid 48); 25 Nov 2019 08:59:48 -0000
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92654] New: internal compiler error: in lookup_template_class_1
Date: Mon, 25 Nov 2019 08:59: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: fiesh at zefix dot tv
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-92654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02966.txt.bz2
Content-length: 1667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92654
Bug ID: 92654
Summary: internal compiler error: in lookup_template_class_1
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: fiesh at zefix dot tv
Target Milestone: ---
The following code results in an internal compiler error in 8, 9, and trunk:
namespace a {
template <typename b, b>
struct c {};
template <typename>
using d = int;
template <typename b, b...>
struct e {};
template <typename b, b g>
using h = e<b, __integer_pack(g)...>;
} // namespace a
template <typename ab, typename i, i... ac>
void ad(ab f, a::e<i, ac...>) {
(f(a::c<i, ac>{}), ...);
}
template <auto j, typename ab>
void k(ab f) {
using i = a::d<decltype(j)>;
using l = a::h<i, j>;
ad(f, l{});
}
template <typename ag, typename ab>
void ah(ab f) {
auto a{f};
k<m(ag{})>(a);
}
enum n {};
constexpr int m(n) { return 2; }
template <n>
struct o;
template <template <n, long, n, long> typename>
void am() {
ah<n>([](auto an) {
auto b = decltype(an)();
[b] {
if constexpr (o<b>::aq)
;
};
});
}
template <n, long, n, long>
struct p;
void as() { am<p>; }
% g++ -std=c++17 crash.cpp
...
crash.cpp:34:5: internal compiler error: in lookup_template_class_1, at
cp/pt.c:9546
Although we ran into the bugs entirely independently, maybe it's related to
#92583?
>From gcc-bugs-return-661173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:00:55 2019
Return-Path: <gcc-bugs-return-661173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110867 invoked by alias); 25 Nov 2019 09: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 110755 invoked by uid 48); 25 Nov 2019 09:00:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92655] New: Suboptimal vectorization of variable shift
Date: Mon, 25 Nov 2019 09:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02967.txt.bz2
Content-length: 1221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92655
Bug ID: 92655
Summary: Suboptimal vectorization of variable shift
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
For the following testcase vect_recog_vector_vector_shift_pattern isn't able
to fully elide the use of 'int' and thus we fall back to vectorization with
SSE instead of AVX with -O3 -march=core-avx2
#define MULSEQ {32,34,35,38}
#define STRIDE 4
#define M61 2305843009213693951ULL
#define BITS 61
typedef unsigned long uint64_t;
typedef struct myvec_t { uint64_t __attribute__ ((aligned (32))) val[STRIDE]; }
__attribute__ ((aligned (32))) myvec_t;
inline uint64_t MULWU(uint64_t k, uint64_t m)
{
return (( (k)<<(m) & M61) + ( (k) >> (BITS-m)) ) ;
}
myvec_t MULWU(myvec_t x)
{
myvec_t __attribute__ ((aligned (32))) v;
myvec_t __attribute__ ((aligned (32))) SPECIALMUL=MULSEQ;
for(int j=0;j<STRIDE;j++)
v.val[j] = MULWU(x.val[j], SPECIALMUL.val[j]);
return v;
}
>From gcc-bugs-return-661174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:10:48 2019
Return-Path: <gcc-bugs-return-661174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117376 invoked by alias); 25 Nov 2019 09:10: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 117335 invoked by uid 48); 25 Nov 2019 09:10:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92655] Suboptimal vectorization of variable shift
Date: Mon, 25 Nov 2019 09:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92655-4-Z4rMQRr0n2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02968.txt.bz2
Content-length: 3293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92655
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-25
CC| |jakub at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue here is that we see
t.ii:10:76: note: ==> examining statement: _2 = x.val[j_22];
t.ii:10:76: note: precomputed vectype: vector(4) long unsigned int
t.ii:10:76: note: nunits = 4
t.ii:10:76: note: ==> examining statement: _10 = (unsigned int) _1;
t.ii:10:76: note: get vectype for scalar type: unsigned int
t.ii:10:76: note: vectype: vector(8) unsigned int
t.ii:10:76: note: nunits = 8
t.ii:10:76: note: ==> examining statement: _14 = _2 << _10;
t.ii:10:76: note: skip.
t.ii:10:76: note: ==> examining pattern def stmt: patt_38 = _1 & 4294967295;
t.ii:10:76: note: precomputed vectype: vector(4) long unsigned int
t.ii:10:76: note: nunits = 4
t.ii:10:76: note: ==> examining pattern statement: patt_37 = _2 << patt_38;
t.ii:10:76: note: precomputed vectype: vector(4) long unsigned int
...
t.ii:10:76: note: ==> examining statement: _16 = 61 - _10;
t.ii:10:76: note: get vectype for scalar type: unsigned int
t.ii:10:76: note: vectype: vector(8) unsigned int
t.ii:10:76: note: nunits = 8
t.ii:10:76: note: ==> examining statement: _17 = _2 >> _16;
t.ii:10:76: note: skip.
t.ii:10:76: note: ==> examining pattern def stmt: patt_36 = (long unsigned
int) _16;
t.ii:10:76: note: precomputed vectype: vector(4) long unsigned int
t.ii:10:76: note: get vectype for smallest scalar type: unsigned int
t.ii:10:76: note: nunits vectype: vector(8) unsigned int
t.ii:10:76: note: nunits = 8
t.ii:10:76: note: ==> examining pattern statement: patt_35 = _2 >> patt_36;
t.ii:10:76: note: precomputed vectype: vector(4) long unsigned int
t.ii:10:76: note: nunits = 4
because
<bb 3> [local count: 858993460]:
# j_22 = PHI <0(2), j_12(5)>
# ivtmp_40 = PHI <4(2), ivtmp_39(5)>
_1 = SPECIALMUL.val[j_22];
_2 = x.val[j_22];
_10 = (unsigned int) _1;
_14 = _2 << _10;
_15 = _14 & 2305843009213693951;
_16 = 61 - _10;
_17 = _2 >> _16;
_18 = _15 + _17;
<retval>.val[j_22] = _18;
j_12 = j_22 + 1;
ivtmp_39 = ivtmp_40 - 1;
if (ivtmp_39 == 0)
goto <bb 4>; [25.00%]
else
goto <bb 5>; [75.00%]
so _10 is used twice and the 2nd shift argument isn't promoted to unsigned long
by any pattern (instead it was demoted earlier). Even if fixing that
in source there's vect_recog_over_widening_pattern undoing that:
t.ii:10:76: note: vect_recog_over_widening_pattern: detected: xyz_10 = 61 -
_1;
t.ii:10:76: note: demoting long unsigned int to unsigned int
t.ii:10:76: note: created pattern stmt: patt_40 = 61 - patt_41;
:/
so it looks like those work against each other here.
>From gcc-bugs-return-661175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:11:37 2019
Return-Path: <gcc-bugs-return-661175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118410 invoked by alias); 25 Nov 2019 09:11:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118370 invoked by uid 48); 25 Nov 2019 09:11:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92655] Suboptimal vectorization of variable shift
Date: Mon, 25 Nov 2019 09:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92655-4-jINQ3QZPxm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02969.txt.bz2
Content-length: 338
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92655
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
"Fixed" source (MULWU), side-stepping GENERIC folding/narrowing of the
subtract:
inline uint64_t MULWU(uint64_t k, uint64_t m)
{
unsigned long xyz = BITS-m;
return (( (k)<<(m) & M61) + ( (k) >> (xyz)) ) ;
}
>From gcc-bugs-return-661176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:21:28 2019
Return-Path: <gcc-bugs-return-661176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128059 invoked by alias); 25 Nov 2019 09:21: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 127992 invoked by uid 48); 25 Nov 2019 09:21:24 -0000
From: "samyavrillon at netcourrier dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92646] Compilation fails on armv7l with sys/cdefs.h: No such file or directory
Date: Mon, 25 Nov 2019 09:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samyavrillon at netcourrier 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-92646-4-t22ZcLHu87@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02970.txt.bz2
Content-length: 1610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92646
--- Comment #2 from Mysaa <samyavrillon at netcourrier dot com> ---
I tried again to compile in a dedicated directory, the same error occurs :
/home/bernard/building/gcc-9.2.0/bld/./gcc/xgcc
-B/home/bernard/building/gcc-9.2.0/bld/./gcc/
-B/usr/local/armv7l-unknown-linux-gnueabihf/bin/
-B/usr/local/armv7l-unknown-linux-gnueabihf/lib/ -isystem
/usr/local/armv7l-unknown-linux-gnueabihf/include -isystem
/usr/local/armv7l-unknown-linux-gnueabihf/sys-include -fno-checking -g -O2
-O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual
-Wno-format -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition
-isystem ./include -fPIC -fno-inline -g -DIN_LIBGCC2 -fbuilding-libgcc
-fno-stack-protector -fPIC -fno-inline -I. -I. -I../.././gcc
-I../../../libgcc -I../../../libgcc/. -I../../../libgcc/../gcc
-I../../../libgcc/../include -DHAVE_CC_TLS -o _muldi3.o -MT _muldi3.o -MD -MP
-MF _muldi3.dep -DL_muldi3 -c ../../../libgcc/libgcc2.c -fvisibility=hidden
-DHIDE_EXPORTS
In file included from /usr/include/stdio.h:27,
from ../../../libgcc/../gcc/tsystem.h:87,
from ../../../libgcc/libgcc2.c:27:
/usr/include/features.h:364:12: fatal error: sys/cdefs.h: No such file or
directory 364 | # include <sys/cdefs.h>
| ^~~~~~~~~~~~~
compilation terminated.
I am on Armbian, a arm version of debian for OrangepiPC, with a dedicated apt
repository.
>From gcc-bugs-return-661177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:31:20 2019
Return-Path: <gcc-bugs-return-661177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14810 invoked by alias); 25 Nov 2019 09:31:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13647 invoked by uid 48); 25 Nov 2019 09:31:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92642] Enhance shift-count-overflow output
Date: Mon, 25 Nov 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed bug_severity
Message-ID: <bug-92642-4-1qmXSA5qAO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02971.txt.bz2
Content-length: 771
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92642
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-25
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(A) seems pointless in this case, it's right there in the caret diagnostic.
The type size_t is irrelevant.
IMO a better testcase would be:
const int n = 41;
auto x = 1 << n;
>From gcc-bugs-return-661178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:33:48 2019
Return-Path: <gcc-bugs-return-661178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21081 invoked by alias); 25 Nov 2019 09:33: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 21040 invoked by uid 48); 25 Nov 2019 09:33:44 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/92616] Inconsistency in time between system_clock::now() and time(nullptr)
Date: Mon, 25 Nov 2019 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi 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-92616-4-dM1y09Y0FT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92616-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02972.txt.bz2
Content-length: 462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92616
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |MOVED
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
OK, let's close this as MOVED then, thanks!
>From gcc-bugs-return-661179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:38:06 2019
Return-Path: <gcc-bugs-return-661179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24486 invoked by alias); 25 Nov 2019 09:38: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 24430 invoked by uid 48); 25 Nov 2019 09:38:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92651] [10 Regression] Unnecessary stv transform in some x86 backend
Date: Mon, 25 Nov 2019 09:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc target_milestone
Message-ID: <bug-92651-4-c3rGt2D4xg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02973.txt.bz2
Content-length: 2101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92651
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC|rguenther at suse dot de |rguenth at gcc dot gnu.org
Target Milestone|--- |10.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, we expand from
_1 = (int) a_4(D);
_2 = (int) b_5(D);
_3 = _1 - _2;
isum_6 = ABS_EXPR <_3>;
return isum_6;
where ABS_EXPR expansion seems to like using smax (and if not smax then
conditional move).
(insn 11 10 12 (parallel [
(set (reg:SI 93)
(minus:SI (reg:SI 91)
(reg:SI 92)))
(clobber (reg:CC 17 flags))
]) "t3.c":3:30 -1
(nil))
(insn 12 11 13 (parallel [
(set (reg:SI 94)
(neg:SI (reg:SI 93)))
(clobber (reg:CC 17 flags))
]) "t3.c":3:9 -1
(nil))
(insn 13 12 14 (parallel [
(set (reg:SI 90 [ isum ])
(smax:SI (reg:SI 93)
(reg:SI 94)))
(clobber (reg:CC 17 flags))
]) "t3.c":3:9 -1
(nil))
expand_abs_nojump first looks for an abs pattern (which we have none - but
STV to the rescue!) and then uses MAX(x, -x) if we have a max pattern
which we now have, thanks to r277481. That would turn into a cmov
sequence later in case STV finds the transform not worthwhile.
For corei7:
Computing gain for chain #1...
Instruction gain 8 for 13: {r90:SI=smax(r93:SI,r94:SI);clobber flags:CC;}
REG_DEAD r94:SI
REG_DEAD r93:SI
REG_UNUSED flags:CC
Instruction conversion gain: 8
Registers conversion cost: 6
Total gain: 2
while the rev. wasn't intended to cover abs() it was intended to cover
cmov because cmov exhibits weird performance characteristics and the
lack of min/max (and here abs) instructions on the GPR side is quite bad.
>From gcc-bugs-return-661180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 09:40:36 2019
Return-Path: <gcc-bugs-return-661180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28758 invoked by alias); 25 Nov 2019 09:40:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28716 invoked by uid 48); 25 Nov 2019 09:40:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92651] [10 Regression] Unnecessary stv transform in some x86 backend
Date: Mon, 25 Nov 2019 09:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92651-4-CA5NbQHBCX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92651-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92651-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02974.txt.bz2
Content-length: 387
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92651
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Btw, which variant is actually the fastest for you? abs expansion doesn't
do any cost comparison but just uses direct abs, max and then the xor with
shift as third option (and after that fall back to compare & jump which later
might be if-converted into cmov).
>From gcc-bugs-return-661181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:01:19 2019
Return-Path: <gcc-bugs-return-661181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48065 invoked by alias); 25 Nov 2019 10:01:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48027 invoked by uid 48); 25 Nov 2019 10:01:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92626] [9/10 Regression] Performance regression in compress-rar on CLX server
Date: Mon, 25 Nov 2019 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget component cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-92626-4-7AAF5yniLT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92626-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92626-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02975.txt.bz2
Content-length: 1111
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92626
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization,
| |needs-bisection
Target| |x86_64-*-*
Component|c |target
Known to work| |9.2.0
Target Milestone|--- |9.3
Summary|Performance regression in |[9/10 Regression]
|compress-rar on CLX server |Performance regression in
| |compress-rar on CLX server
Known to fail| |9.2.1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
That's a lot of changes, bisection might help to track down things further. I
suspect the same regression happens on trunk from wherever the rev. was
backported from.
>From gcc-bugs-return-661182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:02:17 2019
Return-Path: <gcc-bugs-return-661182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49153 invoked by alias); 25 Nov 2019 10:02:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49098 invoked by uid 48); 25 Nov 2019 10:02:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBtaWRkbGUtZW5kLzkyNjI4XSBNYWtlIHVzZSBvZiBUWVBFX1JFU1RS?= =?UTF-8?B?SUNUIGZvciBmdW5jdGlvbi1jYWxsIHBvaW50ZXItZXNjYXBlIGFuYWx5c2lz?= =?UTF-8?B?IOKAkyBlc3BlY2lhbGx5IGZvciBGb3J0cmFu?Date: Mon, 25 Nov 2019 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: blocked
Message-ID: <bug-92628-4-ari2wMC8ay@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92628-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92628-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02976.txt.bz2
Content-length: 586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92628
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Blocks| |49774
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think we have a duplicate asking about restrict to have an effect on
function calls.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49774
[Bug 49774] [meta-bug] restrict qualification aliasing issues
>From gcc-bugs-return-661183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:07:45 2019
Return-Path: <gcc-bugs-return-661183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52774 invoked by alias); 25 Nov 2019 10:07:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52699 invoked by uid 48); 25 Nov 2019 10:07:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] g++ -Wconversion misses int to size_t
Date: Mon, 25 Nov 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85861-4-Dzg4BiqNCj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02977.txt.bz2
Content-length: 1037
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonny Grant from comment #13)
> (In reply to Jonathan Wakely from comment #11)
> > My guess is that we don't want to warn about conversions that are
> > well-defined and the original value can be obtained by a round-trip.
> > Converting a size_t to an int is lossy, i.e. converting back to size_t may
> > not give the original value. But converting an int to size_t and back to an
> > int is value preserving.
>
> Do you mean because size_t is 64bit typically, and int is only 32bit?
>
> I tested this on my 64bit Ubuntu
> It converts a size_t 9,223,372,036,854,775,807 to an int
Which gives -1.
> and ends up with 18,446,744,073,709,551,615
Because that's what (size_t)-1 equals.
>
> Which I was surprised about, as I thought int was 4 bytes.
It is.
> I had expected
> 4,294,967,295
You converted to size_t, not unsigned int.
See https://en.wikipedia.org/wiki/Sign_extension
>From gcc-bugs-return-661184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:08:21 2019
Return-Path: <gcc-bugs-return-661184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53711 invoked by alias); 25 Nov 2019 10:08:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53651 invoked by uid 48); 25 Nov 2019 10:08:16 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92646] Compilation fails on armv7l with sys/cdefs.h: No such file or directory
Date: Mon, 25 Nov 2019 10: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92646-4-KPx6Gabzx8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02978.txt.bz2
Content-length: 154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92646
--- Comment #3 from Andreas Schwab <schwab@linux-m68k.org> ---
Where is <sys/cdefs.h> located then?
>From gcc-bugs-return-661185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:08:29 2019
Return-Path: <gcc-bugs-return-661185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54381 invoked by alias); 25 Nov 2019 10:08: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 54322 invoked by uid 48); 25 Nov 2019 10:08:26 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBtaWRkbGUtZW5kLzkyNjI4XSBNYWtlIHVzZSBvZiBUWVBFX1JFU1RS?= =?UTF-8?B?SUNUIGZvciBmdW5jdGlvbi1jYWxsIHBvaW50ZXItZXNjYXBlIGFuYWx5c2lz?= =?UTF-8?B?IOKAkyBlc3BlY2lhbGx5IGZvciBGb3J0cmFu?Date: Mon, 25 Nov 2019 10:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-92628-4-xoi2B82lKE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92628-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92628-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02979.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92628
--- Comment #4 from Tobias Burnus <burnus at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> I think we have a duplicate asking about restrict to have an effect on
> function calls.
Could be PR tree-optimization/81008.
>From gcc-bugs-return-661186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:10:18 2019
Return-Path: <gcc-bugs-return-661186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56283 invoked by alias); 25 Nov 2019 10:10:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56248 invoked by uid 55); 25 Nov 2019 10:10:13 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/91956] [10 Regression] ICE: verify_cgraph_node failed (error: comdat-local function called by __ct .isra outside its comdat) since r275982
Date: Mon, 25 Nov 2019 10:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
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:
Message-ID: <bug-91956-4-6EAuY46SaM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91956-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02980.txt.bz2
Content-length: 710
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91956
--- Comment #3 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Mon Nov 25 10:09:42 2019
New Revision: 278669
URL: https://gcc.gnu.org/viewcvs?rev=278669&root=gcc&view=rev
Log:
Make IPA-SRA follow comdat-local rules (PR 91956)
2019-11-25 Martin Jambor <mjambor@suse.cz>
PR ipa/91956
* ipa-sra.c (process_isra_node_results): Put the new node to the
same comdat group as the original node.
testsuite/
* g++.dg/ipa/pr91956.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/ipa/pr91956.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-sra.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:11:46 2019
Return-Path: <gcc-bugs-return-661187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58906 invoked by alias); 25 Nov 2019 10:11: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 58839 invoked by uid 48); 25 Nov 2019 10:11:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/92634] [8/9/10 regression] -fsanitize=undefined erroneous null pointer check
Date: Mon, 25 Nov 2019 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-92634-4-CGHvvwl4Dv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92634-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92634-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02981.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92634
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.4
>From gcc-bugs-return-661188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:13:43 2019
Return-Path: <gcc-bugs-return-661188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60595 invoked by alias); 25 Nov 2019 10: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 60528 invoked by uid 55); 25 Nov 2019 10:13:39 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92109] [10 Regression] ICE in modify_call_stmt, at ipa-param-manipulation.c:1586
Date: Mon, 25 Nov 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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: ASSIGNED
X-Bugzilla-Resolution:
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:
Message-ID: <bug-92109-4-gZmZtT7uXO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02982.txt.bz2
Content-length: 901
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92109
--- Comment #8 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Mon Nov 25 10:13:08 2019
New Revision: 278670
URL: https://gcc.gnu.org/viewcvs?rev=278670&root=gcc&view=rev
Log:
ipa: Prevent materialization of clones with removed bodies (PR 92109)
2019-11-25 Martin Jambor <mjambor@suse.cz>
PR ipa/92109
* cgraph.h (cgraph_node::remove_from_clone_tree): Declare.
* cgraphclones.c (cgraph_node::remove_from_clone_tree): New method.
(cgraph_materialize_clone): Move removel from clone tree to the
the new method and use it instead.
* ipa.c (symbol_table::remove_unreachable_nodes): When removing
bodies of clones, also remove it from the clone tree.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cgraph.h
trunk/gcc/cgraphclones.c
trunk/gcc/ipa.c
>From gcc-bugs-return-661189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:14:07 2019
Return-Path: <gcc-bugs-return-661189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61631 invoked by alias); 25 Nov 2019 10:14:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61587 invoked by uid 48); 25 Nov 2019 10:14:03 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/91956] [10 Regression] ICE: verify_cgraph_node failed (error: comdat-local function called by __ct .isra outside its comdat) since r275982
Date: Mon, 25 Nov 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
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-91956-4-ouIKQ6S1fr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91956-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02983.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91956
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:14:47 2019
Return-Path: <gcc-bugs-return-661190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62545 invoked by alias); 25 Nov 2019 10:14:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62506 invoked by uid 48); 25 Nov 2019 10:14:43 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/92109] [10 Regression] ICE in modify_call_stmt, at ipa-param-manipulation.c:1586
Date: Mon, 25 Nov 2019 10:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: 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-92109-4-GUHrZYg1b3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92109-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92109-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02984.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92109
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:22:01 2019
Return-Path: <gcc-bugs-return-661191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71249 invoked by alias); 25 Nov 2019 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 71203 invoked by uid 48); 25 Nov 2019 10:21:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92638] gcc unable to remove empty loop after loop body is removed after malloc/free pair was removed
Date: Mon, 25 Nov 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92638-4-oAUbSGeIUB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02985.txt.bz2
Content-length: 666
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92638
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's not really "iteration" that is missing but the free () stmt is marked
as necessary and only later "elided" but dataflow makes the loop necessary
because of that. We may eventually get away with not considering free
as needed (it doesn't have any output), but propagation will never make
it so so we'd have to fixup manually somehow.
One "fix" would be to turn one of the earlier DCE passes into CD-DCE ones
(I'd really like to unify the passes and make CD vs non-CD a pass
parameter but that requires extensive testsuite adjustments...)
>From gcc-bugs-return-661192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:25:40 2019
Return-Path: <gcc-bugs-return-661192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74253 invoked by alias); 25 Nov 2019 10:25: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 74137 invoked by uid 48); 25 Nov 2019 10:25:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92644] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530
Date: Mon, 25 Nov 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
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-92644-4-cxRmaDPps9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02986.txt.bz2
Content-length: 138
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92644
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
INTEGRAL_TYPE_P
>From gcc-bugs-return-661193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:30:42 2019
Return-Path: <gcc-bugs-return-661193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80456 invoked by alias); 25 Nov 2019 10:30:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80242 invoked by uid 55); 25 Nov 2019 10:30:30 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92575] couple of suspicious assignments in expect.c
Date: Mon, 25 Nov 2019 10:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92575-4-Pi2Wwifau2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02987.txt.bz2
Content-length: 417
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92575
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Mon Nov 25 10:29:51 2019
New Revision: 278671
URL: https://gcc.gnu.org/viewcvs?rev=278671&root=gcc&view=rev
Log:
PR ada/92575
* expect.c (__gnat_expect_poll [VMS, HPUX]): Fix typo.
Modified:
trunk/gcc/ada/ChangeLog
trunk/gcc/ada/expect.c
>From gcc-bugs-return-661195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:31:57 2019
Return-Path: <gcc-bugs-return-661195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83219 invoked by alias); 25 Nov 2019 10:31: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 83142 invoked by uid 55); 25 Nov 2019 10:31:51 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92575] couple of suspicious assignments in expect.c
Date: Mon, 25 Nov 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92575-4-aGFWwVEGQ4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02989.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92575
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Mon Nov 25 10:31:20 2019
New Revision: 278673
URL: https://gcc.gnu.org/viewcvs?rev=278673&root=gcc&view=rev
Log:
PR ada/92575
* expect.c (__gnat_expect_poll [VMS, HPUX]): Fix typo.
Modified:
branches/gcc-8-branch/gcc/ada/ChangeLog
branches/gcc-8-branch/gcc/ada/expect.c
>From gcc-bugs-return-661194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:31:23 2019
Return-Path: <gcc-bugs-return-661194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82069 invoked by alias); 25 Nov 2019 10:31:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81712 invoked by uid 55); 25 Nov 2019 10:31:15 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92575] couple of suspicious assignments in expect.c
Date: Mon, 25 Nov 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92575-4-Jq86phEblZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02988.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92575
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Mon Nov 25 10:30:41 2019
New Revision: 278672
URL: https://gcc.gnu.org/viewcvs?rev=278672&root=gcc&view=rev
Log:
PR ada/92575
* expect.c (__gnat_expect_poll [VMS, HPUX]): Fix typo.
Modified:
branches/gcc-9-branch/gcc/ada/ChangeLog
branches/gcc-9-branch/gcc/ada/expect.c
>From gcc-bugs-return-661197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:33:06 2019
Return-Path: <gcc-bugs-return-661197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84865 invoked by alias); 25 Nov 2019 10:33: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 84672 invoked by uid 48); 25 Nov 2019 10:33:00 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/89863] [meta-bug] Issues that static analyzers (cppcheck, clang-static-analyzer) find that gcc misses
Date: Mon, 25 Nov 2019 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: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-89863-4-2EIVM0OsU4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-89863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-89863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02991.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89863
Bug 89863 depends on bug 92575, which changed state.
Bug 92575 Summary: couple of suspicious assignments in expect.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92575
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-661196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:33:06 2019
Return-Path: <gcc-bugs-return-661196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84828 invoked by alias); 25 Nov 2019 10:33:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84635 invoked by uid 48); 25 Nov 2019 10:33:00 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92575] couple of suspicious assignments in expect.c
Date: Mon, 25 Nov 2019 10:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-92575-4-23KebV439w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92575-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02990.txt.bz2
Content-length: 515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92575
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.4
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Thanks for the reporting the problem.
>From gcc-bugs-return-661198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:43:09 2019
Return-Path: <gcc-bugs-return-661198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92848 invoked by alias); 25 Nov 2019 10:43: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 92775 invoked by uid 48); 25 Nov 2019 10:43:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92644] [9/10 Regression] ICE in wide_int_to_tree_1, at tree.c:1530
Date: Mon, 25 Nov 2019 10:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
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-92644-4-NEK0nObN7E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92644-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02992.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92644
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47350
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47350&action=edit
gcc10-pr92644.patch
Untested fix.
>From gcc-bugs-return-661199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:44:35 2019
Return-Path: <gcc-bugs-return-661199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94398 invoked by alias); 25 Nov 2019 10:44: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 94334 invoked by uid 48); 25 Nov 2019 10:44:31 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Mon, 25 Nov 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-92645-4-daWrREHJyJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02993.txt.bz2
Content-length: 2587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC| |rguenth at gcc dot gnu.org
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
What flags do I need? Hmm, unincluding isn't very successful, with trunk it
seems to at least compile...
I see
<bb 5> [local count: 955630224]:
# ivtmp.13749_388 = PHI <0(4), ivtmp.13749_387(5)>
_571 = {x_111, x_111, x_111, x_111, x_111, x_111, x_111, x_111, x_111, x_111,
x_111, x_111, x_111, x_111, x_111, x_111};
_24 = {color_13(D), color_13(D), color_13(D), color_13(D)};
_93 = MEM[base: src_15(D), index: ivtmp.13749_388, offset: 0B];
_462 = (unsigned int) _93;
_461 = BIT_FIELD_REF <_93, 32, 32>;
_460 = BIT_FIELD_REF <_93, 32, 64>;
_459 = BIT_FIELD_REF <_93, 32, 96>;
MEM <unsigned int> [(struct Vec *)&D.151762] = _462;
MEM <unsigned int> [(struct Vec *)&D.151762 + 4B] = _461;
MEM <unsigned int> [(struct Vec *)&D.151762 + 8B] = _460;
MEM <unsigned int> [(struct Vec *)&D.151762 + 12B] = _459;
src_2 = MEM[(struct Vec *)&D.151762];
_32 = (unsigned char) src_2;
_33 = BIT_FIELD_REF <src_2, 8, 8>;
_34 = BIT_FIELD_REF <src_2, 8, 16>;
_35 = BIT_FIELD_REF <src_2, 8, 24>;
...
_106 = (unsigned char) _455;
_107 = (unsigned char) _456;
_108 = (unsigned char) _457;
_109 = (unsigned char) _458;
_566 = {_109, _108, _107, _106, _105, _104, _103, _102, _101, _100, _99, _98,
_97, _96, _95, _94};
_550 = VIEW_CONVERT_EXPR<__int128 unsigned>(_566);
_89 = (unsigned int) _550;
_90 = BIT_FIELD_REF <_566, 32, 32>;
_91 = BIT_FIELD_REF <_566, 32, 64>;
_92 = BIT_FIELD_REF <_566, 32, 96>;
c ={v} {CLOBBER};
D.98791.lo.lo.val = _89;
D.98791.lo.hi.val = _90;
D.98791.hi.lo.val = _91;
D.98791.hi.hi.val = _92;
_538 = MEM <__int128 unsigned> [(char * {ref-all})&D.98791];
so we're not able to "combine" through all sorts of reshuffling here
(FRE would be able to at least produce some vector CTOR for the final
one but it currently resists because of cost reasons in general).
This might be all because of stupid intrinsic use or because our intrinsic
[inline] expansion is stupid or ...
"extracting" the actual loops (inlined and all) in intrinsic form as a C
testcase would be really really nice.
>From gcc-bugs-return-661200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:49:32 2019
Return-Path: <gcc-bugs-return-661200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100452 invoked by alias); 25 Nov 2019 10:49:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100367 invoked by uid 55); 25 Nov 2019 10:49:27 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92362] [9/10 regression] double elaboration of expression in Address aspect
Date: Mon, 25 Nov 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92362-4-P5nz76bx5U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92362-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02994.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92362
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Mon Nov 25 10:48:55 2019
New Revision: 278675
URL: https://gcc.gnu.org/viewcvs?rev=278675&root=gcc&view=rev
Log:
PR ada/92362
* gcc-interface/trans.c (gnat_to_gnu) <N_Attribute_Definition_Clause>:
Use a temporary instead of clobbering the result with a freeze node.
Added:
trunk/gcc/testsuite/gnat.dg/addr14.adb
Modified:
trunk/gcc/ada/ChangeLog
trunk/gcc/ada/gcc-interface/trans.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:53:08 2019
Return-Path: <gcc-bugs-return-661201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103496 invoked by alias); 25 Nov 2019 10:53: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 103453 invoked by uid 55); 25 Nov 2019 10:53:04 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92362] [9/10 regression] double elaboration of expression in Address aspect
Date: Mon, 25 Nov 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92362-4-5vRotVLHq9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92362-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02995.txt.bz2
Content-length: 753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92362
--- Comment #4 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Mon Nov 25 10:52:33 2019
New Revision: 278676
URL: https://gcc.gnu.org/viewcvs?rev=278676&root=gcc&view=rev
Log:
PR ada/92362
* gcc-interface/trans.c (gnat_to_gnu) <N_Attribute_Definition_Clause>:
Use a temporary instead of clobbering the result with a freeze node.
Added:
branches/gcc-9-branch/gcc/testsuite/gnat.dg/addr14.adb
- copied unchanged from r278675, trunk/gcc/testsuite/gnat.dg/addr14.adb
Modified:
branches/gcc-9-branch/gcc/ada/ChangeLog
branches/gcc-9-branch/gcc/ada/gcc-interface/trans.c
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:54:40 2019
Return-Path: <gcc-bugs-return-661202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106312 invoked by alias); 25 Nov 2019 10:54: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 106249 invoked by uid 48); 25 Nov 2019 10:54:35 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/92362] [9/10 regression] double elaboration of expression in Address aspect
Date: Mon, 25 Nov 2019 10:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ebotcazou at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-92362-4-AQzA84Kv5C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92362-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92362-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02996.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92362
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Thanks for reporting the problem.
>From gcc-bugs-return-661203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 10:59:55 2019
Return-Path: <gcc-bugs-return-661203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112374 invoked by alias); 25 Nov 2019 10:59: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 112277 invoked by uid 48); 25 Nov 2019 10:59:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Mon, 25 Nov 2019 10:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92645-4-kidilSF6hv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02997.txt.bz2
Content-length: 1868
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-25
Ever confirmed|0 |1
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Probably skvx::cast<uint16_t> is the most intrusive one here ending up with
_37 = MEM[(const struct Vec &)&D.98687 + 15].val;
x_38 = (short unsigned int) _37;
_39 = MEM[(const struct Vec &)&D.98687 + 14].val;
x_40 = (short unsigned int) _39;
_41 = MEM[(const struct Vec &)&D.98687 + 13].val;
x_42 = (short unsigned int) _41;
...
c.hi.lo.hi.hi.val = x_46;
c.hi.hi.lo.lo.val = x_44;
c.hi.hi.lo.hi.val = x_42;
c.hi.hi.hi.lo.val = x_40;
c.hi.hi.hi.hi.val = x_38;
_73 = MEM <vector(16) short unsigned int> [(char * {ref-all})&c];
and expecting some kind of upack() to be used. It's template magic though.
But yes, we're missing "patterns" to detect VEC_* tree codes like
VEC_UPACK_{HI,LO}_EXPR from straight-line code and basic-block vectorization
isn't tuned for multiple sizes / "unpacking reductions" and thus does't
work here either, more specifically it first fails at the appearant mismatch
here:
_32 = (unsigned char) src_2;
_33 = BIT_FIELD_REF <src_2, 8, 8>;
(BIT_FIELD_REF vs. cast). But then it would fail at the common source
of the op:
src_2 = MEM[(struct Vec *)&D.151762];
because that's not a grouped store (and it has a vector type, something
BB vectorization doesn't like too much either).
It does vectorize some stmts, but it only goes up to blind vector
construction for the uniform vector cases (at least that).
>From gcc-bugs-return-661204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:06:12 2019
Return-Path: <gcc-bugs-return-661204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117773 invoked by alias); 25 Nov 2019 11:06: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 117688 invoked by uid 48); 25 Nov 2019 11:06:04 -0000
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92637] runtime issue with -ftree-coalesce-vars
Date: Mon, 25 Nov 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dongjianqiang2 at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92637-4-Z1yoO2Mg8W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92637-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92637-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02998.txt.bz2
Content-length: 739
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92637
--- Comment #3 from John Dong <dongjianqiang2 at huawei dot com> ---
(In reply to Andrew Pinski from comment #1)
> > 214: aa0a03e0 mov x0, x10 // HERE x10 is overwriten by glibc
>
>
> Hmm, GCC knows that find_next_zero_bit will not clobber x10 so it uses
> across the call of that. This is due to -fipa-ra .
>
> glibc should not be involved in the call to find_next_zero_bit either.
>
> If the ld.so is clobbering registers, then the bug is there I think.
>
> Also I doubt -ftree-coalesce-vars is the issue but rather exposing the issue
> with -fipa-ra.
>
> Does using -fno-ipa-ra fix the issue?
yes, using -fno-ipa-ra fix the issue.
>From gcc-bugs-return-661205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:08:55 2019
Return-Path: <gcc-bugs-return-661205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119687 invoked by alias); 25 Nov 2019 11:08: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 119635 invoked by uid 48); 25 Nov 2019 11:08:50 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Mon, 25 Nov 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92645-4-GAFhDNUTdH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg02999.txt.bz2
Content-length: 754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Kind-of a testcase for SSE2, but this has a matching BIT_FIELD_REF at least,
but still "fails" at the vector source. Skia seems to pun to __int128
before doing the extracts somehow (maybe that's our intrinsics, who knows).
typedef unsigned short v8hi __attribute__((vector_size(16)));
typedef unsigned int v4si __attribute__((vector_size(16)));
void foo (v4si *dst, v8hi src)
{
unsigned int tem[8];
tem[0] = src[0];
tem[1] = src[1];
tem[2] = src[2];
tem[3] = src[3];
tem[4] = src[4];
tem[5] = src[5];
tem[6] = src[6];
tem[7] = src[7];
dst[0] = *(v4si *)tem;
dst[1] = *(v4si *)&tem[4];
}
>From gcc-bugs-return-661206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:12:23 2019
Return-Path: <gcc-bugs-return-661206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121940 invoked by alias); 25 Nov 2019 11:12: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 121896 invoked by uid 48); 25 Nov 2019 11:12:19 -0000
From: "samyavrillon at netcourrier dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92646] Compilation fails on armv7l with sys/cdefs.h: No such file or directory
Date: Mon, 25 Nov 2019 11:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: samyavrillon at netcourrier 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-92646-4-p1ft9u1Fws@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92646-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03000.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92646
--- Comment #4 from Mysaa <samyavrillon at netcourrier dot com> ---
There is two of them :
bernard@pipi:~$ locate cdefs.h
/home/bernard/building/gcc-9.2.0/fixincludes/tests/base/sys/cdefs.h
/usr/include/arm-linux-gnueabihf/sys/cdefs.h
bernard@pipi:~$
>From gcc-bugs-return-661207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:18:14 2019
Return-Path: <gcc-bugs-return-661207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127839 invoked by alias); 25 Nov 2019 11:18:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127787 invoked by uid 48); 25 Nov 2019 11:18:10 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92655] Suboptimal vectorization of variable shift
Date: Mon, 25 Nov 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92655-4-piGrutfeTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03001.txt.bz2
Content-length: 331
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92655
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Maybe we could check in vect_determine_min_output_precision_1
whether the result is used as a shift amount, and if so do:
precision = MAX (precision, use_stmt_info->min_output_precision);
>From gcc-bugs-return-661208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:18:33 2019
Return-Path: <gcc-bugs-return-661208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128537 invoked by alias); 25 Nov 2019 11:18: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 128505 invoked by uid 48); 25 Nov 2019 11:18:28 -0000
From: "dongjianqiang2 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92637] runtime issue with -ftree-coalesce-vars
Date: Mon, 25 Nov 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: rtl-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dongjianqiang2 at huawei dot com
X-Bugzilla-Status: 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-92637-4-AWyMegqJAE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92637-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92637-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03002.txt.bz2
Content-length: 1049
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92637
John Dong <dongjianqiang2 at huawei dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from John Dong <dongjianqiang2 at huawei dot com> ---
(In reply to Wilco from comment #2)
> (In reply to John Dong from comment #0)
> > Created attachment 47338 [details]
> > testsuite
> >
> > hi, I compiled the attached with aarch64-linux-gnu-gcc -c -O2
> > -march=armv8.1-a testsuite.c -o testsuite.o, it had runtime error, and I
> > found x10 was overwriten ar row 214.
>
> This example doesn't show a problem. Do you have an example that can be run
> and gives the runtime error?
after checking the log, there is another option -mcmodel=large, and this .o
file finally linked to a dynamic library. it is supposed to use -fPIC other
than -mcmodel=large.
>From gcc-bugs-return-661209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:35:33 2019
Return-Path: <gcc-bugs-return-661209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19727 invoked by alias); 25 Nov 2019 11:35:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19681 invoked by uid 48); 25 Nov 2019 11:35:29 -0000
From: "bina2374 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92656] New: The zero_extend insn can't be eliminated in the combine pass
Date: Mon, 25 Nov 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bina2374 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-92656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03003.txt.bz2
Content-length: 3613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92656
Bug ID: 92656
Summary: The zero_extend insn can't be eliminated in the
combine pass
Product: gcc
Version: 9.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bina2374 at gmail dot com
Target Milestone: ---
Target: RISC-V
I compiled the C function with "-march=rv32imafc -mabi=ilp32f
-mtune=sifive-7-series -O2 -funroll-loops", and there are more slli/ srli
instructions than GCC 8.3.
==========
C Source
==========
unsigned short foo(unsigned short val, unsigned short result) {
unsigned char i = 0;
unsigned char data = (unsigned char)(val >> 8);
for (i = 0; i < 3; i++) {
data >>= 1;
if (data & 1)
result ^= 0x4002;
result >>= 1;
}
return result;
}
==========
Assembly
GCC 9.2
=========
foo:
li a5,16384
srli a4,a0,9
addi t0,a5,2
andi t1,a4,1
xor a3,a1,t0
srli a2,a0,10
bne t1,zero,1f; mv a3,a1; 1: # movcc
srli t2,a3,1
andi a6,a2,1
xor a1,t2,t0
srli a0,a0,11
slli a7,a1,16 ###
andi t5,a0,1
srli t3,a7,16 ###
bne a6,zero,1f; mv t3,t2; 1: # movcc
srli t4,t3,1
slli t6,t4,16 ###
srli a5,t6,16 ###
xor t0,a5,t03
slli a4,t0,16 ###
srli t1,a4,16 ###
bne t5,zero,1f; mv t1,a5; 1: # movcc
srli a0,t1,1
ret
==========
Assembly
GCC 8.3
==========
foo:
srli a0,a0,8
li a5,16384
addi t0,a5,2
srli a2,a0,1
xor a3,a1,t0
andi t1,a2,1
bne t1,zero,1f; mv a3,a1; 1: # movcc
srli a4,a0,2
srli t2,a3,1
andi a1,a4,1
xor a6,t2,t0
bne a1,zero,1f; mv a6,t2; 1: # movcc
srli a7,a0,3
srli t3,a6,1
andi t4,a7,1
xor t5,t3,t0
bne t4,zero,1f; mv t5,t3; 1: # movcc
srli a0,t5,1
ret
When combiner try to combine zero_extend insn and another insn, the subst
pattern can not simplify according rule below because the last condition
(nonzero_bits) can not be met.
In simplify-rtx.c:
/* (zero_extend:M (subreg:N <X:O>)) is <X:O> (for M == O) or
(zero_extend:M <X:O>), if X doesn't have any non-zero bits outside
of mode N. E.g.
(zero_extend:SI (subreg:QI (and:SI (reg:SI) (const_int 63)) 0)) is
(and:SI (reg:SI) (const_int 63)). */
if (partial_subreg_p (op)
&& is_a <scalar_int_mode> (mode, &int_mode)
&& is_a <scalar_int_mode> (GET_MODE (SUBREG_REG (op)), &op0_mode)
&& GET_MODE_PRECISION (op0_mode) <= HOST_BITS_PER_WIDE_INT
&& GET_MODE_PRECISION (int_mode) >= GET_MODE_PRECISION (op0_mode)
&& subreg_lowpart_p (op)
&& (nonzero_bits (SUBREG_REG (op), op0_mode)
& ~GET_MODE_MASK (GET_MODE (op))) == 0)
{
if (GET_MODE_PRECISION (int_mode) == GET_MODE_PRECISION (op0_mode))
return SUBREG_REG (op);
return simplify_gen_unary (ZERO_EXTEND, int_mode, SUBREG_REG (op),
op0_mode);
}
By the way, I also noticed this issue could be caused by 2-to-2 combination
(https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=263067).
>From gcc-bugs-return-661210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:41:00 2019
Return-Path: <gcc-bugs-return-661210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25971 invoked by alias); 25 Nov 2019 11:41:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25944 invoked by uid 48); 25 Nov 2019 11:40:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92649] dead store elimination
Date: Mon, 25 Nov 2019 11:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-92649-4-ydpo44c6CJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03004.txt.bz2
Content-length: 731
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92649
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-25
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. Note this would require DSE to adjust the iteration domain.
Peeling one iteratiou would "solve" that.
The testcase is also stupid, so what's the original motivating testcase?
>From gcc-bugs-return-661211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:47:31 2019
Return-Path: <gcc-bugs-return-661211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30482 invoked by alias); 25 Nov 2019 11:47: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 30424 invoked by uid 48); 25 Nov 2019 11:47:26 -0000
From: "franz.flasch at gmx dot at" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92484] In tree build of ISL 0.22 fails: requires C++11
Date: Mon, 25 Nov 2019 11:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: franz.flasch at gmx dot at
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92484-4-ScQ4PtaYxH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92484-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92484-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03005.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92484
--- Comment #5 from franz <franz.flasch at gmx dot at> ---
OK, I've now digged a little further in to this issue.
According to the GCC docs for a native build a 3-stage-build is performed
automatically. So with "--disable-bootstrap" the build should behave the same
as the crosscompile build. I've tested it and isl builds fine with this
setting.
I've checked config.log from isl and yes, c++11 flags are not added in this
case. However I actually don't know why this even has any influence on that.
It seems that in the newest isl version they now use the M4 macro
"AX_CXX_COMPILE_STDCXX_11" for the whole build. In the previous versions it was
only used for "interface/isl_test_cpp", that's the reason why this problem
actually came up.
>From gcc-bugs-return-661212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 11:57:30 2019
Return-Path: <gcc-bugs-return-661212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38284 invoked by alias); 25 Nov 2019 11: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 38258 invoked by uid 48); 25 Nov 2019 11:57:26 -0000
From: "jiangning.liu at amperecomputing dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92649] dead store elimination
Date: Mon, 25 Nov 2019 11:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jiangning.liu at amperecomputing 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-92649-4-7mGeZJO9rT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03006.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92649
--- Comment #3 from Jiangning Liu <jiangning.liu at amperecomputing dot com> ---
It is a stupid test, but it is simplified from a real application.
To solve even more complicated scenario, this simple case needs to be addressed
first.
If we change the case to be as below,
int f(void)
{
int i, a[1024], s=0;
for (i=0; i<1024; i++)
a[i] = 5;
for (i=0; i<37; i++)
s += a[i];
return s;
}
the loop peeling will not work, but compiler should still know the store to
elements with index >= 37 can all be eliminated. Can any framework in GCC solve
this problem?
>From gcc-bugs-return-661213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:14:06 2019
Return-Path: <gcc-bugs-return-661213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54548 invoked by alias); 25 Nov 2019 12:14: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 54478 invoked by uid 48); 25 Nov 2019 12:14:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92123] [F2018/array-descriptor] Scalar allocatable/pointer with array descriptor (via bind(C)): ICE with select rank or error scalar variable with POINTER or ALLOCATABLE in procedure with BIND(C) is not yet supported
Date: Mon, 25 Nov 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: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92123-4-UqnRChI9AG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92123-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92123-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03007.txt.bz2
Content-length: 3212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, I believe we don't need TREE_STATIC. For DECL_CONTEXT, isn't the context
set already by pushdecl that gfc_create_var calls?
The reason why the *... = 42; store is removed is I believe invalid fn spec:
gfor_fndecl_cfi_to_gfc = gfc_build_library_function_decl_with_spec (
get_identifier (PREFIX("cfi_desc_to_gfc_desc")), ".ww",
void_type_node, 2, pvoid_type_node, ppvoid_type_node);
gfor_fndecl_gfc_to_cfi = gfc_build_library_function_decl_with_spec (
get_identifier (PREFIX("gfc_desc_to_cfi_desc")), ".wR",
void_type_node, 2, ppvoid_type_node, pvoid_type_node);
The first one looks weird, reading libgfortran sources, it doesn't look like
the second argument is ever stored into by the function, so shouldn't it be
".wr" instead? And the ".wR" seems to be the reason why the testcase is
miscompiled with the #c10 patch minus TREE_STATIC hunk. R means that the
argument is not written into (correct), that it does not escape (I'd say
incorrect) and that it is only accessed directly, not indirectly.
With incremental:
--- gcc/fortran/trans-decl.c.jj 2019-11-11 21:04:05.217259240 +0100
+++ gcc/fortran/trans-decl.c 2019-11-25 12:54:31.577424800 +0100
@@ -3739,11 +3742,11 @@ gfc_build_builtin_function_decls (void)
void_type_node, 2, pvoid_type_node, pvoid_type_node);
gfor_fndecl_cfi_to_gfc = gfc_build_library_function_decl_with_spec (
- get_identifier (PREFIX("cfi_desc_to_gfc_desc")), ".ww",
+ get_identifier (PREFIX("cfi_desc_to_gfc_desc")), ".wr",
void_type_node, 2, pvoid_type_node, ppvoid_type_node);
gfor_fndecl_gfc_to_cfi = gfc_build_library_function_decl_with_spec (
- get_identifier (PREFIX("gfc_desc_to_cfi_desc")), ".wR",
+ get_identifier (PREFIX("gfc_desc_to_cfi_desc")), ".wr",
void_type_node, 2, ppvoid_type_node, pvoid_type_node);
gfor_fndecl_associated = gfc_build_library_function_decl_with_spec (
it seems to work. That r in there pretends it reads also e.g.
*GFC_DESCRIPTOR_DATA (s) and thus keeps the *... = 42; store. Though, in
reality, for both functions what the second argument points to (the data
pointed by the descriptor) escapes, it doesn't escape to some global memory,
but to the pointer in the structure pointed by the first argument, in the
second call e.g.
void
gfc_desc_to_cfi_desc (CFI_cdesc_t **d_ptr, const gfc_array_void *s)
{
CFI_cdesc_t *d;
if (*d_ptr == NULL)
d = malloc (...);
else
d = *d_ptr;
d->base_addr = s->base_addr;
...
if (*d_ptr == NULL)
*d_ptr = d;
}
Richard, is ".wr" ok for that, even when it is lying, or should it be
".w." ? I think there is no letter for doesn't store anything to the memory
directly and doesn't escape the address directly, but does escape the content
and thus indirect addresses.
>From gcc-bugs-return-661214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:20:37 2019
Return-Path: <gcc-bugs-return-661214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62462 invoked by alias); 25 Nov 2019 12:20:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62408 invoked by uid 48); 25 Nov 2019 12:20:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92654] internal compiler error: in lookup_template_class_1
Date: Mon, 25 Nov 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-92654-4-F3QuWqROEs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03008.txt.bz2
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92654
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-25
CC| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, apparently it's an invalid code, right?
>From gcc-bugs-return-661215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:23:28 2019
Return-Path: <gcc-bugs-return-661215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68290 invoked by alias); 25 Nov 2019 12:23:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67877 invoked by uid 48); 25 Nov 2019 12:23:22 -0000
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92654] internal compiler error: in lookup_template_class_1
Date: Mon, 25 Nov 2019 12:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fiesh at zefix dot tv
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92654-4-F64AqY1wTe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03009.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92654
--- Comment #2 from fiesh at zefix dot tv ---
It's been made invalid by creduce, but the original code was valid.
If necessary, we can try to produce valid code that leads to the same issue.
But I'd only do so if necessary since it's somewhat cumbersome as the
pre-compiled source doesn't work on clang due to the __integer_pack built-in.
>From gcc-bugs-return-661216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:24:47 2019
Return-Path: <gcc-bugs-return-661216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69848 invoked by alias); 25 Nov 2019 12:24: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 69819 invoked by uid 48); 25 Nov 2019 12:24:43 -0000
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92654] internal compiler error: in lookup_template_class_1
Date: Mon, 25 Nov 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fiesh at zefix dot tv
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92654-4-sp1JXpZuhM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03010.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92654
--- Comment #3 from fiesh at zefix dot tv ---
(Or is there some other trick to make it valid apart from extending the
interestingness test of creduce to include a clang compilation step?)
>From gcc-bugs-return-661217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:26:13 2019
Return-Path: <gcc-bugs-return-661217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71268 invoked by alias); 25 Nov 2019 12:26:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71221 invoked by uid 48); 25 Nov 2019 12:26:09 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92123] [F2018/array-descriptor] Scalar allocatable/pointer with array descriptor (via bind(C)): ICE with select rank or error scalar variable with POINTER or ALLOCATABLE in procedure with BIND(C) is not yet supported
Date: Mon, 25 Nov 2019 12:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92123-4-ZoXDACOUc4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92123-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92123-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03011.txt.bz2
Content-length: 795
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well, lying means that for non-escaped desctiptors A and B doing
A.data = malloc();
gfc_desc_to_cfi_desc (&B, &A)
B.data and A.data are not considered aliasing.
So I'd recommend to not lie here. Yes, there's a letter variant missing
for 'r' plus the direct object not escaping. I can see how that might
be useful indeed (but with points-to constructing a testcase where this
makes a difference won't be easy).
So I'd recommend ".w." for correctness, maybe with a comment about what
we can guarantee (we also have no "letter" to say indirect pointed-to
objects transfer from one argument to another, likely usable for
memcpy-like functions as well for example)
>From gcc-bugs-return-661218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:27:11 2019
Return-Path: <gcc-bugs-return-661218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73365 invoked by alias); 25 Nov 2019 12:27:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73334 invoked by uid 48); 25 Nov 2019 12:27:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92654] internal compiler error: in lookup_template_class_1
Date: Mon, 25 Nov 2019 12:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92654-4-k0Lgi0yq6X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03012.txt.bz2
Content-length: 562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92654
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to fiesh from comment #2)
> It's been made invalid by creduce, but the original code was valid.
>
> If necessary, we can try to produce valid code that leads to the same issue.
> But I'd only do so if necessary since it's somewhat cumbersome as the
> pre-compiled source doesn't work on clang due to the __integer_pack built-in.
Yes, the original test-case would be appreciated. I can make the reduction if
you want..
>From gcc-bugs-return-661219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:31:58 2019
Return-Path: <gcc-bugs-return-661219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78438 invoked by alias); 25 Nov 2019 12:31: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 78328 invoked by uid 55); 25 Nov 2019 12:31:49 -0000
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91851] [m68k] Convert the backend to MODE_CC so it can be kept in future releases
Date: Mon, 25 Nov 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernds at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bernds at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91851-4-Pd6WnO5ijJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03013.txt.bz2
Content-length: 9449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91851
--- Comment #8 from Bernd Schmidt <bernds at gcc dot gnu.org> ---
Author: bernds
Date: Mon Nov 25 12:31:16 2019
New Revision: 278681
URL: https://gcc.gnu.org/viewcvs?rev=278681&root=gcc&view=rev
Log:
Convert m68k to not use cc0
* config/m68k/m68k.c (output_move_himode, output_move_qimode):
Replace code for non-CONST_INT constants with gcc_unreachable.
* config/m68k/m68k.md (cbranchdi): Don't generate individual
compare and test.
(CMPMODE): New mode_iterator.
(cbranchsi4, cbranchqi4, cbranchhi4): Replace expanders with
cbranch<mode>4.
(cstoresi4, cstoreqi4, cstorehi4): Replace expanders with
cstore<mode>4.
(cmp<mode>_68881): Remove 'F' constraint from first comparison
operand.
(bit test insns patterns): Use nonimmediate_operand, not
register_operand, for source operands that allow memory in
their constraints.
(divmodsi4, udivmodsi4, divmodhi4 and related unnamed patterns):
Use register_operand, not nonimmediate_operand, for the
destinations.
(DBCC): New mode_iterator.
(dbcc peepholes): Use it to reduce duplication.
(trap): Use const_true_rtx, not const1_rtx.
* config/m68k/predicates.md (m68k_comparison_operand): Renamed
from m68k_subword_comparison_operand and changed to handle
SImode.
PR target/91851
* config/m68k/m68k-protos.h (output-dbcc_and_branch): Adjust
declaration.
(m68k_init_cc): New declaration.
(m68k_output_compare_di, m68k_output_compare_si)
(m68k_output_compare_hi, m68k_output_compare_qi)
(m68k_output_compare_fp, m68k_output_btst, m68k_output_bftst)
(m68k_find_flags_value, m68k_output_scc, m68k_output_scc_float)
(m68k_output_branch_integer, m68k_output_branch_integer_rev.
m68k_output_branch_float, m68k_output_branch_float_rev):
Likewise.
(valid_dbcc_comparison_p_2, flags_in_68881)
(output_btst): Remove declaration.
* config/m68k/m68k.c (INCLDUE_STRING): Define.
(TARGET_ASM_FINAL_POSTSCAN_INSN): Define.
(valid_dbcc_comparison_p_2, flags_in_68881): Delete functions.
(flags_compare_op0, flags_compare_op1, flags_operand1,
flags_operand2, flags_valid): New static variables.
(m68k_find_flags_value, m68k_init_cc): New functions.
(handle_flags_for_move, m68k_asm_final_postscan_insn,
remember_compare_flags): New static functions.
(output_dbcc_and_branch): New argument CODE. Use it, and add
PLUS and MINUS to the possible codes. All callers changed.
(m68k_output_btst): Renamed from output_btst. Remove OPERANDS
and INSN arguments, add CODE arg. Return the comparison code
to use. All callers changed. Use CODE instead of
next_insn_tests_no_inequality, and replace cc_status management
with changing the return code.
(m68k_rtx_costs): Instead of testing for COMPARE, test for
RTX_COMPARE or RTX_COMM_COMPARE.
(output_move_simode, output_move_qimode): Call
handle_flags_for_move.
(notice_update_cc): Delete function.
(m68k_output_bftst, m68k_output_compare_di, m68k_output_compare_si,
m68k_output_compare_hi, m68k_output_compare_qi,
m68k_output_compare_fp, m68k_output_branch_integer,
m68k_output_branch_integer_rev, m68k_output_scc,
m68k_output_branch_float, m68k_output_branch_float_rev,
m68k_output_scc_float): New functions.
(output_andsi3, output_iorsi3, output_xorsi3): Call CC_STATUS_INIT
once at the start, and set flags_valid and flags_operand1 if the
flags are usable.
* config/m68k/m68k.h (CC_IN_68881, NOTICE_UPDATE_CC,
CC_OVERFLOW_UNUSABLE, CC_NO_CARRY, OUTPUT_JUMP): Remove
definitions.
(CC_STATUS_INIT): Define.
* config/m68k/m68k.md (flags_valid): New define_attr.
(tstdi, tstsi_internal_68020_cf, tstsi_internal, tsthi_internal,
tstqi_internal, tst<mode>_68881, tst<mode>_cf, cmpdi_internal,
cmpdi, unnamed cmpsi/cmphi/cmpqi patterns, cmpsi_cf,
cmp<mode>_68881, cmp<mode>_cf, unnamed btst patterns,
tst_bftst_reg, tst_bftst_reg, unnamed scc patterns, scc,
sls, sordered_1, sunordered_1, suneq_1, sunge_1, sungt_1,
sunle_1, sunlt_1, sltgt_1, fsogt_1, fsoge_1, fsolt_1, fsole_1,
bge0_di, blt0_di, beq, bne, bgt, bgtu, blt, bltu, bge, bgeu,
ble, bleu, bordered, bunordered, buneq, bunge, bungt, bunle,
bunlt, bltgt, beq_rev, bne_rev, bgt_rev, bgtu_rev,
blt_rev, bltu_rev, bge_rev, bgeu_rev, ble_rev, bleu_rev,
bordered_rev, bunordered_rev, buneq_rev, bunge_rv, bungt_rev,
bunle_rev, bunlt_rev, bltgt_rev, ctrapdi4, ctrapsi4, ctraphi4,
ctrapqi4, conditional_trap): Delete patterns.
(cbranchdi4_insn): New pattern.
(cbranchdi4): Don't generate cc0 patterns. When testing LT or GE,
test high part only. When testing EQ or NE, generate beq0_di
and bne0_di patterns directly.
(cstoredi4): When testing LT or GE, test high part only.
(both sets of cbranch<mode>4, cstore<mode>4): Don't generate cc0
patterns.
(scc0_constraints, cmp1_constraints, cmp2_constraints,
scc0_cf_constraints, cmp1_cf_constraints, cmp2_cf_constraints,
cmp2_cf_predicate): New define_mode_attrs.
(cbranch<mode>4_insn, cbranch<mode>4_insn_rev,
cbranch<mode>4_insn_cf, cbranch<mode>4_insn_cf_rev,
cstore<mode>4_insn, cstore<mode>4_insn_cf for integer modes)
New patterns.
(cbranch<mode>4_insn_68881, cbranch<mode>4_insn_rev_68881):
(cbranch<mode>4_insn_cf, cbranch<mode>4_insn_rev_cf,
cstore<mode>4_insn_68881, cstore<mode>4_insn_cf for FP):
New patterns.
(cbranchsi4_btst_mem_insn, cbranchsi4_btst_reg_insn,
cbranchsi4_btst_mem_insn_1, cbranchsi4_btst_reg_insn_1):
Likewise.
(BTST): New define_mode_iterator.
(btst_predicate, btst_constraint, btst_range): New
define_mode_attrs.
(cbranch_bftst<mode>_insn, cstore_bftst<mode>_insn): New
patterns.
(movsi_m68k_movsi_m68k2, movsi_cf, unnamed movstrict patterns,
unnamed movhi and movqi patterns, unnamed movsf, movdf and movxf
patterns): Set attr "flags_valid".
(truncsiqi2, trunchiqi2, truncsihi2): Remove manual CC_STATUS
management. Set attr "flags_valid".
(extendsidi2, extendplussidi, unnamed float_extendsfdf pattern,
extendsfdf2_cf, fix_truncdfsi2, fix_truncdfhi2, fix_truncdfqi2,
addi_sexthishl32, adddi_dilshr32, adddi_dilshr32_cf,
addi_dishl32, subdi_sexthishl32, subdi_dishl32, subdi3): Remove
manual CC_STATUS management.
(addsi3_internal, addhi3, addqi3, subsi3, subhi3, subqi3,
unnamed strict_lowpart subhi and subqi patterns): Set attr
"flags_valid".
(unnamed strict_lowpart addhi3 and addqi3 patterns): Likewise.
Remove code to operate on address regs and assert the case
does not occur.
(unnamed mulsidi patterns, divmodhi4, udivmodhi4): Remove
manual CC_STATUS_INIT.
(andsi3_internal, andhi3, andqi3, iorsi3_internal, iorhi3, iorqi3,
xorsi3_internal, xorhi3, xorqi3, negsi2_internal,
negsi2_5200, neghi2, negqi2, one_cmplsi2_internal, one_cmplhi2,
one_cmplqi2, unnamed strict_lowpart patterns
for andhi, andqi, iorhi, iorqi, xorhi, xorqi, neghi, negqi,
one_cmplhi and one_cmplqi): Set attr "flags_valid".
(iorsi_zext_ashl16, iorsi_zext): Remove manual CC_STATUS_INIT.
(ashldi_sexthi, ashlsi_16, ashlsi_17_24): Remove manual
CC_STATUS_INIT.
(ashlsi3, ashlhi3, ashlqi3, ashrsi3, ashrhi3, ashrqi3, lshrsi3,
lshrhi3, shrqi3, rotlsi3, rotlhi3, rotlhi3_lowpart, rotlqi3,
rotlqi3_lowpart, rotrsi3, rotrhi3, rotrhi_lowpart, rotrqi3,
unnamed strict_low_part patterns for HI and
QI versions): Set attr "flags_valid".
(bsetmemqi, bsetmemqi_ext, bsetdreg, bchgdreg, bclrdreg,
bclrmemqi, extzv_8_16_reg, extzv_bfextu_mem, insv_bfchg_mem,
insv_bfclr_mem, insv_bfset_mem, extv_bfextu_reg,
insv_bfclr_reg, insv_bfset_reg, dbne_hi, dbne_si, dbge_hi,
dbge_si, extendsfxf2, extenddfxf2, ): Remove manual cc_status
management.
(various unnamed peepholes): Adjust compare/branch sequences
for new cbranch patterns.
(dbcc peepholes): Likewise, and output the comparison here
as well.
* config/m68k/predicates.md (valid_dbcc_comparison_p): Delete.
(fp_src_operand): Allow constant zero.
(address_reg_operand): New predicate.
* rtl.h (inequality_comparisons_p): Remove declaration.
* recog.h (next_insn_tests_no_inequality): Likewise.
* rtlanal.c (inequality_comparisons_p): Delete function.
* recog.c (next_insn_tests_no_inequality): Likewise.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/m68k/m68k-protos.h
trunk/gcc/config/m68k/m68k.c
trunk/gcc/config/m68k/m68k.h
trunk/gcc/config/m68k/m68k.md
trunk/gcc/config/m68k/predicates.md
trunk/gcc/recog.c
trunk/gcc/recog.h
trunk/gcc/rtl.h
trunk/gcc/rtlanal.c
>From gcc-bugs-return-661220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:34:11 2019
Return-Path: <gcc-bugs-return-661220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83185 invoked by alias); 25 Nov 2019 12: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 83102 invoked by uid 48); 25 Nov 2019 12:34:07 -0000
From: "bernds at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/91851] [m68k] Convert the backend to MODE_CC so it can be kept in future releases
Date: Mon, 25 Nov 2019 12:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernds at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: bernds at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-91851-4-XJsb8m5gnk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03014.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91851
Bernd Schmidt <bernds at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Bernd Schmidt <bernds at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-661221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:35:39 2019
Return-Path: <gcc-bugs-return-661221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86110 invoked by alias); 25 Nov 2019 12:35:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86017 invoked by uid 48); 25 Nov 2019 12:35:35 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/48188] ICE: SIGSEGV in remove_unnecessary_regions (ira-build.c:1855) with --param ira-max-loops-num=0 on basic code
Date: Mon, 25 Nov 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: rtl-optimization
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: ice-on-valid-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:
Message-ID: <bug-48188-4-CtzVvOpU8w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48188-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48188-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03015.txt.bz2
Content-length: 160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48188
--- Comment #4 from Zdenek Sojka <zsojka at seznam dot cz> ---
Doesn't seem to crash since at least gcc-7
>From gcc-bugs-return-661222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:36:22 2019
Return-Path: <gcc-bugs-return-661222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87131 invoked by alias); 25 Nov 2019 12: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 87097 invoked by uid 48); 25 Nov 2019 12:36:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92649] dead store elimination
Date: Mon, 25 Nov 2019 12:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92649-4-Va98AWYYoU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92649-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03016.txt.bz2
Content-length: 1438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92649
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jiangning Liu from comment #3)
> It is a stupid test, but it is simplified from a real application.
>
> To solve even more complicated scenario, this simple case needs to be
> addressed first.
>
> If we change the case to be as below,
>
> int f(void)
> {
> int i, a[1024], s=0;
>
> for (i=0; i<1024; i++)
> a[i] = 5;
>
> for (i=0; i<37; i++)
> s += a[i];
> return s;
> }
>
> the loop peeling will not work, but compiler should still know the store to
> elements with index >= 37 can all be eliminated. Can any framework in GCC
> solve this problem?
No, not when faced with loops. If both loops were completely unrolled then
DSE would do this job but as it stands DSE doesn't know how to adjust
a loops iteration space to elide dead stores. In the above case splitting
the first loop into two so that the first iterates [0, 37[ and the second
[37, 1024[ would make the problem easier for DSE. We could then also
fuse the loops, eliding a completely. So I guess loop fusion might be
the actual transform we're looking after (which for enablement needs the
loop splitting).
I suppose the "real" application doesn't iniitalize a[i] to all 5? But
the first loop is actually some kind of initialization?
>From gcc-bugs-return-661223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 12:50:36 2019
Return-Path: <gcc-bugs-return-661223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107274 invoked by alias); 25 Nov 2019 12:50: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 107193 invoked by uid 48); 25 Nov 2019 12:50:32 -0000
From: "steffen.seckler at tum dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/60228] ICE using lambda in #pragma omp declare reduction
Date: Mon, 25 Nov 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code, openmp
X-Bugzilla-Severity: normal
X-Bugzilla-Who: steffen.seckler at tum 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-60228-4-Yjc01e4jxH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60228-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60228-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03017.txt.bz2
Content-length: 460
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60228
steffen.seckler at tum dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |steffen.seckler at tum dot de
--- Comment #4 from steffen.seckler at tum dot de ---
I would also like to see this supported, as the intel compiler is already able
to support this.
>From gcc-bugs-return-661224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:00:39 2019
Return-Path: <gcc-bugs-return-661224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116530 invoked by alias); 25 Nov 2019 13:00:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116424 invoked by uid 48); 25 Nov 2019 13:00:35 -0000
From: "adhemerval.zanella at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92657] New: High stack usage due ftree-ch
Date: Mon, 25 Nov 2019 13:00: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: adhemerval.zanella at linaro dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-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: 2019-11/txt/msg03018.txt.bz2
Content-length: 2084
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92657
Bug ID: 92657
Summary: High stack usage due ftree-ch
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: adhemerval.zanella at linaro dot org
Target Milestone: ---
Created attachment 47351
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47351&action=edit
High stack usage due ftree-ch
The code snippet (gcc_free_ch_stack.c) shows a high stack usage. With GCC
9.2.1 I see the resulting stack usage using -fstack-usage along with -O2:
arm 632
aarch64 448
powerpc 912
powerpc64le 560
s390 600
s390x 632
i386 1376
x86_64 784
The same issue also shows in master branch. It seems that it is due -ftree-ch
pass with feeds -ftree-loop-im, -ftree-pre, -fmove-loop-invariants, and -fgcse.
Andrew Pinski suggested is mostly due lack of a good estimate register pressure
for loop invariant code motion.
Andrew also suggested to use -fno-tree-loop-im -fno-tree-pre -fno-gcse, however
even with this options the resulting stack usage does not get in par with -Os
option (which disables -ftree-ch). On powerpc64le:
$ ./gcc/xgcc -v 2>&1 | grep 'gcc version'
gcc version 10.0.0 20191121 (experimental) (GCC)
$ ./gcc/xgcc -B gcc -O2 stack_usage.c -fstack-usage -c; cat stack_usage.su
stack_usage.c:157:6:mlx5e_grp_sw_update_stats 496 static
$ ./gcc/xgcc -B gcc -O2 stack_usage.c -fstack-usage -c -fno-tree-loop-im
-fno-tree-pre -fno-move-loop-invariants -fno-gcse; cat stack_usage.su
stack_usage.c:157:6:mlx5e_grp_sw_update_stats 176 static$ ./gcc/xgcc -B
gcc -Os stack_usage.c -fstack-usage -c; cat stack_usage.su
$ ./gcc/xgcc -B gcc -Os stack_usage.c -fstack-usage -c; cat stack_usage.su
stack_usage.c:157:6:mlx5e_grp_sw_update_stats 32 static
>From gcc-bugs-return-661225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:04:42 2019
Return-Path: <gcc-bugs-return-661225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120806 invoked by alias); 25 Nov 2019 13:04:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120722 invoked by uid 48); 25 Nov 2019 13:04:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92123] [F2018/array-descriptor] Scalar allocatable/pointer with array descriptor (via bind(C)): ICE with select rank or error scalar variable with POINTER or ALLOCATABLE in procedure with BIND(C) is not yet supported
Date: Mon, 25 Nov 2019 13:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92123-4-Y66ISnHz2s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92123-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92123-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03019.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92123
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I think other fn spec attributes in trans-decl.c should be checked.
E.g. for internal_pack, I see ".r", when the function sometimes returns a
pointer to a field pointed by the first argument. The address of the
descriptor doesn't escape then, but there is indirect escape. What about
internal_unpack?
Both cfi_desc_to_gfc_desc and gfc_desc_to_cfi_desc should be ".w." as Richi
said.
>From gcc-bugs-return-661226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:06:33 2019
Return-Path: <gcc-bugs-return-661226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122659 invoked by alias); 25 Nov 2019 13:06: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 122547 invoked by uid 48); 25 Nov 2019 13:06:29 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92445] gcc bootstrap fails on Darwin 19.0.0 in stage 1
Date: Mon, 25 Nov 2019 13:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-92445-4-PhaDt3eFbj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92445-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92445-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03020.txt.bz2
Content-length: 599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92445
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |egallager at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
Dup of bug 90835, looks like
*** This bug has been marked as a duplicate of bug 90835 ***
>From gcc-bugs-return-661227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:06:34 2019
Return-Path: <gcc-bugs-return-661227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122666 invoked by alias); 25 Nov 2019 13:06: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 122574 invoked by uid 48); 25 Nov 2019 13:06:29 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90835] Incompatibilities with macOS 10.15 headers
Date: Mon, 25 Nov 2019 13:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-90835-4-m7MV59kcR4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03021.txt.bz2
Content-length: 455
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |juergen.reuter at desy dot de
--- Comment #19 from Eric Gallager <egallager at gcc dot gnu.org> ---
*** Bug 92445 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-661228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:23:20 2019
Return-Path: <gcc-bugs-return-661228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19592 invoked by alias); 25 Nov 2019 13:23:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19491 invoked by uid 48); 25 Nov 2019 13:23:15 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90835] Incompatibilities with macOS 10.15 headers
Date: Mon, 25 Nov 2019 13:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90835-4-lLVTlBh9zr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03022.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
--- Comment #20 from Iain Sandoe <iains at gcc dot gnu.org> ---
As of XCode 11.3beta, the contained SDK works OK:
https://gcc.gnu.org/ml/gcc-testresults/2019-11/msg01439.html
We still have the underlying problems - which need to be addressed (so please
don't close this PR yet) - but for now using the latest SDK should work.
>From gcc-bugs-return-661229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:33:57 2019
Return-Path: <gcc-bugs-return-661229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30622 invoked by alias); 25 Nov 2019 13: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 30579 invoked by uid 48); 25 Nov 2019 13:33:51 -0000
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92654] internal compiler error: in lookup_template_class_1
Date: Mon, 25 Nov 2019 13:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fiesh at zefix dot tv
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92654-4-YDdQUUzEAP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92654-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03023.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92654
--- Comment #5 from fiesh at zefix dot tv ---
Thank you for your offer. The original translation unit is a whopping 20MB and
took about 3 days to reduce ;-)
I changed the file and the interestingness test to make sure clang compiles it.
It's running now and I'll post the reduced result once it's done.
>From gcc-bugs-return-661230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:38:37 2019
Return-Path: <gcc-bugs-return-661230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36060 invoked by alias); 25 Nov 2019 13:38: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 36022 invoked by uid 48); 25 Nov 2019 13:38:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] New: x86 lacks vector extend / truncate
Date: Mon, 25 Nov 2019 13:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03024.txt.bz2
Content-length: 1946
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
Bug ID: 92658
Summary: x86 lacks vector extend / truncate
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
After
2019-11-14 Richard Sandiford <richard.sandiford@arm.com>
* tree-cfg.c (verify_gimple_assign_unary): Handle conversions
between vector types.
* tree-vect-stmts.c (vectorizable_conversion): Extend the
non-widening and non-narrowing path to handle standard
conversion codes, if the target supports them.
* expr.c (convert_move): Try using the extend and truncate optabs
for vectors.
* optabs-tree.c (supportable_convert_operation): Likewise.
* config/aarch64/iterators.md (Vnarroqw): New iterator.
* config/aarch64/aarch64-simd.md (<optab><Vnarrowq><mode>2)
(trunc<mode><Vnarrowq>2): New patterns.
it would now be possible to BB vectorize the following but the x86 backend
lacks appropriate patterns for the vector mode variants (here V8HI -> V8QI
narrowing).
typedef unsigned char v16qi __attribute__((vector_size(16)));
typedef unsigned short v8hi __attribute__((vector_size(16)));
void bar (v8hi *dst, v16qi * __restrict src)
{
unsigned short tem[8];
tem[0] = (*src)[0];
tem[1] = (*src)[1];
tem[2] = (*src)[2];
tem[3] = (*src)[3];
tem[4] = (*src)[4];
tem[5] = (*src)[5];
tem[6] = (*src)[6];
tem[7] = (*src)[7];
dst[0] = *(v8hi *)tem;
}
void foo (v8hi *dst, v16qi src)
{
unsigned short tem[8];
tem[0] = src[0];
tem[1] = src[1];
tem[2] = src[2];
tem[3] = src[3];
tem[4] = src[4];
tem[5] = src[5];
tem[6] = src[6];
tem[7] = src[7];
dst[0] = *(v8hi *)tem;
}
>From gcc-bugs-return-661231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:46:20 2019
Return-Path: <gcc-bugs-return-661231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41683 invoked by alias); 25 Nov 2019 13: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 41650 invoked by uid 55); 25 Nov 2019 13:46:14 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91985] Unsupported DFP not diagnosed with constants or built-in functions
Date: Mon, 25 Nov 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-91985-4-zeCMpNGPui@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91985-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03025.txt.bz2
Content-length: 3391
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91985
--- Comment #2 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Mon Nov 25 13:45:42 2019
New Revision: 278684
URL: https://gcc.gnu.org/viewcvs?rev=278684&root=gcc&view=rev
Log:
Prevent all uses of DFP when unsupported (PR c/91985).
Code that directly uses _Decimal* types on architectures not
supporting DFP is properly diagnosed ("error: decimal floating-point
not supported for this target"), via a call to
targetm.decimal_float_supported_p, if the _Decimal32, _Decimal64 or
_Decimal128 keywords are used to access it. Use via mode attributes
is also diagnosed ("unable to emulate 'SD'"); so is use of the
FLOAT_CONST_DECIMAL64 pragma. However, it is possible to access those
types via typeof applied to constants or built-in functions without
such an error. I expect that there are ways to get an ICE from this;
certainly it uses a completely undefined ABI.
This patch arranges for the types not to exist in the compiler at all
when DFP is not supported. As is done with unsupported _FloatN /
_FloatNx types, the global tree nodes are left as NULL_TREE, and the
built-in function machinery is made to use error_mark_node for them in
that case in builtin-types.def, so that the built-in functions are
unavailable. Code handling constants is adjusted to give an error,
and other code that might not work with the global tree nodes being
NULL_TREE is also updated.
Bootstrapped with no regressions for x86_64-pc-linux-gnu. Also tested
with no regressions for cross to aarch64-linux-gnu, as a configuration
without DFP support.
PR c/91985
gcc:
* builtin-types.def (BT_DFLOAT32, BT_DFLOAT64, BT_DFLOAT128)
(BT_DFLOAT32_PTR, BT_DFLOAT64_PTR, BT_DFLOAT128_PTR): Define to
error_mark_node if corresponding global tree node is NULL.
* tree.c (build_common_tree_nodes): Do not initialize
dfloat32_type_node, dfloat64_type_node or dfloat128_type_node if
decimal floating-point not supported.
gcc/c:
* c-decl.c (finish_declspecs): Use int instead of decimal
floating-point types if decimal floating-point not supported.
gcc/c-family:
* c-common.c (c_common_type_for_mode): Handle decimal
floating-point types being NULL_TREE.
* c-format.c (get_format_for_type_1): Handle specified types being
NULL_TREE.
* c-lex.c (interpret_float): Give an error for decimal
floating-point constants when decimal floating-point not
supported.
gcc/lto:
* lto-lang.c (lto_type_for_mode): Handle decimal floating-point
types being NULL_TREE.
gcc/testsuite:
* gcc.dg/c2x-no-dfp-1.c, gcc.dg/gnu2x-builtins-no-dfp-1.c: New
tests.
* gcc.dg/fltconst-pedantic-dfp.c: Expect errors when decimal
floating-point not supported.
Added:
trunk/gcc/testsuite/gcc.dg/c2x-no-dfp-1.c
trunk/gcc/testsuite/gcc.dg/gnu2x-builtins-no-dfp-1.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/builtin-types.def
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-common.c
trunk/gcc/c-family/c-format.c
trunk/gcc/c-family/c-lex.c
trunk/gcc/c/ChangeLog
trunk/gcc/c/c-decl.c
trunk/gcc/lto/ChangeLog
trunk/gcc/lto/lto-lang.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/fltconst-pedantic-dfp.c
trunk/gcc/tree.c
>From gcc-bugs-return-661232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:48:34 2019
Return-Path: <gcc-bugs-return-661232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43974 invoked by alias); 25 Nov 2019 13:48: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 43808 invoked by uid 48); 25 Nov 2019 13:48:25 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/91985] Unsupported DFP not diagnosed with constants or built-in functions
Date: Mon, 25 Nov 2019 13:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-91985-4-j5cbz0jr7j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-91985-4@http.gcc.gnu.org/bugzilla/>
References: <bug-91985-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03026.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91985
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |10.0
--- Comment #3 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Fixed for GCC 10.
>From gcc-bugs-return-661233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:51:19 2019
Return-Path: <gcc-bugs-return-661233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46320 invoked by alias); 25 Nov 2019 13:51:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45837 invoked by uid 48); 25 Nov 2019 13:51:12 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Mon, 25 Nov 2019 13:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-92645-4-BksoJWS7Ba@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03027.txt.bz2
Content-length: 1631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #5)
>
> "extracting" the actual loops (inlined and all) in intrinsic form as a C
> testcase would be really really nice.
Something like the following? Enjoy!
typedef unsigned int u32v4 __attribute__((vector_size(16)));
typedef unsigned short u16v16 __attribute__((vector_size(32)));
typedef unsigned char u8v16 __attribute__((vector_size(16)));
union vec128 {
u8v16 u8;
u32v4 u32;
};
#define memcpy __builtin_memcpy
u16v16 zxt(u8v16 x)
{
return (u16v16) {
x[0], x[1], x[2], x[3], x[4], x[5], x[6], x[7],
x[8], x[9], x[10], x[11], x[12], x[13], x[14], x[15]
};
}
u8v16 narrow(u16v16 x)
{
return (u8v16) {
x[0], x[1], x[2], x[3], x[4], x[5], x[6], x[7],
x[8], x[9], x[10], x[11], x[12], x[13], x[14], x[15]
};
}
void f(char *dst, char *src, unsigned long n, unsigned c)
{
unsigned ia = 255 - (c >> 24);
ia += ia >> 7;
union vec128 c4 = {0}, ia16 = {0};
c4.u32 += c;
ia16.u8 += (unsigned char)ia;
u16v16 c16 = (zxt(c4.u8) << 8) + 128;
for (; n; src += 16, dst += 16, n -= 4) {
union vec128 s;
memcpy(&s, src, sizeof s);
s.u8 = narrow((zxt(s.u8)*zxt(ia16.u8) + c16) >> 8);
memcpy(dst, &s, sizeof s);
}
}
>From gcc-bugs-return-661234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:55:20 2019
Return-Path: <gcc-bugs-return-661234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50384 invoked by alias); 25 Nov 2019 13:55:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50297 invoked by uid 48); 25 Nov 2019 13:55:16 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92642] Enhance shift-count-overflow output
Date: Mon, 25 Nov 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92642-4-zlBFmXpTBL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03028.txt.bz2
Content-length: 540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92642
--- Comment #2 from Jonny Grant <jg at jguk dot org> ---
(In reply to Jonathan Wakely from comment #1)
> (A) seems pointless in this case, it's right there in the caret diagnostic.
>
> The type size_t is irrelevant.
>
> IMO a better testcase would be:
>
> const int n = 41;
> auto x = 1 << n;
Sounds good. That 'n' might be passed in from somewhere, so worth including the
number in the output if it is visible (compiler is aware of the value if it is
const right?)
>From gcc-bugs-return-661235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 13:57:36 2019
Return-Path: <gcc-bugs-return-661235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54101 invoked by alias); 25 Nov 2019 13:57:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54048 invoked by uid 55); 25 Nov 2019 13:57:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92653] [10 Regression] PGO bootstrap is broken with --with-build-config=bootstrap-lto-lean
Date: Mon, 25 Nov 2019 13: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: 10.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92653-4-CD6pEFUUbv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92653-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92653-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03029.txt.bz2
Content-length: 549
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92653
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Mon Nov 25 13:57:00 2019
New Revision: 278686
URL: https://gcc.gnu.org/viewcvs?rev=278686&root=gcc&view=rev
Log:
Comment too strict checking assert.
2019-11-25 Martin Liska <mliska@suse.cz>
PR bootstrap/92653
* ipa-fnsummary.c (ipa_fn_summary::account_size_time): Comment out
too strict checking assert.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-fnsummary.c
>From gcc-bugs-return-661236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:01:14 2019
Return-Path: <gcc-bugs-return-661236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58647 invoked by alias); 25 Nov 2019 14:01: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 58556 invoked by uid 48); 25 Nov 2019 14:01:06 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92659] New: Suggestions for bitshift
Date: Mon, 25 Nov 2019 14:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03030.txt.bz2
Content-length: 922
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92659
Bug ID: 92659
Summary: Suggestions for bitshift
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jg at jguk dot org
Target Milestone: ---
Could GCC suggest for C/C++ the code change?
#include <stddef.h>
size_t i = 1 << 32;
#1 with x86-64 gcc (trunk)
<source>:2:14: warning: left shift count >= width of type
[-Wshift-count-overflow]
2 | size_t i = 1 << 32;
| ~~^~~~~
Compiler returned: 0
It could output:
<source>:2:14: warning: left shift count >= width of type
[-Wshift-count-overflow]
2 | size_t i = 1 << 32;
| ~~^~~~~
| size_t i = 1 << 32;
| ~~^~~~~
| 1UL << 32;
>From gcc-bugs-return-661237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:02:49 2019
Return-Path: <gcc-bugs-return-661237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60971 invoked by alias); 25 Nov 2019 14:02:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 60186 invoked by uid 48); 25 Nov 2019 14:02:41 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92660] New: overflow warning message enhancement
Date: Mon, 25 Nov 2019 14:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92660-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03031.txt.bz2
Content-length: 989
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92660
Bug ID: 92660
Summary: overflow warning message enhancement
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jg at jguk dot org
Target Milestone: ---
Could GCC, for both C and C++ output the bitsize on the overflow warning ?
const int n = 41111111111;
#1 with x86-64 gcc (trunk)
<source>:1:15: warning: overflow in conversion from 'long int' to 'int' changes
value from '41111111111' to '-1838561849' [-Woverflow]
1 | const int n = 41111111111;
| ^~~~~~~~~~~
Suggestion:
<source>:1:15: warning: overflow in conversion from 'long int' (64bit) to 'int'
(32bit) changes value from '41111111111' to '-1838561849' [-Woverflow]
1 | const int n = 41111111111;
| ^~~~~~~~~~~
>From gcc-bugs-return-661238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:03:26 2019
Return-Path: <gcc-bugs-return-661238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63690 invoked by alias); 25 Nov 2019 14:03:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 63636 invoked by uid 48); 25 Nov 2019 14:03:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92659] Suggestions for bitshift
Date: Mon, 25 Nov 2019 14:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_severity
Message-ID: <bug-92659-4-475Lz93Ub9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92659-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92659-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03032.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92659
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Severity|normal |enhancement
>From gcc-bugs-return-661239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:04:57 2019
Return-Path: <gcc-bugs-return-661239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65696 invoked by alias); 25 Nov 2019 14:04:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65658 invoked by uid 48); 25 Nov 2019 14:04:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/92642] Enhance shift-count-overflow output
Date: Mon, 25 Nov 2019 14:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92642-4-50nousyoWW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92642-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03033.txt.bz2
Content-length: 308
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92642
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
No, not necessarily.
extern const int n; // defined in another file
auto i = 1 << n;
void f(const int n)
{
auto i = 1 << n;
}
Not all const variables are compile-time constants.
>From gcc-bugs-return-661240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:07:20 2019
Return-Path: <gcc-bugs-return-661240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68243 invoked by alias); 25 Nov 2019 14:07: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 68216 invoked by uid 48); 25 Nov 2019 14:07:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/92658] x86 lacks vector extend / truncate
Date: Mon, 25 Nov 2019 14:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92658-4-MzJ5MJpBTv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92658-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03034.txt.bz2
Content-length: 599
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92658
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
It looks like there are already some avx512 patterns matching this but they
are not visible to the RTL expanders.
(define_insn "zero_extendv8qiv8hi2"
[(set (match_operand:V8HI 0 "register_operand" "=x,v")
(zero_extend:V8HI (match_operand:V8QI 1 "register_operand" "x,v")))]
"TARGET_SSE2"
"@
punpcklbw\t{%1, %0|%0, %1}
vpunpcklbw\t{%1, %0|%0, %1}"
)
does it for the testcase pasted but truncation and other extends are also
missing, likewise for floats.
>From gcc-bugs-return-661241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:08:09 2019
Return-Path: <gcc-bugs-return-661241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69649 invoked by alias); 25 Nov 2019 14:08:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69600 invoked by uid 48); 25 Nov 2019 14:08:05 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/92657] High stack usage due ftree-ch
Date: Mon, 25 Nov 2019 14:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-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: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92657-4-nHcnIaHju8@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: 2019-11/txt/msg03035.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92657
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Again, this is not due to tree-ch at all. This is due to the code motion
passes move invariant load/stores out of the loop. Tree-ch pass just allows
those passes to work.
All three (gcse, tree pre and tree lim) need to be disabled to see the
difference as all three are able to do the transformation.
>From gcc-bugs-return-661242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:11:29 2019
Return-Path: <gcc-bugs-return-661242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71808 invoked by alias); 25 Nov 2019 14:11: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 71753 invoked by uid 48); 25 Nov 2019 14:11:25 -0000
From: "adhemerval.zanella 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: Mon, 25 Nov 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adhemerval.zanella at linaro 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-92657-4-lLT8ILdjiu@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: 2019-11/txt/msg03036.txt.bz2
Content-length: 790
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92657
--- Comment #2 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Andrew Pinski from comment #1)
> Again, this is not due to tree-ch at all. This is due to the code motion
> passes move invariant load/stores out of the loop. Tree-ch pass just allows
> those passes to work.
>
> All three (gcse, tree pre and tree lim) need to be disabled to see the
> difference as all three are able to do the transformation.
Sorry if I was not clear that tree-ch is not the culprit, but rather that it
enabled further optimizations to increase register pressure. But as I added by
disabling gcse, tree pre, and tree lim does help total stack usage, but it does
not reach on same level as disabling tree-ch.
>From gcc-bugs-return-661243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:26:49 2019
Return-Path: <gcc-bugs-return-661243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90501 invoked by alias); 25 Nov 2019 14:26:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90466 invoked by uid 48); 25 Nov 2019 14:26:45 -0000
From: "adhemerval.zanella 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: Mon, 25 Nov 2019 14: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: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adhemerval.zanella at linaro 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-92657-4-xvmGUxxvqv@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: 2019-11/txt/msg03037.txt.bz2
Content-length: 1120
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92657
--- Comment #3 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Adhemerval Zanella from comment #2)
> (In reply to Andrew Pinski from comment #1)
> > Again, this is not due to tree-ch at all. This is due to the code motion
> > passes move invariant load/stores out of the loop. Tree-ch pass just allows
> > those passes to work.
> >
> > All three (gcse, tree pre and tree lim) need to be disabled to see the
> > difference as all three are able to do the transformation.
>
> Sorry if I was not clear that tree-ch is not the culprit, but rather that it
> enabled further optimizations to increase register pressure. But as I added
> by disabling gcse, tree pre, and tree lim does help total stack usage, but
> it does not reach on same level as disabling tree-ch.
Ok, gcse, tree pre and tree lim are just tree of the flags that are increasing
the stack. Other not enabled by Os but enabled by O2 are increasing stack
usage.
Maybe changing the title to "High stack usage with tree-loop-im, tree-pre, and
gcse"?
>From gcc-bugs-return-661244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:34:21 2019
Return-Path: <gcc-bugs-return-661244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96924 invoked by alias); 25 Nov 2019 14:34: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 96666 invoked by uid 55); 25 Nov 2019 14:34:16 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/92050] internal compiler error: in gfc_conv_procedure_call
Date: Mon, 25 Nov 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.2.1
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: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92050-4-wpg3FSvIGl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92050-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92050-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03038.txt.bz2
Content-length: 823
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92050
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Mon Nov 25 14:33:32 2019
New Revision: 278689
URL: https://gcc.gnu.org/viewcvs?rev=278689&root=gcc&view=rev
Log:
Fortran] PR 92050 - fix ICE with -fcheck=all
Backport from mainline
2019-10-11 Tobias Burnus <tobias@codesourcery.com>
PR fortran/92050
* trans-expr.c (gfc_conv_procedure_call): Handle code generated
by -fcheck=all.
PR fortran/92050
* gfortran.dg/pr92050.f90: New.
Added:
branches/gcc-9-branch/gcc/testsuite/gfortran.dg/pr92050.f90
Modified:
branches/gcc-9-branch/gcc/fortran/ChangeLog
branches/gcc-9-branch/gcc/fortran/trans-expr.c
branches/gcc-9-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-661245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:44:37 2019
Return-Path: <gcc-bugs-return-661245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110594 invoked by alias); 25 Nov 2019 14:44:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110549 invoked by uid 48); 25 Nov 2019 14:44:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/92645] Hand written vector code is 450 times slower when compiled with GCC compared to Clang
Date: Mon, 25 Nov 2019 14:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92645-4-pTmWm9Sopn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92645-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03039.txt.bz2
Content-length: 1479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92645
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Thanks a lot. So besides the following mismatch for SLP
_24 = MEM[base: src_22(D), index: ivtmp.20_267, offset: 0B];
_97 = (unsigned char) _24;
_98 = (short unsigned int) _97;
_99 = BIT_FIELD_REF <_24, 8, 8>;
_100 = (short unsigned int) _99;
_101 = BIT_FIELD_REF <_24, 8, 16>;
...
there's also missing forwprop (CTOR -> vector SSA) for
_62 = BIT_FIELD_REF <_8, 16, 0>;
_64 = BIT_FIELD_REF <_8, 16, 16>;
_66 = BIT_FIELD_REF <_8, 16, 32>;
_68 = BIT_FIELD_REF <_8, 16, 48>;
_70 = BIT_FIELD_REF <_8, 16, 64>;
_72 = BIT_FIELD_REF <_8, 16, 80>;
_74 = BIT_FIELD_REF <_8, 16, 96>;
_76 = BIT_FIELD_REF <_8, 16, 112>;
_78 = BIT_FIELD_REF <_8, 16, 128>;
_80 = BIT_FIELD_REF <_8, 16, 144>;
_82 = BIT_FIELD_REF <_8, 16, 160>;
_84 = BIT_FIELD_REF <_8, 16, 176>;
_86 = BIT_FIELD_REF <_8, 16, 192>;
_88 = BIT_FIELD_REF <_8, 16, 208>;
_90 = BIT_FIELD_REF <_8, 16, 224>;
_92 = BIT_FIELD_REF <_8, 16, 240>;
_136 = {_78, _80, _82, _84, _86, _88, _90, _92};
_270 = {_62, _64, _66, _68, _70, _72, _74, _76};
because we only look for full vector builds/shuffles but those CTORs
extract the low/high part of _8. I'll see to fix that tomorrow.
The conversion vs. BIT_FIELD_REF somehow completely disables the SLP tree
but we could build from scalars, testing patch to fix that.
>From gcc-bugs-return-661247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:48:49 2019
Return-Path: <gcc-bugs-return-661247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117428 invoked by alias); 25 Nov 2019 14: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 117232 invoked by uid 48); 25 Nov 2019 14:48:27 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92661] [10 Regression] AIX bootstrap failure with builtin-types.def change
Date: Mon, 25 Nov 2019 14:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
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 everconfirmed
Message-ID: <bug-92661-4-IgZuuryByz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03041.txt.bz2
Content-length: 476
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92661
David Edelsohn <dje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-11-25
Ever confirmed|0 |1
--- Comment #1 from David Edelsohn <dje at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-661246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:48:00 2019
Return-Path: <gcc-bugs-return-661246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116247 invoked by alias); 25 Nov 2019 14:48:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116089 invoked by uid 48); 25 Nov 2019 14:47:56 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92661] New: [10 Regression] AIX bootstrap failure with builtin-types.def change
Date: Mon, 25 Nov 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: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
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 bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03040.txt.bz2
Content-length: 954
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92661
Bug ID: 92661
Summary: [10 Regression] AIX bootstrap failure with
builtin-types.def change
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: dje at gcc dot gnu.org
CC: bergner at gcc dot gnu.org, segher at gcc dot gnu.org,
wschmidt at gcc dot gnu.org
Target Milestone: ---
Target: powerpc-ibm-aix*
<built-in>: fatal error: internal error: builtin function '__builtin_ddedpd'
had an unexpected return type 'DD'
AIX does not enable OPTION_MASK_DFP in the CPU masks.
Either rs6000-builtin.def should not define the builtin or rs6000-call.c
rs6000_common_init_builtins should not define the builtin.
started with r278684.
>From gcc-bugs-return-661248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:54:03 2019
Return-Path: <gcc-bugs-return-661248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121453 invoked by alias); 25 Nov 2019 14:54: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 121389 invoked by uid 48); 25 Nov 2019 14:53:59 -0000
From: "tom at geus dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69089] C++11: alignas(0) causes an error
Date: Mon, 25 Nov 2019 14:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: patch, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tom at geus dot me
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-69089-4-LxqLpbdzHX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03042.txt.bz2
Content-length: 426
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69089
Tom de Geus <tom at geus dot me> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tom at geus dot me
--- Comment #7 from Tom de Geus <tom at geus dot me> ---
Same problem here. It would be great if the patch could be integrated!
>From gcc-bugs-return-661249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:55:00 2019
Return-Path: <gcc-bugs-return-661249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123822 invoked by alias); 25 Nov 2019 14:55: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 123770 invoked by uid 48); 25 Nov 2019 14:54:56 -0000
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI2NjJdIE5ldzogY2hhbmdlIGluIGdjYyA4IHZzIDk6IGNh?= =?UTF-8?B?bGwgb2Ygb3ZlcmxvYWRlZCDigJhiYXNpY19zdHJpbmcoPGJyYWNlLWVuY2xv?= =?UTF-8?B?c2VkIGluaXRpYWxpemVyIGxpc3Q+KeKAmSBpcyBhbWJpZ3VvdXM=?Date: Mon, 25 Nov 2019 14:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-92662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03043.txt.bz2
Content-length: 2699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92662
Bug ID: 92662
Summary: change in gcc 8 vs 9: call of overloaded
‘basic_string(<brace-enclosed initializer list>)’ is
ambiguous
Product: gcc
Version: 9.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: matz at gcc dot gnu.org
Target Milestone: ---
A user of ours noted a difference in behaviour between gcc8 and gcc9 regarding
braced initializers. Take this example:
---------------------------------------------
#include <string>
// allow to steal _text from rvalues
struct Test
{
std::string const& str() const& { return _text; }
std::string && str() && { return std::move(_text); }
operator std::string const&() const& { return _text; }
operator std::string && () && { return std::move(_text); }
std::string _text;
};
int main()
{
Test t;
std::string a { std::move(t).str() }; // 1
std::string b { std::move(t) }; // 2
return 0;
}
---------------------------------------------
gcc 8 accepts the program (and str() && is chosen in line 1), whereas gcc 9
only accepts line 1 but not line 2 due to:
xorig.cc: In function ‘int main()’:
xorig.cc:19:32: error: call of overloaded ‘basic_string(<brace-enclosed
initializer list>)’ is ambiguous
19 | std::string b { std::move(t) };
| ^
In file included from /usr/include/c++/9/string:55,
from xorig.cc:1:
/usr/include/c++/9/bits/basic_string.h:3628:7: note: candidate:
‘std::basic_string<_CharT, _Traits,
_Alloc>::basic_string(std::basic_string<_CharT, _Traits, _Alloc>&&) [with
_CharT = char; _Traits = std::char_traits<char>; _Alloc =
std::allocator<char>]’
3628 | basic_string(basic_string&& __str)
| ^~~~~~~~~~~~
/usr/include/c++/9/bits/basic_string.h:3564:7: note: candidate:
‘std::basic_string<_CharT, _Traits, _Alloc>::basic_string(const
std::basic_string<_CharT, _Traits, _Alloc>&) [with _CharT = char; _Traits =
std::char_traits<char>; _Alloc = std::allocator<char>]’
3564 | basic_string(const basic_string& __str);
| ^~~~~~~~~~~~
One difference is the temporary object
used for calling .str() in line 1. But still I have difficulties to see
why there's a difference in ambiguities.
So, who's right (8 or 9), and due to which reasons. (Depending on that this
is either an error in gcc 8 or 9, so I'm not marking it yet).
>From gcc-bugs-return-661250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 14:58:04 2019
Return-Path: <gcc-bugs-return-661250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126352 invoked by alias); 25 Nov 2019 14:58:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126217 invoked by uid 48); 25 Nov 2019 14:57:59 -0000
From: "matz at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI2NjJdIGNoYW5nZSBpbiBnY2MgOCB2cyA5OiBjYWxsIG9m?= =?UTF-8?B?IG92ZXJsb2FkZWQg4oCYYmFzaWNfc3RyaW5nKDxicmFjZS1lbmNsb3NlZCBp?= =?UTF-8?B?bml0aWFsaXplciBsaXN0PinigJkgaXMgYW1iaWd1b3Vz?Date: Mon, 25 Nov 2019 14: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.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matz at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92662-4-oymPTB7otq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03044.txt.bz2
Content-length: 1299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92662
--- Comment #1 from Michael Matz <matz at gcc dot gnu.org> ---
I _think_ a reduced program would be this:
-----------------------------------------
template<typename _Tp> struct remove_ref { typedef _Tp type; };
template<typename _Tp> struct remove_ref<_Tp&> { typedef _Tp type; };
template<typename _Tp> struct remove_ref<_Tp&&> { typedef _Tp type; };
template<typename _Tp>
typename remove_ref<_Tp>::type&&
moveme(_Tp&& __t) noexcept;
struct S
{
S();
};
struct Test
{
S const& str() const&;
S && str() && ;
operator S const&() const&;
operator S && () && ;
};
int main()
{
Test t;
S a { moveme(t).str() };
S b { moveme(t) };
return 0;
}
-----------------------------------------
at least it gives same behaviour and captures the structure of the involved
move() functions.
% gcc-8 -c xreduced.cc
% gcc-9 -c xreduced.cc
x.cc: In function ‘int main()’:
x.cc:27:19: error: call of overloaded ‘S(<brace-enclosed initializer list>)’ is
ambiguous
27 | S b { moveme(t) };
| ^
x.cc:9:8: note: candidate: ‘constexpr S::S(const S&)’
9 | struct S
| ^
x.cc:9:8: note: candidate: ‘constexpr S::S(S&&)’
>From gcc-bugs-return-661251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 15:02:58 2019
Return-Path: <gcc-bugs-return-661251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 427 invoked by alias); 25 Nov 2019 15:02: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 356 invoked by uid 48); 25 Nov 2019 15:02:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvOTI2NjJdIGNoYW5nZSBpbiBnY2MgOCB2cyA5OiBjYWxsIG9m?= =?UTF-8?B?IG92ZXJsb2FkZWQg4oCYYmFzaWNfc3RyaW5nKDxicmFjZS1lbmNsb3NlZCBp?= =?UTF-8?B?bml0aWFsaXplciBsaXN0PinigJkgaXMgYW1iaWd1b3Vz?Date: Mon, 25 Nov 2019 15:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-92662-4-ab5BjQgxBq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03045.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92662
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm pretty sure GCC 9 is correct. It started to be rejected with r269602:
PR c++/86521 - wrong overload resolution with ref-qualifiers.
Here we were wrongly treating binding a const lvalue ref to an xvalue as
direct binding, which is wrong under [dcl.init.ref] and [over.match.ref].
* call.c (build_user_type_conversion_1): Don't use a conversion to
a
reference of the wrong rvalueness for direct binding.
>From gcc-bugs-return-661252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 15:11:06 2019
Return-Path: <gcc-bugs-return-661252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8260 invoked by alias); 25 Nov 2019 15: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 8227 invoked by uid 48); 25 Nov 2019 15:11:02 -0000
From: "fiesh at zefix dot tv" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/92663] New: Add __gcc_has_bug or __gcc_bug_fixed
Date: Mon, 25 Nov 2019 15:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 10.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fiesh at zefix dot tv
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-92663-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03046.txt.bz2
Content-length: 855
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92663
Bug ID: 92663
Summary: Add __gcc_has_bug or __gcc_bug_fixed
Product: gcc
Version: 10.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: fiesh at zefix dot tv
Target Milestone: ---
The former, while logically sounder, seems difficult to implement without
adding every single open ticket on GCC's Bugzilla and returning `true` for
every non-existent one.
So probably the latter is a better choice.
It would allow code like
#if __gcc_bug_fixed(12345)
actual_code();
#else
workaround_code();
#endif
Of course ideally the array containing the fixed bugs' numbers would be filled
directly from Bugzilla's database, if possible.
>From gcc-bugs-return-661253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 15:15:52 2019
Return-Path: <gcc-bugs-return-661253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11293 invoked by alias); 25 Nov 2019 15:15:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11210 invoked by uid 48); 25 Nov 2019 15:15:48 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/90835] Incompatibilities with macOS 10.15 headers
Date: Mon, 25 Nov 2019 15: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: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-90835-4-1bBJ6qnH3K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-90835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03047.txt.bz2
Content-length: 662
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90835
--- Comment #21 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Iain Sandoe from comment #20)
> As of XCode 11.3beta, the contained SDK works OK:
>
> https://gcc.gnu.org/ml/gcc-testresults/2019-11/msg01439.html
>
> We still have the underlying problems - which need to be addressed (so
> please don't close this PR yet) - but for now using the latest SDK should
> work.
"should work" means with the gcc svn trunk or with the patch posted in this
ticket applied? I would understand your remark that it should work without the
applied patch, as it stands from the gcc trunk.
>From gcc-bugs-return-661254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 15:56:55 2019
Return-Path: <gcc-bugs-return-661254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45354 invoked by alias); 25 Nov 2019 15:56: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 45292 invoked by uid 48); 25 Nov 2019 15:56:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/61414] enum class bitfield size-checking needs a separate warning flag controlling it
Date: Mon, 25 Nov 2019 15: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: unknown
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-61414-4-yeEp3CFYRD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61414-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61414-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03048.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61414
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 #21 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 47352
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=47352&action=edit
gcc10-pr61414.patch
Untested fix.
>From gcc-bugs-return-661255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 15:57:44 2019
Return-Path: <gcc-bugs-return-661255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46357 invoked by alias); 25 Nov 2019 15:57:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46298 invoked by uid 48); 25 Nov 2019 15:57:40 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/92661] [10 Regression] AIX bootstrap failure with builtin-types.def change
Date: Mon, 25 Nov 2019 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
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:
Message-ID: <bug-92661-4-bYSDnQ5ON8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
References: <bug-92661-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-11/txt/msg03049.txt.bz2
Content-length: 4434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92661
--- Comment #2 from David Edelsohn <dje at gcc dot gnu.org> ---
A crude work-around to allow GCC to bootstrap and show the extent of the
problem, I need the following patches to comment out all decimal builtins.
Index: rs6000-call.c
===================================================================
--- rs6000-call.c (revision 278691)
+++ rs6000-call.c (working copy)
@@ -7653,7 +7653,7 @@
/* signed args, unsigned return. */
case VSX_BUILTIN_XVCVDPUXDS_UNS:
case ALTIVEC_BUILTIN_FIXUNS_V4SF_V4SI:
- case MISC_BUILTIN_UNPACK_TD:
+ /* case MISC_BUILTIN_UNPACK_TD: */
case MISC_BUILTIN_UNPACK_V1TI:
h.uns_p[0] = 1;
break;
@@ -7676,7 +7676,7 @@
break;
/* unsigned arguments for 128-bit pack instructions. */
- case MISC_BUILTIN_PACK_TD:
+ /* case MISC_BUILTIN_PACK_TD: */
case MISC_BUILTIN_PACK_V1TI:
h.uns_p[1] = 1;
h.uns_p[2] = 1;
Index: rs6000-c.c
===================================================================
--- rs6000-c.c (revision 278691)
+++ rs6000-c.c (working copy)
@@ -4884,6 +4884,7 @@
{ P8V_BUILTIN_VEC_VCLZD, P8V_BUILTIN_VCLZD,
RS6000_BTI_unsigned_V2DI, RS6000_BTI_unsigned_V2DI, 0, 0 },
+#if 0
{ P9_BUILTIN_DFP_TSTSFI_LT, MISC_BUILTIN_TSTSFI_LT_TD,
RS6000_BTI_INTSI, RS6000_BTI_UINTSI, RS6000_BTI_dfloat128, 0 },
{ P9_BUILTIN_DFP_TSTSFI_LT, MISC_BUILTIN_TSTSFI_LT_DD,
@@ -4923,6 +4924,7 @@
RS6000_BTI_INTSI, RS6000_BTI_UINTSI, RS6000_BTI_dfloat128, 0 },
{ P9_BUILTIN_DFP_TSTSFI_OV_DD, MISC_BUILTIN_TSTSFI_OV_DD,
RS6000_BTI_INTSI, RS6000_BTI_UINTSI, RS6000_BTI_dfloat64, 0 },
+#endif
{ P9V_BUILTIN_VEC_VCTZ, P9V_BUILTIN_VCTZB,
RS6000_BTI_V16QI, RS6000_BTI_V16QI, 0, 0 },
Index: rs6000-builtin.def
===================================================================
--- rs6000-builtin.def (revision 278691)
+++ rs6000-builtin.def (working copy)
@@ -2298,6 +2298,7 @@
BU_P7_POWERPC64_MISC_2 (DIVDE, "divde", CONST, dive_di)
BU_P7_POWERPC64_MISC_2 (DIVDEU, "divdeu", CONST, diveu_di)
+#if 0
/* 1 argument DFP (decimal floating point) functions added in ISA 2.05. */
BU_DFP_MISC_1 (DXEX, "dxex", CONST, dfp_dxex_dd)
BU_DFP_MISC_1 (DXEXQ, "dxexq", CONST, dfp_dxex_td)
@@ -2313,6 +2314,7 @@
BU_DFP_MISC_2 (DSCLIQ, "dscliq", CONST, dfp_dscli_td)
BU_DFP_MISC_2 (DSCRI, "dscri", CONST, dfp_dscri_dd)
BU_DFP_MISC_2 (DSCRIQ, "dscriq", CONST, dfp_dscri_td)
+#endif
/* 0 argument void function that we pretend was added in ISA 2.06.
It's a special nop recognized by 2018+ firmware for P7 and up,
@@ -2338,9 +2340,11 @@
BU_P8V_MISC_3 (BCDSUB_GT, "bcdsub_gt", CONST, bcdsub_gt)
BU_P8V_MISC_3 (BCDSUB_OV, "bcdsub_ov", CONST, bcdsub_unordered)
+#if 0
/* 2 argument pack/unpack 128-bit floating point types. */
BU_DFP_MISC_2 (PACK_TD, "pack_dec128", CONST, packtd)
BU_DFP_MISC_2 (UNPACK_TD, "unpack_dec128", CONST, unpacktd)
+#endif
/* 0 argument general-purpose register functions added in ISA 3.0 (power9).
*/
BU_P9_MISC_0 (DARN_32, "darn_32", MISC, darn_32)
@@ -2356,6 +2360,7 @@
BU_P7_MISC_2 (PACK_V1TI, "pack_vector_int128", CONST, packv1ti)
BU_P7_MISC_2 (UNPACK_V1TI, "unpack_vector_int128", CONST, unpackv1ti)
+#if 0
/* 2 argument DFP (Decimal Floating Point) functions added in ISA 3.0. */
BU_P9_DFP_MISC_2 (TSTSFI_LT_DD, "dtstsfi_lt_dd", CONST, dfptstsfi_lt_dd)
BU_P9_DFP_MISC_2 (TSTSFI_LT_TD, "dtstsfi_lt_td", CONST, dfptstsfi_lt_td)
@@ -2385,6 +2390,7 @@
BU_P9_DFP_OVERLOAD_2 (TSTSFI_OV, "dtstsfi_ov")
BU_P9_DFP_OVERLOAD_2 (TSTSFI_OV_DD, "dtstsfi_ov_dd")
BU_P9_DFP_OVERLOAD_2 (TSTSFI_OV_TD, "dtstsfi_ov_td")
+#endif
/* 1 argument vector functions added in ISA 3.0 (power9). */
BU_P9V_AV_1 (VCTZB, "vctzb", CONST, ctzv16qi2)
>From gcc-bugs-return-661256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Nov 25 16:07:05 2019
Return-Path: <gcc-bugs-return-661256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56368 invoked by alias); 25 Nov 2019 16:07:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56309 invoked by uid 89); 25 Nov 2019 16:07:05 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=3.8 required=5.0 testsºYES_50,HTML_MESSAGE,KAM_SHORT,RCVD_IN_JMF_BL,SPF_HELO_PASS,SPF_PASS autolearn=no version=3.3.1 spammy=UD:ly, bit.ly, UD:bit.ly, bitly
X-HELO: arnoldc.com
Received: from arnoldc.com (HELO arnoldc.com) (109.201.142.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Mon, 25 Nov 2019 16:07:03 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; s=dkim99; d=arnoldc.com; h=Reply-To:To:From:Subject:Message-ID:Date:MIME-Version:Content-Type; i=alla.brown@arnoldc.com; bhÞmot8QgiCKPd9/ZUm/LptligrPKio10wvmCq8Pa0jw=; b=WKA8EOcKKFnWPplIJueHzf1ihBNF4J2JgmRACkTHTZhyWjtLXSToL6CZbK+9WSeoUFnxUpWBsFBc EBFFdDWreAdfGca33rVITsBNyvfQd2NRPJN1R+JFkduOtaFGHAVzZ3hrILQbSPJ1c60k5O5Awa54 4rRHJvZYK3vWj5DOJHoReply-To: no-reply@arnoldc.com
To: gcc-bugs@gcc.gnu.org
From: alla.brown@arnoldc.com
Subject: I see all what you do
Message-ID: <2DF36037.5306976@arnoldc.com>
Date: Mon, 25 Nov 2019 16:07:00 -0000
User-Agent: Mozilla/5.0 (Windows NT 6.2; Win64; x64; rv:38.0) Gecko/20100101 Thunderbird/38.0.0
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2019-11/txt/msg03051.txt.bz2
Content-length: 131
I see whatever you do , I have picture of you and all your accounts.
If you dont pay me ....
here the proofhttp://bit.ly/2XJXn91
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/92639] Error: Integer too big for its kind at (1)
2019-11-23 17:11 [Bug fortran/92639] New: Error: Integer too big for its kind at (1) gsocshubham at gmail dot com
@ 2023-03-01 17:51 ` cessenat at gmail dot com
2023-03-01 18:29 ` jvdelisle at gcc dot gnu.org
2023-03-01 18:32 ` sgk at troutmask dot apl.washington.edu
2 siblings, 0 replies; 4+ messages in thread
From: cessenat at gmail dot com @ 2023-03-01 17:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639
--- Comment #2 from Olivier Cessenat <cessenat at gmail dot com> ---
integer(kind=4) valid range is -2147483648_4 to +2147483647_4.
So I consider this is a gfortran bug.
Moreover, if -2147483648_4 is considered out of range, why
-2147483647_4 - 1_4 is not ? Constant elimination makes it evaluated to
-2147483648_4.
I disagree with the term "there are no negative integers"
[-2147483648_4 is equal to +2147483648_4]
Other compilers, such as aocc, nvfortran, ifort, oneapi are OK with that
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/92639] Error: Integer too big for its kind at (1)
2019-11-23 17:11 [Bug fortran/92639] New: Error: Integer too big for its kind at (1) gsocshubham at gmail dot com
2023-03-01 17:51 ` [Bug fortran/92639] " cessenat at gmail dot com
@ 2023-03-01 18:29 ` jvdelisle at gcc dot gnu.org
2023-03-01 18:32 ` sgk at troutmask dot apl.washington.edu
2 siblings, 0 replies; 4+ messages in thread
From: jvdelisle at gcc dot gnu.org @ 2023-03-01 18:29 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #3 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Please observe:
program demonstrate
integer :: i
i = huge(i)
print *, i
i= -huge(i)
print *, i
end program
$ gfc demonstrate.f90
$ ./a.out
2147483647
-2147483647
This is by the fortran standard definition for a 32 bit integer. You cannot
represent 2147483648 in 32 bits because you need bit 32 to represent the sign
of the value. How other compilers are storing the sign I can not speak to.
^ permalink raw reply [flat|nested] 4+ messages in thread
* [Bug fortran/92639] Error: Integer too big for its kind at (1)
2019-11-23 17:11 [Bug fortran/92639] New: Error: Integer too big for its kind at (1) gsocshubham at gmail dot com
2023-03-01 17:51 ` [Bug fortran/92639] " cessenat at gmail dot com
2023-03-01 18:29 ` jvdelisle at gcc dot gnu.org
@ 2023-03-01 18:32 ` sgk at troutmask dot apl.washington.edu
2 siblings, 0 replies; 4+ messages in thread
From: sgk at troutmask dot apl.washington.edu @ 2023-03-01 18:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639
--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Mar 01, 2023 at 05:51:29PM +0000, cessenat at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92639
>
> --- Comment #2 from Olivier Cessenat <cessenat at gmail dot com> ---
> integer(kind=4) valid range is -2147483648_4 to +2147483647_4.
> So I consider this is a gfortran bug.
>
> Moreover, if -2147483648_4 is considered out of range, why
> -2147483647_4 - 1_4 is not ? Constant elimination makes it evaluated to
> -2147483648_4.
>
> I disagree with the term "there are no negative integers"
> [-2147483648_4 is equal to +2147483648_4]
^^^^^^^^^^^^
exceeds huge(1)
% cat a.f90
print *, huge(1)
end
% gfortran -o z a.f90 && ./z
2147483647
I've already explained the issue. But, I'll go over it
one more time. -2147483648_4 is parsed as unary minus
operator and an operand of 2147483648_4. 2147483648_4
exceeds huge(1). Fortunately, gfortran can save you,
and the error message even tells you.
1 | i = -2147483648_4
| 1
Error: Integer too big for its kind at (1). This check can be
disabled with the option '-fno-range-check'
So, let me amend the quote above "there are no negative
integer-literal constants."
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-03-01 18:32 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-11-23 17:11 [Bug fortran/92639] New: Error: Integer too big for its kind at (1) gsocshubham at gmail dot com
2023-03-01 17:51 ` [Bug fortran/92639] " cessenat at gmail dot com
2023-03-01 18:29 ` jvdelisle at gcc dot gnu.org
2023-03-01 18:32 ` sgk at troutmask dot apl.washington.edu
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).