public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c/88774] New: Qualification of parameters does not change a function type: Bug or standard defect?
@ 2019-01-09 19:16 anders.granlund.0 at gmail dot com
0 siblings, 0 replies; only message in thread
From: anders.granlund.0 at gmail dot com @ 2019-01-09 19:16 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: 2698163 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88774
Bug ID: 88774
Summary: Qualification of parameters does not change a function
type: Bug or standard defect?
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
int main(void)
{
typedef void f(int);
typedef void f(const int);
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
No error messages outputed.
Question:
The function types in the two typedefs are compatible, but are they distinct?
The standard is not very clear on this.
If the two function types are distinct the expected behaviour is to get an
error message about redeclaring the typedef name f with a different type.
Else the observed behaviour is expected and there is no bug.
>From gcc-bugs-return-628563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 19:21:31 2019
Return-Path: <gcc-bugs-return-628563-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80777 invoked by alias); 9 Jan 2019 19:21: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 80687 invoked by uid 48); 9 Jan 2019 19:21:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Wed, 09 Jan 2019 19:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-E0aUq0Y4Wi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01372.txt.bz2
Content-length: 936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And, finally found the reason why r266345 causes the wrong-code.
The problem is that the align_dynamic_address instructions are emitted at
whatever spot in the function asked for the temporary slot, those instructions
initialize some pseudo register and that pseudo register is used in the MEM
slot returned from assign_stack_local_1. But one of the assign_stack_local_1
callers,
assign_stack_temp_for_type, is able to reuse such temporary slots, and e.g. on
the gimplify.ii test it does this, first (mem/c:BLK (reg/f:DI 1536) [0 A256])
is created for BLKmode, 24, gimple_stmt_iterator type and then in the same
compiled function returned again in two other spots. The problem is that the
reg/f:DI 1536 initialization code doesn't dominate the other two spots, so
those use uninitialized pointer there.
>From gcc-bugs-return-628564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:03:40 2019
Return-Path: <gcc-bugs-return-628564-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86044 invoked by alias); 9 Jan 2019 20:03: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 83925 invoked by uid 48); 9 Jan 2019 20:03:34 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87314] pointless comparison of malloc result to a string not eliminated
Date: Wed, 09 Jan 2019 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87314-4-FppWvxIAnJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87314-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87314-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01373.txt.bz2
Content-length: 266
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87314
--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
It isn't just with malloc, the following are not optimized either.
int f(){ int a; return &a=="hello"; }
int g(){ return "bye"=="hello"; }
>From gcc-bugs-return-628565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:14:57 2019
Return-Path: <gcc-bugs-return-628565-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19377 invoked by alias); 9 Jan 2019 20:14:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19259 invoked by uid 48); 9 Jan 2019 20:14:43 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/78782] [x86] _mm_loadu_si64 intrinsic missing
Date: Wed, 09 Jan 2019 20:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-78782-4-5x9C6AxA9p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01374.txt.bz2
Content-length: 395
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78782
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
CC added.
>From gcc-bugs-return-628566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:31:52 2019
Return-Path: <gcc-bugs-return-628566-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 952 invoked by alias); 9 Jan 2019 20:31:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 860 invoked by uid 55); 9 Jan 2019 20:31:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68426] Simplification of SPREAD with a derived type element is unimplemented
Date: Wed, 09 Jan 2019 20:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68426-4-Y4pkkIMYvI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01375.txt.bz2
Content-length: 755
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68426
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Wed Jan 9 20:31:07 2019
New Revision: 267781
URL: https://gcc.gnu.org/viewcvs?rev=267781&root=gcc&view=rev
Log:
2019-01-09 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/68426
* simplify.c (gfc_simplify_spread): Also simplify if the
type of source is an EXPR_STRUCTURE.
2019-01-09 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/68426
* gfortran.dg/spread_simplify_1.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/spread_simplify_1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/simplify.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:32:36 2019
Return-Path: <gcc-bugs-return-628567-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7709 invoked by alias); 9 Jan 2019 20:32:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7633 invoked by uid 48); 9 Jan 2019 20:32:32 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88761] [8/9 Regression] ICE in tsubst_copy, at cp/pt.c:15478 when chaining lambda calls & fold-expressions
Date: Wed, 09 Jan 2019 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88761-4-D5OGgYeyeJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01376.txt.bz2
Content-length: 512
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88761
ensadc at mailnesia dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ensadc at mailnesia dot com
--- Comment #2 from ensadc at mailnesia dot com ---
Reduced:
template <int>
void a() {
int b;
[&](auto c) {
if constexpr (sizeof(c) != 42) {
[&] { b; };
}
}(0);
}
template void a<1>();
>From gcc-bugs-return-628568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:33:04 2019
Return-Path: <gcc-bugs-return-628568-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8699 invoked by alias); 9 Jan 2019 20: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 8525 invoked by uid 48); 9 Jan 2019 20:32:59 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68426] Simplification of SPREAD with a derived type element is unimplemented
Date: Wed, 09 Jan 2019 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-68426-4-r8AVGy5xck@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68426-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68426-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01377.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68426
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed on trunk, closing.
>From gcc-bugs-return-628569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:34:46 2019
Return-Path: <gcc-bugs-return-628569-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24861 invoked by alias); 9 Jan 2019 20:34: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 18565 invoked by uid 48); 9 Jan 2019 20:34:40 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88762] C++17 Deduction guide and operator expression produces missing template argument error
Date: Wed, 09 Jan 2019 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88762-4-id6Mcxxu8N@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01378.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88762
ensadc at mailnesia dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ensadc at mailnesia dot com
--- Comment #1 from ensadc at mailnesia dot com ---
Duplicate of bug 87709?
>From gcc-bugs-return-628570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:46:12 2019
Return-Path: <gcc-bugs-return-628570-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62242 invoked by alias); 9 Jan 2019 20:46:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61602 invoked by uid 48); 9 Jan 2019 20:46:01 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 20:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-z5RLTPsqSx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01379.txt.bz2
Content-length: 2668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #27 from Iain Sandoe <iains at gcc dot gnu.org> ---
JFTR, I did an experiment with a trivial hot/cold partitioned object and ld64
from XCode10.1.
Yes, it complains - but it still publishes the symbol as a weak extern.
====
I looked a bit harder at the symbol resolutions you attached.
* In the working case, the libsupc++ (part of libstdc++) versions of the
various new functions/operators are overriding the ones from libc++abi (because
the libstdc++.dylib is presented first, I assume).
* In the non-working case, the various new functions/operators are some
resolved from the static instances [static_1.exe:__Zblahblah] - and some from
libc++abi. This is exactly the kind of fragility I was concerned about.
e.g.
dyld: weak bind: static_1.exe:0x10E034738 = static_1.exe:__ZnamRKSt9nothrow_t,
*0x10E034738 = 0x10DD4E540
dyld: weak bind: libstdc++.6.dylib:0x112FC0980 =
static_1.exe:__ZnamRKSt9nothrow_t, *0x112FC0980 = 0x10DD4E540
dyld: weak bind: libc++abi.dylib:0x7FFF8C76F0A0 =
libc++abi.dylib:__ZnamSt11align_val_t, *0x7FFF8C76F0A0 = 0x7FFF578B9C9D
dyld: weak bind: libstdc++.6.dylib:0x112FC0988 =
libc++abi.dylib:__ZnamSt11align_val_t, *0x112FC0988 = 0x7FFF578B9C9D
dyld: weak bind: static_1.exe:0x10E034740 = static_1.exe:__Znwm, *0x10E034740 =
0x10DD4E500
dyld: weak bind: liblcio.2.12.dylib:0x1125F0E08 = static_1.exe:__Znwm,
*0x1125F0E08 = 0x10DD4E500
and ..
dyld: weak bind: libstdc++.6.dylib:0x112FC0990 = static_1.exe:__Znwm,
*0x112FC0990 = 0x10DD4E500
dyld: weak bind: libc++abi.dylib:0x7FFF8C76F0B0 =
libc++abi.dylib:__ZnwmSt11align_val_t, *0x7FFF8C76F0B0 = 0x7FFF578B9BE7
dyld: weak bind: libstdc++.6.dylib:0x112FC0998 =
libc++abi.dylib:__ZnwmSt11align_val_t, *0x112FC0998 = 0x7FFF578B9BE7
dyld: lazy bind: libgfortran.5.dylib:0x1128D75D0 =
libsystem_pthread.dylib:_pthread_key_create, *0x1128D75D0 = 0x7FFF5A38270C
If you look at the working case, these all seem to be consistently resolved
from libstdc++.dylib (there's a lot of data, I don't claim to have checked
every entry, but a portion).
===
Finally, I don't think that there's been any change to the build of libstdc++
that would actually have changed anything about that particular circumstance
(the warning given) in the period mentioned.
** It *is* possible that there's been some change to the system dyld [dynamic
linker] during that time as part of an OS upgrade (but not sure if there was an
upgrade over that period either) that has tightened up some aspect of the
symbol binding - but not sure how to prove/disprove that right now.
>From gcc-bugs-return-628571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 20:49:19 2019
Return-Path: <gcc-bugs-return-628571-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66851 invoked by alias); 9 Jan 2019 20:49: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 64824 invoked by uid 48); 9 Jan 2019 20:48:33 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] New: [8/9 Regression] Optimize std::string assignment
Date: Wed, 09 Jan 2019 20:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01380.txt.bz2
Content-length: 2571
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
Bug ID: 88775
Summary: [8/9 Regression] Optimize std::string assignment
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: glisse at gcc dot gnu.org
Target Milestone: ---
#include <bits/c++config.h>
#undef _GLIBCXX_EXTERN_TEMPLATE
#define _GLIBCXX_EXTERN_TEMPLATE 0
#include<string>
__attribute__((flatten))
std::string f(){
std::string s;
s="hello";
return s;
}
Yes, I have to go through some lengths to convince gcc to at least try to
optimize...
With gcc-7, I get
<bb 2> [14.44%]:
_3 = &MEM[(struct basic_string *)s_2(D)].D.21635._M_local_buf;
MEM[(struct _Alloc_hider *)s_2(D)]._M_p = _3;
MEM[(size_type *)s_2(D) + 8B] = 0;
MEM[(char_type &)s_2(D) + 16] = 0;
if (_3 != "hello")
goto <bb 3>; [75.00%]
else
goto <bb 4>; [25.00%]
<bb 3> [1.43%]:
__builtin_memcpy (_3, "hello", 5);
goto <bb 5>; [100.00%]
<bb 4> [0.97%]:
__builtin_memcpy ("hello", &MEM[(void *)"hello" + 5B], 5);
<bb 5> [14.43%]:
MEM[(size_type *)s_2(D) + 8B] = 5;
MEM[(char_type &)s_2(D) + 21] = 0;
return s_2(D);
which is kind of OK. It would be much better if we folded _3 != "hello", but it
is already small enough.
With gcc-9, I get something that starts with
__x.7_6 = (long unsigned int) "hello";
__y.8_7 = (long unsigned int) _3;
if (__x.7_6 < __y.8_7)
goto <bb 4>; [50.00%]
else
goto <bb 3>; [50.00%]
<bb 3> [local count: 38463891]:
if (__x.7_6 > __y.8_7)
goto <bb 4>; [50.00%]
else
goto <bb 5>; [50.00%]
ifcombine would kindly turn this into __x.7_6 != __y.8_7, but it doesn't look
like this yet when ifcombine runs. We also have equivalent blocks (reached by
goto, not fallthrough)
<bb 4> [local count: 19039626]:
__builtin_memcpy (_3, "hello", 5);
goto <bb 16>; [100.00%]
<bb 6> [local count: 3173271]:
__builtin_memcpy (_3, "hello", 5);
goto <bb 16>; [100.00%]
<bb 16> [local count: 114817586]:
# prephitmp_14 = PHI <pretmp_16(13), pretmp_25(15), _3(4), _3(8), _3(6),
_3(14)>
that we fail to merge. In the end, we have 4 times more code than we used to...
This is most likely caused by a change in libstdc++, but I am categorizing it
as tree-optimization because I believe we need some improvements there,
whatever libstdc++ decides to do.
>From gcc-bugs-return-628572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:01:34 2019
Return-Path: <gcc-bugs-return-628572-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87689 invoked by alias); 9 Jan 2019 21:01:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87505 invoked by uid 55); 9 Jan 2019 21:01:23 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88774] Qualification of parameters does not change a function type: Bug or standard defect?
Date: Wed, 09 Jan 2019 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88774-4-GJsUsUHI7g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01381.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88774
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Although the wording is different in the two cases (and the rule for
return types is newer), I think qualifiers on function parameters should
be considered as not part of the type just as with qualifiers on return
types. (Qualifiers on parameters *in the function definition* do affect
uses of those parameters within the function definition.) I think the
introduction of the concept of types being the same simply failed to
consider this issue.
>From gcc-bugs-return-628573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:07:39 2019
Return-Path: <gcc-bugs-return-628573-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105784 invoked by alias); 9 Jan 2019 21:07:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103360 invoked by uid 48); 9 Jan 2019 21:07:33 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] New: Namelist read from stdin: loss of data
Date: Wed, 09 Jan 2019 21:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01382.txt.bz2
Content-length: 3135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
Bug ID: 88776
Summary: Namelist read from stdin: loss of data
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: anlauf at gmx dot de
Target Milestone: ---
Reading namelist from unit 5 may skip valid data later when an error is
encountered. This problem does not occur when another unit number is used.
Example:
% cat gfcbug154.f90
program nmlbug
implicit none
integer :: i, stat, nnml
nnml = 5 ! No problem with nnml = 10
! nnml = 10
open (nnml, file="gfcbug154.dat", action="read")
do i = 1, 3
print *, "# Read namelist", i
call read_nml_type_2
print *
end do
contains
subroutine read_nml_type_2
!----------------------------------------------------------
! variant 2 of namelist input: chan = real char(len=*) real
!----------------------------------------------------------
type t_chan
real :: ichan = -1.
character(len=10) :: flag = ''
real :: band = -1.
end type t_chan
type(t_chan) :: chan(2)
namelist /CHAN_NML/ chan
chan(:) = t_chan(-1.,'',-1.)
stat = 0
read (nnml, nml=CHAN_NML, iostat=stat, end=99)
print *, "read_nml_type_2: stat=", stat
print *, "chan(1)=", chan(1)
print *, "chan(2)=", chan(2)
return
99 stop "EOF"
end subroutine read_nml_type_2
end program nmlbug
% cat gfcbug154.dat
&CHAN_NML
chan = 3 '#1 ' '0.1'
6 '#1 ' 0.8
/
&CHAN_NML
chan = 4 '#2 ' 0.1
7 '#2 ' 0.2
/
&CHAN_NML
chan = 5 '#3 ' 0.3
8 '#3 ' 0.4
/
The above code outputs:
# Read namelist 1
read_nml_type_2: stat= 5010
chan(1)= 4.00000000 #2 0.100000001
chan(2)= 7.00000000 #2 0.200000003
# Read namelist 2
read_nml_type_2: stat= 0
chan(1)= 5.00000000 #3 0.300000012
chan(2)= 8.00000000 #3 0.400000006
# Read namelist 3
STOP EOF
whereas with e.g. unit 10 it (correctly) outputs:
# Read namelist 1
read_nml_type_2: stat= 5010
chan(1)= 3.00000000 #1 -1.00000000
chan(2)= -1.00000000 -1.00000000
# Read namelist 2
read_nml_type_2: stat= 0
chan(1)= 4.00000000 #2 0.100000001
chan(2)= 7.00000000 #2 0.200000003
# Read namelist 3
read_nml_type_2: stat= 0
chan(1)= 5.00000000 #3 0.300000012
chan(2)= 8.00000000 #3 0.400000006
For some reason, when an error is encountered during the first read,
it correctly sets the error status, but apparently continues to the
second namelist instance.
>From gcc-bugs-return-628575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:11:53 2019
Return-Path: <gcc-bugs-return-628575-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13324 invoked by alias); 9 Jan 2019 21:11:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13256 invoked by uid 48); 9 Jan 2019 21:11:49 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 21:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-4JVoHGlUa8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01384.txt.bz2
Content-length: 314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #28 from Iain Sandoe <iains at gcc dot gnu.org> ---
I wonder what would happen if you add -rdynamic (or -Wl,-export_dynamic) to the
main exe in the static link case, perhaps that would ensure that the libstdc++
symbols get resolved from there.
>From gcc-bugs-return-628574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:11:44 2019
Return-Path: <gcc-bugs-return-628574-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12538 invoked by alias); 9 Jan 2019 21:11: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 12497 invoked by uid 48); 9 Jan 2019 21:11:39 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Wed, 09 Jan 2019 21:11: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88776-4-CjccpDghKa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01383.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #1 from Harald Anlauf <anlauf at gmx dot de> ---
I wrote "loss of data" because the second (valid) namelist could not be
properly read because of stat /= 0.
>From gcc-bugs-return-628576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:13:45 2019
Return-Path: <gcc-bugs-return-628576-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15269 invoked by alias); 9 Jan 2019 21:13: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 15152 invoked by uid 48); 9 Jan 2019 21:13:41 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] New: [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Wed, 09 Jan 2019 21:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget attachments.created
Message-ID: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01385.txt.bz2
Content-length: 1643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
Bug ID: 88777
Summary: [9 Regression] Out-of-range offsets building glibc
test-tgmath2.c for hppa-linux-gnu
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: jsm28 at gcc dot gnu.org
CC: amodra at gcc dot gnu.org, danglin at gcc dot gnu.org,
law at redhat dot com
Target Milestone: ---
Target: hppa*-*-*
Created attachment 45393
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45393&action=edit
preprocessed source (gzipped)
Building test-tgmath2.c from the glibc testsuite for hppa-linux-gnu produces
errors from the assembler of the form:
/tmp/ccjjfWe2.s: Assembler messages:
/tmp/ccjjfWe2.s:123489: Error: Field out of range [-8192..8191] (8596).
/tmp/ccjjfWe2.s:123563: Error: Field out of range [-8192..8191] (8388).
/tmp/ccjjfWe2.s:151239: Error: Field out of range [-8192..8191] (8600).
/tmp/ccjjfWe2.s:151315: Error: Field out of range [-8192..8191] (8392).
/tmp/ccjjfWe2.s:178466: Error: Field out of range [-8192..8191] (8596).
/tmp/ccjjfWe2.s:178540: Error: Field out of range [-8192..8191] (8388).
This appeared with r267666 ("genattrtab bit-rot, and if_then_else in values"),
though I suppose it was probably latent before then.
gzipped test attached. Compile with: -c -std=gnu11 -fgnu89-inline -g -O2
-fmerge-all-constants -frounding-math -fno-stack-protector -fmath-errno
-fno-builtin
>From gcc-bugs-return-628577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:31:35 2019
Return-Path: <gcc-bugs-return-628577-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64529 invoked by alias); 9 Jan 2019 21:31: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 62107 invoked by uid 48); 9 Jan 2019 21:31:30 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88778] New: Odd Complex float load
Date: Wed, 09 Jan 2019 21:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01386.txt.bz2
Content-length: 967
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
Bug ID: 88778
Summary: Odd Complex float load
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: ubizjak at gmail dot com
Target Milestone: ---
[hjl@gnu-cfl-1 fp16-9]$ cat y.i
_Complex float
foo (_Complex float *p)
{
return *p;
}
[hjl@gnu-cfl-1 fp16-9]$ gcc -S -O2 y.i
[hjl@gnu-cfl-1 fp16-9]$ cat y.s
.file "y.i"
.text
.p2align 4,,15
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
movss 4(%rdi), %xmm0
movss (%rdi), %xmm1
movss %xmm0, -4(%rsp)
movss %xmm1, -8(%rsp)
movq -8(%rsp), %xmm0
ret
.cfi_endproc
A single load should be used.
>From gcc-bugs-return-628579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:38:52 2019
Return-Path: <gcc-bugs-return-628579-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102153 invoked by alias); 9 Jan 2019 21:38:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96556 invoked by uid 48); 9 Jan 2019 21:38:47 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Wed, 09 Jan 2019 21:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-88777-4-76g2u1V9Ry@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01388.txt.bz2
Content-length: 2318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
Ever confirmed|0 |1
--- Comment #1 from Jeffrey A. Law <law at redhat dot com> ---
I see it in my hppa bootstraps as well. I wonder if we mis-simplified the
length computations in the MD file. The offsets I saw weren't even close, so
it's not like we've got an off-by-1 error or something like that.
/tmp/ccUynPaB.s: Assembler messages:
/tmp/ccUynPaB.s:153251: Error: Field out of range [-8192..8191] (8752).
/tmp/ccUynPaB.s:153421: Error: Field out of range [-8192..8191] (8548).
/tmp/ccUynPaB.s:188220: Error: Field out of range [-8192..8191] (8472).
Makefile:1116: recipe for target 'c/c-parser.o' failed
make[3]: *** [c/c-parser.o] Error 1
make[3]: *** Waiting for unfinished jobs....
/tmp/ccS9IfKy.s: Assembler messages:
/tmp/ccS9IfKy.s:135986: Error: Field out of range [-8192..8191] (8424).
/tmp/ccS9IfKy.s:148708: Error: Field out of range [-8192..8191] (8472).
/tmp/ccS9IfKy.s:148723: Error: Field out of range [-8192..8191] (8296).
/tmp/ccS9IfKy.s:149110: Error: Field out of range [-8192..8191] (8484).
/tmp/ccS9IfKy.s:162109: Error: Field out of range [-8192..8191] (8276).
/tmp/ccS9IfKy.s:167348: Error: Field out of range [-8192..8191] (8348).
/tmp/ccS9IfKy.s:167710: Error: Field out of range [-8192..8191] (8212).
/tmp/ccS9IfKy.s:167891: Error: Field out of range [-8192..8191] (8340).
/tmp/ccS9IfKy.s:168136: Error: Field out of range [-8192..8191] (8232).
/tmp/ccS9IfKy.s:168152: Error: Field out of range [-8192..8191] (8316).
/tmp/ccS9IfKy.s:168174: Error: Field out of range [-8192..8191] (8368).
/tmp/ccS9IfKy.s:168268: Error: Field out of range [-8192..8191] (8296).
/tmp/ccS9IfKy.s:168335: Error: Field out of range [-8192..8191] (8332).
/tmp/ccS9IfKy.s:187861: Error: Field out of range [-8192..8191] (8348).
/tmp/ccS9IfKy.s:188993: Error: Field out of range [-8192..8191] (8528).
/tmp/ccS9IfKy.s:194086: Error: Field out of range [-8192..8191] (8276).
Makefile:1116: recipe for target 'c/c-typeck.o' failed
>From gcc-bugs-return-628578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:38:26 2019
Return-Path: <gcc-bugs-return-628578-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83010 invoked by alias); 9 Jan 2019 21:38:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71770 invoked by uid 55); 9 Jan 2019 21:38:17 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16615] throughout gcc docu and code numerous "can not"'s appear
Date: Wed, 09 Jan 2019 21:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 3.4.1
X-Bugzilla-Keywords: documentation, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16615-4-DFWls2wUtA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01387.txt.bz2
Content-length: 14466
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16615
--- Comment #11 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Wed Jan 9 21:37:45 2019
New Revision: 267783
URL: https://gcc.gnu.org/viewcvs?rev=267783&root=gcc&view=rev
Log:
2019-01-09 Sandra Loosemore <sandra@codesourcery.com>
PR other/16615 [1/5]
contrib/
* mklog: Mechanically replace "can not" with "cannot".
gcc/
* Makefile.in: Mechanically replace "can not" with "cannot".
* alias.c: Likewise.
* builtins.c: Likewise.
* calls.c: Likewise.
* cgraph.c: Likewise.
* cgraph.h: Likewise.
* cgraphclones.c: Likewise.
* cgraphunit.c: Likewise.
* combine-stack-adj.c: Likewise.
* combine.c: Likewise.
* common/config/i386/i386-common.c: Likewise.
* config/aarch64/aarch64.c: Likewise.
* config/alpha/sync.md: Likewise.
* config/arc/arc.c: Likewise.
* config/arc/predicates.md: Likewise.
* config/arm/arm-c.c: Likewise.
* config/arm/arm.c: Likewise.
* config/arm/arm.h: Likewise.
* config/arm/arm.md: Likewise.
* config/arm/cortex-r4f.md: Likewise.
* config/csky/csky.c: Likewise.
* config/csky/csky.h: Likewise.
* config/darwin-f.c: Likewise.
* config/epiphany/epiphany.md: Likewise.
* config/i386/i386.c: Likewise.
* config/i386/sol2.h: Likewise.
* config/m68k/m68k.c: Likewise.
* config/mcore/mcore.h: Likewise.
* config/microblaze/microblaze.md: Likewise.
* config/mips/20kc.md: Likewise.
* config/mips/sb1.md: Likewise.
* config/nds32/nds32.c: Likewise.
* config/nds32/predicates.md: Likewise.
* config/pa/pa.c: Likewise.
* config/rs6000/e300c2c3.md: Likewise.
* config/rs6000/rs6000.c: Likewise.
* config/s390/s390.h: Likewise.
* config/sh/sh.c: Likewise.
* config/sh/sh.md: Likewise.
* config/spu/vmx2spu.h: Likewise.
* cprop.c: Likewise.
* dbxout.c: Likewise.
* df-scan.c: Likewise.
* doc/cfg.texi: Likewise.
* doc/extend.texi: Likewise.
* doc/fragments.texi: Likewise.
* doc/gty.texi: Likewise.
* doc/invoke.texi: Likewise.
* doc/lto.texi: Likewise.
* doc/md.texi: Likewise.
* doc/objc.texi: Likewise.
* doc/rtl.texi: Likewise.
* doc/tm.texi: Likewise.
* dse.c: Likewise.
* emit-rtl.c: Likewise.
* emit-rtl.h: Likewise.
* except.c: Likewise.
* expmed.c: Likewise.
* expr.c: Likewise.
* fold-const.c: Likewise.
* genautomata.c: Likewise.
* gimple-fold.c: Likewise.
* hard-reg-set.h: Likewise.
* ifcvt.c: Likewise.
* ipa-comdats.c: Likewise.
* ipa-cp.c: Likewise.
* ipa-devirt.c: Likewise.
* ipa-fnsummary.c: Likewise.
* ipa-icf.c: Likewise.
* ipa-inline-transform.c: Likewise.
* ipa-inline.c: Likewise.
* ipa-polymorphic-call.c: Likewise.
* ipa-profile.c: Likewise.
* ipa-prop.c: Likewise.
* ipa-pure-const.c: Likewise.
* ipa-reference.c: Likewise.
* ipa-split.c: Likewise.
* ipa-visibility.c: Likewise.
* ipa.c: Likewise.
* ira-build.c: Likewise.
* ira-color.c: Likewise.
* ira-conflicts.c: Likewise.
* ira-costs.c: Likewise.
* ira-int.h: Likewise.
* ira-lives.c: Likewise.
* ira.c: Likewise.
* ira.h: Likewise.
* loop-invariant.c: Likewise.
* loop-unroll.c: Likewise.
* lower-subreg.c: Likewise.
* lra-assigns.c: Likewise.
* lra-constraints.c: Likewise.
* lra-eliminations.c: Likewise.
* lra-lives.c: Likewise.
* lra-remat.c: Likewise.
* lra-spills.c: Likewise.
* lra.c: Likewise.
* lto-cgraph.c: Likewise.
* lto-streamer-out.c: Likewise.
* postreload-gcse.c: Likewise.
* predict.c: Likewise.
* profile-count.h: Likewise.
* profile.c: Likewise.
* recog.c: Likewise.
* ree.c: Likewise.
* reload.c: Likewise.
* reload1.c: Likewise.
* reorg.c: Likewise.
* resource.c: Likewise.
* rtl.def: Likewise.
* rtl.h: Likewise.
* rtlanal.c: Likewise.
* sched-deps.c: Likewise.
* sched-ebb.c: Likewise.
* sched-rgn.c: Likewise.
* sel-sched-ir.c: Likewise.
* sel-sched.c: Likewise.
* shrink-wrap.c: Likewise.
* simplify-rtx.c: Likewise.
* symtab.c: Likewise.
* target.def: Likewise.
* toplev.c: Likewise.
* tree-call-cdce.c: Likewise.
* tree-cfg.c: Likewise.
* tree-complex.c: Likewise.
* tree-core.h: Likewise.
* tree-eh.c: Likewise.
* tree-inline.c: Likewise.
* tree-loop-distribution.c: Likewise.
* tree-nrv.c: Likewise.
* tree-profile.c: Likewise.
* tree-sra.c: Likewise.
* tree-ssa-alias.c: Likewise.
* tree-ssa-dce.c: Likewise.
* tree-ssa-dom.c: Likewise.
* tree-ssa-forwprop.c: Likewise.
* tree-ssa-loop-im.c: Likewise.
* tree-ssa-loop-ivcanon.c: Likewise.
* tree-ssa-loop-ivopts.c: Likewise.
* tree-ssa-loop-niter.c: Likewise.
* tree-ssa-phionlycprop.c: Likewise.
* tree-ssa-phiopt.c: Likewise.
* tree-ssa-propagate.c: Likewise.
* tree-ssa-threadedge.c: Likewise.
* tree-ssa-threadupdate.c: Likewise.
* tree-ssa-uninit.c: Likewise.
* tree-ssanames.c: Likewise.
* tree-streamer-out.c: Likewise.
* tree.c: Likewise.
* tree.h: Likewise.
* vr-values.c: Likewise.
gcc/ada/
* exp_ch9.adb: Mechanically replace "can not" with "cannot".
* libgnat/s-regpat.ads: Likewise.
* par-ch4.adb: Likewise.
* set_targ.adb: Likewise.
* types.ads: Likewise.
gcc/cp/
* cp-tree.h: Mechanically replace "can not" with "cannot".
* parser.c: Likewise.
* pt.c: Likewise.
gcc/fortran/
* class.c: Mechanically replace "can not" with "cannot".
* decl.c: Likewise.
* expr.c: Likewise.
* gfc-internals.texi: Likewise.
* intrinsic.texi: Likewise.
* invoke.texi: Likewise.
* io.c: Likewise.
* match.c: Likewise.
* parse.c: Likewise.
* primary.c: Likewise.
* resolve.c: Likewise.
* symbol.c: Likewise.
* trans-array.c: Likewise.
* trans-decl.c: Likewise.
* trans-intrinsic.c: Likewise.
* trans-stmt.c: Likewise.
gcc/go/
* go-backend.c: Mechanically replace "can not" with "cannot".
* go-gcc.cc: Likewise.
gcc/lto/
* lto-partition.c: Mechanically replace "can not" with "cannot".
* lto-symtab.c: Likewise.
* lto.c: Likewise.
gcc/objc/
* objc-act.c: Mechanically replace "can not" with "cannot".
libbacktrace/
* backtrace.h: Mechanically replace "can not" with "cannot".
libgcc/
* config/c6x/libunwind.S: Mechanically replace "can not" with
"cannot".
* config/tilepro/atomic.h: Likewise.
* config/vxlib-tls.c: Likewise.
* generic-morestack-thread.c: Likewise.
* generic-morestack.c: Likewise.
* mkmap-symver.awk: Likewise.
libgfortran/
* caf/single.c: Mechanically replace "can not" with "cannot".
* io/unit.c: Likewise.
libobjc/
* class.c: Mechanically replace "can not" with "cannot".
* objc/runtime.h: Likewise.
* sendmsg.c: Likewise.
liboffloadmic/
* include/coi/common/COIResult_common.h: Mechanically replace
"can not" with "cannot".
* include/coi/source/COIBuffer_source.h: Likewise.
libstdc++-v3/
* include/ext/bitmap_allocator.h: Mechanically replace "can not"
with "cannot".
Modified:
trunk/contrib/mklog
trunk/gcc/ChangeLog
trunk/gcc/Makefile.in
trunk/gcc/ada/ChangeLog
trunk/gcc/ada/exp_ch9.adb
trunk/gcc/ada/libgnat/s-regpat.ads
trunk/gcc/ada/par-ch4.adb
trunk/gcc/ada/set_targ.adb
trunk/gcc/ada/types.ads
trunk/gcc/alias.c
trunk/gcc/builtins.c
trunk/gcc/calls.c
trunk/gcc/cgraph.c
trunk/gcc/cgraph.h
trunk/gcc/cgraphclones.c
trunk/gcc/cgraphunit.c
trunk/gcc/combine-stack-adj.c
trunk/gcc/combine.c
trunk/gcc/common/config/i386/i386-common.c
trunk/gcc/config/aarch64/aarch64.c
trunk/gcc/config/alpha/sync.md
trunk/gcc/config/arc/arc.c
trunk/gcc/config/arc/predicates.md
trunk/gcc/config/arm/arm-c.c
trunk/gcc/config/arm/arm.c
trunk/gcc/config/arm/arm.h
trunk/gcc/config/arm/arm.md
trunk/gcc/config/arm/cortex-r4f.md
trunk/gcc/config/csky/csky.c
trunk/gcc/config/csky/csky.h
trunk/gcc/config/darwin-f.c
trunk/gcc/config/epiphany/epiphany.md
trunk/gcc/config/i386/i386.c
trunk/gcc/config/i386/sol2.h
trunk/gcc/config/m68k/m68k.c
trunk/gcc/config/mcore/mcore.h
trunk/gcc/config/microblaze/microblaze.md
trunk/gcc/config/mips/20kc.md
trunk/gcc/config/mips/sb1.md
trunk/gcc/config/nds32/nds32.c
trunk/gcc/config/nds32/predicates.md
trunk/gcc/config/pa/pa.c
trunk/gcc/config/rs6000/e300c2c3.md
trunk/gcc/config/rs6000/rs6000.c
trunk/gcc/config/s390/s390.h
trunk/gcc/config/sh/sh.c
trunk/gcc/config/sh/sh.md
trunk/gcc/config/spu/vmx2spu.h
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/parser.c
trunk/gcc/cp/pt.c
trunk/gcc/cprop.c
trunk/gcc/dbxout.c
trunk/gcc/df-scan.c
trunk/gcc/doc/cfg.texi
trunk/gcc/doc/extend.texi
trunk/gcc/doc/fragments.texi
trunk/gcc/doc/gty.texi
trunk/gcc/doc/invoke.texi
trunk/gcc/doc/lto.texi
trunk/gcc/doc/md.texi
trunk/gcc/doc/objc.texi
trunk/gcc/doc/rtl.texi
trunk/gcc/doc/tm.texi
trunk/gcc/dse.c
trunk/gcc/emit-rtl.c
trunk/gcc/emit-rtl.h
trunk/gcc/except.c
trunk/gcc/expmed.c
trunk/gcc/expr.c
trunk/gcc/fold-const.c
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/class.c
trunk/gcc/fortran/decl.c
trunk/gcc/fortran/expr.c
trunk/gcc/fortran/gfc-internals.texi
trunk/gcc/fortran/intrinsic.texi
trunk/gcc/fortran/invoke.texi
trunk/gcc/fortran/io.c
trunk/gcc/fortran/match.c
trunk/gcc/fortran/parse.c
trunk/gcc/fortran/primary.c
trunk/gcc/fortran/resolve.c
trunk/gcc/fortran/symbol.c
trunk/gcc/fortran/trans-array.c
trunk/gcc/fortran/trans-decl.c
trunk/gcc/fortran/trans-intrinsic.c
trunk/gcc/fortran/trans-stmt.c
trunk/gcc/genautomata.c
trunk/gcc/gimple-fold.c
trunk/gcc/go/ChangeLog
trunk/gcc/go/go-backend.c
trunk/gcc/go/go-gcc.cc
trunk/gcc/hard-reg-set.h
trunk/gcc/ifcvt.c
trunk/gcc/ipa-comdats.c
trunk/gcc/ipa-cp.c
trunk/gcc/ipa-devirt.c
trunk/gcc/ipa-fnsummary.c
trunk/gcc/ipa-icf.c
trunk/gcc/ipa-inline-transform.c
trunk/gcc/ipa-inline.c
trunk/gcc/ipa-polymorphic-call.c
trunk/gcc/ipa-profile.c
trunk/gcc/ipa-prop.c
trunk/gcc/ipa-pure-const.c
trunk/gcc/ipa-reference.c
trunk/gcc/ipa-split.c
trunk/gcc/ipa-visibility.c
trunk/gcc/ipa.c
trunk/gcc/ira-build.c
trunk/gcc/ira-color.c
trunk/gcc/ira-conflicts.c
trunk/gcc/ira-costs.c
trunk/gcc/ira-int.h
trunk/gcc/ira-lives.c
trunk/gcc/ira.c
trunk/gcc/ira.h
trunk/gcc/loop-invariant.c
trunk/gcc/loop-unroll.c
trunk/gcc/lower-subreg.c
trunk/gcc/lra-assigns.c
trunk/gcc/lra-constraints.c
trunk/gcc/lra-eliminations.c
trunk/gcc/lra-lives.c
trunk/gcc/lra-remat.c
trunk/gcc/lra-spills.c
trunk/gcc/lra.c
trunk/gcc/lto-cgraph.c
trunk/gcc/lto-streamer-out.c
trunk/gcc/lto/ChangeLog
trunk/gcc/lto/lto-partition.c
trunk/gcc/lto/lto-symtab.c
trunk/gcc/lto/lto.c
trunk/gcc/objc/ChangeLog
trunk/gcc/objc/objc-act.c
trunk/gcc/postreload-gcse.c
trunk/gcc/predict.c
trunk/gcc/profile-count.h
trunk/gcc/profile.c
trunk/gcc/recog.c
trunk/gcc/ree.c
trunk/gcc/reload.c
trunk/gcc/reload1.c
trunk/gcc/reorg.c
trunk/gcc/resource.c
trunk/gcc/rtl.def
trunk/gcc/rtl.h
trunk/gcc/rtlanal.c
trunk/gcc/sched-deps.c
trunk/gcc/sched-ebb.c
trunk/gcc/sched-rgn.c
trunk/gcc/sel-sched-ir.c
trunk/gcc/sel-sched.c
trunk/gcc/shrink-wrap.c
trunk/gcc/simplify-rtx.c
trunk/gcc/symtab.c
trunk/gcc/target.def
trunk/gcc/toplev.c
trunk/gcc/tree-call-cdce.c
trunk/gcc/tree-cfg.c
trunk/gcc/tree-complex.c
trunk/gcc/tree-core.h
trunk/gcc/tree-eh.c
trunk/gcc/tree-inline.c
trunk/gcc/tree-loop-distribution.c
trunk/gcc/tree-nrv.c
trunk/gcc/tree-profile.c
trunk/gcc/tree-sra.c
trunk/gcc/tree-ssa-alias.c
trunk/gcc/tree-ssa-dce.c
trunk/gcc/tree-ssa-dom.c
trunk/gcc/tree-ssa-forwprop.c
trunk/gcc/tree-ssa-loop-im.c
trunk/gcc/tree-ssa-loop-ivcanon.c
trunk/gcc/tree-ssa-loop-ivopts.c
trunk/gcc/tree-ssa-loop-niter.c
trunk/gcc/tree-ssa-phionlycprop.c
trunk/gcc/tree-ssa-phiopt.c
trunk/gcc/tree-ssa-propagate.c
trunk/gcc/tree-ssa-threadedge.c
trunk/gcc/tree-ssa-threadupdate.c
trunk/gcc/tree-ssa-uninit.c
trunk/gcc/tree-ssanames.c
trunk/gcc/tree-streamer-out.c
trunk/gcc/tree.c
trunk/gcc/tree.h
trunk/gcc/vr-values.c
trunk/libbacktrace/ChangeLog
trunk/libbacktrace/backtrace.h
trunk/libgcc/ChangeLog
trunk/libgcc/config/c6x/libunwind.S
trunk/libgcc/config/tilepro/atomic.h
trunk/libgcc/config/vxlib-tls.c
trunk/libgcc/generic-morestack-thread.c
trunk/libgcc/generic-morestack.c
trunk/libgcc/mkmap-symver.awk
trunk/libgfortran/ChangeLog
trunk/libgfortran/caf/single.c
trunk/libgfortran/io/unit.c
trunk/libobjc/ChangeLog
trunk/libobjc/class.c
trunk/libobjc/objc/runtime.h
trunk/libobjc/sendmsg.c
trunk/liboffloadmic/ChangeLog
trunk/liboffloadmic/include/coi/common/COIResult_common.h
trunk/liboffloadmic/include/coi/source/COIBuffer_source.h
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/ext/bitmap_allocator.h
>From gcc-bugs-return-628580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:40:26 2019
Return-Path: <gcc-bugs-return-628580-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50833 invoked by alias); 9 Jan 2019 21:40:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50783 invoked by uid 55); 9 Jan 2019 21:40:21 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16615] throughout gcc docu and code numerous "can not"'s appear
Date: Wed, 09 Jan 2019 21:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 3.4.1
X-Bugzilla-Keywords: documentation, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16615-4-9OtyP5f9zi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01389.txt.bz2
Content-length: 840
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16615
--- Comment #12 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Wed Jan 9 21:39:49 2019
New Revision: 267784
URL: https://gcc.gnu.org/viewcvs?rev=267784&root=gcc&view=rev
Log:
2019-01-09 Sandra Loosemore <sandra@codesourcery.com>
PR other/16615 [2/5]
include/
* libiberty.h: Mechanically replace "can not" with "cannot".
* plugin-api.h: Likewise.
libiberty/
* cp-demangle.c: Mechanically replace "can not" with "cannot".
* floatformat.c: Likewise.
* strerror.c: Likewise.
Modified:
trunk/include/ChangeLog
trunk/include/libiberty.h
trunk/include/plugin-api.h
trunk/libiberty/ChangeLog
trunk/libiberty/cp-demangle.c
trunk/libiberty/floatformat.c
trunk/libiberty/strerror.c
>From gcc-bugs-return-628581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:42:13 2019
Return-Path: <gcc-bugs-return-628581-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53400 invoked by alias); 9 Jan 2019 21:42: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 53364 invoked by uid 55); 9 Jan 2019 21:42:08 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16615] throughout gcc docu and code numerous "can not"'s appear
Date: Wed, 09 Jan 2019 21:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 3.4.1
X-Bugzilla-Keywords: documentation, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16615-4-AlBQjZiv96@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01390.txt.bz2
Content-length: 2796
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16615
--- Comment #13 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Wed Jan 9 21:41:36 2019
New Revision: 267785
URL: https://gcc.gnu.org/viewcvs?rev=267785&root=gcc&view=rev
Log:
2019-01-09 Sandra Loosemore <sandra@codesourcery.com>
PR other/16615 [3/5]
gcc/testsuite/
* g++.dg/lto/odr-1_1.C: Update diagnostic message patterns to replace
"can not" with "cannot".
* gfortran.dg/common_15.f90: Likewise.
* gfortran.dg/derived_result_2.f90: Likewise.
* gfortran.dg/do_check_6.f90: Likewise.
* gfortran.dg/namelist_args.f90: Likewise.
* gfortran.dg/negative_unit_check.f90: Likewise.
* gfortran.dg/pure_formal_3.f90: Likewise.
* obj-c++.dg/attributes/method-attribute-2.mm: Likewise.
* obj-c++.dg/exceptions-3.mm: Likewise.
* obj-c++.dg/exceptions-4.mm: Likewise.
* obj-c++.dg/exceptions-5.mm: Likewise.
* obj-c++.dg/property/at-property-23.mm: Likewise.
* obj-c++.dg/property/dotsyntax-17.mm: Likewise.
* obj-c++.dg/property/property-neg-7.mm: Likewise.
* objc.dg/attributes/method-attribute-2.m: Likewise.
* objc.dg/exceptions-3.m: Likewise.
* objc.dg/exceptions-4.m: Likewise.
* objc.dg/exceptions-5.m: Likewise.
* objc.dg/param-1.m: Likewise.
* objc.dg/property/at-property-23.m: Likewise.
* objc.dg/property/dotsyntax-17.m: Likewise.
* objc.dg/property/property-neg-7.m: Likewise.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/lto/odr-1_1.C
trunk/gcc/testsuite/gfortran.dg/common_15.f90
trunk/gcc/testsuite/gfortran.dg/derived_result_2.f90
trunk/gcc/testsuite/gfortran.dg/do_check_6.f90
trunk/gcc/testsuite/gfortran.dg/namelist_args.f90
trunk/gcc/testsuite/gfortran.dg/negative_unit_check.f90
trunk/gcc/testsuite/gfortran.dg/pure_formal_3.f90
trunk/gcc/testsuite/obj-c++.dg/attributes/method-attribute-2.mm
trunk/gcc/testsuite/obj-c++.dg/exceptions-3.mm
trunk/gcc/testsuite/obj-c++.dg/exceptions-4.mm
trunk/gcc/testsuite/obj-c++.dg/exceptions-5.mm
trunk/gcc/testsuite/obj-c++.dg/property/at-property-23.mm
trunk/gcc/testsuite/obj-c++.dg/property/dotsyntax-17.mm
trunk/gcc/testsuite/obj-c++.dg/property/property-neg-7.mm
trunk/gcc/testsuite/objc.dg/attributes/method-attribute-2.m
trunk/gcc/testsuite/objc.dg/exceptions-3.m
trunk/gcc/testsuite/objc.dg/exceptions-4.m
trunk/gcc/testsuite/objc.dg/exceptions-5.m
trunk/gcc/testsuite/objc.dg/param-1.m
trunk/gcc/testsuite/objc.dg/property/at-property-23.m
trunk/gcc/testsuite/objc.dg/property/dotsyntax-17.m
trunk/gcc/testsuite/objc.dg/property/property-neg-7.m
>From gcc-bugs-return-628582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:46:24 2019
Return-Path: <gcc-bugs-return-628582-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122919 invoked by alias); 9 Jan 2019 21:46:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104940 invoked by uid 55); 9 Jan 2019 21:45:34 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16615] throughout gcc docu and code numerous "can not"'s appear
Date: Wed, 09 Jan 2019 21:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 3.4.1
X-Bugzilla-Keywords: documentation, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16615-4-4fFYXb92FR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01391.txt.bz2
Content-length: 1525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16615
--- Comment #14 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Wed Jan 9 21:44:56 2019
New Revision: 267786
URL: https://gcc.gnu.org/viewcvs?rev=267786&root=gcc&view=rev
Log:
2019-01-09 Sandra Loosemore <sandra@codesourcery.com>
PR other/16615 [4/5]
gcc/
* config/pa/pa.c: Change "can not" to "cannot".
* gimple-ssa-evrp-analyze.c: Likewise.
* ipa-icf.c: Likewise.
* ipa-polymorphic-call.c: Likewise.
* ipa-pure-const.c: Likewise.
* lra-constraints.c: Likewise.
* lra-remat.c: Likewise.
* reload1.c: Likewise.
* reorg.c: Likewise.
* tree-ssa-uninit.c: Likewise.
gcc/ada/
* exp_ch11.adb: Change "can not" to "cannot".
* sem_ch4.adb: Likewise.
gcc/fortran/
* expr.c: Change "can not" to "cannot".
libobjc/
* objc/runtime.h: Change "can not" to "cannot".
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ada/ChangeLog
trunk/gcc/ada/exp_ch11.adb
trunk/gcc/ada/sem_ch4.adb
trunk/gcc/config/pa/pa.c
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/expr.c
trunk/gcc/gimple-ssa-evrp-analyze.c
trunk/gcc/ipa-icf.c
trunk/gcc/ipa-polymorphic-call.c
trunk/gcc/ipa-pure-const.c
trunk/gcc/lra-constraints.c
trunk/gcc/lra-remat.c
trunk/gcc/reload1.c
trunk/gcc/reorg.c
trunk/gcc/tree-ssa-uninit.c
trunk/libobjc/ChangeLog
trunk/libobjc/objc/runtime.h
>From gcc-bugs-return-628583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 21:47:21 2019
Return-Path: <gcc-bugs-return-628583-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124534 invoked by alias); 9 Jan 2019 21:47:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124488 invoked by uid 55); 9 Jan 2019 21:47:17 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16615] throughout gcc docu and code numerous "can not"'s appear
Date: Wed, 09 Jan 2019 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 3.4.1
X-Bugzilla-Keywords: documentation, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-16615-4-ycrvq90Qhf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01392.txt.bz2
Content-length: 443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16615
--- Comment #15 from sandra at gcc dot gnu.org ---
Author: sandra
Date: Wed Jan 9 21:46:45 2019
New Revision: 267787
URL: https://gcc.gnu.org/viewcvs?rev=267787&root=gcc&view=rev
Log:
2019-01-09 Sandra Loosemore <sandra@codesourcery.com>
PR other/16615 [5/5]
gcc/po/
* gcc.pot: Regenerate.
Modified:
trunk/gcc/po/ChangeLog
trunk/gcc/po/gcc.pot
>From gcc-bugs-return-628584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 22:01:36 2019
Return-Path: <gcc-bugs-return-628584-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23060 invoked by alias); 9 Jan 2019 22:01: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 22985 invoked by uid 48); 9 Jan 2019 22:01:31 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Wed, 09 Jan 2019 22:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-q5cmcGDh2Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01393.txt.bz2
Content-length: 426
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Marius: do you have a simple testcase which demonstrates an area where the log
could be improved?
[I'm testing a patch right now which ports things to the dump_* API, and thus
should make the existing dump messages also appear in -fopt-info's output, but
that may well not help for your use-case]
>From gcc-bugs-return-628585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 22:02:35 2019
Return-Path: <gcc-bugs-return-628585-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35149 invoked by alias); 9 Jan 2019 22:02: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 35045 invoked by uid 48); 9 Jan 2019 22:02:22 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Wed, 09 Jan 2019 22:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-B2fObuJD7V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01394.txt.bz2
Content-length: 318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #5 from emsr at gcc dot gnu.org ---
Right. fma is irrelevant.
I will wind up with sqrt(1 + __lo).
I won't hope that max * __scale == 1 here but just add 1. And why waste the
partial sort?
New patch tomorrow a.m. (I guess I'm too late though.)
>From gcc-bugs-return-628586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 22:16:54 2019
Return-Path: <gcc-bugs-return-628586-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64378 invoked by alias); 9 Jan 2019 22:16: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 64299 invoked by uid 48); 9 Jan 2019 22:16:49 -0000
From: "sandra at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/16615] throughout gcc docu and code numerous "can not"'s appear
Date: Wed, 09 Jan 2019 22:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 3.4.1
X-Bugzilla-Keywords: documentation, easyhack
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sandra at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: sandra at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-16615-4-ZbgErTG8pX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
References: <bug-16615-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01395.txt.bz2
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=16615
sandra at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from sandra at gcc dot gnu.org ---
I'm marking this issue as fixed, although there are still instances of "can
not" in files maintained outside the normal GCC process. See the mailing list
discussion for details.
Also, I copied the changes to libiberty/ and include/ to the binutils-gdb copy
of those directories.
>From gcc-bugs-return-628587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 22:34:25 2019
Return-Path: <gcc-bugs-return-628587-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83614 invoked by alias); 9 Jan 2019 22:34:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83558 invoked by uid 48); 9 Jan 2019 22:34:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Wed, 09 Jan 2019 22:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-88775-4-wG3cGUv0zG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01396.txt.bz2
Content-length: 850
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45394
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45394&action=edit
gcc9-pr88775.patch
Just as a first step, with this patch I get much better generated code at -O2,
139 bytes for _Z1fB5cxx11v instead of 259. It helps to have much shorter code
already before inlining and that jump threading etc. don't try to deal with
that. Jon, any value in having the __x < __y etc. for C++11 and C++98 when the
methods aren't marked constexpr?
>From gcc-bugs-return-628588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 22:46:11 2019
Return-Path: <gcc-bugs-return-628588-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94231 invoked by alias); 9 Jan 2019 22:46:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94140 invoked by uid 48); 9 Jan 2019 22:46:06 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Wed, 09 Jan 2019 22:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88450-4-xw6ZwkpObT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01397.txt.bz2
Content-length: 545
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #20 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> Untested patch that does that.
It certainly looks saner than the original version and is in keeping with what
expand_stack_vars does in the same situation (maybe on purpose).
>From gcc-bugs-return-628589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:02:27 2019
Return-Path: <gcc-bugs-return-628589-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109287 invoked by alias); 9 Jan 2019 23:02:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109194 invoked by uid 48); 9 Jan 2019 23:02:21 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 23:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-vwktHgoOYv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01398.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #29 from Jürgen Reuter <juergen.reuter at desy dot de> ---
-rdynamic doesn't change anything, and ld doesn't understand -export-dynamic.
I am a bit confused what to do now, as we have a workaround, i.e. using -static
instead of -static-libtool-libs as libtool flag. But in general, the attempt
for a completely static binary (at least on MACOSX) doesn't work, so maybe we
should retire that feature.
>From gcc-bugs-return-628590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:10:51 2019
Return-Path: <gcc-bugs-return-628590-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122263 invoked by alias); 9 Jan 2019 23:10:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122188 invoked by uid 48); 9 Jan 2019 23:10:46 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] Exception handling configured mode does not match the one finally used
Date: Wed, 09 Jan 2019 23:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88772-4-GrX1jzxkx9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01399.txt.bz2
Content-length: 914
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I just wiped the build to start a clean build from scratch, but I remember
> checking this and it was "no". I can confirm it in ~1 hour
Can you confirm that we're talking about the 32-bit multilib of libgcc here?
Then, if the answer was "no", we need to understand why. The check is simple:
dnl Check if the compiler is configured for setjmp/longjmp exceptions.
AC_DEFUN([GCC_CHECK_SJLJ_EXCEPTIONS],
[AC_CACHE_CHECK([whether the compiler is configured for setjmp/longjmp
exceptions],
ac_cv_sjlj_exceptions,
[AC_COMPILE_IFELSE(
[AC_LANG_PROGRAM(
[[#ifdef __USING_SJLJ_EXCEPTIONS__
this will fail
#endif]],
[[int i;]])],
[ac_cv_sjlj_exceptions=no],
[ac_cv_sjlj_exceptions=yes])])])
Can you run it manually with -m32?
>From gcc-bugs-return-628591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:11:13 2019
Return-Path: <gcc-bugs-return-628591-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123196 invoked by alias); 9 Jan 2019 23:11:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123117 invoked by uid 48); 9 Jan 2019 23:11:09 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 23:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-zo0G03wSHF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01400.txt.bz2
Content-length: 400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #30 from Iain Sandoe <iains at gcc dot gnu.org> ---
well, what I'm trying to achieve is that the exe (with libstdc++ linked in)
provides all the symbols.
it's -Wl,-export_dynamic with an underscore, no a hyphen
you might need to add -Wl,-all_load too (to make sure that all archive members
are included even if they are not used)
>From gcc-bugs-return-628592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:13:23 2019
Return-Path: <gcc-bugs-return-628592-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4047 invoked by alias); 9 Jan 2019 23:13: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 4003 invoked by uid 48); 9 Jan 2019 23:13:18 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Wed, 09 Jan 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-jLMCTf00Ao@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01401.txt.bz2
Content-length: 173
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #31 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Then I get tons of duplicate symbol lines.
>From gcc-bugs-return-628593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:19:18 2019
Return-Path: <gcc-bugs-return-628593-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7768 invoked by alias); 9 Jan 2019 23:19: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 7696 invoked by uid 55); 9 Jan 2019 23:19:14 -0000
From: "dave.anglin at bell dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Wed, 09 Jan 2019 23:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dave.anglin at bell dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88777-4-wYuDCunMmW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01402.txt.bz2
Content-length: 974
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
--- Comment #2 from dave.anglin at bell dot net ---
I also see the same in my last build:
/home/dave/gnu/gcc/objdir/./prev-gcc/xgcc
-B/home/dave/gnu/gcc/objdir/./prev-gcc
/ -B/home/dave/opt/gnu/gcc/gcc-9/hppa-linux-gnu/bin/
-B/home/dave/opt/gnu/gcc/gc
c-9/hppa-linux-gnu/bin/
-B/home/dave/opt/gnu/gcc/gcc-9/hppa-linux-gnu/lib/ -isys
tem /home/dave/opt/gnu/gcc/gcc-9/hppa-linux-gnu/include -isystem
/home/dave/opt/
gnu/gcc/gcc-9/hppa-linux-gnu/sys-include  -fno-checking -c -g -O2
-fno-checking
 -mdisable-indexing -gnatpg -W -Wall -nostdinc -I- -I. -Iada/generated
-Iada -I
../../gcc/gcc/ada -I../../gcc/gcc/ada/gcc-interface -Iada/libgnat
-I../../gcc/gc
c/ada/libgnat ../../gcc/gcc/ada/sem_ch6.adb -o ada/sem_ch6.o
/tmp/ccfmSE1D.s: Assembler messages:
/tmp/ccfmSE1D.s:54721: Error: Field out of range [-8192..8191] (8392).
/tmp/ccfmSE1D.s:55137: Error: Field out of range [-8192..8191] (8224).
>From gcc-bugs-return-628594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:26:34 2019
Return-Path: <gcc-bugs-return-628594-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14103 invoked by alias); 9 Jan 2019 23:26:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14059 invoked by uid 48); 9 Jan 2019 23:26:30 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88779] New: No fix-it hints for misspelled member initializers
Date: Wed, 09 Jan 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88779-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01403.txt.bz2
Content-length: 1696
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88779
Bug ID: 88779
Summary: No fix-it hints for misspelled member initializers
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dmalcolm at gcc dot gnu.org
Target Milestone: ---
Consider:
class test
{
test (int col) : colour (col) {}
int color;
};
Trunk emits:
<source>: In constructor 'test::test(int)':
<source>:3:20: error: class 'test' does not have any field named 'colour'
3 | test (int col) : colour (col) {}
| ^~~~~~
Compiler returned: 1
Ideally we'd also emit a "; did you mean 'color'" and a fix-it hint suggesting
replacement of "colour" with "color".
>From gcc-bugs-return-628595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:26:57 2019
Return-Path: <gcc-bugs-return-628595-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14867 invoked by alias); 9 Jan 2019 23:26: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 14821 invoked by uid 48); 9 Jan 2019 23:26:51 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88779] No fix-it hints for misspelled member initializers
Date: Wed, 09 Jan 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to target_milestone
Message-ID: <bug-88779-4-SWj1hXbxvU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88779-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01404.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88779
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
Target Milestone|--- |10.0
>From gcc-bugs-return-628596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:33:48 2019
Return-Path: <gcc-bugs-return-628596-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19660 invoked by alias); 9 Jan 2019 23:33:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19611 invoked by uid 48); 9 Jan 2019 23:33:42 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88780] New: Wstringop-truncation
Date: Wed, 09 Jan 2019 23:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88780-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01405.txt.bz2
Content-length: 3369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88780
Bug ID: 88780
Summary: Wstringop-truncation
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
In the test case below the assignment suppression logic where we look for the
next statement to see if it assigns a nul to the destination is never entered,
resulting in a false positive. I don't know/remember why it isn't used here,
but using it doesn't seem that it would do the right thing here anyway: it
would find the addition that computes pointer to use for the assignment:
_3 = buf_8(D) + namelen_6;
The logic isn't robust enough to track pointer arithmetic when looking for the
assignment. To avoid the false positive the logic needs to be enhanced to
track the destination across pointer arithmetic.
$ cat u.c && gcc -O2 -S -Wall u.c
typedef __SIZE_TYPE__ size_t;
void f (char *d, const char *s, size_t n)
{
size_t len = __builtin_strlen (s);
if (n < len + 1) return;
__builtin_strncpy (d, s, len);
d[len] = '\0';
}
u.c: In function ‘f’:
u.c:3:6: note: finish_function
3 | void f (char *d, const char *s, size_t n)
| ^
u.c:8:3: warning: ‘__builtin_strncpy’ output truncated before terminating nul
copying as many bytes from a string as its length [-Wstringop-truncation]
8 | __builtin_strncpy (d, s, len);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
u.c:5:16: note: length computed here
5 | size_t len = __builtin_strlen (s);
| ^~~~~~~~~~~~~~~~~~~~
The test case was isolated from the following function:
/* Extract the common name of 'cert' into 'buf'. */
static int get_common_name(CERTCertificate *cert, char *buf, size_t bufsiz)
{
/* FIXME --- truncating names with spaces */
size_t namelen;
char *name = CERT_GetCommonName(&cert->subject);
if (!name) return -1;
namelen = strlen(name);
if (bufsiz < namelen+1) return -1;
strncpy(buf, name, namelen);
buf[namelen] = '\0';
PORT_Free(name);
return 0;
}
and the following warning during a Fedora build with GCC 9:
In file included from /usr/include/string.h:494,
from /usr/include/nss3/secport.h:45,
from /usr/include/nss3/seccomon.h:27,
from /usr/include/nss3/nss.h:34,
from certwatch.c:77:
In function 'strncpy',
inlined from 'get_common_name' at certwatch.c:249:5,
inlined from 'check_cert' at certwatch.c:289:9,
inlined from 'main' at certwatch.c:387:12:
/usr/include/bits/string_fortified.h:106:10: error: '__builtin___strncpy_chk'
output truncated before terminating nul copying as many bytes from a string as
its length [-Werror=stringop-truncation]
106 | return __builtin___strncpy_chk (__dest, __src, __len, __bos
(__dest));
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
certwatch.c: In function 'main':
certwatch.c:246:15: note: length computed here
246 | namelen = strlen(name);
| ^~~~~~~~~~~~
cc1: all warnings being treated as errors
>From gcc-bugs-return-628597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:34:47 2019
Return-Path: <gcc-bugs-return-628597-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21588 invoked by alias); 9 Jan 2019 23:34: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 21514 invoked by uid 48); 9 Jan 2019 23:34:40 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59345] _gfortran_internal_pack on compiler generated temps
Date: Wed, 09 Jan 2019 23: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: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-59345-4-f4jH2Td3Y9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01406.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59345
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I'll look at this one.
>From gcc-bugs-return-628598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:39:39 2019
Return-Path: <gcc-bugs-return-628598-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27484 invoked by alias); 9 Jan 2019 23:39: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 27378 invoked by uid 55); 9 Jan 2019 23:39:35 -0000
From: "ian at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/86343] types built by GO share TYPE_FIELDS in unsupported way
Date: Wed, 09 Jan 2019 23:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86343-4-XqMZXqcJ6A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86343-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86343-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01407.txt.bz2
Content-length: 528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86343
--- Comment #3 from ian at gcc dot gnu.org <ian at gcc dot gnu.org> ---
Author: ian
Date: Wed Jan 9 23:38:55 2019
New Revision: 267789
URL: https://gcc.gnu.org/viewcvs?rev=267789&root=gcc&view=rev
Log:
PR go/86343
* go-gcc.cc (Gcc_backend::set_placeholder_struct_type): Go back to
build_distinct_type_copy, but copy the fields so that they have
the right DECL_CONTEXT.
Modified:
trunk/gcc/go/ChangeLog
trunk/gcc/go/go-gcc.cc
>From gcc-bugs-return-628599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:41:36 2019
Return-Path: <gcc-bugs-return-628599-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30155 invoked by alias); 9 Jan 2019 23:41:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29553 invoked by uid 48); 9 Jan 2019 23:41:31 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88781] New: [meta-bug] bogus/missing -Wstringop-truncation warnings
Date: Wed, 09 Jan 2019 23:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88781-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01408.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88781
Bug ID: 88781
Summary: [meta-bug] bogus/missing -Wstringop-truncation
warnings
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
This is a meta-bug to track false positives and negatives in the
-Wstringop-overflow warning, or other improvements to the implementation of the
warning code.
>From gcc-bugs-return-628600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 09 23:46:19 2019
Return-Path: <gcc-bugs-return-628600-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38215 invoked by alias); 9 Jan 2019 23:46: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 38092 invoked by uid 48); 9 Jan 2019 23:46:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88781] [meta-bug] bogus/missing -Wstringop-truncation warnings
Date: Wed, 09 Jan 2019 23:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on dependson everconfirmed
Message-ID: <bug-88781-4-YLeKIltMf1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88781-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88781-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01409.txt.bz2
Content-length: 3826
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88781
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-09
Depends on| |88780, 87383, 86764, 85902,
| |85650, 84732, 84624, 84561,
| |84398, 84397, 84396, 84395,
| |82944, 87028, 85728, 85700,
| |85643, 84649, 84480, 84474,
| |84468, 84228
Ever confirmed|0 |1
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82944
[Bug 82944] missing -Wstringop-truncation on strncpy due to system header macro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84228
[Bug 84228] Bogus -Wstringop-truncation warning with -g
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84395
[Bug 84395] -Wstringop-truncation where -Wstringop-overflow is expected
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84396
[Bug 84396] missing -Wstringop-truncation with non-nul assignment to
destination
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84397
[Bug 84397] missing -Wstringop-truncation on strncpy into a multidimensional
array
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84398
[Bug 84398] missing -Wstringop-truncation on strncpy into VLA and dynamically
allocated arrays
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84468
[Bug 84468] [8 Regression] bogus -Wstringop-truncation despite assignment after
conditional strncpy
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84474
[Bug 84474] Unexpected -Wstringop-truncation on strncpy with string literal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84480
[Bug 84480] [8 Regression] bogus -Wstringop-truncation despite assignment with
an inlined string literal
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84561
[Bug 84561] -Wstringop-truncation with -O2 depends on strncpy's size type
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84624
[Bug 84624] bogus -Wstringop-truncation in a catch statement and nul assignment
outside it
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84649
[Bug 84649] -Wstringop-truncation shouldn't warn on strncat() when 2nd argument
is a char array
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84732
[Bug 84732] false-positive -Wstringop-truncation warning with
-fsanitize-coverage=trace-pc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
[Bug 85643] attribute nonstring fails to squash -Wstringop-truncation warning
at an offset
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85650
[Bug 85650] Additional warnings when -fsanitize=undefined is used with
-Wstringop-truncation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85700
[Bug 85700] Spurious -Wstringop-truncation warning with strncat
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85728
[Bug 85728] strncpy -Wstringop-truncation
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85902
[Bug 85902] -Wstringop-truncation false-positive
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86764
[Bug 86764] missing -Wstringop-truncation writing to the last array member
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87028
[Bug 87028] false positive -Wstringop-truncation strncpy with global variable
source string
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87383
[Bug 87383] improve text and detail in -Wstringop-truncation warnings
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88780
[Bug 88780] bogus -Wstringop-truncation for copying as many bytes from a string
as its length
>From gcc-bugs-return-628601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 00:08:48 2019
Return-Path: <gcc-bugs-return-628601-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86668 invoked by alias); 10 Jan 2019 00:08:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86634 invoked by uid 48); 10 Jan 2019 00:08:44 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Thu, 10 Jan 2019 00:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-Qaix6KtkcF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01410.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #32 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #31)
> Then I get tons of duplicate symbol lines.
ah well, not so simple then,
then I think the next step is for you to identify the last working revision of
the compiler - we can then analyse what the change was that caused the
difference and determine if that's a real regression or just exposing a build
system issue.
>From gcc-bugs-return-628602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 00:33:12 2019
Return-Path: <gcc-bugs-return-628602-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23730 invoked by alias); 10 Jan 2019 00:33:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23635 invoked by uid 48); 10 Jan 2019 00:33:06 -0000
From: "romain.geissler at amadeus dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] New: Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc >= 8.3
Date: Thu, 10 Jan 2019 00:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: romain.geissler at amadeus dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01411.txt.bz2
Content-length: 6105
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88782
Bug ID: 88782
Summary: Crash when mixing make_shared from gcc <= 8.2 with
make_shared from gcc >= 8.3
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: romain.geissler at amadeus dot com
Target Milestone: ---
Hi,
The change introduced in r266380 makes newer gcc >= 8.3 and gcc 9 sometimes
incompatible with object files (archive libraries) generated with gcc <= 8.2,
even when all the generated objects are using -frtti.
See this example where mixing an old library build with an old gcc 8 and a new
library build with a new gcc 8 result in the end in a segfault:
cat > A.h <<END_OF_FILE
class A
{
public:
class Constructor1 {};
class Constructor2 {};
A(A::Constructor1) {};
A(A::Constructor2) {};
};
END_OF_FILE
cat > library1.cpp <<END_OF_FILE
#include "A.h"
#include <memory>
void f1()
{
std::make_shared<A>(A::Constructor1());
}
END_OF_FILE
cat > library2.cpp <<END_OF_FILE
#include "A.h"
#include <memory>
void f2()
{
std::make_shared<A>(A::Constructor2());
}
END_OF_FILE
cat > main.cpp <<END_OF_FILE
#include <memory>
extern void f1();
extern void f2();
int main()
{
f1();
f2();
}
END_OF_FILE
### Built like this: ###
old-g++-8 -g -o library1.o -c library1.cpp
ar cr library1.a library1.o
new-g++-8 -g -o library2.o -c library2.cpp
ar cr library2.a library2.o
new-g++-8 -g -o main.o -c main.cpp
new-g++-8 -o main main.o library1.a library2.a
(in my case, old-g++-8 is actually named
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.40/bin/g++ and
new-g++-8 is actually named
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.46/bin/g++)
### When you run it (with gdb): ###
(gdb) r
Starting program: /tmp/reproduce-gcc-make-shared/main
Program received signal SIGSEGV, Segmentation fault.
0x00000000004011bd in std::type_info::operator== (this=0x403200
<std::_Sp_make_shared_tag::_S_ti()::__tag>, __arg=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.40/include/c++/8.2.1/typeinfo:123
123 || (__name[0] != '*' &&
(gdb) bt
#0 0x00000000004011bd in std::type_info::operator== (this=0x403200
<std::_Sp_make_shared_tag::_S_ti()::__tag>, __arg=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.40/include/c++/8.2.1/typeinfo:123
#1 0x0000000000401d6f in std::_Sp_counted_ptr_inplace<A, std::allocator<A>,
(__gnu_cxx::_Lock_policy)2>::_M_get_deleter (this=0x418c20, __ti=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.40/include/c++/8.2.1/bits/shared_ptr_base.h:569
#2 0x000000000040176e in
std::__shared_count<(__gnu_cxx::_Lock_policy)2>::_M_get_deleter
(this=0x7fffffffc4e8, __ti=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.40/include/c++/8.2.1/bits/shared_ptr_base.h:749
#3 0x0000000000401f8c in std::__shared_ptr<A,
(__gnu_cxx::_Lock_policy)2>::__shared_ptr<std::allocator<A>, A::Constructor2>
(this=0x7fffffffc4e0, __tag=..., __a=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.46/include/c++/8.2.1/bits/shared_ptr_base.h:1328
#4 0x0000000000401f1d in std::shared_ptr<A>::shared_ptr<std::allocator<A>,
A::Constructor2> (this=0x7fffffffc4e0, __tag=..., __a=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.46/include/c++/8.2.1/bits/shared_ptr.h:360
#5 0x0000000000401ee0 in std::allocate_shared<A, std::allocator<A>,
A::Constructor2> (__a=..., __args#0=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.46/include/c++/8.2.1/bits/shared_ptr.h:707
#6 0x0000000000401e68 in std::make_shared<A, A::Constructor2> (__args#0=...)
at
/remote/tools/Linux/2.6/1A/toolchain/x86_64-2.6.32-v4.0.46/include/c++/8.2.1/bits/shared_ptr.h:723
#7 0x0000000000401e00 in f2 () at library2.cpp:6
#8 0x0000000000401152 in main () at main.cpp:9
The reason for that is that the symbols and the vtable for the class
std::_Sp_counted_ptr_inplace comes from the first object that defines it, which
in this case is library1 built with the old gcc behavior. This class is common
both when you call make_shared with constructor 1 or constructor 2, and this is
where _M_get_deleter does it's check for the typeid(_Sp_make_shared_tag).
On the other side, there are two different callers of _M_get_deleter. One with
the old typeid(__tag) tag in the library 1 (when instantiating the call to
constructor 1) and one with the new _Sp_make_shared_tag::_S_ti() tag in the
library 2 (when instantiating the call to constructor 2). Because the linker
picked the "wrong" old _M_get_deleter, the second call ends it in seg fault.
Do we foresee a way to avoid rebuilding all libraries that were built with gcc
<= 8.2 when mixing them with libraries build with gcc >= 8.3 ? I am thinking
about doing something like this:
--- bits/shared_ptr_base.h
+++ bits/shared_ptr_base.h
@@ -509,8 +509,12 @@
static const type_info&
_S_ti() noexcept _GLIBCXX_VISIBILITY(default)
{
+#if __cpp_rtti
+ return typeid(_Sp_make_shared_tag);
+#else
alignas(type_info) static constexpr char __tag[sizeof(type_info)] = { };
return reinterpret_cast<const type_info&>(__tag);
+#endif
}
};
@@ -567,12 +571,6 @@
// as a real type_info object.
if (&__ti == &_Sp_make_shared_tag::_S_ti())
return const_cast<typename remove_cv<_Tp>::type*>(_M_ptr());
-#if __cpp_rtti
- // Callers compiled with old libstdc++ headers and RTTI enabled
- // might pass this instead:
- else if (__ti == typeid(_Sp_make_shared_tag))
- return const_cast<typename remove_cv<_Tp>::type*>(_M_ptr());
-#endif
return nullptr;
}
but that may be quite wrong too (I can just confirm it works on my reduced test
case).
Cheers,
Romain
>From gcc-bugs-return-628603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 00:54:36 2019
Return-Path: <gcc-bugs-return-628603-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109005 invoked by alias); 10 Jan 2019 00:54: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 104519 invoked by uid 48); 10 Jan 2019 00:54:31 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] ICE in reference_record with data statement
Date: Thu, 10 Jan 2019 00:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work assigned_to
Message-ID: <bug-86322-4-SW5P3yjh0b@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01412.txt.bz2
Content-length: 453
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work|8.1.0 |
Assignee|unassigned at gcc dot gnu.org |kargl at gcc dot gnu.org
--- Comment #6 from kargl at gcc dot gnu.org ---
Remove 'Known to work" as this has never worked.
>From gcc-bugs-return-628604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 01:02:29 2019
Return-Path: <gcc-bugs-return-628604-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67531 invoked by alias); 10 Jan 2019 01:02:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67428 invoked by uid 48); 10 Jan 2019 01:02:25 -0000
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Thu, 10 Jan 2019 01:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amodra at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88777-4-mSxGVAr76d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01413.txt.bz2
Content-length: 819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
Alan Modra <amodra at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC|amodra at gcc dot gnu.org |
Assignee|unassigned at gcc dot gnu.org |amodra at gmail dot com
--- Comment #3 from Alan Modra <amodra at gmail dot com> ---
The generated insn-attrtab.c insn_min_length differs after r267666, with a
bunch of insns returning INT_MAX. Prior to my patch,
genattrtab.c:min_attr_value returned the min value of those it could calculate,
rather than returning an "i can't calculate" status of INT_MAX. I'm guessing
that is the change that broke hppa.
>From gcc-bugs-return-628605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 01:12:28 2019
Return-Path: <gcc-bugs-return-628605-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81210 invoked by alias); 10 Jan 2019 01:12: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 81122 invoked by uid 55); 10 Jan 2019 01:12:23 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88376] [7/8/9 Regression] ICE in is_illegal_recursion, at fortran/resolve.c:1689
Date: Thu, 10 Jan 2019 01:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88376-4-3d7JRJ4RM9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01414.txt.bz2
Content-length: 667
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88376
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu Jan 10 01:11:51 2019
New Revision: 267793
URL: https://gcc.gnu.org/viewcvs?rev=267793&root=gcc&view=rev
Log:
2019-01-09 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/88376
* resolve.c (is_illegal_recursion): Remove an assert().
2019-01-09 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/88376
* gfortran.dg/pr88376.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr88376.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 01:14:23 2019
Return-Path: <gcc-bugs-return-628606-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85027 invoked by alias); 10 Jan 2019 01:14: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 84943 invoked by uid 48); 10 Jan 2019 01:14:18 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88376] [7/8/9 Regression] ICE in is_illegal_recursion, at fortran/resolve.c:1689
Date: Thu, 10 Jan 2019 01:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88376-4-d07sNXK8sN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88376-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01415.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88376
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from kargl at gcc dot gnu.org ---
Fixed on trunk. Closing.
>From gcc-bugs-return-628607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 01:56:22 2019
Return-Path: <gcc-bugs-return-628607-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38916 invoked by alias); 10 Jan 2019 01:56:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38415 invoked by uid 48); 10 Jan 2019 01:56:15 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 01:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-vi3FW0SlK9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01416.txt.bz2
Content-length: 228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Candidate patch for porting to the dump_* API:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00512.html
>From gcc-bugs-return-628608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 02:18:32 2019
Return-Path: <gcc-bugs-return-628608-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10998 invoked by alias); 10 Jan 2019 02: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 8771 invoked by uid 48); 10 Jan 2019 02:18:28 -0000
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Thu, 10 Jan 2019 02:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amodra at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88777-4-wrKrquYMF1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01417.txt.bz2
Content-length: 340
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
--- Comment #4 from Alan Modra <amodra at gmail dot com> ---
Created attachment 45395
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45395&action=edit
fix
This patch results in exactly the same gcc/insn-*.[ch] on hppa-linux as
reverting r267666, and identical test-tgmath2.s
>From gcc-bugs-return-628609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 03:14:07 2019
Return-Path: <gcc-bugs-return-628609-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125062 invoked by alias); 10 Jan 2019 03: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 121539 invoked by uid 48); 10 Jan 2019 03:14:01 -0000
From: "helijia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88767] 'unroll and jam' not optimizing some loops
Date: Thu, 10 Jan 2019 03:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: helijia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88767-4-YGhiw7lzPo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88767-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01418.txt.bz2
Content-length: 2180
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88767
Li Jia He <helijia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amker at gcc dot gnu.org
--- Comment #9 from Li Jia He <helijia at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> What's the room for improvement? Why's unrolling the innermost loop not
> profitable?
Hi Richard, I want to achieve the effect of the following code:
__attribute__((noinline)) void calculate(const double* __restrict__ A, const
double* __restrict__ B, double* __restrict__ C) {
unsigned int l_m = 0;
unsigned int l_n = 0;
unsigned int l_k = 0;
A = (const double*)__builtin_assume_aligned(A,16);
B = (const double*)__builtin_assume_aligned(B,16);
C = (double*)__builtin_assume_aligned(C,16);
for ( l_n = 0; l_n < 9; l_n += 3 ) { // loop 1
for ( l_m = 0; l_m < 10; l_m++ ) { // loop 2
C[(l_n*10)+l_m] = 0.0;
C[(l_n*10)+l_m+10] = 0.0;
C[(l_n*10)+l_m+20] = 0.0;
}
for ( l_k = 0; l_k < 17; l_k++ ) { // loop 3
for ( l_m = 0; l_m < 10; l_m++ ) { // loop 4
C[(l_n*10)+l_m] += A[(l_k*20)+l_m] * B[(l_n*20)+l_k];
C[(l_n*10)+l_m+10] += A[(l_k*20)+l_m] * B[(l_n*20)+l_k+20];
C[(l_n*10)+l_m+20] += A[(l_k*20)+l_m] * B[(l_n*20)+l_k+40];
}
}
}
}
#define SIZE 36
double A[SIZE][SIZE] __attribute__((aligned(16)));
double B[SIZE][SIZE] __attribute__((aligned(16)));
double C[SIZE][SIZE] __attribute__((aligned(16)));
int main()
{
long r, i, j;
for (i=0; i < SIZE; i++) {
for (j=0; j < SIZE; j++) {
A[i][j] = 1.0;
B[i][j] = 2.0;
C[i][j] = 3.0;
}
}
for (r=0; r < 1000000; r++) {
calculate(&A[0][0],&B[0][0], &C[0][0]);
}
return 0;
}
In the original code, cunrolli pass will completely expand loop2 and loop4,
causing unroll-and-jam to have no chance to do it. From my test, the
performance
of these codes is expectation code > enable cunrolli > disable cunrolli.
Sorry for not responding in time.
>From gcc-bugs-return-628610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 03:48:48 2019
Return-Path: <gcc-bugs-return-628610-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109798 invoked by alias); 10 Jan 2019 03:48: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 105784 invoked by uid 48); 10 Jan 2019 03:48:04 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53215] Warn if orphaned memory is created by ignoring return value of new
Date: Thu, 10 Jan 2019 03: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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-53215-4-EGcVX3HFhx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53215-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01419.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53215
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
>
> We could probably teach the compiler to warn about unused results of
> anything with attribute__((malloc))
That would probably be a good thing to do anyways, given that the GNU Coding
Standards say to always check the result of malloc:
https://www.gnu.org/prep/standards/html_node/Semantics.html#Semantics
>From gcc-bugs-return-628611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 03:50:16 2019
Return-Path: <gcc-bugs-return-628611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111943 invoked by alias); 10 Jan 2019 03: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 111799 invoked by uid 48); 10 Jan 2019 03:50:12 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/50229] [7/8/9 Regression] Can't cross compile for i686-apple-darwin10 from x86_64-redhat_linux
Date: Thu, 10 Jan 2019 03:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-50229-4-0zt2bIohfr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01420.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50229
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|6.4 |7.4
--- Comment #31 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #30)
> Changing milestone since gcc-5-branch has been closed.
...and again now that gcc-6-branch has been closed.
>From gcc-bugs-return-628612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 03:52:25 2019
Return-Path: <gcc-bugs-return-628612-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114704 invoked by alias); 10 Jan 2019 03:52:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114668 invoked by uid 48); 10 Jan 2019 03:52:20 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/81452] warn on realloc(p, 0)
Date: Thu, 10 Jan 2019 03:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81452-4-doPRw6wjH1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81452-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81452-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01421.txt.bz2
Content-length: 171
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81452
--- Comment #2 from Eric Gallager <egallager at gcc dot gnu.org> ---
any ideas for a name for this proposed warning?
>From gcc-bugs-return-628613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 05:04:11 2019
Return-Path: <gcc-bugs-return-628613-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15919 invoked by alias); 10 Jan 2019 05:04: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 15725 invoked by uid 48); 10 Jan 2019 05:04:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/81452] warn on realloc(p, 0)
Date: Thu, 10 Jan 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: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81452-4-HUyeY2u9nK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81452-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81452-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01422.txt.bz2
Content-length: 209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81452
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
There is -Walloc-zero. If we want a separate knob for just it then maybe
-Wrealloc-zero.
>From gcc-bugs-return-628614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 06:12:47 2019
Return-Path: <gcc-bugs-return-628614-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124222 invoked by alias); 10 Jan 2019 06:12: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 124161 invoked by uid 48); 10 Jan 2019 06:12:41 -0000
From: "tfx_sec at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88783] New: integer overflow in libiberty, heap overflow will be triggered
Date: Thu, 10 Jan 2019 06:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tfx_sec at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01423.txt.bz2
Content-length: 4625
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88783
Bug ID: 88783
Summary: integer overflow in libiberty, heap overflow will be
triggered
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: tfx_sec at hotmail dot com
Target Milestone: ---
Created attachment 45396
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45396&action=edit
nm -C POC
nm -C POC
I use 32bit binutils in 64bit Ubuntu 16.04.4 LTS.
The trigger command is ./nm -C POC
The source Code show as follow in cplus-dem.c
>2246 work->tmpl_argvec = XNEWVEC (char *, r); //sizeof(char*) * r
>2247 work->ntmpl_args = r;
>2248 for (i = 0; i < r; i++)
>2249 work->tmpl_argvec[i] = 0;
Integer overflow when r > 0x40000000 in line 2246, that will trigger heap
overflow in in line 2249.
There are several similar problems in libiberty.
The part of crash output show as follow.
=================================================================
==9029==ERROR: AddressSanitizer: heap-buffer-overflow on address 0xf3bfea80 at
pc 0x083ba887 bp 0xffabcac8 sp 0xffabcac0
WRITE of size 4 at 0xf3bfea80 thread T0
#0 0x83ba886 in demangle_template
./binutils-gdb/libiberty/./cplus-dem.c:2249:23
#1 0x83b8c2e in demangle_signature
./binutils-gdb/libiberty/./cplus-dem.c:1709:18
#2 0x83b62da in internal_cplus_demangle
./binutils-gdb/libiberty/./cplus-dem.c:1258:14
#3 0x83b5143 in cplus_demangle ./binutils-gdb/libiberty/./cplus-dem.c:919:9
#4 0x815d092 in bfd_demangle ./binutils-gdb/bfd/bfd.c:2254:9
#5 0x81460a0 in print_symname ./binutils-gdb/binutils/nm.c:423:19
#6 0x8145035 in print_symbol_info_bsd ./binutils-gdb/binutils/nm.c:1565:3
#7 0x8149d87 in print_symbol ./binutils-gdb/binutils/nm.c:903:3
#8 0x8148828 in print_symbols ./binutils-gdb/binutils/nm.c:1102:7
#9 0x8146fdb in display_rel_file ./binutils-gdb/binutils/nm.c:1215:5
#10 0x8144a11 in display_file ./binutils-gdb/binutils/nm.c:1335:7
#11 0x814424f in main ./binutils-gdb/binutils/nm.c:1816:12
#12 0xf7d3f636 in __libc_start_main (/lib/i386-linux-gnu/libc.so.6+0x18636)
#13 0x806be08 in _start (./binutils-gdb/binutils/nm-new+0x806be08)
0xf3bfea80 is located 0 bytes to the right of 251581056-byte region
[0xe4c11800,0xf3bfea80)
allocated by thread T0 here:
#0 0x8112215 in malloc asan_malloc_linux.cc:146:3
#1 0x83e6659 in xmalloc ./binutils-gdb/libiberty/./xmalloc.c:147:12
#2 0x83b8c2e in demangle_signature
./binutils-gdb/libiberty/./cplus-dem.c:1709:18
#3 0x83b62da in internal_cplus_demangle
./binutils-gdb/libiberty/./cplus-dem.c:1258:14
#4 0x83b5143 in cplus_demangle ./binutils-gdb/libiberty/./cplus-dem.c:919:9
#5 0x815d092 in bfd_demangle ./binutils-gdb/bfd/bfd.c:2254:9
SUMMARY: AddressSanitizer: heap-buffer-overflow
./binutils-gdb/libiberty/./cplus-dem.c:2249:23 in demangle_template
Shadow bytes around the buggy address:
0x3e77fd00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x3e77fd10: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x3e77fd20: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x3e77fd30: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
0x3e77fd40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
=>0x3e77fd50:[fa]fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e77fd60: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e77fd70: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e77fd80: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e77fd90: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
0x3e77fda0: fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa fa
Shadow byte legend (one shadow byte represents 8 application bytes):
Addressable: 00
Partially addressable: 01 02 03 04 05 06 07
Heap left redzone: fa
Freed heap region: fd
Stack left redzone: f1
Stack mid redzone: f2
Stack right redzone: f3
Stack after return: f5
Stack use after scope: f8
Global redzone: f9
Global init order: f6
Poisoned by user: f7
Container overflow: fc
Array cookie: ac
Intra object redzone: bb
ASan internal: fe
Left alloca redzone: ca
Right alloca redzone: cb
Shadow gap: cc
==9029==ABORTING
>From gcc-bugs-return-628615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 06:21:48 2019
Return-Path: <gcc-bugs-return-628615-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83740 invoked by alias); 10 Jan 2019 06:21:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77182 invoked by uid 48); 10 Jan 2019 06:21:42 -0000
From: "tfx_sec at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88783] integer overflow in libiberty, heap overflow will be triggered
Date: Thu, 10 Jan 2019 06:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tfx_sec at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88783-4-lHy7tbvVt6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01424.txt.bz2
Content-length: 134
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88783
--- Comment #1 from tfx <tfx_sec at hotmail dot com> ---
I use latest binutils.
>From gcc-bugs-return-628616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 06:41:55 2019
Return-Path: <gcc-bugs-return-628616-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51049 invoked by alias); 10 Jan 2019 06:41: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 51004 invoked by uid 48); 10 Jan 2019 06:41:51 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Thu, 10 Jan 2019 06:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-9dgcqED0JU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01425.txt.bz2
Content-length: 624
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #33 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Iain Sandoe from comment #32)
> (In reply to Jürgen Reuter from comment #31)
> > Then I get tons of duplicate symbol lines.
>
> ah well, not so simple then,
>
> then I think the next step is for you to identify the last working revision
> of the compiler - we can then analyse what the change was that caused the
> difference and determine if that's a real regression or just exposing a
> build system issue.
I fear I don't have the capacities to do that right now.
>From gcc-bugs-return-628617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 06:44:10 2019
Return-Path: <gcc-bugs-return-628617-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54925 invoked by alias); 10 Jan 2019 06:44:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54902 invoked by uid 48); 10 Jan 2019 06:44:05 -0000
From: "helijia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88784] New: Middle end is missing some optimizations about unsigned
Date: Thu, 10 Jan 2019 06:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: helijia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01426.txt.bz2
Content-length: 952
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88784
Bug ID: 88784
Summary: Middle end is missing some optimizations about
unsigned
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: helijia at gcc dot gnu.org
Target Milestone: ---
For both operands are unsigned, the following optimizations are valid, and
missing:
1. X > Y && X != 0 --> X > Y
2. X > Y || X != 0 --> X != 0
3. X <= Y || X != 0 --> true
4. X <= Y || X == 0 --> X <= Y
5. X > Y && X == 0 --> false
unsigned foo(unsigned x, unsigned y) { return x > y && x != 0; }
should fold to x > y, but I found we haven't done it right now.
I compile the code with the following command.
g++ unsigned.cpp -Ofast -c -S -o unsigned.s -fdump-tree-all
>From gcc-bugs-return-628618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 07:01:26 2019
Return-Path: <gcc-bugs-return-628618-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102480 invoked by alias); 10 Jan 2019 07:01:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101628 invoked by uid 48); 10 Jan 2019 07:00:25 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 07:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-i6z73WwcHy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01427.txt.bz2
Content-length: 2056
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #7 from Marius Messerschmidt <marius.messerschmidt at googlemail dot com> ---
Thanks a lot for working on this!
A simple example would be the following:
-------------- CODE -------------------
int calc(int x, int y, int *flag)
{
if(flag > 5)
return x + y;
else
return x * y;
*flag += 2; // BAD LINE
}
int main(int argc, char **argv)
{
int flag = argc;
int array[250*250];
for(int i = 0; i < 250; i++)
{
for(int j = 0; j < 250
array[i*250 + j] = calc(i, j, &flag);
}
return array[42 + argc];
}
---------------------------------------
The line marked with "BAD LINE" is obviously preventing the unswitching as the
loop condition is no longer constant during the loop. If you uncomment the line
gcc reports ";; unswitched loop" which is great. But if you keep the line, you
get no output at all. The minimal output I would expect is:
";; not unswitching loop: REASON"
so in this case:
";; not unswitching loop: Condition is not invariant"
To further improve the output it would be great if there would be some more
information about the loop, but I do not know which information is available
during this stage. The most helpful additional information would be (also
applies for the successful message):
- File
- Function
- Line number of the loop head (or some other way to identify the loop, e.g.
loop number XY)
- Line number of the if-statement that should be unswitched out of the loop
- Line number of the issue that caused the loop unswitching to stop so in the
example above the commented line.
So I think the perfect log message would be something like this:
";; unswitching loop: testFile.c:82 (Condition: otherFile.c:502)"
";; not unswitching loop: testFile.c:91: Condition (otherFile.c:541) is not
invariant (modified at otherFile.c:32)"
But as I said above I do not know how many information about the original
source file is still available during this stage.
>From gcc-bugs-return-628619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 07:05:18 2019
Return-Path: <gcc-bugs-return-628619-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116191 invoked by alias); 10 Jan 2019 07:05: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 116119 invoked by uid 48); 10 Jan 2019 07:05:14 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 07:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-Pqjz6fLwyu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01428.txt.bz2
Content-length: 271
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #8 from Marius Messerschmidt <marius.messerschmidt at googlemail dot com> ---
Oh minor error from my side, the "BAD LINE" should of course be above the
if/return block otherwise it would work just fine.
>From gcc-bugs-return-628620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 07:08:53 2019
Return-Path: <gcc-bugs-return-628620-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119306 invoked by alias); 10 Jan 2019 07:08: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 119274 invoked by uid 48); 10 Jan 2019 07:08:48 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 07: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88763-4-VW8pXQkCr0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01429.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #9 from Marius Messerschmidt <marius.messerschmidt at googlemail dot com> ---
Created attachment 45397
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45397&action=edit
Basic testcase
As there where some more issues in the example I provided, I added it as an
attachment. Now it should work just fine.
>From gcc-bugs-return-628621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 07:36:51 2019
Return-Path: <gcc-bugs-return-628621-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51151 invoked by alias); 10 Jan 2019 07:36:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50925 invoked by uid 48); 10 Jan 2019 07:36:47 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex value load
Date: Thu, 10 Jan 2019 07:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-29CfLbA00x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01430.txt.bz2
Content-length: 209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
This is due to nonexistent SCmode patterns. I guess that movsc pattern is
needed here.
>From gcc-bugs-return-628622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 07:46:20 2019
Return-Path: <gcc-bugs-return-628622-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85316 invoked by alias); 10 Jan 2019 07:46:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85278 invoked by uid 48); 10 Jan 2019 07:46:15 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88785] New: ICE in as_a, at machmode.h:353
Date: Thu, 10 Jan 2019 07:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01431.txt.bz2
Content-length: 2133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
Bug ID: 88785
Summary: ICE in as_a, at machmode.h:353
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Created attachment 45398
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45398&action=edit
reduced test case
Compile the attached test case with `-g -O2 -std=gnu++17 -march=skylake-avx512
-c`:
during RTL pass: final
ice.cpp: In function ‘void dg() [with dc = a::b<long int>]’:
ice.cpp:192:1: internal compiler error: in as_a, at machmode.h:353
192 | }
| ^
0x6d31e4 scalar_float_mode as_a<scalar_float_mode>(machine_mode)
../../gcc/machmode.h:353
0x6d31e4 insert_float
../../gcc/dwarf2out.c:19456
0xbbc38e add_const_value_attribute
../../gcc/dwarf2out.c:19548
0xbbd9a3 add_location_or_const_value_attribute
../../gcc/dwarf2out.c:20106
0xbbd9a3 add_location_or_const_value_attribute
../../gcc/dwarf2out.c:20060
0xbd000a gen_variable_die
../../gcc/dwarf2out.c:23880
0xbc4348 gen_decl_die
../../gcc/dwarf2out.c:26371
0xbc14cf decls_for_scope
../../gcc/dwarf2out.c:25858
0xbddff6 gen_inlined_subroutine_die
../../gcc/dwarf2out.c:24219
0xbddff6 gen_block_die
../../gcc/dwarf2out.c:25762
0xbc158a decls_for_scope
../../gcc/dwarf2out.c:25887
0xbddff6 gen_inlined_subroutine_die
../../gcc/dwarf2out.c:24219
0xbddff6 gen_block_die
../../gcc/dwarf2out.c:25762
0xbc158a decls_for_scope
../../gcc/dwarf2out.c:25887
0xbc252f gen_subprogram_die
../../gcc/dwarf2out.c:23328
0xbc3f9c gen_decl_die
../../gcc/dwarf2out.c:26288
0xbc4b3e dwarf2out_decl
../../gcc/dwarf2out.c:26856
0xbc4fbe dwarf2out_function_decl
../../gcc/dwarf2out.c:26871
0xc390bc rest_of_handle_final
../../gcc/final.c:4695
0xc390bc execute
../../gcc/final.c:4737
>From gcc-bugs-return-628623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 07:53:25 2019
Return-Path: <gcc-bugs-return-628623-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30534 invoked by alias); 10 Jan 2019 07:53:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30417 invoked by uid 48); 10 Jan 2019 07:53:18 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Thu, 10 Jan 2019 07:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88771-4-LsR7tWQY2x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01432.txt.bz2
Content-length: 1368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #4)
> The warning is triggered by the excessive size argument in the strncpy call.
> The excessive size makes the call invalid regardless of the values of the
> two pointer arguments.
>
> This happens both with the reduced test case in comment #0 and with the
> translation unit and -m32. The warning code just looks at the call:
>
> __builtin_strncpy (_65, buf_30, 4294967295);
>
> I don't see much the warning code alone can do to handle this case. We have
> talked about at least two approaches to dealing these invalid calls earlier.
I see.
> Jeff's preference is to replace them with traps. Others have suggested
> replacing them with __builtin_unreachable().
Btw. can't we just use __builtin_unreachable and provide an option (similar to
-fsanitize-undefined-trap-on-error) which will intrument all these with
__builtin_trap? I guess it's the topic Alexander was trying to address at this
year's Cauldron?
>From gcc-bugs-return-628624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:20:31 2019
Return-Path: <gcc-bugs-return-628624-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9019 invoked by alias); 10 Jan 2019 08:20:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8596 invoked by uid 48); 10 Jan 2019 08:20:20 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Thu, 10 Jan 2019 08:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-qEte2pWJH9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01433.txt.bz2
Content-length: 1682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #6 from Matthias Kretz <kretz at kde dot org> ---
(In reply to Marc Glisse from comment #4)
> Your "reference" number seems strange. Why not do the computation with
> double (or long double or mpfr) or use __builtin_hypotf? Note that it
> changes the value.
Doh. (I didn't know the builtin exists. But use of (long) double should have
been a no-brainer.) I guess my point was the precision of the input to sqrt not
the result of sqrt. The sqrt makes that error almost irrelevant, though. My
numerical analysis skills are not good enough to argue for what approach is
better. But intuitively, keeping the information of the `amax` mantissa for the
final multiplication around might actually make that approach slightly better
(if the input to the sqrt were precise that wouldn't be true, though - but it
never is).
> How precise is hypot supposed to be? I know it is supposed to try and avoid
> spurious overflow/underflow, but I am not convinced that it should aim for
> correct rounding.
That's a good question for all of <cmath> / <math.h>. Any normative wording on
that question would be (welcome) news to me. AFAIK precision is left completely
as QoI. So, except for the Annex F requirements (which we can drop with
-ffast-math), let's implement all of <cmath> as `return 0;`. ;-)
> (I see that you are using clang in that godbolt link, with gcc I need to
> mark the global variables with "extern const" to get a similar asm)
Thanks for the hint. I switched to clang when GCC started to produce code
instead of constants in the asm. (I also like the unicode identifier support in
clang ;-))
>From gcc-bugs-return-628625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:22:08 2019
Return-Path: <gcc-bugs-return-628625-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11613 invoked by alias); 10 Jan 2019 08:22: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 11503 invoked by uid 55); 10 Jan 2019 08:22:04 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Thu, 10 Jan 2019 08:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-N5oiuzl2cb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01434.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #39 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, wilco at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
>
> --- Comment #34 from Wilco <wilco at gcc dot gnu.org> ---
> With just the expr.c patch the gcc regression tests all pass on big-endian
> AArch64. Interestingly this includes the new torture test, ie. it does not
> trigger the union bug.
Does it still pass if you apply the tree-ssa-sccvn.c patch or does
that break things again?
I'm somewhat confused that only the expr.c fix is enough...
>From gcc-bugs-return-628626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:36:58 2019
Return-Path: <gcc-bugs-return-628626-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54696 invoked by alias); 10 Jan 2019 08:36:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54657 invoked by uid 48); 10 Jan 2019 08:36:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88774] Qualification of parameters does not change a function type: Bug or standard defect?
Date: Thu, 10 Jan 2019 08:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88774-4-0bpcMh5j7B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01435.txt.bz2
Content-length: 214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88774
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, that's consistent with how C++ handles top-level cv-qualifiers in function
parameters.
>From gcc-bugs-return-628627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:41:53 2019
Return-Path: <gcc-bugs-return-628627-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117398 invoked by alias); 10 Jan 2019 08:41:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115098 invoked by uid 55); 10 Jan 2019 08:41:48 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Thu, 10 Jan 2019 08:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-PGzOOmSmUE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01436.txt.bz2
Content-length: 2339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #40 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
>
> rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |rsandifo at gcc dot gnu.org
>
> --- Comment #35 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> Yeah, the expr.c patch makes the original testcase work, but we still fail for:
>
> #include<stdio.h>
> typedef unsigned int U32;
> typedef unsigned short U16;
> typedef unsigned char U8;
>
> typedef struct MEM_HEAD_4DW
> {
> /* first word */
> U32 b11 : 1;
> U32 b12 : 3;
> U32 b13 : 3;
> U32 b14 : 1;
> U32 b15 : 16;
> U32 b16 : 8;
>
> /* second word */
> U32 b21 : 16;
> U32 b22 : 1;
> U32 b23 : 4;
> U32 b24 : 11;
>
> /* third word */
> U32 b31 : 32;
>
> /* fourth word */
> U32 b30AddrL : 30;
> U32 b2AddrType : 2;
> }MEM_REQ_HEAD_4DW;
>
> typedef union HEAD_DW4_UNION
> {
> MEM_REQ_HEAD_4DW strMemHead;
> U32 aulValue[4];
> U16 ausValue[8];
> U8 aucValue[16];
> }HEAD_REQ_DW4_UNION;
>
>
>
> U32 Test_func(U32 ulAddr)
> {
> HEAD_REQ_DW4_UNION unData;
>
> unData.strMemHead.b30AddrL = ulAddr >> 2;
> unData.strMemHead.b2AddrType = 0;
> printf("unData.ausValue[6]=0x%x\r\n",unData.ausValue[6]); // why get
> 0x0 instead of 0x1 ?
>
> return 0;
> }
>
> int main()
>
> {
> Test_func(0x10224);
> return 0;
> }
>
> Like Wilco says, the torture test seems to pass with an unpatched compiler (but
> seems like a good thing to have anyway).
Yeah, the torture test fails to have the "large" store being a bitfield
one. I'll see if I can reasonably extend the testcase to covert this
case. Or rather add variants of the testcase.
Richard.
>From gcc-bugs-return-628628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:44:20 2019
Return-Path: <gcc-bugs-return-628628-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129433 invoked by alias); 10 Jan 2019 08:44: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 129385 invoked by uid 48); 10 Jan 2019 08:44:16 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc >= 8.3
Date: Thu, 10 Jan 2019 08:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88782-4-4WmbYF8QIb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01437.txt.bz2
Content-length: 182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88782
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That's wrong in exactly the cases r266380 was meant to solve.
>From gcc-bugs-return-628629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:46:52 2019
Return-Path: <gcc-bugs-return-628629-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15009 invoked by alias); 10 Jan 2019 08:46: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 14891 invoked by uid 48); 10 Jan 2019 08:46:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc >= 8.3
Date: Thu, 10 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88782-4-VnbC7MkUrr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01438.txt.bz2
Content-length: 309
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88782
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think I might need to rename _S_ti() so that old callers will get an old
definition of it that matches what they expect, and new callers of the new
function won't care what _S_ti() does.
>From gcc-bugs-return-628630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:49:26 2019
Return-Path: <gcc-bugs-return-628630-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21801 invoked by alias); 10 Jan 2019 08:49:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21286 invoked by uid 55); 10 Jan 2019 08:48:46 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Thu, 10 Jan 2019 08:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-NWMd3LvgkF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01439.txt.bz2
Content-length: 2419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #41 from rguenther at suse dot de <rguenther at suse dot de> ---
On Wed, 9 Jan 2019, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
>
> --- Comment #38 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> Created attachment 45392
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45392&action=edit
> patch that changes get_ref_base_and_extent for bare SSA_NAMEs
>
> (In reply to Wilco from comment #37)
> > (In reply to rsandifo@gcc.gnu.org from comment #35)
> > > Yeah, the expr.c patch makes the original testcase work, but we still fail
> > > for:
> >
> > That's the folding in ccp1 after inlining, which will require a similar fix.
> > There are likely more places that need to be fixed to handle the 'short' bit
> > types.
>
> Yeah, seems like a can of worms.
>
> The expr.c approach treats a reference to an N-bit integer in an
> M>N-bit mode is relative to M rather than N (i.e. it's relative
> to the addressable storage.) So maybe the point this goes wrong
> is when we ask for get_ref_base_and_extent on a bare 30-bit SSA_NAME
> (no component accesses) and get back an offset of 0. If everything's
> relative to the addressable storage then maybe it should be 2 for
> big-endian?
>
> The attached patch does that and seems to pass all three tests
> in the PR so far. I'll give a spin overnight just in case
> it's at least vaguely sensible.
I considered this. I guess we need to document this somewhere
though. Incidentially the GIMPLE verifier already does
if (!AGGREGATE_TYPE_P (TREE_TYPE (op))
&& maybe_gt (size + bitpos,
tree_to_poly_uint64 (TYPE_SIZE (TREE_TYPE
(op)))))
{
error ("position plus size exceeds size of referenced object
in "
"BIT_FIELD_REF");
return true;
}
so it uses TYPE_SIZE and not TYPE_PREICISON to verify the bounds of
the BIT_FIELD_REF access.
That said we should probably have exhaustive testing on this.
Maybe simply try to add GIMPLE testcases exercising the
BIT_FIELD_REF of bit-precision entities case.
I also wonder whether for the GIMPLE checking we want to verify
that for bit-precision OP the extracted range is within what
is valid (which depends on endianess then?).
>From gcc-bugs-return-628631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 08:52:27 2019
Return-Path: <gcc-bugs-return-628631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49972 invoked by alias); 10 Jan 2019 08:52: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 47669 invoked by uid 48); 10 Jan 2019 08:52:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 08:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
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-88775-4-A245Eg7GTL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01440.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Probably not. I don't think sanitizers flag the unspecified comparisons, so we
could just always do the uintptr_t comparisons for C++98/11. The patch looks
good to me.
>From gcc-bugs-return-628632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 09:26:09 2019
Return-Path: <gcc-bugs-return-628632-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11557 invoked by alias); 10 Jan 2019 09:26: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 11445 invoked by uid 48); 10 Jan 2019 09:25:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87314] pointless comparison of malloc result to a string not eliminated
Date: Thu, 10 Jan 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-87314-4-B34mInOySk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87314-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87314-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01441.txt.bz2
Content-length: 1800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87314
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45399
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45399&action=edit
patch for the string cases
OK, these special cases could be handled easily. They should already
be covered by
/* When the addresses are not directly of decls compare base and offset.
This implements some remaining parts of fold_comparison address
comparisons but still no complete part of it. Still it is good
enough to make fold_stmt not regress when not dispatching to fold_binary.
*/
(for cmp (simple_comparison)
(simplify
(cmp (convert1?@2 addr@0) (convert2? addr@1))
(with
but we fall into
(if (equal == 0
&& DECL_P (base0) && DECL_P (base1)
/* If we compare this as integers require equal offset. */
&& (!INTEGRAL_TYPE_P (TREE_TYPE (@2))
|| known_eq (off0, off1)))
(switch
(if (cmp == EQ_EXPR)
{ constant_boolean_node (false, type); })
(if (cmp == NE_EXPR)
{ constant_boolean_node (true, type); })))))))))
which only handles decl vs. decl.
I'm not sure how to handle "foo" ==/!= "foo" though, dependent on string
merging they could be either equal or not equal. I guess similar
for "foobar"+3 and "bar"?
So sth like the attached which is conservative about string-merging (delaying
to runtime).
>From gcc-bugs-return-628633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 09:28:34 2019
Return-Path: <gcc-bugs-return-628633-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14159 invoked by alias); 10 Jan 2019 09:28:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14068 invoked by uid 48); 10 Jan 2019 09:28:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 09:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-88775-4-6uTsxwUIm3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01442.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Target Milestone|--- |8.3
>From gcc-bugs-return-628634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 09:42:19 2019
Return-Path: <gcc-bugs-return-628634-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67536 invoked by alias); 10 Jan 2019 09:42:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67481 invoked by uid 48); 10 Jan 2019 09:42:15 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88786] New: Expand vector copysign (and xorsign) operations in the vectoriser
Date: Thu, 10 Jan 2019 09:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01443.txt.bz2
Content-length: 1428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88786
Bug ID: 88786
Summary: Expand vector copysign (and xorsign) operations in the
vectoriser
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ktkachov at gcc dot gnu.org
CC: rsandifo at gcc dot gnu.org
Target Milestone: ---
Currently every target defines the copysign optab for vector modes to emit very
similar sequences of extracting the sign bit in RTL. This leads to almost
identical code for AArch64 Adv SIMD, SVE, aarch32 NEON etc.
We should teach the vectoriser to expand a vector copysign operation at the
tree level to benefit from more optimisations early on. Care needs to be taken
to make sure the xorsign optimisation (currently done late in widen_mult) still
triggers for vectorised code. This will allow us to a lot of duplicate code in
the MD patterns and only implement them if the target can actually do a smarter
sequence than the default.
This is similar in principle to the multiplication-by-constant expansion we
already do in tree-vect-patterns.c
See, for example, the gcc.target/aarch64/vect-xorsign_exec.c testcase for the
kind of input for this.
>From gcc-bugs-return-628635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 09:47:42 2019
Return-Path: <gcc-bugs-return-628635-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107923 invoked by alias); 10 Jan 2019 09:47: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 107884 invoked by uid 48); 10 Jan 2019 09:47:37 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] New: [9 regression] C++ constexpr seems to not get expanded
Date: Thu, 10 Jan 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: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01444.txt.bz2
Content-length: 1226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
Bug ID: 88787
Summary: [9 regression] C++ constexpr seems to not get expanded
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: tnfchris at gcc dot gnu.org
Target Milestone: ---
Target: arm-none-linux-gnueabihf
The following testcases from libstdc++ have started failing in the past few
days on trunk:
FAIL: 27_io/filesystem/operations/last_write_time.cc execution test
FAIL: 30_threads/future/cons/constexpr.cc scan-assembler-not
_ZNSt6futureIiEC2Ev
FAIL: 30_threads/future/cons/constexpr.cc scan-assembler-not
_ZNSt6futureIvEC2Ev
FAIL: 30_threads/shared_future/cons/constexpr.cc scan-assembler-not
_ZNSt13shared_futureIiEC2Ev
FAIL: 30_threads/shared_future/cons/constexpr.cc scan-assembler-not
_ZNSt13shared_futureIvEC2Ev
Looking into the tests, it seems that the expression is not evaluated at
compile time as expected anymore but instead are being created dynamically.
e.g. the code contains the inline constructor and destructors and calls to
them.
>From gcc-bugs-return-628636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 09:50:39 2019
Return-Path: <gcc-bugs-return-628636-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5867 invoked by alias); 10 Jan 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 5752 invoked by uid 48); 10 Jan 2019 09:50:35 -0000
From: "10walls at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Thu, 10 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 10walls at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88568-4-caXJVwU75Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01445.txt.bz2
Content-length: 261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
--- Comment #8 from jon_y <10walls at gmail dot com> ---
I've used a linux hosted mingw toolchain to build a mingw toolchain from the
same sources, it seems to be working fine.
I've only enabled C and C++.
>From gcc-bugs-return-628637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:06:10 2019
Return-Path: <gcc-bugs-return-628637-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72147 invoked by alias); 10 Jan 2019 10:06: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 59918 invoked by uid 48); 10 Jan 2019 10:06:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 10:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-MdhRkksTVt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01446.txt.bz2
Content-length: 1355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the
if (__x.7_6 < __y.8_7)
goto <bb 4>; [50.00%]
else
goto <bb 3>; [50.00%]
<bb 3> [local count: 38463891]:
if (__x.7_6 > __y.8_7)
goto <bb 4>; [50.00%]
else
goto <bb 5>; [50.00%]
fails to merge to != because at the time we run ifcombine it still looks like
_4 = _3 > "hello";
_5 = __builtin_constant_p (_4);
if (_5 != 0)
goto <bb 4>; [34.00%]
else
goto <bb 3>; [66.00%]
<bb 3> [local count: 708669605]:
__x.5_6 = (long unsigned int) "hello";
__y.6_7 = (long unsigned int) _3;
_8 = __x.5_6 < __y.6_7;
<bb 4> [local count: 1073741824]:
# _9 = PHI <_4(2), _8(3)>
if (_9 != 0)
goto <bb 8>; [50.00%]
else
goto <bb 5>; [50.00%]
<bb 5> [local count: 536870913]:
_10 = _3 < "hello";
_11 = __builtin_constant_p (_10);
if (_11 != 0)
goto <bb 7>; [34.00%]
else
goto <bb 6>; [66.00%]
<bb 6> [local count: 354334802]:
__x.5_12 = (long unsigned int) _3;
__y.6_13 = (long unsigned int) "hello";
_14 = __x.5_12 < __y.6_13;
<bb 7> [local count: 536870913]:
# _15 = PHI <_10(5), _14(6)>
if (_15 != 0)
goto <bb 8>; [50.00%]
else
goto <bb 9>; [50.00%]
but maybe that is what Jakubs patch fixes.
>From gcc-bugs-return-628638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:13:17 2019
Return-Path: <gcc-bugs-return-628638-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94534 invoked by alias); 10 Jan 2019 10:13:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94475 invoked by uid 48); 10 Jan 2019 10:13:12 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] [8/9 Regression] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc >= 8.3
Date: Thu, 10 Jan 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work assigned_to short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-88782-4-MkaY7eZd39@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01447.txt.bz2
Content-length: 906
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88782
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-10
Known to work| |8.2.0
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Summary|Crash when mixing |[8/9 Regression] Crash when
|make_shared from gcc <= 8.2 |mixing make_shared from gcc
|with make_shared from gcc |<= 8.2 with make_shared
|>= 8.3 |from gcc >= 8.3
Ever confirmed|0 |1
Known to fail| |8.2.1, 9.0
>From gcc-bugs-return-628639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:22:58 2019
Return-Path: <gcc-bugs-return-628639-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35358 invoked by alias); 10 Jan 2019 10:22:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35221 invoked by uid 48); 10 Jan 2019 10:22:54 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] New: [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone attachments.created
Message-ID: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01448.txt.bz2
Content-length: 904
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
Bug ID: 88788
Summary: [9 Regression] Infinite loop in malloc_candidate_p_1
since r264838
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: compile-time-hog
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: marxin at gcc dot gnu.org, prathamesh3492 at gcc dot gnu.org
Target Milestone: ---
Created attachment 45400
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45400&action=edit
test-case
Since the revision the testcase (isolated from libstorage-ng) causes timeout
(300s), which the previous revision compiled the test-case in ~150s.
Command:
$ g++ spinning2.ii -c -O2 -Wno-deprecated-declarations
>From gcc-bugs-return-628640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:24:57 2019
Return-Path: <gcc-bugs-return-628640-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41423 invoked by alias); 10 Jan 2019 10:24: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 40627 invoked by uid 48); 10 Jan 2019 10:24:01 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 10:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on everconfirmed target_milestone cf_known_to_fail
Message-ID: <bug-88788-4-UcleJlb2Zt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01449.txt.bz2
Content-length: 2194
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Known to work| |8.2.0
Keywords| |needs-reduction
Last reconfirmed| |2019-01-10
Ever confirmed|0 |1
Target Milestone|--- |9.0
Known to fail| |9.0
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Patch that can trigger ICE:
diff --git a/gcc/ipa-pure-const.c b/gcc/ipa-pure-const.c
index ba0c7c2d83e..3481719aa9d 100644
--- a/gcc/ipa-pure-const.c
+++ b/gcc/ipa-pure-const.c
@@ -878,8 +878,10 @@ check_retval_uses (tree retval, gimple *stmt)
}
static bool
-malloc_candidate_p_1 (function *fun, tree retval, gimple *ret_stmt, bool ipa)
+malloc_candidate_p_1 (function *fun, tree retval, gimple *ret_stmt, bool ipa,
+ int depth)
{
+ gcc_assert (depth < 40);
cgraph_node *node = cgraph_node::get_create (fun->decl);
if (!check_retval_uses (retval, ret_stmt))
@@ -925,7 +927,7 @@ malloc_candidate_p_1 (function *fun, tree retval, gimple
*ret_stmt, bool ipa)
gimple *arg_def = SSA_NAME_DEF_STMT (arg);
if (is_a<gphi *> (arg_def))
{
- if (!malloc_candidate_p_1 (fun, arg, phi, ipa))
+ if (!malloc_candidate_p_1 (fun, arg, phi, ipa, depth + 1))
DUMP_AND_RETURN ("nested phi fail")
continue;
}
@@ -987,7 +989,7 @@ malloc_candidate_p (function *fun, bool ipa)
|| TREE_CODE (TREE_TYPE (retval)) != POINTER_TYPE)
DUMP_AND_RETURN("Return value is not SSA_NAME or not a pointer type.")
- if (!malloc_candidate_p_1 (fun, retval, ret_stmt, ipa))
+ if (!malloc_candidate_p_1 (fun, retval, ret_stmt, ipa, 0))
return false;
}
I'll try to reduce that.
>From gcc-bugs-return-628641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:27:08 2019
Return-Path: <gcc-bugs-return-628641-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45198 invoked by alias); 10 Jan 2019 10:27:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45115 invoked by uid 48); 10 Jan 2019 10:27:02 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Thu, 10 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88776-4-s81IAgL52s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01450.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from at least 4.3.1 up to trunk (9.0).
>From gcc-bugs-return-628642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:31:17 2019
Return-Path: <gcc-bugs-return-628642-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59994 invoked by alias); 10 Jan 2019 10:31: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 59474 invoked by uid 48); 10 Jan 2019 10:31:00 -0000
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88789] New: epiphany: memory_resource.cc:235:62: error: static assertion failed
Date: Thu, 10 Jan 2019 10:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sebastian.huber@embedded-brains.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-88789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01451.txt.bz2
Content-length: 4419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88789
Bug ID: 88789
Summary: epiphany: memory_resource.cc:235:62: error: static
assertion failed
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: sebastian.huber@embedded-brains.de
Target Milestone: ---
Build fails in libstdc++ currently:
libtool: compile:
/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/./gcc/xgcc
-shared-libgcc
-B/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/./gcc
-nostdinc++
-L/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/libstdc++-v3/src
-L/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/libstdc++-v3/src/.libs
-L/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/libstdc++-v3/libsupc++/.libs
-nostdinc
-B/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/newlib/
-isystem
/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/newlib/targ-include
-isystem
/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/gnu-mirror-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885/newlib/libc/include
-B/home/user/install/rtems/6/epiphany-rtems6/bin/
-B/home/user/install/rtems/6/epiphany-rtems6/lib/ -isystem
/home/user/install/rtems/6/epiphany-rtems6/include -isystem
/home/user/install/rtems/6/epiphany-rtems6/sys-include
-I/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/gnu-mirror-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885/libstdc++-v3/../libgcc
-I/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/libstdc++-v3/include/epiphany-rtems6
-I/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/build/epiphany-rtems6/libstdc++-v3/include
-I/home/user/rtems-source-builder/rtems/build/epiphany-rtems6-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885-newlib-fbd3835384fa586fd32ce80280d81bb51ab042ba-x86_64-linux-gnu-1/gnu-mirror-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885/libstdc++-v3/libsupc++
-std=gnu++17 -fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual
-Wabi=2 -fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=cow-string-inst.lo -fimplicit-templates -g -O2 -c
../../../../../gnu-mirror-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885/libstdc++-v3/src/c++17/cow-string-inst.cc
-o cow-string-inst.o
../../../../../gnu-mirror-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885/libstdc++-v3/src/c++17/memory_resource.cc:
In member function 'void
std::pmr::monotonic_buffer_resource::_M_new_buffer(std::size_t, std::size_t)':
../../../../../gnu-mirror-gcc-76fb04650b2bacd33eaff257f08fabcc237ec885/libstdc++-v3/src/c++17/memory_resource.cc:235:62:
error: static assertion failed
235 | static_assert(alignof(monotonic_buffer_resource::_Chunk) == 1);
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
>From gcc-bugs-return-628643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:35:29 2019
Return-Path: <gcc-bugs-return-628643-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78868 invoked by alias); 10 Jan 2019 10:35:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76357 invoked by uid 48); 10 Jan 2019 10:35:25 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88790] New: No warning for misleading indentation
Date: Thu, 10 Jan 2019 10:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88790-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01452.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88790
Bug ID: 88790
Summary: No warning for misleading indentation
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: segher at gcc dot gnu.org
Target Milestone: ---
-Wmisleading-indentation does not warn for
===
void f(void)
{
}
}
===
(as Daniel (on cc:) found), but not even for
===
void f(void)
{
}
===
Is there a reason for that?
>From gcc-bugs-return-628644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:36:36 2019
Return-Path: <gcc-bugs-return-628644-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91981 invoked by alias); 10 Jan 2019 10:36:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91849 invoked by uid 48); 10 Jan 2019 10:36:30 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 10:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88775-4-Xcw2mk3BBp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01453.txt.bz2
Content-length: 1161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
Ever confirmed|0 |1
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #3)
> _4 = _3 > "hello";
> _5 = __builtin_constant_p (_4);
> if (_5 != 0)
> goto <bb 4>; [34.00%]
> else
> goto <bb 3>; [66.00%]
>
> <bb 3> [local count: 708669605]:
> __x.5_6 = (long unsigned int) "hello";
> __y.6_7 = (long unsigned int) _3;
> _8 = __x.5_6 < __y.6_7;
>
> <bb 4> [local count: 1073741824]:
> # _9 = PHI <_4(2), _8(3)>
> if (_9 != 0)
> goto <bb 8>; [50.00%]
> else
> goto <bb 5>; [50.00%]
which is a somewhat awkward pattern. I think that VN should really be
able to value-number _4 and _8 the same eliding this crap. Let me see
to do that.
OK, that helps _a lot_.
>From gcc-bugs-return-628645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:37:55 2019
Return-Path: <gcc-bugs-return-628645-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93900 invoked by alias); 10 Jan 2019 10:37: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 93799 invoked by uid 48); 10 Jan 2019 10:37:50 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88790] No warning for misleading indentation
Date: Thu, 10 Jan 2019 10:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88790-4-4FO6HoILip@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88790-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88790-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01454.txt.bz2
Content-length: 196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88790
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
(I couldn't add that cc:, Daniel doesn't have a bugzilla account yet).
>From gcc-bugs-return-628646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:39:10 2019
Return-Path: <gcc-bugs-return-628646-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103915 invoked by alias); 10 Jan 2019 10:39:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103622 invoked by uid 48); 10 Jan 2019 10:39:04 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 10:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88775-4-gUcsjNMGKD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01455.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45401
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45401&action=edit
VN patch
Turns f() into just
<bb 2> [local count: 1073741824]:
_3 = &MEM[(struct basic_string *)s_2(D)].D.18989._M_local_buf;
MEM[(struct _Alloc_hider *)s_2(D)]._M_p = _3;
MEM[(size_type *)s_2(D) + 8B] = 0;
MEM[(char_type &)s_2(D) + 16] = 0;
if (_3 != "hello")
goto <bb 3>; [75.00%]
else
goto <bb 4>; [25.00%]
<bb 3> [local count: 805306369]:
__builtin_memcpy (_3, "hello", 5);
goto <bb 5>; [100.00%]
<bb 4> [local count: 134217728]:
__builtin_memcpy ("hello", &MEM[(void *)"hello" + 5B], 5);
<bb 5> [local count: 1073741824]:
MEM[(size_type *)s_2(D) + 8B] = 5;
MEM[(char_type &)s_2(D) + 21] = 0;
return s_2(D);
>From gcc-bugs-return-628647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:40:14 2019
Return-Path: <gcc-bugs-return-628647-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108018 invoked by alias); 10 Jan 2019 10:40:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107250 invoked by uid 48); 10 Jan 2019 10:40:07 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88789] epiphany: memory_resource.cc:235:62: error: static assertion failed
Date: Thu, 10 Jan 2019 10:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88789-4-jFbvhY9Xc2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01456.txt.bz2
Content-length: 581
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88789
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
That type has these members:
unsigned char _M_canary;
unsigned char _M_size;
unsigned char _M_align;
unsigned char _M_next[sizeof(_Chunk*)];
So it should have the same alignment as an unsigned char, no?
>From gcc-bugs-return-628648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:44:02 2019
Return-Path: <gcc-bugs-return-628648-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120104 invoked by alias); 10 Jan 2019 10:44:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120021 invoked by uid 48); 10 Jan 2019 10:43:54 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Thu, 10 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc version everconfirmed cf_known_to_fail
Message-ID: <bug-88787-4-s0TcizOiWN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01457.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
CC| |ktkachov at gcc dot gnu.org
Version|unknown |9.0
Ever confirmed|0 |1
Known to fail| |9.0
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed.
>From gcc-bugs-return-628649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:46:15 2019
Return-Path: <gcc-bugs-return-628649-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122704 invoked by alias); 10 Jan 2019 10:46:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122301 invoked by uid 55); 10 Jan 2019 10:45:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8/9 Regression] 'dllimport' no longer implies 'extern' in C
Date: Thu, 10 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88568-4-7379UX7NoD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01458.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 10 10:44:46 2019
New Revision: 267799
URL: https://gcc.gnu.org/viewcvs?rev=267799&root=gcc&view=rev
Log:
PR c/88568
* attribs.c (handle_dll_attribute): Clear TREE_STATIC after setting
DECL_EXTERNAL.
* gcc.dg/pr88568.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/pr88568.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/attribs.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 10:57:34 2019
Return-Path: <gcc-bugs-return-628650-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83170 invoked by alias); 10 Jan 2019 10:57:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82873 invoked by uid 55); 10 Jan 2019 10:57:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 10:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-LR1GjDw0T0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01459.txt.bz2
Content-length: 721
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 10 10:56:56 2019
New Revision: 267800
URL: https://gcc.gnu.org/viewcvs?rev=267800&root=gcc&view=rev
Log:
PR tree-optimization/88775
* include/bits/stl_function.h (greater<_Tp*>::operator(),
less<_Tp*>::operator(), greater_equal<_Tp*>::operator(),
less_equal<_Tp*>::operator()): Use __builtin_is_constant_evaluated
instead of __builtin_constant_p if available. Don't bother with
the pointer comparison in C++11 and earlier.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/stl_function.h
>From gcc-bugs-return-628651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:01:20 2019
Return-Path: <gcc-bugs-return-628651-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88640 invoked by alias); 10 Jan 2019 11: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 87075 invoked by uid 48); 10 Jan 2019 11:00:57 -0000
From: "ylatuya at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] Exception handling configured mode does not match the one finally used
Date: Thu, 10 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ylatuya at gmail dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88772-4-IMVTnZBla9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01460.txt.bz2
Content-length: 3565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
--- Comment #4 from Andoni <ylatuya at gmail dot com> ---
(In reply to Eric Botcazou from comment #3)
> > I just wiped the build to start a clean build from scratch, but I remember
> > checking this and it was "no". I can confirm it in ~1 hour
>
> Can you confirm that we're talking about the 32-bit multilib of libgcc here?
> Then, if the answer was "no", we need to understand why. The check is
> simple:
>
> dnl Check if the compiler is configured for setjmp/longjmp exceptions.
> AC_DEFUN([GCC_CHECK_SJLJ_EXCEPTIONS],
> [AC_CACHE_CHECK([whether the compiler is configured for setjmp/longjmp
> exceptions],
> ac_cv_sjlj_exceptions,
> [AC_COMPILE_IFELSE(
> [AC_LANG_PROGRAM(
> [[#ifdef __USING_SJLJ_EXCEPTIONS__
> this will fail
> #endif]],
> [[int i;]])],
> [ac_cv_sjlj_exceptions=no],
> [ac_cv_sjlj_exceptions=yes])])])
>
> Can you run it manually with -m32?
For 64bits the result is "no":
643 configure:4751: checking whether the compiler is configured for
setjmp/longjmp exceptions
644 configure:4769: x86_64-w64-mingw32-gcc
-L/home/andoni/mingw/windows/multilib/x86_64-w64-mingw32/lib
-L/home/andoni/mingw/windows/multilib/mingw/lib -isystem /home
/andoni/mingw/windows/multilib/x86_64-w64-mingw32/include -isystem
/home/andoni/mingw/windows/multilib/mingw/include -c -Wall -g -O2
-DWINVER=0x0600 -D_WIN32_ WINNT=0x0600 conftest.c >&5
645 conftest.c: In function 'main':
646 conftest.c:30:5: warning: unused variable 'i' [-Wunused-variable]
647 int i;
648 ^
649 configure:4769: $? = 0
650 configure:4776: result: no
for 32 bits the result is "yes":
631 configure:4751: checking whether the compiler is configured for
setjmp/longjmp exceptions
632 configure:4769: x86_64-w64-mingw32-gcc
-L/home/andoni/mingw/windows/multilib/x86_64-w64-mingw32/lib
-L/home/andoni/mingw/windows/multilib/mingw/lib -isystem /home
/andoni/mingw/windows/multilib/x86_64-w64-mingw32/include -isystem
/home/andoni/mingw/windows/multilib/mingw/include -m32 -c -Wall -g -O2
-DWINVER=0x0600 -D_WIN 32_WINNT=0x0600 conftest.c >&5
633 conftest.c:25:11: error: unknown type name 'this'
634 this will fail
635 ^~~~
636 conftest.c:25:21: error: expected '=', ',', ';', 'asm' or '__attribute__'
before 'fail'
637 this will fail
638 ^~~~
639 configure:4769: $? = 1
[...]
674 configure:4776: result: yes
For 32 bits the final EH model being used is Dwarf2:
340 # Additional sources to handle exceptions; overridden by targets as needed.
341 LIB2ADDEH = $(srcdir)/unwind-dw2.c $(srcdir)/unwind-dw2-fde.c \
342 $(srcdir)/unwind-sjlj.c $(srcdir)/unwind-c.c
What I understand is happening in a multilib build is that for 64 it chooses
SEH because ac_cv_sjlj_exceptions is not "yes" but for 32, it chooses dw2
instead of SJLJ for the same reason, because ac_cv_sjlj_exceptions is not
"yes":
if test x$ac_cv_sjlj_exceptions = xyes; then
tmake_eh_file="i386/t-sjlj-eh"
elif test "${host_address}" = 32; then
# biarch -m32 with --disable-sjlj-exceptions
tmake_eh_file="i386/t-dw2-eh"
md_unwind_header=i386/w32-unwind.h
else
tmake_eh_file="i386/t-seh-eh"
fi
What should happen in a mutilib build is that if the user configured without
passing any specific options for EH, the 32 bits target should be forced to be
configured with --enable-sjlj-exceptions.
>From gcc-bugs-return-628652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:06:58 2019
Return-Path: <gcc-bugs-return-628652-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116994 invoked by alias); 10 Jan 2019 11:06:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116897 invoked by uid 48); 10 Jan 2019 11:06:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Thu, 10 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88777-4-vWcfzFDABW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01461.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-628653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:08:45 2019
Return-Path: <gcc-bugs-return-628653-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130702 invoked by alias); 10 Jan 2019 11:08: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 128463 invoked by uid 48); 10 Jan 2019 11:08:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] [8/9 Regression] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc >= 8.3
Date: Thu, 10 Jan 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority target_milestone
Message-ID: <bug-88782-4-8fcwnNoPeJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01462.txt.bz2
Content-length: 398
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88782
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ABI
Priority|P3 |P1
Target Milestone|--- |8.3
>From gcc-bugs-return-628654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:08:59 2019
Return-Path: <gcc-bugs-return-628654-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2578 invoked by alias); 10 Jan 2019 11:08: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 2363 invoked by uid 48); 10 Jan 2019 11:08:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88568] [7/8 Regression] 'dllimport' no longer implies 'extern' in C
Date: Thu, 10 Jan 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88568-4-yNCO3wctEg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88568-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01463.txt.bz2
Content-length: 539
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[7/8/9 Regression] |[7/8 Regression]
|'dllimport' no longer |'dllimport' no longer
|implies 'extern' in C |implies 'extern' in C
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk so far.
>From gcc-bugs-return-628655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:16:27 2019
Return-Path: <gcc-bugs-return-628655-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4757 invoked by alias); 10 Jan 2019 11:16: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 4541 invoked by uid 48); 10 Jan 2019 11:16:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88784] Middle end is missing some optimizations about unsigned
Date: Thu, 10 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88784-4-0efnCAmGjA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88784-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88784-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01464.txt.bz2
Content-length: 731
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88784
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. Similar for singed and X > Y && X != INT_MIN, etc.
ifcombine is one place to fix (maybe_fold_and_comparisons and friends),
match.pd in case this gets lowered to BIT_AND/IOR.
>From gcc-bugs-return-628656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:17:11 2019
Return-Path: <gcc-bugs-return-628656-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7089 invoked by alias); 10 Jan 2019 11:17: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 5976 invoked by uid 48); 10 Jan 2019 11:17:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88785] [9 Regression] ICE in as_a, at machmode.h:353
Date: Thu, 10 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget target_milestone short_desc
Message-ID: <bug-88785-4-NJeQSFRB85@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01465.txt.bz2
Content-length: 507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*, i?86-*-*
Target Milestone|--- |9.0
Summary|ICE in as_a, at |[9 Regression] ICE in as_a,
|machmode.h:353 |at machmode.h:353
>From gcc-bugs-return-628657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:17:57 2019
Return-Path: <gcc-bugs-return-628657-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10400 invoked by alias); 10 Jan 2019 11:17: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 10319 invoked by uid 48); 10 Jan 2019 11:17:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88786] Expand vector copysign (and xorsign) operations in the vectoriser
Date: Thu, 10 Jan 2019 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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-88786-4-Qulk955n9H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01466.txt.bz2
Content-length: 241
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88786
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think it's a bit too low-level and having the higher-level op benefits
later optimizations (match.pd patterns, etc.)
>From gcc-bugs-return-628658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:18:30 2019
Return-Path: <gcc-bugs-return-628658-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11544 invoked by alias); 10 Jan 2019 11:18: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 11480 invoked by uid 48); 10 Jan 2019 11:18:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Thu, 10 Jan 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-88787-4-2SxsfVgEIp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01467.txt.bz2
Content-length: 356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Target Milestone|--- |9.0
>From gcc-bugs-return-628659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:22:54 2019
Return-Path: <gcc-bugs-return-628659-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21005 invoked by alias); 10 Jan 2019 11:22: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 20958 invoked by uid 48); 10 Jan 2019 11:22:49 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Thu, 10 Jan 2019 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88787-4-xGeZsRnZtW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01468.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Tamar Christina from comment #0)
> The following testcases from libstdc++ have started failing in the past few
> days on trunk:
>
> FAIL: 27_io/filesystem/operations/last_write_time.cc execution test
This one is unrelated to the others. It fails for all 32-bit targets, see
https://gcc.gnu.org/ml/libstdc++/2019-01/msg00033.html
>From gcc-bugs-return-628660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:23:12 2019
Return-Path: <gcc-bugs-return-628660-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21884 invoked by alias); 10 Jan 2019 11:23: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 21802 invoked by uid 48); 10 Jan 2019 11:23:07 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] New: ASAN deadlocks in threaded application
Date: Thu, 10 Jan 2019 11:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01469.txt.bz2
Content-length: 5207
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
Bug ID: 88791
Summary: ASAN deadlocks in threaded application
Product: gcc
Version: 7.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: dominik.strasser@onespin-solutions.com
CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
I have a threaded application which shows random crashes with ASAN. This is
unfortunate but does not bother me too much. What is bothering me is that ASAN
deadlocks after crashes.
It looks like __asan::ReportDeadlySignal tries to acquire the
__asan::thread_registry_placeholder lock which is already held by
__sanitizer::ThreadRegistry::FinishThread
Here are the two partial backtraces form my application:
This is the thread which crashes:
Thread 13 (Thread 0x7f35b94cc700 (LWP 53461)):
#0 atomic_exchange<__sanitizer::atomic_uint32_t>
(mo=__sanitizer::memory_order_acquire, v=2, a=0x7f35f05f8cb8
<__asan::thread_registry_placeholder+24>) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_atomic_clang.h:66
#1 __sanitizer::BlockingMutex::Lock (this=0x7f35f05f8cb8
<__asan::thread_registry_placeholder+24>) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_linux.cc:525
#2 0x00007f35f037bf76 in Lock (this=<optimized out>) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_thread_registry.h:84
#3 StartReporting (this=0x7f35c13e0f5f) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_report.cc:225
#4 __asan::ScopedInErrorReport::ScopedInErrorReport (this=0x7f35c13e0f5f,
fatal=<optimized out>) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_report.cc:120
#5 0x00007f35f0378970 in __asan::ReportDeadlySignal (signo=signo@entry=11,
sig=...) at ../../../../gcc-7.4.0/libsanitizer/asan/asan_report.cc:251
#6 0x00007f35f0377b12 in __asan::AsanOnDeadlySignal (signo=11,
siginfo=0x7f35c13e1bf0, context=0x7f35c13e1ac0) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_posix.cc:99
#7 <signal handler called>
#8 0x00007f35f0398e17 in __sanitizer::ThreadContextBase::ThreadContextBase
(this=0x7f35c469d000, tid=52) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_thread_registry.cc:20
#9 0x00007f35f037f1a2 in AsanThreadContext (tid=52, this=<optimized out>) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_thread.h:42
#10 __asan::GetAsanThreadContext (tid=52) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_thread.cc:55
#11 0x00007f35f0399217 in __sanitizer::ThreadRegistry::CreateThread
(this=0x7f35f05f8ca0 <__asan::thread_registry_placeholder>, user_id=0,
detached=<optimized out>, parent_tid=41, arg=0x7f35ba4f7550) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_thread_registry.cc:129
#12 0x00007f35f037f2f8 in __asan::AsanThread::Create
(start_routine=start_routine@entry=0x7f35d06f5785
<SYSTEM::DetachedThread_startInternal(void*)>, arg=arg@entry=0x6160000f0680,
parent_tid=41, stack=stack@entry=0x7f35ba4f75e0, detached=<optimized out>) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_thread.cc:90
#13 0x00007f35f02cf2a4 in __interceptor_pthread_create (thread=0x6160000f07f0,
attr=<optimized out>, start_routine=0x7f35d06f5785
<SYSTEM::DetachedThread_startInternal(void*)>, arg=0x6160000f0680) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_interceptors.cc:264
#14 0x00007f35d06f8453 in SYSTEM::DetachedThread::start (this=0x6160000f0680)
at mythread.C:491
#15 0x00007f35d06f7e8f in SYSTEM::DetachedThread::startAndWait (threads=...) at
mythread.C:427
This is another thread:
Thread 11 (Thread 0x7f35b9cf9700 (LWP 53463)):
#0 atomic_exchange<__sanitizer::atomic_uint32_t>
(mo=__sanitizer::memory_order_acquire, v=2, a=0x7f35f05f8cb8
<__asan::thread_registry_placeholder+24>) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_atomic_clang.h:66
#1 __sanitizer::BlockingMutex::Lock (this=0x7f35f05f8cb8
<__asan::thread_registry_placeholder+24>) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_linux.cc:525
#2 0x00007f35f03998b5 in GenericScopedLock (mu=0x7f35f05f8cb8
<__asan::thread_registry_placeholder+24>, this=<synthetic pointer>) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_mutex.h:177
#3 __sanitizer::ThreadRegistry::FinishThread (this=0x7f35f05f8ca0
<__asan::thread_registry_placeholder>, tid=42) at
../../../../gcc-7.4.0/libsanitizer/sanitizer_common/sanitizer_thread_registry.cc:251
#4 0x00007f35f037f6f7 in __asan::AsanThread::Destroy (this=0x7f35b6d9d000) at
../../../../gcc-7.4.0/libsanitizer/asan/asan_thread.cc:109
#5 0x00007f35cf574c22 in __nptl_deallocate_tsd () from /lib64/libpthread.so.0
#6 0x00007f35cf574e33 in start_thread () from /lib64/libpthread.so.0
#7 0x00007f35ce0bbbad in clone () from /lib64/libc.so.6
So to me it looks like both threads try to lock
__asan::thread_registry_placeholder
>From gcc-bugs-return-628661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:28:57 2019
Return-Path: <gcc-bugs-return-628661-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43723 invoked by alias); 10 Jan 2019 11:28: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 43636 invoked by uid 48); 10 Jan 2019 11:28:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 11:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-HNzDunIOrD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01470.txt.bz2
Content-length: 801
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
So after the patch we have
__x.5_4 = (long unsigned int) "hello";
__y.6_5 = (long unsigned int) _3;
if (__x.5_4 != __y.6_5)
goto <bb 3>; [75.00%]
else
goto <bb 4>; [25.00%]
<bb 3> [local count: 805306369]:
__builtin_memcpy (_3, "hello", 5);
goto <bb 14>; [100.00%]
<bb 4> [local count: 268435456]:
if (_3 >= &MEM[(void *)"hello" + 5B])
goto <bb 5>; [50.00%]
else
goto <bb 6>; [50.00%]
where we fail to elide this condition. Well, in theory "hello"
could be followed by "hello", thus in .str "hello\0hello\0" and
thus the condition could be true. Somehow w/o the libstdc++ patch
this condition either doesn't appear or is elided.
>From gcc-bugs-return-628662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:37:18 2019
Return-Path: <gcc-bugs-return-628662-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9477 invoked by alias); 10 Jan 2019 11:37:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9443 invoked by uid 55); 10 Jan 2019 11:37:14 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88648] [7/8/9 Regression] Force unified syntax for inline assembly not functional (-masm-syntax-unified)
Date: Thu, 10 Jan 2019 11:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88648-4-HezQziwi3z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01471.txt.bz2
Content-length: 979
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88648
--- Comment #3 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Thu Jan 10 11:36:42 2019
New Revision: 267804
URL: https://gcc.gnu.org/viewcvs?rev=267804&root=gcc&view=rev
Log:
ARM: fix -masm-syntax-unified (PR88648)
This allows to use unified asm syntax when compiling for the
ARM instruction. This matches documentation and seems what the
initial patch was intended doing when the flag got added.
2019-01-10 Stefan Agner <stefan@agner.ch>
PR target/88648
* config/arm/arm.c (arm_option_override_internal): Force
opts->x_inline_asm_unified to true only if TARGET_THUMB2_P.
* gcc.target/arm/pr88648-asm-syntax-unified.c: Add test to
check if -masm-syntax-unified gets applied properly.
Added:
trunk/gcc/testsuite/gcc.target/arm/pr88648-asm-syntax-unified.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/arm/arm.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:39:29 2019
Return-Path: <gcc-bugs-return-628663-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15816 invoked by alias); 10 Jan 2019 11:39: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 15783 invoked by uid 48); 10 Jan 2019 11:39:25 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88648] [7/8 Regression] Force unified syntax for inline assembly not functional (-masm-syntax-unified)
Date: Thu, 10 Jan 2019 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-88648-4-fB41lvqZhm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88648-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01472.txt.bz2
Content-length: 688
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88648
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |9.0
Summary|[7/8/9 Regression] Force |[7/8 Regression] Force
|unified syntax for inline |unified syntax for inline
|assembly not functional |assembly not functional
|(-masm-syntax-unified) |(-masm-syntax-unified)
Known to fail|9.0 |
--- Comment #4 from ktkachov at gcc dot gnu.org ---
Fixed on trunk.
>From gcc-bugs-return-628664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:40:36 2019
Return-Path: <gcc-bugs-return-628664-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17046 invoked by alias); 10 Jan 2019 11:40:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16976 invoked by uid 48); 10 Jan 2019 11:40:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 11: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-vZhScz2zSZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01473.txt.bz2
Content-length: 655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
"hello" string literal surely can be followed by anything else, but don't we
consider it UB?
int
foo (void)
{
int a = 0;
for (int i = 0; i < 32; i++)
a += "hello"[i];
return a;
}
warning: iteration 6 invokes undefined behavior
[-Waggressive-loop-optimizations]
a += "hello"[i];
~~~~~~~^~~
So,
__builtin_memcpy (xyz, &MEM[(void *)"hello" + 5B], 5);
is the same kind of UB.
Note, I don't see any:
__builtin_memcpy ("hello", ..., 5);
in my IL, that would be another UB unless string literals are writable.
>From gcc-bugs-return-628666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:53:50 2019
Return-Path: <gcc-bugs-return-628666-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68024 invoked by alias); 10 Jan 2019 11:53: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 67974 invoked by uid 48); 10 Jan 2019 11:53:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88792] [9 Regression] wrong-code in RPO VN since r263875
Date: Thu, 10 Jan 2019 11:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cf_known_to_work target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88792-4-W1PEZUsYN6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01475.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88792
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
Known to work| |8.2.0
Target Milestone|--- |9.0
Ever confirmed|0 |1
Known to fail| |9.0
>From gcc-bugs-return-628665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:53:32 2019
Return-Path: <gcc-bugs-return-628665-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67247 invoked by alias); 10 Jan 2019 11:53:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67162 invoked by uid 48); 10 Jan 2019 11:53:27 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88792] New: [9 Regression] wrong-code in RPO VN since r263875
Date: Thu, 10 Jan 2019 11:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01474.txt.bz2
Content-length: 1104
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88792
Bug ID: 88792
Summary: [9 Regression] wrong-code in RPO VN since r263875
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Isolated from vim package:
$ cat r.c
int one = 1;
char
__attribute__((noipa))
foo(char v)
{
int modec;
if (one)
{
modec = ((v < 'A' || v > 'Z') ? v : v + ('a' - 'A'));
if (modec != 't' && modec != 'c' && modec != 'g')
modec = 0;
}
else
modec = 'g';
return modec;
}
int main(int argc, char **argv)
{
char c = 't';
int r = foo (c);
__builtin_printf ("called for '%c', returned: %c\n", c, r);
if (r != c)
__builtin_abort ();
return 0;
}
$ gcc -O2 r.c -O2 && ./a.out
called for 't', returned:
Aborted (core dumped)
>From gcc-bugs-return-628667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:55:02 2019
Return-Path: <gcc-bugs-return-628667-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70739 invoked by alias); 10 Jan 2019 11:55:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70213 invoked by uid 55); 10 Jan 2019 11:54:58 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Thu, 10 Jan 2019 11:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85574-4-qHIUufD2U4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01476.txt.bz2
Content-length: 397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #27 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Thu Jan 10 11:54:26 2019
New Revision: 267805
URL: https://gcc.gnu.org/viewcvs?rev=267805&root=gcc&view=rev
Log:
PR tree-optimization/85574
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/tree-ssa-uncprop.c
>From gcc-bugs-return-628668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 11:58:56 2019
Return-Path: <gcc-bugs-return-628668-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93345 invoked by alias); 10 Jan 2019 11:58: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 93305 invoked by uid 48); 10 Jan 2019 11:58:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88792] [9 Regression] wrong-code in RPO VN since r263875
Date: Thu, 10 Jan 2019 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88792-4-t7GF6Ifvyx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01477.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88792
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-628669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:07:33 2019
Return-Path: <gcc-bugs-return-628669-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105785 invoked by alias); 10 Jan 2019 12:07: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 105750 invoked by uid 48); 10 Jan 2019 12:07:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88785] [9 Regression] ICE in as_a, at machmode.h:353
Date: Thu, 10 Jan 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-88785-4-f5gHeK8j0q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01478.txt.bz2
Content-length: 563
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-10
CC| |jakub at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-628670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:14:13 2019
Return-Path: <gcc-bugs-return-628670-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31151 invoked by alias); 10 Jan 2019 12:14:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31097 invoked by uid 48); 10 Jan 2019 12:14:09 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 12:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-0AeQigZaWP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01479.txt.bz2
Content-length: 177
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #2 from prathamesh3492 at gcc dot gnu.org ---
Sorry for the breakage, I will take a look.
Regards,
Prathamesh
>From gcc-bugs-return-628671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:19:41 2019
Return-Path: <gcc-bugs-return-628671-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45879 invoked by alias); 10 Jan 2019 12:19: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 45825 invoked by uid 48); 10 Jan 2019 12:19:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88785] [9 Regression] ICE in as_a, at machmode.h:353
Date: Thu, 10 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88785-4-5uKc2EaNS6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01480.txt.bz2
Content-length: 147
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Guess latent since r214091.
>From gcc-bugs-return-628672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:23:51 2019
Return-Path: <gcc-bugs-return-628672-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105198 invoked by alias); 10 Jan 2019 12:23:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102250 invoked by uid 48); 10 Jan 2019 12:23:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88785] [9 Regression] ICE in as_a, at machmode.h:353
Date: Thu, 10 Jan 2019 12:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88785-4-RkhnOzif49@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01481.txt.bz2
Content-length: 253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45402
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45402&action=edit
gcc9-pr88785.patch
Untested fix.
>From gcc-bugs-return-628673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:24:58 2019
Return-Path: <gcc-bugs-return-628673-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50472 invoked by alias); 10 Jan 2019 12:24: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 45752 invoked by uid 48); 10 Jan 2019 12:24:54 -0000
From: "sebastian.huber@embedded-brains.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88789] epiphany: memory_resource.cc:235:62: error: static assertion failed
Date: Thu, 10 Jan 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sebastian.huber@embedded-brains.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-88789-4-GmYp7cgein@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01482.txt.bz2
Content-length: 222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88789
--- Comment #2 from Sebastian Huber <sebastian.huber@embedded-brains.de> ---
I am not an epiphany expert. I just noticed this while testing the GCC builds
for RTEMS.
>From gcc-bugs-return-628674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:31:28 2019
Return-Path: <gcc-bugs-return-628674-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103465 invoked by alias); 10 Jan 2019 12:31:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103404 invoked by uid 48); 10 Jan 2019 12:31:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88792] [9 Regression] wrong-code in RPO VN since r263875
Date: Thu, 10 Jan 2019 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88792-4-6ZtBykDnDJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01483.txt.bz2
Content-length: 149
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88792
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, I see what goes wrong.
>From gcc-bugs-return-628675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:32:11 2019
Return-Path: <gcc-bugs-return-628675-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105032 invoked by alias); 10 Jan 2019 12:32: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 104983 invoked by uid 48); 10 Jan 2019 12:32:07 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-41ywupOfxi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01484.txt.bz2
Content-length: 284
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to prathamesh3492 from comment #2)
> Sorry for the breakage, I will take a look.
>
> Regards,
> Prathamesh
Wait, I have almost reduced test-case.
>From gcc-bugs-return-628676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:32:40 2019
Return-Path: <gcc-bugs-return-628676-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106040 invoked by alias); 10 Jan 2019 12:32:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105965 invoked by uid 55); 10 Jan 2019 12:32:36 -0000
From: "jules at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/71959] [OpenACC] lto1: ICE in inline_read_section, at ipa-fnsummary.c:3314
Date: Thu, 10 Jan 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords: ice-on-invalid-code, openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jules at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-71959-4-EzeXuVedeC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71959-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71959-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01485.txt.bz2
Content-length: 582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71959
--- Comment #11 from jules at gcc dot gnu.org ---
Author: jules
Date: Thu Jan 10 12:32:03 2019
New Revision: 267806
URL: https://gcc.gnu.org/viewcvs?rev=267806&root=gcc&view=rev
Log:
Add testcase from PR71959
libgomp/
PR lto/71959
* testsuite/libgomp.oacc-c++/pr71959-aux.cc: New.
* testsuite/libgomp.oacc-c++/pr71959.C: New.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c++/pr71959-aux.cc
trunk/libgomp/testsuite/libgomp.oacc-c++/pr71959.C
Modified:
trunk/libgomp/ChangeLog
>From gcc-bugs-return-628677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:35:23 2019
Return-Path: <gcc-bugs-return-628677-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113863 invoked by alias); 10 Jan 2019 12:35: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 113779 invoked by uid 48); 10 Jan 2019 12:35:18 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Thu, 10 Jan 2019 12:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88750-4-9AZgOAHnTb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01486.txt.bz2
Content-length: 1521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
--- Comment #34 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #33)
> (In reply to Iain Sandoe from comment #32)
> > (In reply to Jürgen Reuter from comment #31)
> > > Then I get tons of duplicate symbol lines.
> >
> > ah well, not so simple then,
So .. I think things behave as expected .. like so:
$ cat op-new.C
#include <new>
extern int *foo ();
int main() {
int *p2 = new (std::nothrow) int[10];
int *px = foo ();
delete[] p2;
delete[] px;
}
$ cat foo.C
#include <new>
int *foo () {
int *p2 = new (std::nothrow) int[10];
if (p2)
p2[3] = 10;
return p2;
}
===
/opt/iains/PR88750/bin/g++ foo.C -shared -o libfoo.dylib
^^^ that makes a shared lib that references the libstdc++.dylib
/opt/iains/PR88750/bin/g++ op-new.C -L. -lfoo -o op-sh
^^ builds a "normal" C++ program that resolves the operator new [] from the
shared libstdc++.
/opt/iains/PR88750/bin/gcc -xc++ op-new.C
-Wl,-force_load,x86_64-apple-darwin16/libstdc++-v3/src/.libs/libstdc++.a -L.
-lfoo -o o-sta
(the path to the static instance is local there only because i patched the
operator new [] to print out which version was called.)
^^^ builds a program that uses the "o-sta" as the libstdc++ and resolves both
the call in main *and* the call in libfoo.dylib from the instance in o-sta.
=====
So, whatever else might be wrong - it is nothing to do with the warning that ld
emits.
>From gcc-bugs-return-628678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:45:47 2019
Return-Path: <gcc-bugs-return-628678-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4381 invoked by alias); 10 Jan 2019 12:45: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 4324 invoked by uid 48); 10 Jan 2019 12:45:43 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 12:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88788-4-b5OWnhJ6Rd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01487.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Created attachment 45403
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45403&action=edit
reduced test-case
>From gcc-bugs-return-628679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:49:20 2019
Return-Path: <gcc-bugs-return-628679-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8600 invoked by alias); 10 Jan 2019 12:49: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 8524 invoked by uid 48); 10 Jan 2019 12:49:16 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] Exception handling configured mode does not match the one finally used
Date: Thu, 10 Jan 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88772-4-iuSu4td6nX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01488.txt.bz2
Content-length: 2856
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
--- Comment #5 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> For 64bits the result is "no":
> 643 configure:4751: checking whether the compiler is configured for
> setjmp/longjmp exceptions
> 644 configure:4769: x86_64-w64-mingw32-gcc
> -L/home/andoni/mingw/windows/multilib/x86_64-w64-mingw32/lib
> -L/home/andoni/mingw/windows/multilib/mingw/lib -isystem /home
> /andoni/mingw/windows/multilib/x86_64-w64-mingw32/include -isystem
> /home/andoni/mingw/windows/multilib/mingw/include -c -Wall -g -O2
> -DWINVER=0x0600 -D_WIN32_ WINNT=0x0600 conftest.c >&5
> 645 conftest.c: In function 'main':
> 646 conftest.c:30:5: warning: unused variable 'i' [-Wunused-variable]
> 647 int i;
> 648 ^
> 649 configure:4769: $? = 0
> 650 configure:4776: result: no
As expected.
> for 32 bits the result is "yes":
> 631 configure:4751: checking whether the compiler is configured for
> setjmp/longjmp exceptions
> 632 configure:4769: x86_64-w64-mingw32-gcc
> -L/home/andoni/mingw/windows/multilib/x86_64-w64-mingw32/lib
> -L/home/andoni/mingw/windows/multilib/mingw/lib -isystem /home
> /andoni/mingw/windows/multilib/x86_64-w64-mingw32/include -isystem
> /home/andoni/mingw/windows/multilib/mingw/include -m32 -c -Wall -g -O2
> -DWINVER=0x0600 -D_WIN 32_WINNT=0x0600 conftest.c >&5
> 633 conftest.c:25:11: error: unknown type name 'this'
> 634 this will fail
> 635 ^~~~
> 636 conftest.c:25:21: error: expected '=', ',', ';', 'asm' or
> '__attribute__' before 'fail'
> 637 this will fail
> 638 ^~~~
> 639 configure:4769: $? = 1
> [...]
> 674 configure:4776: result: yes
As expected.
> For 32 bits the final EH model being used is Dwarf2:
>
> 340 # Additional sources to handle exceptions; overridden by targets as
> needed.
> 341 LIB2ADDEH = $(srcdir)/unwind-dw2.c $(srcdir)/unwind-dw2-fde.c \
> 342 $(srcdir)/unwind-sjlj.c $(srcdir)/unwind-c.c
>
>
> What I understand is happening in a multilib build is that for 64 it chooses
> SEH because ac_cv_sjlj_exceptions is not "yes" but for 32, it chooses dw2
> instead of SJLJ for the same reason, because ac_cv_sjlj_exceptions is not
> "yes":
> if test x$ac_cv_sjlj_exceptions = xyes; then
> tmake_eh_file="i386/t-sjlj-eh"
> elif test "${host_address}" = 32; then
> # biarch -m32 with --disable-sjlj-exceptions
> tmake_eh_file="i386/t-dw2-eh"
> md_unwind_header=i386/w32-unwind.h
> else
> tmake_eh_file="i386/t-seh-eh"
> fi
But you said above that the result is "yes" for 32-bit, so how come the test:
x$ac_cv_sjlj_exceptions = xyes;
is false? Does it help to rewrite it into just:
$ac_cv_sjlj_exceptions = yes;
like in libgcc/configure.ac?
>From gcc-bugs-return-628680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 12:50:39 2019
Return-Path: <gcc-bugs-return-628680-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10163 invoked by alias); 10 Jan 2019 12:50:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10090 invoked by uid 48); 10 Jan 2019 12:50:34 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 12:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-ohdJ0VDjLq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01489.txt.bz2
Content-length: 226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #5 from prathamesh3492 at gcc dot gnu.org ---
(In reply to Martin Liška from comment #4)
> Created attachment 45403 [details]
> reduced test-case
Thanks!
>From gcc-bugs-return-628681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 13:31:20 2019
Return-Path: <gcc-bugs-return-628681-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113229 invoked by alias); 10 Jan 2019 13:31: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 113078 invoked by uid 48); 10 Jan 2019 13:31:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88775-4-WAblCnjbKM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01490.txt.bz2
Content-length: 1434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45404
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45404&action=edit
VRP patch
This makes VRP register asserts for the pointer variants. This doesn't help
until after ifcombine because we throw the asserts away if they are not
EQ/NE_EXPR but after ifcombine DOM then manages to optimize the testcase nicely
again. After the libstdc++ patch and dom2:
__attribute__((abi_tag ("cxx11"), flatten))
f ()
{
const size_type __nleft;
char[16] * _3;
long unsigned int __x.5_4;
long unsigned int __y.6_5;
char * _12;
<bb 2> [local count: 1073741824]:
_3 = &MEM[(struct basic_string *)s_2(D)].D.18989._M_local_buf;
MEM[(struct _Alloc_hider *)s_2(D)]._M_p = _3;
MEM[(size_type *)s_2(D) + 8B] = 0;
MEM[(char_type &)s_2(D) + 16] = 0;
__x.5_4 = (long unsigned int) "hello";
__y.6_5 = (long unsigned int) _3;
if (__x.5_4 != __y.6_5)
goto <bb 3>; [75.00%]
else
goto <bb 4>; [25.00%]
<bb 3> [local count: 805306369]:
__builtin_memcpy (_3, "hello", 5);
goto <bb 5>; [100.00%]
<bb 4> [local count: 67108864]:
__builtin_memcpy ("hello", &MEM[(void *)"hello" + 5B], 5);
<bb 5> [local count: 1073741824]:
MEM[(size_type *)s_2(D) + 8B] = 5;
_12 = MEM[(char * *)s_2(D)];
MEM[(char_type &)_12 + 5] = 0;
return s_2(D);
}
>From gcc-bugs-return-628682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 13:33:41 2019
Return-Path: <gcc-bugs-return-628682-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115533 invoked by alias); 10 Jan 2019 13:33: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 115439 invoked by uid 48); 10 Jan 2019 13:33:37 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88702] [7/8/9 regression] We do terrible job optimizing IsHTMLWhitespace from Firefox
Date: Thu, 10 Jan 2019 13:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88702-4-laCIQglkku@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88702-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01491.txt.bz2
Content-length: 792
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88702
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
Just for the record, when rewriting the code with switch:
int IsHTMLWhitespace(int aChar) {
switch (aChar) {
case 0x0009:
case 0x000A:
case 0x000C:
case 0x000D:
case 0x0020:
return 1;
default:
return 0;
}
}
one gets a nice bit-test eventually:
<bb 2> [local count: 1073741824]:
_4 = (unsigned int) aChar_2(D);
if (_4 > 32)
goto <bb 4>; [20.00%]
else
goto <bb 3>; [80.00%]
<bb 3> :
_6 = 1 << _4;
_7 = _6 & 4294981120;
_8 = _7 != 0;
_5 = (int) _8;
<bb 4> [local count: 1073741824]:
# _1 = PHI <_5(3), 0(2)>
return _1;
>From gcc-bugs-return-628683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 13:50:29 2019
Return-Path: <gcc-bugs-return-628683-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61624 invoked by alias); 10 Jan 2019 13:50: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 61486 invoked by uid 48); 10 Jan 2019 13:50:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 13:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-uqJrtUfRt7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01492.txt.bz2
Content-length: 1237
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I get pretty much the same thing with:
--- gcc/match.pd.jj 2019-01-07 17:59:24.100931144 +0100
+++ gcc/match.pd 2019-01-10 14:45:31.870509916 +0100
@@ -1660,6 +1660,19 @@ (define_operator_list COND_TERNARY
(if (TREE_INT_CST_LOW (@1) & 1)
{ constant_boolean_node (cmp == NE_EXPR, type); })))
+/* Turn (uintptr_t) ptr1 != (uintptr_t) ptr2 comparison into just
+ ptr1 != ptr2. Don't do that for non-equality comparisons. */
+(for cmp (eq ne)
+ (simplify
+ (cmp (convert@2 @0) (convert @1))
+ (if (ANY_INTEGRAL_TYPE_P (TREE_TYPE (@2))
+ && POINTER_TYPE_P (TREE_TYPE (@0))
+ && POINTER_TYPE_P (TREE_TYPE (@1))
+ && TYPE_PRECISION (TREE_TYPE (@2)) >= TYPE_PRECISION (TREE_TYPE (@0))
+ && ((GIMPLE && types_compatible_p (TREE_TYPE (@0), TREE_TYPE (@1)))
+ || (GENERIC && TREE_TYPE (@0) == TREE_TYPE (@1))))
+ (cmp @0 @1))))
+
/* Arguments on which one can call get_nonzero_bits to get the bits
possibly set. */
(match with_possible_nonzero_bits
(well, even without the (unsigned long) casts). Isn't this better or do we
want both patches?
>From gcc-bugs-return-628684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 13:58:31 2019
Return-Path: <gcc-bugs-return-628684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74113 invoked by alias); 10 Jan 2019 13:58: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 72410 invoked by uid 48); 10 Jan 2019 13:58:27 -0000
From: "marian.buschsieweke at ovgu dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30475] assert(int+100 > int) optimized away
Date: Thu, 10 Jan 2019 13:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marian.buschsieweke at ovgu dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-30475-4-0yLtNDchpB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01493.txt.bz2
Content-length: 1182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
Marian <marian.buschsieweke at ovgu dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marian.buschsieweke at ovgu dot de
--- Comment #57 from Marian <marian.buschsieweke at ovgu dot de> ---
Sorry for posting to this ancient bugreport.
Is there a way to get a warning when code get optimized out based on undefined
behavior?
I bet that at least 90% of the C developers out there would be completely
surprised that signed integer overflow is actually undefined behavior. And at
least 99% of the C developers out there would not spot the bug in
http://ptrace.fefe.de/int.c spending significant time and energy. So being able
to get a warning for that would be highly appreciated tool to help finding and
fixing those bugs.
Kind regards,
Marian
PS: Please also consider to enable this warning with `-Wall -Wextra -pedantic`.
I bet that 99% of the cases the compiler can optimize code out because of this
undefined behavior the code has a bug in some bound checks.
>From gcc-bugs-return-628686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 14:11:54 2019
Return-Path: <gcc-bugs-return-628686-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2167 invoked by alias); 10 Jan 2019 14:11:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1706 invoked by uid 48); 10 Jan 2019 14:11:50 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30475] assert(int+100 > int) optimized away
Date: Thu, 10 Jan 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-30475-4-KICii6sNwC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01495.txt.bz2
Content-length: 161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
--- Comment #58 from Andreas Schwab <schwab@linux-m68k.org> ---
-Wstrict-overflow=1 is enabled by -Wall.
>From gcc-bugs-return-628685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 14:11:12 2019
Return-Path: <gcc-bugs-return-628685-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 715 invoked by alias); 10 Jan 2019 14:11: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 667 invoked by uid 48); 10 Jan 2019 14:11:09 -0000
From: "ylatuya at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/88772] Exception handling configured mode does not match the one finally used
Date: Thu, 10 Jan 2019 14:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgcc
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ylatuya at gmail dot com
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88772-4-3e7TXRXki0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88772-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01494.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88772
--- Comment #6 from Andoni <ylatuya at gmail dot com> ---
(In reply to Eric Botcazou from comment #5)
>
> But you said above that the result is "yes" for 32-bit, so how come the test:
>
> x$ac_cv_sjlj_exceptions = xyes;
>
> is false? Does it help to rewrite it into just:
>
> $ac_cv_sjlj_exceptions = yes;
>
> like in libgcc/configure.ac?
I see what you mean. "config.log" do report for 32 bits
"ac_cv_sjlj_exceptions=yes" I don't understand why this check fails than. It's
either a problem with the order in which it's done (although I checked and it's
correct) or an issue in how the value is checked.
I will test several option, with quites, without prepending the x, etc... and I
will report back.
>From gcc-bugs-return-628687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 14:43:00 2019
Return-Path: <gcc-bugs-return-628687-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 669 invoked by alias); 10 Jan 2019 14:43: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 590 invoked by uid 48); 10 Jan 2019 14:42:56 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 14:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88775-4-tnFmMpnOKD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01496.txt.bz2
Content-length: 252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45405
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45405&action=edit
gcc9-pr88775.patch
Full patch.
>From gcc-bugs-return-628688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 14:51:53 2019
Return-Path: <gcc-bugs-return-628688-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114175 invoked by alias); 10 Jan 2019 14:51:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109914 invoked by uid 48); 10 Jan 2019 14:51:49 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] New: Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Thu, 10 Jan 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01497.txt.bz2
Content-length: 2069
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
Bug ID: 88793
Summary: Document that __attribute__ ((cold)) is not equivalent
to __builtin_except because of optimization for size
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: documentation
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: fw at gcc dot gnu.org
Target Milestone: ---
The documentation says this:
'cold'
The 'cold' attribute on functions is used to inform the compiler
that the function is unlikely to be executed. The function is
optimized for size rather than speed and on many targets it is
placed into a special subsection of the text section so all cold
functions appear close together, improving code locality of
non-cold parts of program. The paths leading to calls of cold
functions within code are marked as unlikely by the branch
prediction mechanism. It is thus useful to mark functions used to
handle unlikely conditions, such as 'perror', as cold to improve
optimization of hot functions that do call marked functions in rare
occasions.
However, optimizing for size is a very big hammer and causes substantial
performance issues on i386 and x86-64 due to string function inlining. As a
result, the cold attribute is only suitable for code that is basically never
executed. For other cases, like repeated execution which only happens in an
unlikely configuration, it is inappropriate. The documentation does not make
this clear enough, and programmers use __attribute__ ((cold)) and the
propagation into call sites as a more convenient alternative for
__builtin_expect, leading to performance issues.
The referenced downstream bug concerns some old GCC version where GCC
incorrectly inferred cold code regions from __builtin_expect. I'm including it
here to indicate that the distinction matters in practice.
>From gcc-bugs-return-628689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 14:59:47 2019
Return-Path: <gcc-bugs-return-628689-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13098 invoked by alias); 10 Jan 2019 14:59: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 7262 invoked by uid 48); 10 Jan 2019 14:59:42 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88794] New: fixupimm intrinsics are unusable [9.0 regression]
Date: Thu, 10 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01498.txt.bz2
Content-length: 1245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88794
Bug ID: 88794
Summary: fixupimm intrinsics are unusable [9.0 regression]
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
Test case:
```
#include <x86intrin.h>
__m128 f(__m128 x, __m128 &y) {
y = _mm_fixupimm_ps(x, _mm_set1_epi32(0x00000000), 0x00);
return x;
}
__m128 g(__m128 x, __m128 &y) {
y = _mm_mask_fixupimm_ps(y, -1, x, _mm_set1_epi32(0x00000000), 0x00);
return x;
}
__m128 h(__m128 x, __m128 &y, __mmask16 k) {
y = _mm_mask_fixupimm_ps(y, k, x, _mm_set1_epi32(0x00000000), 0x00);
return x;
}
```
The function f (cf. https://godbolt.org/z/f6u-GI) only compiles with GCC 9;
none of GCC 8, clang, or ICC accept f. If one adds `y, ` as first argument to f
it compiles on non-GCC9 (cf. https://godbolt.org/z/rqPT15).
Besides the incompatibility, fixupimm is unusable on GCC9, because the
functions f and g produce garbage in y.
This was introduced in r265827.
>From gcc-bugs-return-628690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:00:53 2019
Return-Path: <gcc-bugs-return-628690-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100034 invoked by alias); 10 Jan 2019 15:00: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 82832 invoked by uid 48); 10 Jan 2019 15:00:39 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Thu, 10 Jan 2019 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-84995-4-v3FnEfJwqi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01499.txt.bz2
Content-length: 788
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
ДилÑн Палаузов <dilyan.palauzov at aegee dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #7 from ДилÑн Палаузов <dilyan.palauzov at aegee dot org> ---
Why doesn’t GCC “make install†put the linker plugin under $libdir/bfd-plugins
and how are program ./configure’s supposed to be written in a way, that LTO
works with both Clang and GCC?
>From gcc-bugs-return-628691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:04:11 2019
Return-Path: <gcc-bugs-return-628691-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42335 invoked by alias); 10 Jan 2019 15:04: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 42229 invoked by uid 48); 10 Jan 2019 15:04:03 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88794] [9 Regression] fixupimm intrinsics are unusable
Date: Thu, 10 Jan 2019 15:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88794-4-z34OiWOW9O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01500.txt.bz2
Content-length: 825
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88794
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
CC| |hjl.tools at gmail dot com,
| |jakub at gcc dot gnu.org,
| |xguo at gcc dot gnu.org
Target Milestone|--- |9.0
Summary|fixupimm intrinsics are |[9 Regression] fixupimm
|unusable [9.0 regression] |intrinsics are unusable
Ever confirmed|0 |1
>From gcc-bugs-return-628692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:08:11 2019
Return-Path: <gcc-bugs-return-628692-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49128 invoked by alias); 10 Jan 2019 15:08:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49072 invoked by uid 48); 10 Jan 2019 15:08:07 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Thu, 10 Jan 2019 15:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88793-4-67OdKXvpkZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01501.txt.bz2
Content-length: 982
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |amonakov at gcc dot gnu.org
--- Comment #1 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #0)
> However, optimizing for size is a very big hammer and causes substantial
> performance issues on i386 and x86-64 due to string function inlining. As a
> result, the cold attribute is only suitable for code that is basically never
> executed. For other cases, like repeated execution which only happens in an
> unlikely configuration, it is inappropriate.
Can you please clarify exactly what issues? If you mean inline 'rep
stosb/movsb', their overhead is on the order of 30 cycles, and I don't see what
is inappropriate about it.
>From gcc-bugs-return-628693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:18:32 2019
Return-Path: <gcc-bugs-return-628693-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65836 invoked by alias); 10 Jan 2019 15:18: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 64632 invoked by uid 48); 10 Jan 2019 15:18:26 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50410] [7/8/9 Regression] ICE in record_reference
Date: Thu, 10 Jan 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50410-4-9snaZ5arUz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50410-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50410-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01502.txt.bz2
Content-length: 237
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50410
--- Comment #32 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Some of the tests in this PR are fixed by the patch at
https://gcc.gnu.org/ml/fortran/2019-01/msg00065.html
>From gcc-bugs-return-628694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:23:55 2019
Return-Path: <gcc-bugs-return-628694-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86722 invoked by alias); 10 Jan 2019 15:23: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 86657 invoked by uid 48); 10 Jan 2019 15:23:49 -0000
From: "sbence92 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Thu, 10 Jan 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: sbence92 at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-KgC5MDTY7R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01503.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #21 from Bence Szabó <sbence92 at gmail dot com> ---
Bootstrap succeeds with trunk + gcc9-pr88450.patch. Ran gcc testsuite, all
stackalignment tests pass and so does the test added by r266345. The CPU was an
Intel Coffee Lake so avx and avx2 is supported but avx512 is not.
>From gcc-bugs-return-628695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:36:43 2019
Return-Path: <gcc-bugs-return-628695-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72871 invoked by alias); 10 Jan 2019 15:36: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 71213 invoked by uid 48); 10 Jan 2019 15:36:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Thu, 10 Jan 2019 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-v1o6VukQrd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01504.txt.bz2
Content-length: 304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The profile_estimate difference is a bug introduced in r191883 and later
extended in r193821 I have a fix for, but it can be ignored, it should have
went into the combine dump instead.
>From gcc-bugs-return-628696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:40:11 2019
Return-Path: <gcc-bugs-return-628696-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81706 invoked by alias); 10 Jan 2019 15:40: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 81626 invoked by uid 48); 10 Jan 2019 15:40:07 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Thu, 10 Jan 2019 15: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: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-PLVx3eL2tr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01505.txt.bz2
Content-length: 146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Yes, that's exactly right.
>From gcc-bugs-return-628697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:41:26 2019
Return-Path: <gcc-bugs-return-628697-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85434 invoked by alias); 10 Jan 2019 15:41:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85377 invoked by uid 48); 10 Jan 2019 15:41:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Thu, 10 Jan 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88787-4-f1iY5oQvqu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01506.txt.bz2
Content-length: 558
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #2)
> (In reply to Tamar Christina from comment #0)
> > The following testcases from libstdc++ have started failing in the past few
> > days on trunk:
> >
> > FAIL: 27_io/filesystem/operations/last_write_time.cc execution test
>
> This one is unrelated to the others. It fails for all 32-bit targets, see
> https://gcc.gnu.org/ml/libstdc++/2019-01/msg00033.html
This is fixed at r267811
>From gcc-bugs-return-628700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:44:54 2019
Return-Path: <gcc-bugs-return-628700-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117283 invoked by alias); 10 Jan 2019 15:44: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 117164 invoked by uid 55); 10 Jan 2019 15:44:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/84877] Local stack copy of BLKmode parameter on the stack is not aligned when the requested alignment exceeds MAX_SUPPORTED_STACK_ALIGNMENT
Date: Thu, 10 Jan 2019 15:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: renlin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84877-4-O5LKtnp4FC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01509.txt.bz2
Content-length: 540
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84877
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 10 15:44:16 2019
New Revision: 267812
URL: https://gcc.gnu.org/viewcvs?rev=267812&root=gcc&view=rev
Log:
PR middle-end/84877
PR bootstrap/88450
* function.c (assign_stack_local_1): Revert the 2018-11-21 changes.
(assign_parm_setup_block): Do the argument slot realignment here
instead.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/function.c
>From gcc-bugs-return-628698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:44:29 2019
Return-Path: <gcc-bugs-return-628698-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116285 invoked by alias); 10 Jan 2019 15:44: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 116236 invoked by uid 48); 10 Jan 2019 15:44:25 -0000
From: "programmer at posteo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88795] New: ICE on class-template argument deduction if non-type parameter has indirection
Date: Thu, 10 Jan 2019 15:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: programmer at posteo 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-88795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01507.txt.bz2
Content-length: 1928
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88795
Bug ID: 88795
Summary: ICE on class-template argument deduction if non-type
parameter has indirection
Product: gcc
Version: 7.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: programmer at posteo dot de
Target Milestone: ---
The following code (compiled with g++ -std=c++17 -Wall -Wextra) causes an
internal compiler error (ICE) with all GCC versions on godbolt starting from
7.1. Clang compiles fine.
// CODE START
template<class, int>
struct Array {};
template<class T, int size_>
struct Foo {
static constexpr int size() {
return size_;// this indirection causes the ICE
}
template<class U>
Foo(U, Array<T, size()>) {}
};
template<class T, int size, class U>
Foo(U, Array<T, size>) -> Foo<T, size>;
int main() {
Array<int, 2> arr{};
Foo foo{2.0, arr};
}
// CODE END
Below I post the error messages from godbolt in order to make it easier to find
this report. See also https://godbolt.org/z/Nb-3YM
GCC 9.0.0 20190109: internal compiler error: tree check: expected tree_list,
have error_mark in type_hash_canon_hash, at tree.c:6811
GCC 8.2.0: internal compiler error: in type_unification_real, at cp/pt.c:20206
GCC 8.1.0: internal compiler error: in type_unification_real, at cp/pt.c:20148
[...] mmap: Invalid argument
GCC 7.4.0: internal compiler error: in type_unification_real, at cp/pt.c:19294
GCC 7.3.0: internal compiler error: in type_unification_real, at cp/pt.c:19239
[...] mmap: Invalid argument
GCC 7.2.0: internal compiler error: in type_unification_real, at cp/pt.c:19209
[...] mmap: Invalid argument
GCC 7.1.0: internal compiler error: in type_unification_real, at cp/pt.c:19127
[...] mmap: Invalid argument
>From gcc-bugs-return-628699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:44:53 2019
Return-Path: <gcc-bugs-return-628699-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117275 invoked by alias); 10 Jan 2019 15:44: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 117186 invoked by uid 55); 10 Jan 2019 15:44:49 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Thu, 10 Jan 2019 15:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88450-4-Mud4o55dWn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01508.txt.bz2
Content-length: 541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 10 15:44:16 2019
New Revision: 267812
URL: https://gcc.gnu.org/viewcvs?rev=267812&root=gcc&view=rev
Log:
PR middle-end/84877
PR bootstrap/88450
* function.c (assign_stack_local_1): Revert the 2018-11-21 changes.
(assign_parm_setup_block): Do the argument slot realignment here
instead.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/function.c
>From gcc-bugs-return-628701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:45:35 2019
Return-Path: <gcc-bugs-return-628701-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119154 invoked by alias); 10 Jan 2019 15:45:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119040 invoked by uid 48); 10 Jan 2019 15:45:31 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88450] [9 regression] ICE in stage 2 compiler while configuring libgcc
Date: Thu, 10 Jan 2019 15:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: critical
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88450-4-7G8PdnlWa8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88450-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01510.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88450
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:46:40 2019
Return-Path: <gcc-bugs-return-628702-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121731 invoked by alias); 10 Jan 2019 15:46: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 121677 invoked by uid 48); 10 Jan 2019 15:46:36 -0000
From: "marian.buschsieweke at ovgu dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30475] assert(int+100 > int) optimized away
Date: Thu, 10 Jan 2019 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marian.buschsieweke at ovgu dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-30475-4-GdxmNp3JBp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01511.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
--- Comment #59 from Marian <marian.buschsieweke at ovgu dot de> ---
Thanks for the fast replay
wget http://ptrace.fefe.de/int.c
gcc -Wstrict-overflow=1 -Wall -Wextra -pedantic -o int int.c
does not produce a warning (except for the missing `#include <stdio.h>`) on gcc
8.2.0 on Alpine Linux for me, nor on GCC 8.2.1 20181127 an Arch Linux.
>From gcc-bugs-return-628703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 15:58:59 2019
Return-Path: <gcc-bugs-return-628703-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82952 invoked by alias); 10 Jan 2019 15:58:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82885 invoked by uid 48); 10 Jan 2019 15:58:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/81452] warn on realloc(p, 0)
Date: Thu, 10 Jan 2019 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81452-4-7SiSBlm0Jy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81452-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81452-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01512.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81452
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #3)
> There is -Walloc-zero. If we want a separate knob for just it then maybe
> -Wrealloc-zero.
Oh right, -Walloc-zero, I forgot about that one. It triggers so rarely that
it's probably safe to keep this proposed warning under that single flag.
>From gcc-bugs-return-628705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:07:51 2019
Return-Path: <gcc-bugs-return-628705-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99546 invoked by alias); 10 Jan 2019 16:07:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98717 invoked by uid 48); 10 Jan 2019 16:07:43 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Thu, 10 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88793-4-2ulIkC6Lde@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01514.txt.bz2
Content-length: 2444
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
--- Comment #2 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #1)
> (In reply to Florian Weimer from comment #0)
> > However, optimizing for size is a very big hammer and causes substantial
> > performance issues on i386 and x86-64 due to string function inlining. As a
> > result, the cold attribute is only suitable for code that is basically never
> > executed. For other cases, like repeated execution which only happens in an
> > unlikely configuration, it is inappropriate.
>
> Can you please clarify exactly what issues? If you mean inline 'rep
> stosb/movsb', their overhead is on the order of 30 cycles, and I don't see
> what is inappropriate about it.
The startup overhead isn't the problem. The asymptotic performance is really
bad, too. (I hope I didn't botch my test, though. It's vaguely based on
what's attached to the downstream bug.)
For len == 5000, I get a factor of 60 difference in favor of glibc 2.28's
strlen. For len == 30, it's still a factor of 11 in favor of strlen. This is
on a machine with a i7-8650U, so a fairly recent CPU with erms.
#include <err.h>
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include <time.h>
static size_t len = 30;
static char *buffer;
static int count = 10000;
__attribute__ ((weak))
size_t
call_strlen (const char *s)
{
return strlen (s);
}
__attribute__ ((weak, cold))
size_t
slow_strlen (const char *s)
{
return strlen (s);
}
__attribute__ ((weak))
size_t
call_slow_strlen (const char *s)
{
return slow_strlen (s);
}
static void
bench (const char *what, size_t (*fptr) (const char *))
{
struct timespec start;
if (clock_gettime (CLOCK_MONOTONIC, &start) != 0)
err (1, "clock_gettime");
for (int i = 0; i < count; ++i)
fptr (buffer);
struct timespec end;
if (clock_gettime (CLOCK_MONOTONIC, &end) != 0)
err (1, "clock_gettime");
double delta = (end.tv_sec - start.tv_sec) * 1e9;
delta += end.tv_nsec - start.tv_nsec;
printf ("%s: %f ns/call\n", what, delta / count);
}
int
main (void)
{
buffer = malloc (len + 1);
if (buffer == NULL)
err (1, "malloc");
memset (buffer, 'a', len);
buffer[len] = 0;
for (int i = 0; i < 10; i++)
{
bench ("strlen", call_strlen);
bench ("strlen (cold)", call_slow_strlen);
}
free (buffer);
return 0;
}
>From gcc-bugs-return-628704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:07:29 2019
Return-Path: <gcc-bugs-return-628704-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97825 invoked by alias); 10 Jan 2019 16:07: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 97160 invoked by uid 55); 10 Jan 2019 16:07:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Thu, 10 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80762-4-HoD9myb0jj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01513.txt.bz2
Content-length: 1287
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu Jan 10 16:06:49 2019
New Revision: 267815
URL: https://gcc.gnu.org/viewcvs?rev=267815&root=gcc&view=rev
Log:
PR libstdc++/80762 avoid ambiguous __constructible_from<void, void>
Ensure we don't try to instantiate __is_constructible_from<void, void>,
because there are two partial specializations that are equally good
matches.
Backport from mainline
2018-12-12 Jonathan Wakely <jwakely@redhat.com>
PR libstdc++/80762
* include/bits/fs_path.h (path::_Path): Use remove_cv_t and is_void.
* include/experimental/bits/fs_path.h (path::_Path): Likewise.
* testsuite/27_io/filesystem/path/construct/80762.cc: New test.
* testsuite/experimental/filesystem/path/construct/80762.cc: New test.
Added:
branches/gcc-8-branch/libstdc++-v3/testsuite/27_io/filesystem/path/construct/80762.cc
branches/gcc-8-branch/libstdc++-v3/testsuite/experimental/filesystem/path/construct/80762.cc
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/include/bits/fs_path.h
branches/gcc-8-branch/libstdc++-v3/include/experimental/bits/fs_path.h
>From gcc-bugs-return-628706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:10:52 2019
Return-Path: <gcc-bugs-return-628706-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104623 invoked by alias); 10 Jan 2019 16:10: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 104549 invoked by uid 48); 10 Jan 2019 16:10:45 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87007] [8/9 Regression] 10% slowdown with -march=skylake-avx512
Date: Thu, 10 Jan 2019 16:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hjl.tools at gmail dot com
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87007-4-9JvS22TATs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87007-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87007-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01515.txt.bz2
Content-length: 204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87007
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
The current patch is posted at
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00298.html
>From gcc-bugs-return-628707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:38:58 2019
Return-Path: <gcc-bugs-return-628707-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15040 invoked by alias); 10 Jan 2019 16:38: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 14948 invoked by uid 48); 10 Jan 2019 16:38:54 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Thu, 10 Jan 2019 16:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-80762-4-dcO95L2bbg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01516.txt.bz2
Content-length: 376
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.3
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 8.3
>From gcc-bugs-return-628708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:39:08 2019
Return-Path: <gcc-bugs-return-628708-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15939 invoked by alias); 10 Jan 2019 16:39: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 15884 invoked by uid 48); 10 Jan 2019 16:39:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Thu, 10 Jan 2019 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80762-4-pnAsjN7kpI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01517.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
.
>From gcc-bugs-return-628709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:54:15 2019
Return-Path: <gcc-bugs-return-628709-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36393 invoked by alias); 10 Jan 2019 16:54:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29974 invoked by uid 55); 10 Jan 2019 16:54:11 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Thu, 10 Jan 2019 16:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85574-4-Er6Jn2C8Nl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01518.txt.bz2
Content-length: 784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #28 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Author: hubicka
Date: Thu Jan 10 16:53:39 2019
New Revision: 267817
URL: https://gcc.gnu.org/viewcvs?rev=267817&root=gcc&view=rev
Log:
Backported from mainline
2019-01-02 Richard Biener <rguenther@suse.de>
PR ipa/85574
* ipa-icf.h (sem_item_optimizer::sort_congruence_split): Declare.
* ipa-icf.c (sem_item_optimizer::sort_congruence_split): New
function.
(sem_item_optimizer::do_congruence_step_f): Sort the congruence
set after UIDs before splitting them.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/ipa-icf.c
branches/gcc-8-branch/gcc/ipa-icf.h
>From gcc-bugs-return-628710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 16:59:51 2019
Return-Path: <gcc-bugs-return-628710-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49602 invoked by alias); 10 Jan 2019 16:59:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49562 invoked by uid 48); 10 Jan 2019 16:59:46 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88763-4-p5XlCl2CNC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01519.txt.bz2
Content-length: 305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #10 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Created attachment 45406
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45406&action=edit
Followup patch to try to dump why a condition can't be unswitched within a loop
>From gcc-bugs-return-628711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:04:17 2019
Return-Path: <gcc-bugs-return-628711-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71036 invoked by alias); 10 Jan 2019 17:04:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70887 invoked by uid 48); 10 Jan 2019 17:04:12 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Thu, 10 Jan 2019 17:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88793-4-vuleq3hHbL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01520.txt.bz2
Content-length: 1303
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
--- Comment #3 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #2)
> The startup overhead isn't the problem. The asymptotic performance is
> really bad, too. (I hope I didn't botch my test, though. It's vaguely
> based on what's attached to the downstream bug.)
>
> For len == 5000, I get a factor of 60 difference in favor of glibc 2.28's
> strlen. For len == 30, it's still a factor of 11 in favor of strlen. This
> is on a machine with a i7-8650U, so a fairly recent CPU with erms.
As noted in the referenced bug, erms does not accelerate scasb and cmpsb (only
movs and stos), so strlen and memcmp/strcmp are among the most extreme
examples. I wrongly assumed gcc did not use scasb to implement strlen inline.
I think it's fair to raise the question if gcc should not use scasb/cmpsb by
default (I thought there was a bug for that but apparently there isn't?).
I doubt it supports the original point about attribute-cold being
inappropriate. If gcc is making a poor decision in cold regions, it will be
making the same poor decision everywhere under -Os, and it's fair to demand
that such decisions are revisited and improved (-Os is not "minimize size at
all costs").
>From gcc-bugs-return-628712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:05:40 2019
Return-Path: <gcc-bugs-return-628712-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84446 invoked by alias); 10 Jan 2019 17:05:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84387 invoked by uid 48); 10 Jan 2019 17:05:36 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 17:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-GhziB1gcon@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01521.txt.bz2
Content-length: 2682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #11 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for the testcase.
(In reply to David Malcolm from comment #10)
> Created attachment 45406 [details]
> Followup patch to try to dump why a condition can't be unswitched within a
> loop
This is a followup patch (on top of the one in comment #6), which tries to dump
the desired information from comment #7.
On the testcase from comment #9, it gives:
$ ./xgcc -B. -c /tmp/t.c -O2 -funswitch-loops -fopt-info-loop-all
/tmp/t.c:17:9: missed: within this loop...
/tmp/t.c:5:7: missed: ...cannot unswitch condition: if (_16 > 5)
/tmp/t.c:3:11: missed: ...as condition is not invariant within loop; modified
here by: _16 = flag_37 + 2;
/tmp/t.c:17:9: missed: within this loop...
/tmp/t.c:17:9: missed: ...cannot unswitch condition: if (j_11 != 250)
/tmp/t.c:17:34: missed: ...as condition is not invariant within loop; modified
here by: j_11 = j_34 + 1;
i.e. it's emitting 3 messages per unswitchable condition, highlighting each of:
* the loop
* the condition
* the problematic statement
The -fsave-optimization-record version of this dump also captures the function
name (and the inlining chain, for inlined statements, such as that of the
condition within the "calc" inlined within "main"):
{
"count": {
"quality": "guessed_local",
"value": 1063000000.0
},
"function": "main",
"impl_location": {
"file": "../../src/gcc/tree-ssa-loop-unswitch.c",
"function": "dump_unswitchable_condition",
"line": 198
},
"inlining_chain": [
{
"fndecl": "calc"
},
{
"fndecl": "main",
"site": {
"column": 25,
"file": "/tmp/t.c",
"line": 19
}
}
],
"kind": "failure",
"location": {
"column": 7,
"file": "/tmp/t.c",
"line": 5
},
"message": [
"...cannot unswitch condition: ",
{
"location": {
"column": 7,
"file": "/tmp/t.c",
"line": 5
},
"stmt": "if (_16 > 5)\n"
}
],
"pass": "0x3a33250"
},
How does this look?
FWIW, this is feeling like gcc 10 material.
>From gcc-bugs-return-628713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:09:39 2019
Return-Path: <gcc-bugs-return-628713-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46783 invoked by alias); 10 Jan 2019 17:09: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 41196 invoked by uid 48); 10 Jan 2019 17:09:35 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88774] Qualification of parameters does not change a function type: Bug or standard defect?
Date: Thu, 10 Jan 2019 17:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88774-4-XAXKeNFPdr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88774-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88774-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01522.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88774
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Ok. Thanks for the answers.
>From gcc-bugs-return-628714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:10:24 2019
Return-Path: <gcc-bugs-return-628714-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87680 invoked by alias); 10 Jan 2019 17:10: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 83237 invoked by uid 48); 10 Jan 2019 17:10:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Thu, 10 Jan 2019 17:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88714-4-DNT5a2qUmT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01523.txt.bz2
Content-length: 1328
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
Ever confirmed|0 |1
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
As for the rest, seems that when tree-ssa-sccvn.c is compiled by the
stage1-gcc/ with -g -O2 -fno-checking -gtoggle options (among others), it emits
something, while when compiled with stage2-gcc/ it emits something different.
Copying tree-ssa-sccvn.o from stage1-gcc/ (prev-gcc) into stage2-gcc/ (gcc) and
rebuilding cc1 makes it generate the same assembly and same -fdump-tree-pre-all
dump for sort.i as stage1-gcc/ generates, otherwise there are differences like:
-exp_gen[6] := { countp_30 (0022), {mem_ref<0B>,countp_30}@.MEM_25 (0007),
{mem_ref<4294967292B>,countp_30}@.MEM_80 (0008), {plus_expr,_10,_11} (0009),
{pointer_plus_expr,countp_30,4} (0033) }
+exp_gen[6] := { countp_30 (0022), {mem_ref<0B>,countp_30}@.MEM_25 (0007), _11
(0008), {plus_expr,_10,_11} (0009), {pointer_plus_expr,countp_30,4} (0033) }
and various others later on.
>From gcc-bugs-return-628715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:13:52 2019
Return-Path: <gcc-bugs-return-628715-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122195 invoked by alias); 10 Jan 2019 17:13: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 122112 invoked by uid 48); 10 Jan 2019 17:13:47 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Thu, 10 Jan 2019 17:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-cUMYyo6MQR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01524.txt.bz2
Content-length: 339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #7 from emsr at gcc dot gnu.org ---
What does this do?
auto __hi_exp =
__hi & simd<_T, _Abi>(std::numeric_limits<_T>::infinity()); // no error
Sorry, I have no simd knowlege yet.
Anyway, doesn't the large scale risk overflow if a, b are large? I guess I'm
lost.
>From gcc-bugs-return-628716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:15:42 2019
Return-Path: <gcc-bugs-return-628716-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126525 invoked by alias); 10 Jan 2019 17:15: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 125430 invoked by uid 48); 10 Jan 2019 17:15:15 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88795] ICE on class-template argument deduction if non-type parameter has indirection
Date: Thu, 10 Jan 2019 17:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-88795-4-dM8fye7GVf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01525.txt.bz2
Content-length: 639
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88795
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r240765.
>From gcc-bugs-return-628717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:22:51 2019
Return-Path: <gcc-bugs-return-628717-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7671 invoked by alias); 10 Jan 2019 17:22:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7571 invoked by uid 48); 10 Jan 2019 17:22:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Thu, 10 Jan 2019 17:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88788-4-QybFcCgOFh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01526.txt.bz2
Content-length: 586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The endless recursion isn't just one issue, by walking all PHI arguments
recursively this way it can be also extremely compile time expensive even if
you avoid recursion on the PHIs currently being processed.
>From gcc-bugs-return-628718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:29:05 2019
Return-Path: <gcc-bugs-return-628718-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76991 invoked by alias); 10 Jan 2019 17:29: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 76887 invoked by uid 48); 10 Jan 2019 17:29:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Thu, 10 Jan 2019 17:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-fePhVo30Tv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01527.txt.bz2
Content-length: 759
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note, the stage1-gcc compiled tree-ssa-sccvn.o is identical no matter whether
-fno-checking or -fchecking=1 was used, and doesn't fail -fcompare-debug with
either, so it is simply that something is miscompiled somewhere.
BTW, stage3-gcc/cc1 results in the same sort.s as stage1-gcc/cc1, only
stage2-gcc/cc1 is different (if it contains the stage1-gcc/cc1plus compiled and
optimized tree-ssa-sccvn.o).
Guess we want a side-by-side debugging sessions in the debugger of
stage2-gcc/cc1 on sort.i when it has tree-ssa-sccvn.o built by the host
compiler and when it has -O2 -fno-checking -g tree-ssa-sccvn.o built by the
stage1 cc1plus.
>From gcc-bugs-return-628719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:31:11 2019
Return-Path: <gcc-bugs-return-628719-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124814 invoked by alias); 10 Jan 2019 17:31:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112890 invoked by uid 48); 10 Jan 2019 17:30:54 -0000
From: "marius.messerschmidt at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88763] Better Output for Loop Unswitching
Date: Thu, 10 Jan 2019 17:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marius.messerschmidt at googlemail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88763-4-3ytdIeDoIS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01528.txt.bz2
Content-length: 385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88763
--- Comment #12 from Marius Messerschmidt <marius.messerschmidt at googlemail dot com> ---
I think this messages look really good!
I believe that this contains everything required to actually work on improving
automatic unswitching, thank you very much!
Do you think that there is a chance that this will be included in GCC9?
>From gcc-bugs-return-628720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 17:49:33 2019
Return-Path: <gcc-bugs-return-628720-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48481 invoked by alias); 10 Jan 2019 17:49: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 48397 invoked by uid 48); 10 Jan 2019 17:49:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Thu, 10 Jan 2019 17:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88787-4-tRorJePA4C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01529.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
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> ---
Guess it must be one of the dozens or more issues with have with constexpr and
the ARM EABI cdtors returning this.
>From gcc-bugs-return-628721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:00:46 2019
Return-Path: <gcc-bugs-return-628721-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74466 invoked by alias); 10 Jan 2019 18:00: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 73959 invoked by uid 48); 10 Jan 2019 18:00:14 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Thu, 10 Jan 2019 18:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-NUxzA3E7yn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01530.txt.bz2
Content-length: 960
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #8 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Yeah, on GCC users' side I think there's a demand for both: treating UB as
unreachable (e.g. on tiny systems with heavy program size constraints) and
transforming UB to a trap briefly annotated with source location information.
In this particular testcase the warning looks like a false positive because
it's emitted on a copy of the original statement that is only called on a
specialized path, if f==-1 (and will surely invoke UB there). In general I'm
afraid it's impossible to say which copy is specialized (e.g. when you unswitch
a loop neither of the two copies is more "specific" than the original), but
perhaps here VRP threading could set some TREE_NO_WARNING flags reasonably?
I think it might have been asked already, but isn't it possible to emit such
warnings before CFG transformations may have taken place?
>From gcc-bugs-return-628723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:32:57 2019
Return-Path: <gcc-bugs-return-628723-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54484 invoked by alias); 10 Jan 2019 18:32: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 54377 invoked by uid 48); 10 Jan 2019 18:32:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Thu, 10 Jan 2019 18:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88796-4-KscoqrDQj9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01532.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-10
CC| |ebotcazou at gcc dot gnu.org,
| |law at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-628722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:32:37 2019
Return-Path: <gcc-bugs-return-628722-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48136 invoked by alias); 10 Jan 2019 18:32: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 48068 invoked by uid 48); 10 Jan 2019 18:32:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] New: -fstack-protector* kills RTL DSE opportunities
Date: Thu, 10 Jan 2019 18:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01531.txt.bz2
Content-length: 5660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
Bug ID: 88796
Summary: -fstack-protector* kills RTL DSE opportunities
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: jakub at gcc dot gnu.org
Target Milestone: ---
Marek has noticed that the gcc.target/i386/pr87370.c testcase FAILs when built
with -fstack-protector-strong (
make check-gcc
RUNTESTFLAGS='--target_board=unix\{-m64,-m64/-fstack-protector-strong\}
i386.exp=pr87370.c'
). It isn't a wrong-code, but seems quite severe anyway. Before the RTL DSE
pass, the dumps look roughly comparable, except that there is the store to the
stack canary at the beginning and read from the stack canary at the end of the
function. In DSE dump for f2 function, one can see without
-fstack-protector-strong:
starting the processing of deferred insns
ending the processing of deferred insns
df_analyze called
**scanning insn=5
mems_found = 0, cannot_delete = true
**scanning insn=14
mem: (plus:DI (reg/f:DI 19 frame)
(const_int -16 [0xfffffffffffffff0]))
after canon_rtx address: (plus:DI (reg/f:DI 19 frame)
(const_int -16 [0xfffffffffffffff0]))
gid=0 offset=-16
processing const base store gid=0[-16..0)
mems_found = 1, cannot_delete = false
**scanning insn=11
mems_found = 0, cannot_delete = true
**scanning insn=12
mems_found = 0, cannot_delete = false
Locally deleting insn 14
deferring deletion of insn with uid = 14.
group 0 is frame related group 0(16+0): n 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15, 16 p
starting the processing of deferred insns
ending the processing of deferred insns
df_analyze called
df_worklist_dataflow_doublequeue: n_basic_blocks 3 n_edges 2 count 3 ( 1)
but with -fstack-protector-strong instead:
starting the processing of deferred insns
ending the processing of deferred insns
df_analyze called
**scanning insn=4
mem: (const_int 40 [0x28])
after canon_rtx address: (const_int 40 [0x28])
after cselib_expand address: (const_int 40 [0x28])
after canon_rtx address: (const_int 40 [0x28])
varying cselib base=1:4426 offset = 0
processing cselib load mem:(mem/f:DI (const_int 40 [0x28]) [4
MEM[(<address-space-1> long unsigned int *)40B]+0 S8 A64 AS1])
mem: (plus:DI (reg/f:DI 19 frame)
(const_int -8 [0xfffffffffffffff8]))
after canon_rtx address: (plus:DI (reg/f:DI 19 frame)
(const_int -8 [0xfffffffffffffff8]))
gid=0 offset=-8
processing const base store gid=0[-8..0)
mems_found = 1, cannot_delete = true
**scanning insn=7
mems_found = 0, cannot_delete = true
**scanning insn=24
mem: (plus:DI (reg/f:DI 19 frame)
(const_int -32 [0xffffffffffffffe0]))
after canon_rtx address: (plus:DI (reg/f:DI 19 frame)
(const_int -32 [0xffffffffffffffe0]))
gid=0 offset=-32
processing const base store gid=0[-32..-16)
trying store in insn=4 gid=0[-8..0)
mems_found = 1, cannot_delete = false
**scanning insn=13
mems_found = 0, cannot_delete = true
**scanning insn=15
mem: (const_int 40 [0x28])
after canon_rtx address: (const_int 40 [0x28])
after cselib_expand address: (const_int 40 [0x28])
after canon_rtx address: (const_int 40 [0x28])
varying cselib base=1:4426 offset = 0
processing cselib load mem:(mem/f:DI (const_int 40 [0x28]) [4
MEM[(<address-space-1> long unsigned int *)40B]+0 S8 A64 AS1])
processing cselib load against insn 24
removing from active insn=24 has store
processing cselib load against insn 4
removing from active insn=4 has store
adding wild read, volatile or barrier.
mems_found = 0, cannot_delete = true
**scanning insn=16
mems_found = 0, cannot_delete = true
**scanning insn=17
mem: (symbol_ref:DI ("__stack_chk_fail") [flags 0x41] <function_decl
0x7f43b618b500 __stack_chk_fail>)
after canon_rtx address: (symbol_ref:DI ("__stack_chk_fail") [flags 0x41]
<function_decl 0x7f43b618b500 __stack_chk_fail>)
gid=1 offset=0
processing const load gid=1[0..1)
**scanning insn=20
mems_found = 0, cannot_delete = false
group 0 is frame related group 0(24+0): n 1, 2, 3, 4, 5, 6, 7, 8, 17, 18, 19,
20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32 p
group 1(0+0): n p
starting the processing of deferred insns
ending the processing of deferred insns
df_analyze called
doing global processing
df_worklist_dataflow_doublequeue: n_basic_blocks 5 n_edges 4 count 5 ( 1)
So, the
(insn 15 13 16 2 (parallel [
(set (reg:CCZ 17 flags)
(unspec:CCZ [
(mem/v/f/c:DI (plus:DI (reg/f:DI 19 frame)
(const_int -8 [0xfffffffffffffff8])) [3
D.1950+0 S8 A64])
(mem/f:DI (const_int 40 [0x28]) [4
MEM[(<address-space-1> long unsigned int *)40B]+0 S8 A64 AS1])
] UNSPEC_SP_TEST))
(clobber (scratch:DI))
]) "pr87370.c":30:1 978 {stack_protect_test_di}
(nil))
stack canary read invalidates the opportunity to remove the dead
(insn 24 7 13 2 (set (mem/c:V1TI (plus:DI (reg/f:DI 19 frame)
(const_int -32 [0xffffffffffffffe0])) [5 D.1928+0 S16 A128])
(reg:V1TI 86)) "pr87370.c":29:10 -1
(expr_list:REG_DEAD (reg:V1TI 86)
(nil)))
store. Any thoughts how we could arrange for RTL DSE to understand how the ssp
set and test patterns work and the test pattern only makes the ssp canary set
insn necessary and no other stores?
>From gcc-bugs-return-628724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:36:43 2019
Return-Path: <gcc-bugs-return-628724-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121347 invoked by alias); 10 Jan 2019 18:36: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); 10 Jan 2019 18:36:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Thu, 10 Jan 2019 18:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88796-4-fKyct2PmsA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01533.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Wonder if we e.g. could use some magic alias set, magic MEM_EXPR or whatever
else to teach RTL DSE about this.
The severity of this is IMHO high because most of the distro vendors compile
everything with -fstack-protector* and if the RTL DSE can't remove stores that
are dea at the end of functions, it could affect a lot of code.
>From gcc-bugs-return-628725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:46:14 2019
Return-Path: <gcc-bugs-return-628725-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75424 invoked by alias); 10 Jan 2019 18:46:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75358 invoked by uid 55); 10 Jan 2019 18:46:10 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] ICE in reference_record with data statement
Date: Thu, 10 Jan 2019 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86322-4-l1eYoBIZxV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01534.txt.bz2
Content-length: 913
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
--- Comment #7 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu Jan 10 18:45:38 2019
New Revision: 267820
URL: https://gcc.gnu.org/viewcvs?rev=267820&root=gcc&view=rev
Log:
2019-01-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/86322
* decl.c (top_var_list): Set locus of expr.
(gfc_match_data): Detect pointer on non-rightmost part-refs.
2019-01-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/86322
* gfortran.dg/pr86322_1.f90: New test.
* gfortran.dg/pr86322_2.f90: Ditto.
* gfortran.dg/pr86322_3.f90: Ditto.
Added:
trunk/gcc/testsuite/gfortran.dg/pr86322_1.f90
trunk/gcc/testsuite/gfortran.dg/pr86322_2.f90
trunk/gcc/testsuite/gfortran.dg/pr86322_3.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:58:16 2019
Return-Path: <gcc-bugs-return-628726-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14934 invoked by alias); 10 Jan 2019 18:58: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 14814 invoked by uid 48); 10 Jan 2019 18:58:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88792] [9 Regression] wrong-code in RPO VN since r263875
Date: Thu, 10 Jan 2019 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88792-4-ogU6pfc6mw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01535.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88792
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 18:58:44 2019
Return-Path: <gcc-bugs-return-628727-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16334 invoked by alias); 10 Jan 2019 18:58: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 16236 invoked by uid 55); 10 Jan 2019 18:58:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88792] [9 Regression] wrong-code in RPO VN since r263875
Date: Thu, 10 Jan 2019 18:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88792-4-hARSZ9MoBJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01536.txt.bz2
Content-length: 647
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88792
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu Jan 10 18:58:08 2019
New Revision: 267821
URL: https://gcc.gnu.org/viewcvs?rev=267821&root=gcc&view=rev
Log:
2019-01-10 Richard Biener <rguenther@suse.de>
PR tree-optimization/88792
* tree-ssa-pre.c (get_representative_for): Do not return a
value-number here.
* gcc.dg/torture/pr88792.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr88792.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-pre.c
>From gcc-bugs-return-628728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 19:01:22 2019
Return-Path: <gcc-bugs-return-628728-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19326 invoked by alias); 10 Jan 2019 19:01:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19208 invoked by uid 48); 10 Jan 2019 19:01:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Thu, 10 Jan 2019 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88796-4-PL7ZnOOL3Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01537.txt.bz2
Content-length: 636
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #1)
> Wonder if we e.g. could use some magic alias set, magic MEM_EXPR or whatever
> else to teach RTL DSE about this.
> The severity of this is IMHO high because most of the distro vendors compile
> everything with -fstack-protector* and if the RTL DSE can't remove stores
> that are dea at the end of functions, it could affect a lot of code.
I'd use a magic MEM_EXPR (just a special decl). IIRC I've seen this trick
used elsewhere (don't remember for what though).
>From gcc-bugs-return-628729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 19:04:45 2019
Return-Path: <gcc-bugs-return-628729-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35304 invoked by alias); 10 Jan 2019 19:04: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 35192 invoked by uid 48); 10 Jan 2019 19:04:41 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex value load
Date: Thu, 10 Jan 2019 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-YPqaujD7Et@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01538.txt.bz2
Content-length: 304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Uroš Bizjak from comment #1)
> This is due to nonexistent SCmode patterns. I guess that movsc pattern is
> needed here.
Can IRA allocate registers for SCmode and DCmode?
>From gcc-bugs-return-628730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 19:50:04 2019
Return-Path: <gcc-bugs-return-628730-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18582 invoked by alias); 10 Jan 2019 19:50: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 14566 invoked by uid 48); 10 Jan 2019 19:49:59 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Thu, 10 Jan 2019 19:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88796-4-VtHpkY7zjU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01539.txt.bz2
Content-length: 2464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
We also use magic alias set e.g. directly in RTL DSE
(ALIAS_SET_MEMORY_BARRIER).
Anyway, there are multiple MEMs that need to be treated specially. For the TLS
cases, it is e.g. on x86_64:
(insn 15 27 16 2 (parallel [
(set (reg:CCZ 17 flags)
(unspec:CCZ [
(mem/v/f/c:DI (plus:DI (reg/f:DI 19 frame)
(const_int -8 [0xfffffffffffffff8])) [3
D.1946+0 S8 A64])
(mem/f:DI (const_int 40 [0x28]) [4
MEM[(<address-space-1> long unsigned int *)40B]+0 S8 A64 AS1])
] UNSPEC_SP_TEST))
(clobber (scratch:DI))
]) "pr87370.c":23:1 978 {stack_protect_test_di}
(nil))
so there is MEM_VOLATILE_P stack canary MEM where we could use a special
MEM_EXPR, after all, we apparently already have there a VAR_DECL, and can
check that in crtl->stack_protect_guard, so this part shouldn't be that hard,
except that we for some strange reason treat all volatile reads as killing
everything, so we'd need to ignore MEM_VOLATILE_P for that special case. The
initial set ssp is a store to a volatile mem, so perhaps just ignoring such
MEMs altogether would DTRT.
The next thing is the TLS MEM, which has some MEM_EXPR in there (and isn't
volatile). Can that use some magic VAR_DECL in MEM_EXPR instead of the
expression it uses? It is weird that outside of MEM_EXPR it actually doesn't
record anywhere that it is another address space. Can we ignore this MEM
altogether too?
Finally, with -mstack-protector-guard=global, we have e.g.:
(insn 13 25 14 2 (parallel [
(set (reg:CCZ 17 flags)
(unspec:CCZ [
(mem/v/f/c:DI (plus:DI (reg/f:DI 19 frame)
(const_int -8 [0xfffffffffffffff8])) [3
D.1946+0 S8 A64])
(mem/v/f/c:DI (symbol_ref:DI ("__stack_chk_guard")
[flags 0x40] <var_decl 0x7f348fa555a0 __stack_chk_guard>) [3 __stack_ch
k_guard+0 S8 A64])
] UNSPEC_SP_TEST))
(clobber (scratch:DI))
]) "pr87370.c":23:1 978 {stack_protect_test_di}
(nil))
so there is yet another MEM_VOLATILE_P memory. Wonder why we are so
conservative about the volatile MEM reads, e.g. for a volatile MEM read from a
var I don't see why it should kill frame related stores.
>From gcc-bugs-return-628731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 19:58:28 2019
Return-Path: <gcc-bugs-return-628731-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107677 invoked by alias); 10 Jan 2019 19:58: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 107579 invoked by uid 48); 10 Jan 2019 19:58:22 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] ICE in reference_record with data statement
Date: Thu, 10 Jan 2019 19:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86322-4-JAyGVbqtV8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01540.txt.bz2
Content-length: 128
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
--- Comment #8 from kargl at gcc dot gnu.org ---
Fixed on trunk. Closing.
>From gcc-bugs-return-628732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 20:00:04 2019
Return-Path: <gcc-bugs-return-628732-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3061 invoked by alias); 10 Jan 2019 20:00: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 2454 invoked by uid 48); 10 Jan 2019 19:59:59 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/86322] ICE in reference_record with data statement
Date: Thu, 10 Jan 2019 20:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86322-4-8AlBI55dMw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01541.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86322
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from kargl at gcc dot gnu.org ---
Actually close the PR!
>From gcc-bugs-return-628733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 20:16:22 2019
Return-Path: <gcc-bugs-return-628733-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118980 invoked by alias); 10 Jan 2019 20:16:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113662 invoked by uid 48); 10 Jan 2019 20:16:14 -0000
From: "anlauf at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Thu, 10 Jan 2019 20:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anlauf at gmx dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88776-4-bACn2SklKl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01542.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #3 from Harald Anlauf <anlauf at gmx dot de> ---
Created attachment 45407
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45407&action=edit
Self-contained testcase
I've been able to produce a self-contained testcase, which may aid
debugging.
While reducing further, I got the impression that it is just a subtle
whitespace issue.
>From gcc-bugs-return-628734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 20:18:14 2019
Return-Path: <gcc-bugs-return-628734-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127885 invoked by alias); 10 Jan 2019 20: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 127797 invoked by uid 48); 10 Jan 2019 20:18:09 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Thu, 10 Jan 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-s5fMTn6mt5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01543.txt.bz2
Content-length: 922
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #8 from emsr at gcc dot gnu.org ---
(In reply to Matthias Kretz from comment #6)
> > How precise is hypot supposed to be? I know it is supposed to try and avoid
> > spurious overflow/underflow, but I am not convinced that it should aim for
> > correct rounding.
>
> That's a good question for all of <cmath> / <math.h>. Any normative wording
> on that question would be (welcome) news to me. AFAIK precision is left
> completely as QoI. So, except for the Annex F requirements (which we can
> drop with -ffast-math), let's implement all of <cmath> as `return 0;`. ;-)
>
It looks like C is trying to incorporate ISO/IEC TS 18661-1 Floating-point
extensions for C — Part 1: Binary floating-point arithmetic, etc.
This adds a lot of rounding control but it looks like correcly rounded
transcendentals are still merely a recommendation.
>From gcc-bugs-return-628735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 20:42:13 2019
Return-Path: <gcc-bugs-return-628735-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57003 invoked by alias); 10 Jan 2019 20:42: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 56964 invoked by uid 48); 10 Jan 2019 20:42:09 -0000
From: "cassio.neri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88797] New: Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Thu, 10 Jan 2019 20:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cassio.neri 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-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01544.txt.bz2
Content-length: 1398
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
Bug ID: 88797
Summary: Unneeded branch added when function is inlined
(function runs faster if not inlined)
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: cassio.neri at gmail dot com
Target Milestone: ---
Consider:
void use(unsigned);
bool f(unsigned x, unsigned y) {
return x < 1111 + (y <= 2222);
}
void test_f(unsigned x, unsigned y) {
for (unsigned i = 0; i < 3333; ++i)
use(f(x++, y++));
}
The generated code for f seems fine and the there's no branch to test y <=
2222:
f(unsigned int, unsigned int):
xorl %eax, %eax
cmpl $2222, %esi
setbe %al
addl $1111, %eax
cmpl %edi, %eax
seta %al
ret
However, when f is inlined in test_f, a branch is introduced to decide whether
x should be compared to 1111 or 1112 (code cut for brevity)
test_f(unsigned int, unsigned int):
[...]
jmp .L6
.L14:
cmpl $1111, %eax
.L12:
[...]
.L6:
[...]
cmpl $2222, %ebx
jbe .L14
cmpl $1110, %eax
jmp .L12
[...]
See https://godbolt.org/z/_EC992 use -O3.
This seems to be a regression: it used to be OK up to 6.3 and then degraded in
7.1 (according to godbolt).
>From gcc-bugs-return-628736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 20:50:36 2019
Return-Path: <gcc-bugs-return-628736-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99282 invoked by alias); 10 Jan 2019 20: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 94881 invoked by uid 48); 10 Jan 2019 20:50:33 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88797] Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Thu, 10 Jan 2019 20:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component
Message-ID: <bug-88797-4-6Qptow5jlT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01545.txt.bz2
Content-length: 612
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Component|rtl-optimization |tree-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This nothing to do with inlinining but rather something which -O3 enables that
-O2 does not.
for aarch64, -O2 gets the non-branch case but -O3 gets the branchy case.
>From gcc-bugs-return-628737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 20:56:28 2019
Return-Path: <gcc-bugs-return-628737-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81694 invoked by alias); 10 Jan 2019 20:56: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 77504 invoked by uid 48); 10 Jan 2019 20:56:24 -0000
From: "cassio.neri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88797] Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Thu, 10 Jan 2019 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cassio.neri at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88797-4-hCckemZkeM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01546.txt.bz2
Content-length: 237
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
--- Comment #2 from Cassio Neri <cassio.neri at gmail dot com> ---
Created attachment 45408
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45408&action=edit
Running example
>From gcc-bugs-return-628738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 21:01:47 2019
Return-Path: <gcc-bugs-return-628738-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104265 invoked by alias); 10 Jan 2019 21:01: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 103534 invoked by uid 48); 10 Jan 2019 21:01:43 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Thu, 10 Jan 2019 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88796-4-xpTjOkgIdD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01547.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45409
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45409&action=edit
gcc9-pr88796.patch
Untested fix.
>From gcc-bugs-return-628739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 21:02:30 2019
Return-Path: <gcc-bugs-return-628739-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128673 invoked by alias); 10 Jan 2019 21:02: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 128577 invoked by uid 48); 10 Jan 2019 21:02:26 -0000
From: "cassio.neri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88797] Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Thu, 10 Jan 2019 21:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cassio.neri 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-88797-4-EqAH9CPPJ9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01548.txt.bz2
Content-length: 1126
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
--- Comment #3 from Cassio Neri <cassio.neri at gmail dot com> ---
The attached file is running example that shows that performance is damaged.
The code runs faster when test_f calls g instead of f where g is
bool g(unsigned x, unsigned y) {
if (x >= y) return false;
return f(n, r);
}
even in the case where x < y and g does call f.
Depending on #defines the example runs either f, g or both. These are the
timings:
$ g++ -O3 -o gcc_issue gcc_issue.cpp -D RUN_SIMPLE && time ./gcc_issue
Running simple function...
real 0m3.646s
user 0m3.645s
sys 0m0.000s
$ g++ -O3 -o gcc_issue gcc_issue.cpp -D RUN_COMPLEX && time ./gcc_issue
Running complex function...
real 0m1.165s
user 0m1.161s
sys 0m0.003s
$ g++ -O3 -o gcc_issue gcc_issue.cpp -D RUN_BOTH && time ./gcc_issue
Running simple function...
Running complex function...
real 0m3.059s
user 0m3.051s
sys 0m0.007s
Notice that run both is faster than running f only! This is so because then the
compiler gives up inlining and calls the (good) generated code for f in
isolation.
>From gcc-bugs-return-628740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 21:03:26 2019
Return-Path: <gcc-bugs-return-628740-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 131011 invoked by alias); 10 Jan 2019 21:03:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130911 invoked by uid 55); 10 Jan 2019 21:03:21 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87305] [9 Regression] Segfault in end_hard_regno in setup_live_pseudos_and_spill_after_risky_transforms on aarch64 big-endian
Date: Thu, 10 Jan 2019 21:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87305-4-8MpkvS2KmX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01549.txt.bz2
Content-length: 942
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87305
--- Comment #4 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Author: vmakarov
Date: Thu Jan 10 21:02:50 2019
New Revision: 267823
URL: https://gcc.gnu.org/viewcvs?rev=267823&root=gcc&view=rev
Log:
2019-01-10 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/87305
* lra-assigns.c
(setup_live_pseudos_and_spill_after_risky_transforms): Check
allocation for big endian pseudos used as paradoxical subregs and
spill them if it is wrong.
* lra-constraints.c (lra_constraints): Add a comment.
2019-01-10 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/87305
* gcc.target/aarch64/pr87305.c: New.
Added:
trunk/gcc/testsuite/gcc.target/aarch64/pr87305.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/lra-assigns.c
trunk/gcc/lra-constraints.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 21:08:16 2019
Return-Path: <gcc-bugs-return-628741-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6189 invoked by alias); 10 Jan 2019 21:08:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6158 invoked by uid 48); 10 Jan 2019 21:08:12 -0000
From: "cassio.neri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88797] Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Thu, 10 Jan 2019 21:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cassio.neri 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-88797-4-yi40NPlJbg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01550.txt.bz2
Content-length: 416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
--- Comment #4 from Cassio Neri <cassio.neri at gmail dot com> ---
Comment on attachment 45408
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45408
Running example
The magic numbers 4, 6, 7, 0x24924924u and 0xb6db6db7u were chosen in an
attempt to maximize the probability of making branch prediction harder and the
difference in performance clearer.
>From gcc-bugs-return-628742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 22:26:01 2019
Return-Path: <gcc-bugs-return-628742-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104858 invoked by alias); 10 Jan 2019 22:26:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104703 invoked by uid 48); 10 Jan 2019 22:25:57 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88613] [9 Regression] ICE in size_binop_loc at fold-const.c:1900 since r267272
Date: Thu, 10 Jan 2019 22:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88613-4-Gcs3q6BOtC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01551.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88613
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
>From gcc-bugs-return-628743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 22:50:39 2019
Return-Path: <gcc-bugs-return-628743-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25572 invoked by alias); 10 Jan 2019 22: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 25501 invoked by uid 48); 10 Jan 2019 22:50:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 22: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: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-DCxoeiInJg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01552.txt.bz2
Content-length: 1094
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Unfortunately the #c11 patch breaks the
20_util/function_objects/comparisons_pointer.cc testcase (wonder if your VRP
patch would break it too), where the testcase does exactly what has been
discussed on IRC:
int b[8];
int a[8];
void
test01()
{
int* p = a + 8;
std::greater<int*> gt;
std::stringstream ss;
ss << gt(p, b) << ' ' << gt(b, p) << ' ' << (!gt(p, b) && !gt(b, p));
So, if we want to do this optimization, we probably need to make sure that
whatever optimizes the a + 8 != b comparisons into false doesn't do that if one
pointer is known or could point to the end of one of the objects and the other
pointer points to the start of another object and those two objects could
potentially live in the same section (though, maybe even different sections
could be problematic if one is at the end of the whole section and another one
is the first one in the next section). As the distinction is gone in RTL, this
must be some GIMPLE or tree opt.
>From gcc-bugs-return-628744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 22:56:42 2019
Return-Path: <gcc-bugs-return-628744-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34081 invoked by alias); 10 Jan 2019 22:56:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33986 invoked by uid 48); 10 Jan 2019 22:56:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 22:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-3Rign7ep3W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01553.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Seems it is the:
/* When the addresses are not directly of decls compare base and offset.
This implements some remaining parts of fold_comparison address
comparisons but still no complete part of it. Still it is good
enough to make fold_stmt not regress when not dispatching to fold_binary.
*/
opt in match.pd. So, we'd need to verify that the problematic case can't
happen (one address being after the last byte in one of the objects and the
other the beginning of another one).
>From gcc-bugs-return-628745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 22:57:29 2019
Return-Path: <gcc-bugs-return-628745-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53227 invoked by alias); 10 Jan 2019 22:57: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 53141 invoked by uid 48); 10 Jan 2019 22:57:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Thu, 10 Jan 2019 22:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-rdeSUwpw4R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01554.txt.bz2
Content-length: 202
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Of course only for equality comparisons, for non-equality the code is ok as is.
>From gcc-bugs-return-628746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 22:59:14 2019
Return-Path: <gcc-bugs-return-628746-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88989 invoked by alias); 10 Jan 2019 22:59: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 84421 invoked by uid 48); 10 Jan 2019 22:59:10 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88798] New: AVX512BW code does not use bit-operations that work on mask registers
Date: Thu, 10 Jan 2019 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wojciech_mula at poczta dot onet.pl
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01555.txt.bz2
Content-length: 2023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88798
Bug ID: 88798
Summary: AVX512BW code does not use bit-operations that work on
mask registers
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: wojciech_mula at poczta dot onet.pl
Target Milestone: ---
Hi!
AVX512BW-related issue: the C compiler generates superfluous moves from 64-bit
mask registers to 64-bit GPRs and then performs basic bit-ops, while the
AVX512BW supports bit-ops for mask registers (instructions: korq, kandq,
kxorq).
I guess the main reason is C does not define a bit-or for type __mask64
and there's always an implicit conversion to uint64_t.
Below is a sample program compiled for Cannon Lake --- the CPU does have
(at least) AVX512BW, AVX512VBMI and AVX512VL.
---perf.c---
#include <immintrin.h>
#include <stdint.h>
uint64_t any_whitespace(__m512i string) {
return _mm512_cmpeq_epu8_mask(string, _mm512_set1_epi8(' '))
| _mm512_cmpeq_epu8_mask(string, _mm512_set1_epi8('\n'))
| _mm512_cmpeq_epu8_mask(string, _mm512_set1_epi8('\r'));
}
---eof--
$ gcc --version
gcc (Debian 8.2.0-13) 8.2.0
$ gcc perf.c -O3 -march=cannonlake -S
$ cat perf.s # redacted
any_whitespace:
vpcmpub $0, .LC0(%rip), %zmm0, %k1
vpcmpub $0, .LC1(%rip), %zmm0, %k2
vpcmpub $0, .LC2(%rip), %zmm0, %k3
kmovq %k1, %rcx
kmovq %k2, %rdx
orq %rcx, %rdx
kmovq %k3, %rax
orq %rdx, %rax
vzeroupper
ret
I'd rather expect to get something like:
any_whitespace:
vpcmpub $0, .LC0(%rip), %zmm0, %k1
vpcmpub $0, .LC1(%rip), %zmm0, %k2
vpcmpub $0, .LC2(%rip), %zmm0, %k3
korq %k1, %k2, %k1
korq %k1, %k3, %k3
kmovq %k3, %rax
vzeroupper
ret
best regards
Wojciech
>From gcc-bugs-return-628747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 23:11:13 2019
Return-Path: <gcc-bugs-return-628747-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96580 invoked by alias); 10 Jan 2019 23:11:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96512 invoked by uid 48); 10 Jan 2019 23:11:09 -0000
From: "pcarroll at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88799] New: Arm -mcpu=PROCESSOR does not result in assembly directives for .arch and .arch_extension
Date: Thu, 10 Jan 2019 23:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pcarroll at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01556.txt.bz2
Content-length: 1764
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88799
Bug ID: 88799
Summary: Arm -mcpu=PROCESSOR does not result in assembly
directives for .arch and .arch_extension
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: pcarroll at codesourcery dot com
Target Milestone: ---
Created attachment 45410
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45410&action=edit
Example test case with embedded PLDW instruction
In June 2017, the mechanism for handling -march and -mcpu was modified for the
GCC 8 Arm compiler. In December 2017, the Arm compiler began emitting .arch
directives within each function that was being emitted, if the current
architecture had changed from the previous function. The problem seems to be
that this new behavior does not track architecture extensions that have been
specified on the command line or in the source.
For example, if I compile a C file with the command line "-S -mcpu=cortex-a9"
and the C file contains an asm instruction that is beyond the basic
architecture instruction set, the GCC 8 compiler generates this assembly code:
.cpu cortex-a9
.eabi_attribute 20, 1
:
.global myfunc
.arch armv7-a
.syntax unified
.arm
:
pldw L1
L1:
:
When this is assembled, I get the message
Error: Selected processor does not support `pldw L1` in ARM mode
If I insert a '.arch_extension mp' directive after the '.arch armv7-a', the
assembly file does assemble without error.
This is a regression from GCC 7.
>From gcc-bugs-return-628748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 23:20:55 2019
Return-Path: <gcc-bugs-return-628748-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80145 invoked by alias); 10 Jan 2019 23:20: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 79882 invoked by uid 55); 10 Jan 2019 23:20:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88785] [9 Regression] ICE in as_a, at machmode.h:353
Date: Thu, 10 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88785-4-QA0kZ58kIc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01557.txt.bz2
Content-length: 963
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu Jan 10 23:20:19 2019
New Revision: 267825
URL: https://gcc.gnu.org/viewcvs?rev=267825&root=gcc&view=rev
Log:
PR target/88785
* config/i386/sse.md (float<floatunssuffix>v2div2sf2): Turn into
define_expand.
(*float<floatunssuffix>v2div2sf2): New define_insn.
(float<floatunssuffix>v2div2sf2_mask): Turn into define_expand.
(*float<floatunssuffix>v2div2sf2_mask): New define_insn.
(*float<floatunssuffix>v2div2sf2_mask_1): Replace
subrtxes (const_vector:V2SF [(const_int 0) (const_int 0)]) with
match_operands with "const0_operand" "C".
* g++.target/i386/pr88785.C: New test.
Added:
trunk/gcc/testsuite/g++.target/i386/pr88785.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/sse.md
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 23:31:39 2019
Return-Path: <gcc-bugs-return-628749-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97504 invoked by alias); 10 Jan 2019 23:31: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 97401 invoked by uid 48); 10 Jan 2019 23:31:33 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Thu, 10 Jan 2019 23:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88044-4-3oI9Go1wMt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01558.txt.bz2
Content-length: 1873
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88044
--- Comment #8 from seurer at gcc dot gnu.org ---
I looked at where the code is hanging and it looks like it is hung in a loop
where it keeps calling memcpy with an incrementing by 1 length.
I set a breakpoint at the start of memcpy to break if the length was greater
than 9000 and when the breakpoint was hit just keeping hitting continue. It
was called with length 9001, 9002, 9003, ... There is nothing in the code that
does anything like this as far as I can tell and this doesn't happen with the
previous revision.
Is the call
s = transfer(vs, s)
expanded into an infinite loop? I don't know fortran so I have no idea what
that is supposed to do.
#0 .__memcpy_power7 () at ../sysdeps/powerpc/powerpc64/power7/memcpy.S:34
#1 0x0000000010000a24 in str_vs (_vs=1, _vs=1, vs=..., .__result=9002,
__result=<optimized out>)
at
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/transfer_intrinsic_3.f90:13
#2 MAIN__ () at
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/transfer_intrinsic_3.f90:34
#3 main (argc=<optimized out>, argv=<optimized out>) at
/home/seurer/gcc/gcc-test2/gcc/testsuite/gfortran.dg/transfer_intrinsic_3.f90:26
#4 0x00003fffb79c7a6c in generic_start_main (main=@0x1001fec0: 0x100008a0
<main>, argc=<optimized out>, argv=0x3fffffffe888, auxvec=0x3fffffffea00,
init=<optimized out>,
rtld_fini=<optimized out>, stack_end=<optimized out>, fini=<optimized out>)
at ../csu/libc-start.c:266
#5 0x00003fffb79c7c94 in __libc_start_main (argc=<optimized out>,
argv=<optimized out>, ev=<optimized out>, auxvec=<optimized out>,
rtld_fini=<optimized out>,
stinfo=<optimized out>, stack_on_entry=<optimized out>) at
../sysdeps/unix/sysv/linux/powerpc/libc-start.c:81
#6 0x0000000000000000 in ?? ()
>From gcc-bugs-return-628750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 23:34:26 2019
Return-Path: <gcc-bugs-return-628750-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100260 invoked by alias); 10 Jan 2019 23:34:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100183 invoked by uid 48); 10 Jan 2019 23:34:22 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86655] std::assoc_legendre should not constrain the value of m
Date: Thu, 10 Jan 2019 23:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86655-4-Uria2jrA2n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01559.txt.bz2
Content-length: 200
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86655
--- Comment #3 from emsr at gcc dot gnu.org ---
Sorry for missing this message. You're right.
Ditto for sph_legendre.
Putting together a patch.
>From gcc-bugs-return-628752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 23:36:47 2019
Return-Path: <gcc-bugs-return-628752-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16274 invoked by alias); 10 Jan 2019 23:36:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4789 invoked by uid 48); 10 Jan 2019 23:36:43 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88798] AVX512BW code does not use bit-operations that work on mask registers
Date: Thu, 10 Jan 2019 23:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88798-4-gfAiNc3vY0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01561.txt.bz2
Content-length: 240
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88798
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Some if not all has been fixed on the trunk. There was just a few weeks ago a
bug that asked for the similar thing.
>From gcc-bugs-return-628751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu Jan 10 23:36:22 2019
Return-Path: <gcc-bugs-return-628751-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69123 invoked by alias); 10 Jan 2019 23:36:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53739 invoked by uid 48); 10 Jan 2019 23:36:18 -0000
From: "harald at gigawatt dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30475] assert(int+100 > int) optimized away
Date: Thu, 10 Jan 2019 23:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: harald at gigawatt dot nl
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-30475-4-gqFH3rqQM8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01560.txt.bz2
Content-length: 1184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
Harald van Dijk <harald at gigawatt dot nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |harald at gigawatt dot nl
--- Comment #60 from Harald van Dijk <harald at gigawatt dot nl> ---
(In reply to Marian from comment #59)
> Thanks for the fast replay
>
> wget http://ptrace.fefe.de/int.c
> gcc -Wstrict-overflow=1 -Wall -Wextra -pedantic -o int int.c
>
> does not produce a warning (except for the missing `#include <stdio.h>`) on
> gcc 8.2.0 on Alpine Linux for me, nor on GCC 8.2.1 20181127 an Arch Linux.
It warned at -O2 -Wall with GCC 4.2 to 7 (-O2 enabling -fstrict-overflow), but
stopped warning in GCC 8. Warnings no longer being emitted in cases where they
are desired is part of bug 80511.
The GCC 8 Changes page[*] says -Wstrict-overflow is deprecated (even if it is
supposed to still work) and recommends to use
-fsanitize=signed-integer-overflow to get a run-time warning, which does catch
this.
[*] https://gcc.gnu.org/gcc-8/changes.html
>From gcc-bugs-return-628753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 00:20:22 2019
Return-Path: <gcc-bugs-return-628753-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 724 invoked by alias); 11 Jan 2019 00:20:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130690 invoked by uid 48); 11 Jan 2019 00:20:16 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Fri, 11 Jan 2019 00:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-ly38hm0dbI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01562.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #9 from Martin Sebor <msebor at gcc dot gnu.org> ---
It might be possible for some. I'm not sure how successful it would be for
others. The thread_jumps pass runs four times and moving the warn_restrict
pass before its first instance results in dozens of regressions. This
particular instance of the warning goes away if the warn_restrict pass is moved
before the second to last threads_jump pass, but that still causes regressions.
Moving the pass just before the last threads_jump pass doesn't help.
>From gcc-bugs-return-628754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 00:24:55 2019
Return-Path: <gcc-bugs-return-628754-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7730 invoked by alias); 11 Jan 2019 00:24: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 7630 invoked by uid 48); 11 Jan 2019 00:24:49 -0000
From: "zackw at panix dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88576] -fno-math-errno causes GCC to consider that malloc does not set errno
Date: Fri, 11 Jan 2019 00:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zackw at panix dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88576-4-QziFW4NpxC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88576-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01563.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88576
--- Comment #14 from Zack Weinberg <zackw at panix dot com> ---
I don't see why it would _ever_ make sense for -fno-alloc-errno to default to
the setting of -fno-math-errno. The math functions and the memory allocation
functions are independent components of the C library. Each toggle's default
should be settable independently by the target configuration.
>From gcc-bugs-return-628755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 00:56:50 2019
Return-Path: <gcc-bugs-return-628755-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50987 invoked by alias); 11 Jan 2019 00:56:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50898 invoked by uid 48); 11 Jan 2019 00:56:46 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35031] ELEMENTAL procedure with BIND(C)
Date: Fri, 11 Jan 2019 00:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc assigned_to target_milestone
Message-ID: <bug-35031-4-Q8zHpYtngx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01564.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35031
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |kargl at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |kargl at gcc dot gnu.org
Target Milestone|--- |9.0
>From gcc-bugs-return-628756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 01:35:10 2019
Return-Path: <gcc-bugs-return-628756-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38591 invoked by alias); 11 Jan 2019 01:35:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38502 invoked by uid 48); 11 Jan 2019 01:35:06 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/47235] Accepts invalid/wrong code: PURE functions and Cray pointers
Date: Fri, 11 Jan 2019 01:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: accepts-invalid, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-47235-4-ncbc4oVC5g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47235-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47235-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01565.txt.bz2
Content-length: 561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47235
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
CC| |kargl at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #2 from kargl at gcc dot gnu.org ---
Closing. The PR has been in the WAITING state for 2 years, 3 months. No
testcase has been submitted.
>From gcc-bugs-return-628757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 01:59:00 2019
Return-Path: <gcc-bugs-return-628757-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42001 invoked by alias); 11 Jan 2019 01:59:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38065 invoked by uid 48); 11 Jan 2019 01:58:56 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88327] Implement P0515R3, P0905R1, P1120R0, C++20 std concepts.
Date: Fri, 11 Jan 2019 01:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88327-4-Sk84ywxPcM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88327-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88327-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01566.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88327
emsr at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from emsr at gcc dot gnu.org ---
This is a duplicate of 88329. Sorry for the noise.
*** This bug has been marked as a duplicate of bug 88329 ***
>From gcc-bugs-return-628759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 01:59:01 2019
Return-Path: <gcc-bugs-return-628759-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42282 invoked by alias); 11 Jan 2019 01:59:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38797 invoked by uid 48); 11 Jan 2019 01:58:56 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/67491] [meta-bug] concepts issues
Date: Fri, 11 Jan 2019 01:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-67491-4-r6caYGKm3W@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67491-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67491-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01568.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67491
Bug 67491 depends on bug 88327, which changed state.
Bug 88327 Summary: Implement P0515R3, P0905R1, P1120R0, C++20 std concepts.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88327
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
>From gcc-bugs-return-628758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 01:59:00 2019
Return-Path: <gcc-bugs-return-628758-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42077 invoked by alias); 11 Jan 2019 01:59:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38423 invoked by uid 48); 11 Jan 2019 01:58:56 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88329] Implement C++20 std concepts.
Date: Fri, 11 Jan 2019 01:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88329-4-pnacz9OBIp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88329-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88329-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01567.txt.bz2
Content-length: 164
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88329
--- Comment #1 from emsr at gcc dot gnu.org ---
*** Bug 88327 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-628760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 01:59:01 2019
Return-Path: <gcc-bugs-return-628760-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42534 invoked by alias); 11 Jan 2019 01:59:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39270 invoked by uid 48); 11 Jan 2019 01:58:57 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88323] implement C++20 language features.
Date: Fri, 11 Jan 2019 01:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88323-4-WR2NUeVteg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01569.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88323
Bug 88323 depends on bug 88327, which changed state.
Bug 88327 Summary: Implement P0515R3, P0905R1, P1120R0, C++20 std concepts.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88327
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
>From gcc-bugs-return-628761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 03:31:43 2019
Return-Path: <gcc-bugs-return-628761-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29968 invoked by alias); 11 Jan 2019 03:31: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 29886 invoked by uid 48); 11 Jan 2019 03:31:38 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80733] -fstrict-enum ineffective, incorrect -Wtype-limits warning
Date: Fri, 11 Jan 2019 03:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80733-4-bdgeQmbDle@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01570.txt.bz2
Content-length: 213
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80733
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
is this related to any of the new -Wtype-limits bugs that have been
filed/updated lately?
>From gcc-bugs-return-628762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 03:33:48 2019
Return-Path: <gcc-bugs-return-628762-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43401 invoked by alias); 11 Jan 2019 03:33:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41234 invoked by uid 48); 11 Jan 2019 03:33:43 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/83773] Create new switch, -Wmacro-redefined, to control warning for redefined macro
Date: Fri, 11 Jan 2019 03:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-83773-4-mYo4dSeaDa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01571.txt.bz2
Content-length: 968
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83773
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Warning for redefined macro |Create new switch,
|does not have its own |-Wmacro-redefined, to
|-Wsomething switch |control warning for
| |redefined macro
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #2)
> Clang calls it -Wmacro-redefined:
>
> $ clang -fdiagnostics-show-option -Wall -c 83773.c
> 83773.c:2:9: warning: 'AAA' macro redefined [-Wmacro-redefined]
> #define AAA 2
> ^
> 83773.c:1:9: note: previous definition is here
> #define AAA 1
> ^
> 1 warning generated.
> $
Retitling to include that name in the title
>From gcc-bugs-return-628763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 06:04:16 2019
Return-Path: <gcc-bugs-return-628763-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57008 invoked by alias); 11 Jan 2019 06:04:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56930 invoked by uid 48); 11 Jan 2019 06:04:12 -0000
From: "wcventure at 126 dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88629] Heap-buffer-overflow problem in function d_expression_1 in cp-demangle.c, as demonstrated by c++filt
Date: Fri, 11 Jan 2019 06:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: demangler
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wcventure at 126 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-88629-4-eKMvLafgIg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88629-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88629-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01572.txt.bz2
Content-length: 157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
--- Comment #4 from Cheng Wen <wcventure at 126 dot com> ---
Hi, does anyone here to look at this bug?
>From gcc-bugs-return-628764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 06:13:08 2019
Return-Path: <gcc-bugs-return-628764-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110889 invoked by alias); 11 Jan 2019 06:13:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110822 invoked by uid 48); 11 Jan 2019 06:13:04 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59345] _gfortran_internal_pack on compiler generated temps
Date: Fri, 11 Jan 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: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59345-4-6OCWyBeO9q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01573.txt.bz2
Content-length: 227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59345
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
So, test case #1 is fixed.
Scrolling down, there are still a few more to be done, so I'll
leave it open.
>From gcc-bugs-return-628765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 06:32:46 2019
Return-Path: <gcc-bugs-return-628765-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34004 invoked by alias); 11 Jan 2019 06:32: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 33962 invoked by uid 55); 11 Jan 2019 06:32:42 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59345] _gfortran_internal_pack on compiler generated temps
Date: Fri, 11 Jan 2019 06:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59345-4-OUlg5TFnzX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01574.txt.bz2
Content-length: 778
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59345
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Fri Jan 11 06:32:10 2019
New Revision: 267829
URL: https://gcc.gnu.org/viewcvs?rev=267829&root=gcc&view=rev
Log:
2019-01-11 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/59345
* trans-array.c (gfc_conv_parameter_array): Temporary
arrays generated for expressions do not need to be repacked.
2019-01-11 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/59345
* gfortran.dg/internal_pack_16.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/internal_pack_16.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 07:55:11 2019
Return-Path: <gcc-bugs-return-628766-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106373 invoked by alias); 11 Jan 2019 07:55:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106310 invoked by uid 48); 11 Jan 2019 07:55:06 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Fri, 11 Jan 2019 07:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-wzdnLSCAhd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01575.txt.bz2
Content-length: 949
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #9 from Matthias Kretz <kretz at kde dot org> ---
(In reply to emsr from comment #7)
> What does this do?
>
> auto __hi_exp =
> __hi & simd<_T, _Abi>(std::numeric_limits<_T>::infinity()); // no error
component-wise bitwise and of __hi and +inf. Or in other words, it sets all
sign bits and mantissa bits to 0. Consequently `__hi / __hi_exp` returns __hi
with the exponent bits set to 0x3f8 (float) / 0x3ff (double) and the mantissa
bits unchanged.
> Sorry, I have no simd knowlege yet.
It's a very simple idea:
- simd<T> holds simd<T>::size() many values of type T.
- All operators/operations act component-wise.
See Section 9 in wg21.link/N4793 for the last WD of the TS.
> Anyway, doesn't the large scale risk overflow if a, b are large? I guess I'm
> lost.
It basically has the same underflow risks as your implementation does, and no
risk of overflow.
>From gcc-bugs-return-628767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 08:07:50 2019
Return-Path: <gcc-bugs-return-628767-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18051 invoked by alias); 11 Jan 2019 08:07: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 17974 invoked by uid 48); 11 Jan 2019 08:07:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Fri, 11 Jan 2019 08:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88771-4-jGztQVEdxV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01576.txt.bz2
Content-length: 2104
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #9)
> It might be possible for some. I'm not sure how successful it would be for
> others. The thread_jumps pass runs four times and moving the warn_restrict
> pass before its first instance results in dozens of regressions. This
> particular instance of the warning goes away if the warn_restrict pass is
> moved before the second to last threads_jump pass, but that still causes
> regressions. Moving the pass just before the last threads_jump pass doesn't
> help.
Either we need to mark some way all the stmts involved in jump threading and
ignore warning on those by the late warning passes (setting gimple_no_warning_p
on those might be too big hammer, but we have one padding bit close to
no_warning, so use that for gimple_jump_threaded_p), or the late warning passes
need to be moved before the first jump threading and have infrastructure
improvement that they are able to figure stuff out better (say on demand VRP,
strlen if needed, etc.) and after that just turn UB statements into
__builtin_unreachable or __builtin_trap or whatever based on what the user
chooses.
I guess the main problem is that we have some jump threading already before the
(non-early) inlining.
As I said multiple times in the past, the problem with jump threading is that
it tends to create statements, just because it sees some often related
comparison somewhere else, those statements can be specialized for constants or
ranges that actually never occur in the program at runtime, but in many cases
no optimization can figure that out. It is a significant difference if the
user writes strncpy (, , -1U) vs. when it appears through jump threading like
in this example.
>From gcc-bugs-return-628768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 08:43:04 2019
Return-Path: <gcc-bugs-return-628768-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68630 invoked by alias); 11 Jan 2019 08:43:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68566 invoked by uid 48); 11 Jan 2019 08:42:59 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86683] ICE in altivec_expand_vec_perm_const at gcc/config/rs6000/rs6000.c:35074
Date: Fri, 11 Jan 2019 08:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86683-4-vu8WpUplTA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01577.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86683
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |linkw at gcc dot gnu.org
--- Comment #3 from Kewen Lin <linkw at gcc dot gnu.org> ---
The rs6000/altivec.md for those instructions look expected.
Hi Martin, could you still reproduce this with trunk?
>From gcc-bugs-return-628769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 08:50:58 2019
Return-Path: <gcc-bugs-return-628769-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80859 invoked by alias); 11 Jan 2019 08:50:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80782 invoked by uid 48); 11 Jan 2019 08:50:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Fri, 11 Jan 2019 08:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88775-4-xbLnQKRfAf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01578.txt.bz2
Content-length: 2298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45411
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45411&action=edit
gcc9-pr88775-2.patch
The following incremental patch (untested except for this testcase and
comparisons_pointer.cc) fixes that. Unfortunately there is still
ptrs_compare_unequal routine that would need similar treatment, and I'm afraid
it will result in less optimized code.
This patch alone though could be useful even without the other patch, perhaps
if we for pointers like before optimize always. The previous case where we
optimized for integral equality comparisons of pointers only if the offsets are
the same is both incorrect (for zero sized objects) and in many cases not
optimizing enough (it is fine if both offsets are different, all we care is
that the problematic cases where one pointer points to the beginning of one
object and the other points to one past last byte of another one aren't
optimized, everything else can).
C99 says:
"Tw o pointers compare equal if and only if both are null pointers, both are
pointers to the same object (including a pointer to an object and a subobject
at its beginning) or function, both are pointers to one past the last element
of the same array object, or one is a pointer to one past the end of one array
object and the other is a pointer to the start of a different array object that
happens to immediately follow the first array object in the address space."
so I think we have to be conservative and need to treat pointer equality the
same as equality of pointers cast to integral types, the question is if we are
prepared for this for GCC9.
Note, in ptrs_compare_unequal for the one obj, one ptr case (the only
interesting one it handles), we could check if the pointer to the obj is known
to be into the middle of the object (if size is constant and offset too, that
is trivial, other cases might be harder and need more discussions) and in that
case we can do whatever it does now. Otherwise, either punt, or e.g. check if
obj is a global var and the other ptr points to only automatic vars (or if obj
is automatic and ptr points to only global vars). Something else we could do?
>From gcc-bugs-return-628770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:26:45 2019
Return-Path: <gcc-bugs-return-628770-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47288 invoked by alias); 11 Jan 2019 09:26: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 47216 invoked by uid 48); 11 Jan 2019 09:26:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88798] AVX512BW code does not use bit-operations that work on mask registers
Date: Fri, 11 Jan 2019 09:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-88798-4-frkbLSW2df@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01579.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88798
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
See PR88473 for more details.
You can use _kor_mask64 if you want explicitly using the mask operations
instead of GPR.
>From gcc-bugs-return-628771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:34:01 2019
Return-Path: <gcc-bugs-return-628771-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54171 invoked by alias); 11 Jan 2019 09:34: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 54088 invoked by uid 48); 11 Jan 2019 09:33:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/83773] Create new switch, -Wmacro-redefined, to control warning for redefined macro
Date: Fri, 11 Jan 2019 09:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, easyhack
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_severity
Message-ID: <bug-83773-4-7TGZD7nXK5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83773-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83773-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01580.txt.bz2
Content-length: 357
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83773
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |easyhack
Severity|normal |enhancement
>From gcc-bugs-return-628772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:35:27 2019
Return-Path: <gcc-bugs-return-628772-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55670 invoked by alias); 11 Jan 2019 09:35: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 55632 invoked by uid 48); 11 Jan 2019 09:35:23 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88768] Derived type io in conjunction with allocatable component and recursion fails
Date: Fri, 11 Jan 2019 09:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88768-4-5gVe60bUuO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01581.txt.bz2
Content-length: 2005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88768
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Confirmed from 7.4.1 up to trunk (9.0).
My instrumented fortran gives at run time
==50613==ERROR: AddressSanitizer: attempting double-free on 0x6020000002d0 in
thread T0:
#0 0x10a361a7f in wrap_free.part.0 sanitizer_malloc_mac.inc:121
#1 0x10788a1ac in __mod_MOD_recurse (a.out:x86_64+0x1000011ac)
#2 0x10788aad6 in MAIN__ (a.out:x86_64+0x100001ad6)
#3 0x10788ad08 in main (a.out:x86_64+0x100001d08)
#4 0x7fff67115ed8 in start (libdyld.dylib:x86_64+0x16ed8)
0x6020000002d0 is located 0 bytes inside of 8-byte region
[0x6020000002d0,0x6020000002d8)
freed by thread T0 here:
#0 0x10a361a7f in wrap_free.part.0 sanitizer_malloc_mac.inc:121
#1 0x107889e4f in __mod_MOD___final_mod_T (a.out:x86_64+0x100000e4f)
#2 0x10788a2fd in __mod_MOD_set (a.out:x86_64+0x1000012fd)
#3 0x10788a193 in __mod_MOD_recurse (a.out:x86_64+0x100001193)
#4 0x10788aad6 in MAIN__ (a.out:x86_64+0x100001ad6)
#5 0x10788ad08 in main (a.out:x86_64+0x100001d08)
#6 0x7fff67115ed8 in start (libdyld.dylib:x86_64+0x16ed8)
previously allocated by thread T0 here:
#0 0x10a360a0f in wrap_malloc sanitizer_malloc_mac.inc:114
#1 0x10788a710 in __mod_MOD_set (a.out:x86_64+0x100001710)
#2 0x10788a1e4 in __mod_MOD_recurse (a.out:x86_64+0x1000011e4)
#3 0x10788a117 in __mod_MOD_recurse (a.out:x86_64+0x100001117)
#4 0x10788aad6 in MAIN__ (a.out:x86_64+0x100001ad6)
#5 0x10788ad08 in main (a.out:x86_64+0x100001d08)
#6 0x7fff67115ed8 in start (libdyld.dylib:x86_64+0x16ed8)
>From gcc-bugs-return-628773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:41:34 2019
Return-Path: <gcc-bugs-return-628773-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84049 invoked by alias); 11 Jan 2019 09:41:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83939 invoked by uid 48); 11 Jan 2019 09:41:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87305] [9 Regression] Segfault in end_hard_regno in setup_live_pseudos_and_spill_after_risky_transforms on aarch64 big-endian
Date: Fri, 11 Jan 2019 09:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87305-4-TU5eG4YCyi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01582.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87305
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:45:53 2019
Return-Path: <gcc-bugs-return-628774-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103288 invoked by alias); 11 Jan 2019 09:45: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 103233 invoked by uid 48); 11 Jan 2019 09:45:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88688] Incorrect association in SELECT TYPE
Date: Fri, 11 Jan 2019 09: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: 8.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88688-4-VXNH9GpeN9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88688-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88688-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01583.txt.bz2
Content-length: 664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88688
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I confirm the behavior from at least 4.8 up to trunk (9.0).
> It's not clear what the correct behavior should be. ...
May be the question could be asked at comp.lang.fortran.
>From gcc-bugs-return-628775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:50:17 2019
Return-Path: <gcc-bugs-return-628775-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108067 invoked by alias); 11 Jan 2019 09:50: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 107983 invoked by uid 48); 11 Jan 2019 09:50:12 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86683] ICE in altivec_expand_vec_perm_const at gcc/config/rs6000/rs6000.c:35074
Date: Fri, 11 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86683-4-6Aw9jixDCY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01584.txt.bz2
Content-length: 618
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86683
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> ---
Can't reproduce either. Maybe it got fixed with r264675 aka PR87149 fix?
Before that change indeed those could be CODE_FOR_nothing if using a cross
without assembler or with too old assembler that didn't support the power8
instructions.
>From gcc-bugs-return-628776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 09:52:53 2019
Return-Path: <gcc-bugs-return-628776-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128809 invoked by alias); 11 Jan 2019 09:52: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 128548 invoked by uid 48); 11 Jan 2019 09:52:48 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88555] [9 Regression] Pack expansion fails
Date: Fri, 11 Jan 2019 09:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88555-4-VV6npIZEB0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88555-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88555-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01585.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88555
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Maybe dup of PR88312?
>From gcc-bugs-return-628777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:04:40 2019
Return-Path: <gcc-bugs-return-628777-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11712 invoked by alias); 11 Jan 2019 10:04:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11576 invoked by uid 48); 11 Jan 2019 10:04:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88296] [9 Regression] Infinite loop in lra_split_hard_reg_for
Date: Fri, 11 Jan 2019 10:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: memory-hog, needs-bisection, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc
Message-ID: <bug-88296-4-cwdSUmRUjD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88296-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88296-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01586.txt.bz2
Content-length: 835
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88296
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
CC| |jakub at gcc dot gnu.org,
| |vmakarov at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
The hang started with r266422 aka PR88157 fix and got fixed (or made latent)
with r266862 aka the second PR88282 fix.
I'm going to include the testcase into the testsuite, for Vlad the question is
just whether r266862 is a real fix or just made it latent. Given that both are
IRA costs changes, I assume it is a real fix.
>From gcc-bugs-return-628778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:12:07 2019
Return-Path: <gcc-bugs-return-628778-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16348 invoked by alias); 11 Jan 2019 10:12: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 16240 invoked by uid 48); 11 Jan 2019 10:12:02 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Fri, 11 Jan 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88044-4-zDdk32nZ7V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01587.txt.bz2
Content-length: 770
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88044
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Could you please replace
(1) 'do n = 0, 3' with 'do n = 2, 3', and
(2) 'do n = 0, 3' with 'do n = 0, 0'?
I am not 100% confident about what 's = transfer(vs, s)' is supposed to do for
zero-sized arrays/strings. In any case the length should never be greater than
2.
>From gcc-bugs-return-628779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:17:50 2019
Return-Path: <gcc-bugs-return-628779-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73000 invoked by alias); 11 Jan 2019 10:17:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72951 invoked by uid 55); 11 Jan 2019 10:17:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88296] [9 Regression] Infinite loop in lra_split_hard_reg_for
Date: Fri, 11 Jan 2019 10:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: memory-hog, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88296-4-kMvdFMgq97@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88296-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88296-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01588.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88296
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 11 10:17:12 2019
New Revision: 267831
URL: https://gcc.gnu.org/viewcvs?rev=267831&root=gcc&view=rev
Log:
PR rtl-optimization/88296
* gcc.target/i386/pr88296.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr88296.c
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:38:22 2019
Return-Path: <gcc-bugs-return-628780-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61429 invoked by alias); 11 Jan 2019 10:38: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 61380 invoked by uid 48); 11 Jan 2019 10:38:17 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88799] Arm -mcpu=PROCESSOR does not result in assembly directives for .arch and .arch_extension
Date: Fri, 11 Jan 2019 10:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88799-4-rxDpVZEjAn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01589.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88799
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #1 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
GCC needs to be taught about the mp extension to armv7-a.
>From gcc-bugs-return-628781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:46:21 2019
Return-Path: <gcc-bugs-return-628781-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69028 invoked by alias); 11 Jan 2019 10:46:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68698 invoked by uid 48); 11 Jan 2019 10:45:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88785] [9 Regression] ICE in as_a, at machmode.h:353
Date: Fri, 11 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88785-4-IXYZoWTEVZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88785-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01590.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88785
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:47:07 2019
Return-Path: <gcc-bugs-return-628782-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70496 invoked by alias); 11 Jan 2019 10:47:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70417 invoked by uid 48); 11 Jan 2019 10:47:01 -0000
From: "tgrabiec at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88800] New: Spurious -Werror=array-bounds for non-taken branch
Date: Fri, 11 Jan 2019 10:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tgrabiec 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-88800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01591.txt.bz2
Content-length: 5300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88800
Bug ID: 88800
Summary: Spurious -Werror=array-bounds for non-taken branch
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: tgrabiec at gmail dot com
Target Milestone: ---
Link to godbolt: https://godbolt.org/z/JXfV2y
gcc flags: -Wall -Werror
Compiles fine with gcc 7.4, errors on 8.2 due to -Warray-bounds.
=====
#include <variant>
#include <stdint.h>
#include <assert.h>
#include <memory>
#include <unordered_map>
#include <type_traits>
#include <string_view>
#include <cstring>
using bytes_view = std::string_view;
struct blob_storage {
struct [[gnu::packed]] ref_type {
blob_storage* ptr;
ref_type() {}
ref_type(blob_storage* ptr) : ptr(ptr) {}
operator blob_storage*() const { return ptr; }
blob_storage* operator->() const { return ptr; }
blob_storage& operator*() const { return *ptr; }
};
using size_type = uint32_t;
using char_type = bytes_view::value_type;
ref_type* backref;
size_type size;
size_type frag_size;
ref_type next;
char_type data[];
blob_storage(ref_type* backref, size_type size, size_type frag_size)
noexcept
: backref(backref)
, size(size)
, frag_size(frag_size)
, next(nullptr)
{
*backref = this;
}
blob_storage(blob_storage&& o) noexcept
: backref(o.backref)
, size(o.size)
, frag_size(o.frag_size)
, next(o.next)
{
*backref = this;
o.next = nullptr;
if (next) {
next->backref = &next;
}
memcpy(data, o.data, frag_size);
}
} __attribute__((packed));
class [[gnu::packed]] managed_bytes {
static constexpr size_t max_inline_size = 15;
struct small_blob {
bytes_view::value_type data[max_inline_size];
};
union [[gnu::packed]] u {
u() {}
~u() {}
blob_storage::ref_type ptr;
small_blob small;
} _u;
int8_t _size; // -1 -> use blob_storage
private:
bool external() const {
return _size < 0;
}
public:
using size_type = blob_storage::size_type;
struct initialized_later {};
managed_bytes(initialized_later, size_type size) {
if (size <= max_inline_size) {
_size = size;
} else {
_size = -1;
auto now = size;
void* p = malloc(sizeof(blob_storage) + now);
new (p) blob_storage(&_u.ptr, size, now);
}
}
managed_bytes(bytes_view v) : managed_bytes(initialized_later(), v.size())
{
if (!external()) {
std::copy(v.begin(), v.end(), _u.small.data);
// ^^^^^^^^^^^^^^^ HERE ^^^^^^^^^^^^^^^^^^^
return;
}
auto p = v.data();
auto s = v.size();
auto b = _u.ptr;
while (s) {
memcpy(b->data, p, b->frag_size);
p += b->frag_size;
s -= b->frag_size;
b = b->next;
}
assert(!b);
}
};
static_assert(sizeof(managed_bytes) == 16, "too large");
int main() {
char c[16] = { 0, };
bytes_view v(c, 16);
managed_bytes b(v);
}
=====
GCC output:
In static member function ‘static _Tp* std::__copy_move<_IsMove, true,
std::random_access_iterator_tag>::__copy_m(const _Tp*, const _Tp*, _Tp*) [with
_Tp = signed char; bool _IsMove = false]’,
inlined from ‘_OI std::__copy_move_a(_II, _II, _OI) [with bool _IsMove =
false; _II = const signed char*; _OI = signed char*]’ at
/usr/include/c++/8/bits/stl_algobase.h:386:30,
inlined from ‘_OI std::__copy_move_a2(_II, _II, _OI) [with bool _IsMove =
false; _II = const signed char*; _OI = signed char*]’ at
/usr/include/c++/8/bits/stl_algobase.h:422:45,
inlined from ‘_OI std::copy(_II, _II, _OI) [with _II = const signed char*;
_OI = signed char*]’ at /usr/include/c++/8/bits/stl_algobase.h:455:8,
inlined from ‘managed_bytes::managed_bytes(bytes_view)’ at
./utils/managed_bytes.hh:195:22,
inlined from ‘managed_bytes::managed_bytes(const bytes&)’ at
./utils/managed_bytes.hh:162:77,
inlined from ‘dht::token dht::bytes_to_token(bytes)’ at
dht/random_partitioner.cc:68:57,
inlined from ‘dht::token dht::random_partitioner::get_token(bytes)’ at
dht/random_partitioner.cc:85:39:
/usr/include/c++/8/bits/stl_algobase.h:368:23: error: ‘void*
__builtin_memmove(void*, const void*, long unsigned int)’ offset 16 from the
object at ‘<anonymous>’ is out of the bounds of referenced subobject
‘managed_bytes::small_blob::data’ with type ‘signed char [15]’ at offset 0
[-Werror=array-bounds]
__builtin_memmove(__result, __first, sizeof(_Tp) * _Num);
~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
{code}
{code}
>From gcc-bugs-return-628783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:51:47 2019
Return-Path: <gcc-bugs-return-628783-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89736 invoked by alias); 11 Jan 2019 10:51:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88407 invoked by uid 48); 11 Jan 2019 10:51:43 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/53294] Optimize out some exception code
Date: Fri, 11 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: antoshkka at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-53294-4-0KqSB2QR30@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-53294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-53294-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01592.txt.bz2
Content-length: 137
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53294
--- Comment #3 from Antony Polukhin <antoshkka at gmail dot com> ---
Any progress?
>From gcc-bugs-return-628784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 10:56:43 2019
Return-Path: <gcc-bugs-return-628784-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93831 invoked by alias); 11 Jan 2019 10:56:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93772 invoked by uid 48); 11 Jan 2019 10:56:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88750] [9 Regression] runtime error in statically linked binaries
Date: Fri, 11 Jan 2019 10:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88750-4-KExlUZLVmV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88750-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01593.txt.bz2
Content-length: 2175
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88750
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #35 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jürgen Reuter from comment #33)
> (In reply to Iain Sandoe from comment #32)
> > (In reply to Jürgen Reuter from comment #31)
> > > Then I get tons of duplicate symbol lines.
> >
> > ah well, not so simple then,
> >
> > then I think the next step is for you to identify the last working revision
> > of the compiler - we can then analyse what the change was that caused the
> > difference and determine if that's a real regression or just exposing a
> > build system issue.
>
> I fear I don't have the capacities to do that right now.
I'm afraid without that there is nothing we can do about it.
While bisection can be time consuming, it doesn't need to be time consuming for
you (at least not that much), it can be scripted.
If you have some compiler that works (guess because this PR got marked as [9
Regression] gcc 8.x works for you) and some compiler that doesn't, I see three
options for the bisection.
One is build with the "good" compiler and "bad" compiler in two separate
directories, verify one works and one doesn't, then make a copy of one of those
directories and bisect between the *.o files, start with half "good" ones and
half "bad" ones and from the outcome try to narrow it to a particular
problematic *.o file. Another one is similar, but if you have "good" and "bad"
options, such as e.g. with -O0 it works and -O2 it doesn't, again bisect object
files to find the problematic one.
And the last one is try to bisect the compiler, after verifying "good"/"bad"
try to build gcc from half way in between those revisions etc.
The bisection to a particular *.o file is something that might help with the
bisection of compilers, you only can bisect the compilation of the problematic
TU and on that check what actually changed.
>From gcc-bugs-return-628785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:01:50 2019
Return-Path: <gcc-bugs-return-628785-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100985 invoked by alias); 11 Jan 2019 11:01: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 100887 invoked by uid 48); 11 Jan 2019 11:01:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88752] 8/9 Regression] ICE in enclosing_instantiation_of, at cp/pt.c:13328
Date: Fri, 11 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc target_milestone short_desc
Message-ID: <bug-88752-4-g2iEjgIf1K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88752-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01594.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88752
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |8.3
Summary|ICE in |8/9 Regression] ICE in
|enclosing_instantiation_of, |enclosing_instantiation_of,
|at cp/pt.c:13328 |at cp/pt.c:13328
>From gcc-bugs-return-628786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:12:21 2019
Return-Path: <gcc-bugs-return-628786-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76243 invoked by alias); 11 Jan 2019 11:12:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76197 invoked by uid 48); 11 Jan 2019 11:12:16 -0000
From: "tgrabiec at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88800] Spurious -Werror=array-bounds for non-taken branch
Date: Fri, 11 Jan 2019 11:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tgrabiec 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-88800-4-JEC4kbb5Oj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01595.txt.bz2
Content-length: 231
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88800
--- Comment #1 from Tomasz Grabiec <tgrabiec at gmail dot com> ---
The gcc flags given in the description were incomplete, should be:
gcc flags: -Wall -Werror -std=c++17 -O2
>From gcc-bugs-return-628787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:33:50 2019
Return-Path: <gcc-bugs-return-628787-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108653 invoked by alias); 11 Jan 2019 11: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 108582 invoked by uid 48); 11 Jan 2019 11:33:46 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Fri, 11 Jan 2019 11: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: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to attachments.created
Message-ID: <bug-88788-4-7eTFrTZlts@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01596.txt.bz2
Content-length: 1728
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
prathamesh3492 at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |prathamesh3492 at gcc dot gnu.org
--- Comment #7 from prathamesh3492 at gcc dot gnu.org ---
Created attachment 45412
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45412&action=edit
Untested fix
Hi,
The issue seems to be recursively calling malloc_candidate_p_1 with duplicate
arguments, for example, with above test-case, it shows following trace:
https://pastebin.com/tF5Qg06X
We can see it is calling malloc_candidate_p_1 with resultobj_164=PHI<...>
thrice because resultobj_164 appears 3 times as a phi-arg in:
resultobj_165 = PHI <_12(12), resultobj_164(13), resultobj_164(14),
resultobj_164(15)>
I think it's more of a compile time hog rather than infinite recursion
happening. To avoid that, I simply skipped walking over duplicate args in the
phi in the attached patch:
+ bool skip_dup_arg = false;
+ for (unsigned j = i; j > 0; j--)
+ if (operand_equal_p (gimple_phi_arg_def (phi, j - 1), arg, 0))
+ {
+ skip_dup_arg = true;
+ break;
+ }
+ if (skip_dup_arg)
+ continue;
+
which appears to compile both the tests again.
I assume a phi stmt usually won't have more than 4 or 5 args, so the loop
shouldn't be too slow in practice ? I will be grateful for any other
suggestions. For the larger test-case it shows 164.08 wall seconds time for
compilation.
Thanks,
Prathamesh
>From gcc-bugs-return-628788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:38:52 2019
Return-Path: <gcc-bugs-return-628788-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114924 invoked by alias); 11 Jan 2019 11:38: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 114886 invoked by uid 48); 11 Jan 2019 11:38:47 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88801] New: [9 Regression] Performance regression on 473.astar on aarch64
Date: Fri, 11 Jan 2019 11:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01597.txt.bz2
Content-length: 998
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88801
Bug ID: 88801
Summary: [9 Regression] Performance regression on 473.astar on
aarch64
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: ktkachov at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Target Milestone: ---
Target: aarch64
We've noticed a performance regression recently on 473.astar on aarch64 (a
Cortex-A57 platform).
On our systems we see about 8% slowdown and I also see a 4% slowdown (among
other similar slowdowns) at:
https://lnt.opensuse.org/db_default/v4/SPEC/1947
https://lnt.opensuse.org/db_default/v4/SPEC/graph?plot.0=13.260.0&highlight_run=1947
I suspect this is something to do with the recent inlining tweaks.
>From gcc-bugs-return-628790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:40:52 2019
Return-Path: <gcc-bugs-return-628790-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130823 invoked by alias); 11 Jan 2019 11:40: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 130774 invoked by uid 48); 11 Jan 2019 11:40:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88125] Erroneous duplicate "basic_stringbuf" symbol entry in libstdc++ gnu.ver file.
Date: Fri, 11 Jan 2019 11:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88125-4-3eFrjaZ2Qe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88125-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88125-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01599.txt.bz2
Content-length: 2262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88125
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Done.
Do we also want this patch?
--- a/libstdc++-v3/config/abi/pre/gnu.ver
+++ b/libstdc++-v3/config/abi/pre/gnu.ver
@@ -1123,6 +1123,7 @@ GLIBCXX_3.4.4 {
GLIBCXX_3.4.5 {
+#ifndef HAVE_SYMVER_SYMBOL_RENAMING_RUNTIME_SUPPORT
# std::string
_ZNKSs11_M_disjunctEPKc;
_ZNKSs15_M_check_lengthE[jmy][jmy]PKc;
@@ -1154,6 +1155,7 @@ GLIBCXX_3.4.5 {
#if !defined(__sun__) && !defined(__svr4__)
_ZNSt19istreambuf_iteratorI[cw]St11char_traitsI[cw]EEppEv;
#endif
+#endif
} GLIBCXX_3.4.4;
GLIBCXX_3.4.6 {
The patterns in the GLIBCXX_3.4.5 node are duplicates of ones in the base
version, that depend on that macro (starting at line 1024):
#ifdef HAVE_SYMVER_SYMBOL_RENAMING_RUNTIME_SUPPORT
# GLIBCXX_ABI compatibility only.
# std::string
_ZNKSs11_M_disjunctEPKc;
_ZNKSs15_M_check_lengthE[jmy][jmy]PKc;
_ZNSs4_Rep26_M_set_length_and_sharableE*;
_ZNSs7_M_copyEPcPKc[jmy];
_ZNSs7_M_moveEPcPKc[jmy];
_ZNSs9_M_assignEPc[jmy]c;
# std::wstring
_ZNKSbIwSt11char_traitsIwESaIwEE11_M_disjunctEPKw;
_ZNKSbIwSt11char_traitsIwESaIwEE15_M_check_lengthE[jmy][jmy]PKc;
_ZNSbIwSt11char_traitsIwESaIwEE4_Rep26_M_set_length_and_sharableE*;
_ZNSbIwSt11char_traitsIwESaIwEE7_M_copyEPwPKw[jmy];
_ZNSbIwSt11char_traitsIwESaIwEE7_M_moveEPwPKw[jmy];
_ZNSbIwSt11char_traitsIwESaIwEE9_M_assignEPw[jmy]w;
_ZNKSt13basic_fstreamI[cw]St11char_traitsI[cw]EE7is_openEv;
_ZNKSt14basic_ifstreamI[cw]St11char_traitsI[cw]EE7is_openEv;
_ZNKSt14basic_ofstreamI[cw]St11char_traitsI[cw]EE7is_openEv;
_ZNSi6ignoreE[ilvx];
_ZNSt13basic_istreamIwSt11char_traitsIwEE6ignoreE[ilvx];
_ZNSt11char_traitsI[cw]E2eqERK[cw]S2_;
_ZNSt19istreambuf_iteratorI[cw]St11char_traitsI[cw]EEppEv;
#endif
This means that when HAVE_SYMVER_SYMBOL_RENAMING_RUNTIME_SUPPORT is defined
those patterns appear twice. Those symbols are meant to have multiple versions
(as Brooks pointed out in comment 0) but they are given those versions by asm
.symver directive in src/c++98/compatibility.cc so I don't think the dups in
the linker script are needed. But I might be misunderstanding something.
>From gcc-bugs-return-628789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:40:22 2019
Return-Path: <gcc-bugs-return-628789-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129754 invoked by alias); 11 Jan 2019 11:40:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129696 invoked by uid 55); 11 Jan 2019 11:40:17 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88125] Erroneous duplicate "basic_stringbuf" symbol entry in libstdc++ gnu.ver file.
Date: Fri, 11 Jan 2019 11:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88125-4-zqjwggQof9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88125-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88125-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01598.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88125
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Jan 11 11:39:45 2019
New Revision: 267834
URL: https://gcc.gnu.org/viewcvs?rev=267834&root=gcc&view=rev
Log:
PR libstdc++/88125 remove duplicate entry in linker script
PR libstdc++/88125
* config/abi/pre/gnu.ver (GLIBCXX_3.4.6): Remove unused duplicate
pattern for std::basic_stringbuf::str().
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/config/abi/pre/gnu.ver
>From gcc-bugs-return-628792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:43:33 2019
Return-Path: <gcc-bugs-return-628792-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3158 invoked by alias); 11 Jan 2019 11:43: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 3037 invoked by uid 48); 11 Jan 2019 11:43:28 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88801] [9 Regression] Performance regression on 473.astar on aarch64
Date: Fri, 11 Jan 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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 blocked everconfirmed
Message-ID: <bug-88801-4-Fxf0uB7eSR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01601.txt.bz2
Content-length: 775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88801
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |needs-bisection
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Blocks| |26163
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Can you please bisect that?
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
[Bug 26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
>From gcc-bugs-return-628791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:43:12 2019
Return-Path: <gcc-bugs-return-628791-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2190 invoked by alias); 11 Jan 2019 11:43: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 2098 invoked by uid 48); 11 Jan 2019 11:43:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Fri, 11 Jan 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-VxtytDYrQP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01600.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I don't see how that can help.
First of all, the duplicate SSA_NAMEs don't have to appear just in the same
PHI, you can have them in multiple different PHIs too.
And, you can have loops there as well, either directly (e.g. a PHI result where
one or more arguments of the PHI is equal to the PHI result), or indirectly.
So, you probably need to remember the outcome of calling the function on some
SSA_NAME already before, and you need to deal with the loops somehow (ignore
back edges is one strategy, there are various others, look at other passes).
>From gcc-bugs-return-628793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:44:20 2019
Return-Path: <gcc-bugs-return-628793-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4329 invoked by alias); 11 Jan 2019 11:44: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 4278 invoked by uid 48); 11 Jan 2019 11:44:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Fri, 11 Jan 2019 11:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-rmkH8rwxY5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01602.txt.bz2
Content-length: 251
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And no, you casn't rely on phis having just a few arguments, there are phis
with tens of thousands of arguments in real-world code.
>From gcc-bugs-return-628794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:46:35 2019
Return-Path: <gcc-bugs-return-628794-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8110 invoked by alias); 11 Jan 2019 11:46:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7740 invoked by uid 48); 11 Jan 2019 11:46:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86683] ICE in altivec_expand_vec_perm_const at gcc/config/rs6000/rs6000.c:35074
Date: Fri, 11 Jan 2019 11:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86683-4-Mx8jN6colE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01603.txt.bz2
Content-length: 477
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86683
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
Yes, I can also confirm that it works for me.
>From gcc-bugs-return-628795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:47:03 2019
Return-Path: <gcc-bugs-return-628795-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9429 invoked by alias); 11 Jan 2019 11:47:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9291 invoked by uid 48); 11 Jan 2019 11:46:58 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Fri, 11 Jan 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: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88787-4-u990EBrcUx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01604.txt.bz2
Content-length: 466
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Indeed, just verified, the 30_threads/ constexpr.cc issues were introduced in
r265788.
>From gcc-bugs-return-628796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:49:20 2019
Return-Path: <gcc-bugs-return-628796-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20258 invoked by alias); 11 Jan 2019 11:49: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 19578 invoked by uid 48); 11 Jan 2019 11:49:13 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Fri, 11 Jan 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88791-4-esnNbIqrRf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01605.txt.bz2
Content-length: 563
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Can you please provide a test-case? Or build steps how to build your
application?
>From gcc-bugs-return-628797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:50:00 2019
Return-Path: <gcc-bugs-return-628797-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22605 invoked by alias); 11 Jan 2019 11:50: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 22546 invoked by uid 48); 11 Jan 2019 11:49:56 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Fri, 11 Jan 2019 11:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88791-4-i2r5sabkKA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01606.txt.bz2
Content-length: 173
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
And please try GCC 8.2, maybe it has been fixed?
>From gcc-bugs-return-628798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 11:52:41 2019
Return-Path: <gcc-bugs-return-628798-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32804 invoked by alias); 11 Jan 2019 11:52: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 32772 invoked by uid 48); 11 Jan 2019 11:52:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Fri, 11 Jan 2019 11:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-myND20tAmf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01607.txt.bz2
Content-length: 655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to ДилÑн Палаузов from comment #7)
> Why doesn’t GCC “make install†put the linker plugin under
> $libdir/bfd-plugins and how are program ./configure’s supposed to be written
> in a way, that LTO works with both Clang and GCC?
It's a location which is automatically used by nm,ar,ranlib,ld when searching
for plugins. Should work automatically when using clang, then object files will
use proper llvm LTO plugin.
>From gcc-bugs-return-628800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:04:46 2019
Return-Path: <gcc-bugs-return-628800-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102001 invoked by alias); 11 Jan 2019 12:04:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101918 invoked by uid 48); 11 Jan 2019 12:04:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88787] [9 regression] C++ constexpr seems to not get expanded
Date: Fri, 11 Jan 2019 12:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88787-4-9MWHeUngQl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88787-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01609.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88787
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-628799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:04:29 2019
Return-Path: <gcc-bugs-return-628799-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101210 invoked by alias); 11 Jan 2019 12:04:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101123 invoked by uid 48); 11 Jan 2019 12:04:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88616] [9 Regression] ICE in gimplify_expr at gcc/gimplify.c:13363
Date: Fri, 11 Jan 2019 12:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88616-4-n6eAwXz7Xq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88616-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01608.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88616
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-628801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:05:47 2019
Return-Path: <gcc-bugs-return-628801-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103424 invoked by alias); 11 Jan 2019 12:05: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 103365 invoked by uid 48); 11 Jan 2019 12:05:42 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Fri, 11 Jan 2019 12:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-g9fqo6IOkh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01610.txt.bz2
Content-length: 575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #9 from ДилÑн Палаузов <dilyan.palauzov at aegee dot org> ---
Yes, $(libdir)/bfd-plugins is a location automatically scanned by ar/nm/ranlib.
The question is, why GCC’s “make install†does not put there its linker plugin.
As long as nobody installs the linker plugins under $(libdir)/bfd-plugins, how
are program ./configure’s supposed to be written in a way, that LTO works with
both Clang and GCC?
>From gcc-bugs-return-628802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:06:31 2019
Return-Path: <gcc-bugs-return-628802-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106656 invoked by alias); 11 Jan 2019 12:06:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106581 invoked by uid 55); 11 Jan 2019 12:06:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Fri, 11 Jan 2019 12:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-8ydhDjPwIT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01611.txt.bz2
Content-length: 492
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 11 12:05:54 2019
New Revision: 267839
URL: https://gcc.gnu.org/viewcvs?rev=267839&root=gcc&view=rev
Log:
PR bootstrap/88714
* passes.c (finish_optimization_passes): Call print_combine_total_stats
inside of pass_combine_1 dump rather than pass_profile_1.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/passes.c
>From gcc-bugs-return-628803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:14:37 2019
Return-Path: <gcc-bugs-return-628803-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115904 invoked by alias); 11 Jan 2019 12:14:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115811 invoked by uid 48); 11 Jan 2019 12:14:32 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Fri, 11 Jan 2019 12:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4-Prw9OWzE0f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01612.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #3 from dominik.strasser@onespin-solutions.com ---
Unfortunately my application is huge and spawns many threads.
Can you propose some debugging aid. I am building gcc myself, so I can add
anything to libasan that you want.
>From gcc-bugs-return-628804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:22:54 2019
Return-Path: <gcc-bugs-return-628804-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 504 invoked by alias); 11 Jan 2019 12:22:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 420 invoked by uid 48); 11 Jan 2019 12:22:50 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Fri, 11 Jan 2019 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88791-4-z9u7GMlDJm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01613.txt.bz2
Content-length: 496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to dominik.strasser from comment #3)
> Unfortunately my application is huge and spawns many threads.
>
> Can you propose some debugging aid. I am building gcc myself, so I can add
> anything to libasan that you want.
Ok, then please try current GCC trunk.
And you can also use:
ASAN_OPTIONS="verbosity=3:debug=1"
that should provide more diagnostics.
>From gcc-bugs-return-628805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:32:20 2019
Return-Path: <gcc-bugs-return-628805-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16294 invoked by alias); 11 Jan 2019 12:32: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 16216 invoked by uid 48); 11 Jan 2019 12:32:15 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86683] ICE in altivec_expand_vec_perm_const at gcc/config/rs6000/rs6000.c:35074
Date: Fri, 11 Jan 2019 12:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-86683-4-EMDxb9WeGy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86683-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01614.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86683
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|WORKSFORME |FIXED
--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Ah, with an assembler without p8 support. Yes that should be fixed by r264675.
>From gcc-bugs-return-628806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:46:49 2019
Return-Path: <gcc-bugs-return-628806-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52780 invoked by alias); 11 Jan 2019 12:46: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 52699 invoked by uid 48); 11 Jan 2019 12:46:45 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Fri, 11 Jan 2019 12:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-NkhSvwt0qg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01615.txt.bz2
Content-length: 369
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #10 from prathamesh3492 at gcc dot gnu.org ---
Oops, I didn't realize there could be loop within phi (phi result being an arg
too). I will try to come up with a better approach for handling nested PHI's.
In the meantime, for stage 4, should I revert the recursive calling hunk ?
Thanks,
Prathamesh
>From gcc-bugs-return-628807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:51:08 2019
Return-Path: <gcc-bugs-return-628807-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73977 invoked by alias); 11 Jan 2019 12:51:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71589 invoked by uid 48); 11 Jan 2019 12:51:04 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88786] Expand vector copysign (and xorsign) operations in the vectoriser
Date: Fri, 11 Jan 2019 12:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88786-4-k5rDDtgyeR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01616.txt.bz2
Content-length: 729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88786
--- Comment #2 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #1)
> I think it's a bit too low-level and having the higher-level op benefits
> later optimizations (match.pd patterns, etc.)
match.pd will already have seen the scalar form though, so I think
we should assume that any optimisations like that have already
been applied.
AFAIK the only copysign optimisation that happens after vectorisation
is the xorsign one. But in a way that's working around the fact that
we *haven't* exposed the individual operations. The xorsign_optab only
exists as a way of representing the result of a particular fold.
>From gcc-bugs-return-628808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 12:56:33 2019
Return-Path: <gcc-bugs-return-628808-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89422 invoked by alias); 11 Jan 2019 12:56: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 89335 invoked by uid 55); 11 Jan 2019 12:56:27 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Fri, 11 Jan 2019 12:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88796-4-My3pCzFJWm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01617.txt.bz2
Content-length: 2891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On January 10, 2019 8:49:58 PM GMT+01:00, "jakub at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
>
>--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
>We also use magic alias set e.g. directly in RTL DSE
>(ALIAS_SET_MEMORY_BARRIER).
>
>Anyway, there are multiple MEMs that need to be treated specially. For
>the TLS
>cases, it is e.g. on x86_64:
>(insn 15 27 16 2 (parallel [
> (set (reg:CCZ 17 flags)
> (unspec:CCZ [
> (mem/v/f/c:DI (plus:DI (reg/f:DI 19 frame)
> (const_int -8 [0xfffffffffffffff8])) [3
>D.1946+0 S8 A64])
> (mem/f:DI (const_int 40 [0x28]) [4
>MEM[(<address-space-1> long unsigned int *)40B]+0 S8 A64 AS1])
> ] UNSPEC_SP_TEST))
> (clobber (scratch:DI))
> ]) "pr87370.c":23:1 978 {stack_protect_test_di}
> (nil))
>
>so there is MEM_VOLATILE_P stack canary MEM where we could use a
>special
>MEM_EXPR, after all, we apparently already have there a VAR_DECL, and
>can
>check that in crtl->stack_protect_guard, so this part shouldn't be that
>hard,
>except that we for some strange reason treat all volatile reads as
>killing
>everything, so we'd need to ignore MEM_VOLATILE_P for that special
>case. The
>initial set ssp is a store to a volatile mem, so perhaps just ignoring
>such
>MEMs altogether would DTRT.
>The next thing is the TLS MEM, which has some MEM_EXPR in there (and
>isn't
>volatile). Can that use some magic VAR_DECL in MEM_EXPR instead of the
>expression it uses? It is weird that outside of MEM_EXPR it actually
>doesn't
>record anywhere that it is another address space. Can we ignore this
>MEM
>altogether too?
>
>Finally, with -mstack-protector-guard=global, we have e.g.:
>(insn 13 25 14 2 (parallel [
> (set (reg:CCZ 17 flags)
> (unspec:CCZ [
> (mem/v/f/c:DI (plus:DI (reg/f:DI 19 frame)
> (const_int -8 [0xfffffffffffffff8])) [3
>D.1946+0 S8 A64])
> (mem/v/f/c:DI (symbol_ref:DI ("__stack_chk_guard")
>[flags 0x40] <var_decl 0x7f348fa555a0 __stack_chk_guard>) [3
>__stack_ch
>k_guard+0 S8 A64])
> ] UNSPEC_SP_TEST))
> (clobber (scratch:DI))
> ]) "pr87370.c":23:1 978 {stack_protect_test_di}
> (nil))
>
>so there is yet another MEM_VOLATILE_P memory. Wonder why we are so
>conservative about the volatile MEM reads, e.g. for a volatile MEM read
>from a
>var I don't see why it should kill frame related stores.
Looks like DSE is too conservative here for no good reason? BTW, I'd prefer a
alias analysis solution without special casing things in DSE.
>From gcc-bugs-return-628809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 13:20:38 2019
Return-Path: <gcc-bugs-return-628809-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71682 invoked by alias); 11 Jan 2019 13: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 71598 invoked by uid 55); 11 Jan 2019 13:20:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88758] [9 Regression] 186.crafty in SPEC CPU 2000 failed to build
Date: Fri, 11 Jan 2019 13:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88758-4-vTthNMjOBd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88758-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01618.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88758
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Fri Jan 11 13:20:01 2019
New Revision: 267840
URL: https://gcc.gnu.org/viewcvs?rev=267840&root=gcc&view=rev
Log:
Add a testcase (PR middle-end/88758).
2019-01-11 Martin Liska <mliska@suse.cz>
PR middle-end/88758
* g++.dg/lto/pr88758_0.C: New test.
* g++.dg/lto/pr88758_1.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/lto/pr88758_0.C
trunk/gcc/testsuite/g++.dg/lto/pr88758_1.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 13:49:21 2019
Return-Path: <gcc-bugs-return-628810-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104191 invoked by alias); 11 Jan 2019 13:49: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 99127 invoked by uid 48); 11 Jan 2019 13:49:17 -0000
From: "tom at kera dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88802] New: std::hash<std::nullptr_t> not implemented
Date: Fri, 11 Jan 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tom at kera dot name
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01619.txt.bz2
Content-length: 948
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88802
Bug ID: 88802
Summary: std::hash<std::nullptr_t> not implemented
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: tom at kera dot name
Target Milestone: ---
See https://stackoverflow.com/q/54147254/560648.
C++17 requires that std::hash<std::nullptr_t> be provided. MSVS does, but dev
libstdc++ doesn't (and neither does libc++). This seems to be the case on trunk
still.
#include <functional>
int main()
{
std::hash<std::nullptr_t> h;
return h(nullptr);
}
Result:
main.cpp: In function 'int main()':
main.cpp:4:31: error: use of deleted function
'std::hash<std::nullptr_t>::hash()'
std::hash<std::nullptr_t> h;
Expected result:
Good build and some return code.
>From gcc-bugs-return-628811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 13:51:01 2019
Return-Path: <gcc-bugs-return-628811-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13132 invoked by alias); 11 Jan 2019 13:51:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13063 invoked by uid 48); 11 Jan 2019 13:50:57 -0000
From: "tom at kera dot name" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88802] std::hash<std::nullptr_t> not implemented
Date: Fri, 11 Jan 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: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tom at kera dot name
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88802-4-dr2PPfh6DT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01620.txt.bz2
Content-length: 753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88802
--- Comment #1 from Tomalak Geret'kal <tom at kera dot name> ---
[unord.hash]/2
> Each specialization of hash is either enabled or disabled, as described below. [ Note: Enabled specializations meet the Cpp17Hash requirements, and disabled specializations do not. — end note ] Each header that declares the template hash provides enabled specializations of hash for nullptr_Ât and all cv-unqualified arithmetic, enumeration, and pointer types. For any type Key for which neither the library nor the user provides an explicit or partial specialization of the class template hash, hash<Key> is disabled.
(Clang HEAD does support this, it turns out.)
>From gcc-bugs-return-628812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 14:03:52 2019
Return-Path: <gcc-bugs-return-628812-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81127 invoked by alias); 11 Jan 2019 14:03:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70845 invoked by uid 48); 11 Jan 2019 14:03:47 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88802] std::hash<std::nullptr_t> not implemented
Date: Fri, 11 Jan 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: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-88802-4-BBitncc0ad@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01621.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88802
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-11
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
On it ...
>From gcc-bugs-return-628813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 14:37:10 2019
Return-Path: <gcc-bugs-return-628813-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116855 invoked by alias); 11 Jan 2019 14:37: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 116796 invoked by uid 48); 11 Jan 2019 14:37:06 -0000
From: "pdziepak at quarnos dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88800] Spurious -Werror=array-bounds for non-taken branch
Date: Fri, 11 Jan 2019 14:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pdziepak at quarnos 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: cc
Message-ID: <bug-88800-4-4VrXiGMYq5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01622.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88800
Paweł Dziepak <pdziepak at quarnos dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pdziepak at quarnos dot org
--- Comment #2 from Paweł Dziepak <pdziepak at quarnos dot org> ---
Smaller reproducer: https://godbolt.org/z/M1EFOv
>From gcc-bugs-return-628814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 14:48:54 2019
Return-Path: <gcc-bugs-return-628814-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98905 invoked by alias); 11 Jan 2019 14:48: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 98867 invoked by uid 48); 11 Jan 2019 14:48:50 -0000
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] New: gfortran documentation warning: '.' or ',' must follow @xref
Date: Fri, 11 Jan 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: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nightstrike at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01623.txt.bz2
Content-length: 725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
Bug ID: 88803
Summary: gfortran documentation warning: '.' or ',' must follow
@xref
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
I see these warnings building gfortran across many versions including current
trunk:
../../gcc/fortran/gfortran.texi:1472: warning: `.' or `,' must follow @xref,
not `o'.
../../gcc/fortran/gfortran.texi:1473: warning: `.' or `,' must follow @xref,
not `e'.
>From gcc-bugs-return-628815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 14:49:13 2019
Return-Path: <gcc-bugs-return-628815-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101436 invoked by alias); 11 Jan 2019 14:49:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99737 invoked by uid 48); 11 Jan 2019 14:49:08 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex value load
Date: Fri, 11 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88778-4-H7ioNdi3FF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01624.txt.bz2
Content-length: 2339
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
More examples:
[hjl@gnu-cfl-1 pr88778]$ cat z.i
_Complex float
foo (_Complex float x)
{
return x;
}
[hjl@gnu-cfl-1 pr88778]$ make z.s
/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc/ -O2 -S z.i
[hjl@gnu-cfl-1 pr88778]$ cat z.s
.file "z.i"
.text
.p2align 4
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
movq %xmm0, -8(%rsp)
movss -8(%rsp), %xmm0
movss %xmm0, -16(%rsp)
movss -4(%rsp), %xmm0
movss %xmm0, -12(%rsp)
movq -16(%rsp), %xmm0
ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.ident "GCC: (GNU) 9.0.0 20190110 (experimental)"
.section .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 pr88778]$ cat x.i
typedef float __v4sf __attribute__ ((__vector_size__ (16)));
typedef float __m128 __attribute__ ((__vector_size__ (16), __may_alias__));
__m128
foo (_Complex float x)
{
return __extension__ (__m128)(__v4sf) { __real x, __imag x,
0.0, 0.0f };
}
[hjl@gnu-cfl-1 pr88778]$ make x.s
/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc/ -O2 -S x.i
[hjl@gnu-cfl-1 pr88778]$ cat x.s
.file "x.i"
.text
.p2align 4
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
movq %xmm0, -16(%rsp)
movss -12(%rsp), %xmm0
movss -16(%rsp), %xmm1
unpcklps %xmm0, %xmm1
movq %xmm1, %xmm0
ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.ident "GCC: (GNU) 9.0.0 20190110 (experimental)"
.section .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 pr88778]$
>From gcc-bugs-return-628816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 14:55:25 2019
Return-Path: <gcc-bugs-return-628816-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73071 invoked by alias); 11 Jan 2019 14:55:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73022 invoked by uid 55); 11 Jan 2019 14:55:21 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88802] std::hash<std::nullptr_t> not implemented
Date: Fri, 11 Jan 2019 14:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88802-4-Xv8x9M1k4v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01625.txt.bz2
Content-length: 682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88802
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri Jan 11 14:54:49 2019
New Revision: 267845
URL: https://gcc.gnu.org/viewcvs?rev=267845&root=gcc&view=rev
Log:
PR libstdc++/88802 define std::hash<nullptr_t> for C++17
PR libstdc++/88802
* include/bits/functional_hash.h (hash<nullptr_t>): Define
specialization for C++17 (P0513R0, LWG 2817).
* testsuite/20_util/hash/nullptr.cc: New test.
Added:
trunk/libstdc++-v3/testsuite/20_util/hash/nullptr.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/functional_hash.h
>From gcc-bugs-return-628817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:00:44 2019
Return-Path: <gcc-bugs-return-628817-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90475 invoked by alias); 11 Jan 2019 15:00: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 90431 invoked by uid 48); 11 Jan 2019 15:00:40 -0000
From: "m101010a at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88804] New: Inconsistently diagnosed unused but set static variable in lambda
Date: Fri, 11 Jan 2019 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m101010a 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-88804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01626.txt.bz2
Content-length: 2352
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88804
Bug ID: 88804
Summary: Inconsistently diagnosed unused but set static
variable in lambda
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: m101010a at gmail dot com
Target Milestone: ---
$ cat x.cpp
void foo(int);
template <class T> void call(T t) {
t(0);
}
void bar() {
static int x=3;
call([](auto){
foo(x);
});
}
$ cat y.cpp
void foo(int);
template <class T> void call(T t) {
t(0);
}
void bar() {
static int x=3;
call([](int){
foo(x);
});
}
$ g++ -fsyntax-only -Wunused-but-set-variable x.cpp
x.cpp: In function ‘void bar()’:
x.cpp:6:13: warning: variable ‘x’ set but not used [-Wunused-but-set-variable]
static int x=3;
^
$ g++ -fsyntax-only -Wunused-but-set-variable y.cpp
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --enable-multilib --disable-werror
--enable-checking=release --enable-default-pie --enable-default-ssp
--enable-cet=auto
Thread model: posix
gcc version 8.2.1 20181127 (GCC)
x is incorrectly diagnosed as unused when used in a lambda with an auto
parameter, but not in a lambda with a type parameter (or no parameter). This
happens even if the lambda isn't called, but does not happen if the lambda is
called in the same function where it is declared.
>From gcc-bugs-return-628818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:00:54 2019
Return-Path: <gcc-bugs-return-628818-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91216 invoked by alias); 11 Jan 2019 15: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 91138 invoked by uid 48); 11 Jan 2019 15:00:50 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Fri, 11 Jan 2019 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88044-4-VJWeszpBIn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01627.txt.bz2
Content-length: 163
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88044
--- Comment #10 from seurer at gcc dot gnu.org ---
I tried both (1) and (2) and the test case does not hang.
>From gcc-bugs-return-628819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:07:32 2019
Return-Path: <gcc-bugs-return-628819-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124673 invoked by alias); 11 Jan 2019 15:07: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 122849 invoked by uid 48); 11 Jan 2019 15:07:28 -0000
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88805] New: hidden symbol `__cpu_model' is referenced by DSO
Date: Fri, 11 Jan 2019 15:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nightstrike at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01628.txt.bz2
Content-length: 1157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
Bug ID: 88805
Summary: hidden symbol `__cpu_model' is referenced by DSO
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Build: x86_64-pc-linux-gnu
Compiling a basic fortran hello world yields:
$ ./gfortran a.f90
/usr/bin/ld: a.out: hidden symbol `__cpu_model' in
/tmp/gcc9/bin/../lib/gcc/x86_64-pc-linux-gnu/9.0.0/libgcc.a(cpuinfo.o) is
referenced by DSO
/usr/bin/ld: final link failed: Nonrepresentable section on output
collect2: error: ld returned 1 exit status
This was previously referenced under PR80600, but that PR was for BSD. I am
seeing this on Linux (CentOS 6), with versions 8.2, 7.4, and current trunk.
8.1 and 7.3 worked.
GCC in this case was configured with:
--disable-nls
--disable-multilib
--enable-languages=fortran
>From gcc-bugs-return-628820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:15:54 2019
Return-Path: <gcc-bugs-return-628820-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16882 invoked by alias); 11 Jan 2019 15:15:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16851 invoked by uid 48); 11 Jan 2019 15:15:50 -0000
From: "m101010a at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88806] New: extern "C" variables declared in different namespaces are considered different
Date: Fri, 11 Jan 2019 15:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m101010a 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-88806-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01629.txt.bz2
Content-length: 2242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88806
Bug ID: 88806
Summary: extern "C" variables declared in different namespaces
are considered different
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: m101010a at gmail dot com
Target Milestone: ---
$ cat x.cpp
namespace A { extern "C" int g; }
namespace B { extern "C" int g; }
using namespace A;
using namespace B;
void f() { g; }
$ g++ -fsyntax-only x.cpp
x.cpp: In function ‘void f()’:
x.cpp:5:12: error: reference to ‘g’ is ambiguous
void f() { g; }
^
x.cpp:2:30: note: candidates are: ‘int B::g’
namespace B { extern "C" int g; }
^
x.cpp:1:30: note: ‘int A::g’
namespace A { extern "C" int g; }
^
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --enable-multilib --disable-werror
--enable-checking=release --enable-default-pie --enable-default-ssp
--enable-cet=auto
Thread model: posix
gcc version 8.2.1 20181127 (GCC)
This is part of the example from the C++ standard section 9.7.3
(namespace.udir) paragraph 6, with g changed from a function to a variable.
Since A::g and B::g refer to the same entity, there should be no ambiguity
between them.
>From gcc-bugs-return-628821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:17:08 2019
Return-Path: <gcc-bugs-return-628821-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18450 invoked by alias); 11 Jan 2019 15:17: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 18317 invoked by uid 48); 11 Jan 2019 15:17:01 -0000
From: "nightstrike at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] New: misleading indentation warnings building libgfortran
Date: Fri, 11 Jan 2019 15:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nightstrike at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01630.txt.bz2
Content-length: 12218
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
Bug ID: 88807
Summary: misleading indentation warnings building libgfortran
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
Assignee: unassigned at gcc dot gnu.org
Reporter: nightstrike at gmail dot com
Target Milestone: ---
While building libgfortran, I receive the following warnings for
-Wmisleading-indentation:
../../../libgfortran/generated/minloc0_4_i1.c: In function 'minloc0_4_i1':
../../../libgfortran/generated/minloc0_4_i1.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_i1.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_i1.c: In function 'minloc0_8_i1':
../../../libgfortran/generated/minloc0_8_i1.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_i1.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_i1.c: In function 'minloc0_16_i1':
../../../libgfortran/generated/minloc0_16_i1.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_i1.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_i2.c: In function 'minloc0_4_i2':
../../../libgfortran/generated/minloc0_4_i2.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_i2.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_i2.c: In function 'minloc0_8_i2':
../../../libgfortran/generated/minloc0_8_i2.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_i2.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_i2.c: In function 'minloc0_16_i2':
../../../libgfortran/generated/minloc0_16_i2.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_i2.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_i4.c: In function 'minloc0_4_i4':
../../../libgfortran/generated/minloc0_4_i4.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_i4.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_i8.c: In function 'minloc0_4_i8':
../../../libgfortran/generated/minloc0_4_i8.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_i8.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_i4.c: In function 'minloc0_16_i4':
../../../libgfortran/generated/minloc0_16_i4.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_i4.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_i8.c: In function 'minloc0_8_i8':
../../../libgfortran/generated/minloc0_8_i8.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_i8.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_i4.c: In function 'minloc0_8_i4':
../../../libgfortran/generated/minloc0_8_i4.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_i4.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_i16.c: In function 'minloc0_8_i16':
../../../libgfortran/generated/minloc0_8_i16.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_i16.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_i8.c: In function 'minloc0_16_i8':
../../../libgfortran/generated/minloc0_16_i8.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_i8.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_i16.c: In function 'minloc0_4_i16':
../../../libgfortran/generated/minloc0_4_i16.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_i16.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_r4.c: In function 'minloc0_16_r4':
../../../libgfortran/generated/minloc0_16_r4.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_r4.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_r4.c: In function 'minloc0_8_r4':
../../../libgfortran/generated/minloc0_8_r4.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_r4.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_r4.c: In function 'minloc0_4_r4':
../../../libgfortran/generated/minloc0_4_r4.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_r4.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_i16.c: In function 'minloc0_16_i16':
../../../libgfortran/generated/minloc0_16_i16.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_i16.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_r8.c: In function 'minloc0_4_r8':
../../../libgfortran/generated/minloc0_4_r8.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_r8.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_r8.c: In function 'minloc0_8_r8':
../../../libgfortran/generated/minloc0_8_r8.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_r8.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_r8.c: In function 'minloc0_16_r8':
../../../libgfortran/generated/minloc0_16_r8.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_r8.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_r10.c: In function 'minloc0_4_r10':
../../../libgfortran/generated/minloc0_4_r10.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_r10.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_r10.c: In function 'minloc0_8_r10':
../../../libgfortran/generated/minloc0_8_r10.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_r10.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_r10.c: In function 'minloc0_16_r10':
../../../libgfortran/generated/minloc0_16_r10.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_r10.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_4_r16.c: In function 'minloc0_4_r16':
../../../libgfortran/generated/minloc0_4_r16.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_4_r16.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_8_r16.c: In function 'minloc0_8_r16':
../../../libgfortran/generated/minloc0_8_r16.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_8_r16.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
../../../libgfortran/generated/minloc0_16_r16.c: In function 'minloc0_16_r16':
../../../libgfortran/generated/minloc0_16_r16.c:138:5: warning: this 'else'
clause does not guard... [-Wmisleading-indentation]
138 | else
| ^~~~
../../../libgfortran/generated/minloc0_16_r16.c:152:7: note: ...this statement,
but the latter is misleadingly indented as if it were guarded by the 'else'
152 | n = 0;
| ^
>From gcc-bugs-return-628822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:44:27 2019
Return-Path: <gcc-bugs-return-628822-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84587 invoked by alias); 11 Jan 2019 15:44:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84552 invoked by uid 48); 11 Jan 2019 15:44:22 -0000
From: "cassio.neri at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88797] Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Fri, 11 Jan 2019 15: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: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cassio.neri 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-88797-4-OeunNcgR6f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01631.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
--- Comment #5 from Cassio Neri <cassio.neri at gmail dot com> ---
There's a (fragile) workaround:
void use(unsigned);
#define VERSION 0
bool f(unsigned x, unsigned y) {
#if VERSION == 0
return x < 1111 + (y <= 2222);
#else
bool b = y <= 2222;
return x < 1111 + b;
#endif
}
void test_f(unsigned x, unsigned y) {
for (unsigned i = 0; i < 3333; ++i)
use(f(x++, y++));
}
f is till the same. Version 0 of test_f has 4 jumps whereas version 1 has only
one.
https://godbolt.org/z/gZZQ2f
>From gcc-bugs-return-628823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 15:46:06 2019
Return-Path: <gcc-bugs-return-628823-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90094 invoked by alias); 11 Jan 2019 15:46: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 90022 invoked by uid 48); 11 Jan 2019 15:46:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88802] std::hash<std::nullptr_t> not implemented
Date: Fri, 11 Jan 2019 15:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88802-4-iog43384jP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88802-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01632.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88802
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for GCC 9.
>From gcc-bugs-return-628824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 16:07:45 2019
Return-Path: <gcc-bugs-return-628824-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51108 invoked by alias); 11 Jan 2019 16:07: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 51011 invoked by uid 48); 11 Jan 2019 16:07:41 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80517] [missed optimization] constant propagation through Intel intrinsics
Date: Fri, 11 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version
Message-ID: <bug-80517-4-UO5Cmb7Eqq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01633.txt.bz2
Content-length: 1530
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80517
Matthias Kretz <kretz at kde dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|8.0 |9.0
--- Comment #3 from Matthias Kretz <kretz at kde dot org> ---
GCC 9 almost resolves this. However, for some reason this extended test case is
not fully optimized: https://gcc.godbolt.org/z/jRrHth
i.e. the call to dont_call_me() should be eliminated as dead code
#include <x86intrin.h>
inline __m128i cmp(__m128i x, __m128i y) {
return _mm_cmpeq_epi16(x, y);
}
inline unsigned to_bits(__m128i mask0) {
return _pext_u32(_mm_movemask_epi8(mask0), 0xaaaa);
}
inline __m128i to_vmask(unsigned bits) {
__m128i mask = _mm_set1_epi16(bits);
mask = _mm_and_si128(mask, _mm_setr_epi16(1, 2, 4, 8, 16, 32, 64, 128));
mask = _mm_cmpeq_epi16(mask, _mm_setzero_si128());
mask = _mm_xor_si128(mask, _mm_cmpeq_epi16(mask, mask));
return mask;
}
inline bool is_eq(unsigned bits, __m128i vmask) {
return to_bits(vmask) == bits;
}
extern const auto a = __m128i{0x0001'0002'0004'0003, 0x0009'0008'0007'0006};
extern const auto b = __m128i{0x0001'0002'0005'0003, 0x0000'0008'0007'0006};
extern const auto c = cmp(a, b);
extern const auto d = to_bits(c);
void call_me();
void dont_call_me();
void f() {
if (is_eq(d, cmp(b, a))) {
call_me();
} else {
dont_call_me();
}
}
>From gcc-bugs-return-628825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 16:18:09 2019
Return-Path: <gcc-bugs-return-628825-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65824 invoked by alias); 11 Jan 2019 16:18: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 65760 invoked by uid 48); 11 Jan 2019 16:18:05 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80517] [missed optimization] constant propagation through Intel intrinsics
Date: Fri, 11 Jan 2019 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80517-4-1WXavXdJa5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01634.txt.bz2
Content-length: 976
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80517
--- Comment #4 from Matthias Kretz <kretz at kde dot org> ---
A similar test case showing that something is still missing
(https://gcc.godbolt.org/z/t1DT7E):
#include <x86intrin.h>
inline __m128i cmp(__m128i x, __m128i y) {
return _mm_cmpeq_epi16(x, y);
}
inline unsigned to_bits(__m128i mask0) {
return _pext_u32(_mm_movemask_epi8(mask0), 0xaaaa);
}
inline __m128i to_vmask(unsigned bits) {
__m128i mask = _mm_set1_epi16(bits);
mask = _mm_and_si128(mask, _mm_setr_epi16(1, 2, 4, 8, 16, 32, 64, 128));
mask = _mm_cmpeq_epi16(mask, _mm_setzero_si128());
mask = _mm_xor_si128(mask, _mm_cmpeq_epi16(mask, mask));
return mask;
}
auto f(__m128i x, __m128i y) {
// should be:
// vpcmpeqw %xmm1, %xmm0, %xmm0
// ret
return to_vmask(to_bits(cmp(x, y)));
}
auto f(unsigned bits) {
// should be equivalent to `return 0xff & bits;`
return to_bits(to_vmask(bits));
}
>From gcc-bugs-return-628826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 16:27:24 2019
Return-Path: <gcc-bugs-return-628826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94522 invoked by alias); 11 Jan 2019 16:27:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94441 invoked by uid 48); 11 Jan 2019 16:27:19 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80517] [missed optimization] constant propagation through Intel intrinsics
Date: Fri, 11 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80517-4-Frtp8f4xSd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01635.txt.bz2
Content-length: 965
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80517
--- Comment #5 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Matthias Kretz from comment #3)
> GCC 9 almost resolves this. However, for some reason this extended test case
> is not fully optimized: https://gcc.godbolt.org/z/jRrHth
> i.e. the call to dont_call_me() should be eliminated as dead code
We are left with:
_GLOBAL__sub_I__Z1fv ()
{
<bb 2> [local count: 1073741824]:
d = 125;
return;
}
f ()
{
unsigned int d.1_1;
<bb 2> [local count: 1073741824]:
d.1_1 = d;
if (d.1_1 == 125)
[...]
This is a classic, if the initialization of global variables is only noticed to
be constant after optimizations (as opposed to in the front-end), gcc doesn't
manage to turn the dynamic initialization into a static one. Making the
intrinsics constexpr may help, but really this is something that would be nice
to fix eventually, there are several PRs blocked by this.
>From gcc-bugs-return-628827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 16:28:17 2019
Return-Path: <gcc-bugs-return-628827-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95633 invoked by alias); 11 Jan 2019 16:28: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 95582 invoked by uid 48); 11 Jan 2019 16:28:12 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88808] New: bitwise operators on AVX512 masks fail to use the new mask instructions
Date: Fri, 11 Jan 2019 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01636.txt.bz2
Content-length: 1496
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88808
Bug ID: 88808
Summary: bitwise operators on AVX512 masks fail to use the new
mask instructions
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
Test case (https://godbolt.org/z/gyCN12):
#include <x86intrin.h>
using V [[gnu::vector_size(16)]] = float;
auto f(V x) {
auto mask = _mm_fpclass_ps_mask(x, 16) | _mm_fpclass_ps_mask(x, 8);
return _mm_mask_blend_ps(mask, x, x + 1);
}
auto g(V x) {
auto mask = _kor_mask8(_mm_fpclass_ps_mask(x, 16), _mm_fpclass_ps_mask(x,
8));
return _mm_mask_blend_ps(mask, x, x + 1);
}
Function f should compile to the same code as g does, i.e. use korb instead of
kmovb + orl + kmovb. Similar test cases can be constructed for kxor, kand, and
kandn as well as for masks of 8 and 16 bits (likely for 32 and 64 as well, but
I have not tested it). For kand it's a bit trickier to trigger, but e.g. the
following shows it:
__mmask8 foo = 0;
auto f(V x) {
auto mask0 = _mm_fpclass_ps_mask(x, 16);
auto mask1 = _mm_fpclass_ps_mask(x, 8);
foo = mask0 | mask1;
return _mm_mask_blend_ps(mask0 & mask1, x, x + 1);
}
>From gcc-bugs-return-628828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 16:45:38 2019
Return-Path: <gcc-bugs-return-628828-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122906 invoked by alias); 11 Jan 2019 16:45:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122808 invoked by uid 48); 11 Jan 2019 16:45:33 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80517] [missed optimization] constant propagation through Intel intrinsics
Date: Fri, 11 Jan 2019 16:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80517-4-IDLvQP8ZLc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80517-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01637.txt.bz2
Content-length: 574
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80517
--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Matthias Kretz from comment #4)
> A similar test case showing that something is still missing
You don't seem to be passing constants here, so this is unrelated to this PR.
If you file a new one, please annotate your example explaining where you expect
what to simplify to what and why.
> (https://gcc.godbolt.org/z/t1DT7E):
Adding -fdump-tree-optimized=- -g0 and showing the compiler output makes this
more understandable for me...
>From gcc-bugs-return-628829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 16:53:19 2019
Return-Path: <gcc-bugs-return-628829-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3795 invoked by alias); 11 Jan 2019 16:53:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3699 invoked by uid 48); 11 Jan 2019 16:53:15 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Fri, 11 Jan 2019 16:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-7A6lbIQbDL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01638.txt.bz2
Content-length: 1391
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
I understand what jump threading does but I don't know enough about how it
works to have a clear idea how viable marking up the created statements would
be. To avoid false negatives it would need to make it possible to distinguish
invalid statements in the original code from invalid statements it introduced.
At the time it runs there may not be a way to tell one from the other yet (the
distinction between valid and invalid isn't exposed until after the constants
along the newly introduced path have been fully propagated into those
statements).
I have been meaning to look into it for a couple of releases. It won't happen
for GCC 9 but in 10, the planned integration of the strlen and sprintf passes
(and perhaps also -Wstringop-overflow, and maybe even -Wrestrict, which would
include this warning) may be a good opportunity to experiment with some of
these ideas.
That said, no solution will ever be perfect. There will always be some false
positives (and false negatives), no matter how early or late these warnings
run. What I think is even more pressing and important than the redesign (and
far more realistic than hoping it will completely solve the problem) is to make
#pragma diagnostic work reliably for middle-end warnings.
>From gcc-bugs-return-628830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 17:03:48 2019
Return-Path: <gcc-bugs-return-628830-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44713 invoked by alias); 11 Jan 2019 17:03:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44675 invoked by uid 48); 11 Jan 2019 17:03:43 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] misleading indentation warnings building libgfortran
Date: Fri, 11 Jan 2019 17:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_severity
Message-ID: <bug-88807-4-HdUx25AB6K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01639.txt.bz2
Content-length: 928
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Severity|normal |enhancement
--- Comment #1 from kargl at gcc dot gnu.org ---
(In reply to nightstrike from comment #0)
> While building libgfortran, I receive the following warnings for
> -Wmisleading-indentation:
>
> ../../../libgfortran/generated/minloc0_4_i1.c: In function 'minloc0_4_i1':
> ../../../libgfortran/generated/minloc0_4_i1.c:138:5: warning: this 'else'
> clause does not guard... [-Wmisleading-indentation]
> 138 | else
> | ^~~~
These files were GENERATED from an m4 file. There cannot
not be anything misleading in these files as a human isn't
expected to read the GENERATED c code.
>From gcc-bugs-return-628831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 17:06:25 2019
Return-Path: <gcc-bugs-return-628831-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63320 invoked by alias); 11 Jan 2019 17:06: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 63287 invoked by uid 48); 11 Jan 2019 17:06:21 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88805] hidden symbol `__cpu_model' is referenced by DSO
Date: Fri, 11 Jan 2019 17:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 8.2.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-88805-4-UE9gNOxLQt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01640.txt.bz2
Content-length: 213
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
--- Comment #1 from kargl at gcc dot gnu.org ---
This appears to be either a problem with your binutils
or pilot error. It is not a problem with libgfortran.
>From gcc-bugs-return-628832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 17:47:08 2019
Return-Path: <gcc-bugs-return-628832-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117302 invoked by alias); 11 Jan 2019 17:47: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 117238 invoked by uid 48); 11 Jan 2019 17:47:04 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88800] Spurious -Werror=array-bounds for non-taken branch
Date: Fri, 11 Jan 2019 17:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed cf_known_to_fail
Message-ID: <bug-88800-4-uhH0V854AR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01641.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88800
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |8.2.0, 9.0
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. The warning is issued by the restrict pass when the memmove call is
being folded into MEM_REF, i.e.,
__builtin_memmove (&b.data, &c, 16);
into:
_15 = MEM[(char * {ref-all})&c];
MEM[(char * {ref-all})&b] = _15;
and before b.size's initial negative value has been constant-propagated. I
don't know if teaching the restrict pass about MEM_REF rather than having the
folder call into the pass would be viable given the unreliability of the
MEM_REF argument.
>From gcc-bugs-return-628833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 17:50:30 2019
Return-Path: <gcc-bugs-return-628833-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120240 invoked by alias); 11 Jan 2019 17:50:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120194 invoked by uid 48); 11 Jan 2019 17:50:26 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88806] extern "C" variables declared in different namespaces are considered different
Date: Fri, 11 Jan 2019 17:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88806-4-grdr8uP6hV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88806-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88806-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01642.txt.bz2
Content-length: 151
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88806
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Related to the old bug 27227.
>From gcc-bugs-return-628834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 17:53:12 2019
Return-Path: <gcc-bugs-return-628834-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3122 invoked by alias); 11 Jan 2019 17:53:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3071 invoked by uid 48); 11 Jan 2019 17:53:08 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88808] bitwise operators on AVX512 masks fail to use the new mask instructions
Date: Fri, 11 Jan 2019 17:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-88808-4-jGGTxMAYAu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01643.txt.bz2
Content-length: 668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88808
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
See PR88473 and PR88798. I'd personally probably revert the changes to make
the mask operations separate from GPR operations and just use special RTL
patterns if GPR operation can't do it (e.g. andn when not BMI, or 64-bit
logicals on 32-bit targets), but it is too late for that for GCC9.
>From gcc-bugs-return-628835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 17:54:24 2019
Return-Path: <gcc-bugs-return-628835-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4374 invoked by alias); 11 Jan 2019 17:54: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 4324 invoked by uid 48); 11 Jan 2019 17:54:19 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88805] hidden symbol `__cpu_model' is referenced by DSO
Date: Fri, 11 Jan 2019 17:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88805-4-JVrKdvs8r7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01644.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>/usr/bin/ld: a.out: hidden symbol `__cpu_model' in /tmp/gcc9/bin/../lib/gcc/x86_64-pc-linux-gnu/9.0.0/libgcc.a(cpuinfo.o) is referenced by DSO
Could you figure out which shared library references __cpu_model ? I doubt it
is one that GCC just built.
I suspect it is libc which means your libc is broken. You will most likely
need a newer libc which does not reference __cpu_model any more.
>From gcc-bugs-return-628836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:01:04 2019
Return-Path: <gcc-bugs-return-628836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22183 invoked by alias); 11 Jan 2019 18:01: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 22085 invoked by uid 48); 11 Jan 2019 18:00:58 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88809] New: do not use rep-scasb for inline strlen/memchr
Date: Fri, 11 Jan 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01645.txt.bz2
Content-length: 1568
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88809
Bug ID: 88809
Summary: do not use rep-scasb for inline strlen/memchr
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: amonakov at gcc dot gnu.org
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
Performance difference between libc strlen and x86 rep-scasb has grown too
large and seems unlikely to improve anytime soon.
On most x86 cores, microcode for rep-scasb is not too sophisticated and runs at
0.5 bytes per cycle or worse (according to Agner Fog's research; with SkylakeX
managing 1 b/c), plus some overhead for entering/leaving the microcode loop (I
think on the order of 20 cycles, but don't have exact info).
Whereas libc strlen typically has small overhead for short strings and uses
register-wide operations on long strings, sustaining on the order of 4-8 b/c
only with integer registers or even in the ballpark of 16-64 b/c with SSE/AVX
(sorry, don't have exact figures here).
A call to strlen is also shorter by itself (rep-scasb needs extra instructions
to setup %rax and fixup %rcx).
(although to be fair, a call to strlen prevents use of redzone and clobbers
more registers)
Therefore I suggest we don't use rep-scasb for inline strlen anymore by default
(we currently do at -Os). This is in part motivated by PR 88793 and the Redhat
bug referenced from there.
>From gcc-bugs-return-628837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:03:44 2019
Return-Path: <gcc-bugs-return-628837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25917 invoked by alias); 11 Jan 2019 18:03: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 25844 invoked by uid 48); 11 Jan 2019 18:03:40 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Fri, 11 Jan 2019 18:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amonakov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88793-4-bNBbDtJS1o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01646.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
--- Comment #4 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #3)
> I think it's fair to raise the question if gcc should not use scasb/cmpsb by
> default (I thought there was a bug for that but apparently there isn't?).
We had PR 43052 for memcmp/cmpsb, which was (accidentally?) fixed. I've now
opened PR 88809 for strlen/scasb.
>From gcc-bugs-return-628838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:05:53 2019
Return-Path: <gcc-bugs-return-628838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28044 invoked by alias); 11 Jan 2019 18:05: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 27992 invoked by uid 48); 11 Jan 2019 18:05:48 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88809] do not use rep-scasb for inline strlen/memchr
Date: Fri, 11 Jan 2019 18:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88809-4-kupb9tu7zd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01647.txt.bz2
Content-length: 653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88809
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #0)
> Therefore I suggest we don't use rep-scasb for inline strlen anymore by
> default (we currently do at -Os). This is in part motivated by PR 88793 and
> the Redhat bug referenced from there.
Is it smaller to call a function or inline it? -Os is really truely optimize
for size no matter what. I know non-embedded folks don't like that and it is
also the reason why Apple added -Oz (a similar thing to this -Os issue but on
PowerPC where the string instructions are used).
>From gcc-bugs-return-628839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:07:40 2019
Return-Path: <gcc-bugs-return-628839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31635 invoked by alias); 11 Jan 2019 18:07: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 31573 invoked by uid 48); 11 Jan 2019 18:07:34 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88809] do not use rep-scasb for inline strlen/memchr
Date: Fri, 11 Jan 2019 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88809-4-r605gTYhuI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88809-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01648.txt.bz2
Content-length: 255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88809
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>(although to be fair, a call to strlen prevents use of redzone and clobbers more registers)
And causes more register pressure ...
>From gcc-bugs-return-628840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:10:40 2019
Return-Path: <gcc-bugs-return-628840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34557 invoked by alias); 11 Jan 2019 18:10: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 34451 invoked by uid 48); 11 Jan 2019 18:10:35 -0000
From: "fw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Fri, 11 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also
Message-ID: <bug-88793-4-YmCEAZGJqO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01649.txt.bz2
Content-length: 594
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
Florian Weimer <fw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=88809
--- Comment #5 from Florian Weimer <fw at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #3)
> (-Os is not "minimize size at all costs").
Bug 88809 comment 1 says the exact opposite. 8-/
>From gcc-bugs-return-628841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:10:41 2019
Return-Path: <gcc-bugs-return-628841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34776 invoked by alias); 11 Jan 2019 18:10:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34520 invoked by uid 48); 11 Jan 2019 18:10:37 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] gfortran documentation warning: '.' or ',' must follow @xref
Date: Fri, 11 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: minor
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc bug_severity
Message-ID: <bug-88803-4-YnLGhKiEXm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01650.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
CC| |egallager at gcc dot gnu.org
Severity|normal |minor
>From gcc-bugs-return-628842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:10:53 2019
Return-Path: <gcc-bugs-return-628842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35889 invoked by alias); 11 Jan 2019 18:10:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35822 invoked by uid 48); 11 Jan 2019 18:10:49 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex value load
Date: Fri, 11 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-EahSYkh5OF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01651.txt.bz2
Content-length: 706
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #4 from åˆ˜è¢‹é¼ <crazylht at gmail dot com> ---
Currently _Complex is classified as SSE_REG_CLASS, and need two 2 hardreg to
handle it. We may need to handle things like TARGET_HARD_REGNO_MODE_OK in
backend. So that ira can work suitable for our complex operation.
static int
classify_argument (machine_mode mode, const_tree type,
enum x86_64_reg_class classes[MAX_CLASSES], int bit_offset)
...
case E_SCmode:
classes[0] = X86_64_SSE_CLASS;
...
static unsigned int
ix86_hard_regno_nregs (unsigned int regno, machine_mode mode)
{
...
if (COMPLEX_MODE_P (mode))
return 2;
...
}
>From gcc-bugs-return-628843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:20:25 2019
Return-Path: <gcc-bugs-return-628843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73310 invoked by alias); 11 Jan 2019 18:20: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 73209 invoked by uid 48); 11 Jan 2019 18:20:21 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Fri, 11 Jan 2019 18:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88044-4-hFVtGNRHQf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01652.txt.bz2
Content-length: 238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88044
--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I tried both (1) and (2) and the test case does not hang.
Could you please try '0, 1', '1, 2', and '0, 2'?
>From gcc-bugs-return-628844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:21:55 2019
Return-Path: <gcc-bugs-return-628844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76186 invoked by alias); 11 Jan 2019 18:21: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 76129 invoked by uid 48); 11 Jan 2019 18:21:52 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88793] Document that __attribute__ ((cold)) is not equivalent to __builtin_except because of optimization for size
Date: Fri, 11 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
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-88793-4-RwJNLXKSD7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01653.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88793
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Florian Weimer from comment #5)
> (In reply to Alexander Monakov from comment #3)
> > (-Os is not "minimize size at all costs").
>
> Bug 88809 comment 1 says the exact opposite. 8-/
And the manual says:
It also performs further optimizations designed to reduce code size.
Also see the thread at:
https://gcc.gnu.org/ml/gcc/2017-08/msg00280.html
>From gcc-bugs-return-628845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:33:26 2019
Return-Path: <gcc-bugs-return-628845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96330 invoked by alias); 11 Jan 2019 18:33:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 96299 invoked by uid 48); 11 Jan 2019 18:33:22 -0000
From: "cand at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88696] Power VSX builtins missing vmuluwm / vector int vec_mul (vector int, vector int);
Date: Fri, 11 Jan 2019 18:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cand at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88696-4-0sdAIPdgGq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01654.txt.bz2
Content-length: 392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88696
--- Comment #1 from Lauri Kasanen <cand at gmx dot com> ---
Actually, seems this is only a documentation bug. vec_mul for the int vectors
is not listed on any of the "PowerPC AltiVec/VSX Built-in Functions" pages,
even though it works. It emulates the multiplication on older ppc and on power8
correctly emits vmuluwm, since r224494.
>From gcc-bugs-return-628846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:38:23 2019
Return-Path: <gcc-bugs-return-628846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104193 invoked by alias); 11 Jan 2019 18:38:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104150 invoked by uid 48); 11 Jan 2019 18:38:19 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88114] "virtual ~destructor() = default": Destructor not created
Date: Fri, 11 Jan 2019 18:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: burnus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88114-4-T1OUYZs2jJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01655.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88114
--- Comment #5 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Updated patch:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00646.html
>From gcc-bugs-return-628848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:42:37 2019
Return-Path: <gcc-bugs-return-628848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109181 invoked by alias); 11 Jan 2019 18:42: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 108935 invoked by uid 48); 11 Jan 2019 18:42:33 -0000
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64862] printf attribute should accept other string types
Date: Fri, 11 Jan 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tromey at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-64862-4-qdqSio3WIT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01657.txt.bz2
Content-length: 231
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64862
--- Comment #9 from Tom Tromey <tromey at gcc dot gnu.org> ---
Created attachment 45413
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45413&action=edit
ancient patch
>From gcc-bugs-return-628847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:42:12 2019
Return-Path: <gcc-bugs-return-628847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107434 invoked by alias); 11 Jan 2019 18:42: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 107381 invoked by uid 48); 11 Jan 2019 18:42:08 -0000
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64862] printf attribute should accept other string types
Date: Fri, 11 Jan 2019 18:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tromey at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64862-4-QkdC2siNVk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01656.txt.bz2
Content-length: 334
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64862
--- Comment #8 from Tom Tromey <tromey at gcc dot gnu.org> ---
Sorry about the extreme delay on this.
I think my patch has long since bit-rotted, but I can attach it for
reference. I believe my assignment situation got sorted out so this
should be fine to read and/or copy from.
>From gcc-bugs-return-628849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:43:44 2019
Return-Path: <gcc-bugs-return-628849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111476 invoked by alias); 11 Jan 2019 18:43: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 111438 invoked by uid 48); 11 Jan 2019 18:43:40 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88798] AVX512BW code does not use bit-operations that work on mask registers
Date: Fri, 11 Jan 2019 18:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wojciech_mula at poczta dot onet.pl
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88798-4-4jzxItyXYH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01658.txt.bz2
Content-length: 511
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88798
--- Comment #3 from Wojciech Mula <wojciech_mula at poczta dot onet.pl> ---
Sorry, I didn't find that bug; I think you may close this one.
BTW, I had checked the code on godbolt.org before submitting. I tested also
with their "GCC (trunk)", but the generated code is the same as for 8.2. The
trunk's version is "g++ (GCC-Explorer-Build) 9.0.0 20190109 (experimental)" --
seems it's a fresh version and should already include the fixes Andrew
mentioned.
>From gcc-bugs-return-628852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:44:36 2019
Return-Path: <gcc-bugs-return-628852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115279 invoked by alias); 11 Jan 2019 18:44: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 115167 invoked by uid 55); 11 Jan 2019 18:44:32 -0000
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Fri, 11 Jan 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88777-4-JGaqGZ5jKT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01661.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
--- Comment #5 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Fri Jan 11 18:44:00 2019
New Revision: 267851
URL: https://gcc.gnu.org/viewcvs?rev=267851&root=gcc&view=rev
Log:
PR 88777
PR 88614
* genattrtab.c (min_fn): Don't translate values.
(min_attr_value): Return INT_MAX when the value can't be calculated.
Return minimum among any values that can be calculated.
(max_attr_value): Adjust.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/genattrtab.c
>From gcc-bugs-return-628851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:44:36 2019
Return-Path: <gcc-bugs-return-628851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115242 invoked by alias); 11 Jan 2019 18:44: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 115181 invoked by uid 55); 11 Jan 2019 18:44:32 -0000
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88614] ICE: output_operand: invalid %z value
Date: Fri, 11 Jan 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88614-4-taLj0gfanI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88614-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88614-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01660.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88614
--- Comment #2 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Fri Jan 11 18:44:00 2019
New Revision: 267851
URL: https://gcc.gnu.org/viewcvs?rev=267851&root=gcc&view=rev
Log:
PR 88777
PR 88614
* genattrtab.c (min_fn): Don't translate values.
(min_attr_value): Return INT_MAX when the value can't be calculated.
Return minimum among any values that can be calculated.
(max_attr_value): Adjust.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/genattrtab.c
>From gcc-bugs-return-628850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:44:20 2019
Return-Path: <gcc-bugs-return-628850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113415 invoked by alias); 11 Jan 2019 18:44: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 113284 invoked by uid 48); 11 Jan 2019 18:44:17 -0000
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/64862] printf attribute should accept other string types
Date: Fri, 11 Jan 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tromey at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64862-4-2HYa5yeXEH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01659.txt.bz2
Content-length: 179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64862
--- Comment #10 from Tom Tromey <tromey at gcc dot gnu.org> ---
Also I think all the test suite changes never really worked.
>From gcc-bugs-return-628853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 18:50:49 2019
Return-Path: <gcc-bugs-return-628853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9355 invoked by alias); 11 Jan 2019 18:50: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 9294 invoked by uid 48); 11 Jan 2019 18:50:44 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88044] [9 regression] gfortran.dg/transfer_intrinsic_3.f90 hangs after r266171
Date: Fri, 11 Jan 2019 18: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: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88044-4-HO6huuExli@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88044-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01662.txt.bz2
Content-length: 371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88044
--- Comment #12 from seurer at gcc dot gnu.org ---
None of those hang, either.
I also experimented with the options a bit. The as-is options affecting
optimization are: -O3 -funroll-loops -fpeel-loops -finline-functions
Change to -O1 and no hang. Dropping the other ones or using -O2 and it still
hangs.
>From gcc-bugs-return-628854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:05:08 2019
Return-Path: <gcc-bugs-return-628854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49860 invoked by alias); 11 Jan 2019 19:05: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 49760 invoked by uid 55); 11 Jan 2019 19:05:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88693] [9 Regression] Wrong code since r263018
Date: Fri, 11 Jan 2019 19:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88693-4-QqM6JhVWw4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01663.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88693
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 11 19:04:32 2019
New Revision: 267852
URL: https://gcc.gnu.org/viewcvs?rev=267852&root=gcc&view=rev
Log:
PR tree-optimization/88693
* tree-ssa-strlen.c (get_min_string_length): Don't set *full_string_p
for STRING_CSTs that don't contain any NUL characters in the first
TREE_STRING_LENGTH bytes.
* gcc.c-torture/execute/pr88693.c: New test.
Added:
trunk/gcc/testsuite/gcc.c-torture/execute/pr88693.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-strlen.c
>From gcc-bugs-return-628855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:06:06 2019
Return-Path: <gcc-bugs-return-628855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51804 invoked by alias); 11 Jan 2019 19:06:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51696 invoked by uid 48); 11 Jan 2019 19:06:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88693] [9 Regression] Wrong code since r263018
Date: Fri, 11 Jan 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: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88693-4-wiw65IVQTp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01664.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88693
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:17:04 2019
Return-Path: <gcc-bugs-return-628856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11172 invoked by alias); 11 Jan 2019 19:17: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 11082 invoked by uid 48); 11 Jan 2019 19:17:01 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Fri, 11 Jan 2019 19:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-DBGQgiDW9f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01665.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Look e.g. at -O2:
void bar (int);
void
foo (int x)
{
int i = 0;
if (x == 8)
{
x = 16;
goto lab;
}
for (; i < 100; i++)
{
lab:
bar (x);
}
}
but pretty much any time you have a loop where some var doesn't really change,
but there is some other edge to the loop header with a different value for that
var.
>From gcc-bugs-return-628857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:26:07 2019
Return-Path: <gcc-bugs-return-628857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10258 invoked by alias); 11 Jan 2019 19:26:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10167 invoked by uid 55); 11 Jan 2019 19:26:02 -0000
From: "vmakarov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87305] [9 Regression] Segfault in end_hard_regno in setup_live_pseudos_and_spill_after_risky_transforms on aarch64 big-endian
Date: Fri, 11 Jan 2019 19:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, ra
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vmakarov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87305-4-fXs4JjjE5x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87305-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01666.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87305
--- Comment #6 from Vladimir Makarov <vmakarov at gcc dot gnu.org> ---
Author: vmakarov
Date: Fri Jan 11 19:25:31 2019
New Revision: 267854
URL: https://gcc.gnu.org/viewcvs?rev=267854&root=gcc&view=rev
Log:
2019-01-11 Vladimir Makarov <vmakarov@redhat.com>
PR rtl-optimization/87305
* lra-assigns.c
(setup_live_pseudos_and_spill_after_risky_transforms): Add code
for little endian pseudos used as paradoxical subreg.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/lra-assigns.c
>From gcc-bugs-return-628858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:40:52 2019
Return-Path: <gcc-bugs-return-628858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41174 invoked by alias); 11 Jan 2019 19:40:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41075 invoked by uid 55); 11 Jan 2019 19:40:47 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88114] "virtual ~destructor() = default": Destructor not created
Date: Fri, 11 Jan 2019 19:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: burnus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88114-4-kFY9ayamXE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01667.txt.bz2
Content-length: 828
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88114
--- Comment #6 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Fri Jan 11 19:40:13 2019
New Revision: 267855
URL: https://gcc.gnu.org/viewcvs?rev=267855&root=gcc&view=rev
Log:
PR C++/88114 Gen destructor of an abstract class
PR C++/8811
* decl2.c (maybe_emit_vtables): If needed, generate code for
the destructor of an abstract class.
(mark_used): Update comment for older function-name change.
PR C++/88114
* g++.dg/cpp0x/defaulted61.C: New.
* g++.dg/cpp0x/defaulted62.C: New.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/defaulted61.C
trunk/gcc/testsuite/g++.dg/cpp0x/defaulted62.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl2.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:40:52 2019
Return-Path: <gcc-bugs-return-628859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41186 invoked by alias); 11 Jan 2019 19:40:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41092 invoked by uid 55); 11 Jan 2019 19:40:48 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/8811] Internal compiler error in extract_constrain_insn_cached
Date: Fri, 11 Jan 2019 19:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 3.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: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-8811-4-9yIrYRQK6B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-8811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-8811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01668.txt.bz2
Content-length: 827
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=8811
--- Comment #2 from Tobias Burnus <burnus at gcc dot gnu.org> ---
Author: burnus
Date: Fri Jan 11 19:40:13 2019
New Revision: 267855
URL: https://gcc.gnu.org/viewcvs?rev=267855&root=gcc&view=rev
Log:
PR C++/88114 Gen destructor of an abstract class
PR C++/8811
* decl2.c (maybe_emit_vtables): If needed, generate code for
the destructor of an abstract class.
(mark_used): Update comment for older function-name change.
PR C++/88114
* g++.dg/cpp0x/defaulted61.C: New.
* g++.dg/cpp0x/defaulted62.C: New.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/defaulted61.C
trunk/gcc/testsuite/g++.dg/cpp0x/defaulted62.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl2.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 19:41:47 2019
Return-Path: <gcc-bugs-return-628860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52311 invoked by alias); 11 Jan 2019 19:41:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52200 invoked by uid 48); 11 Jan 2019 19:41:43 -0000
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88114] "virtual ~destructor() = default": Destructor not created
Date: Fri, 11 Jan 2019 19:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: burnus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: burnus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88114-4-WleAO4lsvN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88114-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88114-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01669.txt.bz2
Content-length: 443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88114
Tobias Burnus <burnus at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
FIXED on the GCC 9 trunk
>From gcc-bugs-return-628861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 20:12:42 2019
Return-Path: <gcc-bugs-return-628861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106978 invoked by alias); 11 Jan 2019 20:12: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 106925 invoked by uid 48); 11 Jan 2019 20:12:39 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88718] Strange inconsistency between old style and new style definitions of inline functions.
Date: Fri, 11 Jan 2019 20:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88718-4-7cAsQYMsr4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88718-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01670.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88718
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00659.html
>From gcc-bugs-return-628862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 20:36:05 2019
Return-Path: <gcc-bugs-return-628862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73978 invoked by alias); 11 Jan 2019 20:36:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73798 invoked by uid 48); 11 Jan 2019 20:36:00 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/87214] [9 Regression] r263772 miscompiled 520.omnetpp_r in SPEC CPU 2017
Date: Fri, 11 Jan 2019 20:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-87214-4-xf5siDdYvG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01671.txt.bz2
Content-length: 358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87214
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |law at redhat dot com
>From gcc-bugs-return-628863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 20:54:29 2019
Return-Path: <gcc-bugs-return-628863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120629 invoked by alias); 11 Jan 2019 20:54: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 120574 invoked by uid 48); 11 Jan 2019 20:54:24 -0000
From: "jb at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88805] hidden symbol `__cpu_model' is referenced by DSO
Date: Fri, 11 Jan 2019 20:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jb at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-88805-4-PgrEsqTTC6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01672.txt.bz2
Content-length: 985
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
Janne Blomqvist <jb at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jb at gcc dot gnu.org
--- Comment #3 from Janne Blomqvist <jb at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> >/usr/bin/ld: a.out: hidden symbol `__cpu_model' in /tmp/gcc9/bin/../lib/gcc/x86_64-pc-linux-gnu/9.0.0/libgcc.a(cpuinfo.o) is referenced by DSO
>
>
> Could you figure out which shared library references __cpu_model ? I doubt
> it is one that GCC just built.
>
> I suspect it is libc which means your libc is broken. You will most likely
> need a newer libc which does not reference __cpu_model any more.
libgfortran/generated/matmul_*.c uses __cpu_model. As to why it does that
instead of using the function multiversioning support, well, beats me.
>From gcc-bugs-return-628864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 20:57:56 2019
Return-Path: <gcc-bugs-return-628864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124211 invoked by alias); 11 Jan 2019 20:57:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124176 invoked by uid 48); 11 Jan 2019 20:57:52 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86655] std::assoc_legendre should not constrain the value of m
Date: Fri, 11 Jan 2019 20:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-86655-4-ZOPTXTANbJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01673.txt.bz2
Content-length: 940
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86655
--- Comment #4 from emsr at gcc dot gnu.org ---
Created attachment 45414
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45414&action=edit
This is a patch on both std and tr1, both sph_legendre and assoc_legendre.
2018-01-11 Edward Smith-Rowland <3dw4rd@verizon.net>
PR libstdc++/86655 - std::assoc_legendre should not constrain
the value of m
* include/tr1/legendre_function.tcc (__assoc_legendre_p,
__sph_legendre): If degree > order Don't throw, return 0.
* testsuite/special_functions/02_assoc_legendre/pr86655.cc: New test.
* testsuite/special_functions/20_sph_legendre/pr86655.cc: New test.
* testsuite/tr1/5_numerical_facilities/special_functions/
02_assoc_legendre/pr86655.cc: New test.
* testsuite/tr1/5_numerical_facilities/special_functions/
22_sph_legendre/pr86655.cc: New test.
>From gcc-bugs-return-628865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 20:59:59 2019
Return-Path: <gcc-bugs-return-628865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10438 invoked by alias); 11 Jan 2019 20:59: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 10394 invoked by uid 48); 11 Jan 2019 20:59:55 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] New: gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Fri, 11 Jan 2019 20:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01674.txt.bz2
Content-length: 1229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
Bug ID: 88810
Summary: gcc/fortran/dependency.c:2200: possible cut'n'paste
error ?
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
gcc/fortran/dependency.c:2200] -> [trunk/gcc/fortran/dependency.c:2205]:
(style) The if condition is the same as the previous if condition
Source code is
/* Set reverse if backward dependence and not inhibited. */
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
reverse[m] = (this_dep == GFC_DEP_BACKWARD) ?
GFC_REVERSE_SET : reverse[m];
/* Set forward if forward dependence and not inhibited. */
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
reverse[m] = (this_dep == GFC_DEP_FORWARD) ?
GFC_FORWARD_SET : reverse[m];
Comment and code on 2nd if don't match.
>From gcc-bugs-return-628866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:04:29 2019
Return-Path: <gcc-bugs-return-628866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41443 invoked by alias); 11 Jan 2019 21:04:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41334 invoked by uid 55); 11 Jan 2019 21:04:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88733] [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Fri, 11 Jan 2019 21:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88733-4-lM1GXwcuPh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01676.txt.bz2
Content-length: 1391
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 11 21:03:53 2019
New Revision: 267858
URL: https://gcc.gnu.org/viewcvs?rev=267858&root=gcc&view=rev
Log:
PR middle-end/85956
PR lto/88733
* tree-inline.h (struct copy_body_data): Add adjust_array_error_bounds
field.
* tree-inline.c (remap_type_1): Formatting fix. If TYPE_MAX_VALUE of
ARRAY_TYPE's TYPE_DOMAIN is newly error_mark_node, replace it with
a dummy "omp dummy var" variable if id->adjust_array_error_bounds.
* omp-low.c (new_omp_context): Set cb.adjust_array_error_bounds.
fortran/
* trans-openmp.c: Include attribs.h.
(gfc_walk_alloc_comps, gfc_omp_clause_linear_ctor): Handle
VAR_DECL max bound with "omp dummy var" attribute like NULL or
error_mark_node - recompute number of elts independently.
testsuite/
* c-c++-common/gomp/pr85956.c: New test.
* g++.dg/gomp/pr88733.C: New test.
Added:
trunk/gcc/testsuite/c-c++-common/gomp/pr85956.c
trunk/gcc/testsuite/g++.dg/gomp/pr88733.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-openmp.c
trunk/gcc/omp-low.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-inline.c
trunk/gcc/tree-inline.h
>From gcc-bugs-return-628867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:04:29 2019
Return-Path: <gcc-bugs-return-628867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41446 invoked by alias); 11 Jan 2019 21:04:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41326 invoked by uid 55); 11 Jan 2019 21:04:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85956] [8/9 Regression] ICE in wide_int_to_tree_1, at tree.c:1549
Date: Fri, 11 Jan 2019 21:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85956-4-6Kp1LzXq8I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85956-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01675.txt.bz2
Content-length: 1391
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85956
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri Jan 11 21:03:53 2019
New Revision: 267858
URL: https://gcc.gnu.org/viewcvs?rev=267858&root=gcc&view=rev
Log:
PR middle-end/85956
PR lto/88733
* tree-inline.h (struct copy_body_data): Add adjust_array_error_bounds
field.
* tree-inline.c (remap_type_1): Formatting fix. If TYPE_MAX_VALUE of
ARRAY_TYPE's TYPE_DOMAIN is newly error_mark_node, replace it with
a dummy "omp dummy var" variable if id->adjust_array_error_bounds.
* omp-low.c (new_omp_context): Set cb.adjust_array_error_bounds.
fortran/
* trans-openmp.c: Include attribs.h.
(gfc_walk_alloc_comps, gfc_omp_clause_linear_ctor): Handle
VAR_DECL max bound with "omp dummy var" attribute like NULL or
error_mark_node - recompute number of elts independently.
testsuite/
* c-c++-common/gomp/pr85956.c: New test.
* g++.dg/gomp/pr88733.C: New test.
Added:
trunk/gcc/testsuite/c-c++-common/gomp/pr85956.c
trunk/gcc/testsuite/g++.dg/gomp/pr88733.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-openmp.c
trunk/gcc/omp-low.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-inline.c
trunk/gcc/tree-inline.h
>From gcc-bugs-return-628869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:05:40 2019
Return-Path: <gcc-bugs-return-628869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44038 invoked by alias); 11 Jan 2019 21:05:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43964 invoked by uid 48); 11 Jan 2019 21:05:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85956] [8 Regression] ICE in wide_int_to_tree_1, at tree.c:1549
Date: Fri, 11 Jan 2019 21:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openmp, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to short_desc
Message-ID: <bug-85956-4-9Tcm4pLMj0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85956-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85956-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01678.txt.bz2
Content-length: 735
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85956
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Assignee|msebor at gcc dot gnu.org |jakub at gcc dot gnu.org
Summary|[8/9 Regression] ICE in |[8 Regression] ICE in
|wide_int_to_tree_1, at |wide_int_to_tree_1, at
|tree.c:1549 |tree.c:1549
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed on the trunk only so far.
>From gcc-bugs-return-628868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:05:21 2019
Return-Path: <gcc-bugs-return-628868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43212 invoked by alias); 11 Jan 2019 21:05: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 43150 invoked by uid 48); 11 Jan 2019 21:05:18 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88733] [9 Regression] ICE in wide_int_to_tree_1, at tree.c:1561
Date: Fri, 11 Jan 2019 21:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to
Message-ID: <bug-88733-4-ftiKnI7Kd8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01677.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88733
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:06:10 2019
Return-Path: <gcc-bugs-return-628870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44997 invoked by alias); 11 Jan 2019 21:06: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 44924 invoked by uid 48); 11 Jan 2019 21:06:06 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88811] New: libstdc++-v3/src/filesystem/path.cc:503: possible cut'n'paste error ?
Date: Fri, 11 Jan 2019 21:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01679.txt.bz2
Content-length: 1037
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88811
Bug ID: 88811
Summary: libstdc++-v3/src/filesystem/path.cc:503: possible
cut'n'paste error ?
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
trunk/libstdc++-v3/src/filesystem/path.cc:503] ->
[trunk/libstdc++-v3/src/filesystem/path.cc:509]: (style) The if condition is
the same as the previous if condition
Source code is
if (!pstr1.empty())
{
w += " [";
w += pstr1;
w += ']';
}
if (!pstr1.empty())
{
w += " [";
w += pstr2;
w += ']';
}
Maybe better code
if (!pstr1.empty())
{
w += " [";
w += pstr1;
w += ']';
}
if (!pstr2.empty())
{
w += " [";
w += pstr2;
w += ']';
}
>From gcc-bugs-return-628871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:10:35 2019
Return-Path: <gcc-bugs-return-628871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50256 invoked by alias); 11 Jan 2019 21:10: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 50191 invoked by uid 48); 11 Jan 2019 21:10:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88806] extern "C" variables declared in different namespaces are considered different
Date: Fri, 11 Jan 2019 21:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88806-4-js3krqDRzN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88806-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88806-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01680.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88806
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
>From gcc-bugs-return-628872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 21:14:33 2019
Return-Path: <gcc-bugs-return-628872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118120 invoked by alias); 11 Jan 2019 21:14:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118061 invoked by uid 48); 11 Jan 2019 21:14:29 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Fri, 11 Jan 2019 21: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: 8.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: cc
Message-ID: <bug-88810-4-FXDSfGzMQE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01681.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org,
| |pault at gcc dot gnu.org
--- Comment #1 from kargl at gcc dot gnu.org ---
Paul
'svn blame' points a finger at you with r212486.
Does this section of code ring a bell.
>From gcc-bugs-return-628873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:07:37 2019
Return-Path: <gcc-bugs-return-628873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54230 invoked by alias); 11 Jan 2019 22:07: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 54167 invoked by uid 48); 11 Jan 2019 22:07:33 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] [9 Regression] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 11 Jan 2019 22:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88699-4-EGWins2DPH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01682.txt.bz2
Content-length: 1221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
The crash occurs during this assertion in add_method:
1136 /* A class should never have more than one destructor. */
1137 gcc_assert (!current_fns || !DECL_DESTRUCTOR_P (method));
when method is a using_decl whereas DECL_DESTRUCTOR_P presumably wants a
function_decl.
This patch stops the crash for comment #4 (though maybe it's papering over the
problem):
diff --git a/gcc/cp/class.c b/gcc/cp/class.c
index e7897f2..e8773c2 100644
--- a/gcc/cp/class.c
+++ b/gcc/cp/class.c
@@ -1134,7 +1134,7 @@ add_method (tree type, tree method, bool via_using)
}
/* A class should never have more than one destructor. */
- gcc_assert (!current_fns || !DECL_DESTRUCTOR_P (method));
+ gcc_assert (!current_fns || via_using || !DECL_DESTRUCTOR_P (method));
current_fns = ovl_insert (method, current_fns, via_using);
>From gcc-bugs-return-628874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:09:48 2019
Return-Path: <gcc-bugs-return-628874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56113 invoked by alias); 11 Jan 2019 22:09: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 55983 invoked by uid 48); 11 Jan 2019 22:09:44 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88555] [9 Regression] Pack expansion fails
Date: Fri, 11 Jan 2019 22:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution assigned_to
Message-ID: <bug-88555-4-TkpUz7GEAr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88555-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88555-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01683.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88555
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Yes.
*** This bug has been marked as a duplicate of bug 88312 ***
>From gcc-bugs-return-628875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:09:48 2019
Return-Path: <gcc-bugs-return-628875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56252 invoked by alias); 11 Jan 2019 22:09: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 56039 invoked by uid 48); 11 Jan 2019 22:09:44 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88312] [9 regression] Mishandled explicitly provided parameter pack
Date: Fri, 11 Jan 2019 22:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88312-4-VIp6aaScUo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01684.txt.bz2
Content-length: 434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88312
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eric at efcs dot ca
--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 88555 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-628876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:10:28 2019
Return-Path: <gcc-bugs-return-628876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57816 invoked by alias); 11 Jan 2019 22:10:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57741 invoked by uid 48); 11 Jan 2019 22:10:24 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88312] [9 regression] Mishandled explicitly provided parameter pack
Date: Fri, 11 Jan 2019 22:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88312-4-x3UQS7uJo2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01685.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88312
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
>From gcc-bugs-return-628877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:11:46 2019
Return-Path: <gcc-bugs-return-628877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59309 invoked by alias); 11 Jan 2019 22: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 59246 invoked by uid 48); 11 Jan 2019 22:11:42 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] [9 Regression] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Fri, 11 Jan 2019 22:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88699-4-LatjJGlrPc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01686.txt.bz2
Content-length: 324
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to David Malcolm from comment #5)
[...]
> This patch stops the crash for comment #4 (though maybe it's papering over
> the problem):
[...]
It also fixes the ICE from the original reproducer.
>From gcc-bugs-return-628878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:12:28 2019
Return-Path: <gcc-bugs-return-628878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60407 invoked by alias); 11 Jan 2019 22:12: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 60350 invoked by uid 48); 11 Jan 2019 22:12:25 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86740] [8/9 Regression] ICE with hana and nested lambdas (likely a regression, tsubst_copy, at cp/pt.c:15325)
Date: Fri, 11 Jan 2019 22:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-86740-4-g2kvVg8gzw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01687.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86740
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jason at gcc dot gnu.org
>From gcc-bugs-return-628879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:24:33 2019
Return-Path: <gcc-bugs-return-628879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76580 invoked by alias); 11 Jan 2019 22:24:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76534 invoked by uid 48); 11 Jan 2019 22:24:29 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88804] Inconsistently diagnosed unused but set static variable in lambda
Date: Fri, 11 Jan 2019 22:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed cf_known_to_fail
Message-ID: <bug-88804-4-46dfYMOR1y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01688.txt.bz2
Content-length: 764
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88804
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |5.4.0, 6.3.0, 7.3.0, 8.2.0,
| |9.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed as far back as GCC 5.
>From gcc-bugs-return-628880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:28:53 2019
Return-Path: <gcc-bugs-return-628880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84503 invoked by alias); 11 Jan 2019 22:28: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 84401 invoked by uid 48); 11 Jan 2019 22:28:49 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88423] [9 Regression] ICE in begin_move_insn, at sched-ebb.c:175
Date: Fri, 11 Jan 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: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88423-4-8YZl4FKuZ6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01689.txt.bz2
Content-length: 983
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88423
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
It's failing the assertion for a NULL edge at line 175:
#1 0x0000000001644fa1 in begin_move_insn (insn=0x7ffff1a4a1f8,
last=0x7ffff18c1a00) at ../../src/gcc/sched-ebb.c:175
175 gcc_checking_assert (BARRIER_P (x));
(gdb) list
170 {
171 rtx_insn *x = NEXT_INSN (insn);
172 if (e)
173 gcc_checking_assert (NOTE_P (x) || LABEL_P (x));
174 else
175 gcc_checking_assert (BARRIER_P (x));
176 }
with a code_label, rather than a barrier:
(gdb) call debug (x)
(code_label 20 19 21 4 (nil) [2 uses])
>From gcc-bugs-return-628881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:30:51 2019
Return-Path: <gcc-bugs-return-628881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87442 invoked by alias); 11 Jan 2019 22:30:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87372 invoked by uid 48); 11 Jan 2019 22:30:46 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] gfortran documentation warning: '.' or ',' must follow @xref
Date: Fri, 11 Jan 2019 22:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88803-4-uKAC8lAJFG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01690.txt.bz2
Content-length: 1578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
CC| |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
More annoying than the warnings id the text displayed in the manual:
the See CONVERT specifier on the open statement or the See
GFORTRAN_CONVERT_UNIT environment variable.
The text has been introduced at revision r251074.
Would
--- ../_clean/gcc/fortran/gfortran.texi 2019-01-01 13:17:33.000000000 +0100
+++ gcc/fortran/gfortran.texi 2019-01-11 23:23:55.000000000 +0100
@@ -1469,8 +1469,8 @@ are four-byte integers by default, and e
compability only) is in effect.
The representation of the record markers is that of unformatted files
-given with the @option{-fconvert} option, the @xref{CONVERT specifier}
-on the open statement or the @xref{GFORTRAN_CONVERT_UNIT} environment
+given with the @option{-fconvert} option, the @ref{CONVERT specifier}
+in an open statement or the @ref{GFORTRAN_CONVERT_UNIT} environment
variable.
The maximum number of bytes of user data in a subrecord is 2147483639
be OK? or does it exist a better replacement for @xref?
>From gcc-bugs-return-628882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:33:21 2019
Return-Path: <gcc-bugs-return-628882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94421 invoked by alias); 11 Jan 2019 22:33:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94394 invoked by uid 48); 11 Jan 2019 22:33:17 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88812] New: Implement C++20 LWG 2499/P0487R1 - Fixing operator>>(basic_istream&, CharT*)
Date: Fri, 11 Jan 2019 22:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01691.txt.bz2
Content-length: 1468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88812
Bug ID: 88812
Summary: Implement C++20 LWG 2499/P0487R1 - Fixing
operator>>(basic_istream&, CharT*)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: emsr at gcc dot gnu.org
Target Milestone: ---
http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0487r1.html
TL;DR Just like deletion of gets() the operator>>(char* str) need to be
replaced by ones that take sized buffers:
#if __cplusplus > 201703L
// Not in LWG2499/P0487R1
template<std::size_t _Num>
basic_istream<char>&
operator>>(basic_istream<char>& __in, char (&__s)[_Num]);
template<typename _Traits, std::size_t _Num>
inline basic_istream<char, _Traits>&
operator>>(basic_istream<char, _Traits>& __in, unsigned char (&__s)[_Num])
{ return (__in >> reinterpret_cast<char*>(__s)); }
template<typename _Traits, std::size_t _Num>
inline basic_istream<char, _Traits>&
operator>>(basic_istream<char, _Traits>& __in, signed char (&__s)[_Num])
{ return (__in >> reinterpret_cast<char*>(__s)); }
#endif
No, I don't have a complete patch.
We'll need to figure out migration deprecation strategies, ABI compatibility
(keep old sigs in istream.cc, just don't declare publicly?).
>From gcc-bugs-return-628883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:36:57 2019
Return-Path: <gcc-bugs-return-628883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51296 invoked by alias); 11 Jan 2019 22: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 50913 invoked by uid 55); 11 Jan 2019 22:36:51 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88613] [9 Regression] ICE in size_binop_loc at fold-const.c:1900 since r267272
Date: Fri, 11 Jan 2019 22:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88613-4-qm8c3SF7v1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01692.txt.bz2
Content-length: 1150
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88613
--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Fri Jan 11 22:36:20 2019
New Revision: 267859
URL: https://gcc.gnu.org/viewcvs?rev=267859&root=gcc&view=rev
Log:
PR c++/88613 - ICE with use of const var in lambda.
The issue here was that we were cp_folding a location wrapper around a
lambda capture proxy before it had been mark_rvalue_used. I considered
adding mark_rvalue_use calls to build_new_op_1, but it seems appropriate to
have them in cp_fold_maybe_rvalue when we know we're trying to produce an
rvalue.
The change to mark_use is for a related issue: when we change the operand of
the location wrapper from VAR_DECL to INTEGER_CST, we need the TREE_CODE of
the location wrapper to change as well, from VIEW_CONVERT_EXPR to
NON_LVALUE_EXPR.
* expr.c (mark_use): Fix location wrapper handling.
* cp-gimplify.c (cp_fold_maybe_rvalue): Call mark_rvalue_use.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/lambda/lambda-const10.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-gimplify.c
trunk/gcc/cp/expr.c
>From gcc-bugs-return-628884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:37:43 2019
Return-Path: <gcc-bugs-return-628884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56771 invoked by alias); 11 Jan 2019 22:37: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 56062 invoked by uid 55); 11 Jan 2019 22:37:36 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88312] [9 regression] Mishandled explicitly provided parameter pack
Date: Fri, 11 Jan 2019 22:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88312-4-BYaDFtuBZa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01693.txt.bz2
Content-length: 725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88312
--- Comment #3 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Fri Jan 11 22:37:01 2019
New Revision: 267860
URL: https://gcc.gnu.org/viewcvs?rev=267860&root=gcc&view=rev
Log:
PR c++/88312 - pack expansion of decltype.
The standard doesn't really talk about an expression depending on the number
of elements of a pack, but that's definitely an important form of template
argument dependence.
* pt.c (instantiation_dependent_r): A template non-type parameter
pack is instantiation-dependent.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/variadic-decltype1.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/pt.c
>From gcc-bugs-return-628885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:52:58 2019
Return-Path: <gcc-bugs-return-628885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124852 invoked by alias); 11 Jan 2019 22:52: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 124803 invoked by uid 48); 11 Jan 2019 22:52:54 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88294] [9 Regression] ICE on (invalid) C++11 code: in tsubst_copy, at cp/pt.c:15391
Date: Fri, 11 Jan 2019 22:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88294-4-vv09b3PTPu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88294-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88294-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01694.txt.bz2
Content-length: 2263
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88294
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
It's a failing assertion:
15401 gcc_assert (cp_unevaluated_operand != 0);
within tsubst_copy's PARM_DECL handling of a "this" PARM_DECL:
(gdb) p t
$2 = <parm_decl 0x7ffff18d7380 this>
15389 case PARM_DECL:
15390 r = retrieve_local_specialization (t);
15391
15392 if (r == NULL_TREE)
15393 {
15394 /* We get here for a use of 'this' in an NSDMI. */
15395 if (DECL_NAME (t) == this_identifier && current_class_ptr)
15396 return current_class_ptr;
15397
15398 /* This can happen for a parameter name used later in a
function
15399 declaration (such as in a late-specified return type).
Just
15400 make a dummy decl, since it's only used for its type. */
15401 gcc_assert (cp_unevaluated_operand != 0);
15402 r = tsubst_decl (t, args, complain);
where the local specialization is NULL.
The PARM_DECL in question is created by the hunk from r266224, which is calling
inject_this_parameter for the "noexcept" fn, in
cp_parser_noexcept_specification_opt
25032 if (current_class_type)
25033 inject_this_parameter (current_class_type,
TYPE_UNQUALIFIED);
This sets current_class_ptr to the "this" PARM_DECL.
It then resets current_class_ptr back to NULL here:
25055 current_class_ptr = save_ccp;
Later, in tsubst_copy on the PARM_DECL in the code quoted above, the PARM_DECL
matches only part of the test here:
15395 if (DECL_NAME (t) == this_identifier && current_class_ptr)
15396 return current_class_ptr;
in that it's DECL_NAME is indeed this_identifier, but current_class_ptr is
NULL, and so we carry on to the assertion:
15401 gcc_assert (cp_unevaluated_operand != 0);
which fails.
>From gcc-bugs-return-628886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 22:58:31 2019
Return-Path: <gcc-bugs-return-628886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66888 invoked by alias); 11 Jan 2019 22:58: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 66821 invoked by uid 48); 11 Jan 2019 22:58:27 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Fri, 11 Jan 2019 22:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on everconfirmed bug_severity
Message-ID: <bug-88810-4-BpL0aKxAJa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01695.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
Severity|normal |minor
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
AFAIU the logic is OK, but the second comment looks strange.
>From gcc-bugs-return-628887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:00:30 2019
Return-Path: <gcc-bugs-return-628887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70939 invoked by alias); 11 Jan 2019 23:00:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70634 invoked by uid 48); 11 Jan 2019 23:00:13 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] misleading indentation warnings building libgfortran
Date: Fri, 11 Jan 2019 23:00: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88807-4-tXy7lR6MNO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01696.txt.bz2
Content-length: 609
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-11
Ever confirmed|0 |1
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Would it be possible to silence the warnings with the option
-Wno-misleading-indentation when building libgfortran/generated?
>From gcc-bugs-return-628888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:13:46 2019
Return-Path: <gcc-bugs-return-628888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83058 invoked by alias); 11 Jan 2019 23:13:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82993 invoked by uid 48); 11 Jan 2019 23:13:41 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88813] New: snprintf less optimal than sprintf for %s with big enough destination
Date: Fri, 11 Jan 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01697.txt.bz2
Content-length: 1962
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88813
Bug ID: 88813
Summary: snprintf less optimal than sprintf for %s with big
enough destination
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The discussion of the background on pr88793
(https://bugzilla.redhat.com/show_bug.cgi?id=1480664) made me realize that GCC
could do a better job optimizing some common snprintf calls.
Specifically, it transforms calls to sprintf(d, "%s", s) to strcpy(d, s), and
it similarly transforms calls to snprintf(d, sizeof d, "%s", s) to memcpy(d, s,
strlen(s) + 1) if it can tell that strlen(s) is less than sizeof(d).
Unfortunately, it can only tell that for constant strings, and it doesn't
consider array sizes. It should be able to both (a) track string lengths (by
relying on the strlen pass), and also (b) make use of array sizes and transform
snprintf(d, sizeof d, "%s", s) to strcpy(d, s) whenever sizeof(s) <= sizeof(d).
(a) is planned for GCC 10. (b)
Below is a test case where GCC could emit optimal code for both functions:
$ cat z.c && gcc -O2 -S -Wall -fdump-tree-optimized=/dev/stdout z.c
char d[8];
char s[8];
void f (void)
{
__builtin_sprintf (d, "%s", s); // optimized
}
void g (void)
{
__builtin_snprintf (d, sizeof d, "%s", s); // not optimized
}
;; Function f (f, funcdef_no=0, decl_uid=1908, cgraph_uid=1, symbol_order=2)
f ()
{
<bb 2> [local count: 1073741824]:
__builtin_strcpy (&d, &s); [tail call]
return;
}
;; Function g (g, funcdef_no=1, decl_uid=1911, cgraph_uid=2, symbol_order=3)
g ()
{
<bb 2> [local count: 1073741824]:
__builtin_snprintf (&d, 8, "%s", &s); [tail call]
return;
}
>From gcc-bugs-return-628889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:22:17 2019
Return-Path: <gcc-bugs-return-628889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13722 invoked by alias); 11 Jan 2019 23:22: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 13651 invoked by uid 55); 11 Jan 2019 23:22:13 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] [9 Regression] Spurious "redundant move in return statement"
Date: Fri, 11 Jan 2019 23:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88692-4-zZpkIcPsb3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01698.txt.bz2
Content-length: 758
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Fri Jan 11 23:21:40 2019
New Revision: 267862
URL: https://gcc.gnu.org/viewcvs?rev=267862&root=gcc&view=rev
Log:
PR c++/88692, c++/87882 - -Wredundant-move false positive with *this.
* typeck.c (maybe_warn_pessimizing_move): Return if ARG isn't
ADDR_EXPR.
* g++.dg/cpp0x/Wredundant-move5.C: New test.
* g++.dg/cpp0x/Wredundant-move6.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/Wredundant-move5.C
trunk/gcc/testsuite/g++.dg/cpp0x/Wredundant-move6.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/typeck.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:26:56 2019
Return-Path: <gcc-bugs-return-628890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29221 invoked by alias); 11 Jan 2019 23:26: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 16917 invoked by uid 48); 11 Jan 2019 23:26:52 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88692] [9 Regression] Spurious "redundant move in return statement"
Date: Fri, 11 Jan 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88692-4-NjICLUxrmc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01699.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88692
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:27:19 2019
Return-Path: <gcc-bugs-return-628891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92596 invoked by alias); 11 Jan 2019 23:27: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 78608 invoked by uid 48); 11 Jan 2019 23:27:15 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87882] -Wredundant-move false positive
Date: Fri, 11 Jan 2019 23:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87882-4-IqHmeeLdqd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87882-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01700.txt.bz2
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87882
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Should be fixed by r267862.
>From gcc-bugs-return-628892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:41:41 2019
Return-Path: <gcc-bugs-return-628892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59114 invoked by alias); 11 Jan 2019 23:41:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55162 invoked by uid 55); 11 Jan 2019 23:41:36 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35031] ELEMENTAL procedure with BIND(C)
Date: Fri, 11 Jan 2019 23:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-35031-4-QE2S7VJ8P5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01701.txt.bz2
Content-length: 696
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35031
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Fri Jan 11 23:41:04 2019
New Revision: 267864
URL: https://gcc.gnu.org/viewcvs?rev=267864&root=gcc&view=rev
Log:
2019-01-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/35031
* decl.c (gfc_match_entry): Check for F2018:C1546. Fix nearby
mis-indentation.
2019-01-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/35031
* gfortran.dg/pr35031.f90: new test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr35031.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/decl.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:46:56 2019
Return-Path: <gcc-bugs-return-628893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32681 invoked by alias); 11 Jan 2019 23:46: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 32607 invoked by uid 48); 11 Jan 2019 23:46:51 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88812] Implement C++20 LWG 2499/P0487R1 - Fixing operator>>(basic_istream&, CharT*)
Date: Fri, 11 Jan 2019 23:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88812-4-QwaxdebzBa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01702.txt.bz2
Content-length: 2103
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88812
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-11
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to emsr from comment #0)
> http://www.open-std.org/JTC1/SC22/WG21/docs/papers/2018/p0487r1.html
>
> TL;DR Just like deletion of gets() the operator>>(char* str) need to be
> replaced by ones that take sized buffers:
>
> #if __cplusplus > 201703L
> // Not in LWG2499/P0487R1
> template<std::size_t _Num>
> basic_istream<char>&
> operator>>(basic_istream<char>& __in, char (&__s)[_Num]);
>
> template<typename _Traits, std::size_t _Num>
> inline basic_istream<char, _Traits>&
> operator>>(basic_istream<char, _Traits>& __in, unsigned char
> (&__s)[_Num])
> { return (__in >> reinterpret_cast<char*>(__s)); }
This cast needs to be to char(&)[_Num] or it tries to call the old signature.
>
> template<typename _Traits, std::size_t _Num>
> inline basic_istream<char, _Traits>&
> operator>>(basic_istream<char, _Traits>& __in, signed char (&__s)[_Num])
> { return (__in >> reinterpret_cast<char*>(__s)); }
Same here.
> #endif
>
> No, I don't have a complete patch.
Coincidentally I just implemented this.
> We'll need to figure out migration deprecation strategies, ABI compatibility
> (keep old sigs in istream.cc, just don't declare publicly?).
I think we should keep the old declarations for C++98 - C++17 in the public
headers. We definitely need to keep exporting the definition from the library.
We can add the new declarations for C++2a only (and maybe for -std=gnu++NN
modes too, or expose them via some new macro, to allow users to either opt in
or opt out).
>From gcc-bugs-return-628894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:47:03 2019
Return-Path: <gcc-bugs-return-628894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33374 invoked by alias); 11 Jan 2019 23:47:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32968 invoked by uid 48); 11 Jan 2019 23:46:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88812] Implement C++20 LWG 2499/P0487R1 - Fixing operator>>(basic_istream&, CharT*)
Date: Fri, 11 Jan 2019 23:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-88812-4-2enZIOPrOd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01703.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88812
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|enhancement |normal
>From gcc-bugs-return-628895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:53:44 2019
Return-Path: <gcc-bugs-return-628895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47523 invoked by alias); 11 Jan 2019 23:53:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47487 invoked by uid 48); 11 Jan 2019 23:53:40 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88814] New: transform snprintf into memccpy
Date: Fri, 11 Jan 2019 23:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01704.txt.bz2
Content-length: 957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88814
Bug ID: 88814
Summary: transform snprintf into memccpy
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
In addition to bug 88813, prompted by the discussion of the background on
pr88793 (https://bugzilla.redhat.com/show_bug.cgi?id=1480664), another
optimization opportunity is to replace snprintf(d, n, "%s", s) calls with
non-zero n with:
memccpy(d, s, 0, n - 1);
d[n - 1] = 0;
Memccpy is not a standard C function but it is in POSIX so GCC configury would
have to detect support for it in order to enable it. GCC also doesn't
recognize memccpy as a built-in so adding such support could yield additional
improvements.
>From gcc-bugs-return-628896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Jan 11 23:54:45 2019
Return-Path: <gcc-bugs-return-628896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48735 invoked by alias); 11 Jan 2019 23:54:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48695 invoked by uid 48); 11 Jan 2019 23:54:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88811] libstdc++-v3/src/filesystem/path.cc:503: possible cut'n'paste error ?
Date: Fri, 11 Jan 2019 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on version assigned_to target_milestone everconfirmed
Message-ID: <bug-88811-4-HZAmNtPUik@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01705.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88811
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-11
Version|8.0 |9.0
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
>From gcc-bugs-return-628897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:06:12 2019
Return-Path: <gcc-bugs-return-628897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59994 invoked by alias); 12 Jan 2019 00:06: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 59919 invoked by uid 48); 12 Jan 2019 00:06:08 -0000
From: "programmer at posteo dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] New: [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Sat, 12 Jan 2019 00:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: programmer at posteo 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-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01706.txt.bz2
Content-length: 1264
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
Bug ID: 88815
Summary: [9 Regression] is_constexpr (based on narrowing
conversion and expression SFINAE) broken
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: programmer at posteo dot de
Target Milestone: ---
[note: following code adopted from
https://stackoverflow.com/a/50169108/2615118]
The following experiment of an "is_constexpr" implementation fails on GCC 9.
https://godbolt.org/z/xDiFet
// BEGIN CODE
struct true_type {
constexpr operator bool() const { return true; }
};
struct false_type {
constexpr operator bool() const { return false; }
};
template<int (*p)()>
true_type is_constexpr_impl(decltype(int{(p(), 0U)}));// narrowing conversion
template<int (*p)()>
false_type is_constexpr_impl(...);
template<int (*p)()>
using is_constexpr = decltype(is_constexpr_impl<p>(0));
constexpr int f() { return 0; }
int g() { return 0; }
static_assert(is_constexpr<f>());
static_assert(!is_constexpr<g>());// this one fails in GCC 9.0.0 20190109
// END CODE
>From gcc-bugs-return-628898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:12:44 2019
Return-Path: <gcc-bugs-return-628898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128541 invoked by alias); 12 Jan 2019 00:12:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127649 invoked by uid 48); 12 Jan 2019 00:12:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88811] libstdc++-v3/src/filesystem/path.cc:503: possible cut'n'paste error ?
Date: Sat, 12 Jan 2019 00:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88811-4-HE3Sm8l6gX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01707.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88811
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed, thanks.
>From gcc-bugs-return-628899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:13:01 2019
Return-Path: <gcc-bugs-return-628899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5606 invoked by alias); 12 Jan 2019 00:13:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1005 invoked by uid 55); 12 Jan 2019 00:12:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83306] filesystem_error is not nothrow copyable
Date: Sat, 12 Jan 2019 00:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83306-4-EIjsmwYjVC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83306-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83306-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01708.txt.bz2
Content-length: 818
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83306
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sat Jan 12 00:12:20 2019
New Revision: 267868
URL: https://gcc.gnu.org/viewcvs?rev=267868&root=gcc&view=rev
Log:
PR libstdc++/88811 fix typo introduced in r266569
PR libstdc++/88811
PR libstdc++/83306
* src/filesystem/path.cc: Fix typo. If first path is empty, show []
before second path.
* testsuite/experimental/filesystem/filesystem_error/cons.cc: New
test.
Added:
trunk/libstdc++-v3/testsuite/experimental/filesystem/filesystem_error/
trunk/libstdc++-v3/testsuite/experimental/filesystem/filesystem_error/cons.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/filesystem/path.cc
>From gcc-bugs-return-628900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:13:01 2019
Return-Path: <gcc-bugs-return-628900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5671 invoked by alias); 12 Jan 2019 00:13:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 953 invoked by uid 55); 12 Jan 2019 00:12:56 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88811] libstdc++-v3/src/filesystem/path.cc:503: possible cut'n'paste error ?
Date: Sat, 12 Jan 2019 00:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88811-4-YXO0aLudZY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01709.txt.bz2
Content-length: 818
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88811
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sat Jan 12 00:12:20 2019
New Revision: 267868
URL: https://gcc.gnu.org/viewcvs?rev=267868&root=gcc&view=rev
Log:
PR libstdc++/88811 fix typo introduced in r266569
PR libstdc++/88811
PR libstdc++/83306
* src/filesystem/path.cc: Fix typo. If first path is empty, show []
before second path.
* testsuite/experimental/filesystem/filesystem_error/cons.cc: New
test.
Added:
trunk/libstdc++-v3/testsuite/experimental/filesystem/filesystem_error/
trunk/libstdc++-v3/testsuite/experimental/filesystem/filesystem_error/cons.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/filesystem/path.cc
>From gcc-bugs-return-628901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:15:41 2019
Return-Path: <gcc-bugs-return-628901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117805 invoked by alias); 12 Jan 2019 00:15: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 112377 invoked by uid 55); 12 Jan 2019 00:15:32 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35031] ELEMENTAL procedure with BIND(C)
Date: Sat, 12 Jan 2019 00:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-35031-4-7COOgyzb8c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01710.txt.bz2
Content-length: 760
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35031
--- Comment #6 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sat Jan 12 00:14:55 2019
New Revision: 267869
URL: https://gcc.gnu.org/viewcvs?rev=267869&root=gcc&view=rev
Log:
2019-01-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/35031
* decl.c (gfc_match_entry): Check for F2018:C1546. Fix nearby
mis-indentation.
2019-01-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/35031
* gfortran.dg/pr35031.f90: new test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr35031.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/decl.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:16:42 2019
Return-Path: <gcc-bugs-return-628902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11577 invoked by alias); 12 Jan 2019 00:16:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11511 invoked by uid 48); 12 Jan 2019 00:16:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88322] Implement C++20 library features.
Date: Sat, 12 Jan 2019 00:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
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-88322-4-F484LeIsxT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88322-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88322-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01711.txt.bz2
Content-length: 229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88322
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
C+2a status is now documented at
https://gcc.gnu.org/onlinedocs/libstdc++/manual/status.html#status.iso.2020
>From gcc-bugs-return-628903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:18:29 2019
Return-Path: <gcc-bugs-return-628903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13679 invoked by alias); 12 Jan 2019 00:18: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 13613 invoked by uid 48); 12 Jan 2019 00:18:25 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88779] No fix-it hints for misspelled member initializers
Date: Sat, 12 Jan 2019 00:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88779-4-5F78vUMHqL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88779-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88779-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01712.txt.bz2
Content-length: 629
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88779
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-12
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Looks like David's made himself the assignee so setting the status to Assigned.
>From gcc-bugs-return-628904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:18:55 2019
Return-Path: <gcc-bugs-return-628904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14490 invoked by alias); 12 Jan 2019 00:18: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 14435 invoked by uid 48); 12 Jan 2019 00:18:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] misleading indentation warnings building libgfortran
Date: Sat, 12 Jan 2019 00: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-88807-4-Fh9PvJqEF1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01713.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45415
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45415&action=edit
gcc9-pr88807.patch
Or we can just reindent the problematic part. The indentation of the generated
files is indeed weird in many spots on many of the files, but with this simple
patch we don't get a warning.
>From gcc-bugs-return-628905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:33:36 2019
Return-Path: <gcc-bugs-return-628905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27321 invoked by alias); 12 Jan 2019 00:33:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 27239 invoked by uid 55); 12 Jan 2019 00:33:33 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35031] ELEMENTAL procedure with BIND(C)
Date: Sat, 12 Jan 2019 00:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-35031-4-2yTe0goacN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01714.txt.bz2
Content-length: 760
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35031
--- Comment #7 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sat Jan 12 00:33:01 2019
New Revision: 267874
URL: https://gcc.gnu.org/viewcvs?rev=267874&root=gcc&view=rev
Log:
2019-01-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/35031
* decl.c (gfc_match_entry): Check for F2018:C1546. Fix nearby
mis-indentation.
2019-01-11 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/35031
* gfortran.dg/pr35031.f90: new test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/pr35031.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/decl.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:34:22 2019
Return-Path: <gcc-bugs-return-628906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28449 invoked by alias); 12 Jan 2019 00:34: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 28409 invoked by uid 48); 12 Jan 2019 00:34:18 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88762] C++17 Deduction guide and operator expression produces missing template argument error
Date: Sat, 12 Jan 2019 00:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed cf_known_to_fail
Message-ID: <bug-88762-4-ysmuvcFnQB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01715.txt.bz2
Content-length: 620
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88762
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-12
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
Known to fail| |7.3.0, 8.2.0, 9.0
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-628908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:34:33 2019
Return-Path: <gcc-bugs-return-628908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29450 invoked by alias); 12 Jan 2019 00:34:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29212 invoked by uid 48); 12 Jan 2019 00:34:29 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32630] [meta-bug] ISO C binding
Date: Sat, 12 Jan 2019 00:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-32630-4-CVEHSyxDTs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32630-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32630-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01717.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32630
Bug 32630 depends on bug 35031, which changed state.
Bug 35031 Summary: ELEMENTAL procedure with BIND(C)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35031
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:34:33 2019
Return-Path: <gcc-bugs-return-628907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29317 invoked by alias); 12 Jan 2019 00:34:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29145 invoked by uid 48); 12 Jan 2019 00:34:29 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35031] ELEMENTAL procedure with BIND(C)
Date: Sat, 12 Jan 2019 00: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: 4.3.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-35031-4-22kzzuMXb7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35031-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01716.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35031
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|9.0 |7.5
--- Comment #8 from kargl at gcc dot gnu.org ---
Fixed on trunk, branch8, and branch-7. Closing.
>From gcc-bugs-return-628909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 00:35:53 2019
Return-Path: <gcc-bugs-return-628909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31287 invoked by alias); 12 Jan 2019 00:35:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31248 invoked by uid 48); 12 Jan 2019 00:35:49 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] misleading indentation warnings building libgfortran
Date: Sat, 12 Jan 2019 00:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88807-4-DAElrNDyvq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01718.txt.bz2
Content-length: 715
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #4 from kargl at gcc dot gnu.org ---
(In reply to Jakub Jelinek from comment #3)
> Created attachment 45415 [details]
> gcc9-pr88807.patch
>
> Or we can just reindent the problematic part. The indentation of the
> generated files is indeed weird in many spots on many of the files, but with
> this simple patch we don't get a warning.
Jakub, if you patch passes regression testing, please commit it.
>From gcc-bugs-return-628910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 01:04:34 2019
Return-Path: <gcc-bugs-return-628910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66990 invoked by alias); 12 Jan 2019 01:04: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 66950 invoked by uid 48); 12 Jan 2019 01:04:29 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Sat, 12 Jan 2019 01:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc component everconfirmed bug_severity
Message-ID: <bug-88738-4-VHZFlinHOM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01719.txt.bz2
Content-length: 1356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-12
CC| |msebor at gcc dot gnu.org
Component|c++ |libstdc++
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Annotating std::operator==(shared_ptr, nullptr_t) with attribute
warn_unused_result is enough to give a warning for the test case in comment #0.
Handling the test case in comment #1 is a bit more involved because GCC doesn't
issue -Wunused-variable warnings for objects of classes with ctors/dtors, so it
will likely take a compiler enhancement (say, an attribute to request such
warnings for classes whose user-defined ctors and dtors have no side-effects).
I've changed the Component to libstdc++ since that's the easy part (and will
let the library maintainers more quickly chime in on if it's doable and when).
>From gcc-bugs-return-628911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 02:38:26 2019
Return-Path: <gcc-bugs-return-628911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35314 invoked by alias); 12 Jan 2019 02:38: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 35264 invoked by uid 48); 12 Jan 2019 02:38:20 -0000
From: "isj-bugzilla at i1 dot dk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88816] New: Constructor calls itself recursively
Date: Sat, 12 Jan 2019 02:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: isj-bugzilla at i1 dot dk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01720.txt.bz2
Content-length: 2783
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88816
Bug ID: 88816
Summary: Constructor calls itself recursively
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: isj-bugzilla at i1 dot dk
Target Milestone: ---
In the reduced code below the constructor
Value::Value(std::vector<Value, std::allocator<Value> > const&)
calls itself in the generated code leading to stack overflow. There is no such
recursive call in the source code.
Bug produced with versions 7.3.1, 8.2.1. And "trunk" on godbolt.org.
Bug is absent with clang, mscv, and icc.
Optimization and debug levels are irrelevant. It just have so have -std=c++11
or later.
---snip---
#include <vector>
enum class value_type_t {
array,
null,
};
class Value {
void clear() {
switch(value_type) {
case value_type_t::array:
u.array_elements.~array_type();
break;
case value_type_t::null:
break;
}
value_type = value_type_t::null;
}
public:
using array_type = std::vector<Value>;
value_type_t value_type;
union U {
U() {}
~U() {}
array_type array_elements;
} u;
Value()
: value_type{value_type_t::null}
{}
Value(const Value &v)
: value_type{value_type_t::null}
{
*this = v;
}
//This is the constructor that unexpectedly calls itself
Value(const array_type &a) {
new(&u.array_elements) array_type{a};
value_type = value_type_t::array;
}
~Value() {
clear();
}
Value& operator=(const Value &v) {
if(this!=&v) {
clear();
switch(v.value_type) {
case value_type_t::array:
new(&u.array_elements)
array_type{v.u.array_elements};
value_type = value_type_t::array;
return *this;
case value_type_t::null:
value_type = value_type_t::null;
break;
}
}
return *this;
}
};
int main(void) {
Value v{Value::array_type{}};
}
---snip---
>From gcc-bugs-return-628912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 04:35:09 2019
Return-Path: <gcc-bugs-return-628912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66873 invoked by alias); 12 Jan 2019 04:35:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66763 invoked by uid 48); 12 Jan 2019 04:35:02 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61765] [7/8/9 Regression] [F03] Rejects valid BIND(C) ENTRY
Date: Sat, 12 Jan 2019 04:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc assigned_to target_milestone
Message-ID: <bug-61765-4-lhbRsAAPjx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01721.txt.bz2
Content-length: 431
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61765
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |kargl at gcc dot gnu.org
Target Milestone|7.5 |9.0
>From gcc-bugs-return-628913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 04:54:17 2019
Return-Path: <gcc-bugs-return-628913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107727 invoked by alias); 12 Jan 2019 04:54: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 107669 invoked by uid 48); 12 Jan 2019 04:54:13 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/37073] -fno-math-errno should be the default on FreeBSD
Date: Sat, 12 Jan 2019 04:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-37073-4-jSZZDS8w4S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37073-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37073-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01722.txt.bz2
Content-length: 338
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37073
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Gerald Pfeifer from comment #2)
> I'll see what I can do about this.
Did you mean to put yourself as the assignee for this, instead of just on cc? I
mean, since you changed the status to ASSIGNED...
>From gcc-bugs-return-628914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 04:56:18 2019
Return-Path: <gcc-bugs-return-628914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112231 invoked by alias); 12 Jan 2019 04:56:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112182 invoked by uid 48); 12 Jan 2019 04:56:14 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/64101] GCC considers that the erf math function does not set errno
Date: Sat, 12 Jan 2019 04:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.7.4
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64101-4-uc8NqdD5pP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64101-4@http.gcc.gnu.org/bugzilla/>
References: <bug-64101-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01723.txt.bz2
Content-length: 219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64101
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
possibly related to some of the other -fmath-errno bugs that have been under
discussion lately?
>From gcc-bugs-return-628915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 07:40:33 2019
Return-Path: <gcc-bugs-return-628915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18982 invoked by alias); 12 Jan 2019 07:40:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18927 invoked by uid 48); 12 Jan 2019 07:40:29 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61765] [7/8/9 Regression] [F03] Rejects valid BIND(C) ENTRY
Date: Sat, 12 Jan 2019 07:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61765-4-w1QoX1FmJF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01724.txt.bz2
Content-length: 160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61765
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Related to/duplicate of pr34500.
>From gcc-bugs-return-628916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 07:42:56 2019
Return-Path: <gcc-bugs-return-628916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20902 invoked by alias); 12 Jan 2019 07:42:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20841 invoked by uid 48); 12 Jan 2019 07:42:50 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34500] Bind(C): Character returning function with ENTRY gives ICE
Date: Sat, 12 Jan 2019 07:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-34500-4-ogjyRwVFcr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34500-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34500-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01725.txt.bz2
Content-length: 2731
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34500
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Related to/duplicate of pr61765.
Note that with the patch at
https://gcc.gnu.org/ml/fortran/2019-01/msg00085.html, the spurious error
pr34500.f90:4:43:
4 | character(len=1,kind=c_char) :: test, bar
| 1
5 | entry bar() bind(C)
| 2
Error: Procedure 'bar' with binding label 'bar' at (1) uses the same global
identifier as entity at (2)
is replaced with an ICE
Process 2220 launched:
'/opt/gcc/gcc9w/libexec/gcc/x86_64-apple-darwin18.2.0/9.0.0/f951' (x86_64)
testProcess 2220 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
frame #0: 0x0000000100106dfc f951`gfc_create_function_decl(gfc_namespace*,
bool) [inlined] contains_struct_check(__g=<unavailable>, __l=<unavailable>,
__f=<unavailable>, __s=<unavailable>, __t=0x0000000000000000) at tree.h:3289
3286 contains_struct_check (tree __t, const enum tree_node_structure_enum
__s,
3287 const char *__f, int __l, const char *__g)
3288 {
-> 3289 if (tree_contains_struct[TREE_CODE (__t)][__s] != 1)
3290 tree_contains_struct_check_failed (__t, __s, __f, __l, __g);
3291 return __t;
3292 }
Target 0: (f951) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
* frame #0: 0x0000000100106dfc f951`gfc_create_function_decl(gfc_namespace*,
bool) [inlined] contains_struct_check(__g=<unavailable>, __l=<unavailable>,
__f=<unavailable>, __s=<unavailable>, __t=0x0000000000000000) at tree.h:3289
frame #1: 0x0000000100106dfc f951`gfc_create_function_decl(gfc_namespace*,
bool)
frame #2: 0x000000010010f593
f951`gfc_generate_function_code(ns=0x000000014306fa00) at trans-decl.c:6420
frame #3: 0x0000000100095214 f951`gfc_parse_file() [inlined]
translate_all_program_units(gfc_global_ns_list=<unavailable>) at parse.c:6134
frame #4: 0x000000010009512a f951`gfc_parse_file()
frame #5: 0x00000001000dd8ec f951`::gfc_be_parse_file() at f95-lang.c:204
frame #6: 0x0000000100c71d0a f951`::compile_file() at toplev.c:456
frame #7: 0x00000001012d9024 f951`toplev::main(int, char**) at
toplev.c:2176
frame #8: 0x00000001012d8ef0 f951`toplev::main(this=0x00007ffeefbff09e,
argc=<unavailable>, argv=<unavailable>)
frame #9: 0x00000001012db891 f951`main(argc=2, argv=0x00007ffeefbff0d8) at
main.c:39
>From gcc-bugs-return-628917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 07:50:18 2019
Return-Path: <gcc-bugs-return-628917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50276 invoked by alias); 12 Jan 2019 07:50: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 50212 invoked by uid 48); 12 Jan 2019 07:50:14 -0000
From: "proski at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] False positive -Waddress-of-packed-member
Date: Sat, 12 Jan 2019 07:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: proski at gnu 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: cc
Message-ID: <bug-88664-4-GN231eh7RM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01726.txt.bz2
Content-length: 815
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
Pavel Roskin <proski at gnu dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |proski at gnu dot org
--- Comment #2 from Pavel Roskin <proski at gnu dot org> ---
C is also affected.
int* fun()
{
struct data {
void *ptr;
} __attribute__((packed)) var;
return (int*)(var.ptr);
}
With today's gcc, git master branch:
test.c: In function ‘fun’:
test.c:7:22: warning: taking address of packed member of ‘struct data’ may
result in an unaligned pointer value [-Waddress-of-packed-member]
7 | return (int*)(var.ptr);
| ~~~~^~~~~
>From gcc-bugs-return-628918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 08:32:13 2019
Return-Path: <gcc-bugs-return-628918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107973 invoked by alias); 12 Jan 2019 08:32:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107915 invoked by uid 48); 12 Jan 2019 08:32:09 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] [9 Regression] False positive -Waddress-of-packed-member
Date: Sat, 12 Jan 2019 08:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone short_desc everconfirmed
Message-ID: <bug-88664-4-0dS656prSm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01727.txt.bz2
Content-length: 657
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-12
Target Milestone|--- |9.0
Summary|False positive |[9 Regression] False
|-Waddress-of-packed-member |positive
| |-Waddress-of-packed-member
Ever confirmed|0 |1
>From gcc-bugs-return-628919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 08:39:58 2019
Return-Path: <gcc-bugs-return-628919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112794 invoked by alias); 12 Jan 2019 08:39: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 112729 invoked by uid 48); 12 Jan 2019 08:39:54 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88811] libstdc++-v3/src/filesystem/path.cc:503: possible cut'n'paste error ?
Date: Sat, 12 Jan 2019 08:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88811-4-TTYkl2Tnrm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01728.txt.bz2
Content-length: 427
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88811
--- Comment #3 from David Binderman <dcb314 at hotmail dot com> ---
Minor quibble on one of the lines:
+ (pstr1.length() || pstr2.length() ? pstr1.length() + 3 : 0)
Given the number of folks who fail to read correctly the ternary
operator, would this be better as
+ ((pstr1.length() || pstr2.length()) ? (pstr1.length() + 3) : 0)
to make the meaning more clear ?
>From gcc-bugs-return-628920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 09:10:46 2019
Return-Path: <gcc-bugs-return-628920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11323 invoked by alias); 12 Jan 2019 09:10: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 11272 invoked by uid 48); 12 Jan 2019 09:10:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88811] libstdc++-v3/src/filesystem/path.cc:503: possible cut'n'paste error ?
Date: Sat, 12 Jan 2019 09:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88811-4-emJtBbZs0k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01729.txt.bz2
Content-length: 294
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88811
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think it's pretty obvious from the context.
Parenthesizing the second operand is certainly useless. Obviously the colon
binds to the question mark, not the plus operator.
>From gcc-bugs-return-628921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 09:16:30 2019
Return-Path: <gcc-bugs-return-628921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20193 invoked by alias); 12 Jan 2019 09:16: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 20143 invoked by uid 55); 12 Jan 2019 09:16:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] misleading indentation warnings building libgfortran
Date: Sat, 12 Jan 2019 09: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88807-4-dV9EpHh0EK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01730.txt.bz2
Content-length: 3074
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Sat Jan 12 09:15:54 2019
New Revision: 267875
URL: https://gcc.gnu.org/viewcvs?rev=267875&root=gcc&view=rev
Log:
PR libfortran/88807
* m4/minloc0.m4: Reindent to avoid -Wmisleading-indentation warnings.
* generated/minloc0_4_i1.c: Regenerated.
* generated/minloc0_4_i2.c: Regenerated.
* generated/minloc0_4_i4.c: Regenerated.
* generated/minloc0_4_i8.c: Regenerated.
* generated/minloc0_4_i16.c: Regenerated.
* generated/minloc0_4_r4.c: Regenerated.
* generated/minloc0_4_r8.c: Regenerated.
* generated/minloc0_4_r10.c: Regenerated.
* generated/minloc0_4_r16.c: Regenerated.
* generated/minloc0_8_i1.c: Regenerated.
* generated/minloc0_8_i2.c: Regenerated.
* generated/minloc0_8_i4.c: Regenerated.
* generated/minloc0_8_i8.c: Regenerated.
* generated/minloc0_8_i16.c: Regenerated.
* generated/minloc0_8_r4.c: Regenerated.
* generated/minloc0_8_r8.c: Regenerated.
* generated/minloc0_8_r10.c: Regenerated.
* generated/minloc0_8_r16.c: Regenerated.
* generated/minloc0_16_i1.c: Regenerated.
* generated/minloc0_16_i2.c: Regenerated.
* generated/minloc0_16_i4.c: Regenerated.
* generated/minloc0_16_i8.c: Regenerated.
* generated/minloc0_16_i16.c: Regenerated.
* generated/minloc0_16_r4.c: Regenerated.
* generated/minloc0_16_r8.c: Regenerated.
* generated/minloc0_16_r10.c: Regenerated.
* generated/minloc0_16_r16.c: Regenerated.
Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/generated/minloc0_16_i1.c
trunk/libgfortran/generated/minloc0_16_i16.c
trunk/libgfortran/generated/minloc0_16_i2.c
trunk/libgfortran/generated/minloc0_16_i4.c
trunk/libgfortran/generated/minloc0_16_i8.c
trunk/libgfortran/generated/minloc0_16_r10.c
trunk/libgfortran/generated/minloc0_16_r16.c
trunk/libgfortran/generated/minloc0_16_r4.c
trunk/libgfortran/generated/minloc0_16_r8.c
trunk/libgfortran/generated/minloc0_4_i1.c
trunk/libgfortran/generated/minloc0_4_i16.c
trunk/libgfortran/generated/minloc0_4_i2.c
trunk/libgfortran/generated/minloc0_4_i4.c
trunk/libgfortran/generated/minloc0_4_i8.c
trunk/libgfortran/generated/minloc0_4_r10.c
trunk/libgfortran/generated/minloc0_4_r16.c
trunk/libgfortran/generated/minloc0_4_r4.c
trunk/libgfortran/generated/minloc0_4_r8.c
trunk/libgfortran/generated/minloc0_8_i1.c
trunk/libgfortran/generated/minloc0_8_i16.c
trunk/libgfortran/generated/minloc0_8_i2.c
trunk/libgfortran/generated/minloc0_8_i4.c
trunk/libgfortran/generated/minloc0_8_i8.c
trunk/libgfortran/generated/minloc0_8_r10.c
trunk/libgfortran/generated/minloc0_8_r16.c
trunk/libgfortran/generated/minloc0_8_r4.c
trunk/libgfortran/generated/minloc0_8_r8.c
trunk/libgfortran/m4/minloc0.m4
>From gcc-bugs-return-628922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 09:25:42 2019
Return-Path: <gcc-bugs-return-628922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33906 invoked by alias); 12 Jan 2019 09:25: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 33038 invoked by uid 48); 12 Jan 2019 09:25:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88807] misleading indentation warnings building libgfortran
Date: Sat, 12 Jan 2019 09:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P5
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-88807-4-CXToDishri@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88807-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01731.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88807
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-628923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 10:23:24 2019
Return-Path: <gcc-bugs-return-628923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96428 invoked by alias); 12 Jan 2019 10: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 96348 invoked by uid 48); 12 Jan 2019 10:23:21 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/69788] FAIL: gfortran.dg/derived_constructor_comps_6.f90 -O0 execution test
Date: Sat, 12 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 5.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-69788-4-Fij927jfhB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01732.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69788
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this PR still valid?
I don't see any related failure in
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00581.html.
>From gcc-bugs-return-628924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 10:27:48 2019
Return-Path: <gcc-bugs-return-628924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100618 invoked by alias); 12 Jan 2019 10:27: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 100592 invoked by uid 55); 12 Jan 2019 10:27:44 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88703] oacc_validate_dims allows invalid dimensions
Date: Sat, 12 Jan 2019 10:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88703-4-MdAAKv8fuz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88703-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88703-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01733.txt.bz2
Content-length: 1304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88703
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Sat Jan 12 10:27:12 2019
New Revision: 267877
URL: https://gcc.gnu.org/viewcvs?rev=267877&root=gcc&view=rev
Log:
[nvptx] Verify dimension limits after applying defaults
There's a problem in oacc_validate_dims that when f.i. the worker dimension
is set using -fopenacc-dim=:32, and the vector_length is set using a
"vector_length (128)" clause, the compiler combines, accepts and emits the
values, while the combination of the two is invalid.
The reason for this is that while oacc_validate_dims validates the dimensions
using targetm.goacc.validate_dims before applying default or minimum values,
it does not do so afterwards.
Work around this in the nvptx port by applying the defaults from
oacc_default_dims at the end of nvptx_goacc_validate_dims_1, as
oacc_validate_dims would do it, and then apply the dimensions limits.
2019-01-12 Tom de Vries <tdevries@suse.de>
PR middle-end/88703
* config/nvptx/nvptx.c (nvptx_goacc_validate_dims_1): Apply defaults
from oacc_default_dims, as oacc_validate_dims would do it, and apply
dimensions limits.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/nvptx/nvptx.c
>From gcc-bugs-return-628925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 10:30:46 2019
Return-Path: <gcc-bugs-return-628925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104359 invoked by alias); 12 Jan 2019 10:30: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 104277 invoked by uid 48); 12 Jan 2019 10:30:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Sat, 12 Jan 2019 10:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-88815-4-Yd1TnJrrZa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01734.txt.bz2
Content-length: 743
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-12
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started with r265789.
>From gcc-bugs-return-628926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 10:39:48 2019
Return-Path: <gcc-bugs-return-628926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119786 invoked by alias); 12 Jan 2019 10:39: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 119700 invoked by uid 48); 12 Jan 2019 10:39:44 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Sat, 12 Jan 2019 10:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: drepper.fsp+rhbz at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88738-4-LpNouTj1DE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01735.txt.bz2
Content-length: 952
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #3 from Ulrich Drepper <drepper.fsp+rhbz at gmail dot com> ---
Created attachment 45416
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45416&action=edit
Add nodiscard support
As Martin suggested, we could indeed use existing attributes in library code to
warn about some of the problems. The code from comment #0 is real, this
happened in a project of mine where I mistyped an assignment. The warning
would have pointed to the problem.
How about the following patch for a start? This compiles cleanly on x86-64. I
haven't run the test suite to see whether it breaks some regression tests.
Also, this approach should be extended beyond shared_ptr and unique_ptr,
probably to at least every single bool operatorXX(...) const. Or even every
single const member function which then of course raises the question whether
the compiler should learn about this…
>From gcc-bugs-return-628927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 10:49:52 2019
Return-Path: <gcc-bugs-return-628927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15587 invoked by alias); 12 Jan 2019 10:49:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15497 invoked by uid 48); 12 Jan 2019 10:49:47 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Sat, 12 Jan 2019 10:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-QURibZCkQd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01736.txt.bz2
Content-length: 3341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #10 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
In armv7hl --enable-checking=release profiledbootstrap I see:
checking for strtoull... ../../libdecnumber/decNumber.c: In function 'decLnOp':
../../libdecnumber/decNumber.c:5581:13: error: number of counters in profile
data for function 'decLnOp' does not match its profile data (counter 'arcs',
expected 54 and have 55) [-Werror=coverage-mismatch]
5581 | decNumber * decLnOp(decNumber *res, const decNumber *rhs,
| ^~~~~~~
../../libdecnumber/decNumber.c:5581:13: error: the control flow of function
'decLnOp' does not match its profile data (counter 'time_profiler')
[-Werror=coverage-mismatch]
../../libdecnumber/decNumber.c: In function 'decExpOp':
../../libdecnumber/decNumber.c:5221:13: error: number of counters in profile
data for function 'decExpOp' does not match its profile data (counter 'arcs',
expected 52 and have 53) [-Werror=coverage-mismatch]
5221 | decNumber * decExpOp(decNumber *res, const decNumber *rhs,
| ^~~~~~~~
../../libdecnumber/decNumber.c:5221:13: error: the control flow of function
'decExpOp' does not match its profile data (counter 'time_profiler')
[-Werror=coverage-mismatch]
../../libdecnumber/decNumber.c: In function 'decMultiplyOp':
../../libdecnumber/decNumber.c:4831:20: error: number of counters in profile
data for function 'decMultiplyOp' does not match its profile data (counter
'arcs', expected 43 and have 46) [-Werror=coverage-mismatch]
4831 | static decNumber * decMultiplyOp(decNumber *res, const decNumber *lhs,
| ^~~~~~~~~~~~~
../../libdecnumber/decNumber.c:4831:20: error: the control flow of function
'decMultiplyOp' does not match its profile data (counter 'time_profiler')
[-Werror=coverage-mismatch]
../../libdecnumber/decNumber.c: In function 'decDivideOp':
../../libdecnumber/decNumber.c:4211:20: error: number of counters in profile
data for function 'decDivideOp' does not match its profile data (counter
'arcs', expected 111 and have 113) [-Werror=coverage-mismatch]
4211 | static decNumber * decDivideOp(decNumber *res,
| ^~~~~~~~~~~
../../libdecnumber/decNumber.c:4211:20: error: the control flow of function
'decDivideOp' does not match its profile data (counter 'single')
[-Werror=coverage-mismatch]
../../libdecnumber/decNumber.c:4211:20: error: the control flow of function
'decDivideOp' does not match its profile data (counter 'time_profiler')
[-Werror=coverage-mismatch]
../../libdecnumber/decNumber.c: In function 'decNumberSquareRoot':
../../libdecnumber/decNumber.c:2797:13: error: number of counters in profile
data for function 'decNumberSquareRoot' does not match its profile data
(counter 'arcs', expected 64 and have 65) [-Werror=coverage-mismatch]
2797 | decNumber * decNumberSquareRoot(decNumber *res, const decNumber *rhs,
| ^~~~~~~~~~~~~~~~~~~
../../libdecnumber/decNumber.c:2797:13: error: the control flow of function
'decNumberSquareRoot' does not match its profile data (counter 'time_profiler')
[-Werror=coverage-mismatch]
which might be related, if one stage generates starting with PRE slightly
different code from the other stage, then the profile mismatches would make a
lot of sense.
>From gcc-bugs-return-628928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 11:01:57 2019
Return-Path: <gcc-bugs-return-628928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51216 invoked by alias); 12 Jan 2019 11:01: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 51146 invoked by uid 48); 12 Jan 2019 11:01:53 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88808] bitwise operators on AVX512 masks fail to use the new mask instructions
Date: Sat, 12 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88808-4-tGE19mqogR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01737.txt.bz2
Content-length: 1288
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88808
--- Comment #2 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Jakub Jelinek from comment #1)
> See PR88473 and PR88798. I'd personally probably revert the changes to make
> the mask operations separate from GPR operations and just use special RTL
> patterns if GPR operation can't do it (e.g. andn when not BMI, or 64-bit
> logicals on 32-bit targets), but it is too late for that for GCC9.
I'm not against the revert, [1] describes the rationale for the current
approach from 2016. In the meantime, a couple of new constraint modifiers were
introduced to better guide register allocation choices, and I believe that with
appropriate RTX costs, it is possible to implement mask operations without
UNSPECs.
I certainly agree with Jakub to postpone new implementation to gcc-10. Without
approporate cost model, we risk that under register pressure, RA will allocate
mask registers for values, expected to live in general registers. At the time,
it was warned that moves between mask and integer registers are quite costly,
so we took the safe way and by introducin UNSPECs, avoided runtime regressions
when mask registers were present.
[1] https://gcc.gnu.org/ml/gcc-patches/2016-11/msg02612.html
>From gcc-bugs-return-628929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 11:15:42 2019
Return-Path: <gcc-bugs-return-628929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79645 invoked by alias); 12 Jan 2019 11:15: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 79580 invoked by uid 48); 12 Jan 2019 11:15:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88808] bitwise operators on AVX512 masks fail to use the new mask instructions
Date: Sat, 12 Jan 2019 11:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88808-4-GNrq7BWadm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01738.txt.bz2
Content-length: 938
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88808
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-12
CC| |hjl.tools at gmail dot com
Ever confirmed|0 |1
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, we probably need to better express in the constraint modifiers the cost
of moving a mask reg into integer reg or vice versa (and measure it). Could
maybe somebody from Intel look into this during stage1 (or even before try to
implement it now and benchmark and if it turns to be a win, propose for
stage1)? Thanks. I'm afraid I'll be busy again the whole stage1 with OpenMP
5.0.
>From gcc-bugs-return-628930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 11:21:20 2019
Return-Path: <gcc-bugs-return-628930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84739 invoked by alias); 12 Jan 2019 11:21:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84704 invoked by uid 48); 12 Jan 2019 11:21:16 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88794] [9 Regression] fixupimm intrinsics are unusable
Date: Sat, 12 Jan 2019 11:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88794-4-3zWWnznQdm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01739.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88794
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
>From gcc-bugs-return-628931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 11:35:53 2019
Return-Path: <gcc-bugs-return-628931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101393 invoked by alias); 12 Jan 2019 11:35:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99045 invoked by uid 48); 12 Jan 2019 11:35:49 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgomp/87835] nvptx offloading: libgomp.oacc-c-c++-common/asyncwait-1.c execution test intermittently fails at -O2
Date: Sat, 12 Jan 2019 11:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libgomp
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87835-4-TKxdjzGg6u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01740.txt.bz2
Content-length: 747
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87835
--- Comment #2 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Tom de Vries from comment #1)
> (In reply to Thomas Schwinge from comment #0)
> > After r264397 "[nvptx] Remove use of CUDA unified memory in libgomp", I'm
> > seeing (intermittently only, and only on some systems):
> >
>
> I see the failure reproduced consistently with a Quadro M1200.
>
> > I have not yet analyzed what's causing this, but I have some ideas about
> > pending patches that might cure it.
>
> OK, let's see if those make it. If not, we may want to investigate and
> decide if we want to revert the patch.
Hi Thomas,
do you intend to address this before stage4 closes?
Thanks,
- Tom
>From gcc-bugs-return-628932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 11:43:39 2019
Return-Path: <gcc-bugs-return-628932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10297 invoked by alias); 12 Jan 2019 11:43:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10222 invoked by uid 48); 12 Jan 2019 11:43:35 -0000
From: "levon at movementarian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/35587] -Warray-bounds does not work at all or does not find all trivial cases, and :works only with -O2 or -O3
Date: Sat, 12 Jan 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: levon at movementarian dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-35587-4-vW4zB2t1WS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01741.txt.bz2
Content-length: 1171
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35587
John Levon <levon at movementarian dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |levon at movementarian dot org
--- Comment #10 from John Levon <levon at movementarian dot org> ---
This is such a pain because of -faggressive-loop-optimizations. Here's a
salient example courtesy of bcantrill:
#define NULL ((void *)0)
static char *arr[2] = { "nasal", "demons" };
long
func()
{
int i;
for (i = 0; i <= 2; i++) {
if (arr[i] == NULL && i == 0)
return (0xbad);
}
return (0xfad);
}
Obviously, the index past the array bounds is undefined behaviour, but GCC
compiling this down to just "return (0xbad)" as it does is not very helpful.
But what's *really* not helpful is that -Warray-bounds=2 can't report on this.
(As per #78678, --fsanitize=object-size does enable detection of this. I'm not
clear if implementation-wise that's the only way to get this reported.)
>From gcc-bugs-return-628933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 11:49:27 2019
Return-Path: <gcc-bugs-return-628933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31248 invoked by alias); 12 Jan 2019 11:49: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 26223 invoked by uid 48); 12 Jan 2019 11:49:23 -0000
From: "levon at movementarian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/35587] -Warray-bounds does not work at all or does not find all trivial cases, and :works only with -O2 or -O3
Date: Sat, 12 Jan 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: levon at movementarian 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-35587-4-0WZrfR6Nq7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01742.txt.bz2
Content-length: 227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35587
--- Comment #11 from John Levon <levon at movementarian dot org> ---
Ugh, and in fact, the sanitize option isn't even enough for the real-life code
that we hit this with.
>From gcc-bugs-return-628935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 12:13:07 2019
Return-Path: <gcc-bugs-return-628935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46153 invoked by alias); 12 Jan 2019 12:13: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 45985 invoked by uid 48); 12 Jan 2019 12:13:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85577] list-initialization chooses initializer-list constructor
Date: Sat, 12 Jan 2019 12:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85577-4-HIFdddcaRe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85577-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85577-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01744.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85577
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |isj-bugzilla at i1 dot dk
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 88816 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-628934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 12:13:06 2019
Return-Path: <gcc-bugs-return-628934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46033 invoked by alias); 12 Jan 2019 12:13: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 45955 invoked by uid 48); 12 Jan 2019 12:13:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88816] Constructor calls itself recursively
Date: Sat, 12 Jan 2019 12:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88816-4-qNJ21CCdQK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01743.txt.bz2
Content-length: 600
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88816
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
See PR 85577 (and PR 86135).
Use parens instead of braces and it works:
new(&u.array_elements) array_type(a);
*** This bug has been marked as a duplicate of bug 85577 ***
>From gcc-bugs-return-628936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 12:27:09 2019
Return-Path: <gcc-bugs-return-628936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128553 invoked by alias); 12 Jan 2019 12:27: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 128500 invoked by uid 48); 12 Jan 2019 12:27:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88816] Constructor calls itself recursively
Date: Sat, 12 Jan 2019 12:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88816-4-er9JrM8Tdo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01745.txt.bz2
Content-length: 724
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88816
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> See PR 85577 (and PR 86135).
>
> Use parens instead of braces and it works:
>
> new(&u.array_elements) array_type(a);
Basically, if you're trying to call the array_type copy constructor then don't
use array_type{a} when array_type has an initializer-list constructor and a is
convertible to the value_type. If you use braces the compiler thinks you're
trying to do array_type{initializer_list<Value>{a}}, i.e. create a vector with
one element copied from a. It converts a to Value, which calls back into the
same constructor and recurses.
>From gcc-bugs-return-628937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 13:32:04 2019
Return-Path: <gcc-bugs-return-628937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68952 invoked by alias); 12 Jan 2019 13:32: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 68874 invoked by uid 48); 12 Jan 2019 13:32:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Sat, 12 Jan 2019 13:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88738-4-Bsz1qIQKDo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01746.txt.bz2
Content-length: 1709
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Ulrich Drepper from comment #3)
> Created attachment 45416 [details]
> Add nodiscard support
>
> As Martin suggested, we could indeed use existing attributes in library code
> to warn about some of the problems. The code from comment #0 is real, this
> happened in a project of mine where I mistyped an assignment. The warning
> would have pointed to the problem.
>
> How about the following patch for a start? This compiles cleanly on x86-64.
> I haven't run the test suite to see whether it breaks some regression tests.
Please do, but it looks good in principle.
I'd feel comfortable adding this in stage 4 if it was only enabled for C++17
and up:
// Macro to warn about unused results.
#if __cplusplus >= 201703L
# define _GLIBCXX_NODISCARD [[__nodiscard__]]
#else
# define _GLIBCXX_NODISCARD
#endif
We could then enable it for C++98/C++11/C++14 during stage 1 if no problems
show up.
> Also, this approach should be extended beyond shared_ptr and unique_ptr,
> probably to at least every single bool operatorXX(...) const. Or even every
> single const member function which then of course raises the question
> whether the compiler should learn about this…
Microsoft went quite aggressive adding [[nodiscard]] *everywhere* in their
library, and ended up backing some out again. There are some subtle cases (or,
depending on your point of view, users do silly things and complain about
getting warnings for their unreasonable code).
I do think Clang's warning in the compiler is better than having to decorate
everything explicitly.
>From gcc-bugs-return-628938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 14:42:11 2019
Return-Path: <gcc-bugs-return-628938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81153 invoked by alias); 12 Jan 2019 14:42: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 81077 invoked by uid 48); 12 Jan 2019 14:42:08 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68933] ICE when mixing "-fprofile-arcs -ftest-coverage" and "-fcoarray=lib" on gcc-6 only
Date: Sat, 12 Jan 2019 14:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68933-4-wlj0jj9seJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68933-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68933-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01747.txt.bz2
Content-length: 197
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68933
--- Comment #7 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
GCC6 is no longer supported, this PR should probably closed as FIXED.
>From gcc-bugs-return-628939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 15:14:53 2019
Return-Path: <gcc-bugs-return-628939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67168 invoked by alias); 12 Jan 2019 15:14: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 67093 invoked by uid 48); 12 Jan 2019 15:14:49 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex float load
Date: Sat, 12 Jan 2019 15:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-rltv4kUiRW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01748.txt.bz2
Content-length: 221
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
Please take a look at
https://github.com/hjl-tools/gcc/commit/a56b4a49b2617a31365bdb9c44340695c31d56e8
>From gcc-bugs-return-628940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 15:16:19 2019
Return-Path: <gcc-bugs-return-628940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70020 invoked by alias); 12 Jan 2019 15:16: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 69971 invoked by uid 48); 12 Jan 2019 15:16:16 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/47149] failing build: execvp: /bin/sh: Argument list too long
Date: Sat, 12 Jan 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 4.5.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-47149-4-AQ0YifdakD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-47149-4@http.gcc.gnu.org/bugzilla/>
References: <bug-47149-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01749.txt.bz2
Content-length: 397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=47149
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this still valid?
>From gcc-bugs-return-628941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 15:26:20 2019
Return-Path: <gcc-bugs-return-628941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76506 invoked by alias); 12 Jan 2019 15:26:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76434 invoked by uid 48); 12 Jan 2019 15:26:16 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48776] ICE(segfault) after -stdù5 diagnostic error involving PROCEDURE
Date: Sat, 12 Jan 2019 15:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-48776-4-QDOKZOA6W0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-48776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-48776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01750.txt.bz2
Content-length: 551
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48776
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> So this PR seems to be another instance of non-deterministic error recovery.
Yet another instance of
==2863==ERROR: AddressSanitizer: heap-use-after-free on address 0x613000002588
at pc 0x0001004e9eab bp 0x7ffeefbfe690 sp 0x7ffeefbfe688
READ of size 8 at 0x613000002588 thread T0
#0 0x1004e9eaa in gfc_sym_get_dummy_args(gfc_symbol*) symbol.c:5215
...
related to pr52622, pr84245, pr86657, and pr87908.
>From gcc-bugs-return-628942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 15:39:14 2019
Return-Path: <gcc-bugs-return-628942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97245 invoked by alias); 12 Jan 2019 15:39: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 93877 invoked by uid 48); 12 Jan 2019 15:39:08 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex float load
Date: Sat, 12 Jan 2019 15:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-g2snO0Dv9y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01751.txt.bz2
Content-length: 246
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
We need to update read_complex_part and write_complex_part to manipulate
SCmode with vector operations instead of 64-bit integers.
>From gcc-bugs-return-628943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 15:52:57 2019
Return-Path: <gcc-bugs-return-628943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116485 invoked by alias); 12 Jan 2019 15:52: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 116447 invoked by uid 48); 12 Jan 2019 15:52:53 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88817] New: Diagnostics improvement: Does not detect attempt to use void expression in some cases.
Date: Sat, 12 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01752.txt.bz2
Content-length: 1006
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88817
Bug ID: 88817
Summary: Diagnostics improvement: Does not detect attempt to
use void expression in some cases.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
extern void v;
int main(void)
{
_Generic(v, default: 0);
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
No error messages outputed.
Possible improvement:
The program has undefined behaviour because it attempts to use the void
expression v (as the controlling expression of _Generic).
Since GCC detects attempts to use void expressions in other case it would be
good if it detected it in this case also.
>From gcc-bugs-return-628944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 16:35:18 2019
Return-Path: <gcc-bugs-return-628944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41490 invoked by alias); 12 Jan 2019 16:35: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 38866 invoked by uid 48); 12 Jan 2019 16:35:14 -0000
From: "isj-bugzilla at i1 dot dk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88816] Constructor calls itself recursively
Date: Sat, 12 Jan 2019 16:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: isj-bugzilla at i1 dot dk
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88816-4-KTnYlyQiwX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01753.txt.bz2
Content-length: 404
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88816
--- Comment #3 from Ivan Skytte Jørgensen <isj-bugzilla at i1 dot dk> ---
Ohhh...! Thank you for the explanation.
That was not at all obvious to me. It would be great if GCC detected it and
warned "brace-initializing a std:vector with a single std::vector may not do
what you think it does, depending on user-defined conversion constructors"
>From gcc-bugs-return-628945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 16:46:44 2019
Return-Path: <gcc-bugs-return-628945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91709 invoked by alias); 12 Jan 2019 16:46: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 91342 invoked by uid 48); 12 Jan 2019 16:46:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] [9 Regression] False positive -Waddress-of-packed-member
Date: Sat, 12 Jan 2019 16:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-88664-4-iXfGXlE488@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01754.txt.bz2
Content-length: 1691
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |hjl.tools at gmail dot com,
| |jakub at gcc dot gnu.org
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I'd use just
struct S { short s; void *p; } __attribute__ ((__packed__));
int *
foo (struct S *x)
{
return (int *) (x->p);
}
for both languages.
Despite quite many tests added in the -Waddress-of-packed-member commit, I
really don't see any testsuite coverage of the
warning_at (location, OPT_Waddress_of_packed_member,
"converting a packed %qT pointer (alignment %d) "
"to %qT (alignment %d) may may result in an "
"unaligned pointer value",
rhstype, rhs_align, type, type_align);
warning (and note the "may may" bug in the wording there), is that covered by
anything?
As for the other path, it doesn't care whether address is taken or not:
if (INDIRECT_REF_P (rhs))
rhs = TREE_OPERAND (rhs, 0);
if (TREE_CODE (rhs) == ADDR_EXPR)
rhs = TREE_OPERAND (rhs, 0);
while it is significant. We shouldn't warn if we are reading content from the
packed structure, but should warn if we are taking address (and for that needs
to take into account the array to pointer conversions, whether they happen
before or after this warning is reported).
>From gcc-bugs-return-628946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 16:49:32 2019
Return-Path: <gcc-bugs-return-628946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100428 invoked by alias); 12 Jan 2019 16: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 100358 invoked by uid 48); 12 Jan 2019 16:49:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] [9 Regression] False positive -Waddress-of-packed-member
Date: Sat, 12 Jan 2019 16:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88664-4-1wSfAzu7OY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01755.txt.bz2
Content-length: 307
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
H.J., can you please look into this?
Plus, I guess we need to reevaluate all the spots where
-Wno-address-of-packed-member has been added, whether we were warning there
correctly or not.
>From gcc-bugs-return-628947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 18:10:03 2019
Return-Path: <gcc-bugs-return-628947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42975 invoked by alias); 12 Jan 2019 18:10:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42856 invoked by uid 48); 12 Jan 2019 18:09:59 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88813] snprintf less optimal than sprintf for %s with big enough destination
Date: Sat, 12 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88813-4-3i5lJDGlfw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01756.txt.bz2
Content-length: 1030
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88813
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
To be safe, even though %s requires that the argument be a nul-terminated
string, the snprintf optimization would need to be predicated on knowing that
it, in fact, is one (to avoid buffer overflow if snprintf was called with a
non-string argument). The optimization opportunity is in the length of the
source string not needing to be known. When the source array is not guaranteed
to be a nul-terminated string then the memccpy optimization described in
pr88814 could take place instead.
So to clarify the example in comment #0, the array size optimization would only
be applicable if s was previously used as a string, such as in an argument to
some string function like in:
char d[8];
char s[8];
char *p;
void g (void)
{
p = __builtin_strchr (s, '/'); // s must be a nul-terminated string
...
__builtin_snprintf (d, sizeof d, "%s", s); // can be folded to strcpy
}
>From gcc-bugs-return-628948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 18:22:38 2019
Return-Path: <gcc-bugs-return-628948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51304 invoked by alias); 12 Jan 2019 18:22:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51249 invoked by uid 48); 12 Jan 2019 18:22:34 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Sat, 12 Jan 2019 18:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88738-4-7uiIqB2Z09@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01757.txt.bz2
Content-length: 855
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
I can see how applying the attribute to every standard library function, even
const, might be excessive, but I wonder if it would make sense for the majority
of them, or at least for most equality and relational operators defined by the
library. If it did we could have GCC apply it implicitly to all such functions
or operators defined in namespace std, and provide a new attribute to disable
it in the cases where it might not be appropriate (say no_warn_unused_result).
We could also add a #pragma to control the scope where the attribute should or
should not be implicitly applied to such functions. If you think this might be
a worthwhile approach to consider let's schedule it as an enhancement for GCC
10.
>From gcc-bugs-return-628949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 18:59:51 2019
Return-Path: <gcc-bugs-return-628949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118190 invoked by alias); 12 Jan 2019 18:59:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118071 invoked by uid 48); 12 Jan 2019 18:59:45 -0000
From: "drepper.fsp+rhbz at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Sat, 12 Jan 2019 18:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: drepper.fsp+rhbz at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88738-4-YcoXVFz4To@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01758.txt.bz2
Content-length: 2227
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #6 from Ulrich Drepper <drepper.fsp+rhbz at gmail dot com> ---
(In reply to Martin Sebor from comment #5)
> If it did we could have GCC apply it implicitly to
> all such functions or operators defined in namespace std, and provide a new
> attribute to disable it in the cases where it might not be appropriate (say
> no_warn_unused_result).
I looked at what clang does and it's very simplistic. The code below produces
the output shows below. I.e., they use the warning for all comparison
operators regardless of
- namespace
- return value
- member function or not
- const-ness of operators
- visible side effects
Nevertheless people use the compiler without complaining, at least visibly.
$ clang++ -c -O -Wall u.cc
u.cc:26:5: warning: equality comparison result unused [-Wunused-comparison]
l == r;
~~^~~~
u.cc:26:5: note: use '=' to turn this equality comparison into an assignment
l == r;
^~
=
u.cc:31:5: warning: inequality comparison result unused [-Wunused-comparison]
l != r;
~~^~~~
u.cc:31:5: note: use '|=' to turn this inequality comparison into an
or-assignment
l != r;
^~
|=
u.cc:36:5: warning: relational comparison result unused [-Wunused-comparison]
l <= r;
~~^~~~
u.cc:41:5: warning: relational comparison result unused [-Wunused-comparison]
l >= r;
~~^~~~
u.cc:46:5: warning: relational comparison result unused [-Wunused-comparison]
l < r;
~~^~~
5 warnings generated.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
struct foo {
int a;
foo(int) : a(42) {}
auto operator==(const foo& o) const { return a == o.a; }
auto operator!=(foo& o) { return a == o.a; }
};
auto operator<=(const foo& l, const foo& r)
{
return l.a == r.a;
}
auto operator>=(foo& l, foo& r)
{
l.a |= 1;
return l.a == r.a;
}
int operator<(foo& l, foo& r)
{
return l.a == r.a ? 0 : l.a < r.a ? -1 : 1;
}
auto f1(foo& l, foo& r)
{
l == r;
}
auto f2(foo& l, foo& r)
{
l != r;
}
auto f3(foo& l, foo& r)
{
l <= r;
}
auto f4(foo& l, foo& r)
{
l >= r;
}
auto f5(foo& l, foo& r)
{
l < r;
}
>From gcc-bugs-return-628950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 20:40:24 2019
Return-Path: <gcc-bugs-return-628950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21620 invoked by alias); 12 Jan 2019 20:40:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21543 invoked by uid 48); 12 Jan 2019 20:40:19 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Sat, 12 Jan 2019 20:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88776-4-MBOGTem8H9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01759.txt.bz2
Content-length: 2452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jvdelisle at gcc dot gnu.org
--- Comment #4 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Harald Anlauf from comment #3)
> Created attachment 45407 [details]
> Self-contained testcase
>
> I've been able to produce a self-contained testcase, which may aid
> debugging.
>
> While reducing further, I got the impression that it is just a subtle
> whitespace issue.
I have looked a little closer at this.
There are a few places where reading is handled differently if the unit is
stdin_unit. For example in list_read.c near line 3614 we have:
while (!dtp->u.p.input_complete)
{
if (!nml_get_obj_data (dtp, &prev_nl, nml_err_msg, sizeof nml_err_msg))
{
printf ("ping: %d, %d\n", dtp->u.p.current_unit->unit_number,
options.stdin_unit);
if (dtp->u.p.current_unit->unit_number != options.stdin_unit)
goto nml_err_ret;
printf("pong\n");
generate_error (&dtp->common, LIBERROR_READ_VALUE, nml_err_msg);
}
Where I have instrumented this a little and running a slightly modified test
case, we take two different error paths. This results in:
$ ./a.out
Calling on unit 10:
ping: 10, 5
Calling on unit 5:
ping: 5, 5
pong
ichan not 2,unit= 5
STOP 3
goto nml_err_ret above is a more graceful return:
nml_err_ret:
/* All namelist error calls return from here */
free_saved (dtp);
free_line (dtp);
generate_error (&dtp->common, LIBERROR_READ_VALUE, nml_err_msg);
return;
Putting a return after the error in the block at 3614 seems to fix it.
if (!nml_get_obj_data (dtp, &prev_nl, nml_err_msg, sizeof nml_err_msg))
{
//printf ("ping: %d, %d\n", dtp->u.p.current_unit->unit_number,
options.stdin_unit);
if (dtp->u.p.current_unit->unit_number != options.stdin_unit)
goto nml_err_ret;
//printf("pong\n");
generate_error (&dtp->common, LIBERROR_READ_VALUE, nml_err_msg);
return;
}
With the printf's commented out:
$ ./a.out
Calling on unit 10:
Calling on unit 5:
I have not regression tested this and will report back.
>From gcc-bugs-return-628951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 20:52:27 2019
Return-Path: <gcc-bugs-return-628951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127899 invoked by alias); 12 Jan 2019 20:52: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 119058 invoked by uid 48); 12 Jan 2019 20:52:23 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/69788] FAIL: gfortran.dg/derived_constructor_comps_6.f90 -O0 execution test
Date: Sat, 12 Jan 2019 20:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 5.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-69788-4-QujfyNmra1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01760.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69788
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from John David Anglin <danglin at gcc dot gnu.org> ---
Don't see failure on hppa2.0w-hp-hpux11.11 in gcc-7 and later.
>From gcc-bugs-return-628952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 21:00:27 2019
Return-Path: <gcc-bugs-return-628952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103103 invoked by alias); 12 Jan 2019 21:00:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102671 invoked by uid 48); 12 Jan 2019 21:00:04 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Sat, 12 Jan 2019 21:00: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88776-4-tHiAgDSKsI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01761.txt.bz2
Content-length: 1085
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
So far this patch seems to test OK.
diff --git a/libgfortran/io/list_read.c b/libgfortran/io/list_read.c
index 4a7ccb3ddd5..d9af255a034 100644
--- a/libgfortran/io/list_read.c
+++ b/libgfortran/io/list_read.c
@@ -3614,11 +3614,7 @@ find_nml_name:
while (!dtp->u.p.input_complete)
{
if (!nml_get_obj_data (dtp, &prev_nl, nml_err_msg, sizeof nml_err_msg))
- {
- if (dtp->u.p.current_unit->unit_number != options.stdin_unit)
- goto nml_err_ret;
- generate_error (&dtp->common, LIBERROR_READ_VALUE, nml_err_msg);
- }
+ goto nml_err_ret;
/* Reset the previous namelist pointer if we know we are not going
to be doing multiple reads within a single namelist object. */
All our current namelist tests pass. We shoud check this against an actual
redirection to stdin which we do not do in our testsuite, but I cannot think of
a reason why it would not be OK. (ie cat file | ./a.out )
>From gcc-bugs-return-628954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 22:19:26 2019
Return-Path: <gcc-bugs-return-628954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101581 invoked by alias); 12 Jan 2019 22:19: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 101489 invoked by uid 55); 12 Jan 2019 22:19:22 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85486] [og7, nvptx] ref-1.C fails with vector length 128
Date: Sat, 12 Jan 2019 22:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: openacc, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85486-4-WaiUZOkjlc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85486-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85486-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01763.txt.bz2
Content-length: 798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85486
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Sat Jan 12 22:18:50 2019
New Revision: 267894
URL: https://gcc.gnu.org/viewcvs?rev=267894&root=gcc&view=rev
Log:
[nvptx] Force vl32 if calling vector-partitionable routines -- test-cases
Add test-cases for "[nvptx] Force vl32 if calling vector-partitionable
routines".
2019-01-12 Tom de Vries <tdevries@suse.de>
PR target/85486
* testsuite/libgomp.oacc-c-c++-common/pr85486-3.c: New test.
* testsuite/libgomp.oacc-c-c++-common/pr85486.c: New test.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr85486-3.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr85486.c
Modified:
trunk/libgomp/ChangeLog
>From gcc-bugs-return-628953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 22:19:14 2019
Return-Path: <gcc-bugs-return-628953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100567 invoked by alias); 12 Jan 2019 22:19:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100501 invoked by uid 55); 12 Jan 2019 22:19:10 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85381] [og7, nvptx, openacc] parallel-loop-1.c fails with default vector length 128
Date: Sat, 12 Jan 2019 22:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85381-4-WXzDXP14mR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85381-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85381-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01762.txt.bz2
Content-length: 729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85381
--- Comment #12 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Sat Jan 12 22:18:39 2019
New Revision: 267893
URL: https://gcc.gnu.org/viewcvs?rev=267893&root=gcc&view=rev
Log:
[nvptx] Don't emit barriers for empty loops -- test-cases
Add test-cases for PR85381.
2019-01-12 Tom de Vries <tdevries@suse.de>
PR target/85381
* testsuite/libgomp.oacc-c-c++-common/pr85381-5.c: New test.
* testsuite/libgomp.oacc-c-c++-common/pr85381.c: New test.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr85381-5.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr85381.c
Modified:
trunk/libgomp/ChangeLog
>From gcc-bugs-return-628955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 23:07:23 2019
Return-Path: <gcc-bugs-return-628955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44350 invoked by alias); 12 Jan 2019 23:07: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 44299 invoked by uid 55); 12 Jan 2019 23:07:18 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Sat, 12 Jan 2019 23:07: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88776-4-yTPih7V18K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01764.txt.bz2
Content-length: 537
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Sat Jan 12 23:06:47 2019
New Revision: 267898
URL: https://gcc.gnu.org/viewcvs?rev=267898&root=gcc&view=rev
Log:
2019-01-12 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libfortran/88776
* io/list_read.c (namelist_read): Use nml_err_ret path on read error
not based on stdin_unit.
Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/list_read.c
>From gcc-bugs-return-628956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 23:20:14 2019
Return-Path: <gcc-bugs-return-628956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60185 invoked by alias); 12 Jan 2019 23: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 60124 invoked by uid 48); 12 Jan 2019 23:20:09 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88817] Diagnostics improvement: Does not detect attempt to use void expression in some cases.
Date: Sat, 12 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88817-4-HqLsE66tZf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01765.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88817
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The controlling expression of a _Generic selection is not evaluated so I don't
see any undefined behavior in the test case, or any more justification for a
diagnostic.
>From gcc-bugs-return-628957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 23:35:23 2019
Return-Path: <gcc-bugs-return-628957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83354 invoked by alias); 12 Jan 2019 23:35: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 83253 invoked by uid 48); 12 Jan 2019 23:35:16 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88737] RFE: Track ownership moves
Date: Sat, 12 Jan 2019 23:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88737-4-1akwrfF7vp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01766.txt.bz2
Content-length: 1008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88737
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #2)
> Wouldn't that break e.g. programs that
> free (a);
> return (uintptr_t) a % 16;
> or similar (i.e. inspect the bits of the pointer rather than what it points
> to)?
> That should be valid even after free, free doesn't modify the pointer, only
> says that what it points to is no longer available.
Strictly speaking (as described in bug 80532), the value of a pointer becomes
indeterminate after the lifetime of the object it points to ends. This goes
for all memory: stack as well as the heap. So the idea of clobbering the
pointer is sound, though it would certainly break code that uses the
indeterminate pointer anyway, such as after realloc. But I agree that a
warning would be quite helpful here to help find such bad code.
I'm not sure I understand the purpose of the requested attribute or how it
might be used or where.
>From gcc-bugs-return-628958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat Jan 12 23:48:51 2019
Return-Path: <gcc-bugs-return-628958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95596 invoked by alias); 12 Jan 2019 23:48: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 95159 invoked by uid 48); 12 Jan 2019 23:48:36 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88736] nullptr_t available without namespace qualification
Date: Sat, 12 Jan 2019 23:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88736-4-vtLi8RTsBA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01767.txt.bz2
Content-length: 781
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88736
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-12
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
I agree. <cstddef> defines C library names in both namespace std and the
global namespace but C++ library names only in std. For some reason, GCC's
<stddef.h> defines nullptr_t in the global namespace (and libstdc++ <cstddef>
in std).
>From gcc-bugs-return-628959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 00:19:08 2019
Return-Path: <gcc-bugs-return-628959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28347 invoked by alias); 13 Jan 2019 00:19:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26294 invoked by uid 48); 13 Jan 2019 00:19:03 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88704] Accepts invalid program with [*] outside function prototype scope.
Date: Sun, 13 Jan 2019 00:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88704-4-VtU0ccvvNA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01768.txt.bz2
Content-length: 710
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88704
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-13
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed, although I'd be more inclined to invest energy into including
-Wstrict-prototypes in -Wall or -Wextra than into diagnosing the VLA in
K&R-style definitions.
>From gcc-bugs-return-628960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 00:24:58 2019
Return-Path: <gcc-bugs-return-628960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36152 invoked by alias); 13 Jan 2019 00:24: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 36012 invoked by uid 48); 13 Jan 2019 00:24:51 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88700] C11 Annex K builtins
Date: Sun, 13 Jan 2019 00:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88700-4-qF0gCTGYbI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88700-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01769.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88700
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Without Glibc support, adding the built-ins to GCC isn't realistic so I'm going
to resolve this request as Won't Fix.
>From gcc-bugs-return-628961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 00:29:03 2019
Return-Path: <gcc-bugs-return-628961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40485 invoked by alias); 13 Jan 2019 00:29: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 40318 invoked by uid 48); 13 Jan 2019 00:28:59 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Sun, 13 Jan 2019 00:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88682-4-ffRvGPmnIa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01770.txt.bz2
Content-length: 725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-13
CC| |msebor at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed based on the latest test results for both targets:
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg01230.html
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg01245.html
>From gcc-bugs-return-628962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 01:12:25 2019
Return-Path: <gcc-bugs-return-628962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75053 invoked by alias); 13 Jan 2019 01:12: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 74953 invoked by uid 48); 13 Jan 2019 01:12:19 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Sun, 13 Jan 2019 01:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88662-4-HXfjN1D1VN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01771.txt.bz2
Content-length: 1479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msebor at gcc dot gnu.org
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to gnzlbg from comment #2)
> > Because (unsigned int)b is undefined otherwise.
>
> AFAICT this is only undefined behavior iff `b` has a trap representation.
Not necessarily. It's undefined if b's value is indeterminate, whether or not
it's a trap representation, or whether or not b's type even has a trap
representation. See C Defect Report 451 for some background:
http://www.open-std.org/jtc1/sc22/wg14/www/docs/dr_451.htm
I don't think copying arbitrary bits into an object changes that, unless those
bits come from an initialized object of the same type in the same program
execution.
That said, there has been a lot of confusion about padding bits and trap
representations so I'm not completely unsympathetic to the request, even
though, as Jonathan says, thos aspects of types are unspecified. But rather
than documenting which bits are padding bits I think it should be sufficient to
either mention which types have padding bits, or expose some additional Common
Predefined Macros to make it possible to determine which ones do (and perhaps
even compute how many).
>From gcc-bugs-return-628963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 01:17:37 2019
Return-Path: <gcc-bugs-return-628963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90908 invoked by alias); 13 Jan 2019 01:17: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 88946 invoked by uid 48); 13 Jan 2019 01:17:32 -0000
From: "jagapeyev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88818] New: Segfault with vtable-verify LTO optimization
Date: Sun, 13 Jan 2019 01:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jagapeyev 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-88818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01772.txt.bz2
Content-length: 989
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88818
Bug ID: 88818
Summary: Segfault with vtable-verify LTO optimization
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jagapeyev at gmail dot com
Target Milestone: ---
struct a {
virtual int b();
};
void c() {}
Compiling the above program with:
g++ -c test.cpp -O1 -flto -fvtable-verify=preinit
Results in the following error:
during GIMPLE pass: ealias
test.cpp: In function ‘_GLOBAL__sub_I.00099__Z1cv’:
test.cpp:4:11: internal compiler error: Segmentation fault
void c() {}
^
Attached is the full gcc -v -save-temps output.
>From preliminary tests, -fvtable-verify=std vs -fvtable-verify=preinit makes no
difference.
Error does not exist with -O0 or -Og, but does exist at -O1 and higher.
>From gcc-bugs-return-628964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 01:22:30 2019
Return-Path: <gcc-bugs-return-628964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117129 invoked by alias); 13 Jan 2019 01:22:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117051 invoked by uid 48); 13 Jan 2019 01:22:24 -0000
From: "jagapeyev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88818] Segfault with vtable-verify LTO optimization
Date: Sun, 13 Jan 2019 01:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jagapeyev at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88818-4-n1kfGRsss3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01773.txt.bz2
Content-length: 4062
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88818
John Agapeyev <jagapeyev at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jagapeyev at gmail dot com
--- Comment #1 from John Agapeyev <jagapeyev at gmail dot com> ---
GCC -v -save-temps output
Using built-in specs.
COLLECT_GCC=g++
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --enable-multilib --disable-werror
--enable-checking=release --enable-default-pie --enable-default-ssp
--enable-cet=auto
Thread model: posix
gcc version 8.2.1 20181127 (GCC)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-std=c++17' '-O1' '-flto'
'-fvtable-verify=std' '-o' 'test.o' '-c' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/cc1plus -E -quiet -v -D_GNU_SOURCE
test2.cpp -mtune=generic -march=x86-64 -std=c++17 -flto -fvtable-verify=std -O1
-fpch-preprocess -o test2.ii
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/x86_64-pc-linux-gnu
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/backward
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/include
/usr/local/include
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/include-fixed
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-std=c++17' '-O1' '-flto'
'-fvtable-verify=std' '-o' 'test.o' '-c' '-shared-libgcc' '-mtune=generic'
'-march=x86-64'
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/cc1plus -fpreprocessed test2.ii -quiet
-dumpbase test2.cpp -mtune=generic -march=x86-64 -auxbase-strip test.o -O1
-std=c++17 -version -flto -fvtable-verify=std -o test2.s
GNU C++17 (GCC) version 8.2.1 20181127 (x86_64-pc-linux-gnu)
compiled by GNU C version 8.2.1 20181127, GMP version 6.1.2, MPFR
version 4.0.1, MPC version 1.1.0, isl version isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C++17 (GCC) version 8.2.1 20181127 (x86_64-pc-linux-gnu)
compiled by GNU C version 8.2.1 20181127, GMP version 6.1.2, MPFR
version 4.0.1, MPC version 1.1.0, isl version isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: c228073cd86637479fc341ff509ca7e7
test2.cpp: In destructor ‘std::basic_ostream<_CharT,
_Traits>::sentry::~sentry()’:
test2.cpp:51414:69: warning: ‘bool std::uncaught_exception()’ is deprecated
[-Wdeprecated-declarations]
if (bool(_M_os.flags() & ios_base::unitbuf) && !uncaught_exception())
^
test2.cpp:3994:8: note: declared here
bool uncaught_exception() noexcept __attribute__ ((__pure__));
^~~~~~~~~~~~~~~~~~
during GIMPLE pass: ealias
test2.cpp: In function ‘_GLOBAL__sub_I.00099__ZN6crypto10DH_KeypairC2Ev’:
test2.cpp:60623:1: internal compiler error: Segmentation fault
}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
>From gcc-bugs-return-628965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 01:27:49 2019
Return-Path: <gcc-bugs-return-628965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121997 invoked by alias); 13 Jan 2019 01:27: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 121931 invoked by uid 48); 13 Jan 2019 01:27:43 -0000
From: "jagapeyev at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88818] Segfault with vtable-verify LTO optimization
Date: Sun, 13 Jan 2019 01:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jagapeyev 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-88818-4-jDuvFLAdn6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01774.txt.bz2
Content-length: 2936
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88818
--- Comment #2 from John Agapeyev <jagapeyev at gmail dot com> ---
Ignore first comment, output was from older test file.
GCC -v output:
Using built-in specs.
COLLECT_GCC=g++
Target: x86_64-pc-linux-gnu
Configured with: /build/gcc/src/gcc/configure --prefix=/usr --libdir=/usr/lib
--libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info
--with-bugurl=https://bugs.archlinux.org/
--enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared
--enable-threads=posix --enable-libmpx --with-system-zlib --with-isl
--enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu
--disable-libstdcxx-pch --disable-libssp --enable-gnu-unique-object
--enable-linker-build-id --enable-lto --enable-plugin
--enable-install-libiberty --with-linker-hash-style=gnu
--enable-gnu-indirect-function --enable-multilib --disable-werror
--enable-checking=release --enable-default-pie --enable-default-ssp
--enable-cet=auto
Thread model: posix
gcc version 8.2.1 20181127 (GCC)
COLLECT_GCC_OPTIONS='-v' '-c' '-O1' '-flto' '-fvtable-verify=preinit'
'-shared-libgcc' '-mtune=generic' '-march=x86-64'
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/cc1plus -quiet -v -D_GNU_SOURCE
test.cpp -quiet -dumpbase test.cpp -mtune=generic -march=x86-64 -auxbase test
-O1 -version -flto -fvtable-verify=preinit -o /tmp/ccGxPiUI.s
GNU C++14 (GCC) version 8.2.1 20181127 (x86_64-pc-linux-gnu)
compiled by GNU C version 8.2.1 20181127, GMP version 6.1.2, MPFR
version 4.0.1, MPC version 1.1.0, isl version isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../x86_64-pc-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/x86_64-pc-linux-gnu
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/../../../../include/c++/8.2.1/backward
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/include
/usr/local/include
/usr/lib/gcc/x86_64-pc-linux-gnu/8.2.1/include-fixed
/usr/include
End of search list.
GNU C++14 (GCC) version 8.2.1 20181127 (x86_64-pc-linux-gnu)
compiled by GNU C version 8.2.1 20181127, GMP version 6.1.2, MPFR
version 4.0.1, MPC version 1.1.0, isl version isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: c228073cd86637479fc341ff509ca7e7
during GIMPLE pass: ealias
test.cpp: In function ‘_GLOBAL__sub_I.00099__Z1cv’:
test.cpp:4:11: internal compiler error: Segmentation fault
void c() {}
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
>From gcc-bugs-return-628966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 03:35:50 2019
Return-Path: <gcc-bugs-return-628966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77816 invoked by alias); 13 Jan 2019 03:35: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 77595 invoked by uid 48); 13 Jan 2019 03:35:28 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] [9 Regression] False positive -Waddress-of-packed-member
Date: Sun, 13 Jan 2019 03:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88664-4-sd3JTCecny@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01775.txt.bz2
Content-length: 2182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jakub Jelinek from comment #3)
> I'd use just
> struct S { short s; void *p; } __attribute__ ((__packed__));
>
> int *
> foo (struct S *x)
> {
> return (int *) (x->p);
> }
> for both languages.
>
> Despite quite many tests added in the -Waddress-of-packed-member commit, I
> really don't see any testsuite coverage of the
> warning_at (location, OPT_Waddress_of_packed_member,
> "converting a packed %qT pointer (alignment %d) "
> "to %qT (alignment %d) may may result in an "
> "unaligned pointer value",
> rhstype, rhs_align, type, type_align);
> warning (and note the "may may" bug in the wording there), is that covered
> by anything?
This is covered by gcc.dg/pr51628-20.c, gcc.dg/pr51628-21.c and
gcc.dg/pr51628-25.c.
> As for the other path, it doesn't care whether address is taken or not:
> if (INDIRECT_REF_P (rhs))
> rhs = TREE_OPERAND (rhs, 0);
>
> if (TREE_CODE (rhs) == ADDR_EXPR)
> rhs = TREE_OPERAND (rhs, 0);
> while it is significant. We shouldn't warn if we are reading content from
> the packed structure, but should warn if we are taking address (and for that
> needs to take into account the array to pointer conversions, whether they
> happen before or after this warning is reported).
I am testing:
diff --git a/gcc/c-family/c-warn.c b/gcc/c-family/c-warn.c
index 79b2d8ad449..c937c016889 100644
--- a/gcc/c-family/c-warn.c
+++ b/gcc/c-family/c-warn.c
@@ -2752,9 +2752,15 @@ check_and_warn_address_of_packed_member (tree type, tree
rhs)
{
if (TREE_CODE (rhs) != COND_EXPR)
{
+ if (TREE_CODE (rhs) == NOP_EXPR)
+ rhs = TREE_OPERAND (rhs, 0);
+
while (TREE_CODE (rhs) == COMPOUND_EXPR)
rhs = TREE_OPERAND (rhs, 1);
+ if (TREE_CODE (rhs) != ADDR_EXPR)
+ return;
+
tree context = check_address_of_packed_member (type, rhs);
if (context)
{
(
>From gcc-bugs-return-628967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 04:03:32 2019
Return-Path: <gcc-bugs-return-628967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 781 invoked by alias); 13 Jan 2019 04:03:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 675 invoked by uid 55); 13 Jan 2019 04:03:23 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61765] [7/8/9 Regression] [F03] Rejects valid BIND(C) ENTRY
Date: Sun, 13 Jan 2019 04:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-61765-4-pkUZhOvvVO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01776.txt.bz2
Content-length: 799
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61765
--- Comment #7 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Sun Jan 13 04:02:46 2019
New Revision: 267902
URL: https://gcc.gnu.org/viewcvs?rev=267902&root=gcc&view=rev
Log:
2019-01-12 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/61765
* resolve.c (gfc_verify_binding_labels): Break if-elseif-elseif
structure into independent if's with a return to simplify logic.
Avoid a check for ENTRY name with bind(c).
2019-01-12 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/61765
* gfortran.dg/pr61765.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr61765.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 04:04:44 2019
Return-Path: <gcc-bugs-return-628969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2428 invoked by alias); 13 Jan 2019 04:04: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 2257 invoked by uid 48); 13 Jan 2019 04:04:37 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/32630] [meta-bug] ISO C binding
Date: Sun, 13 Jan 2019 04:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-32630-4-SDk1vB7E7Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-32630-4@http.gcc.gnu.org/bugzilla/>
References: <bug-32630-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01778.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=32630
Bug 32630 depends on bug 61765, which changed state.
Bug 61765 Summary: [7/8/9 Regression] [F03] Rejects valid BIND(C) ENTRY
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61765
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-628968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 04:04:40 2019
Return-Path: <gcc-bugs-return-628968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2276 invoked by alias); 13 Jan 2019 04:04:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2210 invoked by uid 48); 13 Jan 2019 04:04:33 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61765] [7/8/9 Regression] [F03] Rejects valid BIND(C) ENTRY
Date: Sun, 13 Jan 2019 04: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: 5.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-61765-4-CgDUUN4tHV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61765-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01777.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61765
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from kargl at gcc dot gnu.org ---
Fixed on trunk. Closing.
>From gcc-bugs-return-628970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 04:44:33 2019
Return-Path: <gcc-bugs-return-628970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110826 invoked by alias); 13 Jan 2019 04:44: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 110747 invoked by uid 48); 13 Jan 2019 04:44:25 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51628] __attribute__((packed)) is unsafe in some cases (i.e. add -Waddress-of-packed-member, etc.)
Date: Sun, 13 Jan 2019 04:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.5.1
X-Bugzilla-Keywords: diagnostic, patch, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51628-4-bjzkBtF5fX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51628-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51628-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01779.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51628
--- Comment #59 from H.J. Lu <hjl.tools at gmail dot com> ---
A missing warning:
[hjl@gnu-cfl-1 pr51628-7]$ cat pr51628-33.c
struct pair_t
{
char x;
int i[4];
} __attribute__ ((packed, aligned (4)));
extern struct pair_t p;
extern void bar (int *);
void
foo (struct pair_t *p)
{
bar (p ? p->i : (int *) 0);
}
[hjl@gnu-cfl-1 pr51628-7]$
/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc/xgcc
-B/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc/ -O2 -S
pr51628-33.c
[hjl@gnu-cfl-1 pr51628-7]$
>From gcc-bugs-return-628971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 04:45:05 2019
Return-Path: <gcc-bugs-return-628971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111791 invoked by alias); 13 Jan 2019 04:45: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 111637 invoked by uid 48); 13 Jan 2019 04:44:58 -0000
From: "lichray at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84849] Ambiguous resolution of braze initializer list to a class with explicit constructors
Date: Sun, 13 Jan 2019 04:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: lichray at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84849-4-1pRAHggX7E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01780.txt.bz2
Content-length: 1110
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84849
Zhihao Yuan <lichray at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |lichray at gmail dot com
--- Comment #6 from Zhihao Yuan <lichray at gmail dot com> ---
Here is a possibly related case:
#include <tuple>
template <class T>
struct pair
{
using value_type = pair<std::remove_reference_t<T>>;
T a, b;
constexpr pair& operator=(value_type const& other)
{
a = other.a;
b = other.b;
return *this;
}
constexpr pair& operator=(value_type&& other)
{
a = std::move(other.a);
b = std::move(other.b);
return *this;
}
};
template <class T>
constexpr pair<T&> tie(T& a, T& b) noexcept
{
return { a, b };
}
int main()
{
int a = 3;
int b = 5;
tie(a, b) = { b, a % b }; // works
tie(a, b) = { b, a }; // wat
}
Error messages are very similar https://godbolt.org/z/4FSeOO.
>From gcc-bugs-return-628972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 05:09:50 2019
Return-Path: <gcc-bugs-return-628972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69028 invoked by alias); 13 Jan 2019 05:09:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68253 invoked by uid 48); 13 Jan 2019 05:09:45 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88704] Accepts invalid program with [*] outside function prototype scope.
Date: Sun, 13 Jan 2019 05:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88704-4-iNVZRWMBYA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88704-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01781.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88704
--- Comment #3 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
(In reply to Martin Sebor from comment #2)
> Confirmed, although I'd be more inclined to invest energy into including
> -Wstrict-prototypes in -Wall or -Wextra than into diagnosing the VLA in
> K&R-style definitions.
Yeah, probably not worth fixing since K&R-style function definitions is an
obsolencent feature.
>From gcc-bugs-return-628973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 05:15:57 2019
Return-Path: <gcc-bugs-return-628973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71589 invoked by alias); 13 Jan 2019 05:15:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71545 invoked by uid 48); 13 Jan 2019 05:15:51 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88731] [DR 481] Rejects well-formed program using bit-fields in _Generic.
Date: Sun, 13 Jan 2019 05:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88731-4-ONPqoxV3pA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01782.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88731
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #3 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
(In reply to joseph@codesourcery.com from comment #2)
> GCC makes the integer type of the bit-field in question "unsigned:4".
> See DR#315 (also, see the line of C90 DRs that led to the wording changes
> in C99 relating to types of bit-fields, references in
> <https://gcc.gnu.org/ml/gcc/2017-10/msg00192.html>).
Thanks for the explanation.
>From gcc-bugs-return-628974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 08:52:59 2019
Return-Path: <gcc-bugs-return-628974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47708 invoked by alias); 13 Jan 2019 08:52: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 47633 invoked by uid 48); 13 Jan 2019 08:52:54 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80257] Cygwin test fail: pointer_check_1.f90 output test
Date: Sun, 13 Jan 2019 08:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80257-4-TiDZgND2tz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80257-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80257-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01783.txt.bz2
Content-length: 182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80257
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this PR still valid (over a year without feedback)?
>From gcc-bugs-return-628975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 08:57:22 2019
Return-Path: <gcc-bugs-return-628975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54117 invoked by alias); 13 Jan 2019 08:57:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54043 invoked by uid 48); 13 Jan 2019 08:57:18 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/44589] Missing not-set diagnositic (as READ arguments are clobbered)
Date: Sun, 13 Jan 2019 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-44589-4-yGsGZLrQgT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-44589-4@http.gcc.gnu.org/bugzilla/>
References: <bug-44589-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01784.txt.bz2
Content-length: 143
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=44589
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
(b) is pr30802.
>From gcc-bugs-return-628976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 09:44:20 2019
Return-Path: <gcc-bugs-return-628976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94139 invoked by alias); 13 Jan 2019 09:44: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 94093 invoked by uid 48); 13 Jan 2019 09:44:15 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88819] New: ICE (segfault) when compiling C++ code with -std=c++2a
Date: Sun, 13 Jan 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01785.txt.bz2
Content-length: 1377
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88819
Bug ID: 88819
Summary: ICE (segfault) when compiling C++ code with -std=c++2a
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: su at cs dot ucdavis.edu
Target Milestone: ---
This appears to be a recent regression.
$ g++tk -v
Using built-in specs.
COLLECT_GCC=g++tk
COLLECT_LTO_WRAPPER=/home/su/software/tmp/gcc/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 9.0.0 20190112 (experimental) [trunk revision 267885] (GCC)
$
$ g++tk -std=c++2a tmp.cpp
g++tk: internal compiler error: Segmentation fault signal terminated program
cc1plus
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
$
--------------------------------------
template < typename T, template < T > class TT, class R = TT < 0 > > struct A
{
template < R > struct B {};
};
template < int > struct C {};
A < int, C, C < 0 > > a;
>From gcc-bugs-return-628977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 10:23:30 2019
Return-Path: <gcc-bugs-return-628977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21327 invoked by alias); 13 Jan 2019 10:23:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21281 invoked by uid 48); 13 Jan 2019 10:23:25 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/34706] FE should reuse array temporaries, reduce temporaties and tell ME the array-size type
Date: Sun, 13 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-34706-4-eP8G9HrB7h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-34706-4@http.gcc.gnu.org/bugzilla/>
References: <bug-34706-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01786.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=34706
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
No activity for over 11 years!-(
> Unassigning for the rest of the improvements in this bug.
What is "the rest of the improvements"?
If it is not an empty set, one should file new PRs for them and close this one
as FIXED.
>From gcc-bugs-return-628978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 10:46:08 2019
Return-Path: <gcc-bugs-return-628978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57809 invoked by alias); 13 Jan 2019 10:46:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57709 invoked by uid 48); 13 Jan 2019 10:46:01 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/38619] error message when converting between different derived types with same name
Date: Sun, 13 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status bug_severity
Message-ID: <bug-38619-4-TcTrV6U8WN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38619-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38619-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01787.txt.bz2
Content-length: 984
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38619
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Status|NEW |WAITING
Severity|normal |enhancement
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
The test compiles if SEQUENCE is added after
TYPE :: ta
I agree that the error "Can't convert TYPE(ta) to TYPE(ta)" is not very
helpful.
One possibility is to split
gfc_error ("Can't convert %s to %s at %L",
gfc_typename (&from_ts), gfc_typename (ts), &expr->where);
in intrinsic.c, one for the general case and one for derived types with the
addition of something such as "consider adding a SEQUENCE statement".
Is it worth the trouble (the PR is ten year old)?
>From gcc-bugs-return-628979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 11:01:05 2019
Return-Path: <gcc-bugs-return-628979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110937 invoked by alias); 13 Jan 2019 11:01: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 110706 invoked by uid 48); 13 Jan 2019 11:00:53 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/31592] Better message if using non-intrinsic initialization expression
Date: Sun, 13 Jan 2019 11:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-31592-4-C3GNnEk7ng@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-31592-4@http.gcc.gnu.org/bugzilla/>
References: <bug-31592-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01788.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=31592
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
In the F2018 draft I see
10.1.11 Specification expression
...
5 A function is a specification function if it is a pure function,
is not a standard intrinsic function, is not an internal function,
is not a statement function, and does not have a dummy procedure argument.
It seems that the "is not defined with the RECURSIVE keyword." has been
dropped.
>From gcc-bugs-return-628980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 11:06:40 2019
Return-Path: <gcc-bugs-return-628980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9884 invoked by alias); 13 Jan 2019 11:06:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6882 invoked by uid 55); 13 Jan 2019 11:06:35 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59345] _gfortran_internal_pack on compiler generated temps
Date: Sun, 13 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59345-4-dOPAYo7Y5L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01789.txt.bz2
Content-length: 985
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59345
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Jan 13 11:06:03 2019
New Revision: 267903
URL: https://gcc.gnu.org/viewcvs?rev=267903&root=gcc&view=rev
Log:
2019-01-13 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/59345
* trans-array.c (gfc_conv_array_parameter): Remove TODO. Do not
pack/unpack results of functions which return an explicit-shaped
or allocatable array.
2019-01-13 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/59345
* gfortran.dg/internal_pack_17.f90: New test.
* gfortran.dg/alloc_comp_auto_array_3.f90: Adjust number of calls
to builtin_free.
Added:
trunk/gcc/testsuite/gfortran.dg/internal_pack_17.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/alloc_comp_auto_array_3.f90
>From gcc-bugs-return-628981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 11:07:48 2019
Return-Path: <gcc-bugs-return-628981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23442 invoked by alias); 13 Jan 2019 11:07: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 23400 invoked by uid 48); 13 Jan 2019 11:07:44 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59345] _gfortran_internal_pack on compiler generated temps
Date: Sun, 13 Jan 2019 11:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-59345-4-Jzx7L0Ni9g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01790.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59345
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Fixed, closing.
>From gcc-bugs-return-628982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 11:18:41 2019
Return-Path: <gcc-bugs-return-628982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80256 invoked by alias); 13 Jan 2019 11:18: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 76910 invoked by uid 48); 13 Jan 2019 11:18:36 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/35267] VOLATILE constrain: Misleading error message "Incompatible ranks"
Date: Sun, 13 Jan 2019 11:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
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-35267-4-WEeyWsY9E9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-35267-4@http.gcc.gnu.org/bugzilla/>
References: <bug-35267-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01791.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35267
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Considering
(1) that the code is invalid, hence the compiler can do anything deemed
suitable.
(2) the PR is almost eleven year old without feedback
I am closing the PR as WONTFIX.
>From gcc-bugs-return-628983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 12:36:50 2019
Return-Path: <gcc-bugs-return-628983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60965 invoked by alias); 13 Jan 2019 12:36: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 55510 invoked by uid 48); 13 Jan 2019 12:36:45 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56789] Handling of contiguous dummy arguments
Date: Sun, 13 Jan 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: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-56789-4-5dxlGuBWxD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01792.txt.bz2
Content-length: 381
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789
--- Comment #19 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I have asked in
https://groups.google.com/forum/#!search/comp.lang.fortran$20contiguous$20dummy%7Csort:date/comp.lang.fortran/QiFkx8b48uw/wtQE9M_aFwAJ
.
Let's see what sort of answers there will be, apart from the almost
inevitable references to PL/I...
>From gcc-bugs-return-628984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 12:47:51 2019
Return-Path: <gcc-bugs-return-628984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19605 invoked by alias); 13 Jan 2019 12:47: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 19540 invoked by uid 48); 13 Jan 2019 12:47:45 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] New: ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Sun, 13 Jan 2019 12:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01793.txt.bz2
Content-length: 2573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88820
Bug ID: 88820
Summary: ICE in in C++2a mode for code which is able to be
compiled in C++17 mode
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: hanicka at hanicka dot net
Target Milestone: ---
Created attachment 45420
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45420&action=edit
one file with all includes included
Hi, I found ICE in GCC9-HEAD with CTRE library (I'm author) when I compiled it
with C++2a mode. Same code with C++17 mode is compiled correctly, I wasn't able
to minimize code which reproduce the error.
But I was able to find responsible part of the library and reimplement it
differently (problematic part is enabled with
-DCTRE_ENABLE_TRAMPOLINING_ON_GCC9)
I think that problem is related to class-nontype-template-arguments change in
C++2a, check line 314.
I'm using GCC9 current head (January 13th 2019).
https://gcc.godbolt.org/z/_G0854
(GCC8.2 is compiling correctly the same code.)
g++-HEAD test-me.cpp -std=c++17 -DCTRE_ENABLE_TRAMPOLINING_ON_GCC9 -g0
=> correct
g++-HEAD test-me.cpp -std=c++2a -DCTRE_ENABLE_TRAMPOLINING_ON_GCC9 -g0
=> fail
<source>: In substitution of 'template<class Grammar, basic_fixed_string input,
class ActionSelector, bool IgnoreUnknownActions> template<class Subject> static
constexpr auto ctll::parser<Grammar, input, ActionSelector,
IgnoreUnknownActions>::trampoline_decide(Subject) [with Subject = <missing>;
Grammar = ctll::empty_subject; basic_fixed_string input = <missing>;
ActionSelector = <missing>; bool IgnoreUnknownActions = <missing>]':
<source>:464:74: required from here
<source>:458:68: internal compiler error: tree check: expected tree that
contains 'decl minimal' structure, have 'error_mark' in decl_anon_ns_mem_p, at
cp/tree.c:3478
458 | template <typename Subject = empty_subject> static constexpr auto
trampoline_decide(Subject subject = {}) noexcept {
|
^~~~~~~~~~~~~~~~~
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
Compiler returned: 1
test.me.cpp is attached
>From gcc-bugs-return-628985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 12:49:05 2019
Return-Path: <gcc-bugs-return-628985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26530 invoked by alias); 13 Jan 2019 12:49: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 25945 invoked by uid 48); 13 Jan 2019 12:48:50 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67277] segfault when passing a missing optional argument to an elemental intrinsic
Date: Sun, 13 Jan 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-67277-4-zjTxcs8Wrc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67277-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67277-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01794.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67277
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Let's see if I can do anything about this...
>From gcc-bugs-return-628986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 13:11:05 2019
Return-Path: <gcc-bugs-return-628986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5181 invoked by alias); 13 Jan 2019 13:11: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 5089 invoked by uid 48); 13 Jan 2019 13:10:59 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86356] "invalid use of pack expansion" with fold expressions
Date: Sun, 13 Jan 2019 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86356-4-B548jN3IbA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86356-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86356-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01795.txt.bz2
Content-length: 789
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86356
ensadc at mailnesia dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ensadc at mailnesia dot com
--- Comment #1 from ensadc at mailnesia dot com ---
Reduced:
template<bool B> struct mp_bool { static constexpr bool value = B; };
template<class... T> using mp_any =
mp_bool<(static_cast<bool>(T::value) || ...)>;
template<class T>
struct A { static constexpr bool value = true; };
template<bool> struct variant_base_impl {};
template<class... T> using variant_base
= variant_base_impl<mp_any<mp_bool<true>, A<T>...>::value>;
int main()
{
variant_base<int>();
}
>From gcc-bugs-return-628987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:09:29 2019
Return-Path: <gcc-bugs-return-628987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103634 invoked by alias); 13 Jan 2019 14:09: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 103598 invoked by uid 48); 13 Jan 2019 14:09:24 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/67277] segfault when passing a missing optional argument to an elemental intrinsic
Date: Sun, 13 Jan 2019 14:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
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 assigned_to
Message-ID: <bug-67277-4-c4JzeHip4I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67277-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67277-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01796.txt.bz2
Content-length: 3805
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67277
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEW
Assignee|tkoenig at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
I thought something like this
Index: trans-intrinsic.c
===================================================================
--- trans-intrinsic.c (Revision 267903)
+++ trans-intrinsic.c (Arbeitskopie)
@@ -6355,6 +6355,9 @@ gfc_conv_intrinsic_ishftc (gfc_se * se, gfc_expr *
tree rrot;
tree zero;
unsigned int num_args;
+ bool optional_size = false;
+ gfc_expr *size = NULL;
+ tree library, inlined, present;
num_args = gfc_intrinsic_argument_list_length (expr);
args = XALLOCAVEC (tree, num_args);
@@ -6363,6 +6366,11 @@ gfc_conv_intrinsic_ishftc (gfc_se * se, gfc_expr *
if (num_args == 3)
{
+ size = expr->value.function.actual->next->next->expr;
+ optional_size = size->expr_type == EXPR_VARIABLE
+ && size->symtree->n.sym->attr.dummy
+ && size->symtree->n.sym->attr.optional;
+
/* Use a library function for the 3 parameter version. */
tree int4type = gfc_get_int_type (4);
@@ -6396,14 +6404,19 @@ gfc_conv_intrinsic_ishftc (gfc_se * se, gfc_expr *
default:
gcc_unreachable ();
}
- se->expr = build_call_expr_loc (input_location,
+ library = build_call_expr_loc (input_location,
tmp, 3, args[0], args[1], args[2]);
/* Convert the result back to the original type, if we extended
the first argument's width above. */
if (expr->ts.kind < 4)
- se->expr = convert (type, se->expr);
+ library = convert (type, se->expr);
- return;
+ if (!optional_size)
+ {
+ se->expr = library;
+ return;
+ }
+ // debug_tree (library);
}
type = TREE_TYPE (args[0]);
@@ -6427,8 +6440,20 @@ gfc_conv_intrinsic_ishftc (gfc_se * se, gfc_expr *
/* Do nothing if shift == 0. */
tmp = fold_build2_loc (input_location, EQ_EXPR, logical_type_node, args[1],
zero);
- se->expr = fold_build3_loc (input_location, COND_EXPR, type, tmp, args[0],
- rrot);
+
+ inlined = fold_build3_loc (input_location, COND_EXPR, type, tmp, args[0],
+ rrot);
+
+ // debug_tree(inlined);
+ if (!optional_size)
+ {
+ se->expr = inlined;
+ return;
+ }
+
+ present = gfc_conv_expr_present (size->symtree->n.sym);
+ se->expr = fold_build3_loc (input_location, COND_EXPR, type, present,
+ library, inlined);
}
would do the trick. However, this results in
{
integer(kind=4) r;
integer(kind=4) s[4];
{
static integer(kind=4) A.0[4] = {1, 2, 3, 4};
integer(kind=4) D.3868;
D.3868 = *j;
{
integer(kind=8) S.1;
S.1 = 0;
while (1)
{
if (S.1 > 3) goto L.1;
{
integer(kind=4) D.3870;
integer(kind=4) D.3871;
D.3870 = j != 0B ? D.3868 : 0;
D.3871 = A.0[S.1];
s[S.1] = j != 0B ? _gfortran_ishftc4 (A.0[S.1], 1, D.3870) : D.3871
r>> 31;
}
S.1 = S.1 + 1;
}
L.1:;
}
}
so *j is dereferenced outside the check for presence.
Unassigning for now.
>From gcc-bugs-return-628988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:10:44 2019
Return-Path: <gcc-bugs-return-628988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104953 invoked by alias); 13 Jan 2019 14:10: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 104893 invoked by uid 48); 13 Jan 2019 14:10:39 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] gfortran documentation warning: '.' or ',' must follow @xref
Date: Sun, 13 Jan 2019 14:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: minor
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88803-4-mvmtO84tzH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01797.txt.bz2
Content-length: 1238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #1)
> More annoying than the warnings id the text displayed in the manual:
>
> the See CONVERT specifier on the open statement or the See
> GFORTRAN_CONVERT_UNIT environment variable.
>
> The text has been introduced at revision r251074.
>
> Would
>
> --- ../_clean/gcc/fortran/gfortran.texi 2019-01-01 13:17:33.000000000 +0100
> +++ gcc/fortran/gfortran.texi 2019-01-11 23:23:55.000000000 +0100
> @@ -1469,8 +1469,8 @@ are four-byte integers by default, and e
> compability only) is in effect.
>
> The representation of the record markers is that of unformatted files
> -given with the @option{-fconvert} option, the @xref{CONVERT specifier}
> -on the open statement or the @xref{GFORTRAN_CONVERT_UNIT} environment
> +given with the @option{-fconvert} option, the @ref{CONVERT specifier}
> +in an open statement or the @ref{GFORTRAN_CONVERT_UNIT} environment
> variable.
>
> The maximum number of bytes of user data in a subrecord is 2147483639
>
> be OK? or does it exist a better replacement for @xref?
Looks OK to me, pre-approved.
>From gcc-bugs-return-628989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:20:27 2019
Return-Path: <gcc-bugs-return-628989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58727 invoked by alias); 13 Jan 2019 14:20:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58624 invoked by uid 48); 13 Jan 2019 14:20:22 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57992] Pointless packing of contiguous arrays for simply contiguous functions results as actual arguments
Date: Sun, 13 Jan 2019 14:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-57992-4-Eq6wLH0pML@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01798.txt.bz2
Content-length: 562
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57992
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
After the fix for 56789, only one case left, the call to f2
(contiguous pointer).
Should be straightforward...
>From gcc-bugs-return-628990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:24:59 2019
Return-Path: <gcc-bugs-return-628990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72415 invoked by alias); 13 Jan 2019 14:24:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72325 invoked by uid 48); 13 Jan 2019 14:24:54 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] [9 Regression] False positive -Waddress-of-packed-member
Date: Sun, 13 Jan 2019 14:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88664-4-USfRfmHiAv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01799.txt.bz2
Content-length: 154
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
--- Comment #6 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
There's STRIP_NOPS, isn't there?
>From gcc-bugs-return-628991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:34:03 2019
Return-Path: <gcc-bugs-return-628991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9930 invoked by alias); 13 Jan 2019 14:34: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 9806 invoked by uid 55); 13 Jan 2019 14:33:58 -0000
From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56789] Handling of contiguous dummy arguments
Date: Sun, 13 Jan 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paul.richard.thomas at gmail dot com
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-56789-4-fwynVpH4AG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01800.txt.bz2
Content-length: 1072
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789
--- Comment #20 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Hi Thomas,
I was mulling this over a few months ago and came to the conclusion
that copy-in/copy-out was the only thing that made sense.
The IBM manual is explicit about this:
https://www.ibm.com/support/knowledgecenter/SSGH4D_15.1.3/com.ibm.xlf1513.aix.doc/language_ref/contiguous.html
Regards
Paul
On Sun, 13 Jan 2019 at 12:36, tkoenig at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789
>
> --- Comment #19 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> I have asked in
> https://groups.google.com/forum/#!search/comp.lang.fortran$20contiguous$20dummy%7Csort:date/comp.lang.fortran/QiFkx8b48uw/wtQE9M_aFwAJ
> .
>
> Let's see what sort of answers there will be, apart from the almost
> inevitable references to PL/I...
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
> You are the assignee for the bug.
>From gcc-bugs-return-628992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:40:16 2019
Return-Path: <gcc-bugs-return-628992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13798 invoked by alias); 13 Jan 2019 14:40:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13727 invoked by uid 48); 13 Jan 2019 14:40:11 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56789] Handling of contiguous dummy arguments
Date: Sun, 13 Jan 2019 14:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-56789-4-qCY2mueR8G@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01801.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|pault at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Hi Paul,
> I was mulling this over a few months ago and came to the conclusion
> that copy-in/copy-out was the only thing that made sense.
Well, in that case, I'll take this (if you don't mind).
I am currently working in that area anyway, so I might as
well look at this.
Regards
Thomas
>From gcc-bugs-return-628993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:52:01 2019
Return-Path: <gcc-bugs-return-628993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19577 invoked by alias); 13 Jan 2019 14:52:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19517 invoked by uid 48); 13 Jan 2019 14:51:56 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88821] New: Inline packing of non-contiguous arguments
Date: Sun, 13 Jan 2019 14:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01802.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88821
Bug ID: 88821
Summary: Inline packing of non-contiguous arguments
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
Because the packing / unpacking routines are opaque, they
could result in lots of missed opportunities for inlining.
See https://gcc.gnu.org/bugzilla/attachment.cgi?id=45014 for
PR 57992.
It should be doable to inline this.
>From gcc-bugs-return-628994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:54:21 2019
Return-Path: <gcc-bugs-return-628994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21089 invoked by alias); 13 Jan 2019 14:54: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 21023 invoked by uid 48); 13 Jan 2019 14:54:14 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57992] Pointless packing of contiguous arrays for simply contiguous functions results as actual arguments
Date: Sun, 13 Jan 2019 14:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-57992-4-AC0JNP78mX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01803.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57992
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Chris Elrod from comment #3)
> Created attachment 45014 [details]
> Code that produces lots of unnecessary and performance-crippling
> _gfortran_internal_pack@PLT and _gfortran_internal_unpack@PLT
The packing is not unnecessary, but it is performed in a way
that I am now convinced is sub-optimal.
I have created PR 88821 for this.
>From gcc-bugs-return-628996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:58:17 2019
Return-Path: <gcc-bugs-return-628996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30677 invoked by alias); 13 Jan 2019 14:58:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30588 invoked by uid 55); 13 Jan 2019 14:58:11 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59345] _gfortran_internal_pack on compiler generated temps
Date: Sun, 13 Jan 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: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59345-4-5Oq2kK3hhS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59345-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01805.txt.bz2
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59345
--- Comment #9 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Jan 13 14:57:39 2019
New Revision: 267905
URL: https://gcc.gnu.org/viewcvs?rev=267905&root=gcc&view=rev
Log:
2019-01-13 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/57992
* trans-array.c (gfc_conv_array_parameter): Do not pack/unpack
functions with contiguous results.
2019-01-13 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/59345
* gfortran.dg/internal_pack_18.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/internal_pack_18.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:58:17 2019
Return-Path: <gcc-bugs-return-628995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30660 invoked by alias); 13 Jan 2019 14:58:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30585 invoked by uid 55); 13 Jan 2019 14:58:11 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57992] Pointless packing of contiguous arrays for simply contiguous functions results as actual arguments
Date: Sun, 13 Jan 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: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-57992-4-8QwJVswoKW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01804.txt.bz2
Content-length: 761
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57992
--- Comment #7 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Sun Jan 13 14:57:39 2019
New Revision: 267905
URL: https://gcc.gnu.org/viewcvs?rev=267905&root=gcc&view=rev
Log:
2019-01-13 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/57992
* trans-array.c (gfc_conv_array_parameter): Do not pack/unpack
functions with contiguous results.
2019-01-13 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/59345
* gfortran.dg/internal_pack_18.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/internal_pack_18.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-628997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 14:59:24 2019
Return-Path: <gcc-bugs-return-628997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35040 invoked by alias); 13 Jan 2019 14:59:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 34971 invoked by uid 48); 13 Jan 2019 14:59:20 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88664] [9 Regression] False positive -Waddress-of-packed-member
Date: Sun, 13 Jan 2019 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88664-4-uyRSWS67rL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88664-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01806.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88664
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Nathan Sidwell from comment #6)
> There's STRIP_NOPS, isn't there?
The updated patch is posted at
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00732.html
>From gcc-bugs-return-628998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 15:01:33 2019
Return-Path: <gcc-bugs-return-628998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48062 invoked by alias); 13 Jan 2019 15:01:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47422 invoked by uid 48); 13 Jan 2019 15:01:27 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57992] Pointless packing of contiguous arrays for simply contiguous functions results as actual arguments
Date: Sun, 13 Jan 2019 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
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: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-57992-4-T9w3jWKk2q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57992-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01807.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57992
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
The original part of this bug is fixed.
Closing.
>From gcc-bugs-return-628999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 15:01:36 2019
Return-Path: <gcc-bugs-return-628999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48291 invoked by alias); 13 Jan 2019 15:01: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 47599 invoked by uid 48); 13 Jan 2019 15:01:29 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/36854] [meta-bug] fortran front-end optimization
Date: Sun, 13 Jan 2019 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-36854-4-JYQMRCXtxI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-36854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-36854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01808.txt.bz2
Content-length: 526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=36854
Bug 36854 depends on bug 57992, which changed state.
Bug 57992 Summary: Pointless packing of contiguous arrays for simply contiguous functions results as actual arguments
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57992
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-629000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 15:36:01 2019
Return-Path: <gcc-bugs-return-629000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113275 invoked by alias); 13 Jan 2019 15:36:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113237 invoked by uid 48); 13 Jan 2019 15:35:56 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88822] New: Strange inconsistency between types of qualified rvalues.
Date: Sun, 13 Jan 2019 15: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01809.txt.bz2
Content-length: 1740
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88822
Bug ID: 88822
Summary: Strange inconsistency between types of qualified
rvalues.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
int main()
{
int * const p1 = 0;
int * _Atomic p2 = 0;
int * const _Atomic p3 = 0;
struct S { int x; } s;
s = &*p1; // Type of &*p1 is int * const according to error message.
s = &*p2; // Type of &*p2 is int * according to error message.
s = &*p3; // Type of &*p3 is int * according to error message.
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observations:
The following error messages are outputed:
incompatible types when assigning to type 'struct S' from type 'int *
const'
incompatible types when assigning to type 'struct S' from type 'int *'
incompatible types when assigning to type 'struct S' from type 'int *'
From the error messages it looks like GCC thinks that the type of &*p1 is
int * const and that the types of &*p2 and &*p3 are both int * .
So it seems like if the _Atomic qualifier is used, all qualifiers are
removed, else they are keept.
6.5.3.2/3 describing the special case of &* does not say anything about
droping any qualifiers. However since the result of &* is an rvalue the
intention of the standard was probably to remove all qualifiers always.
>From gcc-bugs-return-629001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 15:42:40 2019
Return-Path: <gcc-bugs-return-629001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118727 invoked by alias); 13 Jan 2019 15:42: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 118674 invoked by uid 48); 13 Jan 2019 15:42:36 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88823] New: ivopts introduces -1(OVF)
Date: Sun, 13 Jan 2019 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01810.txt.bz2
Content-length: 828
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88823
Bug ID: 88823
Summary: ivopts introduces -1(OVF)
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: glisse at gcc dot gnu.org
Target Milestone: ---
int g (int a, int *v)
{
v[0] = a;
v[1] = 0;
while (v[0]-- > 0)
v[1] += v[0];
return v[1];
}
With -O2, ivopts replaces "if (_18 > 0)" with "if (_4 != -1(OVF))". IIUC, it
should at least use drop_tree_overflow to get a clean constant -1, although I
don't know why the overflow appeared in the first place. Maybe the overflow
flag is harmless and you can just close as not-a-bug.
>From gcc-bugs-return-629002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 15:48:51 2019
Return-Path: <gcc-bugs-return-629002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122804 invoked by alias); 13 Jan 2019 15:48:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122639 invoked by uid 48); 13 Jan 2019 15:48:43 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87689] Memory corruption on Power 8
Date: Sun, 13 Jan 2019 15:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: wrong-code
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: dependson
Message-ID: <bug-87689-4-blZqTF6NrY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87689-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87689-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01811.txt.bz2
Content-length: 547
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87689
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |40976
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
This is probably caused by PR40976.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=40976
[Bug 40976] Merge DECL of procedure call with DECL of gfc_get_function_type
>From gcc-bugs-return-629003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 15:51:22 2019
Return-Path: <gcc-bugs-return-629003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124961 invoked by alias); 13 Jan 2019 15:51:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124878 invoked by uid 48); 13 Jan 2019 15:51:18 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/52351] Wrong bounds when passing an array section to an intent-in pointer dummy
Date: Sun, 13 Jan 2019 15: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.7.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also
Message-ID: <bug-52351-4-teh7t3Xp94@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52351-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52351-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01812.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52351
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=56789
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
See also PR 56789, where we also need to add a new descriptor.
>From gcc-bugs-return-629004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 16:21:36 2019
Return-Path: <gcc-bugs-return-629004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14883 invoked by alias); 13 Jan 2019 16:21:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14798 invoked by uid 48); 13 Jan 2019 16:21:32 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56789] Handling of contiguous dummy arguments
Date: Sun, 13 Jan 2019 16:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-56789-4-D535oRelgO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56789-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01813.txt.bz2
Content-length: 511
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56789
--- Comment #22 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #21)
> Hi Paul,
>
> > I was mulling this over a few months ago and came to the conclusion
> > that copy-in/copy-out was the only thing that made sense.
>
> Well, in that case, I'll take this (if you don't mind).
>
> I am currently working in that area anyway, so I might as
> well look at this.
>
> Regards
>
> Thomas
Be my guest!
Paul
>From gcc-bugs-return-629005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 16:55:14 2019
Return-Path: <gcc-bugs-return-629005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119654 invoked by alias); 13 Jan 2019 16:55: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 119613 invoked by uid 48); 13 Jan 2019 16:55:09 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88824] New: ICE on invalid
Date: Sun, 13 Jan 2019 16: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01814.txt.bz2
Content-length: 392
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88824
Bug ID: 88824
Summary: ICE on invalid
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: su at cs dot ucdavis.edu
Target Milestone: ---
>From gcc-bugs-return-629006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 16:57:20 2019
Return-Path: <gcc-bugs-return-629006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121370 invoked by alias); 13 Jan 2019 16:57: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 121336 invoked by uid 48); 13 Jan 2019 16:57:15 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvODg4MjVdIE5ldzogSUNFIG9uIChpbnZhbGlkKSBDKysxMSBj?= =?UTF-8?B?b2RlOiB0cmVlIGNoZWNrOiBleHBlY3RlZCBjbGFzcyDigJh0eXBl4oCZLCBo?= =?UTF-8?B?YXZlIOKAmGV4Y2VwdGlvbmFs4oCZIChlcnJvcl9tYXJrKSBpbiBjYW5fZG9f?= =?UTF-8?B?bnJ2b19wLCBhdCBjcC90eXBlY2suYzo5MzYx?Date: Sun, 13 Jan 2019 16:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01815.txt.bz2
Content-length: 3643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88825
Bug ID: 88825
Summary: ICE on (invalid) C++11 code: tree check: expected
class ‘type’, have ‘exceptional’ (error_mark) in
can_do_nrvo_p, at cp/typeck.c:9361
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: su at cs dot ucdavis.edu
Target Milestone: ---
This seems to be a recent regression.
$ g++tk -v
Using built-in specs.
COLLECT_GCC=g++tk
COLLECT_LTO_WRAPPER=/home/su/software/tmp/gcc/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 9.0.0 20190112 (experimental) [trunk revision 267885] (GCC)
$
$ g++tk -c tmp.cpp
tmp.cpp: In function ‘auto* f()’:
tmp.cpp:4:10: error: unable to deduce ‘auto*’ from ‘t’
4 | return t;
| ^
tmp.cpp:4:10: note: mismatched types ‘auto*’ and ‘int’
tmp.cpp:4:10: internal compiler error: tree check: expected class ‘type’, have
‘exceptional’ (error_mark) in can_do_nrvo_p, at cp/typeck.c:9361
0x608e99 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
../../gcc-source-trunk/gcc/tree.c:9864
0x8fee4b tree_class_check(tree_node*, tree_code_class, char const*, int, char
const*)
../../gcc-source-trunk/gcc/tree.h:3299
0x8fee4b can_do_nrvo_p
../../gcc-source-trunk/gcc/cp/typeck.c:9360
0x9126ae check_return_expr(tree_node*, bool*)
../../gcc-source-trunk/gcc/cp/typeck.c:9671
0x8b065e finish_return_stmt(tree_node*)
../../gcc-source-trunk/gcc/cp/semantics.c:895
0x805227 cp_parser_jump_statement
../../gcc-source-trunk/gcc/cp/parser.c:12848
0x805227 cp_parser_statement
../../gcc-source-trunk/gcc/cp/parser.c:11120
0x805d4f cp_parser_statement_seq_opt
../../gcc-source-trunk/gcc/cp/parser.c:11586
0x805e5f cp_parser_compound_statement
../../gcc-source-trunk/gcc/cp/parser.c:11540
0x806560 cp_parser_function_body
../../gcc-source-trunk/gcc/cp/parser.c:22523
0x806560 cp_parser_ctor_initializer_opt_and_function_body
../../gcc-source-trunk/gcc/cp/parser.c:22558
0x806912 cp_parser_function_definition_after_declarator
../../gcc-source-trunk/gcc/cp/parser.c:27621
0x81ef1a cp_parser_function_definition_from_specifiers_and_declarator
../../gcc-source-trunk/gcc/cp/parser.c:27538
0x81ef1a cp_parser_init_declarator
../../gcc-source-trunk/gcc/cp/parser.c:20196
0x81f3c5 cp_parser_simple_declaration
../../gcc-source-trunk/gcc/cp/parser.c:13480
0x829104 cp_parser_declaration
../../gcc-source-trunk/gcc/cp/parser.c:13167
0x827e0e cp_parser_translation_unit
../../gcc-source-trunk/gcc/cp/parser.c:4692
0x827e0e c_parse_file()
../../gcc-source-trunk/gcc/cp/parser.c:40993
0x981bca c_common_parse_file()
../../gcc-source-trunk/gcc/c-family/c-opts.c:1151
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$
------------------------
auto f () -> auto *
{
int t = 0;
return t;
}
>From gcc-bugs-return-629007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:01:37 2019
Return-Path: <gcc-bugs-return-629007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1689 invoked by alias); 13 Jan 2019 17:01: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 1661 invoked by uid 48); 13 Jan 2019 17:01:33 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Sun, 13 Jan 2019 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88820-4-ncUSOmReer@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01816.txt.bz2
Content-length: 276
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88820
--- Comment #1 from Hana DusÃková <hanicka at hanicka dot net> ---
I think I found a related problem. It's about deducting argument of a class
when instantiating subtype. I created a minimal case. I'm attaching.
>From gcc-bugs-return-629008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:02:05 2019
Return-Path: <gcc-bugs-return-629008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2539 invoked by alias); 13 Jan 2019 17:02:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2465 invoked by uid 48); 13 Jan 2019 17:02:01 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88092] class nontype template deduction failed when providing type to class
Date: Sun, 13 Jan 2019 17:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-88092-4-LH1LfZX7J1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01817.txt.bz2
Content-length: 265
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88092
--- Comment #6 from Hana DusÃková <hanicka at hanicka dot net> ---
Created attachment 45421
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45421&action=edit
argument deduction of parent type
>From gcc-bugs-return-629009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:03:25 2019
Return-Path: <gcc-bugs-return-629009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34038 invoked by alias); 13 Jan 2019 17: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 18753 invoked by uid 48); 13 Jan 2019 17:03:20 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88092] class nontype template deduction failed when providing type to class
Date: Sun, 13 Jan 2019 17:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88092-4-TPnzfaSY2k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01818.txt.bz2
Content-length: 1816
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88092
--- Comment #7 from Hana DusÃková <hanicka at hanicka dot net> ---
If you compile it with:
g++-HEAD minimal.cpp -std=c++2a -DREFERENCE
=> correct
g++-HEAD minimal.cpp -std=c++2a -DAUTO
=> correct
g++-HEAD minimal.cpp -std=c++2a -DCNTTP
minimal.cpp: In member function 'unsigned int Foo<Value>::count()':
minimal.cpp:32:19: error: class template argument deduction failed:
32 | return SubType<0>().value();
| ^
minimal.cpp:32:19: error: no matching function for call to 'ArgType(ArgType)'
minimal.cpp:11:21: note: candidate: 'template<long unsigned int N>
ArgType(const char (&)[N])-> ArgType<N>'
11 | template <size_t N> ArgType(const char (&)[N]) -> ArgType<N>;
| ^~~~~~~
minimal.cpp:11:21: note: template argument deduction/substitution failed:
minimal.cpp:32:19: note: mismatched types 'const char [N]' and 'ArgType'
32 | return SubType<0>().value();
| ^
minimal.cpp:8:12: note: candidate: 'template<long unsigned int N>
ArgType(...)-> ArgType<N>'
8 | constexpr ArgType(...) noexcept { }
| ^~~~~~~
minimal.cpp:8:12: note: template argument deduction/substitution failed:
minimal.cpp:32:19: note: couldn't deduce template parameter 'N'
32 | return SubType<0>().value();
| ^
minimal.cpp:4:28: note: candidate: 'template<long unsigned int N>
ArgType(ArgType<N>)-> ArgType<N>'
4 | template <size_t N> struct ArgType {
| ^~~~~~~
minimal.cpp:4:28: note: template argument deduction/substitution failed:
minimal.cpp:32:19: note: mismatched types 'ArgType<N>' and 'ArgType'
32 | return SubType<0>().value();
| ^
>From gcc-bugs-return-629010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:03:29 2019
Return-Path: <gcc-bugs-return-629010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35258 invoked by alias); 13 Jan 2019 17:03:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32102 invoked by uid 48); 13 Jan 2019 17:03:24 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82215] Feature request to better support two pass compiling with gfortran
Date: Sun, 13 Jan 2019 17:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-82215-4-g8bjKheWTk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82215-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82215-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01819.txt.bz2
Content-length: 469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82215
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #8 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Looking into this.
>From gcc-bugs-return-629011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:16:46 2019
Return-Path: <gcc-bugs-return-629011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44239 invoked by alias); 13 Jan 2019 17:16: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 44173 invoked by uid 48); 13 Jan 2019 17:16:41 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88826] New: ICE (segfault) when compiling invalid C++ code with -std=c++2a
Date: Sun, 13 Jan 2019 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01820.txt.bz2
Content-length: 3056
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88826
Bug ID: 88826
Summary: ICE (segfault) when compiling invalid C++ code with
-std=c++2a
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: su at cs dot ucdavis.edu
Target Milestone: ---
This appears to be a recent regression.
$ g++tk -v
Using built-in specs.
COLLECT_GCC=g++tk
COLLECT_LTO_WRAPPER=/home/su/software/tmp/gcc/gcc-trunk/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc-source-trunk/configure --enable-languages=c,c++,lto
--prefix=/home/su/software/tmp/gcc/gcc-trunk --disable-bootstrap
Thread model: posix
gcc version 9.0.0 20190112 (experimental) [trunk revision 267885] (GCC)
$
$ g++tk -std=c++2a -c tmp.cpp
tmp.cpp:1:40: error: types may not be defined in parameter types
1 | template < class A, class B : public A {}; > void f ();
| ^
tmp.cpp:1:41: error: ‘B’ is not a valid type for a template non-type parameter
because it is not literal
1 | template < class A, class B : public A {}; > void f ();
| ^
tmp.cpp:1:27: note: ‘B’ is not literal because:
1 | template < class A, class B : public A {}; > void f ();
| ^
tmp.cpp:1:41: internal compiler error: Segmentation fault
1 | template < class A, class B : public A {}; > void f ();
| ^
0xec3aff crash_signal
../../gcc-source-trunk/gcc/toplev.c:326
0x6db371 explain_non_literal_class(tree_node*)
../../gcc-source-trunk/gcc/cp/class.c:5516
0x82bce7 invalid_nontype_parm_type_p
../../gcc-source-trunk/gcc/cp/pt.c:24929
0x849768 process_template_parm(tree_node*, unsigned int, tree_node*, bool,
bool)
../../gcc-source-trunk/gcc/cp/pt.c:4316
0x81d79e cp_parser_template_parameter_list
../../gcc-source-trunk/gcc/cp/parser.c:15565
0x82145b cp_parser_explicit_template_declaration
../../gcc-source-trunk/gcc/cp/parser.c:27910
0x82145b cp_parser_template_declaration_after_export
../../gcc-source-trunk/gcc/cp/parser.c:27944
0x829129 cp_parser_declaration
../../gcc-source-trunk/gcc/cp/parser.c:13116
0x827e0e cp_parser_translation_unit
../../gcc-source-trunk/gcc/cp/parser.c:4692
0x827e0e c_parse_file()
../../gcc-source-trunk/gcc/cp/parser.c:40993
0x981bca c_common_parse_file()
../../gcc-source-trunk/gcc/c-family/c-opts.c:1151
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$
---------------------------------------------------------
template < class A, class B : public A {}; > void f ();
>From gcc-bugs-return-629012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:21:09 2019
Return-Path: <gcc-bugs-return-629012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46821 invoked by alias); 13 Jan 2019 17:21: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 46780 invoked by uid 48); 13 Jan 2019 17:21:04 -0000
From: "su at cs dot ucdavis.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88824] erroneous report
Date: Sun, 13 Jan 2019 17:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: su at cs dot ucdavis.edu
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution short_desc
Message-ID: <bug-88824-4-MsYIsmjpvw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01821.txt.bz2
Content-length: 546
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88824
Zhendong Su <su at cs dot ucdavis.edu> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
Summary|ICE on invalid |erroneous report
--- Comment #1 from Zhendong Su <su at cs dot ucdavis.edu> ---
incomplete report for PR 88825 erroneously reported --- apologies
>From gcc-bugs-return-629013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:51:43 2019
Return-Path: <gcc-bugs-return-629013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74279 invoked by alias); 13 Jan 2019 17:51: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 74244 invoked by uid 48); 13 Jan 2019 17:51:39 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Sun, 13 Jan 2019 17:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88820-4-d9dwroUQPt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01822.txt.bz2
Content-length: 1994
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88820
--- Comment #2 from Hana DusÃková <hanicka at hanicka dot net> ---
Created attachment 45422
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45422&action=edit
referencing subtype unable to deduce parent type
~/projekty/ice-gcc > g++-HEAD minimal.cpp -std=c++2a -DREFERENCE
~/projekty/ice-gcc > g++-HEAD minimal.cpp -std=c++2a -DAUTO
~/projekty/ice-gcc > g++-HEAD minimal.cpp -std=c++2a -DCNTTP
minimal.cpp: In member function 'unsigned int Foo<Value>::count()':
minimal.cpp:33:19: error: class template argument deduction failed:
33 | return SubType<0>().value();
| ^
minimal.cpp:33:19: error: no matching function for call to 'ArgType(ArgType)'
minimal.cpp:8:21: note: candidate: 'template<long unsigned int N> ArgType(const
char (&)[N])-> ArgType<N>'
8 | template <size_t N> ArgType(const char (&)[N]) -> ArgType<N>;
| ^~~~~~~
minimal.cpp:8:21: note: template argument deduction/substitution failed:
minimal.cpp:33:19: note: mismatched types 'const char [N]' and 'ArgType'
33 | return SubType<0>().value();
| ^
minimal.cpp:5:12: note: candidate: 'template<long unsigned int N>
ArgType(...)-> ArgType<N>'
5 | constexpr ArgType(...) noexcept { }
| ^~~~~~~
minimal.cpp:5:12: note: template argument deduction/substitution failed:
minimal.cpp:33:19: note: couldn't deduce template parameter 'N'
33 | return SubType<0>().value();
| ^
minimal.cpp:4:28: note: candidate: 'template<long unsigned int N>
ArgType(ArgType<N>)-> ArgType<N>'
4 | template <size_t N> struct ArgType {
| ^~~~~~~
minimal.cpp:4:28: note: template argument deduction/substitution failed:
minimal.cpp:33:19: note: mismatched types 'ArgType<N>' and 'ArgType'
33 | return SubType<0>().value();
| ^
>From gcc-bugs-return-629014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 17:52:34 2019
Return-Path: <gcc-bugs-return-629014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75255 invoked by alias); 13 Jan 2019 17:52: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 75193 invoked by uid 48); 13 Jan 2019 17:52:30 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88092] class nontype template deduction failed when providing type to class
Date: Sun, 13 Jan 2019 17:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88092-4-Tu73iGtj6D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01823.txt.bz2
Content-length: 226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88092
--- Comment #8 from Hana DusÃková <hanicka at hanicka dot net> ---
Please ignore two last comments, I sent them to wrong bug, it was supposed to
be for #88820.
>From gcc-bugs-return-629015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:07:41 2019
Return-Path: <gcc-bugs-return-629015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124552 invoked by alias); 13 Jan 2019 18:07: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 122237 invoked by uid 48); 13 Jan 2019 18:07:37 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88647] Rejects valid program dereferencing pointer with incomplete reference type.
Date: Sun, 13 Jan 2019 18:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88647-4-LskKbsVVDB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88647-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01824.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88647
Anders Granlund <anders.granlund.0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Anders Granlund <anders.granlund.0 at gmail dot com> ---
Invalid, but will open another bug case with a different test case.
>From gcc-bugs-return-629016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:11:03 2019
Return-Path: <gcc-bugs-return-629016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 399 invoked by alias); 13 Jan 2019 18:11: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 316 invoked by uid 48); 13 Jan 2019 18:10:59 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Sun, 13 Jan 2019 18:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed
Message-ID: <bug-88820-4-oaNvrkO1fv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01825.txt.bz2
Content-length: 820
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88820
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-13
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
The first ICE started with r265734. Will try to reduce...
>From gcc-bugs-return-629017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:14:19 2019
Return-Path: <gcc-bugs-return-629017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5645 invoked by alias); 13 Jan 2019 18:14: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 5558 invoked by uid 48); 13 Jan 2019 18:14:13 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88800] Spurious -Werror=array-bounds for non-taken branch
Date: Sun, 13 Jan 2019 18:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88800-4-CzPnLa0MUq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01826.txt.bz2
Content-length: 379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88800
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |msebor at gcc dot gnu.org
>From gcc-bugs-return-629018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:20:41 2019
Return-Path: <gcc-bugs-return-629018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28254 invoked by alias); 13 Jan 2019 18:20:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28186 invoked by uid 48); 13 Jan 2019 18:20:37 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56386] [F03] ICE with ASSOCIATE construct and an derived type array component
Date: Sun, 13 Jan 2019 18:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords: ice-on-valid-code, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
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: bug_status resolution
Message-ID: <bug-56386-4-j3HQ8cxBu4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56386-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56386-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01827.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56386
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #13 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on trunk.
Thanks for the report.
Paul
>From gcc-bugs-return-629019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:20:41 2019
Return-Path: <gcc-bugs-return-629019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28324 invoked by alias); 13 Jan 2019 18:20:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28211 invoked by uid 48); 13 Jan 2019 18:20:38 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87477] [meta-bug] [F03] issues concerning the ASSOCIATE statement
Date: Sun, 13 Jan 2019 18:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87477-4-8WZlBBk8u1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87477-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87477-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01828.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477
Bug 87477 depends on bug 56386, which changed state.
Bug 56386 Summary: [F03] ICE with ASSOCIATE construct and an derived type array component
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56386
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-629022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:21:51 2019
Return-Path: <gcc-bugs-return-629022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31910 invoked by alias); 13 Jan 2019 18:21:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31750 invoked by uid 48); 13 Jan 2019 18:21:47 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/87477] [meta-bug] [F03] issues concerning the ASSOCIATE statement
Date: Sun, 13 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87477-4-NUWHasWiTh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87477-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87477-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01831.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87477
Bug 87477 depends on bug 58618, which changed state.
Bug 58618 Summary: Wrong code with character substring and ASSOCIATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58618
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-629021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:21:50 2019
Return-Path: <gcc-bugs-return-629021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31792 invoked by alias); 13 Jan 2019 18:21: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 31684 invoked by uid 48); 13 Jan 2019 18:21:46 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/58618] Wrong code with character substring and ASSOCIATE
Date: Sun, 13 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-58618-4-i8i5l8mLuG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58618-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58618-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01830.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58618
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on trunk.
Thanks for the report.
Paul
>From gcc-bugs-return-629020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:21:39 2019
Return-Path: <gcc-bugs-return-629020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31035 invoked by alias); 13 Jan 2019 18:21: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 31013 invoked by uid 48); 13 Jan 2019 18:21:34 -0000
From: "anders.granlund.0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88827] New: Rejects valid program using &* operator combination.
Date: Sun, 13 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: anders.granlund.0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01829.txt.bz2
Content-length: 1022
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88827
Bug ID: 88827
Summary: Rejects valid program using &* operator combination.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: anders.granlund.0 at gmail dot com
Target Milestone: ---
Test case (prog.c):
int main()
{
struct S *p = 0;
&*p;
}
Compilation command line:
gcc prog.c -Wall -Wextra -std=c11 -pedantic-errors
Observed behaviour:
The following error message was outputed:
error: dereferencing pointer to incomplete type 'struct S'
Expected behaviour:
No error messages outputed. The program is valid. Note that using the value
0 for pointer p is not a problem since neither & nor * is evaluated due to
the special rule for &* in 6.5.3.2/3.
Note:
Clang accepts the program without outputing any error messages.
>From gcc-bugs-return-629023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:29:41 2019
Return-Path: <gcc-bugs-return-629023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40419 invoked by alias); 13 Jan 2019 18:29: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 40374 invoked by uid 48); 13 Jan 2019 18:29:38 -0000
From: "koenigni at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88729] ICE in libiberty during bootstrap with debug info
Date: Sun, 13 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: koenigni at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88729-4-j9E02L9QpC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88729-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01832.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88729
Nicolas Koenig <koenigni at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Nicolas Koenig <koenigni at gcc dot gnu.org> ---
It still doesn't work, but the error is a new one
>From gcc-bugs-return-629024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 18:55:46 2019
Return-Path: <gcc-bugs-return-629024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69454 invoked by alias); 13 Jan 2019 18:55:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69414 invoked by uid 48); 13 Jan 2019 18:55:42 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88828] New: Inefficient update of the first element of vector registers
Date: Sun, 13 Jan 2019 18:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01833.txt.bz2
Content-length: 1582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88828
Bug ID: 88828
Summary: Inefficient update of the first element of vector
registers
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: ubizjak at gmail dot com
Target Milestone: ---
[hjl@gnu-cfl-1 pr88778]$ cat u4.i
typedef float __v4sf __attribute__ ((__vector_size__ (16)));
typedef float __m128 __attribute__ ((__vector_size__ (16), __may_alias__));
__m128
foo (__m128 x, float f)
{
__m128 y = __extension__ (__m128)(__v4sf)
{ f, ((__v4sf) x)[1], ((__v4sf) x)[2], ((__v4sf) x)[3] };
return y;
}
[hjl@gnu-cfl-1 pr88778]$ gcc -S -O2 u4.i
[hjl@gnu-cfl-1 pr88778]$ cat u4.s
.file "u4.i"
.text
.p2align 4,,15
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
movaps %xmm0, %xmm4
movaps %xmm0, %xmm3
shufps $85, %xmm0, %xmm4
unpckhps %xmm0, %xmm3
unpcklps %xmm4, %xmm1
shufps $255, %xmm0, %xmm0
unpcklps %xmm0, %xmm3
movaps %xmm1, %xmm0
movlhps %xmm3, %xmm0
ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.ident "GCC: (GNU) 8.2.1 20190109 (Red Hat 8.2.1-7)"
.section .note.GNU-stack,"",@progbits
[hjl@gnu-cfl-1 pr88778]$
A simple movss will do.
>From gcc-bugs-return-629025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 19:19:22 2019
Return-Path: <gcc-bugs-return-629025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41322 invoked by alias); 13 Jan 2019 19:19:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38960 invoked by uid 55); 13 Jan 2019 19:19:18 -0000
From: "dominiq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] gfortran documentation warning: '.' or ',' must follow @xref
Date: Sun, 13 Jan 2019 19:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88803-4-aCEyv126pY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01834.txt.bz2
Content-length: 483
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
--- Comment #3 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Sun Jan 13 19:18:46 2019
New Revision: 267906
URL: https://gcc.gnu.org/viewcvs?rev=267906&root=gcc&view=rev
Log:
2019-01-13 Dominique d'Humieres <dominiq@gcc.gnu.org>
PR fortran/88803
* gfortran.texi: Replace @xref with @ref and adjust the sentence.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/gfortran.texi
>From gcc-bugs-return-629026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 19:28:11 2019
Return-Path: <gcc-bugs-return-629026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97977 invoked by alias); 13 Jan 2019 19:28:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97939 invoked by uid 48); 13 Jan 2019 19:28:07 -0000
From: "hanicka at hanicka dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Sun, 13 Jan 2019 19:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hanicka at hanicka dot net
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88820-4-jR0IbRkzf4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01835.txt.bz2
Content-length: 203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88820
--- Comment #4 from Hana DusÃková <hanicka at hanicka dot net> ---
The ICE will not happen if you comment out line 464 from first example.
>From gcc-bugs-return-629027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 19:46:13 2019
Return-Path: <gcc-bugs-return-629027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54080 invoked by alias); 13 Jan 2019 19:46: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 54005 invoked by uid 48); 13 Jan 2019 19:46:10 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] gfortran documentation warning: '.' or ',' must follow @xref
Date: Sun, 13 Jan 2019 19:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88803-4-wkyOgMXULc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01836.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
FIXED.
>From gcc-bugs-return-629028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 19:48:25 2019
Return-Path: <gcc-bugs-return-629028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60018 invoked by alias); 13 Jan 2019 19:48: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 59746 invoked by uid 48); 13 Jan 2019 19:48:03 -0000
From: "Casey at Carter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88829] New: Failure to deduce size of array of 2^31 chars
Date: Sun, 13 Jan 2019 19:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Casey at Carter dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01837.txt.bz2
Content-length: 2375
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88829
Bug ID: 88829
Summary: Failure to deduce size of array of 2^31 chars
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: Casey at Carter dot net
Target Milestone: ---
This sample TU:
using size_t = decltype(sizeof(int));
template<class T> T&& declval();
template<class T, size_t N>
void f(T(&&)[N]) {}
using U = decltype(f(declval<char[(1ULL << 31)]>())); // error: size of
array is negative
fails to compile on trunk with "g++ -std=c++2a repro.cpp", diagnosing:
<source>:8:51: error: no matching function for call to 'f(char
[2147483648])'
8 | using U = decltype(f(declval<char[(1ULL << 31)]>())); // error:
size of array is negative
| ^
<source>:6:6: note: candidate: 'template<class T, long unsigned int N> void
f(T (&&)[N])'
6 | void f(T(&&)[N]) {}
| ^
<source>:6:6: note: template argument deduction/substitution failed:
<source>: In substitution of 'template<class T, long unsigned int N> void
f(T (&&)[N]) [with T = char; long unsigned int N = 18446744071562067968]':
<source>:8:51: required from here
<source>:6:6: error: size of array is negative
<source>:6:8: error: size of array is negative
6 | void f(T(&&)[N]) {}
| ^~~~~~~~
<source>:8:49: error: invalid initialization of reference of type 'char
(&&)[1]' from expression of type 'char [2147483648]'
8 | using U = decltype(f(declval<char[(1ULL << 31)]>())); // error:
size of array is negative
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~^~
<source>:6:8: note: in passing argument 1 of 'void f(T (&&)[N]) [with T =
char; long unsigned int N = 18446744071562067968]'
6 | void f(T(&&)[N]) {}
| ^~~~~~~~
If arrays of size >= 2^31 aren't supported - which is a perfectly legitimate
implementation limit - I expect the formation of the array type to be diagnosed
rather than the deduction to fail. Also, the "size of array is negative"
diagnostic is confusing (#87996 already makes that point).
>From gcc-bugs-return-629029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 21:07:23 2019
Return-Path: <gcc-bugs-return-629029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67079 invoked by alias); 13 Jan 2019 21:07: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 66967 invoked by uid 48); 13 Jan 2019 21:07:18 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/80354] Poor support to silence -Wformat-truncation=1
Date: Sun, 13 Jan 2019 21:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 7.0.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80354-4-YwUFTqVT6o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80354-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80354-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01838.txt.bz2
Content-length: 1388
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80354
--- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
(In reply to Alejandro Colomar from comment #10)
> Many other warnings are supressed with (void), why is this one so special?
Not too many warnings can be suppressed by casts. Those that can must be at
least partially implemented in the front end where otherwise pointless casts
are still visible. -Wformat-truncation (and other warnings like it) is
implemented in the middle-end to benefit from optimizations such as constant
propagation or value range optimization. Semantically pointless casts have
long been removed from expressions by the time the warning sees the program.
It might be possible to use a cast as a suppression mechanism for this warning,
but I'm not convinced it would be helpful. Casting value-returning function
calls to void is a fairly common style used to denote that the return value is
unused. In the case of snprintf, that doesn't necessarily imply that the
program is prepared to deal correctly with the truncated output. In my
experience very few programs are. Most assume it simply doesn't happen. I
don't recall coming across an example involving a non-trivial format string
with arguments, especially of numeric types, where truncation would not have
caused some sort of an unexpected condition later on in the program.
>From gcc-bugs-return-629030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 21:10:05 2019
Return-Path: <gcc-bugs-return-629030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1893 invoked by alias); 13 Jan 2019 21:10:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120780 invoked by uid 48); 13 Jan 2019 21:10:01 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] New: ice in maybe_emit_vtables
Date: Sun, 13 Jan 2019 21:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01839.txt.bz2
Content-length: 1153
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
Bug ID: 88830
Summary: ice in maybe_emit_vtables
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
For this C++ code, compiled with recent gcc:
struct a {
~a();
};
class b {
virtual void c(int &);
};
class C : b {
void c(int &);
virtual int d() = 0;
a e;
};
void C::c(int &) {}
does this:
$ ~/gcc/results/bin/gcc -c -w bug495.cc
<built-in>: internal compiler error: Segmentation fault
0x10c3017 crash_signal
../../trunk/gcc/toplev.c:326
0x9765b4 maybe_emit_vtables
../../trunk/gcc/cp/decl2.c:2232
0x9765b4 c_parse_final_cleanups()
../../trunk/gcc/cp/decl2.c:4797
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
$
The bug seems to occur between revisions 267850 and 267900.
>From gcc-bugs-return-629031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 21:16:13 2019
Return-Path: <gcc-bugs-return-629031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81709 invoked by alias); 13 Jan 2019 21:16:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81608 invoked by uid 48); 13 Jan 2019 21:16:05 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvODg4MjVdIElDRSBvbiAoaW52YWxpZCkgQysrMTEgY29kZTog?= =?UTF-8?B?dHJlZSBjaGVjazogZXhwZWN0ZWQgY2xhc3Mg4oCYdHlwZeKAmSwgaGF2ZSA=?= =?UTF-8?B?4oCYZXhjZXB0aW9uYWzigJkgKGVycm9yX21hcmspIGluIGNhbl9kb19ucnZv?= =?UTF-8?B?X3AsIGF0IGNwL3R5cGVjay5jOjkzNjE=?Date: Sun, 13 Jan 2019 21:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-88825-4-jt2gG1w90n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01840.txt.bz2
Content-length: 740
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88825
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-13
CC| |mpolacek at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
ICE in can_do_nrvo_p -> mine.
>From gcc-bugs-return-629032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 21:47:20 2019
Return-Path: <gcc-bugs-return-629032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128691 invoked by alias); 13 Jan 2019 21:47: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 128632 invoked by uid 48); 13 Jan 2019 21:47:16 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88820] ICE in in C++2a mode for code which is able to be compiled in C++17 mode
Date: Sun, 13 Jan 2019 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88820-4-RqZ05icwcd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01841.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88820
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
This reduced test ICEs left and right with -std=c++17/14 since r236221, but the
ICE changed into another ICE with r248433.
template <__SIZE_TYPE__> class basic_fixed_string;
struct empty_subject;
template <basic_fixed_string> struct parser {
template <typename = empty_subject> static auto trampoline_decide();
bool correct = trampoline_decide();
};
>From gcc-bugs-return-629033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 21:59:28 2019
Return-Path: <gcc-bugs-return-629033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50158 invoked by alias); 13 Jan 2019 21:59:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 50123 invoked by uid 48); 13 Jan 2019 21:59:25 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] [9 Regression] ice in maybe_emit_vtables
Date: Sun, 13 Jan 2019 21:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88830-4-Rqj3uUreLd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01842.txt.bz2
Content-length: 820
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-13
CC| |mpolacek at gcc dot gnu.org
Target Milestone|--- |9.0
Summary|ice in maybe_emit_vtables |[9 Regression] ice in
| |maybe_emit_vtables
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-629034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 22:02:30 2019
Return-Path: <gcc-bugs-return-629034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55004 invoked by alias); 13 Jan 2019 22:02:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54950 invoked by uid 48); 13 Jan 2019 22:02:26 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] [9 Regression] ice in maybe_emit_vtables
Date: Sun, 13 Jan 2019 22:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88830-4-7ZjC4dbDJS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01843.txt.bz2
Content-length: 144
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r267855.
>From gcc-bugs-return-629035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 22:11:34 2019
Return-Path: <gcc-bugs-return-629035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71219 invoked by alias); 13 Jan 2019 22:11:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71127 invoked by uid 48); 13 Jan 2019 22:11:31 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] [9 Regression] ice in maybe_emit_vtables
Date: Sun, 13 Jan 2019 22:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88830-4-hKJF2C8SVH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01844.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
>From gcc-bugs-return-629036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 22:45:55 2019
Return-Path: <gcc-bugs-return-629036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35936 invoked by alias); 13 Jan 2019 22:45: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 35857 invoked by uid 48); 13 Jan 2019 22:45:51 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88819] ICE (segfault) when compiling C++ code with -std=c++2a
Date: Sun, 13 Jan 2019 22:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88819-4-fsjGLNVV4K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01845.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88819
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-13
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed. This started crashing with r265789 and the infinite looping started
with r267108.
>From gcc-bugs-return-629037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Jan 13 23:32:48 2019
Return-Path: <gcc-bugs-return-629037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127597 invoked by alias); 13 Jan 2019 23:32: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 127559 invoked by uid 48); 13 Jan 2019 23:32:44 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvODg4MjVdIFs3LzgvOSBSZWdyZXNzaW9uXSBJQ0Ugb24gKGlu?= =?UTF-8?B?dmFsaWQpIEMrKzExIGNvZGU6IHRyZWUgY2hlY2s6IGV4cGVjdGVkIGNsYXNz?= =?UTF-8?B?IOKAmHR5cGXigJksIGhhdmUg4oCYZXhjZXB0aW9uYWzigJkgKGVycm9yX21h?= =?UTF-8?B?cmspIGluIGNhbl9kb19ucnZvX3AsIGF0IGNwL3R5cGVjay5jOjkzNjE=?Date: Sun, 13 Jan 2019 23:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88825-4-TNdv9FA9tl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01846.txt.bz2
Content-length: 1023
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88825
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
Summary|ICE on (invalid) C++11 |[7/8/9 Regression] ICE on
|code: tree check: expected |(invalid) C++11 code: tree
|class ‘type’, have |check: expected class
|‘exceptional’ (error_mark) |‘type’, have ‘exceptional’
|in can_do_nrvo_p, at |(error_mark) in
|cp/typeck.c:9361 |can_do_nrvo_p, at
| |cp/typeck.c:9361
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think it is a regression because in the past we'd just give an error.
Started with r197248.
>From gcc-bugs-return-629038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 00:22:37 2019
Return-Path: <gcc-bugs-return-629038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59142 invoked by alias); 14 Jan 2019 00:22:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59071 invoked by uid 55); 14 Jan 2019 00:22:32 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Mon, 14 Jan 2019 00:22: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88776-4-OD4ZLo0BXd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01847.txt.bz2
Content-length: 680
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #7 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Mon Jan 14 00:22:00 2019
New Revision: 267910
URL: https://gcc.gnu.org/viewcvs?rev=267910&root=gcc&view=rev
Log:
2019-01-13 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libfortran/88776
* io/open.c (newunit): Free format buffer if the unit specified is for
stdin, stdout, or stderr.
* gfortran.dg/namelist_96.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/namelist_96.f90
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/open.c
>From gcc-bugs-return-629039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 00:23:27 2019
Return-Path: <gcc-bugs-return-629039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60154 invoked by alias); 14 Jan 2019 00: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 60098 invoked by uid 48); 14 Jan 2019 00:23:23 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86655] std::assoc_legendre should not constrain the value of m
Date: Mon, 14 Jan 2019 00:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-86655-4-6FUdkqayf3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01848.txt.bz2
Content-length: 891
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86655
--- Comment #5 from emsr at gcc dot gnu.org ---
Created attachment 45423
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45423&action=edit
Final patch that passes.
2018-01-14 Edward Smith-Rowland <3dw4rd@verizon.net>
PR libstdc++/86655 - std::assoc_legendre should not constrain
the value of m.
* include/tr1/legendre_function.tcc (__assoc_legendre_p,
__sph_legendre): If degree > order Don't throw, return 0.
* testsuite/special_functions/02_assoc_legendre/pr86655.cc: New test.
* testsuite/special_functions/20_sph_legendre/pr86655.cc: New test.
* testsuite/tr1/5_numerical_facilities/special_functions/
02_assoc_legendre/pr86655.cc: New test.
* testsuite/tr1/5_numerical_facilities/special_functions/
22_sph_legendre/pr86655.cc: New test.
>From gcc-bugs-return-629040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 00:31:38 2019
Return-Path: <gcc-bugs-return-629040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9067 invoked by alias); 14 Jan 2019 00:31:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9023 invoked by uid 48); 14 Jan 2019 00:31:34 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Mon, 14 Jan 2019 00:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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-88738-4-XKp6T83aRO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01849.txt.bz2
Content-length: 380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, I would guess that clang's "dumb" warning is fine for 99% of cases, and
the handful of exceptions could use #pragma to disable the warning.
But until/unless G++ gets such a warning, decorating the library in a few
specific places will be an improvement.
>From gcc-bugs-return-629041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 01:13:03 2019
Return-Path: <gcc-bugs-return-629041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22287 invoked by alias); 14 Jan 2019 01:13:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 14164 invoked by uid 55); 14 Jan 2019 01:12:59 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Mon, 14 Jan 2019 01:13: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88776-4-sPwyn4ulK1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01850.txt.bz2
Content-length: 832
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Mon Jan 14 01:12:27 2019
New Revision: 267911
URL: https://gcc.gnu.org/viewcvs?rev=267911&root=gcc&view=rev
Log:
2019-01-13 Jerry DeLisle <jvdelisle@gcc.gnu.org>
PR libfortran/88776
* io/list_read.c (namelist_read): Use nml_err_ret path on read error
not based on stdin_unit.
* io/open.c (newunit): Free format buffer if the unit specified is for
stdin, stdout, or stderr.
* gfortran.dg/namelist_96.f90: New test.
Modified:
branches/gcc-7-branch/gcc/testsuite/ChangeLog
branches/gcc-7-branch/libgfortran/ChangeLog
branches/gcc-7-branch/libgfortran/io/list_read.c
branches/gcc-7-branch/libgfortran/io/open.c
>From gcc-bugs-return-629042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 02:04:10 2019
Return-Path: <gcc-bugs-return-629042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2108 invoked by alias); 14 Jan 2019 02:04:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 615 invoked by uid 55); 14 Jan 2019 02:04:05 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Mon, 14 Jan 2019 02:04: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88776-4-1yZDnBmtob@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01851.txt.bz2
Content-length: 935
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
--- Comment #9 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Author: jvdelisle
Date: Mon Jan 14 02:03:34 2019
New Revision: 267912
URL: https://gcc.gnu.org/viewcvs?rev=267912&root=gcc&view=rev
Log:
2019-01-13 Jerry DeLisle <jvdelisle@gcc.gnu.org>
Backport from trunk
PR libfortran/88776
* io/list_read.c (namelist_read): Use nml_err_ret path on read error
not based on stdin_unit.
* io/open.c (newunit): Free format buffer if the unit specified is for
stdin, stdout, or stderr.
* gfortran.dg/namelist_96.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/namelist_96.f90
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/libgfortran/ChangeLog
branches/gcc-8-branch/libgfortran/io/list_read.c
branches/gcc-8-branch/libgfortran/io/open.c
>From gcc-bugs-return-629043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 02:27:10 2019
Return-Path: <gcc-bugs-return-629043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2399 invoked by alias); 14 Jan 2019 02: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 2215 invoked by uid 48); 14 Jan 2019 02:27:06 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88776] Namelist read from stdin: loss of data
Date: Mon, 14 Jan 2019 02:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88776-4-Fqcxaj5d75@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01852.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88776
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Fixed 7,8, and 9
>From gcc-bugs-return-629044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 02:59:35 2019
Return-Path: <gcc-bugs-return-629044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54439 invoked by alias); 14 Jan 2019 02:59:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40435 invoked by uid 48); 14 Jan 2019 02:59:31 -0000
From: "leolchat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug pch/56549] #pragma once ineffective with BOM in include file
Date: Mon, 14 Jan 2019 02:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: pch
X-Bugzilla-Version: 4.6.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: leolchat at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-56549-4-KqRdak9RaQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-56549-4@http.gcc.gnu.org/bugzilla/>
References: <bug-56549-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01853.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56549
leonard gerard <leolchat at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |leolchat at gmail dot com
--- Comment #4 from leonard gerard <leolchat at gmail dot com> ---
Confirmed with g++ (Ubuntu 7.3.0-27ubuntu1~18.04)
>From gcc-bugs-return-629045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 05:16:25 2019
Return-Path: <gcc-bugs-return-629045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103007 invoked by alias); 14 Jan 2019 05:16:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102919 invoked by uid 48); 14 Jan 2019 05:16:20 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/87329] ICE in patch_jump_insn, at cfgrtl.c:1271
Date: Mon, 14 Jan 2019 05:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87329-4-wSlIgFxIUQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87329-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87329-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01854.txt.bz2
Content-length: 465
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87329
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asolokha at gmx dot com
--- Comment #1 from Arseny Solokha <asolokha at gmx dot com> ---
I can reproduce it on the 8 branch but not on the current trunk w/ the rs6000
backend.
>From gcc-bugs-return-629046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 05:19:56 2019
Return-Path: <gcc-bugs-return-629046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105888 invoked by alias); 14 Jan 2019 05:19: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 105820 invoked by uid 48); 14 Jan 2019 05:19:50 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85368] [8 regression] phi-opt-11 test fails on IBM Z
Date: Mon, 14 Jan 2019 05:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85368-4-3wYjQAtL7D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85368-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85368-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01855.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85368
Arseny Solokha <asolokha at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |asolokha at gmx dot com
--- Comment #17 from Arseny Solokha <asolokha at gmx dot com> ---
Jakub, --param logical-op-non-short-circuit seems to still lack user's
documentation. Is it intentional?
>From gcc-bugs-return-629047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 06:54:28 2019
Return-Path: <gcc-bugs-return-629047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96964 invoked by alias); 14 Jan 2019 06:54:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94890 invoked by uid 48); 14 Jan 2019 06:54:23 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88828] Inefficient update of the first element of vector registers
Date: Mon, 14 Jan 2019 06:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget component
Message-ID: <bug-88828-4-2917Cq9cr8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01856.txt.bz2
Content-length: 1042
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88828
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |x86_64
Component|target |tree-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I think there are two issues here (maybe only one since I have not tested one
of them).
The first is not recognizing:
typedef float __v4sf __attribute__ ((__vector_size__ (16)));
__v4sf
foo (__v4sf x, float f)
{
__v4sf y = __extension__ (__v4sf)
{ f, x[1], x[2], x[3] };
return y;
}
is the same as:
__v4sf
foo1 (__v4sf x, float f)
{
__v4sf y = x;
y[0] = f;
return y;
}
This is a generic tree optimization issue.
The second is if foo1 is not optimized to what you want it to be. That would
be a target issue.
>From gcc-bugs-return-629048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 07:04:46 2019
Return-Path: <gcc-bugs-return-629048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6593 invoked by alias); 14 Jan 2019 07:04:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1327 invoked by uid 48); 14 Jan 2019 07:04:42 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Mon, 14 Jan 2019 07:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88738-4-RJaYAHI04w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01857.txt.bz2
Content-length: 391
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #8 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #7)
> Yes, I would guess that clang's "dumb" warning is fine for 99% of cases, and
> the handful of exceptions could use #pragma to disable the warning.
Or an attribute that says the opposite of nodiscard? (maydiscard? unused?)
>From gcc-bugs-return-629049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 07:11:40 2019
Return-Path: <gcc-bugs-return-629049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49742 invoked by alias); 14 Jan 2019 07:11: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 31576 invoked by uid 48); 14 Jan 2019 07:11:34 -0000
From: "wangchang15 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88831] New: the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Mon, 14 Jan 2019 07: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wangchang15 at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01858.txt.bz2
Content-length: 9135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88831
Bug ID: 88831
Summary: the layout of .data section of a binary is slightly
changed when -g option is enabled.
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: wangchang15 at huawei dot com
Target Milestone: ---
Dear all,
I use a little-endian cross compiler ( gcc7.3-based
build=host=x86_64-suse-linux target=aarch64-linux-gnu) to compile a C
application temp.c which is randomly generated by a CSmith tool.
To check whether the binaries are the same when compiling temp.c with and
without -g option, the following command is used.
/some/path/to/my/cross/compiler/aarch64-linux-gnu-gcc temp.c -static -O2 -I
./csmith/runtime -fcompare-debug=-g -lm -w -o ./temp_O2.exe
The result is an error message " error: temp.c: -fcompare-debug failure
(length)".
I checked the .data section in both binaries (with/without -g option), the
reason is that the position of an array variable (g_32) is changed. Because the
alignment requirement, different number of 0s are supplemented to this array
variable and another array variable g_1161 which leads to the length of .data
section in both binaries are different.
The disassembly fragment of .data section of both binaries are listed below.
The position of array variable g_32 is different in the two binaries.
I do not know whether this situation is normal or this could be some deeper
error.
Definitions of relative variables are listed as follows. All these variables
have initialized to non-zero values at the beginning of the C example.
static int8_t g_32[3][5][7];
static uint16_t g_1161;
static uint64_t g_97[5];
static int32_t g_132;
static int32_t g_562[4][3][6];
static int32_t ** volatile g_997;
static union U0 g_198[5];
.data section fragment 1st (without -g, with -O2):
++++++++++++++++++++++++++++++++++++++++++++++++++
temp_O2.exe: file format elf64-littleaarch64
Disassembly of section .data:
...
0000000000480070 <g_97>:
480070: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480080: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480090: ff ff ff ff ff ff ff ff ........
0000000000480098 <g_1161>:
480098: b1 bf 00 00 ....
000000000048009c <g_132>:
48009c: 01 00 00 00 ....
00000000004800a0 <g_562>:
4800a0: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4800b0: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4800c0: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
4800d0: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4800e0: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4800f0: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480100: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480110: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480120: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480130: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480140: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480150: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480160: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480170: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480180: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480190: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4801a0: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4801b0: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
00000000004801c0 <g_997>:
4801c0: 88 0d 48 00 00 00 00 00 ..H.....
00000000004801c8 <g_32>:
4801c8: cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06
...@......@.....
4801d8: 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40
.@......@......@
4801e8: 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01 06
......@......@..
4801f8: cc cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc
....@......@....
480208: 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01
..@......@......
480218: 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01
@......@......@.
480228: 06 cc cc 06 01 40 01 06 cc 00 00 00 00 00 00 00
.....@..........
0000000000480238 <g_198>:
480238: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480248: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480258: 9e b0 49 35 07 f7 e4 57 ..I5...W
...
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.data section fragment 2nd (with -g and -O2):
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
temp_O2_g.exe: file format elf64-littleaarch64
Disassembly of section .data:
...
0000000000480070 <g_97>:
480070: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480080: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480090: ff ff ff ff ff ff ff ff ........
0000000000480098 <g_32>:
480098: cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06
...@......@.....
4800a8: 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40
.@......@......@
4800b8: 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01 06
......@......@..
4800c8: cc cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc
....@......@....
4800d8: 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01
..@......@......
4800e8: 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01
@......@......@.
4800f8: 06 cc cc 06 01 40 01 06 cc 00 .....@....
0000000000480102 <g_1161>:
480102: b1 bf ..
0000000000480104 <g_132>:
480104: 01 00 00 00 ....
0000000000480108 <g_562>:
480108: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480118: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480128: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480138: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480148: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480158: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480168: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480178: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480188: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480198: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4801a8: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4801b8: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
4801c8: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4801d8: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4801e8: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
4801f8: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480208: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480218: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
0000000000480228 <g_997>:
480228: 80 0d 48 00 00 00 00 00 ..H.....
0000000000480230 <g_198>:
480230: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480240: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480250: 9e b0 49 35 07 f7 e4 57 ..I5...W
...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>From gcc-bugs-return-629050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 07:13:33 2019
Return-Path: <gcc-bugs-return-629050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63333 invoked by alias); 14 Jan 2019 07:13:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59154 invoked by uid 48); 14 Jan 2019 07:13:27 -0000
From: "wangchang15 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88832] New: the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Mon, 14 Jan 2019 07:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wangchang15 at huawei dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01859.txt.bz2
Content-length: 9135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88832
Bug ID: 88832
Summary: the layout of .data section of a binary is slightly
changed when -g option is enabled.
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: wangchang15 at huawei dot com
Target Milestone: ---
Dear all,
I use a little-endian cross compiler ( gcc7.3-based
build=host=x86_64-suse-linux target=aarch64-linux-gnu) to compile a C
application temp.c which is randomly generated by a CSmith tool.
To check whether the binaries are the same when compiling temp.c with and
without -g option, the following command is used.
/some/path/to/my/cross/compiler/aarch64-linux-gnu-gcc temp.c -static -O2 -I
./csmith/runtime -fcompare-debug=-g -lm -w -o ./temp_O2.exe
The result is an error message " error: temp.c: -fcompare-debug failure
(length)".
I checked the .data section in both binaries (with/without -g option), the
reason is that the position of an array variable (g_32) is changed. Because the
alignment requirement, different number of 0s are supplemented to this array
variable and another array variable g_1161 which leads to the length of .data
section in both binaries are different.
The disassembly fragment of .data section of both binaries are listed below.
The position of array variable g_32 is different in the two binaries.
I do not know whether this situation is normal or this could be some deeper
error.
Definitions of relative variables are listed as follows. All these variables
have initialized to non-zero values at the beginning of the C example.
static int8_t g_32[3][5][7];
static uint16_t g_1161;
static uint64_t g_97[5];
static int32_t g_132;
static int32_t g_562[4][3][6];
static int32_t ** volatile g_997;
static union U0 g_198[5];
.data section fragment 1st (without -g, with -O2):
++++++++++++++++++++++++++++++++++++++++++++++++++
temp_O2.exe: file format elf64-littleaarch64
Disassembly of section .data:
...
0000000000480070 <g_97>:
480070: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480080: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480090: ff ff ff ff ff ff ff ff ........
0000000000480098 <g_1161>:
480098: b1 bf 00 00 ....
000000000048009c <g_132>:
48009c: 01 00 00 00 ....
00000000004800a0 <g_562>:
4800a0: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4800b0: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4800c0: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
4800d0: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4800e0: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4800f0: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480100: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480110: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480120: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480130: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480140: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480150: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480160: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480170: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480180: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480190: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4801a0: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4801b0: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
00000000004801c0 <g_997>:
4801c0: 88 0d 48 00 00 00 00 00 ..H.....
00000000004801c8 <g_32>:
4801c8: cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06
...@......@.....
4801d8: 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40
.@......@......@
4801e8: 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01 06
......@......@..
4801f8: cc cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc
....@......@....
480208: 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01
..@......@......
480218: 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01
@......@......@.
480228: 06 cc cc 06 01 40 01 06 cc 00 00 00 00 00 00 00
.....@..........
0000000000480238 <g_198>:
480238: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480248: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480258: 9e b0 49 35 07 f7 e4 57 ..I5...W
...
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.data section fragment 2nd (with -g and -O2):
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
temp_O2_g.exe: file format elf64-littleaarch64
Disassembly of section .data:
...
0000000000480070 <g_97>:
480070: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480080: ff ff ff ff ff ff ff ff f6 ff ff ff ff ff ff ff
................
480090: ff ff ff ff ff ff ff ff ........
0000000000480098 <g_32>:
480098: cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06
...@......@.....
4800a8: 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40
.@......@......@
4800b8: 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01 06
......@......@..
4800c8: cc cc 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc
....@......@....
4800d8: 06 01 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01
..@......@......
4800e8: 40 01 06 cc cc 06 01 40 01 06 cc cc 06 01 40 01
@......@......@.
4800f8: 06 cc cc 06 01 40 01 06 cc 00 .....@....
0000000000480102 <g_1161>:
480102: b1 bf ..
0000000000480104 <g_132>:
480104: 01 00 00 00 ....
0000000000480108 <g_562>:
480108: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480118: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480128: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480138: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480148: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480158: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480168: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480178: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480188: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
480198: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4801a8: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4801b8: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
4801c8: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
4801d8: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
4801e8: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
4801f8: 01 00 00 00 a8 63 4b 59 cc 4f 0a a8 38 29 ad 89
.....cKY.O..8)..
480208: cc 4f 0a a8 a8 63 4b 59 01 00 00 00 a8 63 4b 59
.O...cKY.....cKY
480218: cc 4f 0a a8 38 29 ad 89 cc 4f 0a a8 a8 63 4b 59
.O..8)...O...cKY
0000000000480228 <g_997>:
480228: 80 0d 48 00 00 00 00 00 ..H.....
0000000000480230 <g_198>:
480230: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480240: 9e b0 49 35 07 f7 e4 57 01 00 00 00 00 00 00 00
..I5...W........
480250: 9e b0 49 35 07 f7 e4 57 ..I5...W
...
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>From gcc-bugs-return-629051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 08:19:00 2019
Return-Path: <gcc-bugs-return-629051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35928 invoked by alias); 14 Jan 2019 08:19:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30366 invoked by uid 55); 14 Jan 2019 08:18:56 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Mon, 14 Jan 2019 08:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-B9PgCuycjM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01860.txt.bz2
Content-length: 900
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #12 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 11 Jan 2019, msebor at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
>
> --- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
> I understand what jump threading does but I don't know enough about how it
> works to have a clear idea how viable marking up the created statements would
> be.
Jump threading just makes existing paths explicit, thus path sensitive
analysis would come up with similar answers. There may be cases where
we could prove such paths are unreachable and fail to do so, but the
cases where the path ends up in this kind of "undefined" builtin call
do not count IMHO because it is exactly those cases we want to warn
about - so we cannot really reason they cannot happen because of that.
>From gcc-bugs-return-629052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 08:40:14 2019
Return-Path: <gcc-bugs-return-629052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6573 invoked by alias); 14 Jan 2019 08:40: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 6452 invoked by uid 48); 14 Jan 2019 08:40:09 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Mon, 14 Jan 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-TtZjznBvfs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01861.txt.bz2
Content-length: 1112
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #8 from gnzlbg <gonzalobg88 at gmail dot com> ---
> I think it should be sufficient to either mention which types have padding bits,
I am not sure. An intrinsic that tells me that _Bool has 7 padding bits does
not provide me with any new information. The C standard guarantees that _Bool
has 1 value bit, so if `sizeof(_Bool)` returns N, then _Bool must have N *
CHAR_BITS - 1 padding bits AFAICT.
My question is which values are those padding bits allowed to take, which is
unspecified in the C standard AFAICT.
N1356 (http://www.open-std.org/jtc1/sc22/wg14/www/docs/n1356.htm) stated:
> GCC defines it to have one value bit with the other bits being padding bits and undefined behavior if you access a _Bool representation with any of the padding bits having a nonzero value (such representations being trap representations)
Documenting that this is how GCC defines the value that the padding bits in
_Bool are allowed to take would be an useful guarantee, even if the standard
does not require GCC to make this guarantee.
>From gcc-bugs-return-629053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 08:43:08 2019
Return-Path: <gcc-bugs-return-629053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120537 invoked by alias); 14 Jan 2019 08: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 113032 invoked by uid 48); 14 Jan 2019 08:43:03 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88831] the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Mon, 14 Jan 2019 08:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.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-88831-4-7TUrC6Or2k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01862.txt.bz2
Content-length: 179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88831
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
*** Bug 88832 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-629054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 08:43:08 2019
Return-Path: <gcc-bugs-return-629054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121357 invoked by alias); 14 Jan 2019 08: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 111636 invoked by uid 48); 14 Jan 2019 08:43:03 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88832] the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Mon, 14 Jan 2019 08:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88832-4-dfAEumx9xm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01863.txt.bz2
Content-length: 482
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88832
Andreas Schwab <schwab@linux-m68k.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Andreas Schwab <schwab@linux-m68k.org> ---
dup
*** This bug has been marked as a duplicate of bug 88831 ***
>From gcc-bugs-return-629055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 08:49:44 2019
Return-Path: <gcc-bugs-return-629055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30958 invoked by alias); 14 Jan 2019 08:49:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22703 invoked by uid 48); 14 Jan 2019 08:49:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85368] [8 regression] phi-opt-11 test fails on IBM Z
Date: Mon, 14 Jan 2019 08:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85368-4-krcl14k5Dt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85368-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85368-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01864.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85368
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yes. It is a developer only knob which can go away at any time.
>From gcc-bugs-return-629056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 08:54:07 2019
Return-Path: <gcc-bugs-return-629056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14736 invoked by alias); 14 Jan 2019 08:54: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 3351 invoked by uid 48); 14 Jan 2019 08:54:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Mon, 14 Jan 2019 08:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-1JVQyGHjPw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01865.txt.bz2
Content-length: 1412
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #12)
> On Fri, 11 Jan 2019, msebor at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
> >
> > --- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
> > I understand what jump threading does but I don't know enough about how it
> > works to have a clear idea how viable marking up the created statements would
> > be.
>
> Jump threading just makes existing paths explicit, thus path sensitive
> analysis would come up with similar answers. There may be cases where
> we could prove such paths are unreachable and fail to do so, but the
> cases where the path ends up in this kind of "undefined" builtin call
> do not count IMHO because it is exactly those cases we want to warn
> about - so we cannot really reason they cannot happen because of that.
Sure, but the warnings we are talking about typically don't warn about calls
(etc.) that can overflow, but nothing is known about the value ranges of those
arguments. Because then we'd need to warn about void foo (char *x, char *y,
unsigned long z) { __builtin_strncpy (x, y, z); } which indeed can overflow if
user passes wrong arguments. We'd just warn all the time about that though and
the warning wouldn't be useful at all.
>From gcc-bugs-return-629057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:01:24 2019
Return-Path: <gcc-bugs-return-629057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81832 invoked by alias); 14 Jan 2019 09:01: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 80809 invoked by uid 48); 14 Jan 2019 09:01:11 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Mon, 14 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80762-4-dHzXNTqt7I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01866.txt.bz2
Content-length: 658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tnfchris at gcc dot gnu.org
--- Comment #7 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hello, I'm now seeing the following failure on GCC 8
/src/gcc/libstdc++-v3/testsuite/experimental/filesystem/path/construct/80762.cc:20:
fatal error: experimental/filesystem: No such file or directory
compilation terminated.
On both arm and aarch64 cross builds.
>From gcc-bugs-return-629058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:01:57 2019
Return-Path: <gcc-bugs-return-629058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125826 invoked by alias); 14 Jan 2019 09:01: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 116427 invoked by uid 48); 14 Jan 2019 09:01:53 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Mon, 14 Jan 2019 09:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-ICwWCSkn6y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01867.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #12 from prathamesh3492 at gcc dot gnu.org ---
(In reply to Jakub Jelinek from comment #11)
> Look e.g. at -O2:
> void bar (int);
>
> void
> foo (int x)
> {
> int i = 0;
> if (x == 8)
> {
> x = 16;
> goto lab;
> }
> for (; i < 100; i++)
> {
> lab:
> bar (x);
> }
> }
>
> but pretty much any time you have a loop where some var doesn't really
> change, but there is some other edge to the loop header with a different
> value for that var.
Ah indeed.
Thanks for the explanation!
>From gcc-bugs-return-629059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:14:25 2019
Return-Path: <gcc-bugs-return-629059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124586 invoked by alias); 14 Jan 2019 09:14: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 124517 invoked by uid 48); 14 Jan 2019 09:14:20 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Mon, 14 Jan 2019 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80762-4-R0zxCwYjoJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01868.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I forgot the dg-require-filesystem-ts again.
>From gcc-bugs-return-629060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:31:17 2019
Return-Path: <gcc-bugs-return-629060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95128 invoked by alias); 14 Jan 2019 09:31:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94267 invoked by uid 48); 14 Jan 2019 09:30:51 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88510] GCC generates inefficient U64x2/v2di scalar multiply for NEON32
Date: Mon, 14 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-88510-4-poDQNctUFp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01869.txt.bz2
Content-length: 1157
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88510
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target|armv7-a |arm, aarch64
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |ramana at gcc dot gnu.org
Target Milestone|--- |10.0
Ever confirmed|0 |1
--- Comment #3 from Ramana Radhakrishnan <ramana at gcc dot gnu.org> ---
We are in stage4 at this point of time and a patch for this between now and
when GCC9 releases isn't appropriate (i.e. April). Hopefully someone will pick
this up afterwards for both backends as the logic required for the expansion
should be pretty much identical give or take backend integration issues.
Though I wonder if this is better handled in the fall back path for expansion
of v2di multiplications instead of duplicating this logic in both arm and
aarch64 backends.
>From gcc-bugs-return-629061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:32:19 2019
Return-Path: <gcc-bugs-return-629061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104353 invoked by alias); 14 Jan 2019 09:32: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 101695 invoked by uid 48); 14 Jan 2019 09:32:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88797] [7/8/9 Regression] Unneeded branch added when function is inlined (function runs faster if not inlined)
Date: Mon, 14 Jan 2019 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88797-4-TsDU0JPb2d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01870.txt.bz2
Content-length: 1090
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88797
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |law at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Target Milestone|--- |7.5
Summary|Unneeded branch added when |[7/8/9 Regression] Unneeded
|function is inlined |branch added when function
|(function runs faster if |is inlined (function runs
|not inlined) |faster if not inlined)
Ever confirmed|0 |1
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
It's path splitting again. -fno-split-paths works around this.
>From gcc-bugs-return-629062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:36:08 2019
Return-Path: <gcc-bugs-return-629062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9829 invoked by alias); 14 Jan 2019 09:36: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 9744 invoked by uid 48); 14 Jan 2019 09:36:02 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88798] AVX512BW code does not use bit-operations that work on mask registers
Date: Mon, 14 Jan 2019 09:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.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 cf_gcctarget bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88798-4-Frn34HKqXs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88798-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01871.txt.bz2
Content-length: 694
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88798
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |x86_64-*-*, i?86-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
Ever confirmed|0 |1
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
The testcase still behaves the same on trunk, not sure if exactly a dup or not.
>From gcc-bugs-return-629063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:38:16 2019
Return-Path: <gcc-bugs-return-629063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11763 invoked by alias); 14 Jan 2019 09:38: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 11695 invoked by uid 48); 14 Jan 2019 09:38:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88799] [8/9 Regression] Arm -mcpu=PROCESSOR does not result in assembly directives for .arch and .arch_extension
Date: Mon, 14 Jan 2019 09:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88799-4-oABkOqpbGn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88799-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88799-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01872.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88799
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.3
>From gcc-bugs-return-629064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:39:23 2019
Return-Path: <gcc-bugs-return-629064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13302 invoked by alias); 14 Jan 2019 09:39:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13210 invoked by uid 48); 14 Jan 2019 09:39:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88801] [9 Regression] Performance regression on 473.astar on aarch64
Date: Mon, 14 Jan 2019 09:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88801-4-2tPfPj8lNV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01873.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88801
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-629065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:44:37 2019
Return-Path: <gcc-bugs-return-629065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4004 invoked by alias); 14 Jan 2019 09: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 3869 invoked by uid 55); 14 Jan 2019 09:44:31 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88771] [9 Regression] Misleading -Werror=array-bounds error
Date: Mon, 14 Jan 2019 09:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88771-4-RQ59ceXUrK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01874.txt.bz2
Content-length: 1910
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
--- Comment #14 from rguenther at suse dot de <rguenther at suse dot de> ---
On Mon, 14 Jan 2019, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
>
> --- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
> (In reply to rguenther@suse.de from comment #12)
> > On Fri, 11 Jan 2019, msebor at gcc dot gnu.org wrote:
> >
> > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88771
> > >
> > > --- Comment #11 from Martin Sebor <msebor at gcc dot gnu.org> ---
> > > I understand what jump threading does but I don't know enough about how it
> > > works to have a clear idea how viable marking up the created statements would
> > > be.
> >
> > Jump threading just makes existing paths explicit, thus path sensitive
> > analysis would come up with similar answers. There may be cases where
> > we could prove such paths are unreachable and fail to do so, but the
> > cases where the path ends up in this kind of "undefined" builtin call
> > do not count IMHO because it is exactly those cases we want to warn
> > about - so we cannot really reason they cannot happen because of that.
>
> Sure, but the warnings we are talking about typically don't warn about calls
> (etc.) that can overflow, but nothing is known about the value ranges of those
> arguments. Because then we'd need to warn about void foo (char *x, char *y,
> unsigned long z) { __builtin_strncpy (x, y, z); } which indeed can overflow if
> user passes wrong arguments. We'd just warn all the time about that though and
> the warning wouldn't be useful at all.
Well, the question is then whether you want to live with false negatives
or false positives... I thought from all the attempts to prevent
early folding that we rather want false positives. Otherwise just
fold all undefined stuff to __builtin_trap().
>From gcc-bugs-return-629066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:45:59 2019
Return-Path: <gcc-bugs-return-629066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5869 invoked by alias); 14 Jan 2019 09:45: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 5296 invoked by uid 48); 14 Jan 2019 09:45:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Mon, 14 Jan 2019 09:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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-88738-4-BkgkIbZggP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01875.txt.bz2
Content-length: 336
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The standard maybe_unused attribute seems suitable. If an equality or
relational operator function has that attribute, don't warn if its result is
unused.
So weird operators with side effects can use the attribute.
>From gcc-bugs-return-629067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:46:44 2019
Return-Path: <gcc-bugs-return-629067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6990 invoked by alias); 14 Jan 2019 09:46: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 6768 invoked by uid 48); 14 Jan 2019 09:46:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Mon, 14 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-FuNBO2O3zW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01876.txt.bz2
Content-length: 192
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But it constrains GCC in future, which leaving it unspecified does not.
>From gcc-bugs-return-629068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:50:36 2019
Return-Path: <gcc-bugs-return-629068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10619 invoked by alias); 14 Jan 2019 09: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 10570 invoked by uid 48); 14 Jan 2019 09:50:31 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88805] hidden symbol `__cpu_model' is referenced by DSO
Date: Mon, 14 Jan 2019 09:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88805-4-PtDz6dFN3U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01877.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
It works for me (glibc 2.22).
Can you quote the linker command-line (add -v to the compiler command)?
>From gcc-bugs-return-629069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 09:59:32 2019
Return-Path: <gcc-bugs-return-629069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3812 invoked by alias); 14 Jan 2019 09:59:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3759 invoked by uid 48); 14 Jan 2019 09:59:26 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88833] New: [SVE] Redundant moves for WHILELO-based loops
Date: Mon, 14 Jan 2019 09:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01878.txt.bz2
Content-length: 1304
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88833
Bug ID: 88833
Summary: [SVE] Redundant moves for WHILELO-based loops
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Compiling this function with -O3 -march=armv8-a+sve:
subroutine foo(x, y, z)
real :: x(100), y(100), z(100)
x = y + z(1)
end subroutine foo
gives:
foo_:
.LFB0:
.cfi_startproc
mov x4, 100
mov x5, x4 // Redundant
mov x3, 0
ptrue p1.s, all
whilelo p0.s, xzr, x4
ld1rw z1.s, p1/z, [x2]
.p2align 3,,7
.L2:
ld1w z0.s, p0/z, [x1, x3, lsl 2]
fadd z0.s, z0.s, z1.s
st1w z0.s, p0, [x0, x3, lsl 2]
incw x3
whilelo p0.s, x3, x5
bne .L2
ret
.cfi_endproc
There's no need for the move here. We should just be able to use x4 for both
WHILELOs.
Although the move itself shouldn't be expensive in context, it suggests that
the RA isn't seeing an accurate picture, which could hurt in more complex
cases.
>From gcc-bugs-return-629070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:03:29 2019
Return-Path: <gcc-bugs-return-629070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14071 invoked by alias); 14 Jan 2019 10:03: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 13998 invoked by uid 48); 14 Jan 2019 10:03:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88818] Segfault with vtable-verify LTO optimization
Date: Mon, 14 Jan 2019 10:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc component
Message-ID: <bug-88818-4-LtqgoNzs09@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01879.txt.bz2
Content-length: 724
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88818
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |lto
CC| |hubicka at gcc dot gnu.org,
| |marxin at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Component|c++ |ipa
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think VTV is just bit-rotten seriously and it likely never worked with LTO.
>From gcc-bugs-return-629071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:04:57 2019
Return-Path: <gcc-bugs-return-629071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26785 invoked by alias); 14 Jan 2019 10: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 26732 invoked by uid 48); 14 Jan 2019 10:04:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88821] Inline packing of non-contiguous arguments
Date: Mon, 14 Jan 2019 10:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88821-4-7P48XnSSyw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01880.txt.bz2
Content-length: 553
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88821
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-629072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:13:56 2019
Return-Path: <gcc-bugs-return-629072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88160 invoked by alias); 14 Jan 2019 10:13: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 88125 invoked by uid 48); 14 Jan 2019 10:13:51 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88823] ivopts introduces -1(OVF)
Date: Mon, 14 Jan 2019 10:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-88823-4-ac2i60dykZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01881.txt.bz2
Content-length: 1939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88823
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The flag is usually harmless and might only result in missed optimizations down
the road. At some point it caused VRP to ICE eventually. One -1(OVF) is
built here:
#4 0x000000000137f9d2 in get_computation_aff_1 (loop=0x7ffff6888ee0, at=
<gimple_cond 0x7ffff69cb280>, use=0x31d8e00, cand=0x31d8f90,
aff_inv=0x7fffffffd130, aff_var=0x7fffffffd2f0, prat=0x7fffffffd100)
at /space/rguenther/src/gcc-sccvn/gcc/tree-ssa-loop-ivopts.c:3947
(gdb) l
3942 if (stmt_after_increment (loop, cand, at))
3943 {
3944 aff_tree cstep_aff;
3945
3946 if (common_type != uutype)
3947 cstep_common = fold_convert (common_type, cstep);
where cstep is 4294967295 and common_type is int. That's probably harmless
as we just feed it back to tree-affine. Then there's
#4 0x0000000001383a5a in may_eliminate_iv (data=0x7fffffffd810,
use=0x31d8e00, cand=0x31d90b0, bound=0x7fffffffd638, comp=0x7fffffffd5c4)
at /space/rguenther/src/gcc-sccvn/gcc/tree-ssa-loop-ivopts.c:5147
5147 *bound = fold_convert (TREE_TYPE (cand->iv->base),
(gdb) l
5142 }
5143 }
5144
5145 cand_value_at (loop, cand, use->stmt, desc->niter, &bnd);
5146
5147 *bound = fold_convert (TREE_TYPE (cand->iv->base),
5148 aff_combination_to_tree (&bnd));
where a similar issue happens (unsigned -> signed convert). This is the
one ending up in the IL.
>From gcc-bugs-return-629073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:21:37 2019
Return-Path: <gcc-bugs-return-629073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112696 invoked by alias); 14 Jan 2019 10:21:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112656 invoked by uid 48); 14 Jan 2019 10:21:32 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88834] New: [SVE] Poor addressing mode choices for LD2 and ST2
Date: Mon, 14 Jan 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01882.txt.bz2
Content-length: 1806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88834
Bug ID: 88834
Summary: [SVE] Poor addressing mode choices for LD2 and ST2
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Compiling this code with -O3 -march=armv8-a+sve:
void
f (int *restrict x, int *restrict y, int *restrict z, int n)
{
for (int i = 0; i < n; i += 2)
{
x[i] = y[i] + z[i];
x[i + 1] = y[i + 1] - z[i + 1];
}
}
gives:
f:
.LFB0:
.cfi_startproc
cmp w3, 0
ble .L1
sub w4, w3, #1
cntw x3
ptrue p1.s, all
lsr w4, w4, 1
add w4, w4, 1
whilelo p0.s, xzr, x4
.p2align 3,,7
.L3:
ld2w {z4.s - z5.s}, p0/z, [x1]
ld2w {z2.s - z3.s}, p0/z, [x2]
add z0.s, z4.s, z2.s
sub z1.s, z5.s, z3.s
st2w {z0.s - z1.s}, p0, [x0]
incb x1, all, mul #2
whilelo p0.s, x3, x4
incb x0, all, mul #2
incb x2, all, mul #2
incw x3
ptest p1, p0.b
bne .L3
.L1:
ret
.cfi_endproc
Rather than have one INCB per address, we should have a single IV
that tracks the index, something like:
ld2w {z4.s - z5.s}, p0/z, [x1, x4, lsl #2]
ld2w {z2.s - z3.s}, p0/z, [x2, x4, lsl #2]
add z0.s, z4.s, z2.s
sub z1.s, z5.s, z3.s
st2w {z0.s - z1.s}, p0, [x0, x4, lsl #2]
incw x4, all, mul #2 // or inch
I think this will need work in both the target code and ivopts.
>From gcc-bugs-return-629074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:22:35 2019
Return-Path: <gcc-bugs-return-629074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113740 invoked by alias); 14 Jan 2019 10:22:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113667 invoked by uid 48); 14 Jan 2019 10:22:30 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Mon, 14 Jan 2019 10:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-Ts2CCuFFyi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01883.txt.bz2
Content-length: 1253
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #10 from gnzlbg <gonzalobg88 at gmail dot com> ---
> But it constrains GCC in future, which leaving it unspecified does not.
Documenting whether GCC's C _Bool has the same valid and trap representations
as the target platform's ABI specifies is a trade-off: it does have a cost as
you said, but it also adds value.
The question is whether this trade-off is worth it.
I am not a compiler expert, but using the same representation of _Bool as the
platform's ABI allows GCC to avoid conversions on function arguments, return
values, and when passing _Bools through memory. It appears to me that GCC would
want to avoid doing these conversions anyways. An alternative here would be to,
instead of guaranteeing this behavior, document the current behavior with a
disclaimer that the behavior can change. So the cost of documenting this could
be kept fairly small.
Value-wise, if I want to cast an array of char to an array of _Bool, this
guarantee allows me to check whether doing so will introduce undefined
behavior, which I think is very valuable.
So from my pov, documenting current behavior without guaranteeing it has almost
zero cost, and adds a lot of value.
>From gcc-bugs-return-629076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:23:58 2019
Return-Path: <gcc-bugs-return-629076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121648 invoked by alias); 14 Jan 2019 10:23: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 120991 invoked by uid 48); 14 Jan 2019 10:23:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88828] Inefficient update of the first element of vector registers
Date: Mon, 14 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88828-4-9ZXJyp2G5i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01885.txt.bz2
Content-length: 1508
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88828
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think there's related bugs. foo1 is optimized OK:
y_4 = BIT_INSERT_EXPR <x_2(D), f_3(D), 0 (32 bits)>;
return y_4;
while foo is expanded from
<bb 2> [local count: 1073741824]:
_1 = BIT_FIELD_REF <x_7(D), 32, 32>;
_2 = BIT_FIELD_REF <x_7(D), 32, 64>;
_3 = BIT_FIELD_REF <x_7(D), 32, 96>;
y_6 = {f_5(D), _1, _2, _3};
return y_6;
tree forwprop contains code pattern-matching on vector CONSTRUCTORs,
it could be extended to handle this case I think. IIRC it can detect
arbitrary two-vector permutes already, for the above we could go
through an intermediate
_1 = {f_5(D), f_5(D), ... };
y_6 = VEC_PERM <_1, x_7(D), { .... }>;
and recognize permutes that only replace a single vector element.
So I think we should optimize
__v4sf
foo (__v4sf x, float f)
{
__v4sf y = __extension__ (__v4sf)
{ f, x[2], x[1], x[3] };
return y;
}
as well, first permuting x and then inserting f (at any position).
>From gcc-bugs-return-629075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:23:29 2019
Return-Path: <gcc-bugs-return-629075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120038 invoked by alias); 14 Jan 2019 10:23: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 119996 invoked by uid 48); 14 Jan 2019 10:23:24 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88833] [SVE] Redundant moves for WHILELO-based loops
Date: Mon, 14 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88833-4-h3OqobOBui@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01884.txt.bz2
Content-length: 689
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88833
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |aarch64
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |ktkachov at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed. I see the redundant move as well.
>From gcc-bugs-return-629078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:25:43 2019
Return-Path: <gcc-bugs-return-629078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24283 invoked by alias); 14 Jan 2019 10:25: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 19921 invoked by uid 48); 14 Jan 2019 10:25:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88835] [9 Regression] Maybe misleading -Werror=format-overflow since r265648
Date: Mon, 14 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on cf_known_to_work see_also target_milestone cf_known_to_fail
Message-ID: <bug-88835-4-JISHFcsC1Z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01887.txt.bz2
Content-length: 619
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88835
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2019-1-14
Known to work| |8.2.0
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=24068
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-629077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:25:21 2019
Return-Path: <gcc-bugs-return-629077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13339 invoked by alias); 14 Jan 2019 10:25:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 13077 invoked by uid 48); 14 Jan 2019 10:25:03 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88835] New: [9 Regression] Maybe misleading -Werror=format-overflow since r265648
Date: Mon, 14 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost attachments.created
Message-ID: <bug-88835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01886.txt.bz2
Content-length: 1267
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88835
Bug ID: 88835
Summary: [9 Regression] Maybe misleading
-Werror=format-overflow since r265648
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: msebor at gcc dot gnu.org
Target Milestone: ---
Host: i586-linux-gnu
Created attachment 45424
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45424&action=edit
test-case
I originally reported that to elfutils bugzilla.
The warning looks as follows:
$ gcc -m32 /tmp/readelf.i -c -O2 -Werror=format-overflow
readelf.c: In function ‘print_debug_str_section’:
readelf.c:10152:15: error: ‘%*llx’ directive output between 4 and 2147483647
bytes may cause result to exceed ‘INT_MAX’ [-Werror=format-overflow=]
10152 | printf (" [%*" PRIx64 "] \"%s\"\n", digits, (uint64_t) offset,
str);
| ^~~~~~
readelf.c:10152:15: note: directive argument in the range [0,
18446744073709551614]
>From gcc-bugs-return-629079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:25:47 2019
Return-Path: <gcc-bugs-return-629079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24849 invoked by alias); 14 Jan 2019 10:25:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24286 invoked by uid 48); 14 Jan 2019 10:25:42 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] [9 Regression] ice in maybe_emit_vtables
Date: Mon, 14 Jan 2019 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority version
Message-ID: <bug-88830-4-MqNtkrNLAS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01888.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Version|8.0 |9.0
>From gcc-bugs-return-629080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:29:03 2019
Return-Path: <gcc-bugs-return-629080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29473 invoked by alias); 14 Jan 2019 10:29: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 29385 invoked by uid 48); 14 Jan 2019 10:28:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88831] the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Mon, 14 Jan 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_reconfirmed_on cf_gcchost everconfirmed
Message-ID: <bug-88831-4-c2pgd03N3s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01889.txt.bz2
Content-length: 679
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88831
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |aarch64-linux-gnu
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-14
Host| |x86_64-suse-linux
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
This shouldn't happen. Can you please provide a complete testcase?
>From gcc-bugs-return-629081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:29:37 2019
Return-Path: <gcc-bugs-return-629081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32053 invoked by alias); 14 Jan 2019 10:29: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 31989 invoked by uid 48); 14 Jan 2019 10:29:33 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88834] [SVE] Poor addressing mode choices for LD2 and ST2
Date: Mon, 14 Jan 2019 10:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88834-4-UkEwYstngS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01890.txt.bz2
Content-length: 655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88834
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |aarch64
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |ktkachov at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed.
>From gcc-bugs-return-629082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:34:25 2019
Return-Path: <gcc-bugs-return-629082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63365 invoked by alias); 14 Jan 2019 10:34: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 63221 invoked by uid 48); 14 Jan 2019 10:34:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Mon, 14 Jan 2019 10:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88815-4-H8Z5lT66Dr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01891.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I believe it is the
@@ -25361,7 +25486,10 @@
return NULL_TREE;
case TEMPLATE_PARM_INDEX:
- return *tp;
+ if (dependent_type_p (TREE_TYPE (*tp)))
+ return *tp;
+ /* We'll check value-dependence separately. */
+ return NULL_TREE;
/* Handle expressions with type operands. */
case SIZEOF_EXPR:
pt.c (instantiation_dependent_r) hunk that matters for this testcase, at least
reverting it makes the testcase succeed.
>From gcc-bugs-return-629083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:46:30 2019
Return-Path: <gcc-bugs-return-629083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55802 invoked by alias); 14 Jan 2019 10:46: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 55086 invoked by uid 48); 14 Jan 2019 10:46:25 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88836] New: [SVE] Redundant PTEST in loop test
Date: Mon, 14 Jan 2019 10:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01892.txt.bz2
Content-length: 1509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88836
Bug ID: 88836
Summary: [SVE] Redundant PTEST in loop test
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Compiling this code with -O3 -march=armv8-a+sve:
void
f (int *restrict x, int *restrict y, int *restrict z, int n)
{
for (int i = 0; i < n; i += 2)
{
x[i] = y[i] + z[i];
x[i + 1] = y[i + 1] - z[i + 1];
}
}
gives:
f:
.LFB0:
.cfi_startproc
cmp w3, 0
ble .L1
sub w4, w3, #1
cntw x3
ptrue p1.s, all
lsr w4, w4, 1
add w4, w4, 1
whilelo p0.s, xzr, x4
.p2align 3,,7
.L3:
ld2w {z4.s - z5.s}, p0/z, [x1]
ld2w {z2.s - z3.s}, p0/z, [x2]
add z0.s, z4.s, z2.s
sub z1.s, z5.s, z3.s
st2w {z0.s - z1.s}, p0, [x0]
incb x1, all, mul #2
whilelo p0.s, x3, x4
incb x0, all, mul #2
incb x2, all, mul #2
incw x3
ptest p1, p0.b
bne .L3
.L1:
ret
.cfi_endproc
PR88834 is tracking the poor addressing mode choices. But there's also no need
for that PTEST. We should be able to use the flags set by the WHILELO
directly.
>From gcc-bugs-return-629084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:53:32 2019
Return-Path: <gcc-bugs-return-629084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119715 invoked by alias); 14 Jan 2019 10:53:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119654 invoked by uid 48); 14 Jan 2019 10:53:27 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88836] [SVE] Redundant PTEST in loop test
Date: Mon, 14 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cf_gcctarget bug_status cf_reconfirmed_on cc version everconfirmed
Message-ID: <bug-88836-4-fBLDdhaMxT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01893.txt.bz2
Content-length: 708
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88836
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |aarch64
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |ktkachov at gcc dot gnu.org
Version|unknown |9.0
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed.
>From gcc-bugs-return-629085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 10:59:56 2019
Return-Path: <gcc-bugs-return-629085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20459 invoked by alias); 14 Jan 2019 10:59:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17818 invoked by uid 48); 14 Jan 2019 10:59:51 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Mon, 14 Jan 2019 10:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88788-4-lQvWOwpFWu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01894.txt.bz2
Content-length: 2122
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #13 from Richard Biener <rguenth at gcc dot gnu.org> ---
I think that using a bitmap to mark SSA names already visited and return
true on those would work as well given returning false should (quickly)
propagate.
thus
diff --git a/gcc/ipa-pure-const.c b/gcc/ipa-pure-const.c
index 37b58853fe1..e14394e9853 100644
--- a/gcc/ipa-pure-const.c
+++ b/gcc/ipa-pure-const.c
@@ -878,10 +878,14 @@ check_retval_uses (tree retval, gimple *stmt)
}
static bool
-malloc_candidate_p_1 (function *fun, tree retval, gimple *ret_stmt, bool ipa)
+malloc_candidate_p_1 (function *fun, tree retval, gimple *ret_stmt, bool ipa,
+ bitmap visited)
{
cgraph_node *node = cgraph_node::get_create (fun->decl);
+ if (!bitmap_set_bit (visited, SSA_NAME_VERSION (retval)))
+ return true;
+
if (!check_retval_uses (retval, ret_stmt))
DUMP_AND_RETURN("Return value has uses outside return stmt"
" and comparisons against 0.")
@@ -925,7 +929,7 @@ malloc_candidate_p_1 (function *fun, tree retval, gimple
*ret_stmt, bool ipa)
gimple *arg_def = SSA_NAME_DEF_STMT (arg);
if (is_a<gphi *> (arg_def))
{
- if (!malloc_candidate_p_1 (fun, arg, phi, ipa))
+ if (!malloc_candidate_p_1 (fun, arg, phi, ipa, visited))
DUMP_AND_RETURN ("nested phi fail")
continue;
}
@@ -987,7 +991,8 @@ malloc_candidate_p (function *fun, bool ipa)
|| TREE_CODE (TREE_TYPE (retval)) != POINTER_TYPE)
DUMP_AND_RETURN("Return value is not SSA_NAME or not a pointer type.")
- if (!malloc_candidate_p_1 (fun, retval, ret_stmt, ipa))
+ auto_bitmap visited;
+ if (!malloc_candidate_p_1 (fun, retval, ret_stmt, ipa, visited))
return false;
}
>From gcc-bugs-return-629086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:06:04 2019
Return-Path: <gcc-bugs-return-629086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42057 invoked by alias); 14 Jan 2019 11:06: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 41949 invoked by uid 48); 14 Jan 2019 11:05:59 -0000
From: "plasmahh at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88761] [8/9 Regression] ICE in tsubst_copy, at cp/pt.c:15478 when chaining lambda calls & fold-expressions
Date: Mon, 14 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: plasmahh at gmx dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88761-4-b2LntI2vo0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88761-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01895.txt.bz2
Content-length: 907
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88761
Dennis Lubert <plasmahh at gmx dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |plasmahh at gmx dot net
--- Comment #3 from Dennis Lubert <plasmahh at gmx dot net> ---
I was just about to report the same bug (internal compiler error: in
tsubst_copy, at cp/pt.c:15478) but with different code, maybe this can shed
more light on why it is happening, if not, just ignore it:
#include <vector>
#include <cstdint>
#include <cstddef>
int main(int argc, const char *argv[])
{
const size_t nf = 10'000'000;
auto loop = [&]( auto& vector )
{
long double cy = 0;
auto per = cy/nf;
};
std::vector<int> pv;
loop( pv );
}
>From gcc-bugs-return-629088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:10:21 2019
Return-Path: <gcc-bugs-return-629088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122843 invoked by alias); 14 Jan 2019 11:10: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 122752 invoked by uid 48); 14 Jan 2019 11:10:16 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88837] [SVE] Poor vector construction code in VL-specific mode
Date: Mon, 14 Jan 2019 11:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-88837-4-acdf3EfzEO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01897.txt.bz2
Content-length: 315
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88837
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
>From gcc-bugs-return-629087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:10:05 2019
Return-Path: <gcc-bugs-return-629087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121961 invoked by alias); 14 Jan 2019 11:10:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121842 invoked by uid 48); 14 Jan 2019 11:10:00 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88837] New: [SVE] Poor vector construction code in VL-specific mode
Date: Mon, 14 Jan 2019 11:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01896.txt.bz2
Content-length: 1963
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88837
Bug ID: 88837
Summary: [SVE] Poor vector construction code in VL-specific
mode
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
The reduction testcases in gcc.target/aarch64/sve/slp_5.c require an initial
vector in which all elements except the first two are zero. For the default
VL-agnostic mode we generate reasonable code, e.g.:
vec_slp_int32_t:
.LFB4:
.cfi_startproc
ldp s2, s1, [x1]
cmp w2, 0
ble .L19
mov x3, 0
sbfiz x2, x2, 1, 32
mov z0.b, #0
whilelo p0.s, xzr, x2
insr z0.s, s1
ptrue p1.s, all
insr z0.s, s2
.p2align 3,,7
.L20:
ld1w z1.s, p0/z, [x0, x3, lsl 2]
incw x3
add z0.s, p0/m, z0.s, z1.s
whilelo p0.s, x3, x2
bne .L20
But with -msve-vector-bits=256 the code is much worse:
vec_slp_int32_t:
.LFB4:
.cfi_startproc
ldp w5, w4, [x1]
cmp w2, 0
ble .L31
sub sp, sp, #32
.cfi_def_cfa_offset 32
mov z0.b, #0
str z0, [sp]
mov x3, 0
sbfiz x2, x2, 1, 32
whilelo p0.s, xzr, x2
ldr x6, [sp]
bfi x6, x5, 0, 32
mov x5, x6
bfi x5, x4, 32, 32
str x5, [sp]
ldr z0, [sp]
.p2align 3,,7
.L28:
ld1w z1.s, p0/z, [x0, x3, lsl 2]
add x3, x3, 8
add z0.s, p0/m, z0.s, z1.s
whilelo p0.s, x3, x2
bne .L28
We should try to optimise this, probably by implementing vec_init_optab for
fixed-length vectors.
>From gcc-bugs-return-629089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:31:06 2019
Return-Path: <gcc-bugs-return-629089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30032 invoked by alias); 14 Jan 2019 11:31:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29730 invoked by uid 48); 14 Jan 2019 11:30:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Mon, 14 Jan 2019 11:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80762-4-uVUNZCajAE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01898.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Should be fixed now.
>From gcc-bugs-return-629090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:31:47 2019
Return-Path: <gcc-bugs-return-629090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31327 invoked by alias); 14 Jan 2019 11:31:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31223 invoked by uid 55); 14 Jan 2019 11:31:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Mon, 14 Jan 2019 11:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80762-4-p4Ku0JtxRd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01899.txt.bz2
Content-length: 626
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon Jan 14 11:30:47 2019
New Revision: 267915
URL: https://gcc.gnu.org/viewcvs?rev=267915&root=gcc&view=rev
Log:
PR libstdc++/80762 add missing dg-require-filesystem-ts
PR libstdc++/80762
* testsuite/experimental/filesystem/path/construct/80762.cc: Add
dg-require-filesystem-ts directive.
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/testsuite/experimental/filesystem/path/construct/80762.cc
>From gcc-bugs-return-629091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:42:21 2019
Return-Path: <gcc-bugs-return-629091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36361 invoked by alias); 14 Jan 2019 11:42:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35716 invoked by uid 48); 14 Jan 2019 11:42:15 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Mon, 14 Jan 2019 11:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88788-4-lgPXXH9NnZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01900.txt.bz2
Content-length: 776
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #14 from prathamesh3492 at gcc dot gnu.org ---
Created attachment 45425
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45425&action=edit
Patch
Hi,
In the attached patch, I cache results of malloc_candidate_p_1 and avoid
traversing "back edges".
Does it look OK ?
One issue was with creation of hash_table:
hash_table<mc_map_elem_t> *mc_cache = new hash_table<mc_map_elem_t> (100);
Using num_ssa_names instead of 100 resulted in allocation failure (and ICE)
for spinning-smaller.ii.
Is using a smaller number like 100 OK correctness wise ?
I think Richard's patch in comment 13 is a better approach, since returning
false should indeed propagate quickly. Testing that patch.
Thanks,
Prathamesh
>From gcc-bugs-return-629092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:43:15 2019
Return-Path: <gcc-bugs-return-629092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77360 invoked by alias); 14 Jan 2019 11:43:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71802 invoked by uid 48); 14 Jan 2019 11:43:10 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88838] New: [SVE] Use 32-bit WHILELO in LP64 mode
Date: Mon, 14 Jan 2019 11:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01901.txt.bz2
Content-length: 1751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88838
Bug ID: 88838
Summary: [SVE] Use 32-bit WHILELO in LP64 mode
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Compiling this test with -O3 -march=armv8-a+sve:
void
f (int *restrict x, int *restrict y, int *restrict z, int n)
{
for (int i = 0; i < n; i += 1)
x[i] = y[i] + z[i];
}
produces:
f:
.LFB0:
.cfi_startproc
cmp w3, 0
ble .L1
mov x4, 0
sxtw x3, w3
whilelo p0.s, xzr, x3
.p2align 3,,7
.L3:
ld1w z1.s, p0/z, [x1, x4, lsl 2]
ld1w z0.s, p0/z, [x2, x4, lsl 2]
add z0.s, z0.s, z1.s
st1w z0.s, p0, [x0, x4, lsl 2]
incw x4
whilelo p0.s, x4, x3
bne .L3
.L1:
ret
We could (and should) avoid the SXTW by using WHILELO on W registers instead of
X registers.
vect_verify_full_masking checks which IV widths are supported for WHILELO but
prefers to go to Pmode width. This is because using Pmode allows ivopts to
reuse the IV for indices (as in the loads and store above). However, it would
be better to use a 32-bit WHILELO with a truncated 64-bit IV if:
(a) the limit is extended from 32 bits.
(b) the detection loop in vect_verify_full_masking detects that using a 32-bit
IV would be correct.
The thing to avoid is when using a 32-bit IV might wrap (see
vect_set_loop_masks_directly). In that case it would be better to stick with
64-bit WHILELOs.
>From gcc-bugs-return-629093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:53:19 2019
Return-Path: <gcc-bugs-return-629093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117965 invoked by alias); 14 Jan 2019 11:53: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 117888 invoked by uid 48); 14 Jan 2019 11:53:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Mon, 14 Jan 2019 11:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-2LHuU7hX9j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01902.txt.bz2
Content-length: 989
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #15 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to prathamesh3492 from comment #14)
> Created attachment 45425 [details]
> Patch
>
> Hi,
> In the attached patch, I cache results of malloc_candidate_p_1 and avoid
> traversing "back edges".
> Does it look OK ?
I think it's overkill and not needed.
> One issue was with creation of hash_table:
> hash_table<mc_map_elem_t> *mc_cache = new hash_table<mc_map_elem_t> (100);
>
> Using num_ssa_names instead of 100 resulted in allocation failure (and ICE)
> for spinning-smaller.ii.
> Is using a smaller number like 100 OK correctness wise ?
>
> I think Richard's patch in comment 13 is a better approach, since returning
> false should indeed propagate quickly. Testing that patch.
Thanks, you can actually cache 'visited' around the loop over exit block preds,
just move the auto_bitmap visited; before the loop.
> Thanks,
> Prathamesh
>From gcc-bugs-return-629094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:55:45 2019
Return-Path: <gcc-bugs-return-629094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120359 invoked by alias); 14 Jan 2019 11:55:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120148 invoked by uid 48); 14 Jan 2019 11:55:39 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88839] New: [SVE] Poor implementation of blend-like permutes
Date: Mon, 14 Jan 2019 11:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01903.txt.bz2
Content-length: 1131
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88839
Bug ID: 88839
Summary: [SVE] Poor implementation of blend-like permutes
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: rsandifo at gcc dot gnu.org
Target Milestone: ---
Compiling this code with -O3 -msve-vector-bits=256:
typedef int v8si __attribute__((vector_size(32)));
v8si
f (v8si x, v8si y, v8si sel)
{
return __builtin_shuffle (x, y, (v8si) { 0, 9, 2, 11, 4, 13, 6, 15 });
}
produces an inefficient TBL-based sequence.
In these blend-like cases, where index I of the output comes from index I of
one of the inputs, we should be able to use a SEL with an appropriate predicate
constant. The preferred implementation of the above would be:
ptrue p0.d, vl4 // { 1, 0, 1, 0, ... } when used as p0.s
sel res, p0, y, x
This will also be useful for the default VL-agnostic mode when implementing
support for 2-operation SLP.
>From gcc-bugs-return-629095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 11:56:56 2019
Return-Path: <gcc-bugs-return-629095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13951 invoked by alias); 14 Jan 2019 11:56: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 13916 invoked by uid 48); 14 Jan 2019 11:56:52 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88838] [SVE] Use 32-bit WHILELO in LP64 mode
Date: Mon, 14 Jan 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc version everconfirmed
Message-ID: <bug-88838-4-FNX7ZOrJhs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01904.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88838
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |ktkachov at gcc dot gnu.org
Version|unknown |9.0
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed.
>From gcc-bugs-return-629096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:01:50 2019
Return-Path: <gcc-bugs-return-629096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17855 invoked by alias); 14 Jan 2019 12:01: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 17725 invoked by uid 55); 14 Jan 2019 12:01:38 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Mon, 14 Jan 2019 12:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88796-4-nrodo3Rq9h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01905.txt.bz2
Content-length: 1179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Mon Jan 14 12:01:01 2019
New Revision: 267916
URL: https://gcc.gnu.org/viewcvs?rev=267916&root=gcc&view=rev
Log:
PR rtl-optimization/88796
* emit-rtl.h (struct rtl_data): Add stack_protect_guard_decl field.
* cfgexpand.c (stack_protect_prologue): Initialize
crtl->stack_protect_guard_decl.
* function.c (stack_protect_epilogue): Use it instead of calling
targetm.stack_protect_guard again.
* dse.c (check_mem_read_rtx): Ignore MEM_VOLATILE_P reads from
MEMs with MEM_EXPR equal to crtl->stack_protect_guard or
crtl->stack_protect_guard_decl.
* config/i386/i386.c (ix86_stack_protect_guard): Set TREE_THIS_VOLATILE
on the returned MEM_EXPR.
* gcc.target/i386/pr88796.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr88796.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cfgexpand.c
trunk/gcc/config/i386/i386.c
trunk/gcc/dse.c
trunk/gcc/emit-rtl.h
trunk/gcc/function.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:07:34 2019
Return-Path: <gcc-bugs-return-629098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38132 invoked by alias); 14 Jan 2019 12:07:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38084 invoked by uid 48); 14 Jan 2019 12:07:29 -0000
From: "marian.buschsieweke at ovgu dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/30475] assert(int+100 > int) optimized away
Date: Mon, 14 Jan 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marian.buschsieweke at ovgu dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-30475-4-P4zQDKMrlz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-30475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01907.txt.bz2
Content-length: 1147
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=30475
--- Comment #61 from Marian <marian.buschsieweke at ovgu dot de> ---
Thanks for your reply
> The GCC 8 Changes page[*] says -Wstrict-overflow is deprecated (even if it is supposed to still work) and recommends to use -fsanitize=signed-integer-overflow to get a run-time warning, which does catch this.
I think using run-time warnings will miss a lot of bugs, compared to compile
time warnings. I assume that in production builds that the run-time warnings
will be disabled for performance reasons. I also assume that singed integer
overflows will not "normally" happen, e.g. only when an adversary is abusing
the bug in the integer overflow detection. So unless unit tests are explicitly
checking if the signed integer overflow detection code does work properly, the
run-time checks will never trigger.
Even when production builds would have run time warnings enabled, those
warnings would not stop an adversary in exploiting the integer overflow
detection.
I would greatly appreciate if the GCC developer could reconsider depreciating
-Wstrict-overflow.
Kind regards,
Marian
>From gcc-bugs-return-629097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:07:19 2019
Return-Path: <gcc-bugs-return-629097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37358 invoked by alias); 14 Jan 2019 12:07: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 37288 invoked by uid 48); 14 Jan 2019 12:07:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Mon, 14 Jan 2019 12:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-o4YVQbcHO5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01906.txt.bz2
Content-length: 523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #11 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I disagree. Once it's documented, people will rely on it and scream if it
changes. Caveats about something maybe changing in future don't help. If it's
documented to behave one way today, people will depend on that.
It seems you already know what the behaviour is today, so how would documenting
it but saying "this might change tomorrow!" help you? It tells you nothign you
don't already know.
>From gcc-bugs-return-629099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:13:56 2019
Return-Path: <gcc-bugs-return-629099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119628 invoked by alias); 14 Jan 2019 12:13: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 119545 invoked by uid 48); 14 Jan 2019 12:13:50 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88840] New: [9 Regression] std::allocator::construct signature might be ill-formed now
Date: Mon, 14 Jan 2019 12:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01908.txt.bz2
Content-length: 2341
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88840
Bug ID: 88840
Summary: [9 Regression] std::allocator::construct signature
might be ill-formed now
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
#include <memory>
struct X {
X(int);
};
constexpr bool nothrow =
noexcept(std::allocator<X>().construct(std::declval<X*>()));
That construct() call would ill-formed, because the type isn't default
constructible, but until recently it was possible to query whether it could
throw or not. With current trunk the declaration includes an
exception-specification, which makes it ill-formed:
In file included from
/home/jwakely/gcc/9/include/c++/9.0.0/x86_64-pc-linux-gnu/bits/c++allocator.h:33,
from
/home/jwakely/gcc/9/include/c++/9.0.0/bits/allocator.h:46,
from /home/jwakely/gcc/9/include/c++/9.0.0/memory:63,
from construct.cc:1:
/home/jwakely/gcc/9/include/c++/9.0.0/ext/new_allocator.h: In instantiation of
'void __gnu_cxx::new_allocator<_Tp>::construct(_Up*, _Args&& ...) [with _Up =
X; _Args = {}; _Tp = X]':
construct.cc:7:83: required from here
/home/jwakely/gcc/9/include/c++/9.0.0/ext/new_allocator.h:145:20: error: no
matching function for call to 'X::X()'
145 | noexcept(noexcept(::new((void *)__p)
| ^~~~~~~~~~~~~~~~~~
146 | _Up(std::forward<_Args>(__args)...)))
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
construct.cc:4:3: note: candidate: 'X::X(int)'
4 | X(int);
| ^
construct.cc:4:3: note: candidate expects 1 argument, 0 provided
construct.cc:3:8: note: candidate: 'constexpr X::X(const X&)'
3 | struct X {
| ^
construct.cc:3:8: note: candidate expects 1 argument, 0 provided
construct.cc:3:8: note: candidate: 'constexpr X::X(X&&)'
construct.cc:3:8: note: candidate expects 1 argument, 0 provided
We could constrain the declaration with SFINAE, but the program would still be
ill-formed (you still can't ask if the construct() call would throw, because
the declaration would be SFINAE'd out).
>From gcc-bugs-return-629100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:16:41 2019
Return-Path: <gcc-bugs-return-629100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122897 invoked by alias); 14 Jan 2019 12:16:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122786 invoked by uid 48); 14 Jan 2019 12:16:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88840] [9 Regression] std::allocator::construct signature might be ill-formed now
Date: Mon, 14 Jan 2019 12:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88840-4-5r8k3ajeVe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01909.txt.bz2
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88840
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |glisse at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think this started with r265485.
I don't think there's anything we can do about this, and the code is arguably
bad anyway, so maybe just INVALID?
>From gcc-bugs-return-629101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:19:44 2019
Return-Path: <gcc-bugs-return-629101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35484 invoked by alias); 14 Jan 2019 12:19:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26161 invoked by uid 48); 14 Jan 2019 12:19:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88840] [9 Regression] std::allocator::construct signature might be ill-formed now
Date: Mon, 14 Jan 2019 12:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88840-4-4MD7PyX47A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01910.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88840
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-629102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:20:58 2019
Return-Path: <gcc-bugs-return-629102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49177 invoked by alias); 14 Jan 2019 12:20: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 47540 invoked by uid 48); 14 Jan 2019 12:20:51 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43136] Excess copy-in/copy-out with character argument
Date: Mon, 14 Jan 2019 12:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-43136-4-mNDEr1IOPc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01911.txt.bz2
Content-length: 188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43136
--- Comment #3 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Hm, maybe one could simply remove the substring during resolution.
>From gcc-bugs-return-629103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:21:13 2019
Return-Path: <gcc-bugs-return-629103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55718 invoked by alias); 14 Jan 2019 12:21: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 53599 invoked by uid 48); 14 Jan 2019 12:21:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88739] [7/8/9 Regression] Big-endian union bug
Date: Mon, 14 Jan 2019 12:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88739-4-tckHoNdFfP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01912.txt.bz2
Content-length: 2703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
--- Comment #42 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #41)
> On Wed, 9 Jan 2019, rsandifo at gcc dot gnu.org wrote:
>
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88739
> >
> > --- Comment #38 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
> > Created attachment 45392 [details]
> > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45392&action=edit
> > patch that changes get_ref_base_and_extent for bare SSA_NAMEs
> >
> > (In reply to Wilco from comment #37)
> > > (In reply to rsandifo@gcc.gnu.org from comment #35)
> > > > Yeah, the expr.c patch makes the original testcase work, but we still fail
> > > > for:
> > >
> > > That's the folding in ccp1 after inlining, which will require a similar fix.
> > > There are likely more places that need to be fixed to handle the 'short' bit
> > > types.
> >
> > Yeah, seems like a can of worms.
> >
> > The expr.c approach treats a reference to an N-bit integer in an
> > M>N-bit mode is relative to M rather than N (i.e. it's relative
> > to the addressable storage.) So maybe the point this goes wrong
> > is when we ask for get_ref_base_and_extent on a bare 30-bit SSA_NAME
> > (no component accesses) and get back an offset of 0. If everything's
> > relative to the addressable storage then maybe it should be 2 for
> > big-endian?
Btw, get_inner_reference should be changed the same way, likewise
eventually get_addr_base_and_unit_offset.
> > The attached patch does that and seems to pass all three tests
> > in the PR so far. I'll give a spin overnight just in case
> > it's at least vaguely sensible.
>
> I considered this. I guess we need to document this somewhere
> though. Incidentially the GIMPLE verifier already does
>
> if (!AGGREGATE_TYPE_P (TREE_TYPE (op))
> && maybe_gt (size + bitpos,
> tree_to_poly_uint64 (TYPE_SIZE (TREE_TYPE
> (op)))))
> {
> error ("position plus size exceeds size of referenced object
> in "
> "BIT_FIELD_REF");
> return true;
> }
>
>
> so it uses TYPE_SIZE and not TYPE_PREICISON to verify the bounds of
> the BIT_FIELD_REF access.
>
> That said we should probably have exhaustive testing on this.
> Maybe simply try to add GIMPLE testcases exercising the
> BIT_FIELD_REF of bit-precision entities case.
>
> I also wonder whether for the GIMPLE checking we want to verify
> that for bit-precision OP the extracted range is within what
> is valid (which depends on endianess then?).
>From gcc-bugs-return-629104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:22:54 2019
Return-Path: <gcc-bugs-return-629104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57086 invoked by alias); 14 Jan 2019 12:22:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57050 invoked by uid 48); 14 Jan 2019 12:22:49 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88839] [SVE] Poor implementation of blend-like permutes
Date: Mon, 14 Jan 2019 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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 version everconfirmed
Message-ID: <bug-88839-4-L6Wz9O5FB6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88839-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01913.txt.bz2
Content-length: 1056
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88839
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
CC| |ktkachov at gcc dot gnu.org
Version|unknown |9.0
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed. I see:
f:
ptrue p0.s, vl8
adrp x2, .LANCHOR0
ld1w z1.s, p0/z, [x1]
add x2, x2, :lo12:.LANCHOR0
ld1w z0.s, p0/z, [x0]
ld1w z2.s, p0/z, [x2]
mov z3.d, z2.d
tbl z0.s, z0.s, z2.s
sub z3.s, z3.s, #8
tbl z1.s, z1.s, z3.s
orr z0.d, z0.d, z1.d
st1w z0.s, p0, [x8]
ret
>From gcc-bugs-return-629105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:23:11 2019
Return-Path: <gcc-bugs-return-629105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57821 invoked by alias); 14 Jan 2019 12:23: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 57772 invoked by uid 48); 14 Jan 2019 12:23:06 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87018] Boostrap problems on AIX
Date: Mon, 14 Jan 2019 12:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87018-4-YnDDp2eit0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87018-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87018-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01914.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87018
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Since other people seem to have no problem, and I'm not
going to look at this in the medium future, let's
unclutter the bug database.
>From gcc-bugs-return-629106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:37:53 2019
Return-Path: <gcc-bugs-return-629106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119048 invoked by alias); 14 Jan 2019 12:37:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118993 invoked by uid 48); 14 Jan 2019 12:37:49 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88840] [9 Regression] std::allocator::construct signature might be ill-formed now
Date: Mon, 14 Jan 2019 12:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88840-4-IIoFweHljr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01915.txt.bz2
Content-length: 962
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88840
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
LLVM seems to hit a case where this matters, and I'm not sure if it's invalid
yet:
https://bugzilla.opensuse.org/show_bug.cgi?id=1121591
The __use_relocate member of std::vector will check the exception-specification
without checking if the expression is even valid at all:
#if __cplusplus >= 201103L
static constexpr bool __use_relocate =
noexcept(std::__relocate_a(std::declval<pointer>(),
std::declval<pointer>(),
std::declval<pointer>(),
std::declval<_Tp_alloc_type&>()));
#endif
If something depends on that boolean in a context where it isn't going to
relocate, we might get an error from the ill-formed signature.
We might want to only check that noexcept expression if the type is move
constructible.
>From gcc-bugs-return-629107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 12:42:00 2019
Return-Path: <gcc-bugs-return-629107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35593 invoked by alias); 14 Jan 2019 12:42:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35558 invoked by uid 48); 14 Jan 2019 12:41:55 -0000
From: "gonzalobg88 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88662] Document trap representations of _Bool
Date: Mon, 14 Jan 2019 12:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gonzalobg88 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88662-4-WBlFbXaofs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01916.txt.bz2
Content-length: 1093
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88662
--- Comment #12 from gnzlbg <gonzalobg88 at gmail dot com> ---
> I disagree. Once it's documented, people will rely on it and scream if it changes. Caveats about something maybe changing in future don't help. If it's documented to behave one way today, people will depend on that.
That's fair.
> It seems you already know what the behaviour is today
If you tell me that my thoughts about how this currently works are correct then
that documents current behavior, and my code will depend on this.
> so how would documenting it but saying "this might change tomorrow!" help you? It tells you nothign you don't already know.
If this was documented somewhere for a particular version of GCC, when my code
is compiled with that particular GCC version, I could check inputs for invalid
_Bools in my programs and abort reliably without triggering undefined behavior.
If this is not documented anywhere, I can at best write code that "maybe aborts
or maybe has undefined behavior". I find the difference very significant.
>From gcc-bugs-return-629108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 13:31:54 2019
Return-Path: <gcc-bugs-return-629108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67188 invoked by alias); 14 Jan 2019 13:31:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67136 invoked by uid 48); 14 Jan 2019 13:31:49 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88840] [9 Regression] std::allocator::construct signature might be ill-formed now
Date: Mon, 14 Jan 2019 13:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88840-4-RFltLlm881@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01917.txt.bz2
Content-length: 1220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88840
--- Comment #3 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> We could constrain the declaration with SFINAE, but the program would still
> be ill-formed (you still can't ask if the construct() call would throw,
> because the declaration would be SFINAE'd out).
Normally, a user should first check if the operation is valid, and only then
check if it throws. The nothrow traits are kind of supposed to do that for you
I think (except that there isn't one for allocator::construct).
(In reply to Jonathan Wakely from comment #2)
> The __use_relocate member of std::vector will check the
> exception-specification without checking if the expression is even valid at
> all:
I think I already hit and fixed some very similar problem (found by the
testsuite) while writing this patch, but it is indeed quite possible that the
issue still exists.
It is possible to imagine a type being relocatable but not movable, although we
may not be ready to support that.
It should be possible to define __use_relocate more lazily so it is only looked
at if we call reserve, push_back, some function that requires it.
>From gcc-bugs-return-629109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 13:34:31 2019
Return-Path: <gcc-bugs-return-629109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70741 invoked by alias); 14 Jan 2019 13:34: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 70621 invoked by uid 48); 14 Jan 2019 13:34:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Mon, 14 Jan 2019 13:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-wMGKEbQwmd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01918.txt.bz2
Content-length: 1570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #24 from Richard Biener <rguenth at gcc dot gnu.org> ---
On GCC testcases one large group of MEMs only disambiguated through
base_alias_check is disambiguations agains DSEs group_info->base_mem
which is BLKmode mems based on some "base" pointer. This base_mem
lacks a MEM_EXPR but I think it shouldn't be difficult to add one,
like with (completely lacking sanity testing):
diff --git a/gcc/dse.c b/gcc/dse.c
index 389c52d4284..098c77165de 100644
--- a/gcc/dse.c
+++ b/gcc/dse.c
@@ -1097,6 +1097,7 @@ canon_address (rtx mem,
{
machine_mode address_mode = get_address_mode (mem);
rtx mem_address = XEXP (mem, 0);
+ tree mem_expr = MEM_EXPR (mem);
rtx expanded_address, address;
int expanded;
@@ -1165,6 +1166,9 @@ canon_address (rtx mem,
&& const_or_frame_p (address))
{
group_info *group = get_group_info (address);
+ if (!MEM_EXPR (group->base_mem)
+ && mem_expr)
+ set_mem_expr (group->base_mem, get_base_address (mem_expr));
if (dump_file && (dump_flags & TDF_DETAILS))
{
btw, the disambiguations like
(mem/c:SI (symbol_ref:DI ("g") [flags 0x2] <var_decl 0x7fe01f78a510 g>) [1 g+0
S4 A32])
vs. (mem:DI (pre_dec:DI (reg/f:DI 7 sp)) [0 S8 A8])
are handled through REG_BASE_VALUE which assigns 'sp' (address:DI -1).
I believe we should be working towards adding proper MEM_EXPRs to more
places and simply make find_base_term more conservative which means
simplifying the PLUS/MINUS cases.
>From gcc-bugs-return-629110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 13:44:42 2019
Return-Path: <gcc-bugs-return-629110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122639 invoked by alias); 14 Jan 2019 13:44: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 121745 invoked by uid 48); 14 Jan 2019 13:44:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88796] -fstack-protector* kills RTL DSE opportunities
Date: Mon, 14 Jan 2019 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88796-4-GRjVtk6wcu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88796-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01919.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88796
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for GCC9+.
>From gcc-bugs-return-629111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 13:55:11 2019
Return-Path: <gcc-bugs-return-629111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29085 invoked by alias); 14 Jan 2019 13:55:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29027 invoked by uid 48); 14 Jan 2019 13:55:06 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88755] [9 Regression] ICE in compute_fn_summary, at ipa-fnsummary.c:2513 since r267601
Date: Mon, 14 Jan 2019 13:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: hubicka at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88755-4-7FIQZ0IiaA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88755-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01920.txt.bz2
Content-length: 1130
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88755
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
and:
$ g++ /home/marxin/Programming/gcc/gcc/testsuite/g++.old-deja/g++.eh/catch3p.C
--param uninlined-thunk-insns=2062717165 -Og
during IPA pass: inline
/home/marxin/Programming/gcc/gcc/testsuite/g++.old-deja/g++.eh/catch3p.C: At
global scope:
/home/marxin/Programming/gcc/gcc/testsuite/g++.old-deja/g++.eh/catch3p.C:117:1:
internal compiler error: in estimate_size_after_inlining, at
ipa-inline-analysis.c:272
117 | }
| ^
0x705b89 estimate_size_after_inlining(cgraph_node*, cgraph_edge*)
/home/marxin/Programming/gcc/gcc/ipa-inline-analysis.c:272
0x1799c09 caller_growth_limits
/home/marxin/Programming/gcc/gcc/ipa-inline.c:186
0x1799c09 can_inline_edge_by_limits_p
/home/marxin/Programming/gcc/gcc/ipa-inline.c:428
0x179f0ea inline_small_functions
/home/marxin/Programming/gcc/gcc/ipa-inline.c:1852
0x179f0ea ipa_inline
/home/marxin/Programming/gcc/gcc/ipa-inline.c:2528
0x179f0ea execute
/home/marxin/Programming/gcc/gcc/ipa-inline.c:2936
>From gcc-bugs-return-629112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 14:23:29 2019
Return-Path: <gcc-bugs-return-629112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116473 invoked by alias); 14 Jan 2019 14:23: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 107026 invoked by uid 48); 14 Jan 2019 14:23:23 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/77776] C++17 std::hypot implementation is poor
Date: Mon, 14 Jan 2019 14:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77776-4-xOliiehjjo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77776-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01921.txt.bz2
Content-length: 991
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77776
--- Comment #10 from Matthias Kretz <kretz at kde dot org> ---
Experience from testing my simd implementation:
I had failures (2 ULP deviation from long double result) when using
auto __xx = abs(__x);
auto __yy = abs(__y);
auto __zz = abs(__z);
auto __hi = max(max(__xx, __yy), __zz);
auto __l0 = min(__zz, max(__xx, __yy));
auto __l1 = min(__yy, __xx);
__l0 /= __hi;
__l1 /= __hi;
auto __lo = __l0 * __l0 + __l1 * __l1;
return __hi * sqrt(1 + __lo);
Where the failures occur depends on wether FMA instructions are used. I have
observed only 1 ULP deviation from long double with my algorithm (independent
of FMAs).
Here are two data points that seem challenging:
hypot(0x1.965372p+125f, 0x1.795c92p+126f, 0x1.d0fc96p+125f) -> 0x1.e79366p+126f
hypot(0x1.235f24p+125f, 0x1.5b88f4p+125f, 0x1.d57828p+124f) -> 0x1.feaa26p+125f
>From gcc-bugs-return-629113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:00:37 2019
Return-Path: <gcc-bugs-return-629113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105850 invoked by alias); 14 Jan 2019 15:00: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 96291 invoked by uid 48); 14 Jan 2019 15:00:29 -0000
From: "wei3.xiao at intel dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88794] [9 Regression] fixupimm intrinsics are unusable
Date: Mon, 14 Jan 2019 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wei3.xiao at intel dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88794-4-xqYLKRHuB0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88794-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01922.txt.bz2
Content-length: 314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88794
--- Comment #1 from Wei Xiao <wei3.xiao at intel dot com> ---
My change (r265827) is based on the latest SDM (Intel® 64 and IA-32
Architectures Software Developer Manuals) which is incorrect for the fixupimm
intrinsics. I'm preparing a patch to fix it.
>From gcc-bugs-return-629114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:09:29 2019
Return-Path: <gcc-bugs-return-629114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60890 invoked by alias); 14 Jan 2019 15:09: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 60806 invoked by uid 48); 14 Jan 2019 15:09:24 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 2019 15:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4-PPEVe2elFo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01923.txt.bz2
Content-length: 2600
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #5 from dominik.strasser@onespin-solutions.com ---
ASAN from git crashes like this. Looks like a double fault.
SignalHandler_Unix.h is in my application's code.
I've attached ASAN's debug output where I removed all messages talking about
poisoning/unpoisoning as they look unrelated.
#5 0x00007f6fd264c005 in SYSTEM::handleSignalForThread (t=140117893179136) at
SignalHandler_Unix.h:412
#6 0x00007f6fd264c57f in SYSTEM::gBadSignalHandler (signalNr=11,
info=0x7f6fbd3fb070, ctx=0x7f6fbd3faf40) at SignalHandler_Unix.h:478
#7 <signal handler called>
#8 __asan::GetCurrentThread () at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:415
#9 0x00007f6ffa37c58d in __asan_handle_no_return () at
../../../../gcc-git/libsanitizer/asan/asan_rtl.cc:538
#10 0x00007f6fd264c04e in SYSTEM::handleSignalForThread (t=140117893179136) at
SignalHandler_Unix.h:423
#11 0x00007f6fd264c57f in SYSTEM::gBadSignalHandler (signalNr=11,
info=0x7f6fbd3fbd70, ctx=0x7f6fbd3fbc40) at SignalHandler_Unix.h:478
#12 <signal handler called>
#13 GetCurrentThread () at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:415
#14 __asan::GetCurrentTidOrInvalid () at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:429
#15 0x00007f6ffa37a1ea in __asan::ReportGenericError (pc=140118247917729,
bp=bp@entry=140117893172896, sp=sp@entry=140117893172888, addr=105827994255744,
is_write=is_write@entry=false, access_size=access_size@entry=8, exp=0,
fatal=true) at ../../../../gcc-git/libsanitizer/asan/asan_report.cc:459
#16 0x00007f6ffa37aea8 in __asan::__asan_report_load8 (addr=<optimized out>) at
../../../../gcc-git/libsanitizer/asan/asan_rtl.cc:119
#17 0x00007f6fd264c8a1 in SYSTEM::gBadSignalHandler (signalNr=11,
info=0x7f6fbd3fd630, ctx=0x7f6fbd3fd500) at SignalHandler_Unix.h:502
#18 <signal handler called>
#19 __asan::AsanThread::SetThreadStackAndTls (this=this@entry=0x7f6fbc552000,
options=<optimized out>) at
../../../../gcc-git/libsanitizer/asan/asan_thread.h:80
#20 0x00007f6ffa37e619 in __asan::AsanThread::Init
(this=this@entry=0x7f6fbc552000, options=options@entry=0x0) at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:223
#21 0x00007f6ffa37ea64 in __asan::AsanThread::ThreadStart (this=0x7f6fbc552000,
os_id=5519, signal_thread_is_registered=0x7f6fc29da978) at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:244
#22 0x00007f6fd150de25 in start_thread () from /lib64/libpthread.so.0
#23 0x00007f6fd01dcbad in clone () from /lib64/libc.so.6
>From gcc-bugs-return-629115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:10:13 2019
Return-Path: <gcc-bugs-return-629115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62256 invoked by alias); 14 Jan 2019 15:10: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 62137 invoked by uid 48); 14 Jan 2019 15:10:09 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 2019 15:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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: attachments.created
Message-ID: <bug-88791-4-1AzxLeF9Eh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01924.txt.bz2
Content-length: 235
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #6 from dominik.strasser@onespin-solutions.com ---
Created attachment 45426
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45426&action=edit
ASAN debug output
>From gcc-bugs-return-629116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:16:20 2019
Return-Path: <gcc-bugs-return-629116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90188 invoked by alias); 14 Jan 2019 15: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 89929 invoked by uid 48); 14 Jan 2019 15:16:14 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Mon, 14 Jan 2019 15:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-SqkUe8RJpN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01925.txt.bz2
Content-length: 1731
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
> It's quite strange that following is fine:
>
> $ cat pr88587-2.c
> __attribute__((target("default"))) void a() {
> __attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
> }
>
> __attribute__((target("sse2"))) void a2() {
> __attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
> }
>
> $ gcc -c -m32 -mno-sse -O -g pr88587-2.c
>
> I'll investigate how precisely the debug insn looks like in both situations.
I was wrong, this also fails, so not target_clone attribute related:
$ cat ~/Programming/testcases/pr88587-2.c
__attribute__((target("default"),always_inline)) void a() {
__attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
}
__attribute__((target("sse2"))) void a2() {
a ();
__attribute__((__vector_size__(4 * sizeof(float)))) int b = {};
}
$ gcc ~/Programming/testcases/pr88587-2.c -c -m32 -mno-sse -O -g
/home/marxin/Programming/testcases/pr88587-2.c:1:55: warning: always_inline
function might not be inlinable [-Wattributes]
__attribute__((target("default"),always_inline)) void a() {
^
during RTL pass: expand
/home/marxin/Programming/testcases/pr88587-2.c: In function ‘a2’:
/home/marxin/Programming/testcases/pr88587-2.c:5:38: internal compiler error:
in expand_debug_locations, at cfgexpand.c:5403
__attribute__((target("sse2"))) void a2() {
^~
0x7ffff6996fea __libc_start_main
../csu/libc-start.c:308
The ICE is very old, starting from GCC 4.8.0. Before that target attribute was
not known yet.
>From gcc-bugs-return-629117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:17:11 2019
Return-Path: <gcc-bugs-return-629117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91568 invoked by alias); 14 Jan 2019 15:17: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 91401 invoked by uid 48); 14 Jan 2019 15:17:06 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 2019 15:17: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4-fvbIyHl3dP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01926.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #7 from dominik.strasser@onespin-solutions.com ---
I canse it plays a role:
I am running on a CentOS Linux release 7.5.1804
which has kernel version 3.10.0-862.11.6.el7.x86_64
and glibc glibc-2.17-222.el7.i686
>From gcc-bugs-return-629118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:30:54 2019
Return-Path: <gcc-bugs-return-629118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57705 invoked by alias); 14 Jan 2019 15:30:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57632 invoked by uid 48); 14 Jan 2019 15:30:48 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Mon, 14 Jan 2019 15:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-1JBqHWERJl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01927.txt.bz2
Content-length: 1242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
> I think the canonical way of re-computing DECL_MODE would be to re-layout
> decls since that also updates RTL if that was already set. There's
> relayout_decl for this which is for example called from omp-simd-clone.c
> and the vectorizer.
That's fine, however it eventually calls
SET_DECL_MODE (decl, TYPE_MODE (type));
which calls vector_type_mode (const_tree t)
and
if (VECTOR_MODE_P (mode)
&& (!targetm.vector_mode_supported_p (mode)
|| !have_regs_of_mode[mode]))
{
scalar_int_mode innermode;
/* For integers, try mapping it to a same-sized scalar mode. */
if (is_int_mode (TREE_TYPE (t)->type_common.mode, &innermode))
{
poly_int64 size = (TYPE_VECTOR_SUBPARTS (t)
* GET_MODE_BITSIZE (innermode));
scalar_int_mode mode;
if (int_mode_for_size (size, 0).exists (&mode)
&& have_regs_of_mode[mode]) <--- HERE
return mode;
}
return BLKmode;
}
HERE we return false. Do you know how current_function influences
int_mode_for_size and (or) have_regs_of_mode?
>From gcc-bugs-return-629119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:37:31 2019
Return-Path: <gcc-bugs-return-629119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64878 invoked by alias); 14 Jan 2019 15:37: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 64789 invoked by uid 48); 14 Jan 2019 15:37:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Mon, 14 Jan 2019 15:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-rbykh4GbzS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01928.txt.bz2
Content-length: 2290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Martin Liška from comment #9)
> > I think the canonical way of re-computing DECL_MODE would be to re-layout
> > decls since that also updates RTL if that was already set. There's
> > relayout_decl for this which is for example called from omp-simd-clone.c
> > and the vectorizer.
>
> That's fine, however it eventually calls
> SET_DECL_MODE (decl, TYPE_MODE (type));
> which calls vector_type_mode (const_tree t)
>
> and
>
> if (VECTOR_MODE_P (mode)
> && (!targetm.vector_mode_supported_p (mode)
> || !have_regs_of_mode[mode]))
> {
> scalar_int_mode innermode;
>
> /* For integers, try mapping it to a same-sized scalar mode. */
> if (is_int_mode (TREE_TYPE (t)->type_common.mode, &innermode))
> {
> poly_int64 size = (TYPE_VECTOR_SUBPARTS (t)
> * GET_MODE_BITSIZE (innermode));
> scalar_int_mode mode;
> if (int_mode_for_size (size, 0).exists (&mode)
> && have_regs_of_mode[mode]) <--- HERE
> return mode;
> }
>
> return BLKmode;
> }
>
> HERE we return false. Do you know how current_function influences
> int_mode_for_size and (or) have_regs_of_mode?
ok, happens here:
#0 ix86_conditional_register_usage () at
/home/marxin/Programming/gcc/gcc/config/i386/i386.c:4802
#1 0x0000000000ed04a0 in init_reg_sets_1 () at
/home/marxin/Programming/gcc/gcc/reginfo.c:270
#2 0x0000000000f68b61 in target_reinit () at
/home/marxin/Programming/gcc/gcc/toplev.c:2009
#3 0x0000000001a9f336 in save_target_globals () at
/home/marxin/Programming/gcc/gcc/target-globals.c:86
#4 0x0000000001373dbc in ix86_set_current_function (fndecl=<function_decl
0x7ffff6c5c800 a.sse2.0>) at
/home/marxin/Programming/gcc/gcc/config/i386/i386.c:5768
#5 0x0000000000baa150 in invoke_set_current_function_hook
(fndecl=<function_decl 0x7ffff6c5c800 a.sse2.0>) at
/home/marxin/Programming/gcc/gcc/function.c:4629
#6 0x0000000000bb1175 in invoke_set_current_function_hook (fndecl=<optimized
out>) at /home/marxin/Programming/gcc/gcc/function.c:4613
#7 set_cfun (new_cfun=<optimized out>, force=<optimized out>) at
/home/marxin/Programming/gcc/gcc/function.c:4653
>From gcc-bugs-return-629120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:47:00 2019
Return-Path: <gcc-bugs-return-629120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83787 invoked by alias); 14 Jan 2019 15:47: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 83725 invoked by uid 48); 14 Jan 2019 15:46:56 -0000
From: "matt at godbolt dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88841] New: Missed optimization transforming cascading ||s into a bit select
Date: Mon, 14 Jan 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matt at godbolt dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01929.txt.bz2
Content-length: 1344
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88841
Bug ID: 88841
Summary: Missed optimization transforming cascading ||s into a
bit select
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: matt at godbolt dot org
Target Milestone: ---
It seems around GCC 7 an optimization was added turning multiple comparisons of
a small range into a bit-select. This optimization seems to be sensitive to the
ordering of the comparisons, which seems like a missed opportunity.
On x86_64 GCCs 7 and above (tested with trunk 9.0 too) with -O2 :
---snip
bool isspc_1(char c)
{
return c == ' '
|| c == '\n'
|| c == '\r'
|| c == '\t';
}
bool isspc_2(char c)
{
return c == ' '
|| c == '\r'
|| c == '\n'
|| c == '\t';
}
--- end snip (see https://godbolt.org/z/ovB_Oz )
...the isspc_2 is optimized using the bit selection optimization, but the
isspc_1 is not. The only difference is the order of the comparisons. It's not
clear to me which is actually faster, but my instinct is the results of these
two functions should be the same code.
>From gcc-bugs-return-629122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:48:54 2019
Return-Path: <gcc-bugs-return-629122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88187 invoked by alias); 14 Jan 2019 15:48: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 88122 invoked by uid 48); 14 Jan 2019 15:48:51 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84849] Ambiguous resolution of braze initializer list to a class with explicit constructors
Date: Mon, 14 Jan 2019 15: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: 7.2.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84849-4-24h9vD5y3O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01931.txt.bz2
Content-length: 641
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84849
--- Comment #7 from ensadc at mailnesia dot com ---
(In reply to Zhihao Yuan from comment #6)
> Here is a possibly related case:
>
> [...]
I think this is a different bug. GCC thinks the implicitly-deleted move
assignment operator `pair<int&>& pair<int&>::operator=(pair<int&>&&)` is a
candidate for the assignment, which causes ambiguity with
`operator=(value_type&&)` (where value_type = pair<int>). But as part of
resolution of CWG 1402, [class.copy.assign] specifies that "A defaulted move
assignment operator that is defined as deleted is ignored by overload
resolution".
>From gcc-bugs-return-629121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:48:41 2019
Return-Path: <gcc-bugs-return-629121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87411 invoked by alias); 14 Jan 2019 15:48: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 87355 invoked by uid 48); 14 Jan 2019 15:48:37 -0000
From: "ptdrnvqd at 10mail dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88842] New: missing optimization CSE, reassociation
Date: Mon, 14 Jan 2019 15:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ptdrnvqd at 10mail 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-88842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01930.txt.bz2
Content-length: 1196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88842
Bug ID: 88842
Summary: missing optimization CSE, reassociation
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: ptdrnvqd at 10mail dot org
Target Milestone: ---
from retweet danluu
↓
https://twitter.com/johnregehr/status/923682400676093952
not every day you run across a … easy optimization missing from all of LLVM,
GCC, and Intel CC…
↓
http://lists.llvm.org/pipermail/llvm-dev/2017-October/118476.html
[llvm-dev] [PATCH/RFC] Modifying reassociate for improved CSE: … perf gains
>> “…several people asked if this is safe; here's how LLVM safely reassociates addition with undefined signed overflow…â€
i dont know to what degree is track their development/findings
or was this only llvm-side
>> “… to convince another person that reassociate is a safe pass…â€
also may this apply outside of -ffast-math? for GCC?
>From gcc-bugs-return-629123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:52:03 2019
Return-Path: <gcc-bugs-return-629123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90891 invoked by alias); 14 Jan 2019 15:52: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 90816 invoked by uid 48); 14 Jan 2019 15:51:59 -0000
From: "ptdrnvqd at 10mail dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/88842] missing optimization CSE, reassociation
Date: Mon, 14 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: other
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ptdrnvqd at 10mail 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-88842-4-gxZbkdQ9aT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88842-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01932.txt.bz2
Content-length: 934
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88842
--- Comment #1 from ptdrnvqd at 10mail dot org ---
from retweet danluu
↓
https://twitter.com/johnregehr/status/923682400676093952
not every day you run across a … easy optimization missing from all of LLVM,
GCC, and Intel CC…
↓
http://lists.llvm.org/pipermail/llvm-dev/2017-October/118476.html
[llvm-dev] [PATCH/RFC] Modifying reassociate for improved CSE: … perf gains
>> “…several people asked if this is safe; here's how LLVM safely reassociates addition with undefined signed overflow…â€
i dont know to what degree is track their development/findings
or was this only llvm-side
>> “… to convince another person that reassociate is a safe pass…â€
also may this apply outside of -ffast-math? for GCC?
also i dont know what version, it was over a year ago
>From gcc-bugs-return-629124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:54:37 2019
Return-Path: <gcc-bugs-return-629124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100188 invoked by alias); 14 Jan 2019 15:54: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 100095 invoked by uid 48); 14 Jan 2019 15:54:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88791-4-nv8WoT6Bi2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01933.txt.bz2
Content-length: 702
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to dominik.strasser from comment #7)
> I canse it plays a role:
> I am running on a CentOS Linux release 7.5.1804
> which has kernel version 3.10.0-862.11.6.el7.x86_64
> and glibc glibc-2.17-222.el7.i686
Well, to be honest the glibc is very old. Note that sanitizer are intercepting
glibc calls and there are some issues with compatibility.
So please, try your application on a new system. I would recommend e.g.
https://software.opensuse.org/distributions/tumbleweed
I can help with the system. Can you provide what kind of dependencies your
application has?
>From gcc-bugs-return-629125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 15:56:36 2019
Return-Path: <gcc-bugs-return-629125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103088 invoked by alias); 14 Jan 2019 15:56:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103010 invoked by uid 48); 14 Jan 2019 15:56:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 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: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88791-4-KbjWyNtxya@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01934.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #9 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to dominik.strasser from comment #5)
> ASAN from git crashes like this. Looks like a double fault.
Yes, SEGFAULT happens right in the sanitizer code that's responsible
for creation of a thread. Thus I suspect some incompatibility with
glibc.
> SignalHandler_Unix.h is in my application's code.
> I've attached ASAN's debug output where I removed all messages talking about
> poisoning/unpoisoning as they look unrelated.
>From gcc-bugs-return-629126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 16:04:57 2019
Return-Path: <gcc-bugs-return-629126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79517 invoked by alias); 14 Jan 2019 16: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 78517 invoked by uid 48); 14 Jan 2019 16:04:47 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Mon, 14 Jan 2019 16:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84995-4-gAyAoCxBeD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01935.txt.bz2
Content-length: 1283
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to ДилÑн Палаузов from comment #9)
> Yes, $(libdir)/bfd-plugins is a location automatically scanned by
> ar/nm/ranlib.
>
> The question is, why GCC’s “make install†does not put there its linker
> plugin.
Looks at what we do in SUSE, you can have multiple packages of gcc (like gcc7,
gcc8). But there's a packages 'gcc' that's responsible for creation of the
following symlink:
/usr/lib/bfd-plugins/liblto_plugin.so.0.0.0 ->
/usr/lib64/gcc/x86_64-suse-linux/8/liblto_plugin.so.0.0.0
so then nm,ranlib,.. is relying on the 'system' compiler.
>
> As long as nobody installs the linker plugins under $(libdir)/bfd-plugins,
> how are program ./configure’s supposed to be written in a way, that LTO
> works with both Clang and GCC?
Richi can you please elaborate on that?
>From gcc-bugs-return-629127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 16:06:19 2019
Return-Path: <gcc-bugs-return-629127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81125 invoked by alias); 14 Jan 2019 16:06: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 80998 invoked by uid 48); 14 Jan 2019 16:06:10 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Mon, 14 Jan 2019 16:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88810-4-qtkz7AOnEI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01936.txt.bz2
Content-length: 915
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to kargl from comment #1)
> Paul
>
> 'svn blame' points a finger at you with r212486.
> Does this section of code ring a bell.
I'm I reading r212486 correctly, the previous version of the code already had a
duplicated condition: both copies of the duplicated condition were updated in
r212486 from:
if (reverse && reverse[n] == GFC_ENABLE_REVERSE)
to:
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
I *think* the duplicated condition was introduced by r174302 (but I'm no expert
on this code).
>From gcc-bugs-return-629128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 16:13:49 2019
Return-Path: <gcc-bugs-return-629128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102386 invoked by alias); 14 Jan 2019 16:13: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 102309 invoked by uid 48); 14 Jan 2019 16:13:45 -0000
From: "mcccs at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83531] Build broken on macOS 10.13.2
Date: Mon, 14 Jan 2019 16:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mcccs at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-83531-4-OZGstOPvLY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01937.txt.bz2
Content-length: 596
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83531
MCCCS <mcccs at gmx dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mcccs at gmx dot com
--- Comment #2 from MCCCS <mcccs at gmx dot com> ---
The issue is caused by `os/availability.h` or `AvailabilityInternal.h`.
Instead of `API_AVAILABLE`, only `__API_AVAILABLE` is defined (Clang defines
both) This is also the cause of a few failing tests
(g++.dg/other/darwin-cfstring1.C for example)
>From gcc-bugs-return-629129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 16:35:10 2019
Return-Path: <gcc-bugs-return-629129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6560 invoked by alias); 14 Jan 2019 16:35:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 2363 invoked by uid 48); 14 Jan 2019 16:35:06 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 2019 16:35: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4-vrsDHZ181n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01938.txt.bz2
Content-length: 368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #10 from dominik.strasser@onespin-solutions.com ---
Looking at the backtrace, the effects are very different between gcc 7.4 and
9.0. Making it work on a different glibc wouldn't help for me. CentOs 7.5 ==
RHEL 7.5 which is the latest "commercial" Linux system. What could we do to
make it work?
>From gcc-bugs-return-629130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 16:37:28 2019
Return-Path: <gcc-bugs-return-629130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36361 invoked by alias); 14 Jan 2019 16:37: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 36306 invoked by uid 48); 14 Jan 2019 16:37:24 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88843] New: [9 Regression] make: Circular s-attr-common <- insn-conditions.md dependency dropped.
Date: Mon, 14 Jan 2019 16:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01939.txt.bz2
Content-length: 724
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88843
Bug ID: 88843
Summary: [9 Regression] make: Circular s-attr-common <-
insn-conditions.md dependency dropped.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
On x86-64, r267904 gave
[hjl@gnu-cfl-1 gcc]$ pwd
/export/build/gnu/tools-build/gcc-debug/build-x86_64-linux/gcc
[hjl@gnu-cfl-1 gcc]$ make -j12
make: Circular s-attr-common <- insn-conditions.md dependency dropped.
[hjl@gnu-cfl-1 gcc]$
>From gcc-bugs-return-629131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 16:46:04 2019
Return-Path: <gcc-bugs-return-629131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52235 invoked by alias); 14 Jan 2019 16:46:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52146 invoked by uid 55); 14 Jan 2019 16:45:53 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88822] Strange inconsistency between types of qualified rvalues.
Date: Mon, 14 Jan 2019 16:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88822-4-xG91mQvRUb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01940.txt.bz2
Content-length: 1109
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88822
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
If an rvalue's type (or, for that matter, an lvalue's type) is observed
with _Generic, the qualifiers should be consistently dropped.
If a type is observed with typeof, qualifiers need to be kept in some
cases for compatibility. That's definitely the case with lvalues (because
of use of typeof for defining aliases); I doubt it's the case for at least
these rvalues.
If a type is observed in the text of a diagnostic, there are of course no
compatibility requirements on whether qualifiers are present or not; it's
a question of what's most helpful for the user (and for the message about
the assignment, I don't think the qualifiers are helpful even for lvalues,
given that the RHS has gone through lvalue-to-rvalue conversion).
(For _Atomic, the reference to p3 gets an explicit atomic_load applied by
the compiler in its internal representation before the &* are applied,
hence the qualifiers having been removed there.)
>From gcc-bugs-return-629132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 17:02:39 2019
Return-Path: <gcc-bugs-return-629132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28965 invoked by alias); 14 Jan 2019 17: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 28922 invoked by uid 48); 14 Jan 2019 17:02:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88844] New: poor range info for number of loop iterations with a known upper bound
Date: Mon, 14 Jan 2019 17:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01941.txt.bz2
Content-length: 841
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88844
Bug ID: 88844
Summary: poor range info for number of loop iterations with a
known upper bound
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
The number of iterations of the loop below is bounded by the size of i so the
value of n on loop exit is in the range [0, 4] but get_range_info() reports it
as [0, +INF]. As a result, the if statement is not eliminated.
void f (unsigned i)
{
unsigned n = 0;
while (i) {
i >>= 4;
++n;
}
if (n > sizeof i)
__builtin_abort ();
}
>From gcc-bugs-return-629133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 17:14:08 2019
Return-Path: <gcc-bugs-return-629133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68387 invoked by alias); 14 Jan 2019 17:14:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68347 invoked by uid 48); 14 Jan 2019 17:14:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88843] [9 Regression] make: Circular s-attr-common <- insn-conditions.md dependency dropped.
Date: Mon, 14 Jan 2019 17:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-88843-4-ZlmAN7s2u7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01942.txt.bz2
Content-length: 624
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88843
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I've mistakenly committed also the t-i386 change in r267850 when I meant to
commit just the Makefile.in change. Reverted in r267914.
>From gcc-bugs-return-629134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 17:36:53 2019
Return-Path: <gcc-bugs-return-629134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50034 invoked by alias); 14 Jan 2019 17:36:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49960 invoked by uid 48); 14 Jan 2019 17:36:48 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88835] overly aggressive -Werror=format-overflow for printf since r265648
Date: Mon, 14 Jan 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status see_also short_desc everconfirmed
Message-ID: <bug-88835-4-MYjvZzUWz0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01943.txt.bz2
Content-length: 3407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88835
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=88844
Summary|[9 Regression] Maybe |overly aggressive
|misleading |-Werror=format-overflow for
|-Werror=format-overflow |printf since r265648
|since r265648 |
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning can be reproduced in the (over)simplified test case below. There,
it isn't strictly incorrect -- the upper bound of the width does allow the
output to exceed INT_MAX. But it arguably is overly pedantic.
The root cause in the readelf.i test case is the same: the width the warning
sees is unbounded. But the warning there is a false positive because the width
is clearly bounded. The width is computed in a loop like the one in pr88844
where GCC should be but is unable to determine the maximum number of iterations
(bounded by the size of the integer argument). As a result of the width's
upper bound being unknown it is taken as INT_MAX.
Short of examining the loop and computing the range itself there isn't much the
warning code can do to compensate for the poor range info it relies on. What
it could and maybe should do is avoid using the upper bound at level 1 and
instead use the lower bound.
GCC 8 issues the same warning for calls to sprintf. It doesn't check printf
and fprintf, so it doesn't diagnose the Binutils test case. r265648 extended
the checking to those functions and exposed the underlying issues. As a
result, even though I agree that the warning is overly aggressive, I don't
consider this bug a regression. Let me look into relaxing it.
$ cat pr88835.c && gcc -O2 -S -Wall -fdump-tree-printf-return-value=/dev/stdout
pr88835.c
void f (int n, int i)
{
if (n < 4)
n = 4;
if (i < 4)
i = 4;
__builtin_printf (" %*i", n, i);
}
;; Function f (f, funcdef_no=0, decl_uid=1907, cgraph_uid=1, symbol_order=0)
pr88835.c:8: __builtin_printf: objsize = 18446744073709551615, fmtstr = " %*i"
Directive 1 at offset 0: " ", length = 1
Result: 1, 1, 1, 1 (1, 1, 1, 1)
Directive 2 at offset 1: "%*i", width in range [4, 2147483647]
pr88835.c: In function ‘f’:
pr88835.c:8:23: warning: ‘%*i’ directive output between 4 and 2147483647 bytes
may cause result to exceed ‘INT_MAX’ [-Wformat-overflow=]
8 | __builtin_printf (" %*i", n, i);
| ^~~
pr88835.c:8:21: note: directive argument in the range [4, 2147483647]
8 | __builtin_printf (" %*i", n, i);
| ^~~~~~
Result: 4, 2147483647, 2147483647, 2147483647 (5, 2147483648, 2147483648,
2147483648)
Directive 3 at offset 4: "", length = 1
f (int n, int i)
{
<bb 2> [local count: 1073741824]:
n_4 = MAX_EXPR <n_1(D), 4>;
i_2 = MAX_EXPR <i_3(D), 4>;
__builtin_printf (" %*i", n_4, i_2);
return;
}
>From gcc-bugs-return-629135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 17:41:19 2019
Return-Path: <gcc-bugs-return-629135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126939 invoked by alias); 14 Jan 2019 17:41:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126906 invoked by uid 48); 14 Jan 2019 17:41:16 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88845] New: ICE in lra_set_insn_recog_data, at lra.c:1010
Date: Mon, 14 Jan 2019 17:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01944.txt.bz2
Content-length: 802
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88845
Bug ID: 88845
Summary: ICE in lra_set_insn_recog_data, at lra.c:1010
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bergner at gcc dot gnu.org
Target Milestone: ---
The following ICEs for me with trunk, GCC 8 and GCC 7:
bergner@pike:~$ cat bug.i
struct a {
unsigned b;
float c;
};
void
foo (void)
{
float e;
struct a f;
e = f.c;
__asm__("" : : "f"(e));
}
bergner@pike:~$ gcc -O2 -S bug.i
bug.i: In function ‘foo’:
bug.i:12:1: internal compiler error: in lra_set_insn_recog_data, at lra.c:1010
}
^
>From gcc-bugs-return-629136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 17:54:29 2019
Return-Path: <gcc-bugs-return-629136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79302 invoked by alias); 14 Jan 2019 17:54: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 79251 invoked by uid 48); 14 Jan 2019 17:54:25 -0000
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Mon, 14 Jan 2019 17:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sje at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88682-4-dSPuvxNdrb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01945.txt.bz2
Content-length: 790
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
Steve Ellcey <sje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sje at gcc dot gnu.org
--- Comment #5 from Steve Ellcey <sje at gcc dot gnu.org> ---
It looks like this test is violating strict aliasing. If I compile with
-fno-strict-aliasing then it works.
I think pointing p.i (type __int128_t) to something of type unaligned_int128_t
is a standards violation in C or C++ but I am not a language lawyer.
FYI: I get the same behavior with C or C++ on aarch64. It works with -O1
on aarch64 but fails with -O2 and the difference is the ordering of loads
and stores.
>From gcc-bugs-return-629137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:01:28 2019
Return-Path: <gcc-bugs-return-629137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19538 invoked by alias); 14 Jan 2019 18:01: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 15536 invoked by uid 48); 14 Jan 2019 18:01:20 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88845] ICE in lra_set_insn_recog_data, at lra.c:1010
Date: Mon, 14 Jan 2019 18:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88845-4-zOnhitgFum@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01946.txt.bz2
Content-length: 1645
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88845
--- Comment #1 from Peter Bergner <bergner at gcc dot gnu.org> ---
After IRA, we have the following RTL with pseudo 124 being assigned to r9,
which does not meet the "f" constraint required by the inline asm:
(insn 6 5 7 2 (set (reg:SI 124)
(const_int 0 [0])) "pr88845.i":10:5 494 {*movsi_internal1}
(expr_list:REG_EQUIV (const_int 0 [0])
(nil)))
(insn 7 6 12 2 (parallel [
(asm_operands/v ("") ("") 0 [
(subreg:SF (reg:SI 124) 0)
]
[
(asm_input:SF ("f") pr88845.i:11)
]
[] pr88845.i:11)
(clobber (reg:SI 76 ca))
]) "pr88845.i":11:3 -1
(expr_list:REG_DEAD (reg:SI 124)
(expr_list:REG_UNUSED (reg:SI 76 ca)
(nil))))
LRA then generates the following:
(insn 6 5 14 2 (set (reg:SI 124)
(const_int 0 [0])) "pr88845.i":10:5 494 {*movsi_internal1}
(expr_list:REG_EQUIV (const_int 0 [0])
(nil)))
(insn 14 6 7 2 (set (reg:SF 125)
(subreg:SF (reg:SI 124) 0)) "pr88845.i":11:3 -1
(nil))
(insn 7 14 12 2 (parallel [
(asm_operands/v ("") ("") 0 [
(reg:SF 125)
]
[
(asm_input:SF ("f") pr88845.i:11)
]
[] pr88845.i:11)
(clobber (reg:SI 76 ca))
]) "pr88845.i":11:3 -1
(expr_list:REG_DEAD (reg:SI 124)
(expr_list:REG_UNUSED (reg:SI 76 ca)
(nil))))
...and we ICE in lra_set_insn_recog_data when handling the reload insn 14.
>From gcc-bugs-return-629138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:26:33 2019
Return-Path: <gcc-bugs-return-629138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36594 invoked by alias); 14 Jan 2019 18:26:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 36326 invoked by uid 48); 14 Jan 2019 18:26:29 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88846] New: [9 Regression] pr69776-2.c failure on 32 bit AIX
Date: Mon, 14 Jan 2019 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01947.txt.bz2
Content-length: 925
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88846
Bug ID: 88846
Summary: [9 Regression] pr69776-2.c failure on 32 bit AIX
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: dje at gcc dot gnu.org
CC: bergner at gcc dot gnu.org, segher at gcc dot gnu.org
Target Milestone: ---
Aliasing / LRA bug after combine.c change.
r265397
.f:
lwz 10,LC..2(2)
lwz 9,0(3)
lfd 0,0(10)
stfd 0,0(4)
stw 9,0(3)
blr
r265398
.f:
lwz 9,LC..2(2)
lfd 0,0(9)
stfd 0,0(4)
blr
-maix64
.f:
lwa 9,0(3)
ld 10,LC..2(2)
lfd 0,0(10)
stfd 0,0(4)
stw 9,0(3)
blr
>From gcc-bugs-return-629139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:27:29 2019
Return-Path: <gcc-bugs-return-629139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37851 invoked by alias); 14 Jan 2019 18:27: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 37765 invoked by uid 48); 14 Jan 2019 18:27:25 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88846] [9 Regression] pr69776-2.c failure on 32 bit AIX
Date: Mon, 14 Jan 2019 18:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: cf_gcctarget bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88846-4-fymUvyiziu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01948.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88846
David Edelsohn <dje at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |powerpc*-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
Ever confirmed|0 |1
--- Comment #1 from David Edelsohn <dje at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-629140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:29:26 2019
Return-Path: <gcc-bugs-return-629140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40778 invoked by alias); 14 Jan 2019 18:29:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40708 invoked by uid 48); 14 Jan 2019 18:29:22 -0000
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88846] [9 Regression] pr69776-2.c failure on 32 bit AIX
Date: Mon, 14 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dje at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88846-4-pE2LvYvE6J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01949.txt.bz2
Content-length: 749
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88846
--- Comment #2 from David Edelsohn <dje at gcc dot gnu.org> ---
(insn 9 2 7 2 (set (reg:DF 125)
(mem/u/c:DF (reg/f:SI 124) [0 S8 A64])) "pr69776-2.c":11:7 503
{*movdf_hardfloat32}
(expr_list:REG_DEAD (reg/f:SI 124)
(expr_list:REG_EQUIV (mem:DF (reg:SI 127) [2 *qd_4(D)+0 S8 A32])
(nil))))
the actual insn has the read as alias set 0
so aliasing anything
but, the REG_EQUIV has set 2
and LRA uses that here
that REG_EQUIV is put there by IRA (during the IRA pass, anyway)
the reason you don't get an REG_EQUIV added on linux is there already is one
(for the 0.0 in there; on AIX we don't have that for some reason)
dse1 has put it there (a REG_EQUAL actually)
>From gcc-bugs-return-629141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:41:10 2019
Return-Path: <gcc-bugs-return-629141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21110 invoked by alias); 14 Jan 2019 18:41: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 21046 invoked by uid 55); 14 Jan 2019 18:41:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88263] ICE in coverage_begin_function
Date: Mon, 14 Jan 2019 18:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88263-4-i29gzchi0B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01950.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88263
--- Comment #7 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Mon Jan 14 18:40:34 2019
New Revision: 267921
URL: https://gcc.gnu.org/viewcvs?rev=267921&root=gcc&view=rev
Log:
Fix location of tls_wrapper_fn (PR gcov-profile/88263).
2019-01-14 Martin Liska <mliska@suse.cz>
PR gcov-profile/88263
* decl2.c (get_tls_wrapper_fn): Use DECL_SOURCE_LOCATION
as location of the TLS wrapper.
2019-01-14 Martin Liska <mliska@suse.cz>
PR gcov-profile/88263
* g++.dg/gcov/pr88263-2.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/gcov/pr88263-2.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl2.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:43:04 2019
Return-Path: <gcc-bugs-return-629142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26186 invoked by alias); 14 Jan 2019 18:43:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26078 invoked by uid 48); 14 Jan 2019 18:43:01 -0000
From: "gary_mills at fastmail dot fm" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Mon, 14 Jan 2019 18:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gary_mills at fastmail dot fm
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-HYLXAddXg3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01951.txt.bz2
Content-length: 1249
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #31 from Gary Mills <gary_mills at fastmail dot fm> ---
When I built gcc-7 with even more configuration options, including
--enable-initfini-array, I got this segmentation fault on SPARC hardware:
configure:3662: checking for suffix of object files
configure:3684:
/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/xgcc
-B/export/home/mills/Downloads/code/oi-userland/components/developer/gcc-7/build/sparcv7/./gcc/
-B/usr/gcc/7/sparc-sun-solaris2.11/bin/
-B/usr/gcc/7/sparc-sun-solaris2.11/lib/ -isystem
/usr/gcc/7/sparc-sun-solaris2.11/include -isystem
/usr/gcc/7/sparc-sun-solaris2.11/sys-include -c -g -O2 -mno-app-regs
conftest.c >&5
conftest.c: In function 'main':
conftest.c:11:1: internal compiler error: Segmentation Fault
main ()
^~~~
conftest.c:11:1: internal compiler error: Abort
xgcc: internal compiler error: Abort (program cc1)
This is a known problem, and an old one. The --enable-initfini-array option is
not shown in the help output from gcc-7 configure. When I did a subsequent
build without that option, I got a successful build. It's quite possible that
this option was the source of all the problems.
>From gcc-bugs-return-629144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:44:32 2019
Return-Path: <gcc-bugs-return-629144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29241 invoked by alias); 14 Jan 2019 18:44: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 29098 invoked by uid 48); 14 Jan 2019 18:44:29 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Mon, 14 Jan 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88638-4-aL38gltM6P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01953.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Fixed via r267922.
>From gcc-bugs-return-629143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:44:24 2019
Return-Path: <gcc-bugs-return-629143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28443 invoked by alias); 14 Jan 2019 18:44:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 28173 invoked by uid 48); 14 Jan 2019 18:44:20 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88263] ICE in coverage_begin_function
Date: Mon, 14 Jan 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88263-4-Ux6ynMxGKh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88263-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01952.txt.bz2
Content-length: 437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88263
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
Fixed now.
>From gcc-bugs-return-629145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:44:36 2019
Return-Path: <gcc-bugs-return-629145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29772 invoked by alias); 14 Jan 2019 18:44: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 29207 invoked by uid 55); 14 Jan 2019 18:44:32 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88638] [9 Regression] FAIL: *string-format-1.* on darwin
Date: Mon, 14 Jan 2019 18:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88638-4-uDDKItaDAj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88638-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01954.txt.bz2
Content-length: 1675
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88638
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Author: msebor
Date: Mon Jan 14 18:44:00 2019
New Revision: 267922
URL: https://gcc.gnu.org/viewcvs?rev=267922&root=gcc&view=rev
Log:
PR target/88638 - FAIL: fsf-nsstring-format-1.s on darwin
gcc/c-family/ChangeLog:
PR target/88638
* c-attribs.c (positional_argument): Call valid_format_string_type_p
and issue errors if it fails.
* c-common.h (valid_format_string_type_p): Declare.
* c-format.c (valid_stringptr_type_p): Rename...
(valid_format_string_type_p): ...to this and make extern.
(handle_format_arg_attribute): Adjust to new name.
(check_format_string): Same.
gcc/testsuite/ChangeLog:
PR target/88638
* gcc.dg/format/attr-8.c: New test.
* gcc.dg/darwin-cfstring-format-1.c: Adjust diagnostics.
* gcc.dg/format/attr-3.c: Same.
* obj-c++.dg/fsf-nsstring-format-1.mm: Same.
* objc.dg/fsf-nsstring-format-1.m: Same.
gcc/ChangeLog:
PR target/88638
* doc/extend.texi (Darwin Format Checks): Clarify.
Added:
trunk/gcc/testsuite/gcc.dg/format/attr-8.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-attribs.c
trunk/gcc/c-family/c-common.h
trunk/gcc/c-family/c-format.c
trunk/gcc/doc/extend.texi
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/darwin-cfstring-format-1.c
trunk/gcc/testsuite/gcc.dg/format/attr-3.c
trunk/gcc/testsuite/obj-c++.dg/fsf-nsstring-format-1.mm
trunk/gcc/testsuite/objc.dg/fsf-nsstring-format-1.m
>From gcc-bugs-return-629146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 18:51:19 2019
Return-Path: <gcc-bugs-return-629146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51808 invoked by alias); 14 Jan 2019 18:51: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 51659 invoked by uid 55); 14 Jan 2019 18:51:14 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Mon, 14 Jan 2019 18:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87836-4-Mw8C27QKSd@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01955.txt.bz2
Content-length: 1182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
--- Comment #32 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #31 from Gary Mills <gary_mills at fastmail dot fm> ---
> When I built gcc-7 with even more configuration options, including
> --enable-initfini-array, I got this segmentation fault on SPARC hardware:
[...]
> conftest.c:11:1: internal compiler error: Abort
> xgcc: internal compiler error: Abort (program cc1)
>
> This is a known problem, and an old one. The --enable-initfini-array option is
> not shown in the help output from gcc-7 configure. When I did a subsequent
> build without that option, I got a successful build. It's quite possible that
> this option was the source of all the problems.
As I'd mentioned before, this doesn't astonish me in the least. It took
quite a bit of work for and with the Solaris linker engineers to get
that support right in ld and the configure test to pass. If you're
forcing that support when the test fails, it's quite likely that
something is not quite right with Illumos ld's support (which was only
added independently after Oracle closed down OpenSolaris).
>From gcc-bugs-return-629147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 19:14:42 2019
Return-Path: <gcc-bugs-return-629147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89609 invoked by alias); 14 Jan 2019 19:14: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 89530 invoked by uid 48); 14 Jan 2019 19:14:38 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Mon, 14 Jan 2019 19:14: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: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88791-4-Kfb2Ytf2bh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01956.txt.bz2
Content-length: 1187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #11 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to dominik.strasser from comment #10)
> Looking at the backtrace, the effects are very different between gcc 7.4 and
> 9.0. Making it work on a different glibc wouldn't help for me. CentOs 7.5 ==
> RHEL 7.5 which is the latest "commercial" Linux system. What could we do to
> make it work?
Hm, still, the glibc is really quite old. Anyway, let's try more debugging:
- using the GCC trunk, I would open the application in gdb and step through
GetThreadStackAndTls, please report which line triggers the signal (handled by
your app)? You can build libsanitizer with -O0 which will make debugging more
easier
- you can maybe build newer glibc, install it to a different location and then
use something like LD_PRELOAD to test newer GCC
- you can also -fsanitize=undefined, or -fsanitize=thread in order to test
whether other sanitizer work
- if you trust me, you can contact me personally and provide access to a system
where I can do a debugging
Anyway, I would be happy to help, but it's not so easy without a reproducer ;)
>From gcc-bugs-return-629148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 19:56:58 2019
Return-Path: <gcc-bugs-return-629148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85496 invoked by alias); 14 Jan 2019 19:56: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 84211 invoked by uid 48); 14 Jan 2019 19:56:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Mon, 14 Jan 2019 19:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-lFjWFisvlc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01957.txt.bz2
Content-length: 831
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If I add __attribute__((optimize (0))) to:
static unsigned
do_rpo_vn (function *fn, edge entry, bitmap exit_bbs,
bool iterate, bool eliminate)
and recompile stage2 tree-ssa-sccvn.o + relink stage2 cc1, then sort.i is the
same between stage1/cc1 and stage2/cc1.
../stage1-gcc/cc1plus tree-ssa-sccvn.ii -quiet -mtune=cortex-a9
-mfloat-abi=hard -mfpu=vfpv3-d16 -mtls-dialect=gnu -marm -march=armv7-a+fp -g
-gtoggle -O2 -fno-PIE -fno-checking -fno-exceptions -fno-rtti
-fasynchronous-unwind-tables -fno-ipa-ra -o tree-ssa-sccvn.s
compiled tree-ssa-sccvn.ii without that optimize (0) attribute still works
differently from stage1/cc1.
Let me attach tree-ssa-sccvn.ii and tree-ssa-sccvn.s.
>From gcc-bugs-return-629150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 19:59:58 2019
Return-Path: <gcc-bugs-return-629150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121370 invoked by alias); 14 Jan 2019 19:59: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 121289 invoked by uid 48); 14 Jan 2019 19:59:53 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Mon, 14 Jan 2019 19:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88714-4-jW0GF73LE0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01959.txt.bz2
Content-length: 270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #13 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45428
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45428&action=edit
tree-ssa-sccvn.s.xz
And resulting (bad) assembly
>From gcc-bugs-return-629149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 19:59:08 2019
Return-Path: <gcc-bugs-return-629149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118345 invoked by alias); 14 Jan 2019 19:59:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118270 invoked by uid 48); 14 Jan 2019 19:59:04 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Mon, 14 Jan 2019 19:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88714-4-MyX0stwERX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01958.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #12 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45427
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45427&action=edit
tree-ssa-sccvn.ii.xz
Preprocessed source
>From gcc-bugs-return-629151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 20:05:59 2019
Return-Path: <gcc-bugs-return-629151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33112 invoked by alias); 14 Jan 2019 20:05:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16009 invoked by uid 48); 14 Jan 2019 20:05:54 -0000
From: "husseydevin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88510] GCC generates inefficient U64x2/v2di scalar multiply for NEON32
Date: Mon, 14 Jan 2019 20: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: 8.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: husseydevin at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88510-4-22OpjRoq81@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88510-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01960.txt.bz2
Content-length: 3751
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88510
--- Comment #4 from Devin Hussey <husseydevin at gmail dot com> ---
I am deciding to refer to goodmul as ssemul from now on. I think it is a better
name.
I am also wondering if Aarch64 gets a benefit from this vs. scalarizing if the
value is already in a NEON register. I don't have an Aarch64 device to test on.
For the reference, I use an LG G3 with a Snapdragon 801 (Cortex-A15)
underclocked to 4 cores @ 1.7 GHz.
I also did some testing, and twomul is also fastest if a value can be
interleaved outside of the loop (e.g. a constant). ssemul is only fastest if
either both operands can be interleaved beforehand or the high or low bits are
known to be zero in which it can be simplified.
For example, the xxHash64 routine, which looks like this:
const U8 *p;
const U8 *limit = p + len - 31;
U64x2 v[2];
...
do {
// Actually unrolled
for (int i = 0; i < 2; i++) {
// Load (U8 load because alignment is dumb)
U64x2 inp = vreinterpretq_u64_u8(vld1q_u8(p));
p += 16;
v[i] += inp * PRIME64_2;
v[i] = (v[i] << 31) | (v[i] >> (64 - 31));
v[i] *= PRIME64_1;
}
} while (p < limit);
seems to be the fastest when implemented like this:
// Wordswap and separate low bits for twomul
const U64x2 prime1Base = vdupq_n_u64(PRIME64_1);
const U32x2 prime1Lo = vmovn_u64(prime1Base);
const U32x4 prime1Rev = vrev64q_u32(vreinterpretq_u32_u64(prime1Base));
// Interleave for ssemul
_Alignas(16) const U64 PRIME2[2] = { PRIME64_2, PRIME64_2 };
const U32x2x2 prime2 = vld2_u32((const U32 *)__builtin_assume_aligned(PRIME2,
16));
U64x2 v[2];
do {
// actually unrolled
for (int i = 0; i < 2; i++) {
// Interleaved load
U32x2x2 inp = vld2_u32((const U32 *)p);
p += 16;
// ssemul
// val = (U64x2)inpLo * (U64x2)prime2Hi;
U64x2 val = vmull_u32(inp.val[0], prime2.val[1]);
// val += (U64x2)inpHi * (U64x2)prime2Lo;
val = vmlal_u32(val, inp.val[1], prime2.val[0]);
// val <<= 32;
val = vshlq_n_u64(val, 32);
// val += (U64x2)inpLo * (U64x2)prime2Lo;
val = vmlal_u32(val, inp.val[0], prime2.val[0]);
// end ssemul
// Add
v[i] = vaddq_u64(v[i], val);
// Rotate left
v[i] = vsriq_n_u64(vshlq_n_u64(v[i], 31), v[i], 33);
// twomul
// topLo = v[i] & 0xFFFFFFFF;
U32x2 topLo = vmovn_u64(v[i]);
// top = (U32x4)v[i];
U32x4 top = vreinterpretq_u32_u64(v[i]);
// prod = {
// topLo * prime1Hi,
// topHi * prime1Lo
// };
U32x4 prod = vmulq_u32(top, prime1Rev);
// prod64 = (U64x2)prod[0] + (U64x2)prod[1];
U64x2 prod64 = vpaddlq_u32(prod);
// prod64 <<= 32;
prod64 = vshlq_n_u64(prod64, 32);
// prod64 += (U64x2)topLo * (U64x2)prime1Lo;
prod64 = vmlal_u32(prod64, topLo, prime1Lo);
// end twomul
}
} while (p < limit);
As you can see, since we can do an interleaved load on p, it is fastest to do
ssemul, however, since we are using v for more than just multiplication, we use
twomul.
On my G3 in Termux with the xxhsum 100 KB benchmark, this gets to 2.65 GB/s,
compared to 0.8 GB/s scalar and 2.24 GB/s with both of them using ssemul.
However, this was compiled with Clang. For some reason, even though I see no
major differences in the assembly, GCC consistently produces code at roughly
80% the performance of Clang. But this is mostly an algorithm thing, that isn't
important.
Considering that this is 64-bit arithmetic on a 32-bit device, that is pretty
good.
>From gcc-bugs-return-629152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 20:09:46 2019
Return-Path: <gcc-bugs-return-629152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38687 invoked by alias); 14 Jan 2019 20:09: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 32867 invoked by uid 55); 14 Jan 2019 20:09:41 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] [9 Regression] ice in maybe_emit_vtables
Date: Mon, 14 Jan 2019 20:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88830-4-bYzCYxzl2B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01961.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Mon Jan 14 20:09:10 2019
New Revision: 267924
URL: https://gcc.gnu.org/viewcvs?rev=267924&root=gcc&view=rev
Log:
PR c++/88830 - ICE with abstract class.
* decl2.c (maybe_emit_vtables): Check CLASSTYPE_LAZY_DESTRUCTOR.
Fix formatting.
* g++.dg/other/abstract7.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/other/abstract7.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/decl2.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 20:11:04 2019
Return-Path: <gcc-bugs-return-629153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80168 invoked by alias); 14 Jan 2019 20:11:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80096 invoked by uid 48); 14 Jan 2019 20:11:00 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88830] [9 Regression] ice in maybe_emit_vtables
Date: Mon, 14 Jan 2019 20:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88830-4-zeeaUlfrne@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01962.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88830
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 20:41:52 2019
Return-Path: <gcc-bugs-return-629154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48116 invoked by alias); 14 Jan 2019 20:41:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48008 invoked by uid 48); 14 Jan 2019 20:41:48 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Mon, 14 Jan 2019 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-l7oY0nMa98@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01963.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
That said, if I compile this with r267800 (cross-compiler, but identical output
to the attached one) and then on the problematic do_rpo_vn function return in
gdb at the start of make_more_copies so effectively undo r265398 for that
function, it still fails (== produces different sort.s from stage1).
Could somebody familiar with ARM have a look at this?
>From gcc-bugs-return-629155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 21:03:55 2019
Return-Path: <gcc-bugs-return-629155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19980 invoked by alias); 14 Jan 2019 21:03: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 7589 invoked by uid 48); 14 Jan 2019 21:03:51 -0000
From: "sje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85711] ICE in aarch64_classify_address, at config/aarch64/aarch64.c:5678
Date: Mon, 14 Jan 2019 21: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sje at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85711-4-7sAP496e4L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85711-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85711-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01964.txt.bz2
Content-length: 241
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85711
--- Comment #2 from Steve Ellcey <sje at gcc dot gnu.org> ---
This has been failing for quite a while now and there is apparently a fix for
it. Can we get it fixed for GCC 9.0 release?
>From gcc-bugs-return-629156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 21:05:48 2019
Return-Path: <gcc-bugs-return-629156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69911 invoked by alias); 14 Jan 2019 21:05:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59517 invoked by uid 48); 14 Jan 2019 21:05:44 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88847] New: gcc.target/aarch64/sve/struct_move_1.c ICE with -fstack-protector-strong
Date: Mon, 14 Jan 2019 21:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01965.txt.bz2
Content-length: 2035
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88847
Bug ID: 88847
Summary: gcc.target/aarch64/sve/struct_move_1.c ICE with
-fstack-protector-strong
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
Target: aarch64-unknown-linux-gnu
$ ./cc1 -quiet struct_move_1.c -march=armv8.2-a+sve -msve-vector-bits=256
-mbig-endian -fstack-protector-strong
struct_move_1.c: In function ‘f2_vnx32qi’:
struct_move_1.c:60:1: error: unrecognizable insn:
60 | TEST_TYPE (vnx32qi, z0, z2)
| ^~~~~~~~~
(insn 12 11 13 2 (set (mem/c:VNx32QI (plus:DI (reg/f:DI 85 virtual-stack-vars)
(const_int -80 [0xffffffffffffffb0])) [3 x+0 S64 A128])
(unspec:VNx32QI [
(reg:VNx16BI 93)
(reg:VNx32QI 94)
] UNSPEC_MERGE_PTRUE)) "struct_move_1.c":60:1 -1
(nil))
during RTL pass: vregs
struct_move_1.c:60:1: internal compiler error: in extract_insn, at recog.c:2305
0x59c1ab _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/polacek/src/gcc/gcc/rtl-error.c:108
0x59c1e3 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/polacek/src/gcc/gcc/rtl-error.c:116
0xb8dfaf extract_insn(rtx_insn*)
/home/polacek/src/gcc/gcc/recog.c:2305
0x90ea87 instantiate_virtual_regs_in_insn
/home/polacek/src/gcc/gcc/function.c:1605
0x90ea87 instantiate_virtual_regs
/home/polacek/src/gcc/gcc/function.c:1975
0x90ea87 execute
/home/polacek/src/gcc/gcc/function.c:2024
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
Without -fstack-protector-strong it compiles fine.
>From gcc-bugs-return-629157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 21:08:40 2019
Return-Path: <gcc-bugs-return-629157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4448 invoked by alias); 14 Jan 2019 21:08: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 4372 invoked by uid 48); 14 Jan 2019 21:08:37 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57297] FAIL: gfortran.dg/select_type_4.f90 -O2 execution test
Date: Mon, 14 Jan 2019 21:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-57297-4-WZ8MHubFdK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57297-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57297-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01966.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57297
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #11 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is the problem still present? I cannot reproduce it.
>From gcc-bugs-return-629159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 21:14:47 2019
Return-Path: <gcc-bugs-return-629159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11276 invoked by alias); 14 Jan 2019 21:14:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11209 invoked by uid 48); 14 Jan 2019 21:14:43 -0000
From: "bergner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88845] ICE in lra_set_insn_recog_data, at lra.c:1010
Date: Mon, 14 Jan 2019 21:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bergner at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88845-4-hYetswEsG5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01968.txt.bz2
Content-length: 389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88845
--- Comment #2 from Peter Bergner <bergner at gcc dot gnu.org> ---
Thinking about this, insn 14 doesn't look legal to me for ppc, since FP values
in our FP regs are actually stored as 64-bit quantities, even for SFmode, so
copying a 32-bit SImode value over to a 64-bit wide reg holding a SFmode value
doesn't make sense, correct?
>From gcc-bugs-return-629158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 21:14:10 2019
Return-Path: <gcc-bugs-return-629158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10273 invoked by alias); 14 Jan 2019 21:14:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10203 invoked by uid 48); 14 Jan 2019 21:14:06 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51788] Unstable gfc_verify_binding_labels check for a binding label which collides with a global entity
Date: Mon, 14 Jan 2019 21:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.7.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-51788-4-8y3qXsEAL9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01967.txt.bz2
Content-length: 401
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51788
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Is this still a problem?
>From gcc-bugs-return-629160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 22:02:00 2019
Return-Path: <gcc-bugs-return-629160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15964 invoked by alias); 14 Jan 2019 22:02:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15792 invoked by uid 55); 14 Jan 2019 22:01:56 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvODg4MjVdIFs3LzgvOSBSZWdyZXNzaW9uXSBJQ0Ugb24gKGlu?= =?UTF-8?B?dmFsaWQpIEMrKzExIGNvZGU6IHRyZWUgY2hlY2s6IGV4cGVjdGVkIGNsYXNz?= =?UTF-8?B?IOKAmHR5cGXigJksIGhhdmUg4oCYZXhjZXB0aW9uYWzigJkgKGVycm9yX21h?= =?UTF-8?B?cmspIGluIGNhbl9kb19ucnZvX3AsIGF0IGNwL3R5cGVjay5jOjkzNjE=?Date: Mon, 14 Jan 2019 22:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88825-4-CfjYWuetgG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01969.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88825
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Mon Jan 14 22:01:24 2019
New Revision: 267926
URL: https://gcc.gnu.org/viewcvs?rev=267926&root=gcc&view=rev
Log:
PR c++/88825 - ICE with bogus function return type deduction.
* typeck.c (can_do_nrvo_p): Check error_mark_node.
* g++.dg/cpp1y/auto-fn55.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp1y/auto-fn55.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/typeck.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 22:04:09 2019
Return-Path: <gcc-bugs-return-629161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20162 invoked by alias); 14 Jan 2019 22:04: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 20099 invoked by uid 48); 14 Jan 2019 22:04:05 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBjKysvODg4MjVdIFs3LzgvOSBSZWdyZXNzaW9uXSBJQ0Ugb24gKGlu?= =?UTF-8?B?dmFsaWQpIEMrKzExIGNvZGU6IHRyZWUgY2hlY2s6IGV4cGVjdGVkIGNsYXNz?= =?UTF-8?B?IOKAmHR5cGXigJksIGhhdmUg4oCYZXhjZXB0aW9uYWzigJkgKGVycm9yX21h?= =?UTF-8?B?cmspIGluIGNhbl9kb19ucnZvX3AsIGF0IGNwL3R5cGVjay5jOjkzNjE=?Date: Mon, 14 Jan 2019 22:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88825-4-DiFvCPSClj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01970.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88825
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed. This is ice-on-invalid so not going to backport.
>From gcc-bugs-return-629163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 22:53:18 2019
Return-Path: <gcc-bugs-return-629163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57609 invoked by alias); 14 Jan 2019 22:53: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 57565 invoked by uid 48); 14 Jan 2019 22:53:14 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/33430] Improve -finit-*: Initialization of derived types, equivalenced variables, allocated arrays
Date: Mon, 14 Jan 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-33430-4-aGHLdYCXwZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-33430-4@http.gcc.gnu.org/bugzilla/>
References: <bug-33430-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01972.txt.bz2
Content-length: 260
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=33430
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Patch proposed at https://gcc.gnu.org/ml/fortran/2016-03/msg00014.html.
This has been committed at revision r239489 (2016-08-15).
>From gcc-bugs-return-629162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 22:53:03 2019
Return-Path: <gcc-bugs-return-629162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56829 invoked by alias); 14 Jan 2019 22:53: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 56752 invoked by uid 48); 14 Jan 2019 22:52:58 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51310] -finit-bla doesn't initialize *all* items of type bla to the requested constant.
Date: Mon, 14 Jan 2019 22:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: toon at moene dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51310-4-qFuQwYc6V4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51310-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51310-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01971.txt.bz2
Content-length: 810
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51310
--- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Output from the test in comment 0 is now
NaN 0.0000000000000000 NaN
n= 3
a= NaN NaN
NaN
var= NaN
b= NaN NaN
NaN
c= 0.0000000000000000 0.0000000000000000 0.0000000000000000
i.e., the allocated allocatable arrays are not initialized.
Toon do you still want to have this PR assigned to you?
This PR is also related to pr33430.
>From gcc-bugs-return-629164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:00:50 2019
Return-Path: <gcc-bugs-return-629164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65484 invoked by alias); 14 Jan 2019 23:00:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65440 invoked by uid 48); 14 Jan 2019 23:00:45 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/88805] hidden symbol `__cpu_model' is referenced by DSO
Date: Mon, 14 Jan 2019 23:00: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88805-4-lvf1GzORgt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88805-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01973.txt.bz2
Content-length: 413
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88805
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-14
Ever confirmed|0 |1
>From gcc-bugs-return-629165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:09:37 2019
Return-Path: <gcc-bugs-return-629165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102975 invoked by alias); 14 Jan 2019 23:09: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 102917 invoked by uid 48); 14 Jan 2019 23:09:32 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/82456] missing -Wstringop-overflow on strcpy reading past the end of an array
Date: Mon, 14 Jan 2019 23:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on see_also everconfirmed cf_known_to_fail
Message-ID: <bug-82456-4-sk5wf0N9GP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82456-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82456-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01974.txt.bz2
Content-length: 1800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82456
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-14
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=81437
Ever confirmed|0 |1
Known to fail| |7.3.0, 8.2.0, 9.0
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
GCC 8.2.0 and 9 issue two warnings, one for each of fcst and frng, but none for
gcst or grng, so confirming those are still missing.
See also bug 81437 for a similar (the same?) problem.
$ gcc -O2 -S -Wall z.c
z.c: In function ‘fcst’:
z.c:5:3: warning: array subscript 3 is above array bounds of ‘char[2]’
[-Warray-bounds]
__builtin_strcpy (d, a + 3); // -Warray-bounds (good)
^~~~~~~~~~~~~~~~~~~~~~~~~~~
z.c:5:3: warning: ‘__builtin_strcpy’ offset 3 is out of the bounds [0, 2] of
object ‘a’ with type ‘char[2]’ [-Warray-bounds]
z.c:3:8: note: ‘a’ declared here
char a[2] = "0";
^
z.c: In function ‘frng’:
z.c:16:3: warning: ‘__builtin_strcpy’ offset [3, 2147483647] is out of the
bounds [0, 2] of object ‘a’ with type ‘char[2]’ [-Warray-bounds]
__builtin_strcpy (d, a + i); // both warnings missing
^~~~~~~~~~~~~~~~~~~~~~~~~~~
z.c:11:8: note: ‘a’ declared here
char a[2] = "0";
^
>From gcc-bugs-return-629166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:13:43 2019
Return-Path: <gcc-bugs-return-629166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106381 invoked by alias); 14 Jan 2019 23: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 106333 invoked by uid 48); 14 Jan 2019 23:13:38 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/81437] missing -Wstringop-overflow reading past the end of a string
Date: Mon, 14 Jan 2019 23:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_fail
Message-ID: <bug-81437-4-OUK16a4QEh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81437-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81437-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01975.txt.bz2
Content-length: 1437
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81437
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to fail| |8.2.0, 9.0
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
GCC 9 prints the two warnings below with -m64 as well as -m32. GCC 8.2.0
prints them too but only in LP64 mode. With -m32, it only warns about g.
$ gcc -O2 -S -Wall -m32 a.c
a.c: In function ‘g’:
a.c:12:3: warning: ‘__builtin_memcpy’ forming offset 5 is out of the bounds [0,
4] of object ‘a’ with type ‘const char[4]’ [-Warray-bounds]
12 | __builtin_memcpy (d, a + 4, n); // missing warning
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a.c:10:14: note: ‘a’ declared here
10 | const char a[] = "123";
| ^
a.c: In function ‘f’:
a.c:5:3: warning: ‘__builtin_memcpy’ forming offset [5, 2147483651] is out of
the bounds [0, 4] of object ‘a’ with type ‘const char[4]’ [-Warray-bounds]
5 | __builtin_memcpy (d, a + 4, n); // warning (ok)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a.c:3:14: note: ‘a’ declared here
3 | const char a[] = "123";
| ^
>From gcc-bugs-return-629167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:26:57 2019
Return-Path: <gcc-bugs-return-629167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15156 invoked by alias); 14 Jan 2019 23:26:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15105 invoked by uid 48); 14 Jan 2019 23:26:52 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
Date: Mon, 14 Jan 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88443-4-PxqktZkVGS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88443-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88443-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01976.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
Bug 88443 depends on bug 86552, which changed state.
Bug 86552 Summary: missing warning for reading past the end of non-string arrays
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86552
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-629168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:26:57 2019
Return-Path: <gcc-bugs-return-629168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15163 invoked by alias); 14 Jan 2019 23:26:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15080 invoked by uid 48); 14 Jan 2019 23:26:52 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86552] missing warning for reading past the end of non-string arrays
Date: Mon, 14 Jan 2019 23:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work blocked resolution target_milestone
Message-ID: <bug-86552-4-hjJjBqNd7K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86552-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86552-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01977.txt.bz2
Content-length: 821
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86552
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Known to work| |9.0
Blocks| |88443
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #6 from Martin Sebor <msebor at gcc dot gnu.org> ---
The warning has been implemented in GCC 9 via r264585 (strlen), r264327
(strcpy), and r264822 (sprintf).
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88443
[Bug 88443] [meta-bug] bogus/missing -Wstringop-overflow warnings
>From gcc-bugs-return-629169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:38:01 2019
Return-Path: <gcc-bugs-return-629169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97125 invoked by alias); 14 Jan 2019 23:38: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 94873 invoked by uid 48); 14 Jan 2019 23:37:57 -0000
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88777] [9 Regression] Out-of-range offsets building glibc test-tgmath2.c for hppa-linux-gnu
Date: Mon, 14 Jan 2019 23:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: danglin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: amodra at gmail dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88777-4-LT5WsPVWtV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88777-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01978.txt.bz2
Content-length: 435
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88777
John David Anglin <danglin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from John David Anglin <danglin at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Jan 14 23:54:36 2019
Return-Path: <gcc-bugs-return-629170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126399 invoked by alias); 14 Jan 2019 23:54: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 123935 invoked by uid 48); 14 Jan 2019 23:54:32 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Mon, 14 Jan 2019 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-gKpar5zeoA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01979.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #11 from ДилÑн Палаузов <dilyan.palauzov at aegee dot org> ---
According to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345#c4 it does not
matter whether liblto_plugin.so.0.0.0 from GCC7 or 8 is installed under
$libdir/bfd-plugins: both work for both compiler versions.
>From gcc-bugs-return-629171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 00:08:56 2019
Return-Path: <gcc-bugs-return-629171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55436 invoked by alias); 15 Jan 2019 00:08: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 55384 invoked by uid 48); 15 Jan 2019 00:08:52 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88800] Spurious -Werror=array-bounds for non-taken branch
Date: Tue, 15 Jan 2019 00:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component
Message-ID: <bug-88800-4-OkpO8CtyCo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88800-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01980.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88800
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
Component|c++ |tree-optimization
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00810.html
>From gcc-bugs-return-629172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 00:25:38 2019
Return-Path: <gcc-bugs-return-629172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88872 invoked by alias); 15 Jan 2019 00:25:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88717 invoked by uid 48); 15 Jan 2019 00:25:33 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88848] New: member ambiguous in multiple inheritance lattice
Date: Tue, 15 Jan 2019 00:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01981.txt.bz2
Content-length: 2305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88848
Bug ID: 88848
Summary: member ambiguous in multiple inheritance lattice
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
clang++/icc compile this fine, but g++ says:
bz.C: In substitution of ‘template<class ... ARGS> template<int VALUE> using
Type_t = decltype (#‘using_decl’ not supported by dump_expr#<expression
error>(Integer<VALUE>{})) [with int VALUE = Integer<4>::value; ARGS = {Foo<4,
float>, Foo<8, double>}]’:
bz.C:21:54: required from ‘struct Bar<Foo<4, float>, Foo<8, double> >’
bz.C:30:38: required from here
bz.C:21:35: error: request for member ‘get_type’ is ambiguous in multiple
inheritance lattice
21 | using Type_t = decltype(get_type(Integer<VALUE>{}));
| ~~~~~~~~^~~~~~~~~~~~~~~~~~
bz.C:12:15: note: candidates are: ‘static TYPE Foo<VALUE,
TYPE>::get_type(Foo<VALUE, TYPE>::Integer_t) [with int VALUE = 8; TYPE =
double; Foo<VALUE, TYPE>::Integer_t = Integer<8>]’
12 | static TYPE get_type(Integer_t);
| ^~~~~~~~
bz.C:12:15: note: ‘static TYPE Foo<VALUE,
TYPE>::get_type(Foo<VALUE, TYPE>::Integer_t) [with int VALUE = 4; TYPE = float;
Foo<VALUE, TYPE>::Integer_t = Integer<4>]’
template<typename>
struct True { static constexpr bool value{ true }; };
template<int VALUE>
struct Integer { static constexpr int value{ VALUE }; };
template<int VALUE, typename TYPE>
struct Foo
{
using Integer_t = Integer<VALUE>;
static TYPE get_type(Integer_t);
};
template<typename... ARGS>
struct Bar : ARGS...
{
using ARGS::get_type...;
template<int VALUE>
using Type_t = decltype(get_type(Integer<VALUE>{}));
Bar() { static_assert((True< Type_t<ARGS::Integer_t::value> >::value &&
...)); }
static_assert((True< Type_t<ARGS::Integer_t::value> >::value && ...));
};
int main()
{
Bar<Foo<4, float>, Foo<8, double>> obj;
return int{ sizeof(obj) };
}
>From gcc-bugs-return-629173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 00:28:04 2019
Return-Path: <gcc-bugs-return-629173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92292 invoked by alias); 15 Jan 2019 00:28: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 92086 invoked by uid 48); 15 Jan 2019 00:28:00 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88848] member ambiguous in multiple inheritance lattice
Date: Tue, 15 Jan 2019 00: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: unknown
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88848-4-MzmejpAVxT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01982.txt.bz2
Content-length: 397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88848
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Not a regression AFAICS.
>From gcc-bugs-return-629174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 00:46:04 2019
Return-Path: <gcc-bugs-return-629174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3967 invoked by alias); 15 Jan 2019 00:46:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3953 invoked by uid 89); 15 Jan 2019 00:46:03 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=4.5 required=5.0 testsºYES_80,GIT_PATCH_2,HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,KAM_LAZY_DOMAIN_SECURITY,MISSING_MID,RCVD_IN_PBL,RCVD_IN_RP_RNBL,RCVD_IN_XBL autolearn=no version=3.3.2 spammy=H*RU:SKY-20150219JSJ, H*r:SKY-20150219JSJ, Hx-spam-relays-external:SKY-20150219JSJ, C
X-HELO: kems.com
Received: from Unknown (HELO kems.com) (61.190.160.170) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 15 Jan 2019 00:46:02 +0000
Received: from SKY-20150219JSJ ([127.0.0.1]) by localhost via TCP with ESMTPA; Tue, 15 Jan 2019 08:45:48 +0800
MIME-Version: 1.0
From: nfbfpepr <nfbfpepr@kems.com>
Sender: nfbfpepr <nfbfpepr@kems.com>
To: gcc-bugs@gcc.gnu.org
Date: Tue, 15 Jan 2019 00:46:00 -0000
Subject: =?utf-8?B?5ZCIZeazlUPnu49v6JClUQ==?Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
X-SW-Source: 2019-01/txt/msg01983.txt.bz2
Content-length: 436
5YqeaEogDQombmJzcDsNCueQhiZuYnNwOyZuYnNwOyQmbmJzcDsmbmJzcDsg
Vivkv6FbIQ0KJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7IC0tLS0tLQ0KJmFtcDsmbmJzcDsmbmJzcDsm
bmJzcDskJm5ic3A7Jm5ic3A7IEkgMyA0DQrpq64mbmJzcDsmbmJzcDskJm5i
c3A7Jm5ic3A7MjIyNg0KJmFtcDsmbmJzcDsmbmJzcDsmbmJzcDskJm5ic3A7
MjY2NA0K5ryCICQmbmJzcDsgK1EyNjI4NTU4NTc5DQombmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgLS0tLS0yMDE5
LzEvMTU>From gcc-bugs-return-629175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 02:38:06 2019
Return-Path: <gcc-bugs-return-629175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93832 invoked by alias); 15 Jan 2019 02: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 93798 invoked by uid 48); 15 Jan 2019 02:38:02 -0000
From: "wangchang15 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88831] the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Tue, 15 Jan 2019 02:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wangchang15 at huawei 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: cc attachments.created
Message-ID: <bug-88831-4-Jql9eWe6sK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01984.txt.bz2
Content-length: 1212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88831
wangchang15 <wangchang15 at huawei dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wangchang15 at huawei dot com
--- Comment #3 from wangchang15 <wangchang15 at huawei dot com> ---
Created attachment 45429
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45429&action=edit
C testcase source code
My PC OS is ubuntu 16.
The attachment is the source code temp.c.
This testcase requires a csmith runtime.
We use a version 2.1.0 of csmith tool which can be downloaded from following
URL.
http://embed.cs.utah.edu/csmith/
To build the csmith runtime, you need to run following commands.
cd [csmith-root]
./configure
make
The directory layout of my test is as follows.
The directory csmith is the csmith runtime ([csmith-root]).
$MYTEST/temp.c
$MYTEST/csmith
By running command " /some/path/to/my/cross/compiler/aarch64-linux-gnu-gcc
temp.c -static -O2 -I ./csmith/runtime -fcompare-debug=-g -lm -w -o
./temp_O2.exe ", the error message "-fcompare-debug failure (length)" will
arise.
>From gcc-bugs-return-629176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 02:42:26 2019
Return-Path: <gcc-bugs-return-629176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97890 invoked by alias); 15 Jan 2019 02:42:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97826 invoked by uid 48); 15 Jan 2019 02:42:22 -0000
From: "wangchang15 at huawei dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88831] the layout of .data section of a binary is slightly changed when -g option is enabled.
Date: Tue, 15 Jan 2019 02:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wangchang15 at huawei 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-88831-4-BSOtYje9mb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01985.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88831
--- Comment #4 from wangchang15 <wangchang15 at huawei dot com> ---
(In reply to Richard Biener from comment #2)
> This shouldn't happen. Can you please provide a complete testcase?
Hi,Richard, my reply to your comment is comment #3.
>From gcc-bugs-return-629177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 03:23:55 2019
Return-Path: <gcc-bugs-return-629177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23436 invoked by alias); 15 Jan 2019 03:23: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 23335 invoked by uid 48); 15 Jan 2019 03:23:49 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Tue, 15 Jan 2019 03:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88682-4-MIF9E2V4zw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01986.txt.bz2
Content-length: 230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Yes this does violate aliasing rules. Easy fix is to add may_alias to the
attributes of unaligned_int128_t.
>From gcc-bugs-return-629178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 03:35:16 2019
Return-Path: <gcc-bugs-return-629178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33409 invoked by alias); 15 Jan 2019 03:35: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 33361 invoked by uid 48); 15 Jan 2019 03:35:11 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex float load
Date: Tue, 15 Jan 2019 03:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-GHwTD0Mw7n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01987.txt.bz2
Content-length: 1045
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #7 from åˆ˜è¢‹é¼ <crazylht at gmail dot com> ---
Simple testcase below related to read_complex_part/write_complex_part
cat complex.c
_Complex float
foo (_Complex float a, _Complex float b)
{
_Complex float c,d;
c = a + b;
return c;
}
cat complex.s
.file "complex.c"
.text
.p2align 4
.globl foo
.type foo, @function
foo:
.LFB0:
.cfi_startproc
movq %xmm0, %rax
movq %xmm1, %rdx
vaddss %xmm1, %xmm0, %xmm0
shrq $32, %rax
shrq $32, %rdx
vmovd %eax, %xmm3
vmovd %edx, %xmm4
vaddss %xmm4, %xmm3, %xmm2
vmovd %xmm0, %edx
vmovd %xmm2, %eax
salq $32, %rax
orq %rdx, %rax
movq %rax, %xmm0
ret
.cfi_endproc
.LFE0:
.size foo, .-foo
.ident "GCC: (GNU) 9.0.0 20190110 (experimental)"
.section .note.GNU-stack,"",@progbits
>From gcc-bugs-return-629179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 05:56:03 2019
Return-Path: <gcc-bugs-return-629179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46785 invoked by alias); 15 Jan 2019 05:56:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46719 invoked by uid 48); 15 Jan 2019 05:55:58 -0000
From: "heavy.watal at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88849] New: std::binomial_distribution generates slightly larger values than expected
Date: Tue, 15 Jan 2019 05:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: heavy.watal 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-88849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01988.txt.bz2
Content-length: 1819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88849
Bug ID: 88849
Summary: std::binomial_distribution generates slightly larger
values than expected
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: heavy.watal at gmail dot com
Target Milestone: ---
Created attachment 45430
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45430&action=edit
Visualization of the distribution difference
Here is a reproducible example:
https://github.com/heavywatal/scribble/tree/master/cxx/binomial
The sum of 10000 values from std::binomial_distribution(1000, 0.01) was
calculated 1000 times. Those from libstdc++ are slightly larger than expected.
Environment:
macOS 10.14.2
g++-8 -v
Using built-in specs.
COLLECT_GCC=g++-8
COLLECT_LTO_WRAPPER=/usr/local/Cellar/gcc/8.2.0/libexec/gcc/x86_64-apple-darwin18.0.0/8.2.0/lto-wrapper
Target: x86_64-apple-darwin18.0.0
Configured with: ../configure --build=x86_64-apple-darwin18.0.0
--prefix=/usr/local/Cellar/gcc/8.2.0
--libdir=/usr/local/Cellar/gcc/8.2.0/lib/gcc/8
--enable-languages=c,c++,objc,obj-c++,fortran --program-suffix=-8
--with-gmp=/usr/local/opt/gmp --with-mpfr=/usr/local/opt/mpfr
--with-mpc=/usr/local/opt/libmpc --with-isl=/usr/local/opt/isl
--with-system-zlib --enable-checking=release --with-pkgversion='Homebrew GCC
8.2.0' --with-bugurl=https://github.com/Homebrew/homebrew-core/issues
--disable-nls --disable-multilib --with-native-system-header-dir=/usr/include
--with-sysroot=/Library/Developer/CommandLineTools/SDKs/MacOSX.sdk
Thread model: posix
gcc version 8.2.0 (Homebrew GCC 8.2.0)
>From gcc-bugs-return-629180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 06:50:56 2019
Return-Path: <gcc-bugs-return-629180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38236 invoked by alias); 15 Jan 2019 06:50: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 38093 invoked by uid 48); 15 Jan 2019 06:50:52 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Tue, 15 Jan 2019 06:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80762-4-JrxdvRmGK2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01989.txt.bz2
Content-length: 228
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
--- Comment #11 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hi Jonathan,
I'm still seeing it on a build started at r267915, perhaps something is still
missing?
>From gcc-bugs-return-629181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 07:16:56 2019
Return-Path: <gcc-bugs-return-629181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108089 invoked by alias); 15 Jan 2019 07:16: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 103782 invoked by uid 48); 15 Jan 2019 07:16:51 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88850] New: [9 Regression] Hard register coming out of expand causing reload to fail.
Date: Tue, 15 Jan 2019 07:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01990.txt.bz2
Content-length: 1503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88850
Bug ID: 88850
Summary: [9 Regression] Hard register coming out of expand
causing reload to fail.
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tnfchris at gcc dot gnu.org
Target Milestone: ---
Target: arm-none-linux-gnueabihf
The following testcase
typedef __builtin_neon_qi int8x8_t __attribute__ ((__vector_size__ (8)));
void
foo (int8x8_t z, int8x8_t x, int8x8_t v)
{
__builtin_neon_vuzpv8qi (&v, z, x);
}
ICEs when compiled with
-marm -O2 -march=armv7-a -mfloat-abi=softfp -mfpu=neon -S
-specs=aprofile-validation.specs -Wno-implicit-function-declaration
during reload
pr51968.c:12:1: error: insn does not satisfy its constraints:
12 | }
| ^
(insn 14 13 9 2 (set (reg:V8QI 6 r6 [113])
(reg:V8QI 0 r0 [ z ]))
"/data/tamchr01/gnu-work/src/gcc/gcc/testsuite/gcc.target/arm/pr51968.c":10:1
936 {*neon_movv8qi}
(nil))
during RTL pass: reload
it seems that the address taking of &v is causing it to emit hard registers
(r2) from expand already.
out of expand_call we get
(insn 3 2 4 2 (set (reg/v:V8QI 111 [ xD.5505 ])
(reg:V8QI 2 r2 [ xD.5505 ])) "pr51968.c":10:1 -1
(nil))
but have yet to figure out why.. the pattern itself seems sane to me..
>From gcc-bugs-return-629182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 07:25:04 2019
Return-Path: <gcc-bugs-return-629182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51487 invoked by alias); 15 Jan 2019 07:25:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51068 invoked by uid 48); 15 Jan 2019 07:24:59 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88851] New: [9 Regression] SVE Stack clash and r263173 use conflicting registers
Date: Tue, 15 Jan 2019 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01991.txt.bz2
Content-length: 701
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88851
Bug ID: 88851
Summary: [9 Regression] SVE Stack clash and r263173 use
conflicting registers
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: tnfchris at gcc dot gnu.org
Target Milestone: ---
Target: aarch64*-*-*
When SVE + stack clash protection and the feature introduced in r263173 use the
same r15 as scratch, making both protections invalid when used together.
One register needs to be re-numbered.
>From gcc-bugs-return-629183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 07:33:19 2019
Return-Path: <gcc-bugs-return-629183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77310 invoked by alias); 15 Jan 2019 07:33:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76080 invoked by uid 48); 15 Jan 2019 07:33:14 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43136] Excess copy-in/copy-out with character argument
Date: Tue, 15 Jan 2019 07:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-43136-4-qBPsrq6KDN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01992.txt.bz2
Content-length: 1014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43136
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |tkoenig at gcc dot gnu.org
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Created attachment 45431
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45431&action=edit
Patch which works, but causes some regressions
Apparently, in argument_checking_13.f90, the test in the last routine
interface
subroutine rlv3(y)
character :: y(3)
end subroutine rlv3
end interface
character(2) :: assumed_sh_dummy(:,:,:)
...
call rlv3(assumed_sh_dummy(1,1,1)(1:2)) ! { dg-error "contains too few
elements" }
does not trigger the warning if it is replaced by
call rlv3(assumed_sh_dummy(1,1,1))
So, this needs another test.
>From gcc-bugs-return-629184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 07:36:07 2019
Return-Path: <gcc-bugs-return-629184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80296 invoked by alias); 15 Jan 2019 07:36: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 80264 invoked by uid 48); 15 Jan 2019 07:36:03 -0000
From: "mscfd at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88768] Derived type io in conjunction with allocatable component and recursion fails
Date: Tue, 15 Jan 2019 07:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mscfd at gmx dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88768-4-N20JjyYVTS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88768-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88768-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01993.txt.bz2
Content-length: 823
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88768
--- Comment #2 from martin <mscfd at gmx dot net> ---
If I add the "generic :: write(unformatted) => write_unformatted" part in my
code (but do not use it), I see other failures somehow triggered by openmp
parallelisation (no recursion involved). Using the address sanitizer I can see
that one thread tries to access some memory already freed by another thread.
However, the concerned variables (of what is type(t) in the example code above)
are thread private and in fact several subroutine calls and modules away from
the openmp parallelisation block.
Unfortunately so far I was not able to produce a simple test case. However, it
looks like that the DT IO part uses some kind of global addresses, which does
not work well with recursion or threading?
>From gcc-bugs-return-629185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 07:56:40 2019
Return-Path: <gcc-bugs-return-629185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92691 invoked by alias); 15 Jan 2019 07:56: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 92552 invoked by uid 48); 15 Jan 2019 07:56:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Tue, 15 Jan 2019 07:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85574-4-3LOB5M3rtm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01994.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #29 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:00:43 2019
Return-Path: <gcc-bugs-return-629186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97759 invoked by alias); 15 Jan 2019 08:00: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 97680 invoked by uid 48); 15 Jan 2019 08:00:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88315] SAD and DOT_PROD SLP reductions with initial value != 0 create wrong code
Date: Tue, 15 Jan 2019 08:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: dependson
Message-ID: <bug-88315-4-buUyVkvlDW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88315-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88315-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01995.txt.bz2
Content-length: 591
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88315
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |88567
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Backports should check PR88567 for adjustments.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88567
[Bug 88567] [9 Regression] ICE in get_initial_defs_for_reduction when building
521.wrf_r on AArch64 SVE
>From gcc-bugs-return-629187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:02:14 2019
Return-Path: <gcc-bugs-return-629187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100481 invoked by alias); 15 Jan 2019 08:02: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 100431 invoked by uid 48); 15 Jan 2019 08:02:11 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88301] [8 Regression] Optimization regression with undefined unsigned overflow
Date: Tue, 15 Jan 2019 08:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88301-4-s19ACkdLzE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88301-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88301-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01996.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88301
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
>From gcc-bugs-return-629188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:11:36 2019
Return-Path: <gcc-bugs-return-629188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130261 invoked by alias); 15 Jan 2019 08:11: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 129452 invoked by uid 55); 15 Jan 2019 08:11:32 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Tue, 15 Jan 2019 08:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-drMISmc1kr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01997.txt.bz2
Content-length: 952
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Tue Jan 15 08:11:00 2019
New Revision: 267931
URL: https://gcc.gnu.org/viewcvs?rev=267931&root=gcc&view=rev
Log:
PR tree-optimization/88775
* match.pd (cmp (convert1?@2 addr@0) (convert2? addr@1)): Optimize
equal == 0 equality pointer comparisons some more if compared in
integral types and either one points to an automatic var and the
other to a global, or we can prove at least one points to the middle
or both point to start or both point to end.
* gcc.dg/tree-ssa/pr88775-1.c: New test.
* gcc.dg/tree-ssa/pr88775-2.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr88775-1.c
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr88775-2.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/match.pd
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:19:04 2019
Return-Path: <gcc-bugs-return-629189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5772 invoked by alias); 15 Jan 2019 08:19: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 5694 invoked by uid 48); 15 Jan 2019 08:19:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Tue, 15 Jan 2019 08:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88682-4-WbMvU6g2fY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01998.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Patch to do so is preapproved.
>From gcc-bugs-return-629190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:21:32 2019
Return-Path: <gcc-bugs-return-629190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11096 invoked by alias); 15 Jan 2019 08:21: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 11025 invoked by uid 48); 15 Jan 2019 08:21:27 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87306] test case gcc.dg/vect/bb-slp-pow-1.c fails with its introduction in r263290
Date: Tue, 15 Jan 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: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc assigned_to everconfirmed
Message-ID: <bug-87306-4-7xSdQcUiQc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg01999.txt.bz2
Content-length: 559
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87306
Kewen Lin <linkw at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-15
CC| |linkw at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |linkw at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-629191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:26:06 2019
Return-Path: <gcc-bugs-return-629191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26018 invoked by alias); 15 Jan 2019 08:26: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 25935 invoked by uid 48); 15 Jan 2019 08:26:02 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87306] test case gcc.dg/vect/bb-slp-pow-1.c fails with its introduction in r263290
Date: Tue, 15 Jan 2019 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87306-4-IT0ICk3Qo0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02000.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87306
--- Comment #1 from Kewen Lin <linkw at gcc dot gnu.org> ---
Confirmed.
This issue is power7 and below only, since it implicitly sets
-mno-allow-movmisalign, which disallow unaligned load/store in vectorization.
The proposed fix to guard the case under vect_hw_misalig on power targets.
>From gcc-bugs-return-629192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:28:53 2019
Return-Path: <gcc-bugs-return-629192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33999 invoked by alias); 15 Jan 2019 08:28: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 33947 invoked by uid 48); 15 Jan 2019 08:28:48 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83531] Build broken on macOS 10.13.2
Date: Tue, 15 Jan 2019 08:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83531-4-hIIDkkffb5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02001.txt.bz2
Content-length: 1116
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83531
--- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
On current 10.136, with Xcode 9.4 command line tools, and/or GCC 7.4 (with a
new enough linker to support v2 tbd files), this seems to work for me:
clang bootstrap (trunk)
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg01458.html
GCC: bootstrap:
(trunk)
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00316.html
(8x)
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00754.html
(7x)
https://gcc.gnu.org/ml/gcc-testresults/2019-01/msg00762.html
AFAICT, Darwin 9 through 18 all bootstrap [with the proviso that Apple-4.2.1 no
longer works on the earlier platforms, for trunk (it produces a compiler that
fails its self-tests with a memory-management problem), I've been using GCC-5
as the bootstrap on Darwin9 and 10.
Is this problem still reproducible to anyone?
If not can we close it?
Apropos comment #2, yes we have some header hassles; we need to work through
the test cases fixing them up - patches welcome! Anyway - let's separate the
test-case headers issue from this one.
>From gcc-bugs-return-629193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:32:49 2019
Return-Path: <gcc-bugs-return-629193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73840 invoked by alias); 15 Jan 2019 08:32: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 72789 invoked by uid 48); 15 Jan 2019 08:32:45 -0000
From: "linkw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/87306] test case gcc.dg/vect/bb-slp-pow-1.c fails with its introduction in r263290
Date: Tue, 15 Jan 2019 08:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: linkw at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: linkw at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-87306-4-ysMLLaN8wZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87306-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02002.txt.bz2
Content-length: 274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87306
--- Comment #2 from Kewen Lin <linkw at gcc dot gnu.org> ---
Created attachment 45432
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45432&action=edit
Similar to the patch fixing pr65484
Referring to pr65484.
>From gcc-bugs-return-629194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:34:47 2019
Return-Path: <gcc-bugs-return-629194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101097 invoked by alias); 15 Jan 2019 08:34: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 98832 invoked by uid 48); 15 Jan 2019 08:34:44 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Tue, 15 Jan 2019 08:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
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: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-iNfq9kQgzy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02003.txt.bz2
Content-length: 787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
In theory liblto_plugin is backwards compatible (newer versions work with older
compilers). Still a make install cannot simply replace the installed version
since it may end up replacing a newer one. So it is up to the system
integrator to install it.
It might have been "easier" to bundle liblto_plugin with the BFD linker itself
since it is as much dependent on the BFD plugin interface evolution as the
compiler LTO symtab format.
I agree that documenting bfd-plugin as install location (if you have sysadmin
rights) would be an improvement (as well as the compatibility promise).
But I don't know of any testing of that compatibility guarantee...
>From gcc-bugs-return-629195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:38:23 2019
Return-Path: <gcc-bugs-return-629195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121990 invoked by alias); 15 Jan 2019 08:38:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121967 invoked by uid 48); 15 Jan 2019 08:38:19 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88852] New: [openacc] Host fallback doesn't create private copy for reduction var on gang clause
Date: Tue, 15 Jan 2019 08:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88852-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02004.txt.bz2
Content-length: 1886
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88852
Bug ID: 88852
Summary: [openacc] Host fallback doesn't create private copy
for reduction var on gang clause
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: vries at gcc dot gnu.org
Target Milestone: ---
spinoff from PR 80547 - '[7/8/9 Regression] nvptx back end ICE with OpenACC
"reduction(OP:x)", "x = [...]"'.
Consider this test-case:
...
int
main (void)
{
int x = 123;
#pragma acc parallel num_gangs(1) reduction (+: x)
{
x = 23;
}
if (x != 146)
__builtin_abort();
.
return 0;
}
...
The semantics of the reduction variable are:
...
The reduction clause is allowed on the parallel construct. It specifies a
reduction operator and one or more scalar variables. For each variable, a
private copy is created for each parallel gang and initialized for that
operator. At the end of the region, the values for each gang are combined
using the reduction operator, and the result combined with the value of the
original variable and stored in the original variable. The reduction result is
available after the region
...
Looking at the host fallback at oaccdevlow:
...
__attribute__((oacc function (1, 1, 1), omp target entrypoint))
main._omp_fn.0 (const struct .omp_data_t.0 & restrict .omp_data_i)
{
int x;
int * _3;
int * _6;
int * _8;
int * _11;
<bb 2> [local count: 1073741824]:
_3 = *.omp_data_i_2(D).x;
x_5 = *_3;
_6 = *.omp_data_i_2(D).x;
_8 = *.omp_data_i_2(D).x;
x_10 = 23;
_11 = *.omp_data_i_2(D).x;
*_11 = x_10;
return;
}
...
we see that there's no private copy initialized, and no combination with
original value done.
>From gcc-bugs-return-629196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:40:26 2019
Return-Path: <gcc-bugs-return-629196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124501 invoked by alias); 15 Jan 2019 08:40:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124424 invoked by uid 48); 15 Jan 2019 08:40:22 -0000
From: "simon at pushface dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/88610] ICE with new ACATS test c452003
Date: Tue, 15 Jan 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: simon at pushface 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-88610-4-m2OnHVWsgL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88610-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88610-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02005.txt.bz2
Content-length: 470
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88610
--- Comment #2 from simon at pushface dot org ---
(In reply to Eric Botcazou from comment #1)
> There is probably little value in filling PRs against new ACATS tests though.
I can see this argument if you mean that a new ACATS test might be disputed,
and I’d certainly think twice before reporting a mere compilation failure
in what’s a pretty obscure language area. But this is an ICE.
>From gcc-bugs-return-629197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:40:39 2019
Return-Path: <gcc-bugs-return-629197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125333 invoked by alias); 15 Jan 2019 08:40: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 125223 invoked by uid 48); 15 Jan 2019 08:40:35 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80547] [7/8/9 Regression] nvptx back end ICE with OpenACC "reduction(OP:x)", "x = [...]"
Date: Tue, 15 Jan 2019 08:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80547-4-sbdLRuC6Ar@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80547-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80547-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02006.txt.bz2
Content-length: 672
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80547
--- Comment #8 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #1)
> An additional observation: for host fallback (adding an "if(0)" clause to
> both the OpenMP and OpenACC directives, for example), the OpenMP code still
> works, but for OpenACC, we then get a result of "x = 23", so apparently the
> reduction computation/finalization code is being skipped in this case.
> (Let's please make this a separate PR if it's not directly related to this
> one here.)
Filed PR88852 - "[openacc] Host fallback doesn't create private copy for
reduction var on gang clause"
>From gcc-bugs-return-629198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 08:57:11 2019
Return-Path: <gcc-bugs-return-629198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84930 invoked by alias); 15 Jan 2019 08:57:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84837 invoked by uid 48); 15 Jan 2019 08:57:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Tue, 15 Jan 2019 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80762-4-gRTlfxJepO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02007.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #12 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Doh, yes it's missing the linker option. It should be a different error now,
but still failing.
>From gcc-bugs-return-629199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:02:37 2019
Return-Path: <gcc-bugs-return-629199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16850 invoked by alias); 15 Jan 2019 09:02:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16657 invoked by uid 48); 15 Jan 2019 09:02:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/88587] ICE in expand_debug_locations, at cfgexpand.c:5450
Date: Tue, 15 Jan 2019 09:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88587-4-VG4GISMjrP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88587-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02008.txt.bz2
Content-length: 2781
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88587
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Yes, it depends on the supported ISAs. In essential the issue is that
TYPE_MODE
depends on the (function) context it is used, that's even true for globals
(IIRC there are existing bugs with respect to that).
For your always-inline testcase we override the target attribute conflict
and run into the same issue that the inliner copying is remapping the decl
(but not for debug-decls!).
So for example
# DEBUG b => { 0, 0, 0, 0 }
has BLKmode decl but V4SImode type.
The issue here can possibly befixed (for debug insns) by fixing up the
(debug bind) decl during expansion. Or having it fixed up (aka copied)
during inlining. Given that
(debug_insn 7 6 8 2 (var_location:BLK b (return:CC)) "t.c":2:61 -1
(nil))
is going to be useless anyways (because of :BLK).
The following fixes the always-inline case but not the MV one:
Index: gcc/tree-inline.c
===================================================================
--- gcc/tree-inline.c (revision 267930)
+++ gcc/tree-inline.c (working copy)
@@ -5479,6 +5479,10 @@ copy_decl_for_dup_finish (copy_body_data
if (CODE_CONTAINS_STRUCT (TREE_CODE (copy), TS_DECL_WRTL)
&& !TREE_STATIC (copy) && !DECL_EXTERNAL (copy))
SET_DECL_RTL (copy, 0);
+ /* For vector typed decls make sure to update DECL_MODE according
+ to the new function context. */
+ if (VECTOR_TYPE_P (TREE_TYPE (copy)))
+ SET_DECL_MODE (copy, TYPE_MODE (TREE_TYPE (copy)));
/* These args would always appear unused, if not for this. */
TREE_USED (copy) = 1;
The following helps tracking down affected stmts:
Index: gcc/tree-cfg.c
===================================================================
--- gcc/tree-cfg.c (revision 267930)
+++ gcc/tree-cfg.c (working copy)
@@ -5108,6 +5108,17 @@ verify_node_sharing_1 (tree *tp, int *wa
{
hash_set<void *> *visited = (hash_set<void *> *) data;
+ if (DECL_P (*tp)
+ && VECTOR_TYPE_P (TREE_TYPE (*tp))
+ && DECL_MODE (*tp) != TYPE_MODE (TREE_TYPE (*tp)))
+ {
+ fprintf (stderr, "DECL_MODE %s vs TYPE_MODE %s [%s]: ",
+ mode_name[DECL_MODE (*tp)],
+ mode_name[TYPE_MODE (TREE_TYPE (*tp))],
+ mode_name[TYPE_MODE_RAW (TREE_TYPE (*tp))]);
+ print_generic_expr (stderr, *tp);
+ fprintf (stderr, "\n");
+ }
if (tree_node_can_be_shared (*tp))
{
*walk_subtrees = false;
>From gcc-bugs-return-629201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:05:32 2019
Return-Path: <gcc-bugs-return-629201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21870 invoked by alias); 15 Jan 2019 09:05: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 21390 invoked by uid 48); 15 Jan 2019 09:05:24 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/88610] ICE with new ACATS test c452003
Date: Tue, 15 Jan 2019 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ada
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: SUSPENDED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-88610-4-RNX5kcR5jp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88610-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88610-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02010.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88610
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |SUSPENDED
--- Comment #3 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I can see this argument if you mean that a new ACATS test might be disputed,
> and I’d certainly think twice before reporting a mere compilation failure
> in what’s a pretty obscure language area. But this is an ICE.
My point is that opening a PR has strictly no effects in this case, unlike for
other cases. New ACATS tests are publicly available and the compiler will be
changed accordingly at some point, but the priority is very low.
Let's make this clear by suspending this PR then.
>From gcc-bugs-return-629200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:05:29 2019
Return-Path: <gcc-bugs-return-629200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21459 invoked by alias); 15 Jan 2019 09:05: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 21292 invoked by uid 48); 15 Jan 2019 09:05:19 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Tue, 15 Jan 2019 09:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-1Ver3xBfSL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02009.txt.bz2
Content-length: 718
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #13 from ДилÑн Палаузов <dilyan.palauzov at aegee dot org> ---
At https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345#c4 is written that “Right
now the plugin from any gcc can be used with any gcc.†This is not the same as
the last comment. Please clarify again, if any gcc plugin can be used with any
gcc.
If several plugins can be installed simultaneously and the first one that
claims the .o file wins, why aren’t plugins for both GCC7 and GCC8 installed at
the same time? Just for gcc8 files, the gcc7 plugin will not claim the
responsibility.
>From gcc-bugs-return-629202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:10:52 2019
Return-Path: <gcc-bugs-return-629202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57361 invoked by alias); 15 Jan 2019 09:10: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 57278 invoked by uid 48); 15 Jan 2019 09:10:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88841] Missed optimization transforming cascading ||s into a bit select
Date: Tue, 15 Jan 2019 09:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-88841-4-i84ckospcz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02011.txt.bz2
Content-length: 1240
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88841
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
Component|other |tree-optimization
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is the tests are split in different ways.
isspc_1 (char c)
{
bool D.2304;
bool iftmp.0;
_1 = c == 32;
_2 = c == 10;
_3 = _1 | _2;
if (_3 != 0) goto <D.2306>; else goto <D.2309>;
<D.2309>:
_4 = c == 13;
_5 = c == 9;
_6 = _4 | _5;
if (_6 != 0) goto <D.2306>; else goto <D.2307>;
vs.
isspc_2 (char c)
{
bool D.2311;
bool iftmp.1;
_1 = c == 32;
_2 = c == 13;
_3 = _1 | _2;
if (_3 != 0) goto <D.2313>; else goto <D.2316>;
<D.2316>:
c.2_4 = (unsigned char) c;
_5 = c.2_4 + 247;
if (_5 <= 1) goto <D.2313>; else goto <D.2314>;
>From gcc-bugs-return-629203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:13:43 2019
Return-Path: <gcc-bugs-return-629203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60854 invoked by alias); 15 Jan 2019 09: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 60701 invoked by uid 55); 15 Jan 2019 09:13:38 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Tue, 15 Jan 2019 09:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85574-4-thphMT4crS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02012.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #30 from Jan Hubicka <hubicka at ucw dot cz> ---
We may still want to backport to gcc 7 branch. The ICF bug at least
exists there as well.
>From gcc-bugs-return-629204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:14:40 2019
Return-Path: <gcc-bugs-return-629204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64458 invoked by alias); 15 Jan 2019 09:14: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 64274 invoked by uid 48); 15 Jan 2019 09:14:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88842] missing optimization CSE, reassociation
Date: Tue, 15 Jan 2019 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
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 component everconfirmed
Message-ID: <bug-88842-4-IQWeuSuiFk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88842-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02013.txt.bz2
Content-length: 1027
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88842
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
Component|other |tree-optimization
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
void foo(int a, int b, int c, int d, int e, int *res) {
res[0] = (e * a) * d;
res[1] = (e * b) * d;
res[2] = (e * c) * d;
}
associating (e * d) allows CSE. Only possible when there's no overflow
(-fwrapv or unsigned types).
The issue is that reassoc is a "local" optimization, associating single
chains rather than looking at multiple chains at once.
And of course reassoc isn't "integrated" with CSE.
>From gcc-bugs-return-629205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:20:43 2019
Return-Path: <gcc-bugs-return-629205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68744 invoked by alias); 15 Jan 2019 09:20:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68687 invoked by uid 48); 15 Jan 2019 09:20:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88844] poor range info for number of loop iterations with a known upper bound
Date: Tue, 15 Jan 2019 09:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88844-4-v6crC1PJNS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02014.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88844
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
The issue is that niter analysis cannot compute the number of iterations.
It's sth like floor_log2(i)/4 when header copied.
>From gcc-bugs-return-629207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:21:51 2019
Return-Path: <gcc-bugs-return-629207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70543 invoked by alias); 15 Jan 2019 09:21: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 70473 invoked by uid 48); 15 Jan 2019 09:21:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88850] [9 Regression] Hard register coming out of expand causing reload to fail.
Date: Tue, 15 Jan 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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-88850-4-lrVOy1bHlE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02016.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88850
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Target Milestone|--- |9.0
>From gcc-bugs-return-629206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:21:07 2019
Return-Path: <gcc-bugs-return-629206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69585 invoked by alias); 15 Jan 2019 09:21:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69502 invoked by uid 48); 15 Jan 2019 09:21:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88846] [9 Regression] pr69776-2.c failure on 32 bit AIX
Date: Tue, 15 Jan 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: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88846-4-oncscAHbdA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02015.txt.bz2
Content-length: 293
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88846
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-629208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:22:03 2019
Return-Path: <gcc-bugs-return-629208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71271 invoked by alias); 15 Jan 2019 09:22:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71194 invoked by uid 48); 15 Jan 2019 09:21:59 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88851] [9 Regression] SVE Stack clash and r263173 use conflicting registers
Date: Tue, 15 Jan 2019 09:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: version target_milestone
Message-ID: <bug-88851-4-YRTUFwUaha@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02017.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88851
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Version|unknown |9.0
Target Milestone|--- |9.0
>From gcc-bugs-return-629209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:27:40 2019
Return-Path: <gcc-bugs-return-629209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76740 invoked by alias); 15 Jan 2019 09:27: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 76679 invoked by uid 48); 15 Jan 2019 09:27:36 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88847] gcc.target/aarch64/sve/struct_move_1.c ICE with -fstack-protector-strong
Date: Tue, 15 Jan 2019 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone everconfirmed
Message-ID: <bug-88847-4-1F8bx3Aalz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02018.txt.bz2
Content-length: 960
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88847
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
CC| |ktkachov at gcc dot gnu.org,
| |rsandifo at gcc dot gnu.org,
| |tnfchris at gcc dot gnu.org
Target Milestone|--- |8.3
Ever confirmed|0 |1
--- Comment #1 from ktkachov at gcc dot gnu.org ---
Confirmed. This is the gcc.target/aarch64/sve/struct_move_1.c testcase.
Is this a big-endian SVE problem? or a stack protector implementation problem?
Given that it appears on GCC 8 as well I'm inclined to think the former...
>From gcc-bugs-return-629210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:28:31 2019
Return-Path: <gcc-bugs-return-629210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80389 invoked by alias); 15 Jan 2019 09:28: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 77738 invoked by uid 48); 15 Jan 2019 09:28:26 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88853] New: ICE: verify_type failed (error: type variant differs by TYPE_PACKED)
Date: Tue, 15 Jan 2019 09:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02019.txt.bz2
Content-length: 5122
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88853
Bug ID: 88853
Summary: ICE: verify_type failed (error: type variant differs
by TYPE_PACKED)
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-checking, ice-on-valid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
Created attachment 45433
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45433&action=edit
Testcase
g++-9.0.0-alpha20190113 snapshot (r267906), 8.2, 7.4, 6.3 all ICE when
compiling the attached snippet reduced from gcc/testsuite/g++.dg/ext/pr85503.C
w/ -fpack-struct -g:
% g++-9.0.0-alpha20190113 -fpack-struct -g -c jxdgvov9.cc
jxdgvov9.cc: In instantiation of 'class yp<fd<double, 0> >':
jxdgvov9.cc:15:7: required from 'class n1<fd<double, 0> >'
jxdgvov9.cc:21:7: required from 'class c4<fd<double, 0> >'
jxdgvov9.cc:33:7: required from 'class hb<fd<double, 0> >'
jxdgvov9.cc:45:7: required from 'class fd<double, 0>'
jxdgvov9.cc:52:7: required from 'class dh<dh<fd<double, 0> > >'
jxdgvov9.cc:17:22: required from 'class n1<dh<fd<double, 0> > >'
jxdgvov9.cc:57:19: required from here
jxdgvov9.cc:26:7: error: type variant differs by TYPE_PACKED
26 | class yp
| ^~
<record_type 0x7fefa98a3e70 fd packed type_5 type_6 VOID
align:8 warn_if_not_align:0 symtab:-1451847200 alias-set -1 canonical-type
0x7fefa98a3e70 context <translation_unit_decl 0x7fefa975a168 jxdgvov9.cc>
full-name "class fd<double, 0>"
no-binfo use_template=1 interface-unknown
chain <type_decl 0x7fefa986fb48 fd>>
<record_type 0x7fefa98a3f18 fd readonly type_5 VOID
align:8 warn_if_not_align:0 symtab:-1451847120 alias-set -1 canonical-type
0x7fefa98a3f18 context <translation_unit_decl 0x7fefa975a168 jxdgvov9.cc>
full-name "const class fd<double, 0>"
no-binfo use_template=1 interface-unknown>
jxdgvov9.cc:26:7: internal compiler error: verify_type failed
0x127580b verify_type(tree_node const*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/tree.c:14555
0xc022f4 gen_type_die_with_usage
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25449
0xc040e6 gen_type_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25679
0xc1f343 gen_decl_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:26272
0xc227e3 gen_member_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25133
0xc227e3 gen_struct_or_union_type_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25229
0xc1d954 gen_tagged_type_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25430
0xc02845 gen_type_die_with_usage
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25625
0xc040e6 gen_type_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:25679
0xc1e740 gen_decl_die
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:26311
0xc1f9e6 dwarf2out_decl
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:26856
0xc1feb8 dwarf2out_type_decl
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:26583
0xc1feb8 dwarf2out_type_decl
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dwarf2out.c:26578
0xebfb98 rest_of_type_compilation(tree_node*, int)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:339
0x8bad7c finish_struct_1(tree_node*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cp/class.c:7055
0xa0f5d3 instantiate_class_template_1
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cp/pt.c:11397
0xa0f5d3 instantiate_class_template(tree_node*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cp/pt.c:11436
0xa565fd complete_type(tree_node*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cp/typeck.c:138
0xa5673b complete_type(tree_node*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cp/typeck.c:119
0xa5673b complete_type_or_maybe_complain(tree_node*, tree_node*, int)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/cp/typeck.c:150
>From gcc-bugs-return-629211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:31:24 2019
Return-Path: <gcc-bugs-return-629211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111940 invoked by alias); 15 Jan 2019 09:31:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111864 invoked by uid 48); 15 Jan 2019 09:31:18 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Tue, 15 Jan 2019 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
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: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84995-4-5PxcKGSfVV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02020.txt.bz2
Content-length: 1806
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hubicka at gcc dot gnu.org
--- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to ДилÑн Палаузов from comment #13)
> At https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345#c4 is written that
> “Right now the plugin from any gcc can be used with any gcc.†This is not
> the same as the last comment. Please clarify again, if any gcc plugin can
> be used with any gcc.
Well, liblto_plugin.so is only half of the story. Yes, using any version
will probably "work" but you might get better experience with using a newer
version (though that newer version might present older GCC with resolution
files they do not understand).
> If several plugins can be installed simultaneously and the first one that
> claims the .o file wins, why aren’t plugins for both GCC7 and GCC8 installed
> at the same time? Just for gcc8 files, the gcc7 plugin will not claim the
> responsibility.
It doesn't work that way since any liblto_plugin.so version will accept
any GCC LTO files. It is the lto-wrapper binary that is found to the
one matching the GCC driver version used to invocate the link that
ultimately determines your luck - here strict version matching is required.
Thus LTO linking objects from mixed GCC version is doomed to fail
fatally.
Note plugin auto-loading will only work reliably for ar/nm/ranlib because
of this and indeed for those the version of the plugin doesn't really matter.
>From gcc-bugs-return-629212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:32:15 2019
Return-Path: <gcc-bugs-return-629212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113314 invoked by alias); 15 Jan 2019 09:32:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113208 invoked by uid 48); 15 Jan 2019 09:32:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85574] [8/9 Regression] LTO bootstapped binaries differ
Date: Tue, 15 Jan 2019 09:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85574-4-GqGHEYTrOu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85574-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02021.txt.bz2
Content-length: 267
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85574
--- Comment #31 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #30)
> We may still want to backport to gcc 7 branch. The ICF bug at least
> exists there as well.
Sure.
>From gcc-bugs-return-629213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 09:37:58 2019
Return-Path: <gcc-bugs-return-629213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118786 invoked by alias); 15 Jan 2019 09:37: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 118726 invoked by uid 55); 15 Jan 2019 09:37:54 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88788] [9 Regression] Infinite loop in malloc_candidate_p_1 since r264838
Date: Tue, 15 Jan 2019 09:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: compile-time-hog, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88788-4-TqiLu1XHXA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88788-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02022.txt.bz2
Content-length: 678
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88788
--- Comment #16 from prathamesh3492 at gcc dot gnu.org ---
Author: prathamesh3492
Date: Tue Jan 15 09:37:22 2019
New Revision: 267933
URL: https://gcc.gnu.org/viewcvs?rev=267933&root=gcc&view=rev
Log:
2019-01-15 Richard Biener <rguenther@suse.de>
Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
PR ipa/88788
* ipa-pure-const.c (malloc_candidate_p_1): Add parameter visited and
return true if SSA_NAME is already marked in visited bitmap.
(malloc_candidate_p): Pass visited to malloc_candidate_p_1.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-pure-const.c
>From gcc-bugs-return-629214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:07:15 2019
Return-Path: <gcc-bugs-return-629214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87130 invoked by alias); 15 Jan 2019 10:07:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87005 invoked by uid 48); 15 Jan 2019 10:07:10 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Tue, 15 Jan 2019 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-E9tTKO4HlF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02023.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #15 from ДилÑн Палаузов <dilyan.palauzov at aegee dot org> ---
Why isn’t liblto_plugin.so tweaked to claim only the GCC LTO files, it can
handle? E.g. liblto_plugin.so from GCC7 does not claim files for GCC 8 LTO?
I do not get the conclusion here:
* liblto_plugin.so from $libdir/bfd-plugins is only magially called by
ar/nm/ranlib and there the version number does not matter;
* in case where liblto_plugin.so is not called by ar/nm/ranlib the version
number matters, but no auto-loading happens, so installing it under
$libdir/bfd-plugins is irrelevant
So when will it be problematic to do auto loading by ar/nm/ranlib and when can
installing the plugin under $libdir/bfd-plugins create problems?
>From gcc-bugs-return-629215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:11:52 2019
Return-Path: <gcc-bugs-return-629215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105593 invoked by alias); 15 Jan 2019 10:11:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105543 invoked by uid 55); 15 Jan 2019 10:11:48 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/80547] [7/8/9 Regression] nvptx back end ICE with OpenACC "reduction(OP:x)", "x = [...]"
Date: Tue, 15 Jan 2019 10:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: ice-on-valid-code, openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80547-4-iBzhbwTTPx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80547-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80547-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02024.txt.bz2
Content-length: 810
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80547
--- Comment #9 from Tom de Vries <vries at gcc dot gnu.org> ---
Author: vries
Date: Tue Jan 15 10:11:16 2019
New Revision: 267934
URL: https://gcc.gnu.org/viewcvs?rev=267934&root=gcc&view=rev
Log:
[nvptx] Handle assignment to gang-level reduction variable
2019-01-15 Tom de Vries <tdevries@suse.de>
PR target/80547
* config/nvptx/nvptx.c (nvptx_goacc_reduction_init): Handle
lhs == NULL_TREE for gang-level reduction.
* testsuite/libgomp.oacc-c-c++-common/gang-reduction-var-assignment.c:
New test.
Added:
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/gang-reduction-var-assignment.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/nvptx/nvptx.c
trunk/libgomp/ChangeLog
>From gcc-bugs-return-629216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:21:42 2019
Return-Path: <gcc-bugs-return-629216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25461 invoked by alias); 15 Jan 2019 10:21:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22943 invoked by uid 48); 15 Jan 2019 10:21:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Tue, 15 Jan 2019 10:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80762-4-3usGlTGSGK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02025.txt.bz2
Content-length: 309
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
--- Comment #13 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But it's a { dg-do compile } test so doesn't need the linker option.
So I don't know how this is failing still. If the <experimental/filesystem>
header is absent, the test shouldn't run.
>From gcc-bugs-return-629217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:24:48 2019
Return-Path: <gcc-bugs-return-629217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62422 invoked by alias); 15 Jan 2019 10:24: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 62321 invoked by uid 48); 15 Jan 2019 10:24:36 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/71499] ICE in LTO1 when attempting NVPTX offloading (-fopenacc)
Date: Tue, 15 Jan 2019 10:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code, lto, openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-71499-4-3ckgbIEfxI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71499-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71499-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02026.txt.bz2
Content-length: 2724
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71499
Tom de Vries <vries at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |vries at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #3 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Thomas Schwinge from comment #2)
> The is the OpenACC variant of OpenMP's PR71535.
>
> You need to add "#pragma acc routine" for function "test". (Of course, we
> shouldn't run into an ICE nevertheless.)
This is a duplicate of
libgomp/testsuite/libgomp.oacc-c-c++-common/function-not-offloaded.c , which
was fixed here ( https://gcc.gnu.org/ml/gcc-cvs/2018-12/msg00431.html ):
...
Author: vries
Date: Fri Dec 14 13:48:56 2018
New Revision: 267134
URL: https://gcc.gnu.org/viewcvs?rev=267134&root=gcc&view=rev
Log:
[offloading] Error on missing symbols
When compiling an OpenMP or OpenACC program containing a reference in the
offloaded code to a symbol that has not been included in the offloaded code,
the offloading compiler may ICE in lto1.
Fix this by erroring out instead, mentioning the problematic symbol:
...
error: variable 'var' has been referenced in offloaded code but hasn't
been marked to be included in the offloaded code
lto1: fatal error: errors during merging of translation units
compilation terminated.
...
Build x86_64 with nvptx accelerator and reg-tested libgomp.
Build x86_64 and reg-tested libgomp.
2018-12-14 Tom de Vries <tdevries@suse.de>
* lto-cgraph.c (verify_node_partition): New function.
(input_overwrite_node, input_varpool_node): Use verify_node_partition.
* testsuite/libgomp.c-c++-common/function-not-offloaded-aux.c: New
test.
* testsuite/libgomp.c-c++-common/function-not-offloaded.c: New test.
* testsuite/libgomp.c-c++-common/variable-not-offloaded.c: New test.
* testsuite/libgomp.oacc-c-c++-common/function-not-offloaded.c: New
test.
* testsuite/libgomp.oacc-c-c++-common/variable-not-offloaded.c: New
test.
Added:
trunk/libgomp/testsuite/libgomp.c-c++-common/function-not-offloaded-aux.c
trunk/libgomp/testsuite/libgomp.c-c++-common/function-not-offloaded.c
trunk/libgomp/testsuite/libgomp.c-c++-common/variable-not-offloaded.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/function-not-offloaded.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/variable-not-offloaded.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/lto-cgraph.c
trunk/libgomp/ChangeLog
...
>From gcc-bugs-return-629218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:30:48 2019
Return-Path: <gcc-bugs-return-629218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87239 invoked by alias); 15 Jan 2019 10:30:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86221 invoked by uid 48); 15 Jan 2019 10:30:26 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 10:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-MuB5LfaWTD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02027.txt.bz2
Content-length: 658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #15 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Ah, except that isn't all that r265398 did. It has both the make_more_copies
part and
|| (HARD_REGISTER_P (dest)
- && ! TEST_HARD_REG_BIT (fixed_reg_set, REGNO (dest))
- && targetm.class_likely_spilled_p (REGNO_REG_CLASS (REGNO
(dest))))))
+ && ! TEST_HARD_REG_BIT (fixed_reg_set, REGNO (dest)))))
hunk in cant_combine_insn_p. If I revert both, then it works properly, but as
I said, not doing make_more_copies alone or reverting this
class_likely_spilled_p check alone doesn't fix it.
>From gcc-bugs-return-629219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:41:02 2019
Return-Path: <gcc-bugs-return-629219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37973 invoked by alias); 15 Jan 2019 10:41: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 30639 invoked by uid 48); 15 Jan 2019 10:40:58 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] New: redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 10:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone
Message-ID: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02028.txt.bz2
Content-length: 1009
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
Bug ID: 88854
Summary: redundant store after load that would makes aliasing
UB
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Test cases:
This is optimized at -O1 and with GCC 5 at -O2. -fdisable-tree-fre1 and
-fno-strict-aliasing also remove the store to a.
void f(int *a, float *b) {
int x = *a;
*b = 0;
x = *a;
*a = x;
}
The following is an extension that reloads *a after store to b into a different
variable. Still the store to a must be dead, since otherwise the read of a
would be UB.
int g(int *a, float *b) {
int x = *a;
*b = 0;
int r = *a;
*a = x;
return r;
}
>From gcc-bugs-return-629220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:44:02 2019
Return-Path: <gcc-bugs-return-629220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128279 invoked by alias); 15 Jan 2019 10:44: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 121261 invoked by uid 48); 15 Jan 2019 10:43:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 10:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88854-4-Exys7h2GlY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02029.txt.bz2
Content-length: 1592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-15
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. For f the CSE opportunity makes the lookup for redudnant store
detection fail since that is not allowed to use TBAA. The following fixes that
at the cost of some extra hash table entries:
Index: gcc/tree-ssa-sccvn.c
===================================================================
--- gcc/tree-ssa-sccvn.c (revision 267930)
+++ gcc/tree-ssa-sccvn.c (working copy)
@@ -4088,7 +4088,11 @@ visit_reference_op_load (tree lhs, tree
}
if (result)
- changed = set_ssa_val_to (lhs, result);
+ {
+ changed = set_ssa_val_to (lhs, result);
+ if (last_vuse != gimple_vuse (stmt))
+ vn_reference_insert (op, result, gimple_vuse (stmt), NULL_TREE);
+ }
else
{
changed = set_ssa_val_to (lhs, lhs);
the same happens for g thus g is fixed as well.
>From gcc-bugs-return-629221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:50:47 2019
Return-Path: <gcc-bugs-return-629221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6853 invoked by alias); 15 Jan 2019 10:50: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 6743 invoked by uid 55); 15 Jan 2019 10:50:41 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Tue, 15 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-c9FUICnwtr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02030.txt.bz2
Content-length: 2943
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #16 from Jan Hubicka <hubicka at ucw dot cz> ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
>
> Richard Biener <rguenth at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |hubicka at gcc dot gnu.org
>
> --- Comment #14 from Richard Biener <rguenth at gcc dot gnu.org> ---
> (In reply to ДилÑн Палаузов from comment #13)
> > At https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70345#c4 is written that
> > “Right now the plugin from any gcc can be used with any gcc.†This is not
> > the same as the last comment. Please clarify again, if any gcc plugin can
> > be used with any gcc.
>
> Well, liblto_plugin.so is only half of the story. Yes, using any version
> will probably "work" but you might get better experience with using a newer
> version (though that newer version might present older GCC with resolution
> files they do not understand).
I think we only extended resolution file for new resolution types passed
by newer linkers, so it should be backward compatible to original
implementation. Notable changes was made to pass -flinker-output.
Both however matters only for the cases where linker is invoked from gcc
command, not for ar/ranlib/nm.
We may want to update symbol table eventually but I do not think it
would be big deal to keep plugin understand old format becuse it is
simple.
>
> > If several plugins can be installed simultaneously and the first one that
> > claims the .o file wins, why aren’t plugins for both GCC7 and GCC8 installed
> > at the same time? Just for gcc8 files, the gcc7 plugin will not claim the
> > responsibility.
>
> It doesn't work that way since any liblto_plugin.so version will accept
> any GCC LTO files. It is the lto-wrapper binary that is found to the
> one matching the GCC driver version used to invocate the link that
> ultimately determines your luck - here strict version matching is required.
> Thus LTO linking objects from mixed GCC version is doomed to fail
> fatally.
>
> Note plugin auto-loading will only work reliably for ar/nm/ranlib because
> of this and indeed for those the version of the plugin doesn't really matter.
Plugin interface should be good enough to allow LTO optimizing one
binary with multiple compilers (multiple versions of GCC or GCC+LLVM
combination) where obviously no cross-module optimization between
compilers will happen but still each compiler will get acurate
resolution data that will let it to optimize well within the portion of
binary it understands.
We are missing way to specify multiple plugins to linker and some other
supporting bits I believe.
Honza
>From gcc-bugs-return-629222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 10:53:14 2019
Return-Path: <gcc-bugs-return-629222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18773 invoked by alias); 15 Jan 2019 10:53:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18726 invoked by uid 48); 15 Jan 2019 10:53:10 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88854-4-nmVRFaNUbB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02031.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
GCC 5 doesn't see the CSE opportunity because it doesn't process the unused
load and the translation code is not up-to-speed. Then DOM figures out the
redundant store it sees them adjacent.
So I wouldn't really call this a regression.
>From gcc-bugs-return-629223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 11:08:38 2019
Return-Path: <gcc-bugs-return-629223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71901 invoked by alias); 15 Jan 2019 11:08:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71794 invoked by uid 48); 15 Jan 2019 11:08:33 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Tue, 15 Jan 2019 11:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-0pcNLO38v8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02032.txt.bz2
Content-length: 2818
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #8 from ktkachov at gcc dot gnu.org ---
btw looks likes ICC vectorises this as well as unrolling:
..B1.14:
movl (%rcx,%rbx,4), %r15d
vmovsd (%rdi,%r15,8), %xmm2
movl 4(%rcx,%rbx,4), %r15d
vmovhpd (%rdi,%r15,8), %xmm2, %xmm3
movl 8(%rcx,%rbx,4), %r15d
vfmadd231pd (%r10,%rbx,8), %xmm3, %xmm0
vmovsd (%rdi,%r15,8), %xmm4
movl 12(%rcx,%rbx,4), %r15d
vmovhpd (%rdi,%r15,8), %xmm4, %xmm5
movl 16(%rcx,%rbx,4), %r15d
vfmadd231pd 16(%r10,%rbx,8), %xmm5, %xmm1
vmovsd (%rdi,%r15,8), %xmm6
movl 20(%rcx,%rbx,4), %r15d
vmovhpd (%rdi,%r15,8), %xmm6, %xmm7
movl 24(%rcx,%rbx,4), %r15d
vfmadd231pd 32(%r10,%rbx,8), %xmm7, %xmm0
vmovsd (%rdi,%r15,8), %xmm8
movl 28(%rcx,%rbx,4), %r15d
vmovhpd (%rdi,%r15,8), %xmm8, %xmm9
vfmadd231pd 48(%r10,%rbx,8), %xmm9, %xmm1
addq $8, %rbx
cmpq %r14, %rbx
jb ..B1.14
Is that something GCC could reasonably do?
>From gcc-bugs-return-629224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 11:16:09 2019
Return-Path: <gcc-bugs-return-629224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126443 invoked by alias); 15 Jan 2019 11:16:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126348 invoked by uid 48); 15 Jan 2019 11:16:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Tue, 15 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
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: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-cJ6uxdWUy5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02033.txt.bz2
Content-length: 969
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #17 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jan Hubicka from comment #16)
>
> Plugin interface should be good enough to allow LTO optimizing one
> binary with multiple compilers (multiple versions of GCC or GCC+LLVM
> combination) where obviously no cross-module optimization between
> compilers will happen but still each compiler will get acurate
> resolution data that will let it to optimize well within the portion of
> binary it understands.
>
> We are missing way to specify multiple plugins to linker and some other
> supporting bits I believe.
Yes, the main issue is how we find lto-wrapper (COLLECT_GCC*
environment) and that lto-wrapper does _not_ work across GCC versions.
I guess lto-plugin would ideally partition the set of files according
to the LTO byte-code version and we'd have a way to lookup gcc and
lto-wrapper by LTO byte-code version.
> Honza
>From gcc-bugs-return-629225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 11:19:44 2019
Return-Path: <gcc-bugs-return-629225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2079 invoked by alias); 15 Jan 2019 11:19:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1955 invoked by uid 55); 15 Jan 2019 11:19:37 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Tue, 15 Jan 2019 11:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-XpYH6sRWbp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02034.txt.bz2
Content-length: 3201
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 15 Jan 2019, ktkachov at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
>
> --- Comment #8 from ktkachov at gcc dot gnu.org ---
> btw looks likes ICC vectorises this as well as unrolling:
> ..B1.14:
> movl (%rcx,%rbx,4), %r15d
> vmovsd (%rdi,%r15,8), %xmm2
> movl 4(%rcx,%rbx,4), %r15d
> vmovhpd (%rdi,%r15,8), %xmm2, %xmm3
> movl 8(%rcx,%rbx,4), %r15d
> vfmadd231pd (%r10,%rbx,8), %xmm3, %xmm0
> vmovsd (%rdi,%r15,8), %xmm4
> movl 12(%rcx,%rbx,4), %r15d
> vmovhpd (%rdi,%r15,8), %xmm4, %xmm5
> movl 16(%rcx,%rbx,4), %r15d
> vfmadd231pd 16(%r10,%rbx,8), %xmm5, %xmm1
> vmovsd (%rdi,%r15,8), %xmm6
> movl 20(%rcx,%rbx,4), %r15d
> vmovhpd (%rdi,%r15,8), %xmm6, %xmm7
> movl 24(%rcx,%rbx,4), %r15d
> vfmadd231pd 32(%r10,%rbx,8), %xmm7, %xmm0
> vmovsd (%rdi,%r15,8), %xmm8
> movl 28(%rcx,%rbx,4), %r15d
> vmovhpd (%rdi,%r15,8), %xmm8, %xmm9
> vfmadd231pd 48(%r10,%rbx,8), %xmm9, %xmm1
> addq $8, %rbx
> cmpq %r14, %rbx
> jb ..B1.14
>
> Is that something GCC could reasonably do?
GCC could choose a larger vectorization factor, yes.
The longer epilogue could be vectorized with the same
vector size again then.
>From gcc-bugs-return-629226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 11:30:58 2019
Return-Path: <gcc-bugs-return-629226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39531 invoked by alias); 15 Jan 2019 11:30: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 39483 invoked by uid 48); 15 Jan 2019 11:30:53 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88855] New: [9 Regression] ICE: verify_ssa failed (error: SSA_NAME_OCCURS_IN_ABNORMAL_PHI should be set)
Date: Tue, 15 Jan 2019 11:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02035.txt.bz2
Content-length: 1809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88855
Bug ID: 88855
Summary: [9 Regression] ICE: verify_ssa failed (error:
SSA_NAME_OCCURS_IN_ABNORMAL_PHI should be set)
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-checking, ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc-9.0.0-alpha20190113 snapshot (r267906) ICEs when compiling
gcc/testsuite/gcc.dg/torture/pr82402.c w/ -O1 -ftree-loop-if-convert -ftree-vrp
-fno-tree-copy-prop -fno-tree-dce -fno-tree-dominator-opts:
% gcc-9.0.0-alpha20190113 -O1 -ftree-loop-if-convert -ftree-vrp
-fno-tree-copy-prop -fno-tree-dce -fno-tree-dominator-opts -c
gcc/testsuite/gcc.dg/torture/pr82402.c
gcc/testsuite/gcc.dg/torture/pr82402.c: In function 'e':
gcc/testsuite/gcc.dg/torture/pr82402.c:13:5: error:
SSA_NAME_OCCURS_IN_ABNORMAL_PHI should be set
13 | int e ()
| ^
for SSA_NAME: .MEM_7 in statement:
.MEM_5(ab) = PHI <.MEM_7(5), .MEM_9(ab)(6)>
PHI argument
.MEM_7
for PHI node
.MEM_5(ab) = PHI <.MEM_7(5), .MEM_9(ab)(6)>
during GIMPLE pass: ifcvt
gcc/testsuite/gcc.dg/torture/pr82402.c:13:5: internal compiler error:
verify_ssa failed
0xf914ff verify_ssa(bool, bool)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/tree-ssa.c:1188
0xc897bd execute_function_todo
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:1984
0xc8a5be execute_todo
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/passes.c:2031
>From gcc-bugs-return-629227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 11:57:17 2019
Return-Path: <gcc-bugs-return-629227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94451 invoked by alias); 15 Jan 2019 11:57:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91085 invoked by uid 48); 15 Jan 2019 11:57:11 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37835] -fno-automatic does not work for derived types with default initalizer
Date: Tue, 15 Jan 2019 11:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-37835-4-Lib6gooRsw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02036.txt.bz2
Content-length: 1101
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37835
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Updated patch
--- ../_clean/gcc/fortran/resolve.c 2019-01-13 08:36:53.000000000 +0100
+++ gcc/fortran/resolve.c 2019-01-15 11:06:51.000000000 +0100
@@ -16649,7 +16649,7 @@ resolve_types (gfc_namespace *ns)
gfc_traverse_ns (ns, resolve_values);
- if (ns->save_all)
+ if (ns->save_all || !flag_automatic)
gfc_save_all (ns);
iter_stack = NULL;
With this patch the tests
gfortran.dg/dec_static_2.f90
gfortran.dg/save_1.f90
gfortran.dg/save_5.f90
gfortran.dg/save_6.f90
regress with
Warning: Legacy Extension: Duplicate SAVE attribute specified at (1)
At this point I don't know what to do.
I can
(1) adjust the tests by removing the explicit SAVEs,
(2) add -w to the options to silence the warning,
(3) adjust the doc to say that -fno-automatic should not be used in TUs with
variables having an explicit SAVE attribute,
(4) add a suitable condition to the test,
(5) leave thing as they are now and close the PR as WONTFIX or INVALID,
(6) ...
>From gcc-bugs-return-629228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 11:58:11 2019
Return-Path: <gcc-bugs-return-629228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14237 invoked by alias); 15 Jan 2019 11:58:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 10189 invoked by uid 48); 15 Jan 2019 11:58:07 -0000
From: "doko at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88856] New: [8/9 Regression] gfortran producing wrong code with -funroll-loops
Date: Tue, 15 Jan 2019 11:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: doko at debian dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02037.txt.bz2
Content-length: 841
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88856
Bug ID: 88856
Summary: [8/9 Regression] gfortran producing wrong code with
-funroll-loops
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: doko at debian dot org
Target Milestone: ---
seen when build scipy on s390x with the current GCC 8 branch. According to the
Debian report [1] this is tracked down to miscompilation of one Fortran file
with -funroll-loops. The Ubuntu report [2] has a "standalone" python test case.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915738
[2] https://bugs.launchpad.net/ubuntu/+source/python-scipy/+bug/1811798
>From gcc-bugs-return-629229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 12:09:59 2019
Return-Path: <gcc-bugs-return-629229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43164 invoked by alias); 15 Jan 2019 12:09: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 43058 invoked by uid 48); 15 Jan 2019 12:09:49 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42958] Weird temporary array allocation
Date: Tue, 15 Jan 2019 12:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-42958-4-24lvWyqMRl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-42958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-42958-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02038.txt.bz2
Content-length: 375
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=42958
--- Comment #25 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> If you find anything still missing in the library, please let me know.
> I thought I had converted everything to the macros, which are fairly
> easy to change, but I may be mistaken.
Is there anything left? or could this PR be closed as FIXED?
>From gcc-bugs-return-629230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 12:11:46 2019
Return-Path: <gcc-bugs-return-629230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45356 invoked by alias); 15 Jan 2019 12: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 45210 invoked by uid 48); 15 Jan 2019 12:11:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/70303] Value-initialized debug iterators
Date: Tue, 15 Jan 2019 12:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-70303-4-hRTLJ7IsB5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02039.txt.bz2
Content-length: 222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70303
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
My reading of the N3644 changes is that only equality comparisons are
supported, not relational ones.
>From gcc-bugs-return-629231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 12:14:53 2019
Return-Path: <gcc-bugs-return-629231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47957 invoked by alias); 15 Jan 2019 12:14: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 47899 invoked by uid 48); 15 Jan 2019 12:14:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/70303] Value-initialized debug iterators
Date: Tue, 15 Jan 2019 12:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-70303-4-CHD1561hm3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02040.txt.bz2
Content-length: 268
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70303
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Or is the implication of equality being valid that a+n is valid for n==0, and
therefore b-a is valid, and therefore relational ops are valid?
>From gcc-bugs-return-629232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 12:28:35 2019
Return-Path: <gcc-bugs-return-629232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81067 invoked by alias); 15 Jan 2019 12:28: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 76114 invoked by uid 48); 15 Jan 2019 12:28:29 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Tue, 15 Jan 2019 12:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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: attachments.created
Message-ID: <bug-88791-4-VWoCJlaCsJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02041.txt.bz2
Content-length: 238
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #12 from dominik.strasser@onespin-solutions.com ---
Created attachment 45434
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45434&action=edit
Debug output in gdb
>From gcc-bugs-return-629233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 12:39:18 2019
Return-Path: <gcc-bugs-return-629233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92590 invoked by alias); 15 Jan 2019 12:39: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 92526 invoked by uid 48); 15 Jan 2019 12:39:13 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Tue, 15 Jan 2019 12:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88810-4-n0uvbrD6hW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02042.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
As far as I can see, the duplicated code does not do anything bad,
and removing the duplicate also would not do anything bad.
A patch removing the duplication is pre-approved, provided it
passes a regression test.
>From gcc-bugs-return-629234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 12:55:14 2019
Return-Path: <gcc-bugs-return-629234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75766 invoked by alias); 15 Jan 2019 12:55:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75439 invoked by uid 48); 15 Jan 2019 12:55:09 -0000
From: "will at benfold dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88857] New: ICE in build_value_init
Date: Tue, 15 Jan 2019 12: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: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: will at benfold 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-88857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02043.txt.bz2
Content-length: 2587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88857
Bug ID: 88857
Summary: ICE in build_value_init
Product: gcc
Version: 7.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: will at benfold dot com
Target Milestone: ---
ICE on invalid code (g calls f with the wrong number of args).
----
class Foo
{
int a;
};
void f (const Foo &, int);
void g (auto)
{
f({});
}
----
$ g++ test.cpp -o test.o
test.cpp: In function ‘void g(auto:1)’:
test.cpp:10:7: internal compiler error: in build_value_init, at cp/init.c:338
f({});
^
0x6ac21f build_value_init(tree_node*, int)
../../gcc/cp/init.c:337
0x5d8379 convert_like_real
../../gcc/cp/call.c:6702
0x5d80a6 convert_like_real
../../gcc/cp/call.c:6844
0x5e0363 initialize_reference(tree_node*, tree_node*, int, int)
../../gcc/cp/call.c:10437
0x6a055d convert_for_initialization(tree_node*, tree_node*, tree_node*, int,
impl_conv_rhs, tree_node*, int, int)
../../gcc/cp/typeck.c:8679
0x6a178c convert_arguments
../../gcc/cp/typeck.c:3818
0x6a178c cp_build_function_call_vec(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, int)
../../gcc/cp/typeck.c:3660
0x5e07e3 build_new_function_call(tree_node*, vec<tree_node*, va_gc,
vl_embed>**, bool, int)
../../gcc/cp/call.c:4243
0x6c03a1 finish_call_expr(tree_node*, vec<tree_node*, va_gc, vl_embed>**, bool,
bool, int)
../../gcc/cp/semantics.c:2454
0x67393c cp_parser_postfix_expression
../../gcc/cp/parser.c:6997
0x67426d cp_parser_unary_expression
../../gcc/cp/parser.c:8108
0x675013 cp_parser_cast_expression
../../gcc/cp/parser.c:8786
0x675787 cp_parser_binary_expression
../../gcc/cp/parser.c:8887
0x675e54 cp_parser_assignment_expression
../../gcc/cp/parser.c:9174
0x67904a cp_parser_expression
../../gcc/cp/parser.c:9343
0x67da78 cp_parser_expression_statement
../../gcc/cp/parser.c:10898
0x66a8b9 cp_parser_statement
../../gcc/cp/parser.c:10714
0x66b71d cp_parser_statement_seq_opt
../../gcc/cp/parser.c:11040
0x66b7c7 cp_parser_compound_statement
../../gcc/cp/parser.c:10994
0x67c550 cp_parser_function_body
../../gcc/cp/parser.c:21455
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-629235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:01:29 2019
Return-Path: <gcc-bugs-return-629235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33821 invoked by alias); 15 Jan 2019 13: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 33137 invoked by uid 48); 15 Jan 2019 13:00:44 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Tue, 15 Jan 2019 13:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4-z0UD3WmZr0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02044.txt.bz2
Content-length: 3331
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #13 from dominik.strasser@onespin-solutions.com ---
The crash is not 100% reproducible. Looks like it is a race.
I'll check whether I can give you access to a system on our side.
I also encountered a differnt crash:
[Switching to Thread 0x7fffb920b700 (LWP 45227)]
0x00007ffff7357d76 in __asan::AsanThread::isUnwinding (this=0x7fffb9944000) at
../../../../gcc-git/libsanitizer/asan/asan_thread.h:126
126 bool isUnwinding() const { return unwinding_; }
(gdb) p unwinding_
Cannot access memory at address 0x7fffb9951e80
(gdb) up
#1 0x00007ffff74a19ad in __asan::GetStackTrace (fast=true, context=0x0,
bp=140736299312784, pc=140737342216507, max_depth=100, stack=0x7fffb9209e00)
at ../../../../gcc-git/libsanitizer/asan/asan_stack.h:40
40 if ((t = GetCurrentThread()) && !t->isUnwinding()) {
#0 0x00007ffff7357d76 in __asan::AsanThread::isUnwinding (this=0x7fffb92f9000)
at ../../../../gcc-git/libsanitizer/asan/asan_thread.h:126
#1 0x00007ffff74a19ad in __asan::GetStackTrace (fast=true, context=0x0,
bp=140736316278416, pc=140737342216507, max_depth=100, stack=0x7fffba237e00)
at ../../../../gcc-git/libsanitizer/asan/asan_stack.h:40
#2 operator new (size=32) at
../../../../gcc-git/libsanitizer/asan/asan_new_delete.cc:104
#3 0x00000000004f11b5 in
__gnu_cxx::new_allocator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > >::allocate
(this=0x7fffba238928, __n=1)
at /local/strasser/gcc-git/include/c++/9.0.0/ext/new_allocator.h:114
#4 0x00000000004ebf38 in
std::allocator_traits<std::allocator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > >::allocate (__a=..., __n=1)
at /local/strasser/gcc-git/include/c++/9.0.0/bits/alloc_traits.h:444
#5 0x00000000004e4978 in std::_Vector_base<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >,
std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > > >::_M_allocate (this=0x7fffba238928, __n=1) at
/local/strasser/gcc-git/include/c++/9.0.0/bits/stl_vector.h:343
#6 0x00000000005b61e3 in std::vector<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >,
std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > >
>::_M_allocate_and_copy<__gnu_cxx::__normal_iterator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > const*,
std::vector<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> > > > > > (this=0x7fffba238928,
__n=1, __first="SATEQC",
__last=<error: Cannot access memory at address 0x400000500000503>) at
/local/strasser/gcc-git/include/c++/9.0.0/bits/stl_vector.h:1472
#7 0x00000000005b3a5b in std::vector<std::__cxx11::basic_string<char,
std::char_traits<char>, std::allocator<char> >,
std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>,
std::allocator<char> > > >::operator= (this=0x7fffba238928, __x=std::vector of
length 1, capacity 1 = {...}) at
/local/strasser/gcc-git/include/c++/9.0.0/bits/vector.tcc:227
...
>From gcc-bugs-return-629236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:27:40 2019
Return-Path: <gcc-bugs-return-629236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27055 invoked by alias); 15 Jan 2019 13:27: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 27012 invoked by uid 48); 15 Jan 2019 13:27:36 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88857] ICE in build_value_init
Date: Tue, 15 Jan 2019 13:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88857-4-QVzaH4P6GW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02045.txt.bz2
Content-length: 656
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88857
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed. Not a recent regression.
>From gcc-bugs-return-629237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:35:37 2019
Return-Path: <gcc-bugs-return-629237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71458 invoked by alias); 15 Jan 2019 13:35: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 69510 invoked by uid 48); 15 Jan 2019 13:35:32 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88857] [7/8/9 Regression] ICE in build_value_init
Date: Tue, 15 Jan 2019 13:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88857-4-knjB97c7GU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02046.txt.bz2
Content-length: 525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88857
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |7.5
Summary|ICE in build_value_init |[7/8/9 Regression] ICE in
| |build_value_init
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r202612.
>From gcc-bugs-return-629238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:36:28 2019
Return-Path: <gcc-bugs-return-629238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72722 invoked by alias); 15 Jan 2019 13:36:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72666 invoked by uid 48); 15 Jan 2019 13:36:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88857] [7/8/9 Regression] ICE in build_value_init
Date: Tue, 15 Jan 2019 13:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88857-4-AYXczbiOER@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02047.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88857
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
>From gcc-bugs-return-629240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:37:52 2019
Return-Path: <gcc-bugs-return-629240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74919 invoked by alias); 15 Jan 2019 13:37:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74855 invoked by uid 48); 15 Jan 2019 13:37:48 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88855] [9 Regression] ICE: verify_ssa failed (error: SSA_NAME_OCCURS_IN_ABNORMAL_PHI should be set)
Date: Tue, 15 Jan 2019 13:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-88855-4-UHpgoUnAiA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02049.txt.bz2
Content-length: 636
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88855
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-15
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look.
>From gcc-bugs-return-629239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:37:28 2019
Return-Path: <gcc-bugs-return-629239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74002 invoked by alias); 15 Jan 2019 13:37:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73929 invoked by uid 48); 15 Jan 2019 13:37:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88856] [8/9 Regression] gfortran producing wrong code with -funroll-loops
Date: Tue, 15 Jan 2019 13:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88856-4-0V9tkTDjRg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02048.txt.bz2
Content-length: 419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88856
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.3
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I guess we need something better than a python testcase.
>From gcc-bugs-return-629241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:42:28 2019
Return-Path: <gcc-bugs-return-629241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78560 invoked by alias); 15 Jan 2019 13:42: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 78470 invoked by uid 48); 15 Jan 2019 13:42:21 -0000
From: "Johan.karlsson at enea dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/86964] Too many debug symbols included, especially for extern globals
Date: Tue, 15 Jan 2019 13:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 6.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Johan.karlsson at enea 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-86964-4-4srdFi63hw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86964-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86964-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02050.txt.bz2
Content-length: 776
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86964
Johan.karlsson at enea dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Johan.karlsson at enea dot com
--- Comment #5 from Johan.karlsson at enea dot com ---
I'm also affected by this "lack of feature" I looked into dwarf2out.c to see
what I could do about it. Unfortunately I quickly noticed that I'm definitely
going to break stuff if I try to tweak the code.
So I'm hoping that some GCC developer can take the time implement
-feliminate-unused-debug-symbols for DWARF.
Right now the ELF file gets so large the my debugger crashes. So I'm stuck
using GCC 4 or 5.
>From gcc-bugs-return-629242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:43:03 2019
Return-Path: <gcc-bugs-return-629242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80412 invoked by alias); 15 Jan 2019 13:43:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80324 invoked by uid 48); 15 Jan 2019 13:42:57 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88858] New: ICE in rtl_verify_fallthru, at cfgrtl.c:2930 in Firefox build with LTO and PGO
Date: Tue, 15 Jan 2019 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02051.txt.bz2
Content-length: 2133
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88858
Bug ID: 88858
Summary: ICE in rtl_verify_fallthru, at cfgrtl.c:2930 in
Firefox build with LTO and PGO
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org, marxin at gcc dot gnu.org
Target Milestone: ---
Using following git branch:
https://github.com/marxin/gecko-dev/tree/lto-stable-2
and r267935 of GCC I see following ICE in profile_use phase:
108:40.08 /home/marxin/Programming/gecko-dev/js/src/vm/JSAtom.cpp: In function
‘Atomize’:
108:40.08 /home/marxin/Programming/gecko-dev/js/src/vm/JSAtom.cpp:965: error:
verify_flow_info: Incorrect fallthru 423->424
108:40.08 965 | }
108:40.08 |
108:40.08 /home/marxin/Programming/gecko-dev/js/src/vm/JSAtom.cpp:965: error:
wrong insn in the fallthru edge
108:40.08 (barrier 6592 9309 2658)
108:40.08 during RTL pass: bbro
108:40.08 /home/marxin/Programming/gecko-dev/js/src/vm/JSAtom.cpp:965: internal
compiler error: in rtl_verify_fallthru, at cfgrtl.c:2930
108:40.08 0x6417c0 _fatal_insn(char const*, rtx_def const*, char const*, int,
char const*)
108:40.08 /home/marxin/Programming/gcc/gcc/rtl-error.c:108
108:40.08 0x80dba1 rtl_verify_fallthru
108:40.08 /home/marxin/Programming/gcc/gcc/cfgrtl.c:2930
108:40.08 0x80dba1 rtl_verify_flow_info
108:40.08 /home/marxin/Programming/gcc/gcc/cfgrtl.c:3031
108:40.08 0x7f1e0d verify_flow_info()
108:40.08 /home/marxin/Programming/gcc/gcc/cfghooks.c:263
108:40.08 0x80b8b9 checking_verify_flow_info
108:40.08 /home/marxin/Programming/gcc/gcc/cfghooks.h:198
108:40.08 0x80b8b9 cfg_layout_finalize()
108:40.08 /home/marxin/Programming/gcc/gcc/cfgrtl.c:4359
108:40.08 0x13a18f9 execute
108:40.08 /home/marxin/Programming/gcc/gcc/bb-reorder.c:2658
would be non-trivial to reduce/debug.
>From gcc-bugs-return-629243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:49:04 2019
Return-Path: <gcc-bugs-return-629243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129623 invoked by alias); 15 Jan 2019 13:49: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 129500 invoked by uid 48); 15 Jan 2019 13:48:58 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88079] warn about procedure arguments without INTENT
Date: Tue, 15 Jan 2019 13:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88079-4-CpataFAkxJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88079-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88079-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02052.txt.bz2
Content-length: 854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88079
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
CC| |tkoenig at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to kargl from comment #1)
> How does gfortran differential between new Fortran code and
> old Fortran code. It is the programmer's responsibility to
> know what he or she is doing.
Well, anybody who wants to use old code should never use
such an option :-)
This could be useful, I suppose.
>From gcc-bugs-return-629244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:52:42 2019
Return-Path: <gcc-bugs-return-629244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119429 invoked by alias); 15 Jan 2019 13:52: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 114233 invoked by uid 48); 15 Jan 2019 13:52:37 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88801] [9 Regression] Performance regression on 473.astar on aarch64
Date: Tue, 15 Jan 2019 13:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88801-4-nPuFQp1I9U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02053.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88801
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #2 from ktkachov at gcc dot gnu.org ---
I couldn't reproduce it myself after all and I don't see it anymore in our
testers
>From gcc-bugs-return-629245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:52:43 2019
Return-Path: <gcc-bugs-return-629245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120613 invoked by alias); 15 Jan 2019 13:52: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 116650 invoked by uid 48); 15 Jan 2019 13:52:39 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/26163] [meta-bug] missed optimization in SPEC (2k17, 2k and 2k6 and 95)
Date: Tue, 15 Jan 2019 13:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords: meta-bug, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-26163-4-S3E35hiAhc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
References: <bug-26163-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02054.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=26163
Bug 26163 depends on bug 88801, which changed state.
Bug 88801 Summary: [9 Regression] Performance regression on 473.astar on aarch64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88801
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-629246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 13:58:17 2019
Return-Path: <gcc-bugs-return-629246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72162 invoked by alias); 15 Jan 2019 13:58:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 72080 invoked by uid 48); 15 Jan 2019 13:58:12 -0000
From: "will at benfold dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88857] [7/8/9 Regression] ICE in build_value_init
Date: Tue, 15 Jan 2019 13:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: will at benfold dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88857-4-uv710FXPa5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02055.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88857
--- Comment #3 from Will Benfold <will at benfold dot com> ---
(In reply to Marek Polacek from comment #2)
> Started with r202612.
Is that just because before r202612, there was no support for 'auto' in a
function declaration?
I see the ICE with every release down to 4.7.1 (the earliest version I have
access to), if I change g to:
template<typename>
void g ()
{
f({});
}
>From gcc-bugs-return-629247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:12:57 2019
Return-Path: <gcc-bugs-return-629247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18345 invoked by alias); 15 Jan 2019 14:12: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 15774 invoked by uid 48); 15 Jan 2019 14:12:50 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37826] gfortran emits incorrect debug information if compiled with -finit-local-zero
Date: Tue, 15 Jan 2019 14:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: steven at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_severity
Message-ID: <bug-37826-4-pGyKvBiTLC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02056.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37826
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Severity|normal |enhancement
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
AFAICT -gstabs+ is no longer supported on OSX.
The PR is more than ten year old and I don't understand what is the expected
behavior.
Should not it be closed as FIXED or WORKSFORME?
>From gcc-bugs-return-629248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:15:48 2019
Return-Path: <gcc-bugs-return-629248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26799 invoked by alias); 15 Jan 2019 14:15:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26530 invoked by uid 48); 15 Jan 2019 14:15:22 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65847] SSE2 code for adding two structs is much worse at -O3 than at -O2
Date: Tue, 15 Jan 2019 14:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-65847-4-szyqZQ2NPN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02057.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65847
--- Comment #2 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
I've just found the same issue. The code is a bit different (here, AFAIK, this
is AVX), but I assume that the cause is the same.
With -O2:
foo:
.LFB0:
.cfi_startproc
vaddsd %xmm3, %xmm1, %xmm1
vaddsd %xmm2, %xmm0, %xmm0
ret
.cfi_endproc
With -O3:
foo:
.LFB0:
.cfi_startproc
vmovq %xmm0, -40(%rsp)
vmovq %xmm1, -32(%rsp)
vmovapd -40(%rsp), %xmm5
vmovq %xmm2, -24(%rsp)
vmovq %xmm3, -16(%rsp)
vaddpd -24(%rsp), %xmm5, %xmm4
vmovaps %xmm4, -40(%rsp)
vmovsd -32(%rsp), %xmm1
vmovsd -40(%rsp), %xmm0
ret
.cfi_endproc
Tested with:
gcc (Debian 20190102-1) 9.0.0 20190102 (experimental) [trunk revision 267505]
>From gcc-bugs-return-629249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:25:51 2019
Return-Path: <gcc-bugs-return-629249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43058 invoked by alias); 15 Jan 2019 14:25: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 42998 invoked by uid 48); 15 Jan 2019 14:25:46 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/78421] [7/8/9 Regression] vect-strided-a-u8-i2-gap.c fails on armeb
Date: Tue, 15 Jan 2019 14:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris 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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-78421-4-UTVwKcUNBx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78421-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78421-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02058.txt.bz2
Content-length: 585
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78421
Tamar Christina <tnfchris at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
CC| |tnfchris at gcc dot gnu.org
Resolution|--- |FIXED
--- Comment #10 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hi Martin,
sorry I wasn't on CC here. Yes the issue no longer fails on GCC 8/9.
>From gcc-bugs-return-629250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:28:22 2019
Return-Path: <gcc-bugs-return-629250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47986 invoked by alias); 15 Jan 2019 14:28:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47955 invoked by uid 48); 15 Jan 2019 14:28:17 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/39795] Support round-to-zero in Fortran front-end
Date: Tue, 15 Jan 2019 14:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-39795-4-H0Tmhp8xMm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-39795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-39795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02059.txt.bz2
Content-length: 480
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=39795
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Would it be acceptable to close this rotting PR to WONTFIX?
If no, IMO it should be moved to 'target'.
>From gcc-bugs-return-629251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:34:46 2019
Return-Path: <gcc-bugs-return-629251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40391 invoked by alias); 15 Jan 2019 14:34: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 40310 invoked by uid 48); 15 Jan 2019 14:34:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88854-4-0Q3AjXdyUz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02060.txt.bz2
Content-length: 270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Causes
FAIL: gcc.dg/tree-ssa/ssa-pre-30.c scan-tree-dump-times pre "Replaced MEM" 2
the extra entry somehow confuses PRE (AVAIL compute I guess).
>From gcc-bugs-return-629252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:36:56 2019
Return-Path: <gcc-bugs-return-629252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69887 invoked by alias); 15 Jan 2019 14: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 68526 invoked by uid 48); 15 Jan 2019 14:36:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88046] [9 Regression] ICE in add_data_member_location_attribute at gcc/dwarf2out.c:19237 since r261885
Date: Tue, 15 Jan 2019 14:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88046-4-psp17zIBhG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02061.txt.bz2
Content-length: 861
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88046
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
This particular ICE can be fixed with avoiding generating inheritance DIEs
late.
Index: gcc/dwarf2out.c
===================================================================
--- gcc/dwarf2out.c (revision 267930)
+++ gcc/dwarf2out.c (working copy)
@@ -25046,7 +25046,7 @@ gen_member_die (tree type, dw_die_ref co
the TREE node representing the appropriate (containing) type. */
/* First output info about the base classes. */
- if (binfo)
+ if (binfo && early_dwarf)
{
vec<tree, va_gc> *accesses = BINFO_BASE_ACCESSES (binfo);
int i;
I am going to test that.
>From gcc-bugs-return-629253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:42:18 2019
Return-Path: <gcc-bugs-return-629253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88494 invoked by alias); 15 Jan 2019 14:42:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88417 invoked by uid 48); 15 Jan 2019 14:42:12 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] New: FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 14:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcctarget
Message-ID: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02062.txt.bz2
Content-length: 2533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
Bug ID: 88859
Summary: FAIL: experimental/string_view/operators/wchar_t/2.cc
execution test
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
Target Milestone: ---
Target: x32
On x32, r267938 gave
FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Program received signal SIGSEGV, Segmentation fault.
0xf7be907c in __wmemcmp_avx2_movbe () from /libx32/libc.so.6
(gdb) bt
#0 0xf7be907c in __wmemcmp_avx2_movbe () from /libx32/libc.so.6
#1 0x00401304 in std::char_traits<wchar_t>::compare (__n=<optimized out>,
__s2=<optimized out>, __s1=<optimized out>)
at
/export/build/gnu/tools-build/gcc-x32-debug/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/bits/char_traits.h:422
#2 std::experimental::fundamentals_v1::basic_string_view<wchar_t,
std::char_traits<wchar_t> >::compare (__str=..., this=<synthetic pointer>)
at
/export/build/gnu/tools-build/gcc-x32-debug/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/experimental/string_view:290
#3 std::experimental::fundamentals_v1::operator==<wchar_t,
std::char_traits<wchar_t> > (__y=..., __x=...)
at
/export/build/gnu/tools-build/gcc-x32-debug/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/experimental/string_view:451
#4 std::experimental::fundamentals_v1::operator!=<wchar_t,
std::char_traits<wchar_t> > (__x=..., __y=..., __y@entry=...)
at
/export/build/gnu/tools-build/gcc-x32-debug/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/experimental/string_view:481
#5 0x00401fa9 in test01 ()
at
/export/build/gnu/tools-build/gcc-x32-debug/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/bits/char_traits.h:433
#6 0x0040111c in main ()
at
/export/gnu/import/git/sources/gcc/libstdc++-v3/testsuite/experimental/string_view/operators/wchar_t/2.cc:241
(gdb) f 1
#1 0x00401304 in std::char_traits<wchar_t>::compare (__n=<optimized out>,
__s2=<optimized out>, __s1=<optimized out>)
at
/export/build/gnu/tools-build/gcc-x32-debug/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/bits/char_traits.h:422
422 return wmemcmp(__s1, __s2, __n);
(gdb)
>From gcc-bugs-return-629254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:47:35 2019
Return-Path: <gcc-bugs-return-629254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97664 invoked by alias); 15 Jan 2019 14:47: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 97603 invoked by uid 48); 15 Jan 2019 14:47:31 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88854-4-lqrfpJMuIH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02063.txt.bz2
Content-length: 699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
--- Comment #4 from Matthias Kretz <kretz at kde dot org> ---
Another test case, which the patch doesn't optimize:
short f(int *a, short *b) {
short y = *b; // 1
int x = *a; // 2
*b = 1;
*a = x;
return y;
}
The loads in 1+2 are either UB or a and b must not alias. Consequently the
store to b won't change a and the store to a is dead.
General rule:
Given two pointers a and b of different type, where b is not a pointer to char,
unsigned char, or std::byte, if
- a load of a is followed by a load of b, or
- a store to a is followed by a load of b
then a and b are guaranteed to point to different addresses.
>From gcc-bugs-return-629255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:49:08 2019
Return-Path: <gcc-bugs-return-629255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103000 invoked by alias); 15 Jan 2019 14:49:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102704 invoked by uid 48); 15 Jan 2019 14:48:52 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 14:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-pmR5PUfb6u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02064.txt.bz2
Content-length: 907
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Hmm, I can no longer reproduce -g0 vs -g on x86_64-linux. Ians testresults now
list
FAIL: g++.dg/asan/pr62017.C -O2 -flto (internal compiler error)
FAIL: g++.dg/asan/pr62017.C -O2 -flto (test for excess errors)
FAIL: g++.dg/asan/pr62017.C -O2 -flto -flto-partition=none (internal
compiler error)
FAIL: g++.dg/asan/pr62017.C -O2 -flto -flto-partition=none (test for excess
errors)
FAIL: g++.dg/asan/pr78651.C -O2 -flto (internal compiler error)
FAIL: g++.dg/asan/pr78651.C -O2 -flto (test for excess errors)
FAIL: g++.dg/asan/pr78651.C -O2 -flto -flto-partition=none (internal
compiler error)
FAIL: g++.dg/asan/pr78651.C -O2 -flto -flto-partition=none (test for excess
errors)
but I can't reproduce with pr62017.C or pr78651.C either right now.
>From gcc-bugs-return-629256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:52:35 2019
Return-Path: <gcc-bugs-return-629256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60322 invoked by alias); 15 Jan 2019 14:52:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 55960 invoked by uid 55); 15 Jan 2019 14:52:30 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 14:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88854-4-9fwYako0Nu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02065.txt.bz2
Content-length: 1225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
--- Comment #5 from rguenther at suse dot de <rguenther at suse dot de> ---
On Tue, 15 Jan 2019, kretz at kde dot org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
>
> --- Comment #4 from Matthias Kretz <kretz at kde dot org> ---
> Another test case, which the patch doesn't optimize:
>
> short f(int *a, short *b) {
> short y = *b; // 1
> int x = *a; // 2
> *b = 1;
> *a = x;
> return y;
> }
>
> The loads in 1+2 are either UB or a and b must not alias. Consequently the
> store to b won't change a and the store to a is dead.
>
> General rule:
> Given two pointers a and b of different type, where b is not a pointer to char,
> unsigned char, or std::byte, if
> - a load of a is followed by a load of b, or
> - a store to a is followed by a load of b
> then a and b are guaranteed to point to different addresses.
Yeah, we do not perform this kind of "flow-sensitive" TBAA. So
when trying to DSE *a = x; we only look at
int x = *a;
*b = 1;
*a = x;
and do not consider the earlier load from *b at all because it is
not on the path from the load making the store possibly redundant.
>From gcc-bugs-return-629257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:53:28 2019
Return-Path: <gcc-bugs-return-629257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63244 invoked by alias); 15 Jan 2019 14:53: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 63083 invoked by uid 48); 15 Jan 2019 14:53:22 -0000
From: "dominik.strasser@onespin-solutions.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Tue, 15 Jan 2019 14:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominik.strasser@onespin-solutions.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-88791-4-SPC4SJqAgR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02066.txt.bz2
Content-length: 4541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #14 from dominik.strasser@onespin-solutions.com ---
With the 9.0 version of libasan I also experience an additional crash which is
100% reproducible:
buffer points to non-accessible memory:
(gdb) p buffer
$1 = (__sanitizer::u64 *) 0x7fff49eff000
(gdb) p *buffer
Cannot access memory at address 0x7fff49eff000
log:
...
==56701==T7 TSDDtor
==56701==T7 exited
==56701==poisoning: 0x7fff38c62350 250
==56701==T5 TSDDtor
==56701==poisoning: 0x7fff38c71480 3c8
==56701==T5 exited
==56701==poisoning: 0x7fff38c76e10 128
[Thread 0x7fff21d46700 (LWP 63421) exited]
Thread 8 "TclShellThread" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fff20d44700 (LWP 63444)]
0x00007ffff7360744 in
__sanitizer::SizeClassAllocator64<__asan::AP64>::PackedCounterArray<__sanitizer::SizeClassAllocator64<__asan::AP64>::MemoryMapper>::Inc
(this=0x7fff20d42cb0, i=662)
at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_primary64.h:377
377 buffer[index] += 1ULL << bit_offset;
(gdb) where
#0 0x00007ffff7360744 in
__sanitizer::SizeClassAllocator64<__asan::AP64>::PackedCounterArray<__sanitizer::SizeClassAllocator64<__asan::AP64>::MemoryMapper>::Inc
(this=0x7fff20d42cb0, i=662)
at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_primary64.h:377
#1 0x00007ffff735fb93 in
__sanitizer::SizeClassAllocator64<__asan::AP64>::ReleaseFreeMemoryToOS<__sanitizer::SizeClassAllocator64<__asan::AP64>::MemoryMapper>
(free_array=0x604e00000000,
free_array_count=68304, chunk_size=64, allocated_pages_count=3872,
memory_mapper=0x7fff20d42db0) at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_primary64.h:498
#2 0x00007ffff735ea5e in
__sanitizer::SizeClassAllocator64<__asan::AP64>::MaybeReleaseToOS
(this=0x7ffff7534ea0 <__asan::instance>, class_id=4, force=false)
at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_primary64.h:840
#3 0x00007ffff735f289 in
__sanitizer::SizeClassAllocator64<__asan::AP64>::ReturnToAllocator
(this=0x7ffff7534ea0 <__asan::instance>, stat=0x7fff31ac8c40, class_id=4,
chunks=0x7fff31abc130,
n_chunks=126) at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_primary64.h:130
#4 0x00007ffff735e06c in
__sanitizer::SizeClassAllocator64LocalCache<__sanitizer::SizeClassAllocator64<__asan::AP64>
>::Drain (this=0x7fff31abb0e0, c=0x7fff31abc120,
allocator=0x7ffff7534ea0 <__asan::instance>, class_id=4, count=126) at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_local_cache.h:120
#5 0x00007ffff735d764 in
__sanitizer::SizeClassAllocator64LocalCache<__sanitizer::SizeClassAllocator64<__asan::AP64>
>::Drain (this=0x7fff31abb0e0, allocator=0x7ffff7534ea0 <__asan::instance>)
at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_local_cache.h:74
#6 0x00007ffff735ba03 in
__sanitizer::CombinedAllocator<__sanitizer::SizeClassAllocator64<__asan::AP64>,
__sanitizer::SizeClassAllocatorLocalCache<__sanitizer::SizeClassAllocator64<__asan::AP64>
>, __sanitizer::LargeMmapAllocator<__asan::AsanMapUnmapCallback,
__sanitizer::LargeMmapAllocatorPtrArrayDynamic> >::SwallowCache
(this=0x7ffff7534ea0 <__asan::instance>, cache=0x7fff31abb0e0)
at
../../../../gcc-git/libsanitizer/sanitizer_common/sanitizer_allocator_combined.h:159
#7 0x00007ffff735a8c1 in __asan::Allocator::CommitBack (this=0x7ffff7534ea0
<__asan::instance>, ms=0x7fff31abb060, stack=0x7fff20d42fb0) at
../../../../gcc-git/libsanitizer/asan/asan_allocator.cc:698
#8 0x00007ffff73560bd in __asan::AsanThreadLocalMallocStorage::CommitBack
(this=0x7fff31abb060) at
../../../../gcc-git/libsanitizer/asan/asan_allocator.cc:857
#9 0x00007ffff74af6a2 in __asan::AsanThread::Destroy (this=0x7fff31abb000) at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:102
#10 0x00007ffff74af647 in __asan::AsanThread::TSDDtor (tsd=0x7fff5d292460) at
../../../../gcc-git/libsanitizer/asan/asan_thread.cc:95
#11 0x00007ffff74a6dba in __asan::PlatformTSDDtor (tsd=0x7fff5d292460) at
../../../../gcc-git/libsanitizer/asan/asan_posix.cc:66
#12 0x00007fff5d07ac22 in __nptl_deallocate_tsd () from /lib64/libpthread.so.0
#13 0x00007fff5d07ae33 in start_thread () from /lib64/libpthread.so.0
#14 0x00007fff59f8dbad in clone () from /lib64/libc.so.6
>From gcc-bugs-return-629258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 14:57:57 2019
Return-Path: <gcc-bugs-return-629258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128423 invoked by alias); 15 Jan 2019 14:57: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 128354 invoked by uid 48); 15 Jan 2019 14:57:52 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 14:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88854-4-SnXesGAsTe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02067.txt.bz2
Content-length: 580
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
--- Comment #6 from Matthias Kretz <kretz at kde dot org> ---
Regarding gcc.dg/tree-ssa/ssa-pre-30.c
I'd argue that for `bar`, GCC may assume b == 0, because otherwise f would be
read both via int and float pointer, which is UB. So bar can be optimized to
`foo` shows a case I forgot in my "General rule". Pointers to integers that
only differ in signedness can do aliasing loads without UB and thus can't
trigger the optimization. And all the other aliasing exceptions listed in
http://eel.is/c++draft/basic.lval#11.
>From gcc-bugs-return-629259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:02:48 2019
Return-Path: <gcc-bugs-return-629259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108698 invoked by alias); 15 Jan 2019 15:02:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 108579 invoked by uid 48); 15 Jan 2019 15:02:43 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88854] redundant store after load that would makes aliasing UB
Date: Tue, 15 Jan 2019 15:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88854-4-DjUF5cPv7k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02068.txt.bz2
Content-length: 732
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88854
--- Comment #7 from Matthias Kretz <kretz at kde dot org> ---
(In reply to rguenther@suse.de from comment #5)
> Yeah, we do not perform this kind of "flow-sensitive" TBAA. So
> when trying to DSE *a = x; we only look at
>
> int x = *a;
> *b = 1;
> *a = x;
>
> and do not consider the earlier load from *b at all because it is
> not on the path from the load making the store possibly redundant.
However, if I annotate a and/or b as __restrict__ GCC does the DSE. I don't
think I want another DSE special case but a general case of inducing aliasing
knowledge, which may affect decisions throughout the whole program where the
pointers are used.
>From gcc-bugs-return-629260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:07:43 2019
Return-Path: <gcc-bugs-return-629260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120630 invoked by alias); 15 Jan 2019 15:07: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 120528 invoked by uid 48); 15 Jan 2019 15:07:38 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88795] ICE on class-template argument deduction if non-type parameter has indirection
Date: Tue, 15 Jan 2019 15:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-88795-4-orXnzGbqcw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02069.txt.bz2
Content-length: 922
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88795
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |dmalcolm at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
ICE occurs at gcc/tree.c:6811 here:
6809 case FUNCTION_TYPE:
6810 for (tree t = TYPE_ARG_TYPES (type); t; t = TREE_CHAIN (t))
6811 if (TREE_VALUE (t) != error_mark_node)
6812 hstate.add_object (TYPE_HASH (TREE_VALUE (t)));
6813 break;
where "t" itself is error_mark_node, and so the TREE_VALUE (t) is erroneous.
Am working on a fix
>From gcc-bugs-return-629261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:20:21 2019
Return-Path: <gcc-bugs-return-629261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57488 invoked by alias); 15 Jan 2019 15:20:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57423 invoked by uid 48); 15 Jan 2019 15:20:16 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Tue, 15 Jan 2019 15:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85949-4-7j1uOmn9S4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02070.txt.bz2
Content-length: 957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
--- Comment #2 from Jonny Grant <jg at jguk dot org> ---
Many thanks Martin. Your change is a big improvement.
I ran on Godbolt.org
g++ (GCC-Explorer-Build) 9.0.0 20190114 (experimental)
The carat is now at the end of the attributes - is there a way to get the carat
on the actual argument 3?
===================
#1 with x86-64 gcc (trunk)
<source>:7:82: error: 'format' attribute argument 3 value '1' does not refer to
a variable argument list
7 | void str_fmt(const char * const format, ...) __attribute__ ((format
(printf,1,1)));
|
^
Compiler returned: 1
===================
>From gcc-bugs-return-629262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:23:44 2019
Return-Path: <gcc-bugs-return-629262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83690 invoked by alias); 15 Jan 2019 15:23:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83601 invoked by uid 48); 15 Jan 2019 15:23:39 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88791] ASAN deadlocks in threaded application
Date: Tue, 15 Jan 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 7.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88791-4-PjU8zHba7r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88791-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02071.txt.bz2
Content-length: 643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88791
--- Comment #15 from Martin Liška <marxin at gcc dot gnu.org> ---
Okey, I really believe there's some ABI incompatibility between libsanitizer
and glibc. Maybe here:
https://github.com/gcc-mirror/gcc/blob/master/libsanitizer/sanitizer_common/sanitizer_linux_libcdep.cc#L266
or maybe struct ucontext_t does not match among GCC and glibc.
Anyway I would start with running GCC's libsanitizer tests in your build
directory:
$ make check -k -j10 RUNTESTFLAGS="asan.exp"
and
$ make check -k RUNTESTFLAGS="tsan.exp"
then search for '^FAIL' in
find gcc/testsuite/ -name '*.log'
>From gcc-bugs-return-629263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:25:33 2019
Return-Path: <gcc-bugs-return-629263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89993 invoked by alias); 15 Jan 2019 15:25: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 89038 invoked by uid 48); 15 Jan 2019 15:24:42 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-NSEt9URmnB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02072.txt.bz2
Content-length: 18144
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> Hmm, I can no longer reproduce -g0 vs -g on x86_64-linux. Ians testresults
> now
> list
>
> FAIL: g++.dg/asan/pr62017.C -O2 -flto (internal compiler error)
> FAIL: g++.dg/asan/pr62017.C -O2 -flto (test for excess errors)
> FAIL: g++.dg/asan/pr62017.C -O2 -flto -flto-partition=none (internal
> compiler error)
> FAIL: g++.dg/asan/pr62017.C -O2 -flto -flto-partition=none (test for
> excess errors)
> FAIL: g++.dg/asan/pr78651.C -O2 -flto (internal compiler error)
> FAIL: g++.dg/asan/pr78651.C -O2 -flto (test for excess errors)
> FAIL: g++.dg/asan/pr78651.C -O2 -flto -flto-partition=none (internal
> compiler error)
> FAIL: g++.dg/asan/pr78651.C -O2 -flto -flto-partition=none (test for
> excess errors)
>
> but I can't reproduce with pr62017.C or pr78651.C either right now.
81021 has indeed started to pass (I didn't notice when).
===== 62017 is:
$ /XC/9.4/usr/bin/lldb --
/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1 -fPIC
-feliminate-unused-debug-symbols -quiet -dumpdir ./ -dumpbase pr62017.exe
-mmacosx-version-min=10.12.0 -mtune=core2 -m32 -mmacosx-version-min=10.12.0
-mtune=core2 -auxbase-strip pr62017.exe.lto.o -g -O2 -O2 -version
-fdiagnostics-color=never -fno-openmp -fno-openacc -fPIC -fsanitize=address
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fmessage-length=0 -flto-partition=none
@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccyWmZmy -o pr62017.s
(lldb) target create
"/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1"
Current executable set to
'/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1' (x86_64).
(lldb) settings set -- target.run-args "-fPIC"
"-feliminate-unused-debug-symbols" "-quiet" "-dumpdir" "./" "-dumpbase"
"pr62017.exe" "-mmacosx-version-min=10.12.0" "-mtune=core2" "-m32"
"-mmacosx-version-min=10.12.0" "-mtune=core2" "-auxbase-strip"
"pr62017.exe.lto.o" "-g" "-O2" "-O2" "-version" "-fdiagnostics-color=never"
"-fno-openmp" "-fno-openacc" "-fPIC" "-fsanitize=address"
"-fno-diagnostics-show-caret" "-fno-diagnostics-show-line-numbers"
"-fmessage-length=0" "-flto-partition=none"
"@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccyWmZmy" "-o" "pr62017.s"
(lldb) b internal_error
Breakpoint 1: where = lto1`internal_error(char const*, ...) + 121 [inlined]
_ZN21auto_diagnostic_groupC4Ev, address = 0x00000001010abcb9
(lldb) r
Process 22051 launched:
'/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1' (x86_64)
GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision 267925]
(x86_64-apple-darwin16)
compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl version
isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision 267925]
(x86_64-apple-darwin16)
compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl version
isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Process 22051 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
frame #0: 0x0000000100f7a941 lto1`tree_to_shwi(t=0x0000000000000000) at
tree.c:7169
7166 tree_fits_shwi_p (const_tree t)
7167 {
7168 return (t != NULL_TREE
-> 7169 && TREE_CODE (t) == INTEGER_CST
7170 && wi::fits_shwi_p (wi::to_widest (t)));
7171 }
7172
Target 0: (lto1) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=1, address=0x0)
* frame #0: 0x0000000100f7a941 lto1`tree_to_shwi(t=0x0000000000000000) at
tree.c:7169
frame #1: 0x00000001007ddb3b
lto1`::add_data_member_location_attribute(die=0x000000014482b9b0,
decl=0x00000001448250c0, ctx=<unavailable>) at dwarf2out.c:19306
frame #2: 0x00000001007e6c3e lto1`::gen_struct_or_union_type_die(tree,
dw_die_ref, debug_info_usage) at dwarf2out.c:24580
frame #3: 0x00000001007e6b29
lto1`::gen_struct_or_union_type_die(type=0x0000000144826000,
context_die=0x000000014482b000, usage=<unavailable>)
frame #4: 0x00000001007e205e
lto1`::gen_tagged_type_die(type=0x0000000144826000, context_die=<unavailable>,
usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25430
frame #5: 0x00000001007e248f
lto1`::gen_typedef_die(decl=0x0000000144821558, context_die=0x000000014482b000)
at dwarf2out.c:25344
frame #6: 0x00000001007e2a15 lto1`::gen_decl_die(decl=0x0000000144821558,
origin=<unavailable>, ctx=<unavailable>, context_die=0x000000014482b000) at
dwarf2out.c:26314
frame #7: 0x00000001007c5ef3
lto1`::gen_type_die_with_usage(type=0x0000000144826000,
context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25495
frame #8: 0x00000001007c785a lto1`::gen_type_die(type=0x0000000144826000,
context_die=<unavailable>) at dwarf2out.c:25679
frame #9: 0x00000001007c80b0
lto1`::modified_type_die(type=0x0000000144826000, cv_quals=0,
reverse=<unavailable>, context_die=0x000000014482b870) at dwarf2out.c:13373
frame #10: 0x00000001007ca931
lto1`::add_type_attribute(object_die=0x000000014482b8c0, type=<unavailable>,
cv_quals=<unavailable>, reverse=<unavailable>, context_die=<unavailable>) at
dwarf2out.c:21601
frame #11: 0x00000001007e6c2e lto1`::gen_struct_or_union_type_die(tree,
dw_die_ref, debug_info_usage) at dwarf2out.c:24578
frame #12: 0x00000001007e6b29
lto1`::gen_struct_or_union_type_die(type=0x00000001448260a8,
context_die=0x000000014482b000, usage=<unavailable>)
frame #13: 0x00000001007e205e
lto1`::gen_tagged_type_die(type=0x00000001448260a8, context_die=<unavailable>,
usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25430
frame #14: 0x00000001007e248f
lto1`::gen_typedef_die(decl=0x00000001448217b8, context_die=0x000000014482b000)
at dwarf2out.c:25344
frame #15: 0x00000001007e2a15 lto1`::gen_decl_die(decl=0x00000001448217b8,
origin=<unavailable>, ctx=<unavailable>, context_die=0x000000014482b000) at
dwarf2out.c:26314
frame #16: 0x00000001007c5ef3
lto1`::gen_type_die_with_usage(type=0x00000001448260a8,
context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25495
frame #17: 0x00000001007c785a lto1`::gen_type_die(type=0x00000001448260a8,
context_die=<unavailable>) at dwarf2out.c:25679
frame #18: 0x00000001007c80b0
lto1`::modified_type_die(type=0x00000001448260a8, cv_quals=0,
reverse=<unavailable>, context_die=0x000000014482b690) at dwarf2out.c:13373
frame #19: 0x00000001007ca931
lto1`::add_type_attribute(object_die=0x000000014482b7d0, type=<unavailable>,
cv_quals=<unavailable>, reverse=<unavailable>, context_die=<unavailable>) at
dwarf2out.c:21601
frame #20: 0x00000001007bdf53
lto1`::gen_variable_die(decl=0x0000000142ce0e10, origin=<unavailable>,
context_die=0x000000014482b690) at dwarf2out.c:23843
frame #21: 0x00000001007e2c3b lto1`::gen_decl_die(decl=0x0000000142ce0e10,
origin=0x0000000000000000, ctx=0x0000000000000000,
context_die=0x000000014482b690) at dwarf2out.c:26371
frame #22: 0x00000001007c01dd
lto1`::process_scope_var(stmt=0x00000001448252a0, decl=0x0000000142ce0e10,
origin=<unavailable>, context_die=0x000000014482b690) at dwarf2out.c:25832
frame #23: 0x00000001007c06c9
lto1`::decls_for_scope(stmt=0x00000001448252a0, context_die=0x000000014482b690,
recurse=<unavailable>) at dwarf2out.c:25858
frame #24: 0x00000001007c19c7 lto1`::gen_subprogram_die(decl=<unavailable>,
context_die=<unavailable>) at dwarf2out.c:23328
frame #25: 0x00000001007e2705 lto1`::gen_decl_die(decl=0x0000000144824100,
origin=0x0000000000000000, ctx=0x0000000000000000,
context_die=0x000000014482b000) at dwarf2out.c:26288
frame #26: 0x00000001007e428b
lto1`::dwarf2out_decl(decl=0x0000000144824100) at dwarf2out.c:26856
frame #27: 0x00000001007e4d5f
lto1`::dwarf2out_function_decl(decl=<unavailable>) at dwarf2out.c:26871
frame #28: 0x0000000100851128 lto1`pass_final::execute(this=<unavailable>,
(null)=<unavailable>) const at final.c:4695
frame #29: 0x0000000100b814af
lto1`execute_one_pass(pass=0x0000000143811c20) at passes.c:2483
frame #30: 0x0000000100b81b63
lto1`::execute_pass_list_1(pass=0x0000000143811c20) at passes.c:2569
frame #31: 0x0000000100b81b75
lto1`::execute_pass_list_1(pass=0x0000000143811740) at passes.c:2570
frame #32: 0x0000000100b81b75
lto1`::execute_pass_list_1(pass=0x000000014380fac0) at passes.c:2570
frame #33: 0x0000000100b81ba2 lto1`execute_pass_list(fn=0x000000014482d000,
pass=<unavailable>) at passes.c:2580
frame #34: 0x00000001006eb445
lto1`cgraph_node::expand(this=0x0000000143d24438) at cgraphunit.c:2196
frame #35: 0x00000001006ec322 lto1`symbol_table::compile() at
cgraphunit.c:2334
frame #36: 0x00000001006ec221
lto1`symbol_table::compile(this=0x0000000143d25100)
frame #37: 0x0000000100030ff0 lto1`lto_main() at lto.c:3390
frame #38: 0x0000000100c982ca lto1`::compile_file() at toplev.c:456
frame #39: 0x0000000101710faf lto1`toplev::main(int, char**) at
toplev.c:2176
frame #40: 0x0000000101710e7b lto1`toplev::main(this=0x00007fff5fbff68e,
argc=<unavailable>, argv=<unavailable>)
frame #41: 0x0000000101713821 lto1`main(argc=31, argv=0x00007fff5fbff6c8)
at main.c:39
frame #42: 0x00007fff9e132235 libdyld.dylib`start + 1
frame #43: 0x00007fff9e132235 libdyld.dylib`start + 1
(lldb)
========= pr78651 is:
$ /XC/9.4/usr/bin/lldb --
/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1 -fPIC
-feliminate-unused-debug-symbols -quiet -dumpdir ./ -dumpbase pr78651.exe
-mmacosx-version-min=10.12.0 -mtune=core2 -m32 -mmacosx-version-min=10.12.0
-mtune=core2 -auxbase-strip pr78651.exe.lto.o -g -O2 -O2 -version
-fdiagnostics-color=never -fno-openmp -fno-openacc -fsanitize=address
-fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
-fmessage-length=0 -flto-partition=none -fpic
@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up -o pr78651.s
(lldb) target create
"/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1"
Current executable set to
'/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
(x86_64).
(lldb) settings set -- target.run-args "-fPIC"
"-feliminate-unused-debug-symbols" "-quiet" "-dumpdir" "./" "-dumpbase"
"pr78651.exe" "-mmacosx-version-min=10.12.0" "-mtune=core2" "-m32"
"-mmacosx-version-min=10.12.0" "-mtune=core2" "-auxbase-strip"
"pr78651.exe.lto.o" "-g" "-O2" "-O2" "-version" "-fdiagnostics-color=never"
"-fno-openmp" "-fno-openacc" "-fsanitize=address" "-fno-diagnostics-show-caret"
"-fno-diagnostics-show-line-numbers" "-fmessage-length=0"
"-flto-partition=none" "-fpic"
"@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up" "-o" "pr78651.s"
(lldb) b internal_error
r
Breakpoint 1: where = lto1`internal_error(char const*, ...) + 121 [inlined]
_ZN21auto_diagnostic_groupC4Ev, address = 0x00000001010abcb9
(lldb) r
Process 22101 launched:
'/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1' (x86_64)
GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision 267925]
(x86_64-apple-darwin16)
compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl version
isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision 267925]
(x86_64-apple-darwin16)
compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl version
isl-0.20-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Process 22101 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
[inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
diagnostic.c:1616
1613
1614 auto_diagnostic_group::auto_diagnostic_group ()
1615 {
-> 1616 global_dc->diagnostic_group_nesting_depth++;
1617 }
1618
1619 /* Destructor: "pop" this group from global_dc. */
Target 0: (lto1) stopped.
(lldb) bt
* thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
* frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
[inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
diagnostic.c:1616
frame #1: 0x00000001010abcb9 lto1`internal_error(gmsgid="in %s, at %s:%d")
frame #2: 0x000000010170bf9c lto1`fancy_abort(file=<unavailable>,
line=<unavailable>, function=<unavailable>) at diagnostic.c:1607
frame #3: 0x00000001015991fc lto1`lhd_decl_printable_name(tree_node*, int)
at langhooks.c:222
frame #4: 0x00000001007b4288 lto1`::add_pubtype(decl=0x0000000143e25f18,
die=0x0000000143e27f50) at dwarf2out.c:11333
frame #5: 0x00000001007e70f1
lto1`::gen_struct_or_union_type_die(type=0x0000000143e25f18,
context_die=<unavailable>, usage=<unavailable>) at dwarf2out.c:25256
frame #6: 0x00000001007e205e
lto1`::gen_tagged_type_die(type=0x0000000143e25f18, context_die=<unavailable>,
usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25430
frame #7: 0x00000001007e248f
lto1`::gen_typedef_die(decl=0x0000000143e214c0, context_die=0x0000000143e27190)
at dwarf2out.c:25344
frame #8: 0x00000001007e2a15 lto1`::gen_decl_die(decl=0x0000000143e214c0,
origin=<unavailable>, ctx=<unavailable>, context_die=0x0000000143e27190) at
dwarf2out.c:26314
frame #9: 0x00000001007c5ef3
lto1`::gen_type_die_with_usage(type=0x0000000143e25f18,
context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25495
frame #10: 0x00000001007c785a lto1`::gen_type_die(type=0x0000000143e25f18,
context_die=<unavailable>) at dwarf2out.c:25679
frame #11: 0x00000001007c80b0
lto1`::modified_type_die(type=0x0000000143e25f18, cv_quals=0,
reverse=<unavailable>, context_die=0x0000000143e27e60) at dwarf2out.c:13373
frame #12: 0x00000001007ca931
lto1`::add_type_attribute(object_die=0x0000000143e27eb0, type=<unavailable>,
cv_quals=<unavailable>, reverse=<unavailable>, context_die=<unavailable>) at
dwarf2out.c:21601
frame #13: 0x00000001007bdf53
lto1`::gen_variable_die(decl=0x0000000142ce0e10, origin=<unavailable>,
context_die=0x0000000143e27e60) at dwarf2out.c:23843
frame #14: 0x00000001007e2c3b lto1`::gen_decl_die(decl=0x0000000142ce0e10,
origin=0x0000000000000000, ctx=0x0000000000000000,
context_die=0x0000000143e27e60) at dwarf2out.c:26371
frame #15: 0x00000001007c01dd
lto1`::process_scope_var(stmt=0x0000000143e2c540, decl=0x0000000142ce0e10,
origin=<unavailable>, context_die=0x0000000143e27e60) at dwarf2out.c:25832
frame #16: 0x00000001007c06c9
lto1`::decls_for_scope(stmt=0x0000000143e2c540, context_die=0x0000000143e27e60,
recurse=<unavailable>) at dwarf2out.c:25858
frame #17: 0x00000001007e9dd4 lto1`::gen_block_die(tree, dw_die_ref) at
dwarf2out.c:24180
frame #18: 0x00000001007e9d0c lto1`::gen_block_die(stmt=0x0000000143e2c540,
context_die=<unavailable>)
frame #19: 0x00000001007c076f
lto1`::decls_for_scope(stmt=0x0000000143e2c4e0, context_die=0x0000000143e27af0,
recurse=<unavailable>) at dwarf2out.c:25887
frame #20: 0x00000001007c19c7 lto1`::gen_subprogram_die(decl=<unavailable>,
context_die=<unavailable>) at dwarf2out.c:23328
frame #21: 0x00000001007e2705 lto1`::gen_decl_die(decl=0x0000000143e24300,
origin=0x0000000000000000, ctx=0x0000000000000000,
context_die=0x0000000143e27190) at dwarf2out.c:26288
frame #22: 0x00000001007e428b
lto1`::dwarf2out_decl(decl=0x0000000143e24300) at dwarf2out.c:26856
frame #23: 0x00000001007e4d5f
lto1`::dwarf2out_function_decl(decl=<unavailable>) at dwarf2out.c:26871
frame #24: 0x0000000100851128 lto1`pass_final::execute(this=<unavailable>,
(null)=<unavailable>) const at final.c:4695
frame #25: 0x0000000100b814af
lto1`execute_one_pass(pass=0x0000000142d13f50) at passes.c:2483
frame #26: 0x0000000100b81b63
lto1`::execute_pass_list_1(pass=0x0000000142d13f50) at passes.c:2569
frame #27: 0x0000000100b81b75
lto1`::execute_pass_list_1(pass=0x0000000142d13a70) at passes.c:2570
frame #28: 0x0000000100b81b75
lto1`::execute_pass_list_1(pass=0x0000000142d11df0) at passes.c:2570
frame #29: 0x0000000100b81ba2 lto1`execute_pass_list(fn=0x0000000143e2d000,
pass=<unavailable>) at passes.c:2580
frame #30: 0x00000001006eb445
lto1`cgraph_node::expand(this=0x0000000143c045a0) at cgraphunit.c:2196
frame #31: 0x00000001006ec322 lto1`symbol_table::compile() at
cgraphunit.c:2334
frame #32: 0x00000001006ec221
lto1`symbol_table::compile(this=0x0000000143c05100)
frame #33: 0x0000000100030ff0 lto1`lto_main() at lto.c:3390
frame #34: 0x0000000100c982ca lto1`::compile_file() at toplev.c:456
frame #35: 0x0000000101710faf lto1`toplev::main(int, char**) at
toplev.c:2176
frame #36: 0x0000000101710e7b lto1`toplev::main(this=0x00007fff5fbff68e,
argc=<unavailable>, argv=<unavailable>)
frame #37: 0x0000000101713821 lto1`main(argc=31, argv=0x00007fff5fbff6c8)
at main.c:39
frame #38: 0x00007fff9e132235 libdyld.dylib`start + 1
frame #39: 0x00007fff9e132235 libdyld.dylib`start + 1
>From gcc-bugs-return-629264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:28:40 2019
Return-Path: <gcc-bugs-return-629264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94722 invoked by alias); 15 Jan 2019 15:28: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 94641 invoked by uid 48); 15 Jan 2019 15:28:35 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/88860] New: Clarify gcc online manual 6.38 Attribute Syntax
Date: Tue, 15 Jan 2019 15:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02073.txt.bz2
Content-length: 1397
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88860
Bug ID: 88860
Summary: Clarify gcc online manual 6.38 Attribute Syntax
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: jg at jguk dot org
Target Milestone: ---
Hello
I propose two changes to clarify gcc online manual 6.38 Attribute Syntax
https://gcc.gnu.org/onlinedocs/gcc/Attribute-Syntax.html#Attribute-Syntax
1) Change "infelicities" to "limitations" - I'm an English native speaking, I
don't know that word "infelicities" and I've certainly never used or read it.
Could that change be made?
2) Provide a __attribute__ ((format (printf,1,2))); example. Explaining which
arguments it relates to. Eg add something like the following :-
=================
The following __attribute__ causes gcc to check run printf argument checks on
argument '3' which is 'const char * string format' (when visible at compile
time), against argument '4' the '...' variadic ellipsis. In the example below,
arguments '1' and '2' are not checked.
void string_format(const char * prefix, size_t line, const char * const format,
...) __attribute__ ((format (printf,3,4)));
==========
>From gcc-bugs-return-629265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:31:43 2019
Return-Path: <gcc-bugs-return-629265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102944 invoked by alias); 15 Jan 2019 15:31: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 101881 invoked by uid 48); 15 Jan 2019 15:31:38 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Tue, 15 Jan 2019 15:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
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_status resolution
Message-ID: <bug-85949-4-4NBLkvpWln@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02074.txt.bz2
Content-length: 722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
Jonny Grant <jg at jguk dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|FIXED |---
--- Comment #3 from Jonny Grant <jg at jguk dot org> ---
Clang gets the attribute parameter right :-
<source>:7:62: error: 'format' attribute parameter 2 is out of bounds
void str_fmt(const char * const format, ...) __attribute__ ((format
(printf,2,3)));
^ ~
1 error generated.
Compiler returned: 1
>From gcc-bugs-return-629266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:33:41 2019
Return-Path: <gcc-bugs-return-629266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107823 invoked by alias); 15 Jan 2019 15:33: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 105405 invoked by uid 48); 15 Jan 2019 15:33:37 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 15:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-tQo0EWTs8O@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02075.txt.bz2
Content-length: 298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> ---
62017 would seem to suggest that we've generated bad code for the stage#3
tree_fits_shwi_p function (which would be a separate issue) but maybe the tree
shouldn't be null anyway.
>From gcc-bugs-return-629267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:34:29 2019
Return-Path: <gcc-bugs-return-629267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123662 invoked by alias); 15 Jan 2019 15:34: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 123592 invoked by uid 48); 15 Jan 2019 15:34:24 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Tue, 15 Jan 2019 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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-85949-4-9PUYuFjhov@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02076.txt.bz2
Content-length: 531
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
Ever confirmed|0 |1
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Martin: would it be possible to enhance the location?
>From gcc-bugs-return-629268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:34:54 2019
Return-Path: <gcc-bugs-return-629268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124642 invoked by alias); 15 Jan 2019 15:34:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124418 invoked by uid 48); 15 Jan 2019 15:34:43 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 15:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-6brQLk53Ww@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02077.txt.bz2
Content-length: 18975
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #5)
> (In reply to Richard Biener from comment #4)
> > Hmm, I can no longer reproduce -g0 vs -g on x86_64-linux. Ians testresults
> > now
> > list
> >
> > FAIL: g++.dg/asan/pr62017.C -O2 -flto (internal compiler error)
> > FAIL: g++.dg/asan/pr62017.C -O2 -flto (test for excess errors)
> > FAIL: g++.dg/asan/pr62017.C -O2 -flto -flto-partition=none (internal
> > compiler error)
> > FAIL: g++.dg/asan/pr62017.C -O2 -flto -flto-partition=none (test for
> > excess errors)
> > FAIL: g++.dg/asan/pr78651.C -O2 -flto (internal compiler error)
> > FAIL: g++.dg/asan/pr78651.C -O2 -flto (test for excess errors)
> > FAIL: g++.dg/asan/pr78651.C -O2 -flto -flto-partition=none (internal
> > compiler error)
> > FAIL: g++.dg/asan/pr78651.C -O2 -flto -flto-partition=none (test for
> > excess errors)
> >
> > but I can't reproduce with pr62017.C or pr78651.C either right now.
>
> 81021 has indeed started to pass (I didn't notice when).
>
> ===== 62017 is:
>
> $ /XC/9.4/usr/bin/lldb --
> /scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1 -fPIC
> -feliminate-unused-debug-symbols -quiet -dumpdir ./ -dumpbase pr62017.exe
> -mmacosx-version-min=10.12.0 -mtune=core2 -m32 -mmacosx-version-min=10.12.0
> -mtune=core2 -auxbase-strip pr62017.exe.lto.o -g -O2 -O2 -version
> -fdiagnostics-color=never -fno-openmp -fno-openacc -fPIC -fsanitize=address
> -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> -fmessage-length=0 -flto-partition=none
> @/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccyWmZmy -o pr62017.s
> (lldb) target create
> "/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1"
> Current executable set to
> '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1'
> (x86_64).
> (lldb) settings set -- target.run-args "-fPIC"
> "-feliminate-unused-debug-symbols" "-quiet" "-dumpdir" "./" "-dumpbase"
> "pr62017.exe" "-mmacosx-version-min=10.12.0" "-mtune=core2" "-m32"
> "-mmacosx-version-min=10.12.0" "-mtune=core2" "-auxbase-strip"
> "pr62017.exe.lto.o" "-g" "-O2" "-O2" "-version" "-fdiagnostics-color=never"
> "-fno-openmp" "-fno-openacc" "-fPIC" "-fsanitize=address"
> "-fno-diagnostics-show-caret" "-fno-diagnostics-show-line-numbers"
> "-fmessage-length=0" "-flto-partition=none"
> "@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccyWmZmy" "-o"
> "pr62017.s"
> (lldb) b internal_error
> Breakpoint 1: where = lto1`internal_error(char const*, ...) + 121 [inlined]
> _ZN21auto_diagnostic_groupC4Ev, address = 0x00000001010abcb9
> (lldb) r
> Process 22051 launched:
> '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++/../../lto1'
> (x86_64)
> GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> 267925] (x86_64-apple-darwin16)
> compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> version isl-0.20-GMP
>
> GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> 267925] (x86_64-apple-darwin16)
> compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> version isl-0.20-GMP
>
> GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> Process 22051 stopped
> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
> (code=1, address=0x0)
> frame #0: 0x0000000100f7a941 lto1`tree_to_shwi(t=0x0000000000000000) at
> tree.c:7169
> 7166 tree_fits_shwi_p (const_tree t)
> 7167 {
> 7168 return (t != NULL_TREE
> -> 7169 && TREE_CODE (t) == INTEGER_CST
> 7170 && wi::fits_shwi_p (wi::to_widest (t)));
> 7171 }
> 7172
> Target 0: (lto1) stopped.
> (lldb) bt
> * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
> (code=1, address=0x0)
> * frame #0: 0x0000000100f7a941 lto1`tree_to_shwi(t=0x0000000000000000) at
> tree.c:7169
> frame #1: 0x00000001007ddb3b
> lto1`::add_data_member_location_attribute(die=0x000000014482b9b0,
> decl=0x00000001448250c0, ctx=<unavailable>) at dwarf2out.c:19306
> frame #2: 0x00000001007e6c3e lto1`::gen_struct_or_union_type_die(tree,
> dw_die_ref, debug_info_usage) at dwarf2out.c:24580
> frame #3: 0x00000001007e6b29
> lto1`::gen_struct_or_union_type_die(type=0x0000000144826000,
> context_die=0x000000014482b000, usage=<unavailable>)
> frame #4: 0x00000001007e205e
> lto1`::gen_tagged_type_die(type=0x0000000144826000,
> context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25430
> frame #5: 0x00000001007e248f
> lto1`::gen_typedef_die(decl=0x0000000144821558,
> context_die=0x000000014482b000) at dwarf2out.c:25344
> frame #6: 0x00000001007e2a15
> lto1`::gen_decl_die(decl=0x0000000144821558, origin=<unavailable>,
> ctx=<unavailable>, context_die=0x000000014482b000) at dwarf2out.c:26314
> frame #7: 0x00000001007c5ef3
> lto1`::gen_type_die_with_usage(type=0x0000000144826000,
> context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25495
> frame #8: 0x00000001007c785a
> lto1`::gen_type_die(type=0x0000000144826000, context_die=<unavailable>) at
> dwarf2out.c:25679
> frame #9: 0x00000001007c80b0
> lto1`::modified_type_die(type=0x0000000144826000, cv_quals=0,
> reverse=<unavailable>, context_die=0x000000014482b870) at dwarf2out.c:13373
> frame #10: 0x00000001007ca931
> lto1`::add_type_attribute(object_die=0x000000014482b8c0, type=<unavailable>,
> cv_quals=<unavailable>, reverse=<unavailable>, context_die=<unavailable>) at
> dwarf2out.c:21601
> frame #11: 0x00000001007e6c2e lto1`::gen_struct_or_union_type_die(tree,
> dw_die_ref, debug_info_usage) at dwarf2out.c:24578
> frame #12: 0x00000001007e6b29
> lto1`::gen_struct_or_union_type_die(type=0x00000001448260a8,
> context_die=0x000000014482b000, usage=<unavailable>)
> frame #13: 0x00000001007e205e
> lto1`::gen_tagged_type_die(type=0x00000001448260a8,
> context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25430
> frame #14: 0x00000001007e248f
> lto1`::gen_typedef_die(decl=0x00000001448217b8,
> context_die=0x000000014482b000) at dwarf2out.c:25344
> frame #15: 0x00000001007e2a15
> lto1`::gen_decl_die(decl=0x00000001448217b8, origin=<unavailable>,
> ctx=<unavailable>, context_die=0x000000014482b000) at dwarf2out.c:26314
> frame #16: 0x00000001007c5ef3
> lto1`::gen_type_die_with_usage(type=0x00000001448260a8,
> context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25495
> frame #17: 0x00000001007c785a
> lto1`::gen_type_die(type=0x00000001448260a8, context_die=<unavailable>) at
> dwarf2out.c:25679
> frame #18: 0x00000001007c80b0
> lto1`::modified_type_die(type=0x00000001448260a8, cv_quals=0,
> reverse=<unavailable>, context_die=0x000000014482b690) at dwarf2out.c:13373
> frame #19: 0x00000001007ca931
> lto1`::add_type_attribute(object_die=0x000000014482b7d0, type=<unavailable>,
> cv_quals=<unavailable>, reverse=<unavailable>, context_die=<unavailable>) at
> dwarf2out.c:21601
> frame #20: 0x00000001007bdf53
> lto1`::gen_variable_die(decl=0x0000000142ce0e10, origin=<unavailable>,
> context_die=0x000000014482b690) at dwarf2out.c:23843
> frame #21: 0x00000001007e2c3b
> lto1`::gen_decl_die(decl=0x0000000142ce0e10, origin=0x0000000000000000,
> ctx=0x0000000000000000, context_die=0x000000014482b690) at dwarf2out.c:26371
> frame #22: 0x00000001007c01dd
> lto1`::process_scope_var(stmt=0x00000001448252a0, decl=0x0000000142ce0e10,
> origin=<unavailable>, context_die=0x000000014482b690) at dwarf2out.c:25832
> frame #23: 0x00000001007c06c9
> lto1`::decls_for_scope(stmt=0x00000001448252a0,
> context_die=0x000000014482b690, recurse=<unavailable>) at dwarf2out.c:25858
> frame #24: 0x00000001007c19c7
> lto1`::gen_subprogram_die(decl=<unavailable>, context_die=<unavailable>) at
> dwarf2out.c:23328
> frame #25: 0x00000001007e2705
> lto1`::gen_decl_die(decl=0x0000000144824100, origin=0x0000000000000000,
> ctx=0x0000000000000000, context_die=0x000000014482b000) at dwarf2out.c:26288
> frame #26: 0x00000001007e428b
> lto1`::dwarf2out_decl(decl=0x0000000144824100) at dwarf2out.c:26856
> frame #27: 0x00000001007e4d5f
> lto1`::dwarf2out_function_decl(decl=<unavailable>) at dwarf2out.c:26871
> frame #28: 0x0000000100851128
> lto1`pass_final::execute(this=<unavailable>, (null)=<unavailable>) const at
> final.c:4695
> frame #29: 0x0000000100b814af
> lto1`execute_one_pass(pass=0x0000000143811c20) at passes.c:2483
> frame #30: 0x0000000100b81b63
> lto1`::execute_pass_list_1(pass=0x0000000143811c20) at passes.c:2569
> frame #31: 0x0000000100b81b75
> lto1`::execute_pass_list_1(pass=0x0000000143811740) at passes.c:2570
> frame #32: 0x0000000100b81b75
> lto1`::execute_pass_list_1(pass=0x000000014380fac0) at passes.c:2570
> frame #33: 0x0000000100b81ba2
> lto1`execute_pass_list(fn=0x000000014482d000, pass=<unavailable>) at
> passes.c:2580
> frame #34: 0x00000001006eb445
> lto1`cgraph_node::expand(this=0x0000000143d24438) at cgraphunit.c:2196
> frame #35: 0x00000001006ec322 lto1`symbol_table::compile() at
> cgraphunit.c:2334
> frame #36: 0x00000001006ec221
> lto1`symbol_table::compile(this=0x0000000143d25100)
> frame #37: 0x0000000100030ff0 lto1`lto_main() at lto.c:3390
> frame #38: 0x0000000100c982ca lto1`::compile_file() at toplev.c:456
> frame #39: 0x0000000101710faf lto1`toplev::main(int, char**) at
> toplev.c:2176
> frame #40: 0x0000000101710e7b lto1`toplev::main(this=0x00007fff5fbff68e,
> argc=<unavailable>, argv=<unavailable>)
> frame #41: 0x0000000101713821 lto1`main(argc=31,
> argv=0x00007fff5fbff6c8) at main.c:39
> frame #42: 0x00007fff9e132235 libdyld.dylib`start + 1
> frame #43: 0x00007fff9e132235 libdyld.dylib`start + 1
> (lldb)
OK, that's PR88046 for which I have a patch in my tree.
>
> ========= pr78651 is:
>
> $ /XC/9.4/usr/bin/lldb --
> /scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1 -fPIC
> -feliminate-unused-debug-symbols -quiet -dumpdir ./ -dumpbase pr78651.exe
> -mmacosx-version-min=10.12.0 -mtune=core2 -m32 -mmacosx-version-min=10.12.0
> -mtune=core2 -auxbase-strip pr78651.exe.lto.o -g -O2 -O2 -version
> -fdiagnostics-color=never -fno-openmp -fno-openacc -fsanitize=address
> -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> -fmessage-length=0 -flto-partition=none -fpic
> @/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up -o pr78651.s
> (lldb) target create
> "/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1"
> Current executable set to
> '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
> (x86_64).
> (lldb) settings set -- target.run-args "-fPIC"
> "-feliminate-unused-debug-symbols" "-quiet" "-dumpdir" "./" "-dumpbase"
> "pr78651.exe" "-mmacosx-version-min=10.12.0" "-mtune=core2" "-m32"
> "-mmacosx-version-min=10.12.0" "-mtune=core2" "-auxbase-strip"
> "pr78651.exe.lto.o" "-g" "-O2" "-O2" "-version" "-fdiagnostics-color=never"
> "-fno-openmp" "-fno-openacc" "-fsanitize=address"
> "-fno-diagnostics-show-caret" "-fno-diagnostics-show-line-numbers"
> "-fmessage-length=0" "-flto-partition=none" "-fpic"
> "@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up" "-o"
> "pr78651.s"
> (lldb) b internal_error
> r
> Breakpoint 1: where = lto1`internal_error(char const*, ...) + 121 [inlined]
> _ZN21auto_diagnostic_groupC4Ev, address = 0x00000001010abcb9
> (lldb) r
> Process 22101 launched:
> '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
> (x86_64)
> GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> 267925] (x86_64-apple-darwin16)
> compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> version isl-0.20-GMP
>
> GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> 267925] (x86_64-apple-darwin16)
> compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> version isl-0.20-GMP
>
> GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> Process 22101 stopped
> * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
> frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
> [inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
> diagnostic.c:1616
> 1613
> 1614 auto_diagnostic_group::auto_diagnostic_group ()
> 1615 {
> -> 1616 global_dc->diagnostic_group_nesting_depth++;
> 1617 }
> 1618
> 1619 /* Destructor: "pop" this group from global_dc. */
> Target 0: (lto1) stopped.
> (lldb) bt
> * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
> * frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
> [inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
> diagnostic.c:1616
> frame #1: 0x00000001010abcb9 lto1`internal_error(gmsgid="in %s, at
> %s:%d")
> frame #2: 0x000000010170bf9c lto1`fancy_abort(file=<unavailable>,
> line=<unavailable>, function=<unavailable>) at diagnostic.c:1607
> frame #3: 0x00000001015991fc lto1`lhd_decl_printable_name(tree_node*,
> int) at langhooks.c:222
> frame #4: 0x00000001007b4288 lto1`::add_pubtype(decl=0x0000000143e25f18,
> die=0x0000000143e27f50) at dwarf2out.c:11333
> frame #5: 0x00000001007e70f1
> lto1`::gen_struct_or_union_type_die(type=0x0000000143e25f18,
> context_die=<unavailable>, usage=<unavailable>) at dwarf2out.c:25256
> frame #6: 0x00000001007e205e
> lto1`::gen_tagged_type_die(type=0x0000000143e25f18,
> context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25430
> frame #7: 0x00000001007e248f
> lto1`::gen_typedef_die(decl=0x0000000143e214c0,
> context_die=0x0000000143e27190) at dwarf2out.c:25344
> frame #8: 0x00000001007e2a15
> lto1`::gen_decl_die(decl=0x0000000143e214c0, origin=<unavailable>,
> ctx=<unavailable>, context_die=0x0000000143e27190) at dwarf2out.c:26314
> frame #9: 0x00000001007c5ef3
> lto1`::gen_type_die_with_usage(type=0x0000000143e25f18,
> context_die=<unavailable>, usage=DINFO_USAGE_DIR_USE) at dwarf2out.c:25495
> frame #10: 0x00000001007c785a
> lto1`::gen_type_die(type=0x0000000143e25f18, context_die=<unavailable>) at
> dwarf2out.c:25679
> frame #11: 0x00000001007c80b0
> lto1`::modified_type_die(type=0x0000000143e25f18, cv_quals=0,
> reverse=<unavailable>, context_die=0x0000000143e27e60) at dwarf2out.c:13373
> frame #12: 0x00000001007ca931
> lto1`::add_type_attribute(object_die=0x0000000143e27eb0, type=<unavailable>,
> cv_quals=<unavailable>, reverse=<unavailable>, context_die=<unavailable>) at
> dwarf2out.c:21601
> frame #13: 0x00000001007bdf53
> lto1`::gen_variable_die(decl=0x0000000142ce0e10, origin=<unavailable>,
> context_die=0x0000000143e27e60) at dwarf2out.c:23843
> frame #14: 0x00000001007e2c3b
> lto1`::gen_decl_die(decl=0x0000000142ce0e10, origin=0x0000000000000000,
> ctx=0x0000000000000000, context_die=0x0000000143e27e60) at dwarf2out.c:26371
> frame #15: 0x00000001007c01dd
> lto1`::process_scope_var(stmt=0x0000000143e2c540, decl=0x0000000142ce0e10,
> origin=<unavailable>, context_die=0x0000000143e27e60) at dwarf2out.c:25832
> frame #16: 0x00000001007c06c9
> lto1`::decls_for_scope(stmt=0x0000000143e2c540,
> context_die=0x0000000143e27e60, recurse=<unavailable>) at dwarf2out.c:25858
> frame #17: 0x00000001007e9dd4 lto1`::gen_block_die(tree, dw_die_ref) at
> dwarf2out.c:24180
> frame #18: 0x00000001007e9d0c
> lto1`::gen_block_die(stmt=0x0000000143e2c540, context_die=<unavailable>)
> frame #19: 0x00000001007c076f
> lto1`::decls_for_scope(stmt=0x0000000143e2c4e0,
> context_die=0x0000000143e27af0, recurse=<unavailable>) at dwarf2out.c:25887
> frame #20: 0x00000001007c19c7
> lto1`::gen_subprogram_die(decl=<unavailable>, context_die=<unavailable>) at
> dwarf2out.c:23328
> frame #21: 0x00000001007e2705
> lto1`::gen_decl_die(decl=0x0000000143e24300, origin=0x0000000000000000,
> ctx=0x0000000000000000, context_die=0x0000000143e27190) at dwarf2out.c:26288
> frame #22: 0x00000001007e428b
> lto1`::dwarf2out_decl(decl=0x0000000143e24300) at dwarf2out.c:26856
> frame #23: 0x00000001007e4d5f
> lto1`::dwarf2out_function_decl(decl=<unavailable>) at dwarf2out.c:26871
> frame #24: 0x0000000100851128
> lto1`pass_final::execute(this=<unavailable>, (null)=<unavailable>) const at
> final.c:4695
> frame #25: 0x0000000100b814af
> lto1`execute_one_pass(pass=0x0000000142d13f50) at passes.c:2483
> frame #26: 0x0000000100b81b63
> lto1`::execute_pass_list_1(pass=0x0000000142d13f50) at passes.c:2569
> frame #27: 0x0000000100b81b75
> lto1`::execute_pass_list_1(pass=0x0000000142d13a70) at passes.c:2570
> frame #28: 0x0000000100b81b75
> lto1`::execute_pass_list_1(pass=0x0000000142d11df0) at passes.c:2570
> frame #29: 0x0000000100b81ba2
> lto1`execute_pass_list(fn=0x0000000143e2d000, pass=<unavailable>) at
> passes.c:2580
> frame #30: 0x00000001006eb445
> lto1`cgraph_node::expand(this=0x0000000143c045a0) at cgraphunit.c:2196
> frame #31: 0x00000001006ec322 lto1`symbol_table::compile() at
> cgraphunit.c:2334
> frame #32: 0x00000001006ec221
> lto1`symbol_table::compile(this=0x0000000143c05100)
> frame #33: 0x0000000100030ff0 lto1`lto_main() at lto.c:3390
> frame #34: 0x0000000100c982ca lto1`::compile_file() at toplev.c:456
> frame #35: 0x0000000101710faf lto1`toplev::main(int, char**) at
> toplev.c:2176
> frame #36: 0x0000000101710e7b lto1`toplev::main(this=0x00007fff5fbff68e,
> argc=<unavailable>, argv=<unavailable>)
> frame #37: 0x0000000101713821 lto1`main(argc=31,
> argv=0x00007fff5fbff6c8) at main.c:39
> frame #38: 0x00007fff9e132235 libdyld.dylib`start + 1
> frame #39: 0x00007fff9e132235 libdyld.dylib`start + 1
That I can't reproduce even when backing out all dwarf2out.c changes.
>From gcc-bugs-return-629269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:36:21 2019
Return-Path: <gcc-bugs-return-629269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127650 invoked by alias); 15 Jan 2019 15:36:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 127537 invoked by uid 55); 15 Jan 2019 15:36:16 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Tue, 15 Jan 2019 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88810-4-Xkr7j1sTgc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02078.txt.bz2
Content-length: 2874
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jan 15, 2019 at 12:39:13PM +0000, tkoenig at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
>
> Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |tkoenig at gcc dot gnu.org
>
> --- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> As far as I can see, the duplicated code does not do anything bad,
> and removing the duplicate also would not do anything bad.
>
> A patch removing the duplication is pre-approved, provided it
> passes a regression test.
>
Are you sure it is duplicate code?
Here, if reverse[m] == GFC_ENABLE_REVERSE and this_dep == GFC_DEP_BACKWARD,
then reverse[m] is update to GFC_REVERSE_SET; otherwise it is left as-is
which is GFC_ENABLE_REVERSE.
/* Set reverse if backward dependence and not inhibited. */
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
reverse[m] = (this_dep == GFC_DEP_BACKWARD) ?
GFC_REVERSE_SET : reverse[m];
Here, if reverse[m] was updated to GFC_REVERSE_SET, the first
conditional fails and reverse[m] is left unchanged. However, if
reverse[m] was left unchanged from above, it is then GFC_ENABLE_REVERSE.
gfortran then checks this_dep == GFC_DEP_FORWARD and updates accordingly.
/* Set forward if forward dependence and not inhibited. */
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
reverse[m] = (this_dep == GFC_DEP_FORWARD) ?
GFC_FORWARD_SET : reverse[m];
The code is likely correct as-is, but confusing. Some would have
written
/* Set reverse if backward dependence and not inhibited. */
if (reverse && reverse[m] == GFC_ENABLE_REVERSE
&& this_dep == GFC_DEP_BACKWARD)
reverse[m] = GFC_REVERSE_SET;
/* Set forward if forward dependence and not inhibited. */
if (reverse && reverse[m] == GFC_ENABLE_REVERSE
&& this_dep == GFC_DEP_FORWARD)
reverse[m] = GFC_FORWARD_SET;
or
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
{
if (this_dep == GFC_DEP_BACKWARD)
reverse[m] = GFC_REVERSE_SET;
else if (this_dep == GFC_DEP_FORWARD)
reverse[m] = GFC_FORWARD_SET;
}
If this_dep can only take on the values of GFC_REVERSE_SET and
GFC_DEP_FORWARD, then the above can be collapsed to
if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
reverse[m] = this_dep == GFC_DEP_BACKWARD
? GFC_REVERSE_SET : GFC_FORWARD_SET;
Looks like this PR is a false positive.
>From gcc-bugs-return-629271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:38:05 2019
Return-Path: <gcc-bugs-return-629271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 576 invoked by alias); 15 Jan 2019 15:38: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 130930 invoked by uid 55); 15 Jan 2019 15:38:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88855] [9 Regression] ICE: verify_ssa failed (error: SSA_NAME_OCCURS_IN_ABNORMAL_PHI should be set)
Date: Tue, 15 Jan 2019 15:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88855-4-ZlB8SA3H9R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02080.txt.bz2
Content-length: 658
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88855
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 15 15:37:29 2019
New Revision: 267939
URL: https://gcc.gnu.org/viewcvs?rev=267939&root=gcc&view=rev
Log:
2019-01-15 Richard Biener <rguenther@suse.de>
PR tree-optimization/88855
* tree-if-conv.c (combine_blocks): Collect
SSA_NAME_OCCURS_IN_ABNORMAL_PHI from propagated out virtuals.
* gcc.dg/pr88855.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/pr88855.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-if-conv.c
>From gcc-bugs-return-629270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:38:02 2019
Return-Path: <gcc-bugs-return-629270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130954 invoked by alias); 15 Jan 2019 15:38: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 130856 invoked by uid 48); 15 Jan 2019 15:37:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88855] [9 Regression] ICE: verify_ssa failed (error: SSA_NAME_OCCURS_IN_ABNORMAL_PHI should be set)
Date: Tue, 15 Jan 2019 15:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88855-4-Tbr8ZsKLJT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02079.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88855
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:41:00 2019
Return-Path: <gcc-bugs-return-629272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7334 invoked by alias); 15 Jan 2019 15: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 7293 invoked by uid 48); 15 Jan 2019 15:40:55 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88857] [7/8/9 Regression] ICE in build_value_init
Date: Tue, 15 Jan 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88857-4-1azLkW25HH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02081.txt.bz2
Content-length: 827
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88857
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
With the modified testcase the ICE started with r173679:
$ ./cc1plus.173678 -quiet ~/k.C -std=c++0x
k.C: In function ‘void g()’:
k.C:11:7: error: invalid initialization of reference of type ‘const Foo&’ from
expression of type ‘<brace-enclosed initializer list>’
k.C:6:6: error: in passing argument 1 of ‘void f(const Foo&, int)’
$ ./cc1plus.173679 -quiet ~/k.C -std=c++0x
k.C: In function ‘void g()’:
k.C:11:7: internal compiler error: in cxx_eval_bare_aggregate, at
cp/semantics.c:6539
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
>From gcc-bugs-return-629273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:41:24 2019
Return-Path: <gcc-bugs-return-629273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8366 invoked by alias); 15 Jan 2019 15:41: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 8266 invoked by uid 48); 15 Jan 2019 15:41:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88859-4-OiIY5qbFjf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02082.txt.bz2
Content-length: 400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Is r267938 a bisection result?
>From gcc-bugs-return-629274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:44:16 2019
Return-Path: <gcc-bugs-return-629274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16827 invoked by alias); 15 Jan 2019 15:44: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 16604 invoked by uid 48); 15 Jan 2019 15:44:09 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 15:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-VpYcHoGyRj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02083.txt.bz2
Content-length: 4858
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> (In reply to Iain Sandoe from comment #5)
> > (In reply to Richard Biener from comment #4)
> > > Hmm, I can no longer reproduce -g0 vs -g on x86_64-linux. Ians testresults
> > > now
> > > list
> > >
> > > but I can't reproduce with pr62017.C or pr78651.C either right now.
> >
> > 81021 has indeed started to pass (I didn't notice when).
> >
> > ===== 62017 is:
<snip>
> OK, that's PR88046 for which I have a patch in my tree.
great.
>
> >
> > ========= pr78651 is:
> >
> > $ /XC/9.4/usr/bin/lldb --
> > /scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1 -fPIC
> > -feliminate-unused-debug-symbols -quiet -dumpdir ./ -dumpbase pr78651.exe
> > -mmacosx-version-min=10.12.0 -mtune=core2 -m32 -mmacosx-version-min=10.12.0
> > -mtune=core2 -auxbase-strip pr78651.exe.lto.o -g -O2 -O2 -version
> > -fdiagnostics-color=never -fno-openmp -fno-openacc -fsanitize=address
> > -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> > -fmessage-length=0 -flto-partition=none -fpic
> > @/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up -o pr78651.s
> > (lldb) target create
> > "/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1"
> > Current executable set to
> > '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
> > (x86_64).
> > (lldb) settings set -- target.run-args "-fPIC"
> > "-feliminate-unused-debug-symbols" "-quiet" "-dumpdir" "./" "-dumpbase"
> > "pr78651.exe" "-mmacosx-version-min=10.12.0" "-mtune=core2" "-m32"
> > "-mmacosx-version-min=10.12.0" "-mtune=core2" "-auxbase-strip"
> > "pr78651.exe.lto.o" "-g" "-O2" "-O2" "-version" "-fdiagnostics-color=never"
> > "-fno-openmp" "-fno-openacc" "-fsanitize=address"
> > "-fno-diagnostics-show-caret" "-fno-diagnostics-show-line-numbers"
> > "-fmessage-length=0" "-flto-partition=none" "-fpic"
> > "@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up" "-o"
> > "pr78651.s"
> > (lldb) b internal_error
> > r
> > Breakpoint 1: where = lto1`internal_error(char const*, ...) + 121 [inlined]
> > _ZN21auto_diagnostic_groupC4Ev, address = 0x00000001010abcb9
> > (lldb) r
> > Process 22101 launched:
> > '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
> > (x86_64)
> > GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> > 267925] (x86_64-apple-darwin16)
> > compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> > 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> > version isl-0.20-GMP
> >
> > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> > GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> > 267925] (x86_64-apple-darwin16)
> > compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> > 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> > version isl-0.20-GMP
> >
> > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> > Process 22101 stopped
> > * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
> > frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
> > [inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
> > diagnostic.c:1616
> > 1613
> > 1614 auto_diagnostic_group::auto_diagnostic_group ()
> > 1615 {
> > -> 1616 global_dc->diagnostic_group_nesting_depth++;
> > 1617 }
> > 1618
> > 1619 /* Destructor: "pop" this group from global_dc. */
> > Target 0: (lto1) stopped.
> > (lldb) bt
> > * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
> > * frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
> > [inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
> > diagnostic.c:1616
> > frame #1: 0x00000001010abcb9 lto1`internal_error(gmsgid="in %s, at
> > %s:%d")
> > frame #2: 0x000000010170bf9c lto1`fancy_abort(file=<unavailable>,
> > line=<unavailable>, function=<unavailable>) at diagnostic.c:1607
> > frame #3: 0x00000001015991fc lto1`lhd_decl_printable_name(tree_node*,
> > int) at langhooks.c:222
> > frame #4: 0x00000001007b4288 lto1`::add_pubtype(decl=0x0000000143e25f18,
> > die=0x0000000143e27f50) at dwarf2out.c:11333
> > frame #5: 0x00000001007e70f1
> > lto1`::gen_struct_or_union_type_die(type=0x0000000143e25f18,
> > context_die=<unavailable>, usage=<unavailable>) at dwarf2out.c:25256
<snip>
>
> That I can't reproduce even when backing out all dwarf2out.c changes.
pubnames are on by default on Darwin, and not for Linux?
>From gcc-bugs-return-629275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:47:40 2019
Return-Path: <gcc-bugs-return-629275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21237 invoked by alias); 15 Jan 2019 15:47:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21123 invoked by uid 48); 15 Jan 2019 15:47:35 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88859-4-q7pFPzSZWA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02084.txt.bz2
Content-length: 198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Richard Biener from comment #1)
> Is r267938 a bisection result?
No.
>From gcc-bugs-return-629277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:49:33 2019
Return-Path: <gcc-bugs-return-629277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23722 invoked by alias); 15 Jan 2019 15:49: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 23669 invoked by uid 48); 15 Jan 2019 15:49:26 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Tue, 15 Jan 2019 15:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_known_to_work target_milestone cf_known_to_fail
Message-ID: <bug-88861-4-6kwMgQSSsz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02086.txt.bz2
Content-length: 403
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Known to work| |8.2.0
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-629276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:49:06 2019
Return-Path: <gcc-bugs-return-629276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22832 invoked by alias); 15 Jan 2019 15:49: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 22599 invoked by uid 48); 15 Jan 2019 15:48:46 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] New: [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Tue, 15 Jan 2019 15:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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 cf_gcchost cf_gcctarget
Message-ID: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02085.txt.bz2
Content-length: 1867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
Bug ID: 88861
Summary: [9 Regression] ICE in calc_dfs_tree, at
dominance.c:458
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: segher at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: ppc64-linux-gnu
Following is causing ICE:
$ cat flex.ii
struct Ax {
int n, a[];
};
int i = 12345678;
int main() {
static Ax s{456, i};
((s.a[0]) ? (void)0 : (void)0);
}
$ ppc64-linux-gnu-g++ flex.ii -O2 -fnon-call-exceptions -c
during RTL pass: ce2
flex.ii: In function ‘int main()’:
flex.ii:9:1: internal compiler error: in calc_dfs_tree, at dominance.c:458
9 | }
| ^
0x5923df calc_dfs_tree
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/dominance.c:458
0x82365d calculate_dominance_info(cdi_direction)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/dominance.c:734
0x7c476d flow_loops_find(loops*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/cfgloop.c:431
0x9ed2ae loop_optimizer_init(unsigned int)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/loop-init.c:93
0x117c280 if_convert
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/ifcvt.c:5374
0x117dc1d execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/ifcvt.c:5553
>From gcc-bugs-return-629279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:54:27 2019
Return-Path: <gcc-bugs-return-629279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52139 invoked by alias); 15 Jan 2019 15:54:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49781 invoked by uid 48); 15 Jan 2019 15:54:22 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88862] ICE in extract_affine, at graphite-sese-to-poly.c:313
Date: Tue, 15 Jan 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone cf_known_to_fail
Message-ID: <bug-88862-4-bU59ZWkV9B@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02088.txt.bz2
Content-length: 348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88862
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
Known to fail| |9.0
>From gcc-bugs-return-629278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:54:03 2019
Return-Path: <gcc-bugs-return-629278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43693 invoked by alias); 15 Jan 2019 15: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 43594 invoked by uid 48); 15 Jan 2019 15:53:58 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88862] New: ICE in extract_affine, at graphite-sese-to-poly.c:313
Date: Tue, 15 Jan 2019 15:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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 cf_gcchost cf_gcctarget
Message-ID: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02087.txt.bz2
Content-length: 2380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88862
Bug ID: 88862
Summary: ICE in extract_affine, at graphite-sese-to-poly.c:313
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: rguenth at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: arm-linux-gnueabihf
One graphite ICE:
$ arm-linux-gnueabi-gfortran
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/loc_2.f90 -O2
-fno-tree-loop-im --param graphite-max-nb-scop-params=2147483647
-fgraphite-identity -fwrapv
during GIMPLE pass: graphite
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.dg/loc_2.f90:19:0:
19 | subroutine testloc
|
internal compiler error: in extract_affine, at graphite-sese-to-poly.c:313
0x118db5d extract_affine
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite-sese-to-poly.c:313
0x118dced extract_affine
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite-sese-to-poly.c:293
0x118ef2a add_condition_to_pbb
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite-sese-to-poly.c:347
0x118ef2a add_conditions_to_domain
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite-sese-to-poly.c:414
0x118ef2a build_iteration_domains
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite-sese-to-poly.c:864
0x118f107 build_poly_scop(scop*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite-sese-to-poly.c:1213
0x11821e8 graphite_transform_loops()
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite.c:406
0x11825b0 graphite_transforms
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite.c:476
0x11825b0 execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-arm/build/gcc/graphite.c:553
>From gcc-bugs-return-629280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 15:59:07 2019
Return-Path: <gcc-bugs-return-629280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79605 invoked by alias); 15 Jan 2019 15:59:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79519 invoked by uid 48); 15 Jan 2019 15:59:02 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88863] New: ICE in extract_insn, at recog.c:2305
Date: Tue, 15 Jan 2019 15:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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 cf_gcchost cf_gcctarget
Message-ID: <bug-88863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02089.txt.bz2
Content-length: 2141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88863
Bug ID: 88863
Summary: ICE in extract_insn, at recog.c:2305
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: segher at gcc dot gnu.org
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: ppc64-linux-gnu
Following is causing trouble:
$ cat math.i
int a;
void b() {
__builtin_log(a);
__builtin_logf(a);
__builtin_logl(a);
__builtin_log10f(a);
__builtin_log10l(a);
__builtin_log1p(a);
__builtin_log2f(a);
}
$ ppc64-linux-gnu-gcc -fno-tree-dce -fno-tree-sink -Ofast -c math.i -c
math.i: In function ‘b’:
math.i:10:1: error: unrecognizable insn:
10 | }
| ^
(insn 21 20 22 4 (set (reg:DI 138)
(ungt:DI (reg:CCFP 137)
(const_int 0 [0]))) -1
(nil))
during RTL pass: vregs
math.i:10:1: internal compiler error: in extract_insn, at recog.c:2305
0x577d1d _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/rtl-error.c:108
0x577d39 _fatal_insn_not_found(rtx_def const*, char const*, int, char const*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/rtl-error.c:116
0x577226 extract_insn(rtx_insn*)
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/recog.c:2305
0x7cc4ef instantiate_virtual_regs_in_insn
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/function.c:1605
0x7cc4ef instantiate_virtual_regs
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/function.c:1975
0x7cc4ef execute
/home/marxin/BIG/buildbot/buildworker/marxinbox-gcc-trunk-ppc64/build/gcc/function.c:2024
>From gcc-bugs-return-629281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:01:15 2019
Return-Path: <gcc-bugs-return-629281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83503 invoked by alias); 15 Jan 2019 16:01:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82846 invoked by uid 48); 15 Jan 2019 16:00:27 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 16:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-1iGWd7hkxx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02090.txt.bz2
Content-length: 4930
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Iain Sandoe from comment #8)
> (In reply to Richard Biener from comment #7)
> > (In reply to Iain Sandoe from comment #5)
> > > ========= pr78651 is:
> > >
> > > $ /XC/9.4/usr/bin/lldb --
> > > /scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1 -fPIC
> > > -feliminate-unused-debug-symbols -quiet -dumpdir ./ -dumpbase pr78651.exe
> > > -mmacosx-version-min=10.12.0 -mtune=core2 -m32 -mmacosx-version-min=10.12.0
> > > -mtune=core2 -auxbase-strip pr78651.exe.lto.o -g -O2 -O2 -version
> > > -fdiagnostics-color=never -fno-openmp -fno-openacc -fsanitize=address
> > > -fno-diagnostics-show-caret -fno-diagnostics-show-line-numbers
> > > -fmessage-length=0 -flto-partition=none -fpic
> > > @/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up -o pr78651.s
> > > (lldb) target create
> > > "/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1"
> > > Current executable set to
> > > '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
> > > (x86_64).
> > > (lldb) settings set -- target.run-args "-fPIC"
> > > "-feliminate-unused-debug-symbols" "-quiet" "-dumpdir" "./" "-dumpbase"
> > > "pr78651.exe" "-mmacosx-version-min=10.12.0" "-mtune=core2" "-m32"
> > > "-mmacosx-version-min=10.12.0" "-mtune=core2" "-auxbase-strip"
> > > "pr78651.exe.lto.o" "-g" "-O2" "-O2" "-version" "-fdiagnostics-color=never"
> > > "-fno-openmp" "-fno-openacc" "-fsanitize=address"
> > > "-fno-diagnostics-show-caret" "-fno-diagnostics-show-line-numbers"
> > > "-fmessage-length=0" "-flto-partition=none" "-fpic"
> > > "@/var/folders/tj/17r7407j14d324dzf67cnvxm000114/T//ccUkv7Up" "-o"
> > > "pr78651.s"
> > > (lldb) b internal_error
> > > r
> > > Breakpoint 1: where = lto1`internal_error(char const*, ...) + 121 [inlined]
> > > _ZN21auto_diagnostic_groupC4Ev, address = 0x00000001010abcb9
> > > (lldb) r
> > > Process 22101 launched:
> > > '/scratch/10-12-sie/gcc-trunk-unpatched/gcc/testsuite/g++2/../../lto1'
> > > (x86_64)
> > > GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> > > 267925] (x86_64-apple-darwin16)
> > > compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> > > 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> > > version isl-0.20-GMP
> > >
> > > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> > > GNU GIMPLE (GCC) version 9.0.0 20190114 (experimental) [trunk revision
> > > 267925] (x86_64-apple-darwin16)
> > > compiled by GNU C version 9.0.0 20190114 (experimental) [trunk revision
> > > 267925], GMP version 6.1.2, MPFR version 3.1.6, MPC version 1.1.0, isl
> > > version isl-0.20-GMP
> > >
> > > GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
> > > Process 22101 stopped
> > > * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
> > > frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
> > > [inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
> > > diagnostic.c:1616
> > > 1613
> > > 1614 auto_diagnostic_group::auto_diagnostic_group ()
> > > 1615 {
> > > -> 1616 global_dc->diagnostic_group_nesting_depth++;
> > > 1617 }
> > > 1618
> > > 1619 /* Destructor: "pop" this group from global_dc. */
> > > Target 0: (lto1) stopped.
> > > (lldb) bt
> > > * thread #1, queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
> > > * frame #0: 0x00000001010abcb9 lto1`internal_error(char const*, ...)
> > > [inlined] _ZN21auto_diagnostic_groupC4Ev(this=<unavailable>) at
> > > diagnostic.c:1616
> > > frame #1: 0x00000001010abcb9 lto1`internal_error(gmsgid="in %s, at
> > > %s:%d")
> > > frame #2: 0x000000010170bf9c lto1`fancy_abort(file=<unavailable>,
> > > line=<unavailable>, function=<unavailable>) at diagnostic.c:1607
> > > frame #3: 0x00000001015991fc lto1`lhd_decl_printable_name(tree_node*,
> > > int) at langhooks.c:222
> > > frame #4: 0x00000001007b4288 lto1`::add_pubtype(decl=0x0000000143e25f18,
> > > die=0x0000000143e27f50) at dwarf2out.c:11333
> > > frame #5: 0x00000001007e70f1
> > > lto1`::gen_struct_or_union_type_die(type=0x0000000143e25f18,
> > > context_die=<unavailable>, usage=<unavailable>) at dwarf2out.c:25256
>
> <snip>
> >
> > That I can't reproduce even when backing out all dwarf2out.c changes.
>
> pubnames are on by default on Darwin, and not for Linux?
True. But -g[gnu-]pubnames doesn't change things :/ So we run into
const char *
lhd_decl_printable_name (tree decl, int ARG_UNUSED (verbosity))
{
gcc_assert (decl && DECL_NAME (decl));
return IDENTIFIER_POINTER (DECL_NAME (decl));
with a decl without a name?
>From gcc-bugs-return-629282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:02:05 2019
Return-Path: <gcc-bugs-return-629282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86098 invoked by alias); 15 Jan 2019 16:02:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86017 invoked by uid 48); 15 Jan 2019 16:02:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88862] ICE in extract_affine, at graphite-sese-to-poly.c:313
Date: Tue, 15 Jan 2019 16:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88862-4-gBhf32eyzi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02091.txt.bz2
Content-length: 583
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88862
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-15
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I will have a look.
>From gcc-bugs-return-629283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:03:09 2019
Return-Path: <gcc-bugs-return-629283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87407 invoked by alias); 15 Jan 2019 16:03: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 87342 invoked by uid 48); 15 Jan 2019 16:03:05 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Tue, 15 Jan 2019 16:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88861-4-Y24xinmGqq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02092.txt.bz2
Content-length: 161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
That means we have unreachable blocks.
>From gcc-bugs-return-629284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:07:19 2019
Return-Path: <gcc-bugs-return-629284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31228 invoked by alias); 15 Jan 2019 16:07: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 23935 invoked by uid 55); 15 Jan 2019 16:07:14 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88046] [9 Regression] ICE in add_data_member_location_attribute at gcc/dwarf2out.c:19237 since r261885
Date: Tue, 15 Jan 2019 16:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88046-4-7jCqUxkLBI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02093.txt.bz2
Content-length: 621
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88046
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Tue Jan 15 16:06:42 2019
New Revision: 267940
URL: https://gcc.gnu.org/viewcvs?rev=267940&root=gcc&view=rev
Log:
2019-01-15 Richard Biener <rguenther@suse.de>
PR debug/88046
* dwarf2out.c (gen_member_die): Do not generate inheritance
DIEs late.
* g++.dg/lto/pr88046_0.C: New testcase.
Added:
trunk/gcc/testsuite/g++.dg/lto/pr88046_0.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/dwarf2out.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:08:24 2019
Return-Path: <gcc-bugs-return-629285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62832 invoked by alias); 15 Jan 2019 16:08: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 62752 invoked by uid 48); 15 Jan 2019 16:08:20 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88046] [9 Regression] ICE in add_data_member_location_attribute at gcc/dwarf2out.c:19237 since r261885
Date: Tue, 15 Jan 2019 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88046-4-Ehw1EomTc4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02094.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88046
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:08:25 2019
Return-Path: <gcc-bugs-return-629286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62954 invoked by alias); 15 Jan 2019 16:08:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62788 invoked by uid 48); 15 Jan 2019 16:08:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/86549] [8/9 Regression] -flto -g0 vs. -g issues
Date: Tue, 15 Jan 2019 16:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-86549-4-owZU7B5s9J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86549-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86549-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02095.txt.bz2
Content-length: 523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86549
Bug 86549 depends on bug 88046, which changed state.
Bug 88046 Summary: [9 Regression] ICE in add_data_member_location_attribute at gcc/dwarf2out.c:19237 since r261885
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88046
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-629287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:11:49 2019
Return-Path: <gcc-bugs-return-629287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94923 invoked by alias); 15 Jan 2019 16:11: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 94799 invoked by uid 48); 15 Jan 2019 16:11:42 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 16:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-IjED5Ll5DY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02096.txt.bz2
Content-length: 1569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #10 from Iain Sandoe <iains at gcc dot gnu.org> ---
dunno if this is helpful...
frame #4: 0x00000001007b4288 lto1`::add_pubtype(decl=0x0000000144625f18,
die=0x0000000144627f50) at dwarf2out.c:11333
11330 scope = TYPE_P (decl) ? TYPE_CONTEXT (decl) : NULL;
11331 if (scope && TREE_CODE (scope) == NAMESPACE_DECL)
11332 {
-> 11333 scope_name = lang_hooks.dwarf_name (scope, 1);
11334 if (scope_name != NULL && scope_name[0] != '\0')
11335 scope_name = concat (scope_name, sep, NULL);
11336 else
(lldb) p (void)debug_tree(decl)
<record_type 0x144625f18 SomeRandomType asm_written QI
size <integer_cst 0x144402cc0 type <integer_type 0x1444170a8 bitsizetype>
constant 8>
unit-size <integer_cst 0x144402cd8 type <integer_type 0x144417000 sizetype>
constant 1>
align:8 warn_if_not_align:0 symtab:1147305808 alias-set -1 canonical-type
0x144625f18 context <namespace_decl 0x1446212f8 D.4634>>
(lldb) p (void)debug_tree((tree) 0x1446212f8)
<namespace_decl 0x1446212f8 D.4634
type <void_type 0x14441e0a8 void VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 structural-equality
pointer_to_this <pointer_type 0x14441e150>>
VOID /src/gcc-trunk/gcc/testsuite/g++.dg/asan/pr78651.C:7:1
align:1 warn_if_not_align:0 context <translation_unit_decl 0x14440c1e0
/src/gcc-trunk/gcc/testsuite/g++.dg/asan/pr78651.C>>
>From gcc-bugs-return-629288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:17:44 2019
Return-Path: <gcc-bugs-return-629288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105463 invoked by alias); 15 Jan 2019 16:17:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 105379 invoked by uid 48); 15 Jan 2019 16:17:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 16:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-eKRMbeXYMq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02097.txt.bz2
Content-length: 5745
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #16 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Some more progress.
I've used
--- gcc/combine.c.jj 2019-01-10 11:43:17.050333949 +0100
+++ gcc/combine.c 2019-01-15 14:47:28.009094300 +0100
@@ -2319,6 +2319,9 @@ contains_muldiv (rtx x)
}
}
+int cxcnt = -1;
+int cxcurcnt = 0;
+
/* Determine whether INSN can be used in a combination. Return nonzero if
not. This is used in try_combine to detect early some cases where we
can't perform combinations. */
@@ -2361,7 +2364,8 @@ cant_combine_insn_p (rtx_insn *insn)
#endif
|| (HARD_REGISTER_P (dest)
&& ! TEST_HARD_REG_BIT (fixed_reg_set, REGNO (dest))
- && targetm.class_likely_spilled_p (REGNO_REG_CLASS (REGNO
(dest))))))
+ && (targetm.class_likely_spilled_p (REGNO_REG_CLASS (REGNO
(dest)))
+ || (getenv ("COMBINE_FIRST") && cxcurcnt == cxcnt)))))
return 1;
return 0;
@@ -14993,6 +14997,12 @@ make_more_copies (void)
{
basic_block bb;
+ if (cxcnt == -1 && getenv ("COMBINE_CNT"))
+ cxcnt = atoi (getenv ("COMBINE_CNT"));
+ ++cxcurcnt;
+ if (getenv ("COMBINE_SECOND") && cxcurcnt == cxcnt)
+ return;
+
FOR_EACH_BB_FN (bb, cfun)
{
rtx_insn *insn;
hack to undo both or any one of the two changes r265398 did on the function of
my choice (initialy for binary search I was using cxcurcnt >= cxcnt instead of
cxcurcnt == cxcnt in the two spots), and found that with
COMBINE_CNT=74 COMBINE_FIRST=1 COMBINE_SECOND=1
sort.i works as in stage1, so it is
_ZL21vn_reference_lookup_2P6ao_refP9tree_nodejPv that actually matters.
COMBINE_CNT=74 COMBINE_SECOND=1 generates the same (good assembly) as
COMBINE_CNT=74 COMBINE_FIRST=1 COMBINE_SECOND=1, while
COMBINE_CNT=74 COMBINE_FIRST=1 doesn't work the same as COMBINE_CNT=200.
The "bad" to "good" assembly difference is:
.type _ZL21vn_reference_lookup_2P6ao_refP9tree_nodejPv, %function
_ZL21vn_reference_lookup_2P6ao_refP9tree_nodejPv:
.fnstart
@ args = 0, pretend = 0, frame = 8
@ frame_needed = 0, uses_anonymous_args = 0
movw r0, #:lower16:global_options
- mov ip, r1
- movt r0, #:upper16:global_options
push {r4, r5, r6, lr}
.save {r4, r5, r6, lr}
- ldr r0, [r0, #88]
+ movt r0, #:upper16:global_options
+ mov r5, r3
.pad #8
sub sp, sp, #8
- str r3, [sp]
- ldr r1, [r0, #540]
- cmp r1, r2
+ ldr r3, [r0, #88]
+ str r5, [sp]
+ ldr r3, [r3, #540]
+ cmp r3, r2
bcc .L2103
- movw r5, #:lower16:.LANCHOR1
- mov r4, r3
- movt r5, #:upper16:.LANCHOR1
- ldr r3, [r5, #176]
+ movw r4, #:lower16:.LANCHOR1
+ mov ip, r1
+ movt r4, #:upper16:.LANCHOR1
+ ldr r3, [r4, #176]
cmp r3, #0
- strne ip, [r3]
- ldr r3, [r4, #12]
+ strne r1, [r3]
+ ldr r3, [r5, #12]
cmp r3, #0
ldrne r2, [r3, #4]
- ldrne r3, [r4, #8]
+ ldrne r3, [r5, #8]
subne r3, r3, r2
- strne r3, [r4, #8]
- cmp ip, #0
+ strne r3, [r5, #8]
+ cmp r1, #0
beq .L2104
- ldr r6, [r5, #12]
+ ldr r6, [r4, #12]
b .L2101
.L2127:
- ldr ip, [r2, #4]
+ ldr ip, [r3, #4]
.L2099:
- ldr r3, [r5, #8]
+ ldr r3, [r4, #8]
cmp r3, ip
beq .L2125
ldrb r3, [ip, #3] @ zero_extendqisi2
tst r3, #2
beq .L2126
.L2101:
ldr r2, [ip, #4]
add r1, sp, #4
mov r0, r6
str ip, [sp, #4]
bl
_ZN10hash_tableI17vn_ssa_aux_hasher11xcallocatorE14find_with_hashERKP9tree_nodej
- ldr r2, [r0]
- cmp r2, #0
+ ldr r3, [r0]
+ cmp r3, #0
beq .L2098
- ldrb r3, [r2, #16] @ zero_extendqisi2
- tst r3, #1
+ ldrb r2, [r3, #16] @ zero_extendqisi2
+ tst r2, #1
bne .L2127
.L2098:
ldr ip, [sp, #4]
b .L2099
.L2126:
- ldr r1, [sp]
+ ldr r3, [sp]
.L2097:
- ldrd r2, [r1, #8]
- str ip, [r4, #12]
- ldr r0, [r5, #28]
- cmp r3, #0
- ldrne r3, [r3, #4]
+ str ip, [r5, #12]
+ ldr r1, [r3, #12]
+ ldr r2, [r3, #8]
+ ldr r0, [r4, #28]
+ cmp r1, #0
+ ldrne r1, [r1, #4]
ldr r0, [r0, #8]
- addne r2, r2, r3
- mov r3, #0
- strne r2, [r1, #8]
+ addne r2, r2, r1
mov r1, sp
+ strne r2, [r3, #8]
+ mov r3, #0
bl
_ZN10hash_tableI19vn_reference_hasher11xcallocatorE19find_slot_with_hashERKP14vn_reference_sj13insert_option
cmp r0, #0
ldrne r0, [r0]
.L2093:
add sp, sp, #8
@ sp needed
pop {r4, r5, r6, pc}
.L2103:
mvn r0, #0
add sp, sp, #8
@ sp needed
pop {r4, r5, r6, pc}
.L2104:
- mov r1, r4
+ mov r3, r5
b .L2097
.L2125:
movw r2, #:lower16:.LC42
movw r0, #:lower16:.LC3
movt r2, #:upper16:.LC42
movt r0, #:upper16:.LC3
movw r1, #481
bl _Z11fancy_abortPKciS0_
.fnend
.size _ZL21vn_reference_lookup_2P6ao_refP9tree_nodejPv,
.-_ZL21vn_reference_lookup_2P6ao_refP9tree_nodejPv
>From gcc-bugs-return-629289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:22:18 2019
Return-Path: <gcc-bugs-return-629289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115552 invoked by alias); 15 Jan 2019 16:22: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 115484 invoked by uid 48); 15 Jan 2019 16:22:14 -0000
From: "Casey at Carter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/70303] Value-initialized debug iterators
Date: Tue, 15 Jan 2019 16:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Casey at Carter dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-70303-4-v4neKPkREQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02098.txt.bz2
Content-length: 1170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70303
Casey Carter <Casey at Carter dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Casey at Carter dot net
--- Comment #4 from Casey Carter <Casey at Carter dot net> ---
(In reply to Jonathan Wakely from comment #3)
> Or is the implication of equality being valid that a+n is valid for n==0,
> and therefore b-a is valid, and therefore relational ops are valid?
Certainly b-a is required to be valid, since such an n exists as required by
[random.access.iterators] - but admittedly the IS doesn't specify the domain
for relational comparisons on Cpp17 iterators. IMO this is a defect since it
implies you can *never* compare two iterators with e.g. <.
We should require the domain of relational comparisons to be the same as the
domain of equality, which would then make it clear that value-initialized
iterators are in their domain. (I was under the impression that we *did*
require this "somewhere" when I filed this issue and fixed MSFTL's iterators.)
>From gcc-bugs-return-629290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:25:05 2019
Return-Path: <gcc-bugs-return-629290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120635 invoked by alias); 15 Jan 2019 16:25:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120021 invoked by uid 48); 15 Jan 2019 16:24:39 -0000
From: "Casey at Carter dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/70303] Value-initialized debug iterators
Date: Tue, 15 Jan 2019 16:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: Casey at Carter dot net
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-70303-4-jeyMEiwXkb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70303-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02099.txt.bz2
Content-length: 328
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70303
--- Comment #5 from Casey Carter <Casey at Carter dot net> ---
IIRC my reasoning was that [random.access.iterators] specifies the operational
semantics of `a < b` to be `b - a > 0`, which suggests but doesn't quite
require that `a < b` is valid whenever `b - a` is valid.
>From gcc-bugs-return-629291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:27:27 2019
Return-Path: <gcc-bugs-return-629291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126836 invoked by alias); 15 Jan 2019 16:27: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 126645 invoked by uid 48); 15 Jan 2019 16:27:23 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Tue, 15 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-8LOCp8rDIq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02100.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
so, no... it doesn't have a name.
(lldb) p ((tree)0x1446212f8)->decl_minimal.name
(tree) $5 = 0x0000000000000000
>From gcc-bugs-return-629292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:28:42 2019
Return-Path: <gcc-bugs-return-629292-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129428 invoked by alias); 15 Jan 2019 16: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 129315 invoked by uid 48); 15 Jan 2019 16:28:37 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37835] -fno-automatic does not work for derived types with default initalizer
Date: Tue, 15 Jan 2019 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-37835-4-qCMLB5CAWE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-37835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-37835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02101.txt.bz2
Content-length: 1255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=37835
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> (6) ...
The additional patch
--- ../_clean/gcc/fortran/symbol.c 2019-01-09 22:54:02.000000000 +0100
+++ gcc/fortran/symbol.c 2019-01-15 16:28:17.000000000 +0100
@@ -1306,9 +1306,7 @@ gfc_add_save (symbol_attribute *attr, sa
if (s == SAVE_EXPLICIT)
gfc_unset_implicit_pure (NULL);
- if (s == SAVE_EXPLICIT && attr->save == SAVE_EXPLICIT)
+ if (s == SAVE_EXPLICIT && attr->save == SAVE_EXPLICIT && flag_automatic)
{
if (!gfc_notify_std (GFC_STD_LEGACY,
"Duplicate SAVE attribute specified at %L",
silences the warnings (errors).
Do we need to add to the -fno-automatic doc a note saying that TUs with
variables having an explicit SAVE attribute are silently accepted (even with
-std=f*)?
Along this line do we need to forbid it with -pedantic (by adding &&
!pedantic)?
>From gcc-bugs-return-629293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:28:48 2019
Return-Path: <gcc-bugs-return-629293-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130078 invoked by alias); 15 Jan 2019 16:28: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 129380 invoked by uid 48); 15 Jan 2019 16:28:40 -0000
From: "barry.revzin at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88864] New: default template arguments not merged across all declarations
Date: Tue, 15 Jan 2019 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: barry.revzin at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02102.txt.bz2
Content-length: 747
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88864
Bug ID: 88864
Summary: default template arguments not merged across all
declarations
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: barry.revzin at gmail dot com
Target Milestone: ---
Shorter repro from StackOverflow https://stackoverflow.com/q/54202462/2069064:
struct B {
template<typename T, typename U> B(T t);
};
template <typename T, typename U = int>
B::B(T t) { }
B b(3);
This is rejected by all versions of gcc because of an inability to deduce U.
>From gcc-bugs-return-629294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:31:28 2019
Return-Path: <gcc-bugs-return-629294-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30836 invoked by alias); 15 Jan 2019 16:31:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 30013 invoked by uid 48); 15 Jan 2019 16:30:48 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/87836] ICE in cc1 for gcc-6.5.0 with SPARC hardware
Date: Tue, 15 Jan 2019 16:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-87836-4-UDcIehIVYR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02103.txt.bz2
Content-length: 510
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87836
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #33 from Rainer Orth <ro at gcc dot gnu.org> ---
Unless I'm mistaken, we've now established that there's no bug in gcc here.
Thus closing as invalid.
>From gcc-bugs-return-629295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 16:47:34 2019
Return-Path: <gcc-bugs-return-629295-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78144 invoked by alias); 15 Jan 2019 16:47:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 78064 invoked by uid 55); 15 Jan 2019 16:47:29 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/52813] %rsp in clobber list is silently ignored
Date: Tue, 15 Jan 2019 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: inline-asm
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: patch
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-52813-4-4hBtPx66bw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-52813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-52813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02104.txt.bz2
Content-length: 1867
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52813
--- Comment #8 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Tue Jan 15 16:46:54 2019
New Revision: 267941
URL: https://gcc.gnu.org/viewcvs?rev=267941&root=gcc&view=rev
Log:
PR inline-asm/52813 revisited
The original patch for this PR made it an error to list the stack
pointer in the clobber list of an inline asm. However, the general
feeling seemed to be that going straight to a hard error was too harsh,
since there's quite a bit of existing code that has the clobber.
This patch implements the compromise discussed on IRC of making it
a -Wdeprecated warning instead.
2019-01-15 Richard Sandiford <richard.sandiford@arm.com>
gcc/
PR inline-asm/52813
* doc/extend.texi: Document that listing the stack pointer in the
clobber list of an asm is a deprecated feature.
* common.opt (Wdeprecated): Moved from c-family/c.opt.
* cfgexpand.c (asm_clobber_reg_is_valid): Issue a -Wdeprecated
warning instead of an error for clobbers of the stack pointer.
Add a note explaining why.
gcc/c-family/
PR inline-asm/52813
* c.opt (Wdeprecated): Move documentation and variable to common.opt.
gcc/d/
PR inline-asm/52813
* lang.opt (Wdeprecated): Reference common.opt instead of c.opt.
gcc/testsuite/
PR inline-asm/52813
* gcc.target/i386/pr52813.c (test1): Turn the diagnostic into a
-Wdeprecated warning and expect a following note:.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c.opt
trunk/gcc/cfgexpand.c
trunk/gcc/common.opt
trunk/gcc/d/ChangeLog
trunk/gcc/d/lang.opt
trunk/gcc/doc/extend.texi
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.target/i386/pr52813.c
>From gcc-bugs-return-629296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 17:02:07 2019
Return-Path: <gcc-bugs-return-629296-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129062 invoked by alias); 15 Jan 2019 17:02:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129013 invoked by uid 48); 15 Jan 2019 17:02:02 -0000
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88865] New: [[no_unique_address]] leads to sizeof(T) == 0, which cannot be
Date: Tue, 15 Jan 2019 17: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redbeard0531 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-88865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02105.txt.bz2
Content-length: 1653
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88865
Bug ID: 88865
Summary: [[no_unique_address]] leads to sizeof(T) == 0, which
cannot be
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redbeard0531 at gmail dot com
Target Milestone: ---
https://godbolt.org/z/rJT5X9
struct B {};
struct A {
[[no_unique_address]] B a;
[[no_unique_address]] B b;
[[no_unique_address]] B c;
[[no_unique_address]] B d;
};
int f() {
return sizeof(A);
}
f():
push rbp
mov rbp, rsp
mov eax, 0
pop rbp
ret
In addition to the major issue that sizeof(A) must not be 0, it also must not
be 1 either. It must be (at least) 4.
http://eel.is/c++draft/intro.object#9.sentence-2 is very clear that
[[no_unique_address]] (which clauses 7 and 8 define to mean a "subobject of
zero size") only allows members of *different types* to overlap. a,b,c, and d
are all distinct objects of the same type B, and therefore must have distinct
addresses.
> Two objects with overlapping lifetimes that are not bit-fields may have the same address if one is nested within the other, or if at least one is a subobject of zero size and they are of different types; otherwise, they have distinct addresses and occupy disjoint bytes of storage.
https://godbolt.org/z/160XGN shows that some parts of gcc seem to understand
this rule, some something very strange must be going on.
>From gcc-bugs-return-629297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 17:07:20 2019
Return-Path: <gcc-bugs-return-629297-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12967 invoked by alias); 15 Jan 2019 17: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 12936 invoked by uid 48); 15 Jan 2019 17:07:16 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88866] New: g++.dg/cpp0x/variadic126.C fails with -std=c++2a
Date: Tue, 15 Jan 2019 17:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02106.txt.bz2
Content-length: 791
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88866
Bug ID: 88866
Summary: g++.dg/cpp0x/variadic126.C fails with -std=c++2a
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
FAIL: g++.dg/cpp0x/variadic126.C -std=c++2a (test for errors, line 6)
FAIL: g++.dg/cpp0x/variadic126.C -std=c++2a (test for excess errors)
error: type/value mismatch at argument 1 in template parameter list for
'template<class ...> struct A'
error: expected '{' before ';' token
starting with r267741. Perhaps we need tentative parsing after all...
>From gcc-bugs-return-629298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 17:07:44 2019
Return-Path: <gcc-bugs-return-629298-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13842 invoked by alias); 15 Jan 2019 17: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 13778 invoked by uid 48); 15 Jan 2019 17:07:39 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88866] g++.dg/cpp0x/variadic126.C fails with -std=c++2a
Date: Tue, 15 Jan 2019 17:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to target_milestone everconfirmed
Message-ID: <bug-88866-4-0KzW8bQBfF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02107.txt.bz2
Content-length: 548
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88866
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-15
Assignee|unassigned at gcc dot gnu.org |mpolacek at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
>From gcc-bugs-return-629299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 17:21:30 2019
Return-Path: <gcc-bugs-return-629299-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57855 invoked by alias); 15 Jan 2019 17:21:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57825 invoked by uid 48); 15 Jan 2019 17:21:26 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43210] Initializer of huge static arrays should be improved
Date: Tue, 15 Jan 2019 17:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-43210-4-02FUy0hznI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-43210-4@http.gcc.gnu.org/bugzilla/>
References: <bug-43210-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02108.txt.bz2
Content-length: 441
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43210
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |WAITING
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This PR is almost ten year old. Any point to let it rot anymore?
>From gcc-bugs-return-629300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 17:36:42 2019
Return-Path: <gcc-bugs-return-629300-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83554 invoked by alias); 15 Jan 2019 17:36: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 83464 invoked by uid 48); 15 Jan 2019 17:36:35 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Tue, 15 Jan 2019 17:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85949-4-KRY9Zru9bM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02109.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Unfortunately, not easily. By the time attribute arguments are being validated
their location information has been stripped. Keeping it around is possible
but will likely involve some intrusive changes that would not be appropriate at
this stage of GCC 9 development. Hopefully we can improve things in GCC 10.
David Malcolm has been doing great work in the area of diagnostic location
information so maybe it's already on his to-do list.
>From gcc-bugs-return-629301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:03:08 2019
Return-Path: <gcc-bugs-return-629301-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73764 invoked by alias); 15 Jan 2019 18:03: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 73683 invoked by uid 48); 15 Jan 2019 18:03:03 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Tue, 15 Jan 2019 18:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.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: attachments.created
Message-ID: <bug-85949-4-CIuYqLBQav@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02110.txt.bz2
Content-length: 246
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
--- Comment #6 from Jonny Grant <jg at jguk dot org> ---
Created attachment 45435
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45435&action=edit
Could these be detected as errors?
>From gcc-bugs-return-629302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:10:26 2019
Return-Path: <gcc-bugs-return-629302-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32410 invoked by alias); 15 Jan 2019 18:10:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31512 invoked by uid 48); 15 Jan 2019 18:10:21 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88866] [9 Regression] g++.dg/cpp0x/variadic126.C fails with -std=c++2a
Date: Tue, 15 Jan 2019 18:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88866-4-LEbmXOjOee@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02111.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88866
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|rejects-valid |
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Ah actually that's invalid code and the error message just needs tweaking. No
need for tentative parsing.
>From gcc-bugs-return-629303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:11:21 2019
Return-Path: <gcc-bugs-return-629303-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33525 invoked by alias); 15 Jan 2019 18:11: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 33470 invoked by uid 48); 15 Jan 2019 18:11:16 -0000
From: "levon at movementarian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88867] New: -Waggressive-loop-optimizations doesn't warn when -faggressive-loop-optimizations is in play
Date: Tue, 15 Jan 2019 18: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: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: levon at movementarian 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-88867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02112.txt.bz2
Content-length: 1325
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88867
Bug ID: 88867
Summary: -Waggressive-loop-optimizations doesn't warn when
-faggressive-loop-optimizations is in play
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: levon at movementarian dot org
Target Milestone: ---
Given how dangerous -faggressive-loop-optimizations has been proven to be, it's
unfortunate that -Waggressive-loop-optimizations is non-functional in even
simple cases. For example this test case:
#define NULL ((void *)0)
static char *arr[2] = { "nasal", "demons" };
long
func()
{
int i;
for (i = 0; i <= 2; i++) {
if (arr[i] == NULL && i == 0)
return (0xbad);
}
return (0xfad);
}
Is optimized to "return 0xbad" with -faggressive-loop-optimizations, but it is
not possible to get GCC to warn about this. -Waggressive-loop-optimizations
should warn every single time it relies on out-of-bounds behaviour like this.
Otherwise, such code becomes impossible to find and fix.
Same with trunk gcc on godbolt:
https://godbolt.org/z/MN1beq
>From gcc-bugs-return-629304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:21:05 2019
Return-Path: <gcc-bugs-return-629304-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81583 invoked by alias); 15 Jan 2019 18:21: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 81510 invoked by uid 48); 15 Jan 2019 18:21:01 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88867] -Waggressive-loop-optimizations doesn't warn when -faggressive-loop-optimizations is in play
Date: Tue, 15 Jan 2019 18:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component
Message-ID: <bug-88867-4-64cAhh3JQI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02113.txt.bz2
Content-length: 637
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88867
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Component|c |tree-optimization
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
>Otherwise, such code becomes impossible to find and fix.
I think with Address Santizier you could find it and fix it.
That being said security is about auditing and putting in place auditing
methods.
>From gcc-bugs-return-629305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:26:44 2019
Return-Path: <gcc-bugs-return-629305-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104306 invoked by alias); 15 Jan 2019 18:26:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104223 invoked by uid 55); 15 Jan 2019 18:26:39 -0000
From: "dominiq at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88803] gfortran documentation warning: '.' or ',' must follow @xref
Date: Tue, 15 Jan 2019 18:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: minor
X-Bugzilla-Who: dominiq at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88803-4-eRT7jmBd9A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02114.txt.bz2
Content-length: 515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88803
--- Comment #5 from dominiq at gcc dot gnu.org ---
Author: dominiq
Date: Tue Jan 15 18:26:07 2019
New Revision: 267943
URL: https://gcc.gnu.org/viewcvs?rev=267943&root=gcc&view=rev
Log:
2019-01-15 Dominique d'Humieres <dominiq@gcc.gnu.org>
PR fortran/88803
* gfortran.texi: Replace @xref with @ref and adjust the sentence.
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/gfortran.texi
>From gcc-bugs-return-629306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:29:02 2019
Return-Path: <gcc-bugs-return-629306-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110367 invoked by alias); 15 Jan 2019 18:29: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 110264 invoked by uid 48); 15 Jan 2019 18:28:57 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85949] __attribute__ ((format (printf,1,1))); improve error messages
Date: Tue, 15 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85949-4-3PA2Fpt42u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85949-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02115.txt.bz2
Content-length: 2119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85949
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
There are two kinds of warnings for printf-type functions: -Wformat implemented
in the front-ends, and -Wformat-overflow/truncation implemented in the
middle-end. The former detects mostly just type-based errors and doesn't
depend on optimization, while the latter detects errors that depend on control
and data flow analyses exposed by optimization (buffer overflow, truncation,
null pointers, and some uses of unterminated character arrays as %s
arguments). Some bugs that are in the intersection of the two are not detected
by either.
The test case in attachment 45435 is of the latter kind: it depends on data
flow analysis. With optimization enabled it can detect the bug in the second
call to str_fmt(), but only if the call uses the arguments (or is not known not
to use it). The extra argument in the first call to str_fmt() is not detected
-- it's in the third class of problems: the front-end doesn't see the value of
the format string and the middle-end doesn't check for extra arguments.
Ideally, there would be just one implementation of all format warnings that did
all kinds of checking, but merging the two existing implementations would be a
lot of effort. Short of that, we could look into moving (or duplicating) some
of the same front-end checks into the middle-end in cases where it's important.
The trick is to avoid issuing duplicate warnings between the two sets of
checks. The caveat with that, though, is that detecting the problems with
non-constants only works with optimization.
$ cat t.c && gcc -O2 -S -Wall t.c
void str_fmt(const char * const format, ...) __attribute__ ((format
(printf,1,2)));
int main()
{
const int i = 0;
const char * str = "abc";
const char * str2 = "%s";
str_fmt(str, i);
str_fmt(str2, i);
}
t.c: In function ‘main’:
t.c:11:5: warning: ‘%s’ directive argument is null [-Wformat-overflow=]
11 | str_fmt(str2, i);
| ^~~~~~~~~~~~~~~~
>From gcc-bugs-return-629307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:35:37 2019
Return-Path: <gcc-bugs-return-629307-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125772 invoked by alias); 15 Jan 2019 18:35: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 125725 invoked by uid 55); 15 Jan 2019 18:35:33 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88866] [9 Regression] g++.dg/cpp0x/variadic126.C fails with -std=c++2a
Date: Tue, 15 Jan 2019 18:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88866-4-fjd2GVcNbm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02116.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88866
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Tue Jan 15 18:35:01 2019
New Revision: 267944
URL: https://gcc.gnu.org/viewcvs?rev=267944&root=gcc&view=rev
Log:
PR c++/88866
* g++.dg/cpp0x/variadic126.C: Tweak dg-error.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/cpp0x/variadic126.C
>From gcc-bugs-return-629308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:37:48 2019
Return-Path: <gcc-bugs-return-629308-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129939 invoked by alias); 15 Jan 2019 18:37:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129885 invoked by uid 48); 15 Jan 2019 18:37:44 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88866] [9 Regression] g++.dg/cpp0x/variadic126.C fails with -std=c++2a
Date: Tue, 15 Jan 2019 18:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88866-4-facS9XFnRq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02117.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88866
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:39:06 2019
Return-Path: <gcc-bugs-return-629309-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 744 invoked by alias); 15 Jan 2019 18:39: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 674 invoked by uid 48); 15 Jan 2019 18:39:02 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88868] New: [SSE] pshufb can be omitted for a specific pattern
Date: Tue, 15 Jan 2019 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wojciech_mula at poczta dot onet.pl
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02118.txt.bz2
Content-length: 1434
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88868
Bug ID: 88868
Summary: [SSE] pshufb can be omitted for a specific pattern
Product: gcc
Version: 8.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: wojciech_mula at poczta dot onet.pl
Target Milestone: ---
SSSE3 instruction PSHUFB (and the AVX2 counterpart VPSHUFB) acts as a
no-operation
when its argument is a sequence 0..15. Such invocation does not alter shuffled
register, thus PSHUFB can be safely omitted
BTW, clang does this optimization, but ICC doesn't.
---pshufb.c---
#include <immintrin.h>
__m128i shuffle(__m128i x) {
const __m128i noop = _mm_setr_epi8(0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15);
return _mm_shuffle_epi8(x, noop);
}
---eof---
$ gcc --version
gcc (Debian 8.2.0-13) 8.2.0
$ gcc -O3 -march=skylake -S pshufb.c
$ cat pshufb.s
shuffle:
vpshufb .LC0(%rip), %xmm0, %xmm0
ret
.LC0:
.byte 0
.byte 1
.byte 2
.byte 3
.byte 4
.byte 5
.byte 6
.byte 7
.byte 8
.byte 9
.byte 10
.byte 11
.byte 12
.byte 13
.byte 14
.byte 15
An expected output:
shuffle:
ret
>From gcc-bugs-return-629310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:46:50 2019
Return-Path: <gcc-bugs-return-629310-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100956 invoked by alias); 15 Jan 2019 18:46: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 96327 invoked by uid 48); 15 Jan 2019 18:46:45 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88312] [9 regression] Mishandled explicitly provided parameter pack
Date: Tue, 15 Jan 2019 18:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88312-4-Aqp9h5r6Hc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88312-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02119.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88312
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:49:26 2019
Return-Path: <gcc-bugs-return-629311-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72699 invoked by alias); 15 Jan 2019 18:49: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 72210 invoked by uid 48); 15 Jan 2019 18:49:01 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88795] ICE on class-template argument deduction if non-type parameter has indirection
Date: Tue, 15 Jan 2019 18:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88795-4-PBOO96Ayma@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02120.txt.bz2
Content-length: 198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88795
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Candidate patch:
https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00865.html
>From gcc-bugs-return-629312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:56:04 2019
Return-Path: <gcc-bugs-return-629312-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98997 invoked by alias); 15 Jan 2019 18:56: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 98888 invoked by uid 48); 15 Jan 2019 18:55:59 -0000
From: "levon at movementarian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88867] -Waggressive-loop-optimizations doesn't warn when -faggressive-loop-optimizations is in play
Date: Tue, 15 Jan 2019 18:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: levon at movementarian 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-88867-4-3yFcRZOEac@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02121.txt.bz2
Content-length: 184
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88867
--- Comment #2 from John Levon <levon at movementarian dot org> ---
There is no Address Sanitizer in our kernel, bootloaders etc.
>From gcc-bugs-return-629313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 18:57:56 2019
Return-Path: <gcc-bugs-return-629313-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106398 invoked by alias); 15 Jan 2019 18:57: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 106352 invoked by uid 48); 15 Jan 2019 18:57:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88867] -Waggressive-loop-optimizations doesn't warn when -faggressive-loop-optimizations is in play
Date: Tue, 15 Jan 2019 18:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88867-4-Gs1QfOyzZA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88867-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02122.txt.bz2
Content-length: 356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88867
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to John Levon from comment #2)
> There is no Address Sanitizer in our kernel, bootloaders etc.
There is support for asan in the Linux kernel and maybe others. Again security
is about auditing and not just about warnings.
>From gcc-bugs-return-629314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 19:03:16 2019
Return-Path: <gcc-bugs-return-629314-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119590 invoked by alias); 15 Jan 2019 19:03:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119494 invoked by uid 48); 15 Jan 2019 19:03:11 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Tue, 15 Jan 2019 19: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88861-4-XLS9xlHl6g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02123.txt.bz2
Content-length: 600
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
CC| |dmalcolm at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed (with target==ppc64le-redhat-linux)
>From gcc-bugs-return-629315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 19:21:23 2019
Return-Path: <gcc-bugs-return-629315-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126529 invoked by alias); 15 Jan 2019 19:21:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126398 invoked by uid 55); 15 Jan 2019 19:21:17 -0000
From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Tue, 15 Jan 2019 19:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: paul.richard.thomas at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88810-4-moVyA6jPob@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02124.txt.bz2
Content-length: 3567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
--- Comment #6 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Hi Steve and Thomas,
I plead guilty to creating confusing code... It developed step by step
and I didn't go back and consolidate it.
If you can simplify it and still obtain the same result, that would be great.
Cheers
Paul
On Tue, 15 Jan 2019 at 15:36, sgk at troutmask dot apl.washington.edu
<gcc-bugzilla@gcc.gnu.org> wrote:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
>
> --- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
> On Tue, Jan 15, 2019 at 12:39:13PM +0000, tkoenig at gcc dot gnu.org wrote:
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
> >
> > Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
> >
> > What |Removed |Added
> > ----------------------------------------------------------------------------
> > CC| |tkoenig at gcc dot gnu.org
> >
> > --- Comment #4 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> > As far as I can see, the duplicated code does not do anything bad,
> > and removing the duplicate also would not do anything bad.
> >
> > A patch removing the duplication is pre-approved, provided it
> > passes a regression test.
> >
>
> Are you sure it is duplicate code?
>
> Here, if reverse[m] == GFC_ENABLE_REVERSE and this_dep == GFC_DEP_BACKWARD,
> then reverse[m] is update to GFC_REVERSE_SET; otherwise it is left as-is
> which is GFC_ENABLE_REVERSE.
>
> /* Set reverse if backward dependence and not inhibited. */
> if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
> reverse[m] = (this_dep == GFC_DEP_BACKWARD) ?
> GFC_REVERSE_SET : reverse[m];
>
> Here, if reverse[m] was updated to GFC_REVERSE_SET, the first
> conditional fails and reverse[m] is left unchanged. However, if
> reverse[m] was left unchanged from above, it is then GFC_ENABLE_REVERSE.
> gfortran then checks this_dep == GFC_DEP_FORWARD and updates accordingly.
>
> /* Set forward if forward dependence and not inhibited. */
> if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
> reverse[m] = (this_dep == GFC_DEP_FORWARD) ?
> GFC_FORWARD_SET : reverse[m];
>
> The code is likely correct as-is, but confusing. Some would have
> written
>
> /* Set reverse if backward dependence and not inhibited. */
> if (reverse && reverse[m] == GFC_ENABLE_REVERSE
> && this_dep == GFC_DEP_BACKWARD)
> reverse[m] = GFC_REVERSE_SET;
>
> /* Set forward if forward dependence and not inhibited. */
> if (reverse && reverse[m] == GFC_ENABLE_REVERSE
> && this_dep == GFC_DEP_FORWARD)
> reverse[m] = GFC_FORWARD_SET;
>
> or
>
> if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
> {
> if (this_dep == GFC_DEP_BACKWARD)
> reverse[m] = GFC_REVERSE_SET;
> else if (this_dep == GFC_DEP_FORWARD)
> reverse[m] = GFC_FORWARD_SET;
> }
>
> If this_dep can only take on the values of GFC_REVERSE_SET and
> GFC_DEP_FORWARD, then the above can be collapsed to
>
> if (reverse && reverse[m] == GFC_ENABLE_REVERSE)
> reverse[m] = this_dep == GFC_DEP_BACKWARD
> ? GFC_REVERSE_SET : GFC_FORWARD_SET;
>
> Looks like this PR is a false positive.
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>From gcc-bugs-return-629316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 19:28:42 2019
Return-Path: <gcc-bugs-return-629316-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7411 invoked by alias); 15 Jan 2019 19: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 7220 invoked by uid 48); 15 Jan 2019 19:28:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88613] [9 Regression] ICE in size_binop_loc at fold-const.c:1900 since r267272
Date: Tue, 15 Jan 2019 19:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88613-4-LO5Lv14OC6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88613-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02125.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88613
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 19:31:17 2019
Return-Path: <gcc-bugs-return-629317-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16776 invoked by alias); 15 Jan 2019 19:31:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12502 invoked by uid 55); 15 Jan 2019 19:30:55 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88810] gcc/fortran/dependency.c:2200: possible cut'n'paste error ?
Date: Tue, 15 Jan 2019 19:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: minor
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88810-4-wTqUoUvNr0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02126.txt.bz2
Content-length: 615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88810
--- Comment #7 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Tue, Jan 15, 2019 at 07:21:16PM +0000, paul.richard.thomas at gmail dot com
wrote:
>
> Hi Steve and Thomas,
>
> I plead guilty to creating confusing code... It developed step
> by step and I didn't go back and consolidate it.
>
> If you can simplify it and still obtain the same result, that
> would be great.
>
Paul,
I'll take a closer look at the code later this week (unless
Thomas beats me). I doubt that this is the only confusing
code ever committed. :-)
>From gcc-bugs-return-629318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 19:38:07 2019
Return-Path: <gcc-bugs-return-629318-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26089 invoked by alias); 15 Jan 2019 19:38:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25978 invoked by uid 48); 15 Jan 2019 19:38:03 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Tue, 15 Jan 2019 19:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc assigned_to
Message-ID: <bug-81849-4-RvNmaKiQIY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02127.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |kargl at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |kargl at gcc dot gnu.org
>From gcc-bugs-return-629319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:05:32 2019
Return-Path: <gcc-bugs-return-629319-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102614 invoked by alias); 15 Jan 2019 20:05:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102504 invoked by uid 48); 15 Jan 2019 20:05:26 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88055] ICE in extract_insn, at recog.c:2305 on ppc64le
Date: Tue, 15 Jan 2019 20:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88055-4-qFRueqAlEX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88055-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88055-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02128.txt.bz2
Content-length: 187
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88055
--- Comment #7 from Segher Boessenkool <segher at gcc dot gnu.org> ---
*** Bug 88863 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-629320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:05:33 2019
Return-Path: <gcc-bugs-return-629320-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102670 invoked by alias); 15 Jan 2019 20:05:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102479 invoked by uid 48); 15 Jan 2019 20:05:25 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88863] ICE in extract_insn, at recog.c:2305
Date: Tue, 15 Jan 2019 20:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88863-4-iGMWWaxOd5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02129.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88863
Segher Boessenkool <segher at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Segher Boessenkool <segher at gcc dot gnu.org> ---
dup.
*** This bug has been marked as a duplicate of bug 88055 ***
>From gcc-bugs-return-629321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:18:17 2019
Return-Path: <gcc-bugs-return-629321-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13187 invoked by alias); 15 Jan 2019 20:18: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 12293 invoked by uid 55); 15 Jan 2019 20:18:09 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Tue, 15 Jan 2019 20:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81849-4-JL8WRUeorQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02130.txt.bz2
Content-length: 736
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
--- Comment #4 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Tue Jan 15 20:17:35 2019
New Revision: 267948
URL: https://gcc.gnu.org/viewcvs?rev=267948&root=gcc&view=rev
Log:
2019-01-15 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/81849
* resolve.c (resolve_symbol): Host associated varaibles can appear
in the specification statement of a RESULT array.
2019-01-15 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/81849
* gfortran.dg/pr81849.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr81849.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:19:17 2019
Return-Path: <gcc-bugs-return-629322-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15748 invoked by alias); 15 Jan 2019 20:19:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15608 invoked by uid 48); 15 Jan 2019 20:19:10 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88868] [SSE] pshufb can be omitted for a specific pattern
Date: Tue, 15 Jan 2019 20:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-88868-4-OWvbGFvDKq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88868-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88868-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02131.txt.bz2
Content-length: 687
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88868
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
Component|tree-optimization |target
Ever confirmed|0 |1
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
When the second argument is constant, I think we should turn _mm_shuffle_epi8
into a __builtin_shuffle.
>From gcc-bugs-return-629323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:32:39 2019
Return-Path: <gcc-bugs-return-629323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99411 invoked by alias); 15 Jan 2019 20:32:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99323 invoked by uid 55); 15 Jan 2019 20:32:32 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] [7/8 Regression] GCC thinks that translation unit does not contain a definition of inline function.
Date: Tue, 15 Jan 2019 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88726-4-Gfin79H1u0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02132.txt.bz2
Content-length: 2575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
--- Comment #3 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Tue Jan 15 20:32:00 2019
New Revision: 267949
URL: https://gcc.gnu.org/viewcvs?rev=267949&root=gcc&view=rev
Log:
Fix diagnostics for never-defined inline and nested functions (PR c/88720, PR
c/88726).
Bugs 88720 and 88726 report issues where a function is declared inline
in an inner scope, resulting in spurious diagnostics about it being
declared but never defined when that scope is left (possibly in some
cases also wrongly referring to the function as a nested function).
These are regressions that were introduced with the support for C99
inline semantics in 4.3 (they don't appear with 4.2; it's possible
some aspects of the bugs might have been introduced later than 4.3).
For the case of functions being wrongly referred to as nested,
DECL_EXTERNAL was not the right condition for a function being
non-nested; TREE_PUBLIC is appropriate for the case of non-nested
functions with external linkage, while !b->nested means this is the
outermost scope in which the function was declared and so avoids
catching the case of a file-scope static being redeclared inline
inside a function.
For the non-nested, external-linkage case, the code attempts to avoid
duplicate diagnostics by diagnosing only when scope != external_scope,
but actually scope == external_scope is more appropriate, as it's only
when the file and external scopes are popped that the code can
actually tell whether a function ended up being defined, and all such
functions will appear in the (GCC-internal) external scope.
Bootstrapped with no regressions on x86_64-pc-linux-gnu.
gcc/c:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* c-decl.c (pop_scope): Use TREE_PUBLIC and b->nested to determine
whether a function is nested, not DECL_EXTERNAL. Diagnose inline
functions declared but never defined only for external scope, not
for other scopes.
gcc/testsuite:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* gcc.dg/inline-40.c, gcc.dg/inline-41.c: New tests.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/inline-40.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/inline-41.c
Modified:
branches/gcc-8-branch/gcc/c/ChangeLog
branches/gcc-8-branch/gcc/c/c-decl.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:32:39 2019
Return-Path: <gcc-bugs-return-629324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99421 invoked by alias); 15 Jan 2019 20:32: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 99326 invoked by uid 55); 15 Jan 2019 20:32:32 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] [7/8 Regression] Strange error message about nested function declared but not defined when using inline.
Date: Tue, 15 Jan 2019 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88720-4-i8f5rIBcxp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02133.txt.bz2
Content-length: 2575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
--- Comment #3 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Tue Jan 15 20:32:00 2019
New Revision: 267949
URL: https://gcc.gnu.org/viewcvs?rev=267949&root=gcc&view=rev
Log:
Fix diagnostics for never-defined inline and nested functions (PR c/88720, PR
c/88726).
Bugs 88720 and 88726 report issues where a function is declared inline
in an inner scope, resulting in spurious diagnostics about it being
declared but never defined when that scope is left (possibly in some
cases also wrongly referring to the function as a nested function).
These are regressions that were introduced with the support for C99
inline semantics in 4.3 (they don't appear with 4.2; it's possible
some aspects of the bugs might have been introduced later than 4.3).
For the case of functions being wrongly referred to as nested,
DECL_EXTERNAL was not the right condition for a function being
non-nested; TREE_PUBLIC is appropriate for the case of non-nested
functions with external linkage, while !b->nested means this is the
outermost scope in which the function was declared and so avoids
catching the case of a file-scope static being redeclared inline
inside a function.
For the non-nested, external-linkage case, the code attempts to avoid
duplicate diagnostics by diagnosing only when scope != external_scope,
but actually scope == external_scope is more appropriate, as it's only
when the file and external scopes are popped that the code can
actually tell whether a function ended up being defined, and all such
functions will appear in the (GCC-internal) external scope.
Bootstrapped with no regressions on x86_64-pc-linux-gnu.
gcc/c:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* c-decl.c (pop_scope): Use TREE_PUBLIC and b->nested to determine
whether a function is nested, not DECL_EXTERNAL. Diagnose inline
functions declared but never defined only for external scope, not
for other scopes.
gcc/testsuite:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* gcc.dg/inline-40.c, gcc.dg/inline-41.c: New tests.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/inline-40.c
branches/gcc-8-branch/gcc/testsuite/gcc.dg/inline-41.c
Modified:
branches/gcc-8-branch/gcc/c/ChangeLog
branches/gcc-8-branch/gcc/c/c-decl.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:34:32 2019
Return-Path: <gcc-bugs-return-629326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104658 invoked by alias); 15 Jan 2019 20:34: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 104609 invoked by uid 48); 15 Jan 2019 20:34:28 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] [7 Regression] GCC thinks that translation unit does not contain a definition of inline function.
Date: Tue, 15 Jan 2019 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88726-4-Hvme6MtMT0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02135.txt.bz2
Content-length: 682
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|8.3 |7.5
Summary|[7/8 Regression] GCC thinks |[7 Regression] GCC thinks
|that translation unit does |that translation unit does
|not contain a definition of |not contain a definition of
|inline function. |inline function.
--- Comment #4 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Also now fixed for GCC 8.3.
>From gcc-bugs-return-629325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:34:00 2019
Return-Path: <gcc-bugs-return-629325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103567 invoked by alias); 15 Jan 2019 20:34:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103523 invoked by uid 48); 15 Jan 2019 20:33:55 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] [7 Regression] Strange error message about nested function declared but not defined when using inline.
Date: Tue, 15 Jan 2019 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88720-4-zNBbSKtRGO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02134.txt.bz2
Content-length: 687
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|8.3 |7.5
Summary|[7/8 Regression] Strange |[7 Regression] Strange
|error message about nested |error message about nested
|function declared but not |function declared but not
|defined when using inline. |defined when using inline.
--- Comment #4 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Also now fixed for GCC 8.3.
>From gcc-bugs-return-629327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:41:20 2019
Return-Path: <gcc-bugs-return-629327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37482 invoked by alias); 15 Jan 2019 20:41: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 37402 invoked by uid 48); 15 Jan 2019 20:41:16 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 20:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-fvsyR8QTkO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02136.txt.bz2
Content-length: 405
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #17 from Segher Boessenkool <segher at gcc dot gnu.org> ---
It's not obvious to me what machine code is wrong here. Maybe it is obvious
to someone who is better at Arm code than I am?
Does it all work if you use -fno-if-conversion2 though? Or, what other
later pass causes it? Or is the RTL code immediately after combine already
bad?
>From gcc-bugs-return-629328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:44:18 2019
Return-Path: <gcc-bugs-return-629328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41317 invoked by alias); 15 Jan 2019 20: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 41212 invoked by uid 48); 15 Jan 2019 20:44:06 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] [8/9 Regression] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 20:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-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 short_desc everconfirmed
Message-ID: <bug-88859-4-EvdoRC326l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02137.txt.bz2
Content-length: 804
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-15
Summary|FAIL: |[8/9 Regression] FAIL:
|experimental/string_view/op |experimental/string_view/op
|erators/wchar_t/2.cc |erators/wchar_t/2.cc
|execution test |execution test
Ever confirmed|0 |1
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
This was triggered by r254832. The bug may be latent before.
>From gcc-bugs-return-629329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:46:38 2019
Return-Path: <gcc-bugs-return-629329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49846 invoked by alias); 15 Jan 2019 20:46:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49747 invoked by uid 55); 15 Jan 2019 20:46:34 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Tue, 15 Jan 2019 20:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81849-4-krybxzWC5j@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02138.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
--- Comment #5 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Tue Jan 15 20:45:43 2019
New Revision: 267951
URL: https://gcc.gnu.org/viewcvs?rev=267951&root=gcc&view=rev
Log:
2019-01-15 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/81849
* resolve.c (resolve_symbol): Host associated varaibles can appear
in the specification statement of a RESULT array.
2019-01-15 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/81849
* gfortran.dg/pr81849.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/pr81849.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/resolve.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:53:23 2019
Return-Path: <gcc-bugs-return-629330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56345 invoked by alias); 15 Jan 2019 20:53:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56207 invoked by uid 48); 15 Jan 2019 20:53:17 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Tue, 15 Jan 2019 20:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88861-4-OmfEHLOzTb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02139.txt.bz2
Content-length: 2809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
--- Comment #3 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Assertion fails in dom_info::calc_dfs_tree:
457 /* This aborts e.g. when there is _no_ path from ENTRY to EXIT at
all. */
458 gcc_assert (m_nodes == (unsigned int) m_n_basic_blocks - 1);
(gdb) p m_nodes
$8 = 9
(gdb) p m_n_basic_blocks
$9 = 11
Block 9 in .263r.ud_dce has one in-edge from block 6 (insn 29), and no out-edge
Block 9 in .264r.combine has no in-edges or out-edges
Within .263r.ud_dce:
(note 25 69 26 6 [bb 6] NOTE_INSN_BASIC_BLOCK)
(insn 26 25 28 6 (set (reg/f:DI 142)
(mem/u/c:DI (unspec:DI [
(symbol_ref/u:DI ("*.LC1") [flags 0x2])
(reg:DI 2 2)
] UNSPEC_TOCREL) [3 S8 A8])) "/tmp/test.c":7:21 608
{*movdi_internal64}
(expr_list:REG_EQUAL (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(nil)))
(insn 28 26 29 6 (set (reg:SI 135 [ i ])
(mem/c:SI (plus:DI (reg/f:DI 142)
(const_int 4 [0x4])) [1 i+0 S4 A32])) "/tmp/test.c":7:21 494
{*movsi_internal1}
(expr_list:REG_EQUAL (mem/c:SI (const:DI (plus:DI (symbol_ref:DI
("*.LANCHOR1") [flags 0x182])
(const_int 4 [0x4]))) [1 i+0 S4 A32])
(nil)))
(insn 29 28 30 6 (set (mem:SI (plus:DI (reg/f:DI 142)
(const_int 4 [0x4])) [1 s+4 S4 A32])
(reg:SI 135 [ i ])) "/tmp/test.c":7:21 494 {*movsi_internal1}
(expr_list:REG_DEAD (reg:SI 135 [ i ])
(expr_list:REG_EH_REGION (const_int 1 [0x1])
(nil))))
...but within .264r.combine:
[...snip...]
allowing combination of insns 28 and 29
original costs 4 + 4 = 8
replacement cost 0
deferring deletion of insn with uid = 28.
modifying insn i3 29: [r142:DI+0x4]=[r142:DI+0x4]
REG_EH_REGION 0x1
deferring rescan insn with uid = 29.
Can't combine i2 into i3
Can't combine i2 into i3
Can't combine i2 into i3
Can't combine i2 into i3
Can't combine i2 into i3
Can't combine i2 into i3
Can't combine i2 into i3
Can't combine i2 into i3
deleting noop move 29
deferring deletion of insn with uid = 29.
starting the processing of deferred insns
rescanning insn with uid = 23.
ending the processing of deferred insns
[...snip...]
(note 25 69 26 6 [bb 6] NOTE_INSN_BASIC_BLOCK)
(insn 26 25 28 6 (set (reg/f:DI 142)
(mem/u/c:DI (unspec:DI [
(symbol_ref/u:DI ("*.LC1") [flags 0x2])
(reg:DI 2 2)
] UNSPEC_TOCREL) [3 S8 A8])) "/tmp/test.c":7:21 608
{*movdi_internal64}
(expr_list:REG_EQUAL (symbol_ref:DI ("*.LANCHOR1") [flags 0x182])
(nil)))
(note 28 26 30 6 NOTE_INSN_DELETED)
which, if I'm reading it right, seems to have deleted the usage of EH region 1,
and has left block 9 orphaned.
>From gcc-bugs-return-629331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:53:56 2019
Return-Path: <gcc-bugs-return-629331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57272 invoked by alias); 15 Jan 2019 20:53:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57170 invoked by uid 55); 15 Jan 2019 20:53:45 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Tue, 15 Jan 2019 20:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81849-4-xKamlcnarS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02140.txt.bz2
Content-length: 800
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
--- Comment #6 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Tue Jan 15 20:53:13 2019
New Revision: 267952
URL: https://gcc.gnu.org/viewcvs?rev=267952&root=gcc&view=rev
Log:
2019-01-15 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/81849
* resolve.c (resolve_symbol): Host associated varaibles can appear
in the specification statement of a RESULT array.
2019-01-15 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/81849
* gfortran.dg/pr81849.f90: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/pr81849.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/resolve.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 20:54:49 2019
Return-Path: <gcc-bugs-return-629332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58573 invoked by alias); 15 Jan 2019 20:54: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 58496 invoked by uid 48); 15 Jan 2019 20:54:43 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Tue, 15 Jan 2019 20:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-81849-4-JIVKCRyn1e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02141.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |7.5
--- Comment #7 from kargl at gcc dot gnu.org ---
Fixed on trunk, branch-8, and branch-7. Closing.
>From gcc-bugs-return-629333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 21:25:16 2019
Return-Path: <gcc-bugs-return-629333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124202 invoked by alias); 15 Jan 2019 21:25:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120753 invoked by uid 48); 15 Jan 2019 21:25:08 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] [8/9 Regression] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 21:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88859-4-B33ZwaeRAV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02142.txt.bz2
Content-length: 1380
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
[hjl@gnu-skx-1 pr88859]$ cat x.cc
#include <experimental/string_view>
#define VERIFY(fn) if (!(fn)) __builtin_abort();
int
main()
{
std::experimental::wstring_view str_0(L"costa rica");
std::experimental::wstring_view str_1(L"costa marbella");
std::experimental::wstring_view str_2(L"cost");
std::experimental::wstring_view str_3(L"costa ricans");
std::experimental::wstring_view str_4;
str_4 = str_0;
VERIFY( !(str_0 == str_1) );
VERIFY( !(str_0 == str_2) );
VERIFY( !(str_0 == str_3) );
VERIFY( !(str_1 == str_0) );
VERIFY( !(str_2 == str_0) );
VERIFY( !(str_3 == str_0) );
VERIFY( str_4 == str_0 );
VERIFY( str_0 == str_4 );
VERIFY( !(str_0 == L"costa marbella") );
VERIFY( !(str_0 == L"cost") );
VERIFY( !(str_0 == L"costa ricans") );
VERIFY( !(L"cost" == str_0) );
VERIFY( !(L"costa ricans" == str_0) );
VERIFY( L"costa rica" == str_0 );
VERIFY( str_0 == L"costa rica" );
VERIFY( L"costa ricans" != str_0 );
VERIFY( !(L"costa rica" != str_0) );
return 0;
}
[hjl@gnu-skx-1 pr88859]$ make
g++ -O2 -mx32 -S x.cc
g++ -O2 -mx32 -o x x.s
./x
make: *** [Makefile:12: all] Segmentation fault
[hjl@gnu-skx-1 pr88859]$
>From gcc-bugs-return-629334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:03:47 2019
Return-Path: <gcc-bugs-return-629334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128521 invoked by alias); 15 Jan 2019 22:03: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 128399 invoked by uid 48); 15 Jan 2019 22:03:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 22:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-ePqwN8RfGg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02143.txt.bz2
Content-length: 1624
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #18 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
So, I've hacked up assembly version which contained 2 versions of this function
(good and bad) plus a wrapper function:
void *
vn_reference_lookup_2b (ao_ref *op, tree vuse, unsigned int cnt, void *vr_);
void *
vn_reference_lookup_2c (ao_ref *op, tree vuse, unsigned int cnt, void *vr_);
void *
vn_reference_lookup_2a (ao_ref *op, tree vuse, unsigned int cnt, void *vr_)
{
vn_reference_t vr = (vn_reference_t)vr_;
vn_reference_s a = *vr;
void *r1 = vn_reference_lookup_2a (op, vuse, cnt, vr_);
vn_reference_s b = *vr;
*vr = a;
void *r2 = vn_reference_lookup_2b (op, vuse, cnt, vr_);
if (r1 != r2 || __builtin_memcmp (vr, &b, sizeof (b)))
fancy_abort (__FILE__, __LINE__, __FUNCTION__);
return r1;
}
adjusted in the assembly, so that it is actually that vn_reference_lookup_2
that calls the good and bad versions.
This ICEs on the second call to vn_reference_lookup_2.
vuse is .MEM_59, so is vr->vuse on entry and vr->hashcode is 0xd16d45ea.
The
if (vr->vuse)
vr->hashcode = vr->hashcode - (vr->vuse)->base.u.version;
is performed correctly in both, changing vr->hashcode to 0xd16d45af (i.e.
subtracting 59), next vr->vuse is updated to .MEM_48.
The problem is with the
if (vr->vuse)
vr->hashcode = vr->hashcode + (vr->vuse)->base.u.version;
in the good version it does what the source tells it to do, adds 48, making
vr->hashcode 0xd16d45df and calling find_slot_with_hash with that value.
But in the bad version, we actually store 0xd16d45ea again.
>From gcc-bugs-return-629335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:17:09 2019
Return-Path: <gcc-bugs-return-629335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31988 invoked by alias); 15 Jan 2019 22:17: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 31907 invoked by uid 48); 15 Jan 2019 22:17:02 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Tue, 15 Jan 2019 22:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88815-4-JuuJDJEp9e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02144.txt.bz2
Content-length: 525
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
I think the problem is that we're not detecting narrowing conversions in
decltype; which is basically a dup of PR 78244 assigned to... me.
>From gcc-bugs-return-629336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:19:36 2019
Return-Path: <gcc-bugs-return-629336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35961 invoked by alias); 15 Jan 2019 22:19: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 35866 invoked by uid 55); 15 Jan 2019 22:19:29 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43072] unneeded temporary (s=s+f(a))
Date: Tue, 15 Jan 2019 22:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
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: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-43072-4-JQYRIne2NU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-43072-4@http.gcc.gnu.org/bugzilla/>
References: <bug-43072-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02145.txt.bz2
Content-length: 948
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43072
--- Comment #10 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Tue Jan 15 22:18:55 2019
New Revision: 267953
URL: https://gcc.gnu.org/viewcvs?rev=267953&root=gcc&view=rev
Log:
2019-01-15 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/43072
* resolve.c (resolve_array_ref): Add equal_length argument; set it
if the length of the substring equals that of the orignal
variable.
(resolve_ref): Remove the substring if it is equal in length to
the original variable, unless it is an EXPR_SUBSTRING).
2019-01-15 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/43072
* gfortran.dg/actual_array_substr_3.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/actual_array_substr_3.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/resolve.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:21:55 2019
Return-Path: <gcc-bugs-return-629338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40585 invoked by alias); 15 Jan 2019 22:21: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 40413 invoked by uid 48); 15 Jan 2019 22:21:51 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43136] Excess copy-in/copy-out with character argument
Date: Tue, 15 Jan 2019 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
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: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-43136-4-uhPmtlUDCr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02147.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43136
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Actually fixed in r267953, the original commit had the wrong PR number.
Closing.
>From gcc-bugs-return-629339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:21:56 2019
Return-Path: <gcc-bugs-return-629339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40682 invoked by alias); 15 Jan 2019 22:21:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40433 invoked by uid 48); 15 Jan 2019 22:21:52 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/19276] [meta-bug] CHARACTER related bugs in gfortran
Date: Tue, 15 Jan 2019 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.0.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-19276-4-wuHpteeAYX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-19276-4@http.gcc.gnu.org/bugzilla/>
References: <bug-19276-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02148.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19276
Bug 19276 depends on bug 43136, which changed state.
Bug 43136 Summary: Excess copy-in/copy-out with character argument
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43136
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-629337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:21:03 2019
Return-Path: <gcc-bugs-return-629337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39278 invoked by alias); 15 Jan 2019 22:21:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39201 invoked by uid 55); 15 Jan 2019 22:20:57 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/43136] Excess copy-in/copy-out with character argument
Date: Tue, 15 Jan 2019 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tkoenig at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-43136-4-Aozi7sJP41@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
References: <bug-43136-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02146.txt.bz2
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43136
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Author: tkoenig
Date: Tue Jan 15 22:20:26 2019
New Revision: 267954
URL: https://gcc.gnu.org/viewcvs?rev=267954&root=gcc&view=rev
Log:
2019-01-15 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/43136
* resolve.c (resolve_array_ref): Add equal_length argument; set it
if the length of the substring equals that of the orignal
variable.
(resolve_ref): Remove the substring if it is equal in length to
the original variable, unless it is an EXPR_SUBSTRING).
2019-01-15 Thomas Koenig <tkoenig@gcc.gnu.org>
PR fortran/43136
* gfortran.dg/actual_array_substr_3.f90: New test.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:25:56 2019
Return-Path: <gcc-bugs-return-629340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45731 invoked by alias); 15 Jan 2019 22:25: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 45647 invoked by uid 48); 15 Jan 2019 22:25:49 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88782] [8/9 Regression] Crash when mixing make_shared from gcc <= 8.2 with make_shared from gcc > 8.2
Date: Tue, 15 Jan 2019 22:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-88782-4-URPY6GaYnL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02149.txt.bz2
Content-length: 973
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88782
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9 Regression] Crash when |[8/9 Regression] Crash when
|mixing make_shared from gcc |mixing make_shared from gcc
|<= 8.2 with make_shared |<= 8.2 with make_shared
|from gcc >= 8.3 |from gcc > 8.2
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Romain Geissler from comment #0)
> The change introduced in r266380 makes newer gcc >= 8.3 and gcc 9
I'm changing the summary to say > 8.2 because there is no 8.3 release yet, so
claiming this affects 8.3 is misleading.
It affects the gcc-8-branch post r266380 which means 8.2.1 (20181122) and
later, but it's going to be fixed before the 8.3 release.
>From gcc-bugs-return-629341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:40:19 2019
Return-Path: <gcc-bugs-return-629341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81184 invoked by alias); 15 Jan 2019 22:40: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 81041 invoked by uid 48); 15 Jan 2019 22:40:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 22:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88714-4-FZFj26zM87@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02150.txt.bz2
Content-length: 4209
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ktkachov at gcc dot gnu.org,
| |ramana at gcc dot gnu.org,
| |rearnsha at gcc dot gnu.org
--- Comment #19 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
To me, this looks like buggy arm peephole2.
In *.compgotos pass we have:
(insn 96 95 97 18 (set (mem/f:SI (plus:SI (reg/v/f:SI 4 r4 [orig:137 vr_ ]
[137])
(const_int 12 [0xc])) [12 MEM[(struct vn_reference_s
*)vr__23(D)].vuse+0 S4 A32])
(reg/v/f:SI 12 ip [orig:135 vuse ] [135]))
"/tmp/tree-ssa-sccvn.ii":87248:12 650 {*arm_movsi_vfp}
(expr_list:REG_DEAD (reg/v/f:SI 12 ip [orig:135 vuse ] [135])
(expr_list:REG_DEAD (reg/v/f:SI 4 r4 [orig:137 vr_ ] [137])
(nil))))
(insn 97 96 98 18 (set (reg/f:SI 3 r3 [orig:118 _11 ] [118])
(mem/f:SI (plus:SI (reg/f:SI 1 r1 [orig:123 prephitmp_29 ] [123])
(const_int 12 [0xc])) [12 prephitmp_29->vuse+0 S4 A32]))
"/tmp/tree-ssa-sccvn.ii":87249:11 650 {*arm_movsi_vfp}
(nil))
(insn 98 97 99 18 (set (reg:SI 2 r2 [orig:120 _14 ] [120])
(mem:SI (plus:SI (reg/f:SI 1 r1 [orig:123 prephitmp_29 ] [123])
(const_int 8 [0x8])) [4 prephitmp_29->hashcode+0 S4 A32])) 650
{*arm_movsi_vfp}
(nil))
The first stmt is the vr->vuse = ... store from vr->vuse = vuse_ssa_val (vuse);
The next two stmts load vr->hashcode and vr->vuse, but unfortunately the GIMPLE
optimizers weren't able to figure out that
vr is equal to vr__23(D):
# _42 = PHI <iftmp.125_55(16), vuse_26(D)(7)>
# prephitmp_29 = PHI <pretmp_64(16), vr__23(D)(7)>
MEM[(struct vn_reference_s *)vr__23(D)].vuse = _42;
_11 = prephitmp_29->vuse;
pretmp_49 = prephitmp_29->hashcode;
at that point (note, vr is address taken variable).
Then comes peephole2 and does:
Splitting with gen_peephole2_11
scanning new insn with uid = 217.
deleting insn with uid = 98.
deleting insn with uid = 97.
verify found no changes in insn with uid = 217.
and constructs
(insn 96 95 217 18 (set (mem/f:SI (plus:SI (reg/v/f:SI 4 r4 [orig:137 vr_ ]
[137])
(const_int 12 [0xc])) [12 MEM[(struct vn_reference_s
*)vr__23(D)].vuse+0 S4 A32])
(reg/v/f:SI 12 ip [orig:135 vuse ] [135]))
"/tmp/tree-ssa-sccvn.ii":87248:12 650 {*arm_movsi_vfp}
(expr_list:REG_DEAD (reg/v/f:SI 12 ip [orig:135 vuse ] [135])
(expr_list:REG_DEAD (reg/v/f:SI 4 r4 [orig:137 vr_ ] [137])
(nil))))
(insn 217 96 99 18 (set (reg:DI 2 r2)
(mem:DI (plus:SI (reg/f:SI 1 r1 [orig:123 prephitmp_29 ] [123])
(const_int 8 [0x8])) [4 prephitmp_29->hashcode+0 S8 A32])) -1
(nil))
out of this. The insn 217 is a ldrd. The bug is that the DImode MEM uses the
same MEM_ALIAS_SET and same MEM_EXPR as
that of the SImode prephitmp_29->hashcode read, even when it now covers two
fields of the structure. So, either it needs to throw away MEM_EXPR and clear
MEM_ALIAS_SET, or find something conservatively correct covering both.
Finally, sched2 comes and swaps the two, because the (incorrect) aliasing info
makes alias.c believe it can swap the two:
(insn:TI 217 116 96 12 (set (reg:DI 2 r2)
(mem:DI (plus:SI (reg/f:SI 1 r1 [orig:123 prephitmp_29 ] [123])
(const_int 8 [0x8])) [4 prephitmp_29->hashcode+0 S8 A32])) 652
{*movdi_vfp}
(nil))
(insn:TI 96 217 109 12 (set (mem/f:SI (plus:SI (reg/v/f:SI 4 r4 [orig:137 vr_ ]
[137])
(const_int 12 [0xc])) [12 MEM[(struct vn_reference_s
*)vr__23(D)].vuse+0 S4 A32])
(reg/v/f:SI 12 ip [orig:135 vuse ] [135]))
"/tmp/tree-ssa-sccvn.ii":87248:12 650 {*arm_movsi_vfp}
(expr_list:REG_DEAD (reg/v/f:SI 12 ip [orig:135 vuse ] [135])
(expr_list:REG_DEAD (reg/v/f:SI 4 r4 [orig:137 vr_ ] [137])
(nil))))
and thus, instead of using the new vr->vuse value for the vr->hashcode
computation we use the old one.
>From gcc-bugs-return-629342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 22:51:22 2019
Return-Path: <gcc-bugs-return-629342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108068 invoked by alias); 15 Jan 2019 22:51:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 107888 invoked by uid 48); 15 Jan 2019 22:51:18 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 22:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-MAbj5Sro4e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02151.txt.bz2
Content-length: 243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #20 from ktkachov at gcc dot gnu.org ---
Thanks for investigating this.
At an initial glance, I guess this is something gen_operands_ldrd_strd in
config/arm/arm.c should handle
>From gcc-bugs-return-629343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:08:39 2019
Return-Path: <gcc-bugs-return-629343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124253 invoked by alias); 15 Jan 2019 23:08:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 124150 invoked by uid 48); 15 Jan 2019 23:08:32 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] [8/9 Regression] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 23:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88859-4-GMlSIcl0Fz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02152.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
Breakpoint 1, std::char_traits<wchar_t>::compare (__n=<optimized out>,
__s2=<optimized out>, __s1=<optimized out>)
at
/export/build/gnu/tools-build/gcc-x32-debug-8/build-x86_64-linux/x86_64-pc-linux-gnu/x32/libstdc++-v3/include/bits/char_traits.h:420
420 return wmemcmp(__s1, __s2, __n);
(gdb) c
Continuing.
Breakpoint 2, __wmemcmp_avx2_movbe ()
at ../sysdeps/x86_64/multiarch/memcmp-avx2-movbe.S:61
61 shl $2, %rdx
$7 = 18049617241309194
(gdb) p/x $rdx
$8 = 0x4020080000000a
(gdb)
18049617241309194 is a bogus length.
>From gcc-bugs-return-629344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:08:39 2019
Return-Path: <gcc-bugs-return-629344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124265 invoked by alias); 15 Jan 2019 23:08: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 124196 invoked by uid 48); 15 Jan 2019 23:08:35 -0000
From: "daniel at hebirobotics dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88869] New: ICE (Segmentation Fault) when using lambda
Date: Tue, 15 Jan 2019 23:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daniel at hebirobotics 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-88869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02153.txt.bz2
Content-length: 1251
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88869
Bug ID: 88869
Summary: ICE (Segmentation Fault) when using lambda
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel at hebirobotics dot com
Target Milestone: ---
I found a bug when trying to pass a lambda to a structure which holds the
lambda along with some additional state. I haven't had time to simply my repro
to see where the code begins to "break," but a segmentation fault is clearly an
indication of something going wrong within the compiler. Clang seems to compile
the godbolt link which GCC struggles with below.
While the version I specified is `8.2.1`, I am not entirely sure which versions
this can be reproduced on. I originally found it on my Fedora 29 machine
running `gcc (GCC) 8.2.1 20181215 (Red Hat 8.2.1-6)`, but it also appears to be
reproducible on the `gcc (trunk)` version from Matt Godbolt's website
(gcc.godbolt.org) as of 15 January 2019.
I have attached a simplified version of the code I found this bug in here:
https://gcc.godbolt.org/z/4LQb4j
>From gcc-bugs-return-629345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:11:07 2019
Return-Path: <gcc-bugs-return-629345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127965 invoked by alias); 15 Jan 2019 23: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 127839 invoked by uid 48); 15 Jan 2019 23:11:02 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 23:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-8VUwZaeH92@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02154.txt.bz2
Content-length: 1902
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #21 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Short testcase -O2 -mtune=cortex-a9 -mfloat-abi=hard -mfpu=vfpv3-d16
-mtls-dialect=gnu -marm -march=armv7-a+fp:
struct S { int a, b, c; int *d; };
void bar (int, int, int, int);
void
foo (struct S *x, struct S *y, int *z)
{
x->d = z;
if (y->d)
y->c = y->c + y->d[0];
bar (0, 0, y->c, 0);
}
This one actually isn't miscompiled (dunno how to convince sched2 that it wants
to schedule the ldrd before the x->d store), but if you put a breakpoint on
true_dependence_1 if mem->mode == E_DImode || x->mode == E_DImode, then you
should be able to see that it considers swapping those and doesn't find
aliasing reason not to.
What the peephole2 does is similar to what e.g. store-merging does, which for
alias sets does:
if (!n1->alias_set
|| alias_ptr_types_compatible_p (n1->alias_set, n2->alias_set))
n->alias_set = n1->alias_set;
else
n->alias_set = ptr_type_node;
i.e. uses alias set 0 if they aren't compatible.
Another possibility would be to use an alternate pattern for the ldrd when it
is matched by such a peephole2, instead of presenting it as a DImode read
present it as 2 SImode reads, so (set r2 (mem:SI ...)) (set r3 (mem:SI ...)).
That way you could use the original MEM_ALIAS_SET and MEM_EXPRs. Seems arm.md
even has similar patterns like *thumb2_ldrd_base. So, in ldrdstrd.md do a
similar thing for TARGET_ARM as for TARGET_THUMB2, just the TARGET_ARM patterns
would need to also verify the two registers are consecutive (can be done in the
insn condition) and make sure it handles any cases where the two memory
addresses are 4 bytes appart (again, can be done in the insn condition).
I think this would be better than to drop alias set to 0, which then can
prevent optimal scheduling etc.
>From gcc-bugs-return-629346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:17:34 2019
Return-Path: <gcc-bugs-return-629346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11343 invoked by alias); 15 Jan 2019 23:17: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 11276 invoked by uid 48); 15 Jan 2019 23:17:26 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] [8/9 Regression] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Tue, 15 Jan 2019 23:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88859-4-ggzHFoptH4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02155.txt.bz2
Content-length: 631
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
__y is passed in %rsi:
(gdb) p &__y
Address requested for identifier "__y" which is in register $rsi
(gdb) p __y
$24 = {static npos = <optimized out>, _M_len = 10,
_M_str = 0x402008 L"costa rica"}
(gdb) p/x $rsi
$25 = 0x4020080000000a
(gdb)
0x00401690 <+32>: mov %rdi,%rdx
^^^^^^^^^^^ This should be "mov %edi, %edx".
0x00401693 <+35>: shr $0x20,%rsi
0x00401697 <+39>: shr $0x20,%rdi
0x0040169b <+43>: callq 0x401050 <wmemcmp@plt>
>From gcc-bugs-return-629347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:20:59 2019
Return-Path: <gcc-bugs-return-629347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19150 invoked by alias); 15 Jan 2019 23:20: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 19063 invoked by uid 48); 15 Jan 2019 23:20:53 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77960] ICE in gfc_conv_ss_startstride, at fortran/trans-array.c:3966
Date: Tue, 15 Jan 2019 23:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc assigned_to
Message-ID: <bug-77960-4-p44IRGG65d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02156.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77960
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |kargl at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |kargl at gcc dot gnu.org
>From gcc-bugs-return-629348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:29:52 2019
Return-Path: <gcc-bugs-return-629348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15370 invoked by alias); 15 Jan 2019 23:29: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 15317 invoked by uid 55); 15 Jan 2019 23:29:47 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88795] ICE on class-template argument deduction if non-type parameter has indirection
Date: Tue, 15 Jan 2019 23:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88795-4-aXBX9Yi7I7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02157.txt.bz2
Content-length: 1420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88795
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Author: dmalcolm
Date: Tue Jan 15 23:29:15 2019
New Revision: 267957
URL: https://gcc.gnu.org/viewcvs?rev=267957&root=gcc&view=rev
Log:
Fix ICE on class-template argument deduction (PR c++/88795)
PR c++/88795 reports an ICE building a function_type for a deduction guide
when the substitution into the function signature fails, due to an
error_mark_node being returned from tsubst_arg_types but not being checked
for. This error_mark_node gets used as the TYPE_ARG_TYPES, leading to
ICEs in various places that assume this is a TREE_LIST.
This patch checks the result of tsubst_arg_types and propagates the failure
if it returns error_mark_node. It also adds an assertion to
build_function_type, to fail faster if passed in error_mark_node.
gcc/cp/ChangeLog:
PR c++/88795
* pt.c (build_deduction_guide): Bail out if tsubst_arg_types
fails.
gcc/testsuite/ChangeLog:
PR c++/88795
* g++.dg/template/pr88795.C: New test.
gcc/ChangeLog:
PR c++/88795
* tree.c (build_function_type): Assert that arg_types is not
error_mark_node.
Added:
trunk/gcc/testsuite/g++.dg/template/pr88795.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/pt.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree.c
>From gcc-bugs-return-629349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:31:27 2019
Return-Path: <gcc-bugs-return-629349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17430 invoked by alias); 15 Jan 2019 23:31:27 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17345 invoked by uid 48); 15 Jan 2019 23:31:23 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88795] ICE on class-template argument deduction if non-type parameter has indirection
Date: Tue, 15 Jan 2019 23:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88795-4-vDiyg0x1vL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88795-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02158.txt.bz2
Content-length: 159
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88795
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed on trunk by r267957.
>From gcc-bugs-return-629350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:32:35 2019
Return-Path: <gcc-bugs-return-629350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19514 invoked by alias); 15 Jan 2019 23:32:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 19419 invoked by uid 48); 15 Jan 2019 23:32:31 -0000
From: "tromey at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80635] std::optional and bogus -Wmaybe-uninitialized warning
Date: Tue, 15 Jan 2019 23:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tromey at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80635-4-wHIGypmjMW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80635-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02159.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80635
--- Comment #14 from Tom Tromey <tromey at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #8)
> Something like __builtin_unreachable() to say "trust me" would be nice, but
> I can't think how to do it.
How about an attribute that can be attached to the member?
Then tree-ssa-uninit could check for this and suppress the warning.
>From gcc-bugs-return-629351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:44:55 2019
Return-Path: <gcc-bugs-return-629351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 131028 invoked by alias); 15 Jan 2019 23:44:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 130930 invoked by uid 48); 15 Jan 2019 23:44:50 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Tue, 15 Jan 2019 23:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-OU3aJaXjRl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02160.txt.bz2
Content-length: 1146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #22 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Self-contained testcase which actually fails because of this bug, even e.g.
when compiled with -O0 and gcc 8.2.1. That doesn't mean this bug shouldn't be
P1, because preventing bootstrap on a primary target is extremely severe.
struct S { int a, b, c; int *d; };
struct T { int *e, *f, *g; } *t = 0;
int *o = 0;
__attribute__((noipa))
void bar (int *x, int y, int z, int w)
{
if (w == -1)
{
if (x != 0 || y != 0 || z != 0)
__builtin_abort ();
}
else if (w != 0 || x != t->g || y != 0 || z != 12)
__builtin_abort ();
}
__attribute__((noipa)) void
foo (struct S *x, struct S *y, int *z, int w)
{
*o = w;
if (w)
bar (0, 0, 0, -1);
x->d = z;
if (y->d)
y->c = y->c + y->d[0];
bar (t->g, 0, y->c, 0);
}
int
main ()
{
int a[4] = { 8, 9, 10, 11 };
struct S s = { 1, 2, 3, &a[0] };
struct T u = { 0, 0, &a[3] };
o = &a[2];
t = &u;
foo (&s, &s, &a[1], 5);
if (s.c != 12 || s.d != &a[1])
__builtin_abort ();
return 0;
}
>From gcc-bugs-return-629352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Jan 15 23:49:56 2019
Return-Path: <gcc-bugs-return-629352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43799 invoked by alias); 15 Jan 2019 23:49: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 43734 invoked by uid 48); 15 Jan 2019 23:49:52 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/86308] [7/8/9 Regression] ICE in verify_gimple calling an invalid index() declaration
Date: Tue, 15 Jan 2019 23:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86308-4-McCa4wwu2m@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86308-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86308-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02161.txt.bz2
Content-length: 210
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86308
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Looks like I dropped the ball on this. Let me see if I can still get it done
for GCC 9.
>From gcc-bugs-return-629353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 00:59:44 2019
Return-Path: <gcc-bugs-return-629353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92595 invoked by alias); 16 Jan 2019 00:59: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 92474 invoked by uid 48); 16 Jan 2019 00:59:40 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Wed, 16 Jan 2019 00:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-B2EaTGYfQB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02162.txt.bz2
Content-length: 205
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
On the #c22 testcase this started with r242549, but guess it has been latent
before.
>From gcc-bugs-return-629354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 01:03:07 2019
Return-Path: <gcc-bugs-return-629354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109920 invoked by alias); 16 Jan 2019 01:03:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 109868 invoked by uid 48); 16 Jan 2019 01:03:02 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/77960] ICE in gfc_conv_ss_startstride, at fortran/trans-array.c:3966
Date: Wed, 16 Jan 2019 01:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-77960-4-rOjJP9g9fa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77960-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77960-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02163.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77960
--- Comment #2 from kargl at gcc dot gnu.org ---
This is an interesting bug. Fortran 2003 exlicitly forbids
a procedure pointer from appearing in a READ statement.
F2003:C932 (R915) A variable that is an input-item shall
not be a procedure pointer.
This constraint is missing in F2008 and F2018. One then
looks at from say F2008
R916 input-item is variable
or io-implied-do
Well, a procedure pointer is certainly not an io-implied-do.
So, one must argue that a procedure pointer is not a variable.
>From gcc-bugs-return-629355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 02:03:35 2019
Return-Path: <gcc-bugs-return-629355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48347 invoked by alias); 16 Jan 2019 02:03: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 25660 invoked by uid 48); 16 Jan 2019 02:03:29 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Wed, 16 Jan 2019 02: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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88861-4-I0hK7vBC3e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02164.txt.bz2
Content-length: 471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Am testing a fix.
>From gcc-bugs-return-629356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 02:19:24 2019
Return-Path: <gcc-bugs-return-629356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119743 invoked by alias); 16 Jan 2019 02:19:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119678 invoked by uid 48); 16 Jan 2019 02:19:17 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88870] New: ICE: Segmentation fault (in df_worklist_propagate_backward)
Date: Wed, 16 Jan 2019 02:19: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: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: asolokha at gmx dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02165.txt.bz2
Content-length: 2247
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88870
Bug ID: 88870
Summary: ICE: Segmentation fault (in
df_worklist_propagate_backward)
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: asolokha at gmx dot com
Target Milestone: ---
gcc-9.0.0-alpha20190113 snapshot (r267906), 8.2, 7.4, 6.3, 5.4, 4.9.4, 4.8.5
all ICE when compiling the following snippet w/ -O1 -fexceptions
-fnon-call-exceptions -ftrapv -fno-tree-dominator-opts:
int ou, je;
void
r8 (int *y4)
{
int dc = 0;
{
int by;
y4 = &dc;
for (;;)
{
y4 = &by;
je = 0;
by = dc + 1;
je = dc = 1;
++ou;
}
}
}
% gcc-9.0.0-alpha20190113 -O1 -fexceptions -fnon-call-exceptions -ftrapv
-fno-tree-dominator-opts -c hbwhwojh.c
during RTL pass: rtl_dce
hbwhwojh.c: In function 'r8':
hbwhwojh.c:22:1: internal compiler error: Segmentation fault
22 | }
| ^
0xd6fc7f crash_signal
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/toplev.c:326
0x96e542 df_worklist_propagate_backward
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/df-core.c:953
0x96e542 df_worklist_dataflow_doublequeue
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/df-core.c:1043
0x96e542 df_worklist_dataflow(dataflow*, bitmap_head*, int*, int)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/df-core.c:1120
0x96eb2c df_analyze_problem(dataflow*, bitmap_head*, int*, int)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/df-core.c:1174
0x1580c52 fast_dce
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dce.c:1161
0x1580cd4 rest_of_handle_fast_dce
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20190113/work/gcc-9-20190113/gcc/dce.c:1186
>From gcc-bugs-return-629357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 07:13:44 2019
Return-Path: <gcc-bugs-return-629357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60919 invoked by alias); 16 Jan 2019 07: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 60843 invoked by uid 48); 16 Jan 2019 07:13:37 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Wed, 16 Jan 2019 07:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81849-4-E5FpFFQiDW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02166.txt.bz2
Content-length: 233
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
--- Comment #8 from Jürgen Reuter <juergen.reuter at desy dot de> ---
I think this fix or something very near by causes an ICE in our code, I will
provide a bug report soon.
>From gcc-bugs-return-629358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 07:22:28 2019
Return-Path: <gcc-bugs-return-629358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125410 invoked by alias); 16 Jan 2019 07:22:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125388 invoked by uid 48); 16 Jan 2019 07:22:24 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] New: [9.0 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 07:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02167.txt.bz2
Content-length: 966
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
Bug ID: 88871
Summary: [9.0 regression] ICE segmentation fault in f951
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: juergen.reuter at desy dot de
Target Milestone: ---
Created attachment 45436
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45436&action=edit
File that triggers the ICE.
The following (legacy) code included in our software package fails compilation
with an ICE in f951 with r267961, while r267903 was still working.
$ gfortran -g -O2 mnread.f
f951: internal compiler error: Segmentation fault: 11
libbacktrace could not find executable to open
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-629359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 07:25:04 2019
Return-Path: <gcc-bugs-return-629359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128621 invoked by alias); 16 Jan 2019 07:25:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128304 invoked by uid 48); 16 Jan 2019 07:24:58 -0000
From: "m.olbrich at pengutronix dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88872] New: ICE with g++ 8.x in cp_build_addr_expr_1, at cp/typeck.c:5936
Date: Wed, 16 Jan 2019 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m.olbrich at pengutronix 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-88872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02168.txt.bz2
Content-length: 3342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88872
Bug ID: 88872
Summary: ICE with g++ 8.x in cp_build_addr_expr_1, at
cp/typeck.c:5936
Product: gcc
Version: 8.2.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: m.olbrich at pengutronix dot de
Target Milestone: ---
Created attachment 45437
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45437&action=edit
Test code to reproduce the ICE
The current gcc-8-branch generates a ICE with the attached code.
This does not happen with trunk and was introduces in revision 260674
("PR c++/85864 - literal template and default template arg.").
ice.cxx:6:45: warning: literal operator suffixes not preceded by ‘_’ are
reserved for future standardization [-Wliteral-suffix]
template <char...> constexpr a operator"" n() { return d; }
^
ice.cxx: In instantiation of ‘j< <template-parameter-1-1> >::k() [with
<template-parameter-1-1> = int]::<lambda(auto:1)> [with auto:1 = int]’:
ice.cxx:19:40: required from ‘void j< <template-parameter-1-1> >::k() [with
<template-parameter-1-1> = int]’
ice.cxx:25:22: required from here
ice.cxx:19:31: internal compiler error: in cp_build_addr_expr_1, at
cp/typeck.c:5936
[](auto) { constexpr auto l = 2n; }(keywords);
^
0x5906e8 cp_build_addr_expr_1
.../gcc/gcc/cp/typeck.c:5936
0x5906e8 cp_build_addr_expr_1
.../gcc/gcc/cp/typeck.c:5797
0x5d02b7 convert_like_real
.../gcc/gcc/cp/call.c:7081
0x5d3669 build_over_call
.../gcc/gcc/cp/call.c:7999
0x5d29e9 build_new_method_call_1
.../gcc/gcc/cp/call.c:9378
0x5d29e9 build_new_method_call(tree_node*, tree_node*, vec<tree_node*, va_gc,
vl_embed>**, tree_node*, int, tree_node**, int)
.../gcc/gcc/cp/call.c:9453
0x5d52f9 build_special_member_call(tree_node*, tree_node*, vec<tree_node*,
va_gc, vl_embed>**, tree_node*, int, int)
.../gcc/gcc/cp/call.c:8980
0x60496f ocp_convert(tree_node*, tree_node*, int, int, int)
.../gcc/gcc/cp/cvt.c:907
0x641545 expand_default_init
.../gcc/gcc/cp/init.c:1843
0x641545 expand_aggr_init_1
.../gcc/gcc/cp/init.c:2021
0x64185b build_aggr_init(tree_node*, tree_node*, int, int)
.../gcc/gcc/cp/init.c:1761
0x60fe57 build_aggr_init_full_exprs
.../gcc/gcc/cp/decl.c:6283
0x60fe57 check_initializer
.../gcc/gcc/cp/decl.c:6432
0x61e99b cp_finish_decl(tree_node*, tree_node*, bool, tree_node*, int)
.../gcc/gcc/cp/decl.c:7145
0x6b846c tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
.../gcc/gcc/cp/pt.c:16767
0x6b6b43 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
.../gcc/gcc/cp/pt.c:16921
0x6b6b43 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
.../gcc/gcc/cp/pt.c:16921
0x6b6b43 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
.../gcc/gcc/cp/pt.c:16921
0x6b57c8 tsubst_expr(tree_node*, tree_node*, int, tree_node*, bool)
.../gcc/gcc/cp/pt.c:16606
0x6b57c8 instantiate_decl(tree_node*, bool, bool)
.../gcc/gcc/cp/pt.c:24056
>From gcc-bugs-return-629360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 07:25:43 2019
Return-Path: <gcc-bugs-return-629360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3883 invoked by alias); 16 Jan 2019 07:25: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 129718 invoked by uid 48); 16 Jan 2019 07:25:26 -0000
From: "m.olbrich at pengutronix dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88872] ICE with g++ 8.x in cp_build_addr_expr_1, at cp/typeck.c:5936
Date: Wed, 16 Jan 2019 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: m.olbrich at pengutronix 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-88872-4-PtnHGf4Bft@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02169.txt.bz2
Content-length: 169
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88872
--- Comment #1 from m.olbrich at pengutronix dot de ---
I forgot to mention: This only happens with "-std=c++17"
>From gcc-bugs-return-629361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 07:49:03 2019
Return-Path: <gcc-bugs-return-629361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84799 invoked by alias); 16 Jan 2019 07:48: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 84634 invoked by uid 48); 16 Jan 2019 07:48:41 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9.0 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 07:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-ECJhJ2GIHj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02170.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
--- Comment #1 from Jürgen Reuter <juergen.reuter at desy dot de> ---
My suspicion goes toward the fix for PR81849, so maybe also the gcc-7 and gcc-8
branches are affected.
>From gcc-bugs-return-629362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 08:02:14 2019
Return-Path: <gcc-bugs-return-629362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56397 invoked by alias); 16 Jan 2019 08:02:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46289 invoked by uid 55); 16 Jan 2019 08:02:09 -0000
From: "drepper at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88738] treat shared_ptr and unique_ptr more like plain old pointers
Date: Wed, 16 Jan 2019 08:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: drepper at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88738-4-DqPWuIAcLR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02171.txt.bz2
Content-length: 847
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88738
--- Comment #10 from drepper at gcc dot gnu.org ---
Author: drepper
Date: Wed Jan 16 08:01:22 2019
New Revision: 267964
URL: https://gcc.gnu.org/viewcvs?rev=267964&root=gcc&view=rev
Log:
PR libstdc++/88738 treat shared_ptr and unique_ptr more like plain old pointers
PR libstdc++/88738
Warn about unused comparisons of shared_ptr/unique_ptr
* include/bits/c++config [_GLIBCXX_NODISCARD]: Define.
* include/bits/shared_ptr.h: Use it for operator ==, !=,
<, <=, >, >= for shared_ptr.
* include/bits/unique_ptr.h: Likewise for unique_ptr.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/c++config
trunk/libstdc++-v3/include/bits/shared_ptr.h
trunk/libstdc++-v3/include/bits/unique_ptr.h
>From gcc-bugs-return-629363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 08:22:41 2019
Return-Path: <gcc-bugs-return-629363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49295 invoked by alias); 16 Jan 2019 08:22:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49179 invoked by uid 48); 16 Jan 2019 08:22:36 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Wed, 16 Jan 2019 08:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-88714-4-BepQwYvrU1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02172.txt.bz2
Content-length: 711
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #24 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45438
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45438&action=edit
gcc9-pr88714-poc.patch
Proof of concept that fixes the short testcase.
One would need to write remaining non-thumb patterns (strd in vfp.md, ldrd +
strd in arm.md and ldrd + strd in iwmmxt.md, all close to the movdi patterns,
unless there is a possibility to unify them (but, e.g. iwmmxt.md uses r instead
of q, etc.?)) and do it always in ldrdst*.md. Not really sure about the
predicates, constraints etc. either., will defer that to those familiar with
the backend and architecture.
>From gcc-bugs-return-629364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 08:46:36 2019
Return-Path: <gcc-bugs-return-629364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11619 invoked by alias); 16 Jan 2019 08:46:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11560 invoked by uid 48); 16 Jan 2019 08:46:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88870] [7/8/9 Regression] ICE: Segmentation fault (in df_worklist_propagate_backward)
Date: Wed, 16 Jan 2019 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88870-4-aQleAKnPHA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02173.txt.bz2
Content-length: 1035
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88870
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |jakub at gcc dot gnu.org
Target Milestone|--- |7.5
Summary|ICE: Segmentation fault (in |[7/8/9 Regression] ICE:
|df_worklist_propagate_backw |Segmentation fault (in
|ard) |df_worklist_propagate_backw
| |ard)
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started to ICE in between r184930 (last good) and r184937 (first ICE).
So either r184932, or r184933, or 184937.
>From gcc-bugs-return-629365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 08:58:01 2019
Return-Path: <gcc-bugs-return-629365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71128 invoked by alias); 16 Jan 2019 08:58: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 66216 invoked by uid 48); 16 Jan 2019 08:57:56 -0000
From: "crazylht at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88778] Odd Complex float load
Date: Wed, 16 Jan 2019 08:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: crazylht at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88778-4-2bztjqTF1Y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88778-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02174.txt.bz2
Content-length: 847
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88778
--- Comment #8 from åˆ˜è¢‹é¼ <crazylht at gmail dot com> ---
(In reply to H.J. Lu from comment #5)
> Please take a look at
>
> https://github.com/hjl-tools/gcc/commit/
> a56b4a49b2617a31365bdb9c44340695c31d56e8
How did you handle MOV reg(SCmode) <---- CONST_RTX(SCmode), I got an error
report bellow insn wasn't recognized.
(insn 31 16 17 2 (set (reg:SC 91 [ c ])
(concat:SC (const_double:SF 0.0 [0x0.0p+0])
(const_double:SF 0.0 [0x0.0p+0]))) "complex.c":5:5 -1
(nil))
reference patch is at
https://github.com/algebra84/gcc/commit/2dcce0fcdddd964b4d3034344a8c242edf6e6d0c
Simple case bellow will reproduce problem:
cat complex.c
_Complex float
foo (_Complex float a, _Complex float b)
{
_Complex float c,d;
c = a + b;
return c;
}
>From gcc-bugs-return-629366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:03:11 2019
Return-Path: <gcc-bugs-return-629366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89757 invoked by alias); 16 Jan 2019 09:03:11 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 89591 invoked by uid 48); 16 Jan 2019 09:03:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88872] [8 Regression] ICE with g++ 8.x in cp_build_addr_expr_1, at cp/typeck.c:5936
Date: Wed, 16 Jan 2019 09:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-88872-4-VkFUSy5U1i@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02175.txt.bz2
Content-length: 1314
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88872
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |jakub at gcc dot gnu.org,
| |jason at gcc dot gnu.org
Target Milestone|--- |8.3
Summary|ICE with g++ 8.x in |[8 Regression] ICE with g++
|cp_build_addr_expr_1, at |8.x in
|cp/typeck.c:5936 |cp_build_addr_expr_1, at
| |cp/typeck.c:5936
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Confirmed on the 8.x branch (including Jun 15 2018 and Jan 8 2019 snapshots),
but doesn't ICE in 7.x, nor at 8.x branchpoint, nor at current trunk.
On the trunk it started to ICE with r260672 and got fixed with r265788 (but
given the number of issues that revision exposed I think it isn't really
backportable).
The testcase should be added to trunk testsuite I guess.
>From gcc-bugs-return-629367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:03:50 2019
Return-Path: <gcc-bugs-return-629367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90887 invoked by alias); 16 Jan 2019 09:03:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90819 invoked by uid 48); 16 Jan 2019 09:03:44 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9.0 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 09:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-OGsLSxvXkW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02176.txt.bz2
Content-length: 880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
--- Comment #2 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Here is a more minimal example:
SUBROUTINE MNREAD(IFLGIN,IFLGUT)
IMPLICIT DOUBLE PRECISION (A-H,O-Z)
PARAMETER (MNE=100 , MNI=50)
PARAMETER (MNIHL=MNI*(MNI+1)/2)
CHARACTER*10 CPNAM
COMMON
1/MN7NAM/ CPNAM(MNE)
2/MN7EXT/ U(MNE)
CHARACTER CRDBUF*80, CUPBUF*10
CUPBUF(1:10) = CRDBUF(1:10)
RETURN
END
or also to completely implicit typing
SUBROUTINE MNREAD(IFLGIN,IFLGUT)
PARAMETER (MNE=100 , MNI=50)
PARAMETER (MNIHL=MNI*(MNI+1)/2)
CHARACTER*10 CPNAM
COMMON
1/MN7NAM/ CPNAM(MNE)
2/MN7EXT/ U(MNE)
CHARACTER CRDBUF*80, CUPBUF*10
CUPBUF(1:10) = CRDBUF(1:10)
RETURN
END
>From gcc-bugs-return-629368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:11:59 2019
Return-Path: <gcc-bugs-return-629368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124187 invoked by alias); 16 Jan 2019 09:11: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 123841 invoked by uid 48); 16 Jan 2019 09:11:54 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88869] ICE (Segmentation Fault) when using lambda
Date: Wed, 16 Jan 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: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88869-4-8e5qVetnZe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02177.txt.bz2
Content-length: 785
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88869
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Reduced testcase (-std=c++17):
using A = int;
template <typename> struct B;
template <> struct B<A> {
template <typename> struct C { C (); };
auto foo () { C (); }
};
That is ice-on-invalid, dunno if the original is invalid too or not.
>From gcc-bugs-return-629369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:36:36 2019
Return-Path: <gcc-bugs-return-629369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80408 invoked by alias); 16 Jan 2019 09:36: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 80200 invoked by uid 48); 16 Jan 2019 09:36:31 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/88714] [9 regression] bootstrap comparison failure on armv7l since r265398
Date: Wed, 16 Jan 2019 09:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88714-4-8EU1HF6NnP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02178.txt.bz2
Content-length: 200
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88714
--- Comment #25 from ktkachov at gcc dot gnu.org ---
Thanks, I've reproduced the failure with the reduced testcase (aborts at -O2
but not at -O0)
>From gcc-bugs-return-629371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:46:52 2019
Return-Path: <gcc-bugs-return-629371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40305 invoked by alias); 16 Jan 2019 09:46: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 40158 invoked by uid 48); 16 Jan 2019 09:46:45 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70696] [Coarray] ICE on EVENT POST of host-associated EVENT_TYPE coarray
Date: Wed, 16 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-70696-4-onHkmoF8nU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02180.txt.bz2
Content-length: 4395
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70696
Uroš Bizjak <ubizjak at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #17 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to vehre from comment #9)
> Author: vehre
> Date: Fri Jan 13 10:22:21 2017
> New Revision: 244407
>
> URL: https://gcc.gnu.org/viewcvs?rev=244407&root=gcc&view=rev
> Log:
> gcc/testsuite/ChangeLog:
>
> 2017-01-13 Andre Vehreschild <vehre@gcc.gnu.org>
>
> PR fortran/70696
> * gfortran.dg/coarray/event_3.f08: New test.
What is this test supposed to test? The _.optimized dump shows only:
--cut here--
;; Function main (main, funcdef_no=2, decl_uid=952, cgraph_uid=3,
symbol_order=2) (executed once)
__attribute__((externally_visible))
main (integer(kind=4) argc, character(kind=1) * * argv)
{
struct FRAME.global_event FRAME.1;
static integer(kind=4) options.0[7] = {2116, 4095, 0, 1, 1, 0, 31};
integer(kind=4) _8;
<bb 2> [local count: 1073741824]:
_gfortran_set_args (argc_2(D), argv_3(D));
_gfortran_set_options (7, &options.0[0]);
_8 = FRAME.1.x;
if (_8 != 0)
goto <bb 3>; [0.04%]
else
goto <bb 4>; [99.96%]
<bb 3> [local count: 429497]:
_gfortran_error_stop_numeric (1, 0);
<bb 4> [local count: 1073312328]:
return 0;
}
--cut here--
which results in uninitialized load from FRAME.1. The resulting x86_64 assembly
is:
main:
.LFB2:
.cfi_startproc
subq $8, %rsp
.cfi_def_cfa_offset 16
call _gfortran_set_args
movl $options.0.3867, %esi
movl $7, %edi
call _gfortran_set_options
xorl %eax, %eax
addq $8, %rsp
.cfi_def_cfa_offset 8
ret
.cfi_endproc
which does not test anything. While x86_64 optimizers are able to eliminate
uninitialized load, it remains in alpha assembly:
main:
.frame $30,32,$26,0
.mask 0x4000000,-32
$LFB2:
.cfi_startproc
ldah $29,0($27) !gpdisp!1 #,,
lda $29,0($29) !gpdisp!1 #,,
$main..ng:
lda $30,-32($30) #,,
.cfi_def_cfa_offset 32
ldq $27,_gfortran_set_args($29) !literal!3 #,,,
stq $26,0($30) #,
.cfi_offset 26, -32
.prologue 1
# event_3.f08:10: call exchange
jsr $26,($27),_gfortran_set_args !lituse_jsr!3 #,,
ldah $29,0($26) !gpdisp!4 #
lda $16,7($31) #,
lda $29,0($29) !gpdisp!4 #,,
ldah $17,options.0.956($29) !gprelhigh # tmp75,,
lda $17,options.0.956($17) !gprellow #,, tmp75
ldq $27,_gfortran_set_options($29) !literal!5 #,,,
jsr $26,($27),_gfortran_set_options !lituse_jsr!5 #,,
ldah $29,0($26) !gpdisp!6 #
# event_3.f08:17: if (cnt /= 2) error stop 1
ldl $1,16($30) # FRAME.1.x, FRAME.1.x
# event_3.f08:10: call exchange
lda $29,0($29) !gpdisp!6 #,,
# event_3.f08:17: if (cnt /= 2) error stop 1
bis $31,$31,$31
bne $1,$L4 #, FRAME.1.x,
# event_3.f08:10: call exchange
mov $31,$0 #,
ldq $26,0($30) #,
lda $30,32($30) #,,
.cfi_remember_state
.cfi_restore 26
.cfi_def_cfa_offset 0
ret $31,($26),1
$L4:
.cfi_restore_state
# event_3.f08:17: if (cnt /= 2) error stop 1
mov $31,$17 #,
ldq $27,_gfortran_error_stop_numeric($29) !literal!2
#,,,
lda $16,1($31) #,
jsr $26,($27),_gfortran_error_stop_numeric !lituse_jsr!2
#,,
.cfi_endproc
$LFE2:
bis $31,$31,$31
.end main
Please note:
ldl $1,16($30) # FRAME.1.x, FRAME.1.x
...
bne $1,$L4 #, FRAME.1.x,
Which loads uninitialized value from the stack and later branches on non-zero
value. When the testcase is sun inside the debugger, it is evident that a
garbage value is loaded from the 16($30) stack location.
>From gcc-bugs-return-629370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:46:52 2019
Return-Path: <gcc-bugs-return-629370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40295 invoked by alias); 16 Jan 2019 09:46: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 40204 invoked by uid 48); 16 Jan 2019 09:46:48 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68887] [6 regression] gfortran.dg/coarray/event_[12].f90 -fcoarray=lib -O2 -lcaf_single -latomic fails
Date: Wed, 16 Jan 2019 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: vehre at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-68887-4-3p3clJL3VT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68887-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68887-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02179.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68887
Bug 68887 depends on bug 70696, which changed state.
Bug 70696 Summary: [Coarray] ICE on EVENT POST of host-associated EVENT_TYPE coarray
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70696
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
>From gcc-bugs-return-629372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 09:51:53 2019
Return-Path: <gcc-bugs-return-629372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45661 invoked by alias); 16 Jan 2019 09:51:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45608 invoked by uid 48); 16 Jan 2019 09:51:48 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88873] New: missing vectorization for decomposed operations on a vector type
Date: Wed, 16 Jan 2019 09:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88873-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02181.txt.bz2
Content-length: 1944
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88873
Bug ID: 88873
Summary: missing vectorization for decomposed operations on a
vector type
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: vincent-gcc at vinc17 dot net
Target Milestone: ---
To compute a vectorized fma, one needs to apply it on the decomposed vector
components. Here's an example with a structure type and with a vector type. The
structure type solution is just given for comparison. This bug is about the
vector type solution.
#include <math.h>
typedef struct { double x, y; } s_t;
typedef double v2df __attribute__ ((vector_size (2 * sizeof(double))));
s_t foo (s_t a, s_t b, s_t c)
{
return (s_t) { fma(a.x, b.x, c.x), fma (a.y, b.y, c.y) };
}
v2df bar (v2df a, v2df b, v2df c)
{
v2df r;
r[0] = fma (a[0], b[0], c[0]);
r[1] = fma (a[1], b[1], c[1]);
return r;
}
With -O3, I get on x86_64:
* For function foo (struct type):
[...]
vfmadd132pd -40(%rsp), %xmm7, %xmm6
[...]
This is vectorized as expected, though this solution is affected by bug 65847.
* For function bar (vector type):
bar:
.LFB1:
.cfi_startproc
vmovapd %xmm0, %xmm3
vunpckhpd %xmm0, %xmm0, %xmm0
vfmadd132sd %xmm1, %xmm2, %xmm3
vunpckhpd %xmm1, %xmm1, %xmm1
vunpckhpd %xmm2, %xmm2, %xmm2
vfmadd132sd %xmm1, %xmm2, %xmm0
vunpcklpd %xmm0, %xmm3, %xmm0
ret
.cfi_endproc
This is not vectorized: one has 2 vfmadd132sd instead of a single vfmadd132pd.
Note: The problem is the same with addition, but in the addition case, one can
simply do a + b. This is not possible with fma.
This bug seems similar to bug 77399.
>From gcc-bugs-return-629373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:10:00 2019
Return-Path: <gcc-bugs-return-629373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87838 invoked by alias); 16 Jan 2019 10:09:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 86949 invoked by uid 48); 16 Jan 2019 10:09:49 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 16 Jan 2019 10:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88760-4-lhiG0yvZES@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02182.txt.bz2
Content-length: 2026
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |rsandifo at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #10 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
FWIW, I agree that pure unrolling doesn't feel like a gimple-level
optimisation. Whether it's a win or not depends on whether the
unrolled loop will make better use of the microarchitecture.
The problem isn't just that that's hard to decide at the gimple level,
but that the result can't be represented directly in gimple. AIUI
there's no real significance to the schedule of gimple statements
(beyond ensuring valid SSA and functional correctness).
This is different from vectorisation and ivopts, which can represent
the benefit of the transformation directly in gimple (using vector
ops and TARGET_MEM_REFs respectively).
As Kyrill pointed out off-list, LLVM does the unrolling in the vectoriser
rather than a separate unrolling pass. (Use -mllvm -print-after-all
to see this.)
I think for AArch64 we can view LDP and STP as 2-element vector loads
and stores that have zero-cost insertion and extraction. So converting:
ldr x0, [...]
add x0, x0, 1
str x0, [...]
into:
ldp x0, x1, [...]
add x0, x0, 1
add x1, x1, 1
stp x0, x1, [...]
is IMO genuine vectorisation. The LDPs and STPs are effectively
scalar IFN_LOAD_LANES and IFN_STORE_LANES, although we could also
represent them as single-element (V1) vector ops instead if that
seems more consistent.
Vectorising operations other than loads and stores would simply
involve duplicating the statements VF times.
>From gcc-bugs-return-629374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:12:46 2019
Return-Path: <gcc-bugs-return-629374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 90379 invoked by alias); 16 Jan 2019 10:12: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 90315 invoked by uid 48); 16 Jan 2019 10:12:42 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88874] New: support FMA on vector types
Date: Wed, 16 Jan 2019 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02183.txt.bz2
Content-length: 615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88874
Bug ID: 88874
Summary: support FMA on vector types
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: vincent-gcc at vinc17 dot net
Target Milestone: ---
Please support FMA on vector types (vector extensions).
FYI, there is a already a similar PR for sqrt: PR 54408.
Note also that autovectorization on decomposed vector types does not work
currently: PR 88873.
>From gcc-bugs-return-629375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:23:16 2019
Return-Path: <gcc-bugs-return-629375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7264 invoked by alias); 16 Jan 2019 10:23: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 6816 invoked by uid 48); 16 Jan 2019 10:23:12 -0000
From: "vincent-gcc at vinc17 dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88873] missing vectorization for decomposed operations on a vector type
Date: Wed, 16 Jan 2019 10:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vincent-gcc at vinc17 dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88873-4-AurQtM2F9M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88873-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88873-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02184.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88873
--- Comment #1 from Vincent Lefèvre <vincent-gcc at vinc17 dot net> ---
Note: with Clang, I get vectorized code as expected:
bar: # @bar
.cfi_startproc
# %bb.0:
vfmadd213pd %xmm2, %xmm1, %xmm0 # xmm0 = (xmm1 * xmm0) + xmm2
retq
.Lfunc_end1:
.size bar, .Lfunc_end1-bar
.cfi_endproc
>From gcc-bugs-return-629376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:36:26 2019
Return-Path: <gcc-bugs-return-629376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18910 invoked by alias); 16 Jan 2019 10:36: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 18798 invoked by uid 48); 16 Jan 2019 10:36:17 -0000
From: "dilyan.palauzov at aegee dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/84995] Documentation gcc-ar and gcc-ranlib vs {libdir}/bfd-plugins
Date: Wed, 16 Jan 2019 10:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dilyan.palauzov at aegee dot org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84995-4-AONDjt0TOY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84995-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02185.txt.bz2
Content-length: 3950
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84995
--- Comment #18 from ДилÑн Палаузов <dilyan.palauzov at aegee dot org> ---
I will sum up the discussion so far on this and other tickets:
When one distributes source code software packages, the developers directly or
indirectly use AR to create static libraries, when the user wants static
libraries. Think on autoconf/libtool packages, where the users of those
packages = software developers do not deal with AR.
When a mortal user wants to build something with LTO, the user has to pass
-flto to the compiler, for any source code package. Doing the LTO build
process more complex than that leads to a situation, where LTO is not utilized,
due to the complixity of running it.
Some distributions install the linker plugin under $libdir/bfd-plugins and make
ar/nm/ranlib deal transparently with -flto, but putting the plugin under
$libdir/bfd-plugin for using ar/ranlib/nm is apparently kind of secret or too
complicated, as not all distributions do this. So sticking to AR for building
with LTO is currently not portable.
When CMake is used, it chooses the appropriate gcc-ar-4, gcc-ar, llvm-ar-4.0 or
llvm-ar (see https://gitlab.kitware.com/cmake/cmake/commit/630235bd9e049a8da47
and https://gitlab.kitware.com/cmake/cmake/commit/75accaae8b6a691b031f2) and
ensures, that the just passing -flto will enable LTO. As can be seen from the
commits above, instead of installing the linker plugin under
$libdir/bfd-plugins, distributions rename gcc-ar to something different.
CPython’s autoconf tries to detect if LTO is used and either switches to
llvm-lto or (with GCC) uses fat lto objects, but does not use gcc-ar. Likewise
valgrind’s ./configure uses gcc-ar, but not llvm-ar, so does libical’s
Cmakefile (to enable LTO in old cmake versions). So the solution of compiling
platform independent software is not in the distributions, the solution is to
do incomplete hacks in the configure steps, and apparently meson has some
knowledge how to do this (büt does not append the version number), cmake has
the most complete knowledge and experimenting with autoconf nobody provides
portable software where LTO is works both under LLVM and GCC. Thus the
intention of tweaking ./configure is to achieve portability but nobody managed
to achieve it in an optimal way yet.
Installing the linker plugin under $libdir/bfd-plugins by the compiler will
suggest to all distributions that the linker plugin has to be there and the
distributions will ensure that at all time there is a linker plugin, while it
is in practice irrelevant from which GCC version the linker plugin comes. It
is irrelevant, because the plugin there is only used by ar/nm/ranlib and the
differences between the versions of liblto_plugin are insignificant to
ar/nm/ranlib.
There are now two options:
* installing the linker plugin by gcc’s “make install†in $libdir/bfd-plugin
which will lead in mid-term to having AR deal with LTO in a portable way
* not installing the linker plugin by gcc’s “make install†in
$libdir/bfd-plugin. The only portable/cross-platform way to build with LTO is
using cmake. Seriously.
That said, there are advantages when gcc’s “make install†inserts its plugin in
$libdir/bfd-plugins and no disadvantages. While not doing so has only
disadvantages.
Please explain whe gcc’s “make install†does not insert its linker plugin on
the rigth place and how are supposed software developers to write
software/build systems, that support LTO on any platform.
Finally, not installing the plugin under $libdir/bfd-plugins because of
differences in the versions, forces users to use gcc-ar, but it has the very
same problems with differences in the versions.
>From gcc-bugs-return-629377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:42:29 2019
Return-Path: <gcc-bugs-return-629377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36511 invoked by alias); 16 Jan 2019 10:42: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 35954 invoked by uid 48); 16 Jan 2019 10:42:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/54408] sqrt for vector types
Date: Wed, 16 Jan 2019 10:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords:
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-54408-4-9Df0PihTTg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-54408-4@http.gcc.gnu.org/bugzilla/>
References: <bug-54408-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02186.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54408
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
__builtin_tg_sqrt () maybe. The difficulty is in expected behavior for
"standard" -O[0] when you supply vector arguments. I think the most
"convenient" thing to do is to say that __builtin_tg_sqrt () when not
invoked on scalar types can (but also might not) affect errno but in
unpredictable ways. OTOH for sqrt the only documented errno is EDOM
thus the result would be that errno is EDOM if at least one component
caused a domain error. That would support lowering non-scalar variants
to component-wise operation and also gives eventual support from math
libraries the necessary freedom.
>From gcc-bugs-return-629378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:50:05 2019
Return-Path: <gcc-bugs-return-629378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42922 invoked by alias); 16 Jan 2019 10:50: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 42787 invoked by uid 48); 16 Jan 2019 10:50:00 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88869] [7/8/9 Regression] ICE (Segmentation Fault) when using lambda
Date: Wed, 16 Jan 2019 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc target_milestone short_desc
Message-ID: <bug-88869-4-JnZaCy4Ghw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02187.txt.bz2
Content-length: 1014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88869
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
CC| |jason at gcc dot gnu.org
Target Milestone|--- |7.5
Summary|ICE (Segmentation Fault) |[7/8/9 Regression] ICE
|when using lambda |(Segmentation Fault) when
| |using lambda
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Started to ICE with r249816 aka PR81180 fix which has been backported to 7.x
where it ICEs now too.
Better testcase which is accepted by clang++:
using A = int;
template <typename> struct B;
template <> struct B<A> {
template <typename T> struct C {
T e;
C (T f) : e(f) {}
};
auto foo () { C ([] {}); }
};
>From gcc-bugs-return-629379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:51:06 2019
Return-Path: <gcc-bugs-return-629379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44412 invoked by alias); 16 Jan 2019 10:51: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 44303 invoked by uid 48); 16 Jan 2019 10:51:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88873] missing vectorization for decomposed operations on a vector type
Date: Wed, 16 Jan 2019 10:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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 blocked everconfirmed
Message-ID: <bug-88873-4-vlyj1OQMzA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88873-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88873-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02188.txt.bz2
Content-length: 2452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88873
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
Blocks| |53947
Ever confirmed|0 |1
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. bar is not vectorized because it looks like
<bb 2> [local count: 1073741824]:
_1 = BIT_FIELD_REF <c_10(D), 64, 0>;
_2 = BIT_FIELD_REF <b_11(D), 64, 0>;
_3 = BIT_FIELD_REF <a_12(D), 64, 0>;
_4 = fma (_3, _2, _1);
r_14 = BIT_INSERT_EXPR <r_13(D), _4, 0 (64 bits)>;
_5 = BIT_FIELD_REF <c_10(D), 64, 64>;
_6 = BIT_FIELD_REF <b_11(D), 64, 64>;
_7 = BIT_FIELD_REF <a_12(D), 64, 64>;
_8 = fma (_7, _6, _5);
r_15 = BIT_INSERT_EXPR <r_14, _8, 64 (64 bits)>;
return r_15;
and there are no loads/stores BB vectorization can work with. There's
an enhancement request for BB vectorization to key off
vector constructors and this one is similar. Eventually
r_14 = BIT_INSERT_EXPR <r_13(D), _4, 0 (64 bits)>;
r_15 = BIT_INSERT_EXPR <r_14, _8, 64 (64 bits)>;
should be combined to
r_15 = { _4, _8 };
but then dependence on BB SLP of vector CONSTRUCTORs remains. There's
also still no loads but eventually the BIT_FIELD_REFs are enough here.
Appearantly not:
v2df r;
v2df bar (v2df a, v2df b, v2df c)
{
r[0] = fma (a[0], b[0], c[0]);
r[1] = fma (a[1], b[1], c[1]);
return r;
}
results in
<bb 2> [local count: 1073741824]:
_1 = BIT_FIELD_REF <c_13(D), 64, 0>;
_2 = BIT_FIELD_REF <b_14(D), 64, 0>;
_3 = BIT_FIELD_REF <a_15(D), 64, 0>;
_4 = fma (_3, _2, _1);
_5 = BIT_FIELD_REF <c_13(D), 64, 64>;
_6 = BIT_FIELD_REF <b_14(D), 64, 64>;
_7 = BIT_FIELD_REF <a_15(D), 64, 64>;
_8 = fma (_7, _6, _5);
_16 = {_4, _8};
vect_cst__17 = _16;
MEM[(vector(2) double *)&r] = vect_cst__17;
_12 = r;
return _12;
so we only vectorize the store:
t.c:18:10: missed: Build SLP failed: not grouped load _3 = BIT_FIELD_REF
<a_15(D), 64, 0>;
but that should be possible to fix as well.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=53947
[Bug 53947] [meta-bug] vectorizer missed-optimizations
>From gcc-bugs-return-629380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:53:01 2019
Return-Path: <gcc-bugs-return-629380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46038 invoked by alias); 16 Jan 2019 10:53:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45957 invoked by uid 48); 16 Jan 2019 10:52:57 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88872] [8 Regression] ICE with g++ 8.x in cp_build_addr_expr_1, at cp/typeck.c:5936
Date: Wed, 16 Jan 2019 10:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority cf_known_to_work cf_known_to_fail
Message-ID: <bug-88872-4-GEk5jad1WR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88872-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88872-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02189.txt.bz2
Content-length: 481
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88872
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P3 |P2
Known to work| |7.4.0, 8.1.0, 9.0
Known to fail| |8.2.0
>From gcc-bugs-return-629381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 10:56:34 2019
Return-Path: <gcc-bugs-return-629381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62152 invoked by alias); 16 Jan 2019 10:56: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 61651 invoked by uid 48); 16 Jan 2019 10:56:29 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88870] [7/8/9 Regression] ICE: Segmentation fault (in df_worklist_propagate_backward)
Date: Wed, 16 Jan 2019 10:56: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.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-88870-4-5R6eyfJKnF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02190.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88870
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45439
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45439&action=edit
gcc9-pr88870.patch
Untested fix.
>From gcc-bugs-return-629382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:04:26 2019
Return-Path: <gcc-bugs-return-629382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92511 invoked by alias); 16 Jan 2019 11:04: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 92421 invoked by uid 48); 16 Jan 2019 11:04:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 11:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88871-4-9d0FYcm4I2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02191.txt.bz2
Content-length: 575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
Summary|[9.0 regression] ICE |[9 regression] ICE
|segmentation fault in f951 |segmentation fault in f951
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Seems to work on the branches but I can't reproduce on trunk either.
>From gcc-bugs-return-629383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:06:24 2019
Return-Path: <gcc-bugs-return-629383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102032 invoked by alias); 16 Jan 2019 11:06:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 101979 invoked by uid 48); 16 Jan 2019 11:06:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87015] [8/9 Regression] miscompilation of template heavy Boost Spirit code
Date: Wed, 16 Jan 2019 11:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-87015-4-UE236l3b9X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02192.txt.bz2
Content-length: 748
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87015
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
If what you are compiling has multiple sources and if e.g. -O0 helps, then you
could bisect among the object files to find the problematic *.o file.
That can be then preprocessed e.g. with -save-temps.
Further analysis can be done by using bisection in the file using #pragma GCC
optimize (0) and/or __attribute__((optimize (0))) to find problematic
function/method.
>From gcc-bugs-return-629384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:07:39 2019
Return-Path: <gcc-bugs-return-629384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103637 invoked by alias); 16 Jan 2019 11:07:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103573 invoked by uid 48); 16 Jan 2019 11:07:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/87015] [8/9 Regression] miscompilation of template heavy Boost Spirit code
Date: Wed, 16 Jan 2019 11:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87015-4-FX25wmws3M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87015-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87015-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02193.txt.bz2
Content-length: 374
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87015
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Or if 7.3 works and 8.x doesn't and the two are ABI compatible (dunno about
mingw), then you could after you find problematic *.ii file try to bisect which
compiler revision changed the behavior and from there you we could try to
discover what changed.
>From gcc-bugs-return-629385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:14:52 2019
Return-Path: <gcc-bugs-return-629385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115382 invoked by alias); 16 Jan 2019 11:14: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 115309 invoked by uid 48); 16 Jan 2019 11:14:47 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88870] [7/8/9 Regression] ICE: Segmentation fault (in df_worklist_propagate_backward)
Date: Wed, 16 Jan 2019 11:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88870-4-aoRoC9Ja31@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02194.txt.bz2
Content-length: 1871
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88870
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
fast_dce gathers postorder and friends computing all_blocks before it
eventually does
if (global_changed)
{
/* Turn off the RUN_DCE flag to prevent recursive calls to
dce. */
int old_flag = df_clear_flags (DF_LR_RUN_DCE);
/* So something was deleted that requires a redo. Do it on
the cheap. */
delete_unmarked_insns ();
^^^
which alters the CFG, removing edges/blocks here:
#0 remove_edge (e=<edge 0x7ffff69d82d0 (3 -> 5)>)
at /space/rguenther/src/svn/gcc-8-branch/gcc/cfghooks.c:423
#1 0x0000000000a16458 in purge_dead_edges (
bb=<basic_block 0x7ffff68852d8 (3)>)
at /space/rguenther/src/svn/gcc-8-branch/gcc/cfgrtl.c:3080
#2 0x0000000000a0fcb9 in delete_insn_and_edges (insn=0x7ffff69d51f8)
at /space/rguenther/src/svn/gcc-8-branch/gcc/cfgrtl.c:233
#3 0x0000000001b8f314 in delete_unmarked_insns ()
at /space/rguenther/src/svn/gcc-8-branch/gcc/dce.c:636
where we'd eventually alos purge unreachable blocks.
but then we simply continue
bitmap_clear (marked);
bitmap_clear (processed);
bitmap_clear (redo_out);
/* We do not need to rescan any instructions. We only need
to redo the dataflow equations for the blocks that had a
change at the top of the block. Then we need to redo the
iteration. */
if (word_level)
df_analyze_problem (df_word_lr, all_blocks, postorder, n_blocks);
else
df_analyze_problem (df_lr, all_blocks, postorder, n_blocks);
and here things blow up because DF is still set up on the old CFG or
we are at least passing in old CFG state (all_blocks, postorder, n_blocks)
here.
>From gcc-bugs-return-629386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:16:50 2019
Return-Path: <gcc-bugs-return-629386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117608 invoked by alias); 16 Jan 2019 11:16:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117488 invoked by uid 48); 16 Jan 2019 11:16:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88869] [7/8/9 Regression] ICE (Segmentation Fault) when using lambda
Date: Wed, 16 Jan 2019 11:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-88869-4-uOXTXyRswZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02195.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88869
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P5 |P2
>From gcc-bugs-return-629387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:44:02 2019
Return-Path: <gcc-bugs-return-629387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33035 invoked by alias); 16 Jan 2019 11:44: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 32934 invoked by uid 48); 16 Jan 2019 11:43:57 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 11:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-nr0l4xHcQg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02196.txt.bz2
Content-length: 417
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
--- Comment #4 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Richard Biener from comment #3)
> Seems to work on the branches but I can't reproduce on trunk either.
That is strange. Did you try to compile several
times? Sometimes it comes, sometimes it doesn’t.
I did svn up and compiled the gcc,
maybe I have to recompile all?
>From gcc-bugs-return-629388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:49:06 2019
Return-Path: <gcc-bugs-return-629388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52521 invoked by alias); 16 Jan 2019 11:49:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49652 invoked by uid 48); 16 Jan 2019 11:49:01 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Wed, 16 Jan 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80762-4-RR5Sv1RdEE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02197.txt.bz2
Content-length: 335
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
--- Comment #14 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hi Jonathan,
You're right, I was going off the results of a script but it doesn't seem to
have detected the change between FAIL -> UNSUPPORTED and left the state as
FAIL.
Sorry, I've manually checked it now.
>From gcc-bugs-return-629389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:49:25 2019
Return-Path: <gcc-bugs-return-629389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62004 invoked by alias); 16 Jan 2019 11:49: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 59100 invoked by uid 48); 16 Jan 2019 11:49:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 11:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88871-4-dRR01xK7gB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02198.txt.bz2
Content-length: 3523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
==16636== Invalid read of size 8
==16636== at 0x93E930: resolve_ref(gfc_expr*) (resolve.c:5058)
==16636== by 0x93FCFB: resolve_variable(gfc_expr*) (resolve.c:5536)
==16636== by 0x942C1E: gfc_resolve_expr(gfc_expr*) (resolve.c:6852)
==16636== by 0x94D1F0: gfc_resolve_code(gfc_code*, gfc_namespace*)
(resolve.c:11283)
==16636== by 0x95AB35: resolve_codes(gfc_namespace*) (resolve.c:16733)
==16636== by 0x95AC5F: gfc_resolve(gfc_namespace*) (resolve.c:16768)
==16636== by 0x92A436: resolve_all_program_units(gfc_namespace*)
(parse.c:6073)
==16636== by 0x92AC01: gfc_parse_file() (parse.c:6323)
==16636== by 0x989C74: gfc_be_parse_file() (f95-lang.c:204)
==16636== by 0x11F99D2: compile_file() (toplev.c:456)
==16636== by 0x11FC4F8: do_compile() (toplev.c:2176)
==16636== by 0x11FC7EB: toplev::main(int, char**) (toplev.c:2311)
==16636== Address 0x519cc98 is 728 bytes inside a block of size 736 free'd
==16636== at 0x4839A0C: free (vg_replace_malloc.c:540)
==16636== by 0x8ABA40: gfc_free_ref_list(gfc_ref*) (expr.c:606)
==16636== by 0x93E914: resolve_ref(gfc_expr*) (resolve.c:5082)
==16636== by 0x93FCFB: resolve_variable(gfc_expr*) (resolve.c:5536)
==16636== by 0x942C1E: gfc_resolve_expr(gfc_expr*) (resolve.c:6852)
==16636== by 0x94D1F0: gfc_resolve_code(gfc_code*, gfc_namespace*)
(resolve.c:11283)
==16636== by 0x95AB35: resolve_codes(gfc_namespace*) (resolve.c:16733)
==16636== by 0x95AC5F: gfc_resolve(gfc_namespace*) (resolve.c:16768)
==16636== by 0x92A436: resolve_all_program_units(gfc_namespace*)
(parse.c:6073)
==16636== by 0x92AC01: gfc_parse_file() (parse.c:6323)
==16636== by 0x989C74: gfc_be_parse_file() (f95-lang.c:204)
==16636== by 0x11F99D2: compile_file() (toplev.c:456)
==16636== Block was alloc'd at
==16636== at 0x483AB1A: calloc (vg_replace_malloc.c:762)
==16636== by 0x2194710: xcalloc (xmalloc.c:162)
==16636== by 0x92C245: match_substring(gfc_charlen*, int, gfc_ref**, bool)
(primary.c:861)
==16636== by 0x92F18B: gfc_match_varspec(gfc_expr*, int, bool, bool)
(primary.c:2428)
==16636== by 0x932B29: match_variable(gfc_expr**, int, int) (primary.c:3977)
==16636== by 0x932B7F: gfc_match_variable(gfc_expr**, int) (primary.c:3992)
==16636== by 0x8EB50B: gfc_match(char const*, ...) (match.c:1165)
==16636== by 0x8EBA5C: gfc_match_assignment() (match.c:1343)
==16636== by 0x91D87F: match_word(char const*, match (*)(), locus*)
(parse.c:65)
==16636== by 0x91E35D: decode_statement() (parse.c:361)
==16636== by 0x923453: next_fixed() (parse.c:1425)
==16636== by 0x923558: next_statement() (parse.c:1473)
>From gcc-bugs-return-629390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:50:37 2019
Return-Path: <gcc-bugs-return-629390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72972 invoked by alias); 16 Jan 2019 11:50: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 72874 invoked by uid 48); 16 Jan 2019 11:50:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/80762] is_constructible<filesystem::path, void> gives hard error with clang
Date: Wed, 16 Jan 2019 11:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80762-4-oEkEaoxw23@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80762-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02199.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80762
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #15 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Great, thanks for confirming it.
>From gcc-bugs-return-629391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 11:56:18 2019
Return-Path: <gcc-bugs-return-629391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91466 invoked by alias); 16 Jan 2019 11:56: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 91389 invoked by uid 48); 16 Jan 2019 11:56:13 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88856] [8/9 Regression] gfortran producing wrong code with -funroll-loops
Date: Wed, 16 Jan 2019 11:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88856-4-54qm6JAqwG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02200.txt.bz2
Content-length: 1245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88856
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2019-01-16
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, like that problematic source, all gfortran options used to compile that,
any needed modules too + stubbed whatever it calls and whatever is needed in
MAIN__ or main to reproduce, ideally with minimal dependencies.
If you know the exact problematic routine, see in the debugger how many times
it is called and in which invocation of the routine it misbehaves and try to
capture on which arguments it is called. If you don't know the exact
problematic routine, one can e.g. play with assembly bisection between
-funroll-loops and no -funroll-loops, rename .L* labels in one of them so that
it can be merged by hand more easily. I think gfortran doesn't have optimize
(0) attribute yet.
>From gcc-bugs-return-629392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 12:02:59 2019
Return-Path: <gcc-bugs-return-629392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16139 invoked by alias); 16 Jan 2019 12:02: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 16072 invoked by uid 48); 16 Jan 2019 12:02:55 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 12:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88871-4-kDpIW8sq8q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02201.txt.bz2
Content-length: 458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #6 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
Could be a result of my recent commit, r267953. I'll take a look tonight.
>From gcc-bugs-return-629393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 12:08:28 2019
Return-Path: <gcc-bugs-return-629393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68864 invoked by alias); 16 Jan 2019 12:08:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68775 invoked by uid 48); 16 Jan 2019 12:08:24 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 12:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-wBkp46Kfyr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02202.txt.bz2
Content-length: 394
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
--- Comment #7 from Jürgen Reuter <juergen.reuter at desy dot de> ---
(In reply to Thomas Koenig from comment #6)
> Could be a result of my recent commit, r267953. I'll take a look tonight.
That would be my guess, too,
I think it has to do with the array
descriptor together with implicit
typing and maybe together the common
block.
>From gcc-bugs-return-629394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 12:18:10 2019
Return-Path: <gcc-bugs-return-629394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110458 invoked by alias); 16 Jan 2019 12:18: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 110353 invoked by uid 48); 16 Jan 2019 12:18:04 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 12:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88871-4-ztZajGqTeB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02203.txt.bz2
Content-length: 775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
--- Comment #8 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> My suspicion goes toward the fix for PR81849
Debugger shows
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS
(code=EXC_I386_GPFLT)
frame #0: 0x00000001000b2e1d f951`::resolve_ref(expr=0x0000000142c1c580) at
resolve.c:5060
5057
5058
5059 for (ref = expr->ref, prev = &expr->ref; ref; prev = &ref->next, ref
= ref->next)
-> 5060 switch (ref->type)
5061 {
5062 case REF_ARRAY:
5063 if (!resolve_array_ref (&ref->u.ar))
so Il'd blame rather r267953.
The test gcc/testsuite/gfortran.dg/actual_array_substr_3.f90 fails at the same
place.
>From gcc-bugs-return-629395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 12:22:02 2019
Return-Path: <gcc-bugs-return-629395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127275 invoked by alias); 16 Jan 2019 12:22: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 125759 invoked by uid 48); 16 Jan 2019 12:21:58 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] New: [8 regression] initializer_list and explicit ctor
Date: Wed, 16 Jan 2019 12:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02204.txt.bz2
Content-length: 1503
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88875
Bug ID: 88875
Summary: [8 regression] initializer_list and explicit ctor
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: nathan at gcc dot gnu.org
Target Milestone: ---
Created attachment 45440
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45440&action=edit
testcase
We reject default member list initializers when the member has an explicit ctor
taking a list. We accept such an initialier on an explicit member initializer.
GCC-8 accepted this.
g++ -std=c++17 -c gb.cc -save-temps
gb.cc:10:14: error: converting to 'X' from initializer list would use explicit
constructor 'X::X(const std::initializer_list<int>&)'
10 | X x { 1, 2 }; // error
member initialization is direct-initialization:
The expression-list or braced-init-list in a mem-initializer is used to
initialize the designated subobject (or, in the case of a delegating
constructor, the complete class object) according to the initialization rules
of 9.3 for direct-initialization. [class.base.init]/7
/copy/-list-initialization prohibits resolving to an explicit-ctor:
In copy-list-initialization, if an explicit constructor is chosen, the
initialization is ill-formed. [over.match.list]/2
but there's no such restriction for direct initialization.
>From gcc-bugs-return-629396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 12:24:57 2019
Return-Path: <gcc-bugs-return-629396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130999 invoked by alias); 16 Jan 2019 12:24: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 130375 invoked by uid 48); 16 Jan 2019 12:24:22 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] [9 regression] initializer_list and explicit ctor
Date: Wed, 16 Jan 2019 12:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cf_known_to_work target_milestone short_desc everconfirmed
Message-ID: <bug-88875-4-XM0DZhYwPt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02205.txt.bz2
Content-length: 772
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88875
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
Known to work| |8.2.1
Target Milestone|--- |9.0
Summary|[8 regression] |[9 regression]
|initializer_list and |initializer_list and
|explicit ctor |explicit ctor
Ever confirmed|0 |1
>From gcc-bugs-return-629397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 12:49:06 2019
Return-Path: <gcc-bugs-return-629397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116813 invoked by alias); 16 Jan 2019 12:49: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 114801 invoked by uid 48); 16 Jan 2019 12:48:55 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] [9 regression] initializer_list and explicit ctor
Date: Wed, 16 Jan 2019 12:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88875-4-8Nxdp2TIlQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02206.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88875
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mpolacek at gcc dot gnu.org
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Started with r260126.
>From gcc-bugs-return-629398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:32:40 2019
Return-Path: <gcc-bugs-return-629398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19670 invoked by alias); 16 Jan 2019 13:32:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17068 invoked by uid 48); 16 Jan 2019 13:32:36 -0000
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88876] New: [9 regression] ICE in propagate_pure_const ipa-pure-const.c:1502
Date: Wed, 16 Jan 2019 13:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dimhen 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-88876-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02207.txt.bz2
Content-length: 1735
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88876
Bug ID: 88876
Summary: [9 regression] ICE in propagate_pure_const
ipa-pure-const.c:1502
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: lto
Assignee: unassigned at gcc dot gnu.org
Reporter: dimhen at gmail dot com
CC: marxin at gcc dot gnu.org
Target Milestone: ---
r261210 PASS
r261341 FAIL
r267961 FAIL
$ cat a.i
extern int c();
int a;
int b() {
if (a)
if (c())
return 0;
return 1;
}
#pragma GCC optimize "O0"
int c() {return 0;}
$ /usr/local/gcc_current/bin/gcc -fpreprocessed -O2 -fno-semantic-interposition
-fPIC -DPIC -flto -c a.i -o a.o
$ /usr/local/gcc_current/bin/gcc -fPIC -DPIC -shared -nostdlib -flto a.o
during IPA pass: pure-const
lto1: internal compiler error: Segmentation fault
0xec389f crash_signal
/home/dimhen/src/gcc_current/gcc/toplev.c:326
0x7f57c15535bf ???
/usr/src/debug/glibc-2.28-60-g4d7af7815a/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
0x184197e propagate_pure_const
/home/dimhen/src/gcc_current/gcc/ipa-pure-const.c:1502
0x184197e execute
/home/dimhen/src/gcc_current/gcc/ipa-pure-const.c:1991
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
lto-wrapper: fatal error: /usr/local/gcc_current/bin/gcc returned 1 exit status
compilation terminated.
/usr/local/binutils_current/bin/ld: error: lto-wrapper failed
collect2: error: ld returned 1 exit status
>From gcc-bugs-return-629399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:39:17 2019
Return-Path: <gcc-bugs-return-629399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63777 invoked by alias); 16 Jan 2019 13:39: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 63710 invoked by uid 48); 16 Jan 2019 13:39:12 -0000
From: "dimhen at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88876] [9 regression] ICE in propagate_pure_const ipa-pure-const.c:1502
Date: Wed, 16 Jan 2019 13:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dimhen 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-88876-4-yL0nL5Bppu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88876-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88876-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02208.txt.bz2
Content-length: 1020
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88876
--- Comment #1 from Dmitry G. Dyachenko <dimhen at gmail dot com> ---
$ /usr/local/gcc_current/bin/gcc -v
Using built-in specs.
COLLECT_GCC=/usr/local/gcc_current/bin/gcc
COLLECT_LTO_WRAPPER=/usr/local/gcc_current/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
Target: x86_64-pc-linux-gnu
Configured with: /home/dimhen/src/gcc_current/configure
--prefix=/usr/local/gcc_current --enable-checking=yes,df,fold,rtl,extra
--enable-languages=c,c++,lto --disable-multilib --enable-shared
--enable-threads=posix --enable-__cxa_atexit --disable-libunwind-exceptions
--enable-gnu-unique-object --enable-linker-build-id
--with-linker-hash-style=gnu --enable-plugin --enable-initfini-array --with-isl
--enable-libmpx --enable-offload-targets=nvptx-none --without-cuda-driver
--enable-gnu-indirect-function --with-tune=native
Thread model: posix
gcc version 9.0.0 20190116 (experimental) [trunk revision 267961] (GCC)
>From gcc-bugs-return-629400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:44:56 2019
Return-Path: <gcc-bugs-return-629400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51390 invoked by alias); 16 Jan 2019 13:44: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 42596 invoked by uid 48); 16 Jan 2019 13:44:52 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/88871] [9 regression] ICE segmentation fault in f951
Date: Wed, 16 Jan 2019 13:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority
Message-ID: <bug-88871-4-F8QYdKl8hL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88871-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02209.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88871
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
I've confirmed this started with r267953 (running under valgrind, otherwise it
doesn't reproduce for me).
>From gcc-bugs-return-629402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:46:21 2019
Return-Path: <gcc-bugs-return-629402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117118 invoked by alias); 16 Jan 2019 13:46: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 106355 invoked by uid 48); 16 Jan 2019 13:46:17 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88876] [9 regression] ICE in propagate_pure_const ipa-pure-const.c:1502
Date: Wed, 16 Jan 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority
Message-ID: <bug-88876-4-KtEPLSfMfZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88876-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88876-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02211.txt.bz2
Content-length: 361
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88876
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-valid-code
Priority|P3 |P1
>From gcc-bugs-return-629401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:46:10 2019
Return-Path: <gcc-bugs-return-629401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95602 invoked by alias); 16 Jan 2019 13:46:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80012 invoked by uid 48); 16 Jan 2019 13:46:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88876] [9 regression] ICE in propagate_pure_const ipa-pure-const.c:1502
Date: Wed, 16 Jan 2019 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work assigned_to target_milestone everconfirmed cf_known_to_fail
Message-ID: <bug-88876-4-4E66nrV5O8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88876-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88876-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02210.txt.bz2
Content-length: 770
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88876
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-16
Known to work| |8.2.0
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
Known to fail| |9.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with my commit r261322.
>From gcc-bugs-return-629403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:48:04 2019
Return-Path: <gcc-bugs-return-629403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31375 invoked by alias); 16 Jan 2019 13:48:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 31203 invoked by uid 48); 16 Jan 2019 13:47:58 -0000
From: "kamleshbhalui at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] New: rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 13:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kamleshbhalui 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-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02212.txt.bz2
Content-length: 1172
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
Bug ID: 88877
Summary: rs6000 emits signed extension for unsigned int
type(__floatunsidf).
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: kamleshbhalui at gmail dot com
Target Milestone: ---
consider below testcase:
$cat test.c
void foo(){
unsigned int x=-1;
double d=x;
}
$./cc1 test.c -msoft-float -m64
$cat test.s
.foo:
.LFB0:
mflr 0
std 0,16(1)
stdu 1,-128(1)
.LCFI0:
li 9,-1
stw 9,112(1)
lwa 9,112(1)
mr 3,9
bl .__floatunsidf
nop
mr 9,3
std 9,120(1)
nop
addi 1,1,128
.LCFI1:
ld 0,16(1)
mtlr 0
blr
.long 0
.byte 0,0,0,1,128,0,0,1
Here, you can see that sign extension before calling the __floatunsidf routine.
As per my understanding it should emit zero extension here because
__floatunsidf has its argument as unsigned int type.
>From gcc-bugs-return-629404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 13:56:32 2019
Return-Path: <gcc-bugs-return-629404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86100 invoked by alias); 16 Jan 2019 13:56:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85979 invoked by uid 48); 16 Jan 2019 13:56:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88869] [7/8/9 Regression] ICE (Segmentation Fault) when using lambda
Date: Wed, 16 Jan 2019 13:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.2.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88869-4-1Z6p9b3Q1c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88869-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02213.txt.bz2
Content-length: 722
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88869
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Note the auto return type on foo isn't important, it ICEs even with void foo ()
{ C ([] {}); }
The ICE is in
26858 tparms = DECL_TEMPLATE_PARMS (fn_tmpl);
26859 /* If type is a member class template, DECL_TI_ARGS (ctor) will
have
26860 fully specialized args for the enclosing class. Strip those
off, as
26861 the deduction guide won't have those template parameters. */
26862 targs = get_innermost_template_args (DECL_TI_ARGS (ctor),
26863 TMPL_PARMS_DEPTH
(tparms));
because tparms is NULL.
>From gcc-bugs-return-629405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:01:56 2019
Return-Path: <gcc-bugs-return-629405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92883 invoked by alias); 16 Jan 2019 14:01: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 92728 invoked by uid 48); 16 Jan 2019 14:01:46 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Wed, 16 Jan 2019 14:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-88684-4-n8VVW80KNs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02214.txt.bz2
Content-length: 1161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.0 |---
Summary|[7/8/9 Regression] Please |Please make
|make |SANITIZER_NON_UNIQUE_TYPEIN
|SANITIZER_NON_UNIQUE_TYPEIN |FO a runtime flag (or
|FO a runtime flag (or |always true)
|always true) |
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Why is this actually considered a regression?
While in GCC 6 and older libsanitizer didn't have SANITIZER_NON_UNIQUE_TYPEINFO
macro, it performed only == comparisons of the string pointers, so in the end
it acted as if the current default of SANITIZER_NON_UNIQUE_TYPEINFO. Not
suitable for libstdc++, sure, but not a regression.
That said, I'm willing to ack it for GCC9 even then if upstream comes up with
something or if they don't care, eventually as a GCC only tweak.
>From gcc-bugs-return-629406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:05:36 2019
Return-Path: <gcc-bugs-return-629406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101395 invoked by alias); 16 Jan 2019 14:05: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 101301 invoked by uid 48); 16 Jan 2019 14:05:32 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Wed, 16 Jan 2019 14:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-88684-4-s66FdSnkQI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02215.txt.bz2
Content-length: 583
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
--- Comment #10 from Martin Liška <marxin at gcc dot gnu.org> ---
> That said, I'm willing to ack it for GCC9 even then if upstream comes up
> with something or if they don't care, eventually as a GCC only tweak.
Works for me. Note that so far there has been no reply to my patch.
>From gcc-bugs-return-629408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:06:35 2019
Return-Path: <gcc-bugs-return-629408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103633 invoked by alias); 16 Jan 2019 14:06: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 103560 invoked by uid 48); 16 Jan 2019 14:06:30 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/86934] Feature test macros in <version> should respect _GLIBCXX_HOSTED
Date: Wed, 16 Jan 2019 14:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86934-4-cDdPrJrFWj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86934-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86934-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02217.txt.bz2
Content-length: 1155
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86934
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #1)
> That should be simple, just include <bits/stdc++.h> and <version> and
> compile with -Wsystem-headers to check for redefinition warnings.
As discussed on IRC,
for i in 98 11 14 17 2a; do echo '#include <bits/stdc++.h>' | g++
-D_GLIBCXX_VERSION_INCLUDED -E -std=c++$i -dD -xc++ - | grep
'^[[:blank:]]*#[[:blank:]]*define[[:blank:]]*__cpp_' | sort -u > /tmp/1; echo
'#include <version>' | g++ -E -std=c++$i -dD -xc++ - | grep
'^[[:blank:]]*#[[:blank:]]*define[[:blank:]]*__cpp_' | sort -u > /tmp/2; diff
-up /tmp/1 /tmp/2; done
is a more thorough way of checking not just the case where both <version> and
other headers define the same __cpp_lib* macro differently, but also when one
defines one and the other doesn't.
>From gcc-bugs-return-629407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:06:06 2019
Return-Path: <gcc-bugs-return-629407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102642 invoked by alias); 16 Jan 2019 14:06:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 102465 invoked by uid 48); 16 Jan 2019 14:06:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/49330] Integer arithmetic on addresses optimised with pointer arithmetic rules
Date: Wed, 16 Jan 2019 14:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 4.6.1
X-Bugzilla-Keywords: alias, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-49330-4-AuBgES6oRN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49330-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02216.txt.bz2
Content-length: 469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49330
--- Comment #25 from Richard Biener <rguenth at gcc dot gnu.org> ---
When considering the patch from comment#18 additional data is that only
95802 out of 636160 disambiguations that ultimately require base_alias_check
involve non-CONST_INT_P "other" operand. That is out of 9531871 total
cases that would run into base_alias_check, or 1%.
This is w/o "fixing" DSE (the simple patch of course miscompiles things).
>From gcc-bugs-return-629409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:07:05 2019
Return-Path: <gcc-bugs-return-629409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105075 invoked by alias); 16 Jan 2019 14:07:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104551 invoked by uid 48); 16 Jan 2019 14:06:59 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] [9 regression] initializer_list and explicit ctor
Date: Wed, 16 Jan 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: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88875-4-rsOxRbKLKW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02218.txt.bz2
Content-length: 248
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88875
--- Comment #2 from Nathan Sidwell <nathan at gcc dot gnu.org> ---
That change looks suspicious in its own right -- it ends up mutating the
initializer during the adding of overload candidates.
>From gcc-bugs-return-629410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:17:38 2019
Return-Path: <gcc-bugs-return-629410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71054 invoked by alias); 16 Jan 2019 14:17:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71006 invoked by uid 48); 16 Jan 2019 14:17:34 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Wed, 16 Jan 2019 14:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88861-4-TsnCBl3tRz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02219.txt.bz2
Content-length: 230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
--- Comment #5 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Cool, thanks! Is the plan to simply not allow something that can throw to be
recognised as noop move?
>From gcc-bugs-return-629411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:19:25 2019
Return-Path: <gcc-bugs-return-629411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73387 invoked by alias); 16 Jan 2019 14:19: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 73212 invoked by uid 55); 16 Jan 2019 14:19:20 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Wed, 16 Jan 2019 14:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88682-4-IQcdW7AHh6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02220.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 16 14:18:47 2019
New Revision: 267970
URL: https://gcc.gnu.org/viewcvs?rev=267970&root=gcc&view=rev
Log:
PR c/51628
PR target/88682
* c-c++-common/pr51628-10.c (unaligned_int128_t): Add
may_alias attribute.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/c-c++-common/pr51628-10.c
>From gcc-bugs-return-629412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:19:26 2019
Return-Path: <gcc-bugs-return-629412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73636 invoked by alias); 16 Jan 2019 14:19:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73287 invoked by uid 55); 16 Jan 2019 14:19:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/51628] __attribute__((packed)) is unsafe in some cases (i.e. add -Waddress-of-packed-member, etc.)
Date: Wed, 16 Jan 2019 14:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.5.1
X-Bugzilla-Keywords: diagnostic, patch, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51628-4-Io1noCuA2I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51628-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51628-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02221.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51628
--- Comment #60 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Wed Jan 16 14:18:47 2019
New Revision: 267970
URL: https://gcc.gnu.org/viewcvs?rev=267970&root=gcc&view=rev
Log:
PR c/51628
PR target/88682
* c-c++-common/pr51628-10.c (unaligned_int128_t): Add
may_alias attribute.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/c-c++-common/pr51628-10.c
>From gcc-bugs-return-629413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:28:17 2019
Return-Path: <gcc-bugs-return-629413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89097 invoked by alias); 16 Jan 2019 14:28: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 85384 invoked by uid 48); 16 Jan 2019 14:28:11 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Wed, 16 Jan 2019 14:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-MvHeiaJkWL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02222.txt.bz2
Content-length: 1270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #12 from Richard Biener <rguenth at gcc dot gnu.org> ---
OK, so C++ has
else if ((DECL_NAME (decl) == NULL_TREE)
&& TREE_CODE (decl) == NAMESPACE_DECL)
dump_decl (cxx_pp, decl, TFF_PLAIN_IDENTIFIER | TFF_UNQUALIFIED_NAME);
and thus "copes" with namespaces without a name. I wonder if we want
pubnames late at all. For darwin and other targets with "crippled"
early LTO support (read: no support) this means we'd not generate those
lookup entries.
Since we output_pubtables only from dwarf2out_finish (why?) we don't
get those into early debug. Sth to investigate.
The ICE can probably be fixed with the following - can you test that?
diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
index a1b5a5eaf19..cd2e889a8cc 100644
--- a/gcc/dwarf2out.c
+++ b/gcc/dwarf2out.c
@@ -11074,7 +11074,9 @@ output_comp_unit (dw_die_ref die, int output_if_empty,
static inline bool
want_pubnames (void)
{
- if (debug_info_level <= DINFO_LEVEL_TERSE)
+ if (debug_info_level <= DINFO_LEVEL_TERSE
+ /* Names and types go to the early debug part only. */
+ || in_lto_p)
return false;
if (debug_generate_pub_sections != -1)
return debug_generate_pub_sections;
>From gcc-bugs-return-629414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:29:19 2019
Return-Path: <gcc-bugs-return-629414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111050 invoked by alias); 16 Jan 2019 14:29: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 110971 invoked by uid 48); 16 Jan 2019 14:29:14 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88682] new test case c-c++-common/pr51628-10.c fails starting with its introduction in r267313
Date: Wed, 16 Jan 2019 14:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88682-4-NhGQejeuyE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02223.txt.bz2
Content-length: 423
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88682
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-629415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:31:20 2019
Return-Path: <gcc-bugs-return-629415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119335 invoked by alias); 16 Jan 2019 14:31:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119033 invoked by uid 48); 16 Jan 2019 14:30:39 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88875] [9 regression] initializer_list and explicit ctor
Date: Wed, 16 Jan 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-88875-4-PYNfS8PEod@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88875-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02224.txt.bz2
Content-length: 363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88875
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |jakub at gcc dot gnu.org
>From gcc-bugs-return-629416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:31:47 2019
Return-Path: <gcc-bugs-return-629416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121744 invoked by alias); 16 Jan 2019 14:31:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121665 invoked by uid 48); 16 Jan 2019 14:31:42 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88847] gcc.target/aarch64/sve/struct_move_1.c ICE with -fstack-protector-strong
Date: Wed, 16 Jan 2019 14:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88847-4-KdYBhRP5BE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88847-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02225.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88847
--- Comment #2 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Using stack protector created an invalid addressing mode.
It changes SP-64 into SP-80, presumably due to it storing the canary value.
However 80 is not a multple of SVE_BYTE_MODE (32) so the instruction can't
match.
We probably need to insert some padding after the canary is stored?
>From gcc-bugs-return-629417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:32:16 2019
Return-Path: <gcc-bugs-return-629417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122692 invoked by alias); 16 Jan 2019 14:32: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 122570 invoked by uid 48); 16 Jan 2019 14:32:07 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/70682] [9 Regression] -fcompare-debug building LLVM with checking=release compiler on ppc64le
Date: Wed, 16 Jan 2019 14:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords: deferred
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 10.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-70682-4-dRhwNkTUxa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02226.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70682
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|9.0 |10.0
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Too late to do it for GCC9 as well. The workaround is still in.
>From gcc-bugs-return-629418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:32:57 2019
Return-Path: <gcc-bugs-return-629418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123668 invoked by alias); 16 Jan 2019 14:32: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 123595 invoked by uid 48); 16 Jan 2019 14:32:53 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88878] New: .debug_pubnames/types empty with -flto
Date: Wed, 16 Jan 2019 14:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-88878-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02227.txt.bz2
Content-length: 702
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88878
Bug ID: 88878
Summary: .debug_pubnames/types empty with -flto
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
Currently building with -g -gpubnames -flto will get you an empty
.debug_pubnames
section because dwarf2out_early_finish doesn't emit those into the early debug
part (LTO section setup for pubnames is also missing).
Since -gpubtypes is off by default on linux nobody noticed sofar.
>From gcc-bugs-return-629419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:34:53 2019
Return-Path: <gcc-bugs-return-629419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66456 invoked by alias); 16 Jan 2019 14:34:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64235 invoked by uid 48); 16 Jan 2019 14:34:49 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Wed, 16 Jan 2019 14:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88861-4-FZADCfhGbs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02228.txt.bz2
Content-length: 398
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
--- Comment #6 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
(In reply to Segher Boessenkool from comment #5)
> Cool, thanks! Is the plan to simply not allow something that can throw to be
> recognised as noop move?
Candidate patch: https://gcc.gnu.org/ml/gcc-patches/2019-01/msg00914.html
(caveat: I'm relatively new to this code)
>From gcc-bugs-return-629420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:36:59 2019
Return-Path: <gcc-bugs-return-629420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82540 invoked by alias); 16 Jan 2019 14:36: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 82468 invoked by uid 48); 16 Jan 2019 14:36:55 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Wed, 16 Jan 2019 14:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-YSWUJiEbMk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02229.txt.bz2
Content-length: 557
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #17 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Without the #c11 patch (+ removal of the !INTEGRAL_TYPE_P special case from the
above committed change + fixing up ptrs_compare_unequal, or something
equivalent like the VRP change) I'm afraid there isn't much possibilities left
to do, and those changes are too risky for GCC9. The problem with your
testcase is that NRV is in place, so we don't even know if s is an automatic
variable or a global variable, or a heap variable etc.
>From gcc-bugs-return-629421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:39:03 2019
Return-Path: <gcc-bugs-return-629421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93642 invoked by alias); 16 Jan 2019 14:39:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 90917 invoked by uid 48); 16 Jan 2019 14:38:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] New: [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 14:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02230.txt.bz2
Content-length: 560
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
Bug ID: 88879
Summary: [9 Regression] ICE in sel_target_adjust_priority, at
sel-sched.c:3332
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: rguenth at gcc dot gnu.org
Target Milestone: ---
Building SPEC 2000 on Itanium ICEs left and right in
sel_target_adjust_priority.
>From gcc-bugs-return-629422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:42:36 2019
Return-Path: <gcc-bugs-return-629422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113343 invoked by alias); 16 Jan 2019 14:42:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113314 invoked by uid 48); 16 Jan 2019 14:42:31 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 14:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-88879-4-yiLJUTDZkp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02231.txt.bz2
Content-length: 4648
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 45441
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45441&action=edit
preprocessed source
/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/bin/gcc -c -o unlzw.o
-O3 unlzw.c -save-temps -v
Using built-in specs.
COLLECT_GCC=/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/bin/gcc
Target: ia64-unknown-linux-gnu
Configured with: /gcc/spec/sb-terbium-head-64/gcc/configure
--prefix=/gcc/spec/sb-terbium-head-64/ia64/install-201901161204
--enable-languages=c,c++,fortran --enable-threads=posix --disable-nls
--enable-__cxa_atexit --enable-clocale=gnu --enable-checking=release
--disable-libstdcxx-pch --disable-libsanitizer --disable-libcilkrts
--without-isl --disable-werror
Thread model: posix
gcc version 9.0.0 20190116 (experimental) [trunk revision 267969] (GCC)
COLLECT_GCC_OPTIONS='-c' '-o' 'unlzw.o' '-O3' '-save-temps' '-v'
/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/libexec/gcc/ia64-unknown-linux-gnu/9.0.0/cc1
-E -quiet -v unlzw.c -O3 -fpch-preprocess -o unlzw.i
ignoring nonexistent directory
"/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/lib/gcc/ia64-unknown-linux-gnu/9.0.0/../../../../ia64-unknown-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/lib/gcc/ia64-unknown-linux-gnu/9.0.0/include
/usr/local/include
/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/include
/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/lib/gcc/ia64-unknown-linux-gnu/9.0.0/include-fixed
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-c' '-o' 'unlzw.o' '-O3' '-save-temps' '-v'
/gcc/spec/sb-terbium-head-64/ia64/install-201901161204/libexec/gcc/ia64-unknown-linux-gnu/9.0.0/cc1
-fpreprocessed unlzw.i -quiet -dumpbase unlzw.c -auxbase-strip unlzw.o -O3
-version -o unlzw.s
GNU C17 (GCC) version 9.0.0 20190116 (experimental) [trunk revision 267969]
(ia64-unknown-linux-gnu)
compiled by GNU C version 9.0.0 20190116 (experimental) [trunk revision
267969], GMP version 5.0.5, MPFR version 3.1.0-p1, MPC version 0.8.2, isl
version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C17 (GCC) version 9.0.0 20190116 (experimental) [trunk revision 267969]
(ia64-unknown-linux-gnu)
compiled by GNU C version 9.0.0 20190116 (experimental) [trunk revision
267969], GMP version 5.0.5, MPFR version 3.1.0-p1, MPC version 0.8.2, isl
version none
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: b841429784bb4c1bcbfd81a8b6b2b964
unlzw.c: In function 'unlzw':
unlzw.c:261:19: warning: implicit declaration of function 'spec_read'
[-Wimplicit-function-declaration]
261 | if ((rsize = read(in, (char*)inbuf+insize, INBUFSIZ)) == EOF) {
| ^~~~~~~~~
during RTL pass: mach
unlzw.c:377:1: internal compiler error: in sel_target_adjust_priority, at
sel-sched.c:3332
377 | }
| ^
0x4000000000db257f sel_target_adjust_priority
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:3332
0x4000000000db257f fill_vec_av_set
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:3726
0x4000000000db34ff fill_ready_list
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:4027
0x4000000000db34ff find_best_expr
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:4387
0x4000000000db34ff fill_insns
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:5548
0x4000000000dba63f schedule_on_fences
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:7364
0x4000000000dba63f sel_sched_region_2
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:7502
0x4000000000dbedff sel_sched_region_1
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:7544
0x4000000000dc20ef sel_sched_region(int)
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:7645
0x4000000000dc20ef sel_sched_region(int)
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:7630
0x4000000000dc350f run_selective_scheduling()
/gcc/spec/sb-terbium-head-64/gcc/gcc/sel-sched.c:7731
0x4000000001583aaf ia64_reorg
/gcc/spec/sb-terbium-head-64/gcc/gcc/config/ia64/ia64.c:9857
0x4000000000d3274f execute
/gcc/spec/sb-terbium-head-64/gcc/gcc/reorg.c:3979
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-629423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:43:20 2019
Return-Path: <gcc-bugs-return-629423-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115323 invoked by alias); 16 Jan 2019 14:43: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 115005 invoked by uid 48); 16 Jan 2019 14:43:15 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 14:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget cc target_milestone
Message-ID: <bug-88879-4-BgF0ZdroVJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02232.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |ia64
CC| |amonakov at gcc dot gnu.org
Target Milestone|--- |9.0
>From gcc-bugs-return-629424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:46:51 2019
Return-Path: <gcc-bugs-return-629424-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20621 invoked by alias); 16 Jan 2019 14:46: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 20516 invoked by uid 48); 16 Jan 2019 14:46:41 -0000
From: "kamleshbhalui at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 14:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kamleshbhalui 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-88877-4-yUOUzIU08s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02233.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
--- Comment #1 from Kamlesh Kumar <kamleshbhalui at gmail dot com> ---
Following patch fixes the problem but would like to know the experts thought on
the below patch .
static machine_mode
-rs6000_promote_function_mode (const_tree type ATTRIBUTE_UNUSED,
+rs6000_promote_function_mode (const_tree type ,
machine_mode mode,
- int *punsignedp ATTRIBUTE_UNUSED,
+ int *punsignedp ,
const_tree, int)
{
+ if(type)
PROMOTE_MODE (mode, *punsignedp, type);
-
return mode;
}
Here, argument 'type' being null signifies that it's a libcalls.
So we will not promote the mode in this case,is that ok ?
>From gcc-bugs-return-629425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:47:32 2019
Return-Path: <gcc-bugs-return-629425-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21835 invoked by alias); 16 Jan 2019 14:47:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21758 invoked by uid 48); 16 Jan 2019 14:47:28 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 14:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88879-4-q6Kyoj5BwZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02234.txt.bz2
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
A little detail is that host GCC is GCC 4.1.2 which happened to miscompile GCC
itself for quite a while (but now somehow we're back).
>From gcc-bugs-return-629426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:51:18 2019
Return-Path: <gcc-bugs-return-629426-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26872 invoked by alias); 16 Jan 2019 14:51: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 26813 invoked by uid 48); 16 Jan 2019 14:51:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 14:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88879-4-qagzqdGmq1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02235.txt.bz2
Content-length: 524
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
Ever confirmed|0 |1
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
I can reproduce it with a cross from x86_64-linux.
>From gcc-bugs-return-629427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:56:51 2019
Return-Path: <gcc-bugs-return-629427-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66963 invoked by alias); 16 Jan 2019 14:56:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62770 invoked by uid 48); 16 Jan 2019 14:56:46 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 14:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-88877-4-OgKjIFA8tU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02236.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ABI
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you provide what the ABI says here?
>From my memory it says it sign extended into 64bits but I could be wrong. I
know the AARCH64 ABI says the top 32bits are undefined but that is not the
powerpc64 ABI.
>From gcc-bugs-return-629428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 14:58:18 2019
Return-Path: <gcc-bugs-return-629428-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88636 invoked by alias); 16 Jan 2019 14:58: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 88558 invoked by uid 48); 16 Jan 2019 14:58:11 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88859] [8/9 Regression] FAIL: experimental/string_view/operators/wchar_t/2.cc execution test
Date: Wed, 16 Jan 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: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status see_also resolution
Message-ID: <bug-88859-4-d2QC3m4kco@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02237.txt.bz2
Content-length: 643
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88859
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
See Also| |https://sourceware.org/bugz
| |illa/show_bug.cgi?id=24097
Resolution|--- |MOVED
--- Comment #7 from H.J. Lu <hjl.tools at gmail dot com> ---
This is a glibc bug:
https://sourceware.org/bugzilla/show_bug.cgi?id=24097
>From gcc-bugs-return-629429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:16:03 2019
Return-Path: <gcc-bugs-return-629429-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53069 invoked by alias); 16 Jan 2019 15:15: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 47000 invoked by uid 48); 16 Jan 2019 15:15:18 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88865] [[no_unique_address]] leads to sizeof(T) == 0, which cannot be
Date: Wed, 16 Jan 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: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ABI, wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-88865-4-0iR9v9TuJA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02238.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88865
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
Ever confirmed|0 |1
>From gcc-bugs-return-629430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:18:46 2019
Return-Path: <gcc-bugs-return-629430-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 57743 invoked by alias); 16 Jan 2019 15:18:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 57655 invoked by uid 55); 16 Jan 2019 15:18:40 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Wed, 16 Jan 2019 15:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-5EeUhBxuwR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02239.txt.bz2
Content-length: 2944
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #11 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Wed Jan 16 15:18:05 2019
New Revision: 267971
URL: https://gcc.gnu.org/viewcvs?rev=267971&root=gcc&view=rev
Log:
__builtin_<add/sub>_overflow issues on AArch64 (redux)
Further investigation showed that my previous patch for this issue was
still incomplete.
The problem stemmed from what I suspect was a mis-understanding of the
way overflow is calculated on aarch64 when values are subtracted (and
hence in comparisons). In this case, unlike addition, the carry flag
is /cleared/ if there is overflow (technically, underflow) and set
when that does not happen. This patch clears up this issue by using
CCmode for all subtractive operations (this can fully describe the
normal overflow conditions without anything particularly fancy);
clears up the way we express normal unsigned overflow using CC_Cmode
(the result of a sum is less than one of the operands) and adds a new
mode, CC_ADCmode to handle expressing overflow of an add-with-carry
operation, where the standard idiom is no-longer sufficient to
describe the overflow condition.
PR target/86891
* config/aarch64/aarch64-modes.def: Add comment about how the carry
bit is set by add and compare.
(CC_ADC): New CC_MODE.
* config/aarch64/aarch64.c (aarch64_select_cc_mode): Use variables
to cache the code and mode of X. Adjust the shape of a CC_Cmode
comparison. Add detection for CC_ADCmode.
(aarch64_get_condition_code_1): Update code support for CC_Cmode. Add
CC_ADCmode.
* config/aarch64/aarch64.md (uaddv<mode>4): Use LTU with CCmode.
(uaddvti4): Comparison result is in CC_ADCmode and the condition is
GEU.
(add<mode>3_compareC_cconly_imm): Delete. Merge into...
(add<mode>3_compareC_cconly): ... this. Restructure the comparison
to eliminate the need for zero-extending the operands.
(add<mode>3_compareC_imm): Delete. Merge into ...
(add<mode>3_compareC): ... this. Restructure the comparison to
eliminate the need for zero-extending the operands.
(add<mode>3_carryin): Use LTU for the overflow detection.
(add<mode>3_carryinC): Use CC_ADCmode for the result of the carry out.
Reexpress comparison for overflow.
(add<mode>3_carryinC_zero): Update for change to add<mode>3_carryinC.
(add<mode>3_carryinC): Likewise.
(add<mode>3_carryinV): Use LTU for carry between partials.
* config/aarch64/predicates.md (aarch64_carry_operation): Update
handling of CC_Cmode and add CC_ADCmode.
(aarch64_borrow_operation): Likewise.
Modified:
trunk/gcc/config/aarch64/aarch64-modes.def
trunk/gcc/config/aarch64/aarch64.c
trunk/gcc/config/aarch64/aarch64.md
trunk/gcc/config/aarch64/predicates.md
>From gcc-bugs-return-629431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:20:01 2019
Return-Path: <gcc-bugs-return-629431-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60531 invoked by alias); 16 Jan 2019 15:20: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 60453 invoked by uid 48); 16 Jan 2019 15:19:57 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 15:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: umesh.kalappa0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88877-4-g5C1tXMhov@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02240.txt.bz2
Content-length: 695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
Umesh Kalappa <umesh.kalappa0 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |umesh.kalappa0 at gmail dot com
--- Comment #3 from Umesh Kalappa <umesh.kalappa0 at gmail dot com> ---
https://members.openpowerfoundation.org/document/dl/576
it says we infer that,
Map simple integer types (char, short, int, long, enum) to a single doubleword.
Sign or zero extend values shorter than a doubleword to a doubleword based on
whether the source data type is signed or unsigned.
>From gcc-bugs-return-629432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:21:34 2019
Return-Path: <gcc-bugs-return-629432-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63307 invoked by alias); 16 Jan 2019 15:21: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 63245 invoked by uid 48); 16 Jan 2019 15:21:29 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] New: Wrong code since r264897
Date: Wed, 16 Jan 2019 15:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02241.txt.bz2
Content-length: 692
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
Bug ID: 88880
Summary: Wrong code since r264897
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
Target Milestone: ---
Created attachment 45442
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45442&action=edit
test-case
The test-case is isolated from OpenBLAS library.
$ gcc /tmp/blast.c -g -O2 && ./a.out
-9280:2.47 != 1.23
Aborted (core dumped)
>From gcc-bugs-return-629434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:22:25 2019
Return-Path: <gcc-bugs-return-629434-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65335 invoked by alias); 16 Jan 2019 15:22:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65267 invoked by uid 48); 16 Jan 2019 15:22:20 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on cc cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-88880-4-yiLxP8Xxix@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02243.txt.bz2
Content-length: 676
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2019-1-16
CC| |bergner at gcc dot gnu.org
Known to work| |8.2.0
Target Milestone|--- |9.0
Summary|Wrong code since r264897 |[9 Regression] Wrong code
| |since r264897
Known to fail| |9.0
>From gcc-bugs-return-629435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:22:46 2019
Return-Path: <gcc-bugs-return-629435-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67513 invoked by alias); 16 Jan 2019 15:22:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66977 invoked by uid 48); 16 Jan 2019 15:22:40 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority cc
Message-ID: <bug-88880-4-jY5bSznwFh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02244.txt.bz2
Content-length: 366
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |law at gcc dot gnu.org
>From gcc-bugs-return-629433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:22:14 2019
Return-Path: <gcc-bugs-return-629433-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64616 invoked by alias); 16 Jan 2019 15:22: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 64343 invoked by uid 48); 16 Jan 2019 15:22:10 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88881] New: std::filesystem::status gives bad results on mingw32
Date: Wed, 16 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88881-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02242.txt.bz2
Content-length: 1274
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88881
Bug ID: 88881
Summary: std::filesystem::status gives bad results on mingw32
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
// { dg-options "-std=gnu++17" }
#include <filesystem>
#include <iostream>
void print_status(std::filesystem::path p)
{
std::cout << p << " exists? " << std::boolalpha << exists(p) << '\n';
}
int main()
{
print_status("./");
print_status("./nonexistent-path/..");
print_status("./nonexistent-path/../");
}
This prints:
"./" exists? false
"./nonexistent-path/.." exists? true
"./nonexistent-path/../" exists? false
It seems that mingw's stat() fails for a directory with a trailing slash.
It also implicitly resolves .. components, without consideration for whether
the previous component exists or not (which seems consistent with DOS commands,
e.g. "cd .\kgjhfjfj\.." is equivalent to "cd .", but is not how stat is
supposed to work).
I'll report these to mingw32-w64 but will need to add workarounds to
std::filesystem.
>From gcc-bugs-return-629436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:22:56 2019
Return-Path: <gcc-bugs-return-629436-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68322 invoked by alias); 16 Jan 2019 15:22: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 67923 invoked by uid 55); 16 Jan 2019 15:22:49 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/86891] [9 Regression] __builtin_sub_overflow incorrect for unsigned types
Date: Wed, 16 Jan 2019 15:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86891-4-mnfanxoa4E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02245.txt.bz2
Content-length: 411
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86891
--- Comment #12 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Wed Jan 16 15:22:08 2019
New Revision: 267972
URL: https://gcc.gnu.org/viewcvs?rev=267972&root=gcc&view=rev
Log:
__builtin_<add/sub>_overflow issues on AArch64 (redux) (cont)
And the ChangeLog for PR target/86891 fix.
Modified:
trunk/gcc/ChangeLog
>From gcc-bugs-return-629438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:23:53 2019
Return-Path: <gcc-bugs-return-629438-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70424 invoked by alias); 16 Jan 2019 15:23: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 70156 invoked by uid 48); 16 Jan 2019 15:23:48 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/86736] [9 regression] g++.dg/asan/pr81021.C -O2 -flto -flto-partition=none ICE at dwarf2out.c:31111
Date: Wed, 16 Jan 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-86736-4-HDFDsI7Cfk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86736-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02247.txt.bz2
Content-length: 2029
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86736
--- Comment #13 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #12)
> OK, so C++ has
>
> else if ((DECL_NAME (decl) == NULL_TREE)
> && TREE_CODE (decl) == NAMESPACE_DECL)
> dump_decl (cxx_pp, decl, TFF_PLAIN_IDENTIFIER | TFF_UNQUALIFIED_NAME);
>
> and thus "copes" with namespaces without a name. I wonder if we want
> pubnames late at all. For darwin and other targets with "crippled"
> early LTO support (read: no support)
FWIW, I've implemented the GCC part of the support (it needs a bit of tidying
for posting, but [probably] not a stage #4 thing). Also discussed the required
support in dsymutil with one of the devs (there seems no objection to doing
this, in principle)... so it's "when" rather than "if".
... progress on new features and enhancements for Darwin will go quicker if we
can squish the codegen and testsuite bugs (which is where the effort is going
at present) ;)
> this means we'd not generate those lookup entries.
>
> Since we output_pubtables only from dwarf2out_finish (why?) we don't
> get those into early debug. Sth to investigate.
my (limited) understanding of the purpose is to improve startup time for debug
sessions, so possibly relevant outside of darwin?
> The ICE can probably be fixed with the following - can you test that?
yes, that fixes it (only tested c++ asan).
>
> diff --git a/gcc/dwarf2out.c b/gcc/dwarf2out.c
> index a1b5a5eaf19..cd2e889a8cc 100644
> --- a/gcc/dwarf2out.c
> +++ b/gcc/dwarf2out.c
> @@ -11074,7 +11074,9 @@ output_comp_unit (dw_die_ref die, int
> output_if_empty,
> static inline bool
> want_pubnames (void)
> {
> - if (debug_info_level <= DINFO_LEVEL_TERSE)
> + if (debug_info_level <= DINFO_LEVEL_TERSE
> + /* Names and types go to the early debug part only. */
> + || in_lto_p)
> return false;
> if (debug_generate_pub_sections != -1)
> return debug_generate_pub_sections;
>From gcc-bugs-return-629437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:23:39 2019
Return-Path: <gcc-bugs-return-629437-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69272 invoked by alias); 16 Jan 2019 15:23:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69236 invoked by uid 48); 16 Jan 2019 15:23:34 -0000
From: "qrzhang at gatech dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88882] New: gcc generates wrong debug information at -O1
Date: Wed, 16 Jan 2019 15:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: qrzhang at gatech dot edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88882-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02246.txt.bz2
Content-length: 1849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88882
Bug ID: 88882
Summary: gcc generates wrong debug information at -O1
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: qrzhang at gatech dot edu
Target Milestone: ---
It incorrectly prints "l = 0" at -O1. CC'ing alex..
$ gcc-trunk -v
Using built-in specs.
COLLECT_GCC=gcc-trunk
COLLECT_LTO_WRAPPER=/home/absozero/trunk/root-gcc/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../gcc/configure --prefix=/home/absozero/trunk/root-gcc
--enable-languages=c,c++ --disable-werror --enable-multilib
Thread model: posix
gcc version 9.0.0 20181224 (experimental) [trunk revision 267411] (GCC)
$ gdb-trunk -v
GNU gdb (GDB) 8.2.50.20181223-git
It prints "l = 2" without optimization.
$ gcc-trunk -g abc.c outer.c
$ gdb-trunk -x cmds -batch a.out
Breakpoint 1 at 0x40048e: file abc.c, line 9.
Breakpoint 1, main () at abc.c:9
9 optimize_me_not();
$1 = 2
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 11426) killed]
It incorrectly prints "l = 0" at -O1.
$ gcc-trunk -g abc.c outer.c -O1
$ gdb-trunk -x cmds -batch a.out
Breakpoint 1 at 0x400489: file abc.c, line 9.
Breakpoint 1, main () at abc.c:9
9 optimize_me_not();
$1 = 0
Kill the program being debugged? (y or n) [answered Y; input not from terminal]
[Inferior 1 (process 11440) killed]
$ cat abc.c
int a;
int b;
int c;
int main() {
for (; b;)
;
int l = 2;
for (; c < 2; c++)
optimize_me_not();
l = a;
}
$ cat outer.c
optimize_me_not() {}
$ cat cmds
b 9
r
p l
k
q
>From gcc-bugs-return-629439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:25:41 2019
Return-Path: <gcc-bugs-return-629439-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72982 invoked by alias); 16 Jan 2019 15:25: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 72796 invoked by uid 48); 16 Jan 2019 15:25:23 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88880-4-RBo9ielshe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02248.txt.bz2
Content-length: 163
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
That inline asm looks big and suspicious.
>From gcc-bugs-return-629440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:26:42 2019
Return-Path: <gcc-bugs-return-629440-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75763 invoked by alias); 16 Jan 2019 15:26: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 75642 invoked by uid 48); 16 Jan 2019 15:26:37 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 15:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88877-4-oaFFwRbAe5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02249.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
--- Comment #4 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
"Values shorter than 32 bits are sign-extended or zero-extended, depending on
whether they are signed or unsigned." Source:
https://www.polyomino.org.uk/publications/2011/Power-Arch-32-bit-ABI-supp-1.0-Embedded.pdf,
p.33.
The same is true of the 64-bit ABIs, both ELFv1 and ELFv2.
>From gcc-bugs-return-629442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:27:41 2019
Return-Path: <gcc-bugs-return-629442-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107394 invoked by alias); 16 Jan 2019 15:27: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 104991 invoked by uid 48); 16 Jan 2019 15:27:37 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88880-4-iMcYyj8AQq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02251.txt.bz2
Content-length: 206
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
The inline asm modifies the 0th and 1st operands. I think the inline asm is
broken .
>From gcc-bugs-return-629441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:27:13 2019
Return-Path: <gcc-bugs-return-629441-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91892 invoked by alias); 16 Jan 2019 15:27:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88761 invoked by uid 48); 16 Jan 2019 15:27:08 -0000
From: "pexu@gcc-bugzilla.mail.kapsi.fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/88883] New: [AArch64] gcc/config/aarch64/aarch64.opt: aarch64_branch_protection_string type
Date: Wed, 16 Jan 2019 15:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: driver
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pexu@gcc-bugzilla.mail.kapsi.fi
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-88883-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02250.txt.bz2
Content-length: 1753
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88883
Bug ID: 88883
Summary: [AArch64] gcc/config/aarch64/aarch64.opt:
aarch64_branch_protection_string type
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: driver
Assignee: unassigned at gcc dot gnu.org
Reporter: pexu@gcc-bugzilla.mail.kapsi.fi
Target Milestone: ---
Host: x86_64-w64-mingw32
Target: aarch64-none-elf
Build: x86_64-linux-gnu
Hi.
It appears that when trying to build an x86_64-w64-mingw32 cross compiler
targetting AArch64 the build fails at generated `gcc/options-save.c' due to
narrowing conversion (using the latest trunk). This has likely something to do
with the latest branch protection patches.
The generated code looks like this (generated by `gcc/optc-save-gen.awk'):
if (ptr->x_aarch64_branch_protection_string)
fprintf (file, "%*s%s (%#lx)\n",
indent, "",
"aarch64_branch_protection_string",
(unsigned long)ptr->x_aarch64_branch_protection_string);
And this will cause something like:
options-save.c:nnnn:mm: error: cast from 'const char*' to 'long unsigned int'
loses precision [-fpermissive]
(unsigned long)ptr->x_aarch64_branch_protection_string);
I'm not sure who is the real culprit here. Should the generated options saving
code handle narrowing conversions better, or, as the above cast is only done
for any option that does not fall under char, short, int, enum or /string/
types is this caused by a mishap when selecting the proper type for
aarch64_branch_protection_string (at aarch64.opt)?
>From gcc-bugs-return-629443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:28:47 2019
Return-Path: <gcc-bugs-return-629443-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129624 invoked by alias); 16 Jan 2019 15:28: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 127253 invoked by uid 48); 16 Jan 2019 15:28:43 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 15:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88877-4-5XddTizRZc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02252.txt.bz2
Content-length: 606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
Bill Schmidt <wschmidt at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wschmidt at gcc dot gnu.org
--- Comment #5 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
So technically, if the target is 32-bit powerpc, the ABI is silent on the upper
32 bits. That's not necessarily a reasonable position to stand on, but when
targeting powerpc (not powerpc64*) those bits are meaningless.
>From gcc-bugs-return-629444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:38:10 2019
Return-Path: <gcc-bugs-return-629444-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119231 invoked by alias); 16 Jan 2019 15:38:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119155 invoked by uid 55); 16 Jan 2019 15:38:05 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88214] ICE in bitmap_intersect_p() on 32-bit BE platforms
Date: Wed, 16 Jan 2019 15:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 7.3.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88214-4-7hWyrDjQuo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02253.txt.bz2
Content-length: 857
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88214
--- Comment #11 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Wed Jan 16 15:37:33 2019
New Revision: 267974
URL: https://gcc.gnu.org/viewcvs?rev=267974&root=gcc&view=rev
Log:
[PR 88214] Check that an argument is a pointer
2019-01-16 Martin Jambor <mjambor@suse.cz>
Backported from mainline
2018-12-10 Martin Jambor <mjambor@suse.cz>
PR ipa/88214
* ipa-prop.c (determine_locally_known_aggregate_parts): Make sure
we check pointers against pointers.
testsuite/
* gcc.dg/ipa/pr88214.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.dg/ipa/pr88214.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/ipa-prop.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:38:52 2019
Return-Path: <gcc-bugs-return-629445-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2165 invoked by alias); 16 Jan 2019 15:38: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 125547 invoked by uid 48); 16 Jan 2019 15:38:45 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Wed, 16 Jan 2019 15:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88815-4-lxUzidtf69@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02254.txt.bz2
Content-length: 1554
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
--- Comment #4 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
There can be three scenarios:
1) decltype is in a template and it has no dependent expressions -- PROBLEM
- we call finish_compound_literal from cp_parser_functional_cast
- processing_template_decl is 1, so we just return compound_literal; without
calling check_narrowing
- then we call finish_decltype_type, EXPR is {NON_LVALUE_EXPR <2.0e+0>} but
that is not instantiation_dependent_uneval_expression_p, so we just take its
unlowered_expr_type and return it, without calling check_narrowing.
2) decltype is in a template and has dependent expressions
- we call finish_compound_literal from cp_parser_functional_cast
- processing_template_decl is 1, so we just return compound_literal; without
calling check_narrowing
- then we call finish_decltype_type, EXPR is
instantiation_dependent_uneval_expression_p, so we create DECLTYPE_TYPE with
the dependent expression
- tsubst_copy_and_build then calls
RETURN (finish_compound_literal (type, r, complain, cl));
while substituting the CONSTRUCTOR. Now processing_template_decl is 0, so
finish_compound_literal calls check_narrowing, so we detect it.
3) decltype is not in a template
- we call finish_compound_literal from cp_parser_functional_cast, but
processing_template_decl is 0, so we call check_narrowing so we detect it.
So one idea would to be to walk_tree on the expression at the end of
finish_decltype_type, looking for compound literals and call check_narrowing.
>From gcc-bugs-return-629446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:41:44 2019
Return-Path: <gcc-bugs-return-629446-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 34521 invoked by alias); 16 Jan 2019 15:41: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 34419 invoked by uid 55); 16 Jan 2019 15:41:39 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/88214] ICE in bitmap_intersect_p() on 32-bit BE platforms
Date: Wed, 16 Jan 2019 15:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 7.3.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88214-4-fndxjIzu7Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02255.txt.bz2
Content-length: 857
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88214
--- Comment #12 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Wed Jan 16 15:41:07 2019
New Revision: 267975
URL: https://gcc.gnu.org/viewcvs?rev=267975&root=gcc&view=rev
Log:
[PR 88214] Check that an argument is a pointer
2019-01-16 Martin Jambor <mjambor@suse.cz>
Backported from mainline
2018-12-10 Martin Jambor <mjambor@suse.cz>
PR ipa/88214
* ipa-prop.c (determine_locally_known_aggregate_parts): Make sure
we check pointers against pointers.
testsuite/
* gcc.dg/ipa/pr88214.c: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gcc.dg/ipa/pr88214.c
Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/ipa-prop.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:44:04 2019
Return-Path: <gcc-bugs-return-629447-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45174 invoked by alias); 16 Jan 2019 15:44:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45042 invoked by uid 48); 16 Jan 2019 15:44:00 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Wed, 16 Jan 2019 15:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88815-4-56QHlDGlpD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02256.txt.bz2
Content-length: 214
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
--- Comment #5 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(My proof-of-concept patch to deal with narrowing in decltype fixed this PR as
a result.)
>From gcc-bugs-return-629448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:47:29 2019
Return-Path: <gcc-bugs-return-629448-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28380 invoked by alias); 16 Jan 2019 15:47: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 25821 invoked by uid 48); 16 Jan 2019 15:47:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88880-4-3kX4AVTjwv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02257.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> The inline asm modifies the 0th and 1st operands. I think the inline asm is
> broken .
You are right, they are modified. Can you please help me how to fix the
assembly (marking these 2 as output as well)?
>From gcc-bugs-return-629450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:48:58 2019
Return-Path: <gcc-bugs-return-629450-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70979 invoked by alias); 16 Jan 2019 15:48:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67258 invoked by uid 48); 16 Jan 2019 15:48:52 -0000
From: "amonakov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 15:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88879-4-oT7GNwpiH1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02259.txt.bz2
Content-length: 1047
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
Alexander Monakov <amonakov at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |abel at gcc dot gnu.org
--- Comment #4 from Alexander Monakov <amonakov at gcc dot gnu.org> ---
Thanks. This broke when the patch for PR 85458 was applied, and Andreas raised
it on the gcc-patches thread:
https://gcc.gnu.org/ml/gcc-patches/2018-09/msg00128.html
Soon after that, the HP-PA adjust_priority target hook was removed, making the
sel-sched change unnecessary. Therefore, my recommendation is to revert the
sel-sched patch, or remove the new assert as Andreas has suggested. Andrey,
which approach would you prefer?
It's also possible to implement Jeff's suggestion and clamp negative priorities
to zero in create_speculation_check, but that may turn out to be insufficient
if there is other code producing negative priority values.
>From gcc-bugs-return-629449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:48:58 2019
Return-Path: <gcc-bugs-return-629449-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70780 invoked by alias); 16 Jan 2019 15:48:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68040 invoked by uid 48); 16 Jan 2019 15:48:53 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc everconfirmed
Message-ID: <bug-88880-4-ihxGYZxIhO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02258.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
CC| |law at redhat dot com
Ever confirmed|0 |1
>From gcc-bugs-return-629451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:52:09 2019
Return-Path: <gcc-bugs-return-629451-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61064 invoked by alias); 16 Jan 2019 15:52: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 60987 invoked by uid 48); 16 Jan 2019 15:52:05 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88879] [9 Regression] ICE in sel_target_adjust_priority, at sel-sched.c:3332
Date: Wed, 16 Jan 2019 15:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-88879-4-LqbooQiedv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88879-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02260.txt.bz2
Content-length: 1245
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88879
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Created attachment 45443
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45443&action=edit
Reduced test case
This ICEs with -O3 at the same place.
3332 gcc_assert (new_priority >= 0);
where:
3321 static int
3322 sel_target_adjust_priority (expr_t expr)
3323 {
3324 int priority = EXPR_PRIORITY (expr);
3325 int new_priority;
3326
3327 if (targetm.sched.adjust_priority)
3328 new_priority = targetm.sched.adjust_priority (EXPR_INSN_RTX (expr),
priority);
3329 else
3330 new_priority = priority;
3331
3332 gcc_assert (new_priority >= 0);
(gdb) p expr->priority
$7 = -1
(gdb) p new_priority
$8 = -1
(gdb) (gdb) p targetm.sched.adjust_priority
Undefined command: "". Try "help".
(gdb) p targetm.sched.adjust_priority
$9 = (int (*)(rtx_insn *, int)) 0x0
>From gcc-bugs-return-629452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:53:02 2019
Return-Path: <gcc-bugs-return-629452-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62436 invoked by alias); 16 Jan 2019 15:53:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 62307 invoked by uid 48); 16 Jan 2019 15:52:58 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88880-4-WjovY7DcrV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02261.txt.bz2
Content-length: 225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Replace:
:
:
"r" (i),
"r" (n),
With:
:
"+r" (i),
"+r" (n),
:
>From gcc-bugs-return-629453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:55:14 2019
Return-Path: <gcc-bugs-return-629453-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65309 invoked by alias); 16 Jan 2019 15:55:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 65213 invoked by uid 48); 16 Jan 2019 15:55:10 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Wed, 16 Jan 2019 15:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88815-4-r51DPdmABh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02262.txt.bz2
Content-length: 243
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
And of course r265789 changed int{(p(), 0U)} from being dependent to being
non-dependent, so scenario 2) to scenario 1).
>From gcc-bugs-return-629454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:56:18 2019
Return-Path: <gcc-bugs-return-629454-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68425 invoked by alias); 16 Jan 2019 15:56:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68331 invoked by uid 48); 16 Jan 2019 15:56:13 -0000
From: "rafael at espindo dot la" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/88684] Please make SANITIZER_NON_UNIQUE_TYPEINFO a runtime flag (or always true)
Date: Wed, 16 Jan 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: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rafael at espindo dot la
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88684-4-GOGxxJ0ABE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88684-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02263.txt.bz2
Content-length: 467
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88684
--- Comment #11 from Rafael Avila de Espindola <rafael at espindo dot la> ---
(In reply to Martin Liška from comment #10)
> > That said, I'm willing to ack it for GCC9 even then if upstream comes up
> > with something or if they don't care, eventually as a GCC only tweak.
>
> Works for me. Note that so far there has been no reply to my patch.
You might want to CC:
Filipe Cabecinhas <me@filcab.net>
>From gcc-bugs-return-629455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:57:34 2019
Return-Path: <gcc-bugs-return-629455-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103820 invoked by alias); 16 Jan 2019 15:57:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103747 invoked by uid 48); 16 Jan 2019 15:57:30 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 15:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88880-4-G2rhxEJHbe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02264.txt.bz2
Content-length: 681
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> Replace:
> :
> :
> "r" (i),
> "r" (n),
>
> With:
> :
> "+r" (i),
> "+r" (n),
> :
I can confirm it works, thus it's failure in the package. Let me report that.
>From gcc-bugs-return-629456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 15:59:11 2019
Return-Path: <gcc-bugs-return-629456-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110318 invoked by alias); 16 Jan 2019 15:59: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 110214 invoked by uid 55); 16 Jan 2019 15:59:07 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/78244] Narrowing conversion is accepted in a function template, but it should be rejected
Date: Wed, 16 Jan 2019 15: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: 6.2.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-78244-4-SRVIdXVxKq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78244-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78244-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02265.txt.bz2
Content-length: 895
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78244
--- Comment #9 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed Jan 16 15:58:34 2019
New Revision: 267976
URL: https://gcc.gnu.org/viewcvs?rev=267976&root=gcc&view=rev
Log:
PR c++/78244 - narrowing conversion in template not detected.
* call.c (perform_implicit_conversion_flags): Set
IMPLICIT_CONV_EXPR_BRACED_INIT.
* cp-tree.h (IMPLICIT_CONV_EXPR_BRACED_INIT): New.
* pt.c (tsubst_copy_and_build): Use it.
* g++.dg/cpp0x/Wnarrowing13.C: New test.
* g++.dg/cpp0x/Wnarrowing14.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/Wnarrowing13.C
trunk/gcc/testsuite/g++.dg/cpp0x/Wnarrowing14.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/pt.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:04:39 2019
Return-Path: <gcc-bugs-return-629457-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15429 invoked by alias); 16 Jan 2019 16:04:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15293 invoked by uid 48); 16 Jan 2019 16:04:35 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88880] [9 Regression] Wrong code since r264897
Date: Wed, 16 Jan 2019 16:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88880-4-uD8tuePJIA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88880-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02266.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88880
--- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
Upstream bug:
https://github.com/xianyi/OpenBLAS/issues/1964
>From gcc-bugs-return-629458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:12:34 2019
Return-Path: <gcc-bugs-return-629458-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59532 invoked by alias); 16 Jan 2019 16:12: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 59372 invoked by uid 48); 16 Jan 2019 16:12:22 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 16:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88877-4-lx9PVRE3WL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02267.txt.bz2
Content-length: 348
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
--- Comment #6 from Segher Boessenkool <segher at gcc dot gnu.org> ---
Sure, with 32-bit ABIs the registers are just 32 bits, for all intents and
purposes.
But we have -m64 here. (see also the "lwa" insn).
I think that because __floatunsidf has no prototype all its args are taken
to be int?
>From gcc-bugs-return-629459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:26:30 2019
Return-Path: <gcc-bugs-return-629459-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97905 invoked by alias); 16 Jan 2019 16:26:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97833 invoked by uid 48); 16 Jan 2019 16:26:25 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Wed, 16 Jan 2019 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at redhat dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-88815-4-odeLgTtfdZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02268.txt.bz2
Content-length: 1371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
--- Comment #7 from Jeffrey A. Law <law at redhat dot com> ---
Note that "dcmtk" in Fedora may be tripping over this as well. I haven't
looked in detail at it yet...
BUILDSTDERR: In file included from
/builddir/build/BUILD/dcmtk-3.6.2/ofstd/include/dcmtk/ofstd/variadic/variant.h:19,
BUILDSTDERR: from
/builddir/build/BUILD/dcmtk-3.6.2/ofstd/include/dcmtk/ofstd/ofvriant.h:379,
BUILDSTDERR: from
/builddir/build/BUILD/dcmtk-3.6.2/ofstd/tests/tvariant.cc:26:
BUILDSTDERR:
/builddir/build/BUILD/dcmtk-3.6.2/ofstd/include/dcmtk/ofstd/variadic/helpers.h:57:32:
error: narrowing conversion of '-1' from 'int' to 'long unsigned int'
[-Wnarrowing]
BUILDSTDERR: 57 | : OFintegral_constant<size_t,-1> {};
BUILDSTDERR: | ^
BUILDSTDERR: make[2]: ***
[ofstd/tests/CMakeFiles/ofstd_tests.dir/build.make:352:
ofstd/tests/CMakeFiles/ofstd_tests.dir/tvariant.cc.o] Error 1
BUILDSTDERR: make[2]: *** Waiting for unfinished jobs....
Not exactly enough information to determine from the log file...
>From gcc-bugs-return-629460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:27:11 2019
Return-Path: <gcc-bugs-return-629460-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100623 invoked by alias); 16 Jan 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 100506 invoked by uid 55); 16 Jan 2019 16:27:07 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Wed, 16 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81849-4-9GPSwhrPiS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02269.txt.bz2
Content-length: 485
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
--- Comment #9 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, Jan 16, 2019 at 07:13:37AM +0000, juergen.reuter at desy dot de wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
>
> --- Comment #8 from Jürgen Reuter <juergen.reuter at desy dot de> ---
> I think this fix or something very near by causes an ICE in our code, I will
> provide a bug report soon.
>
That's a bummer.
>From gcc-bugs-return-629461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:27:42 2019
Return-Path: <gcc-bugs-return-629461-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116320 invoked by alias); 16 Jan 2019 16:27: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 113633 invoked by uid 48); 16 Jan 2019 16:27:37 -0000
From: "trnka at scm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/84487] [8/9 Regression] Large rodate section increase in 465.tonto with r254427
Date: Wed, 16 Jan 2019 16:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: trnka at scm dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84487-4-DW76ro1cVi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84487-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84487-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02270.txt.bz2
Content-length: 2014
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84487
Tomáš Trnka <trnka at scm dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |trnka at scm dot com
--- Comment #12 from Tomáš Trnka <trnka at scm dot com> ---
(In reply to Wilco from comment #11)
> I'm not sure it's the same problem but the huge size increases I noticed are
> due to not optimizing zeroes from initializers, so we end up with huge
> rodata with only zeroes in it.
It indeed is the same problem. The change in r254427 causes def_init to be
generated for all types in a module (even if there's nothing to initialize), so
any type with a large array in it will end up taking lots of space in rodata.
Example:
module FooModule
type Foo
integer :: array(1000000)
end type
end module
program def_init_size
use FooModule
type(Foo) :: x
x%array(1) = 1
write(*,*) x%array(1)
end program
VM SIZE FILE SIZE
-------------- --------------
50.0% 3.81Mi .rodata 3.81Mi 99.6%
100.0% 3.81Mi __foomodule_MOD___def_init_foomodule_Foo 3.81Mi 100.0%
0.0% 60 [section .rodata] 60 0.0%
0.0% 48 __foomodule_MOD___vtab_foomodule_Foo 48 0.0%
0.0% 28 options.1.3571 28 0.0%
0.0% 4 _IO_stdin_used 4 0.0%
50.0% 3.81Mi .bss 0 0.0%
100.0% 3.81Mi x.3565 0 NAN%
0.0% 31 [section .bss] 0 NAN%
0.0% 1 completed.7132 0 NAN%
>From gcc-bugs-return-629462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:29:54 2019
Return-Path: <gcc-bugs-return-629462-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27396 invoked by alias); 16 Jan 2019 16:29: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 27317 invoked by uid 48); 16 Jan 2019 16:29:50 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/81849] Size of automatic array argument specified by host-associated variable.
Date: Wed, 16 Jan 2019 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81849-4-gAW2Kd7K5t@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02271.txt.bz2
Content-length: 235
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81849
--- Comment #10 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Actually, it was Thomas Koenig in r267953, so not your commits, but very
close.^^ The report is PR88871.
>From gcc-bugs-return-629464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:32:48 2019
Return-Path: <gcc-bugs-return-629464-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32433 invoked by alias); 16 Jan 2019 16:32: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 32349 invoked by uid 48); 16 Jan 2019 16:32:44 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Wed, 16 Jan 2019 16:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88815-4-U1MKJgbFWy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02273.txt.bz2
Content-length: 416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
--- Comment #8 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
That is most likely a bug in the package. GCC 8 wasn't very good at detecting
narrow conversions, but in GCC 9 things have improved, so probably we just
detect invalid code now. The problem in this PR is that we still don't detect
narrow conversions in certain contexts (here, decltype).
>From gcc-bugs-return-629463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:32:29 2019
Return-Path: <gcc-bugs-return-629463-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31553 invoked by alias); 16 Jan 2019 16:32: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 31458 invoked by uid 48); 16 Jan 2019 16:32:24 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88734] [8/9 Regression] AArch64's ACLE intrinsics give an ICE instead of compile error when option mismatch.
Date: Wed, 16 Jan 2019 16:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-88734-4-A8v8rvUa5v@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02272.txt.bz2
Content-length: 660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88734
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Created attachment 45444
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45444&action=edit
gcc9-pr88734.patch
Untested fix. I'll defer proper testcase to somebody familiar with
gcc.target/aarch64/ testing.
That said, I'm surprised GCC accepts this bogus syntax silently.
>From gcc-bugs-return-629465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:39:46 2019
Return-Path: <gcc-bugs-return-629465-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46796 invoked by alias); 16 Jan 2019 16: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 46722 invoked by uid 48); 16 Jan 2019 16:39:42 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88734] [8/9 Regression] AArch64's ACLE intrinsics give an ICE instead of compile error when option mismatch.
Date: Wed, 16 Jan 2019 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88734-4-zzz6LAP1aY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02274.txt.bz2
Content-length: 1140
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88734
--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Actually, with -Wsystem-headers we do warn about that:
include/arm_neon.h:33073:9: warning: ‘#pragma GCC option’ is not a string
[-Wpragmas]
33073 | #pragma GCC target(("arch=armv8.2-a+sm4"))
| ^~~
include/arm_neon.h:33140:9: warning: ‘#pragma GCC option’ is not a string
[-Wpragmas]
33140 | #pragma GCC target(("arch=armv8.2-a+crypto"))
| ^~~
include/arm_neon.h:33302:9: warning: ‘#pragma GCC option’ is not a string
[-Wpragmas]
33302 | #pragma GCC target(("arch=armv8.3-a"))
| ^~~
include/arm_neon.h:33305:9: warning: ‘#pragma GCC option’ is not a string
[-Wpragmas]
33305 | #pragma GCC target(("+fp16"))
| ^~~
include/arm_neon.h:33776:9: warning: ‘#pragma GCC option’ is not a string
[-Wpragmas]
33776 | #pragma GCC target(("arch=armv8.2-a+fp16fml"))
| ^~~
So it is just that nobody tried -Wsystem-headers with the arm and aarch64
intrinsic headers.
>From gcc-bugs-return-629466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:40:05 2019
Return-Path: <gcc-bugs-return-629466-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49364 invoked by alias); 16 Jan 2019 16:40: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 47741 invoked by uid 48); 16 Jan 2019 16:39:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88881] std::filesystem::status gives bad results on mingw32
Date: Wed, 16 Jan 2019 16:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-88881-4-GxthI2a724@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88881-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88881-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02275.txt.bz2
Content-length: 657
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88881
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |i.nixman at autistici dot org
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The trailing slash problem is apparently fixed in mingw-w64:
https://sourceforge.net/p/mingw-w64/bugs/643/
>From gcc-bugs-return-629467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:55:53 2019
Return-Path: <gcc-bugs-return-629467-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126020 invoked by alias); 16 Jan 2019 16:55: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 121779 invoked by uid 48); 16 Jan 2019 16:55:48 -0000
From: "nathan at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/86610] [8/9 Regression] non-const operator erroneously called in lambda in templated function
Date: Wed, 16 Jan 2019 16:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: nathan at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: nathan at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-86610-4-hlmz9mRTrG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86610-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86610-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02276.txt.bz2
Content-length: 381
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86610
Nathan Sidwell <nathan at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |nathan at gcc dot gnu.org
>From gcc-bugs-return-629468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 16:57:27 2019
Return-Path: <gcc-bugs-return-629468-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96195 invoked by alias); 16 Jan 2019 16:57: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 90285 invoked by uid 48); 16 Jan 2019 16:57:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88881] std::filesystem::status gives bad results on mingw32
Date: Wed, 16 Jan 2019 16:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88881-4-CHhoTUof8u@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88881-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88881-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02277.txt.bz2
Content-length: 1809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88881
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
But that fix looks wrong, it means "file/" will resolve to "file" and that's
wrong a for a non-directory, because "file/" should fail.
Testcase demonstrating the mingw bugs:
#include <sys/stat.h>
#include <stdio.h>
void print(const char* s, int i, int expected)
{
printf("%-26s %2d %s\n", s, i, i == expected ? "" : " FAIL");
}
void f1()
{
struct stat st;
int i;
i = stat(".\\", &st);
print("stat(\".\\\")", i, 0);
i = stat(".\\nonesuch\\..", &st);
print("stat(\".\\nonesuch\\..\")", i, -1);
// Trailing slash after a non-directory should fail:
i = stat("a.exe\\", &st);
print("stat(\"a.exe\\\")", i, -1);
// "/." after a non-directory is also wrong:
i = stat("a.exe\\.", &st);
print("stat(\"a.exe\\.\")", i, -1);
// And resolving "/dir/.." after a non-directory is also wrong:
i = stat("a.exe\\nonesuch\\..", &st);
print("stat(\"a.exe\\nonesuch\\..\")", i, -1);
}
void f2()
{
struct _stat st;
int i;
i = _stat(".\\", &st);
print("_stat(\".\\\")", i, 0);
i = _stat(".\\nonesuch\\..", &st);
print("_stat(\".\\nonesuch\\..\")", i, -1);
}
void f3()
{
struct _stat st;
int i;
i = _wstat(L".\\", &st);
print("_wstat(L\".\\\")", i, 0);
i = _wstat(L".\\nonesuch\\..", &st);
print("_wstat(L\".\\nonesuch\\..\")", i, -1);
}
int main()
{
f1();
f2();
f3();
}
Output for mingw-w64 5.0
stat(".\") 0
stat(".\nonesuch\..") 0 FAIL
stat("a.exe\") 0 FAIL
stat("a.exe\.") 0 FAIL
stat("a.exe\nonesuch\..") 0 FAIL
_stat(".\") -1 FAIL
_stat(".\nonesuch\..") 0 FAIL
_wstat(L".\") -1 FAIL
_wstat(L".\nonesuch\..") 0 FAIL
>From gcc-bugs-return-629469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:04:08 2019
Return-Path: <gcc-bugs-return-629469-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9467 invoked by alias); 16 Jan 2019 17:04:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 9116 invoked by uid 48); 16 Jan 2019 17:04:00 -0000
From: "umesh.kalappa0 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 17:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: umesh.kalappa0 at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88877-4-xcKgQiX73T@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02278.txt.bz2
Content-length: 240
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
--- Comment #7 from Umesh Kalappa <umesh.kalappa0 at gmail dot com> ---
Segher,true ,so how do we fix the case , modify the __floatunsidf to clear arg
higher 32 bits , before it use ?
>From gcc-bugs-return-629470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:15:56 2019
Return-Path: <gcc-bugs-return-629470-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26903 invoked by alias); 16 Jan 2019 17:15: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 25985 invoked by uid 48); 16 Jan 2019 17:15:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88881] std::filesystem::status gives bad results on mingw32
Date: Wed, 16 Jan 2019 17:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88881-4-jHN92zaQ51@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88881-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88881-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02279.txt.bz2
Content-length: 212
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88881
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The "nonexistent-path/.." part is reported as
https://sourceforge.net/p/mingw-w64/bugs/782/
>From gcc-bugs-return-629471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:17:44 2019
Return-Path: <gcc-bugs-return-629471-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33889 invoked by alias); 16 Jan 2019 17:17:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33813 invoked by uid 48); 16 Jan 2019 17:17:39 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88775] [8/9 Regression] Optimize std::string assignment
Date: Wed, 16 Jan 2019 17:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88775-4-qqL1lTNJNv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88775-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02280.txt.bz2
Content-length: 1452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88775
--- Comment #18 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #17)
> Without the #c11 patch (+ removal of the !INTEGRAL_TYPE_P special case from
> the above committed change + fixing up ptrs_compare_unequal, or something
> equivalent like the VRP change)
I am a bit lost with the current status there ;-) (I don't have much time now
so I can't really follow anyway, no need to explain it to me)
> I'm afraid there isn't much possibilities
> left to do, and those changes are too risky for GCC9.
I am not in a hurry. I don't personally write code where the performance of
string matters, I was forwarding (the first part of) a report by some user.
> The problem with your
> testcase is that NRV is in place, so we don't even know if s is an automatic
> variable or a global variable, or a heap variable etc.
NRV complicates things, but even with NRV I think we should be able to say that
s and "hello" cannot have the same address, since the caller is supposed to
pass the address of a writable buffer as argument. Or can you think of cases
where NRV would allow the return object and a string literal to have the same
address? Maybe if we store the returned value in a const object and never
compare the address of this const object to another one the compiler could skip
constructing the object and use a reference to a constant object?
>From gcc-bugs-return-629472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:27:20 2019
Return-Path: <gcc-bugs-return-629472-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53742 invoked by alias); 16 Jan 2019 17:27: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 53661 invoked by uid 48); 16 Jan 2019 17:27:14 -0000
From: "segher at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88877] rs6000 emits signed extension for unsigned int type(__floatunsidf).
Date: Wed, 16 Jan 2019 17:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ABI
X-Bugzilla-Severity: normal
X-Bugzilla-Who: segher at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88877-4-hGGe2M4PQj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88877-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02281.txt.bz2
Content-length: 258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88877
--- Comment #8 from Segher Boessenkool <segher at gcc dot gnu.org> ---
There is no bug, so we don't have to do anything.
To make slightly better code we could make the soft float routines be
prototyped?
>From gcc-bugs-return-629473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:40:24 2019
Return-Path: <gcc-bugs-return-629473-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22669 invoked by alias); 16 Jan 2019 17:40:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22536 invoked by uid 48); 16 Jan 2019 17:40:19 -0000
From: "mcccs at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83531] Build broken on macOS 10.13.2
Date: Wed, 16 Jan 2019 17:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 5.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mcccs at gmx dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83531-4-rwxgZmtSxG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02282.txt.bz2
Content-length: 6655
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83531
--- Comment #4 from MCCCS <mcccs at gmx dot com> ---
Iain could you please test if this patch works for you
too? If so, I'll send it as a patch tomorrow
(For me, it even fixes g++.dg/other/darwin-cfstring1.C):
Index: fixincludes/fixincl.x
===================================================================
--- fixincludes/fixincl.x (revision 267969)
+++ fixincludes/fixincl.x (working copy)
@@ -2,11 +2,11 @@
*
* DO NOT EDIT THIS FILE (fixincl.x)
*
- * It has been AutoGen-ed October 16, 2018 at 11:38:39 AM by AutoGen 5.18.7
+ * It has been AutoGen-ed January 16, 2019 at 07:37:22 PM by AutoGen 5.18.12
* From the definitions inclhack.def
* and the template file fixincl
*/
-/* DO NOT SVN-MERGE THIS FILE, EITHER Tue Oct 16 11:38:39 CEST 2018
+/* DO NOT SVN-MERGE THIS FILE, EITHER Wed Jan 16 19:37:22 CEST 2019
*
* You must regenerate it. Use the ./genfixes script.
*
@@ -15,7 +15,7 @@
* certain ANSI-incompatible system header files which are fixed to work
* correctly with ANSI C and placed in a directory that GNU C will search.
*
- * This file contains 251 fixup descriptions.
+ * This file contains 252 fixup descriptions.
*
* See README for more information.
*
@@ -2636,6 +2636,56 @@ static const char* apzDarwin_AvailabilityinternalP
/* * * * * * * * * * * * * * * * * * * * * * * * * *
*
+ * Description of Darwin_Api_Availability fix
+ */
+tSCC zDarwin_Api_AvailabilityName[] =
+ "darwin_api_availability";
+
+/*
+ * File name selection pattern
+ */
+tSCC zDarwin_Api_AvailabilityList[] =
+ "os/availability.h\0";
+/*
+ * Machine/OS name selection pattern
+ */
+tSCC* apzDarwin_Api_AvailabilityMachs[] = {
+ "*-*-darwin*",
+ (const char*)NULL };
+
+/*
+ * content selection pattern - do fix if pattern found
+ */
+tSCC zDarwin_Api_AvailabilitySelect0[] =
+ " *#define __API_AVAILABLE.*\n\
+ *#define __API_DEPRECATED.*\n\
+ *#define __API_DEPRECATED_WITH_REPLACEMENT.*\n\
+ *#define __API_UNAVAILABLE.*\n";
+
+/*
+ * content bypass pattern - skip fix if pattern found
+ */
+tSCC zDarwin_Api_AvailabilityBypass0[] =
+ "__IPHONE_OS_VERSION_MIN_REQUIRED";
+
+#define DARWIN_API_AVAILABILITY_TEST_CT 2
+static tTestDesc aDarwin_Api_AvailabilityTests[] = {
+ { TT_NEGREP, zDarwin_Api_AvailabilityBypass0, (regex_t*)NULL },
+ { TT_EGREP, zDarwin_Api_AvailabilitySelect0, (regex_t*)NULL }, };
+
+/*
+ * Fix Command Arguments for Darwin_Api_Availability
+ */
+static const char* apzDarwin_Api_AvailabilityPatch[] = {
+ "format",
+ " #define API_AVAILABLE(...)\n\
+ #define API_DEPRECATED(...)\n\
+ #define API_DEPRECATED_WITH_REPLACEMENT(...)\n\
+ #define API_UNAVAILABLE(...)\n",
+ (char*)NULL };
+
+/* * * * * * * * * * * * * * * * * * * * * * * * * *
+ *
* Description of Darwin_9_Long_Double_Funcs_2 fix
*/
tSCC zDarwin_9_Long_Double_Funcs_2Name[] =
@@ -10188,9 +10238,9 @@ static const char* apzX11_SprintfPatch[] = {
*
* List of all fixes
*/
-#define REGEX_COUNT 289
+#define REGEX_COUNT 291
#define MACH_LIST_SIZE_LIMIT 187
-#define FIX_COUNT 251
+#define FIX_COUNT 252
/*
* Enumerate the fixes
@@ -10258,6 +10308,7 @@ typedef enum {
CTRL_QUOTES_USE_FIXIDX,
CXX_UNREADY_FIXIDX,
DARWIN_AVAILABILITYINTERNAL_FIXIDX,
+ DARWIN_API_AVAILABILITY_FIXIDX,
DARWIN_9_LONG_DOUBLE_FUNCS_2_FIXIDX,
DARWIN_EXTERNC_FIXIDX,
DARWIN_GCC4_BREAKAGE_FIXIDX,
@@ -10760,6 +10811,11 @@ tFixDesc fixDescList[ FIX_COUNT ] = {
DARWIN_AVAILABILITYINTERNAL_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE,
aDarwin_AvailabilityinternalTests, apzDarwin_AvailabilityinternalPatch,
0 },
+ { zDarwin_Api_AvailabilityName, zDarwin_Api_AvailabilityList,
+ apzDarwin_Api_AvailabilityMachs,
+ DARWIN_API_AVAILABILITY_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE,
+ aDarwin_Api_AvailabilityTests, apzDarwin_Api_AvailabilityPatch, 0 },
+
{ zDarwin_9_Long_Double_Funcs_2Name, zDarwin_9_Long_Double_Funcs_2List,
apzDarwin_9_Long_Double_Funcs_2Machs,
DARWIN_9_LONG_DOUBLE_FUNCS_2_TEST_CT, FD_MACH_ONLY | FD_SUBROUTINE,
Index: fixincludes/inclhack.def
===================================================================
--- fixincludes/inclhack.def (revision 267969)
+++ fixincludes/inclhack.def (working copy)
@@ -1298,6 +1298,33 @@ fix = {
};
/*
+ * macOS 10.13 and 10.14 forget to define API_AVAILABLE if
+ * __attribute__((availability)) is not supported.
+ */
+fix = {
+ hackname = darwin_api_availability;
+ mach = "*-*-darwin*";
+ files = os/availability.h;
+ bypass = "__IPHONE_OS_VERSION_MIN_REQUIRED";
+ select =
+ " *#define __API_AVAILABLE.*\n"
+ " *#define __API_DEPRECATED.*\n"
+ " *#define __API_DEPRECATED_WITH_REPLACEMENT.*\n"
+ " *#define __API_UNAVAILABLE.*\n";
+ c_fix = format;
+ c_fix_arg =
+ " #define API_AVAILABLE(...)\n"
+ " #define API_DEPRECATED(...)\n"
+ " #define API_DEPRECATED_WITH_REPLACEMENT(...)\n"
+ " #define API_UNAVAILABLE(...)\n";
+ test_text =
+ "#define __API_AVAILABLE(...)\n"
+ "#define __API_DEPRECATED(...)\n"
+ "#define __API_DEPRECATED_WITH_REPLACEMENT(...)\n"
+ "#define __API_UNAVAILABLE(...)\n";
+};
+
+/*
* For the AAB_darwin7_9_long_double_funcs fix to be useful,
* you have to not use "" includes.
*/
Index: fixincludes/tests/base/os/availability.h
===================================================================
--- fixincludes/tests/base/os/availability.h (nonexistent)
+++ fixincludes/tests/base/os/availability.h (working copy)
@@ -0,0 +1,18 @@
+/* DO NOT EDIT THIS FILE.
+
+ It has been auto-edited by fixincludes from:
+
+ "fixinc/tests/inc/os/availability.h"
+
+ This had to be done to correct non-standard usages in the
+ original, manufacturer supplied header file. */
+
+
+
+#if defined( DARWIN_API_AVAILABILITY_CHECK )
+ #define API_AVAILABLE(...)
+ #define API_DEPRECATED(...)
+ #define API_DEPRECATED_WITH_REPLACEMENT(...)
+ #define API_UNAVAILABLE(...)
+
+#endif /* DARWIN_API_AVAILABILITY_CHECK */
>From gcc-bugs-return-629474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:46:28 2019
Return-Path: <gcc-bugs-return-629474-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43580 invoked by alias); 16 Jan 2019 17:46:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43466 invoked by uid 48); 16 Jan 2019 17:46:22 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 16 Jan 2019 17:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-ULHcZ54AD8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02283.txt.bz2
Content-length: 1573
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #11 from ktkachov at gcc dot gnu.org ---
Thank you all for the input.
Just to add a bit of data.
I've instrumented 510.parest_r to count the number of loop iterations to get a
feel for how much of the unrolled loop is spent in the actual unrolled part
rather than the prologue/peeled part. Overall, the hot function itself is
entered 290M times. The distribution of loop iteration counts is:
Frequency iter:
92438870 36
87028560 54
20404571 24
17312960 62
14237184 72
13403904 108
7574437 102
7574420 70
5564881 40
4328249 64
4328240 46
3142656 48
2666496 124
1248176 8
1236641 16
1166592 204
1166592 140
1134392 4
857088 80
666624 92
666624 128
618320 30
613056 1
234464 2
190464 32
95232 60
84476 20
48272 10
6896 5
So the two most common iteration counts are 36 and 54. For an 8x unrolled loop
that's 4 and 6 iterations spent in the prologue with 4 and 6 times going around
the 8x unrolled loop respectively.
As an experiment I hacked the AArch64 assembly of the function generated with
-funroll-loops to replace the peeled prologue version with a simple
non-unrolled loop. That gave a sizeable speedup on two AArch64 platforms: >7%.
So beyond the vectorisation point Richard S. made above, maybe it's worth
considering replacing the peeled prologue with a simple loop instead?
Or at least add that as a distinct unrolling strategy and work to come up with
an analysis that would allow us to choose one over the other?
>From gcc-bugs-return-629475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:51:15 2019
Return-Path: <gcc-bugs-return-629475-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50143 invoked by alias); 16 Jan 2019 17:51: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 50049 invoked by uid 55); 16 Jan 2019 17:51:10 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/88046] [9 Regression] ICE in add_data_member_location_attribute at gcc/dwarf2out.c:19237 since r261885
Date: Wed, 16 Jan 2019 17:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88046-4-EWDsPPmIPM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88046-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02284.txt.bz2
Content-length: 522
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88046
--- Comment #7 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Author: tnfchris
Date: Wed Jan 16 17:50:38 2019
New Revision: 267980
URL: https://gcc.gnu.org/viewcvs?rev=267980&root=gcc&view=rev
Log:
Fix PR88046 on AArch64 and Arm bare metal targets.
gcc/testsuite/ChangeLog:
PR debug/88046
* g++.dg/lto/pr88046_0.C: Check for shared and fPIC.
Modified:
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/lto/pr88046_0.C
>From gcc-bugs-return-629476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 17:59:34 2019
Return-Path: <gcc-bugs-return-629476-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78380 invoked by alias); 16 Jan 2019 17:59: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 78329 invoked by uid 48); 16 Jan 2019 17:59:30 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88815] [9 Regression] is_constexpr (based on narrowing conversion and expression SFINAE) broken
Date: Wed, 16 Jan 2019 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88815-4-C9HKcCAx1q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02285.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88815
--- Comment #9 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #4)
> So one idea would to be to walk_tree on the expression at the end of
> finish_decltype_type, looking for compound literals and call check_narrowing.
Scratch this -- I don't know what I did last night but this is not the
solution. Perhaps we should create DECLTYPE_TYPE in finish_decltype_type when
there's narrowing.
>From gcc-bugs-return-629477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:02:12 2019
Return-Path: <gcc-bugs-return-629477-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81888 invoked by alias); 16 Jan 2019 18:02: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 81782 invoked by uid 48); 16 Jan 2019 18:02:07 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88734] [8/9 Regression] AArch64's ACLE intrinsics give an ICE instead of compile error when option mismatch.
Date: Wed, 16 Jan 2019 18:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88734-4-c7B5GwlAYe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02286.txt.bz2
Content-length: 264
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88734
--- Comment #4 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
Hi Jakub,
Thanks for the patch, I've started a testrun but the fix looks sensible to me.
I'll post the result as soon as it's finished.
>From gcc-bugs-return-629478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:16:40 2019
Return-Path: <gcc-bugs-return-629478-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117917 invoked by alias); 16 Jan 2019 18:16:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117849 invoked by uid 48); 16 Jan 2019 18:16:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/88884] New: std::filesystem::absolute("//") does not produce an absolute path on mingw
Date: Wed, 16 Jan 2019 18:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88884-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02287.txt.bz2
Content-length: 1776
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88884
Bug ID: 88884
Summary: std::filesystem::absolute("//") does not produce an
absolute path on mingw
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
The current implementation of filesystem::absolute uses GetFullPathNameW which
turns a path like "//" into "\\", and "////a" into "\\\\a", which are not
considered absolute by the filesystem::path::is_absolute() function.
The Windows function might be interpreting it as a UNC path (probably an
invalid one) but the std::filesystem library doesn't support UNC names. We
might need special handling in filesystem::absolute, something like:
--- a/libstdc++-v3/src/c++17/fs_ops.cc
+++ b/libstdc++-v3/src/c++17/fs_ops.cc
@@ -86,13 +86,24 @@ fs::absolute(const path& p, error_code& ec)
return ret;
}
#ifdef _GLIBCXX_FILESYSTEM_IS_WINDOWS
- const wstring& s = p.native();
+ const wstring& native = p.native();
+ const wchar_t* s = native.c_str();
+ const auto pos = native.find_first_not_of(L"/\\");
+ // If there are multiple directory separators at the start,
+ // skip all but one of them:
+ if (pos > 1)
+ {
+ if (pos == native.npos)
+ s += native.length() - 1;
+ else
+ s += pos - 1;
+ }
uint32_t len = 1024;
wstring buf;
do
{
buf.resize(len);
- len = GetFullPathNameW(s.c_str(), len, buf.data(), nullptr);
+ len = GetFullPathNameW(s, len, buf.data(), nullptr);
}
while (len > buf.size());
>From gcc-bugs-return-629479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:22:44 2019
Return-Path: <gcc-bugs-return-629479-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5329 invoked by alias); 16 Jan 2019 18:22:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5265 invoked by uid 48); 16 Jan 2019 18:22:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88864] default template arguments not merged across all declarations
Date: Wed, 16 Jan 2019 18:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88864-4-ufAhZqVcQ0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02288.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88864
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm pretty sure this is a dup of an existing bug.
>From gcc-bugs-return-629481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:23:47 2019
Return-Path: <gcc-bugs-return-629481-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7263 invoked by alias); 16 Jan 2019 18:23:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7023 invoked by uid 48); 16 Jan 2019 18:23:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65396] Function template default template arguments not merged
Date: Wed, 16 Jan 2019 18:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-65396-4-yanX4gGNFu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65396-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65396-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02290.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65396
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 88864 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-629480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:23:46 2019
Return-Path: <gcc-bugs-return-629480-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7125 invoked by alias); 16 Jan 2019 18:23:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6997 invoked by uid 48); 16 Jan 2019 18:23:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88864] default template arguments not merged across all declarations
Date: Wed, 16 Jan 2019 18:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88864-4-lag5KrrxRP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02289.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88864
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
.
*** This bug has been marked as a duplicate of bug 65396 ***
>From gcc-bugs-return-629482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:29:00 2019
Return-Path: <gcc-bugs-return-629482-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18684 invoked by alias); 16 Jan 2019 18:29:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 18555 invoked by uid 48); 16 Jan 2019 18:28:55 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/88760] GCC unrolling is suboptimal
Date: Wed, 16 Jan 2019 18:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88760-4-D8wH4Dpn8F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02291.txt.bz2
Content-length: 949
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88760
--- Comment #12 from ktkachov at gcc dot gnu.org ---
(In reply to ktkachov from comment #11)
>
> As an experiment I hacked the AArch64 assembly of the function generated
> with -funroll-loops to replace the peeled prologue version with a simple
> non-unrolled loop. That gave a sizeable speedup on two AArch64 platforms:
> >7%.
>
> So beyond the vectorisation point Richard S. made above, maybe it's worth
> considering replacing the peeled prologue with a simple loop instead?
> Or at least add that as a distinct unrolling strategy and work to come up
> with an analysis that would allow us to choose one over the other?
Upon reflection I think I may have bungled up the assembly hacking (the changes
I made may not be equivalent to the source). I'll redo that experiment soon, so
please disregard that part for now. The iteration count distribution numbers
are still valid though.
>From gcc-bugs-return-629483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:39:45 2019
Return-Path: <gcc-bugs-return-629483-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112534 invoked by alias); 16 Jan 2019 18:39: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 111855 invoked by uid 48); 16 Jan 2019 18:39:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/65396] Function template default template arguments not merged
Date: Wed, 16 Jan 2019 18:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-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-65396-4-kzmiWR5d07@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65396-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65396-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02292.txt.bz2
Content-length: 668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65396
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2016-01-24 00:00:00 |2019-1-16
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
From PR 88864:
Shorter repro from StackOverflow https://stackoverflow.com/q/54202462/2069064:
struct B {
template<typename T, typename U> B(T t);
};
template <typename T, typename U = int>
B::B(T t) { }
B b(3);
This is rejected by all versions of gcc because of an inability to deduce U.
>From gcc-bugs-return-629484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 18:56:09 2019
Return-Path: <gcc-bugs-return-629484-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111134 invoked by alias); 16 Jan 2019 18:56: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 111082 invoked by uid 48); 16 Jan 2019 18:56:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/88858] ICE in rtl_verify_fallthru, at cfgrtl.c:2930 in Firefox build with LTO and PGO
Date: Wed, 16 Jan 2019 18:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-88858-4-KqLAVJq865@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02293.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88858
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2019-01-16
Assignee|unassigned at gcc dot gnu.org |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Lemme try to fix it.
>From gcc-bugs-return-629485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 19:12:20 2019
Return-Path: <gcc-bugs-return-629485-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61673 invoked by alias); 16 Jan 2019 19:12:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61559 invoked by uid 48); 16 Jan 2019 19:12:15 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/86214] [8/9 Regression] Strongly increased stack usage
Date: Wed, 16 Jan 2019 19:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.3
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-86214-4-F9DPLwGE68@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86214-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86214-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02294.txt.bz2
Content-length: 2008
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=86214
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #11 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Looking at the #c7 testcase, confirming that ~ 29KB stack in one of the
functions. The problem is that msg has char buf[8192]; variable in it and is
inline, gets inlined into a function 3 times and can throw.
ehcleanup1 removes the buf (and str) clobbers that were the only reason to have
an EH pad that just rethrows (and I agree it is a good idea to do that, because
otherwise inliner thinks the functions are more expensive than they actually
are).
But then the function into which this function is ultimately inlined has some
finalization (destructors) covering the code into which it has been inlined, so
the former EH with no successor block because it would throw externally now
becomes EH edge from the code to a landing block onto which everything is
marked as conflicting, there is no clobber at all for the variables.
So, I wonder if we shouldn't add in such cases clobbers to the start of those
landing pads in the situation, either for all variables that live in memory, or
at least for the larger ones. Will play with it tomorrow.
There is another thing - I've noticed add_stack_var_conflict is often called
with x == y, shouldn't we return right away in that case? We don't need to
record that a var conflicts with itself, we later on return that no variable
conflicts with itself.
Note, before r255104 we weren't inlining msg into the bigger function and thus
the issue was latent.
The workaround for MySQL, at least for -O2, would be to move logger:msg
definition out from the class, so it is not inline, then at least gcc trunk
doesn't want to inline it and you don't run into this.
>From gcc-bugs-return-629486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 19:22:51 2019
Return-Path: <gcc-bugs-return-629486-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104296 invoked by alias); 16 Jan 2019 19:22:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104258 invoked by uid 55); 16 Jan 2019 19:22:45 -0000
From: "toon at moene dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/51310] -finit-bla doesn't initialize *all* items of type bla to the requested constant.
Date: Wed, 16 Jan 2019 19:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: toon at moene dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: toon at moene dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-51310-4-Q1qZPm49NT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-51310-4@http.gcc.gnu.org/bugzilla/>
References: <bug-51310-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02295.txt.bz2
Content-length: 1003
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51310
--- Comment #10 from Toon Moene <toon at moene dot org> ---
On 1/14/19 11:52 PM, dominiq at lps dot ens.fr wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=51310
>
> --- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Output from the test in comment 0 is now
>
> NaN 0.0000000000000000 NaN
> n= 3
> a= NaN NaN
> NaN
> var= NaN
> b= NaN NaN
> NaN
> c= 0.0000000000000000 0.0000000000000000 0.0000000000000000
>
> i.e., the allocated allocatable arrays are not initialized.
>
> Toon do you still want to have this PR assigned to you?
>
> This PR is also related to pr33430.
>
Yes, leave it for the time being - I will see if I can do something
about it (or unassign, if not).
Thanks,
>From gcc-bugs-return-629487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 19:54:49 2019
Return-Path: <gcc-bugs-return-629487-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87349 invoked by alias); 16 Jan 2019 19:54:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 87301 invoked by uid 48); 16 Jan 2019 19:54:44 -0000
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88885] New: GCC ICE internal compiler error: Segmentation fault in mpd
Date: Wed, 16 Jan 2019 19:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: raj.khem 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-88885-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02296.txt.bz2
Content-length: 1071
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88885
Bug ID: 88885
Summary: GCC ICE internal compiler error: Segmentation fault in
mpd
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: raj.khem at gmail dot com
Target Milestone: ---
Created attachment 45445
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45445&action=edit
test case
While compiling mpd on cortex-a5 machine with gcc 9.0 snapshot from 9-20190113
g++ is segfaulting on attached test case
arm-yoe-linux-musleabi-g++ -march=armv7-a -mfpu=neon -mfloat-abi=hard
--sysroot=/mnt/a/yoe/build/tmp/work/cortexa5t2hf-neon-vfpv4-yoe-linux-musleabi/mpd/0.20.22-r0/recipe-sysroot
a.cpp -c
<built-in>: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
>From gcc-bugs-return-629488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 19:58:58 2019
Return-Path: <gcc-bugs-return-629488-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123588 invoked by alias); 16 Jan 2019 19:58:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123551 invoked by uid 48); 16 Jan 2019 19:58:54 -0000
From: "raj.khem at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88885] GCC ICE internal compiler error: Segmentation fault in mpd
Date: Wed, 16 Jan 2019 19:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: raj.khem 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-88885-4-ArF4deNbWx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88885-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88885-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02297.txt.bz2
Content-length: 271
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88885
--- Comment #1 from Khem Raj <raj.khem at gmail dot com> ---
there are more errors probably same root cause
http://errors.yoctoproject.org/Errors/Details/216895/
http://errors.yoctoproject.org/Errors/Details/216899/
>From gcc-bugs-return-629489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:07:57 2019
Return-Path: <gcc-bugs-return-629489-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29390 invoked by alias); 16 Jan 2019 20:07: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 29308 invoked by uid 48); 16 Jan 2019 20:07:51 -0000
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83531] Build broken on macOS 10.13.2
Date: Wed, 16 Jan 2019 20: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: 5.5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83531-4-rHUhtUcLVC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83531-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02298.txt.bz2
Content-length: 2876
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83531
--- Comment #5 from Iain Sandoe <iains at gcc dot gnu.org> ---
* thanks for looking at this! (my machines are all tied up right now, so any
testing won't happen before 'tomorrow')
* apologies if this comes across as negative - but TBH I'm a bit nervous about
applying something like this without wider testing - certainly full reg-straps
on affected systems.
* A visual inspection of the patch, suggests it might be disabling more than is
necessary - GCC has attributes "available" and "deprecated" - it's only
"unavailable" that's currently missing [I have a patch for that somewhere, will
have to dust it off for 10]. (deprecated_with_replacement could be implemented
in terms of deprecated with message).
* I did not need any patch to bootstrap open branches [7, 8, and trunk] on
10.13.6 (in fact, not on any Darwin that supports libsanitizer - bearing in
mind that upstream doesn't support 10.6 now).
* GCC5 is closed, so any patch we might have would be something applied
"locally" to any private branches.
* The underlying issue is that there are a number of problems with system
headers [e.g. missing guards for __has_feature(), missing guards for block
syntax, nullability and lightweight generics, the latter two especially an
issue for objective c]. The problems tend to be dependent on the SDK version,
which is unfortunate because typically one could target 10.13 from 10.14 using
the 10.14 SDK, so the target OS version is not a 100% reliable test (TODO:
investigate whether there's an SDK version that we can easily pick up).
* for tests where there are a large number of problems (e.g. the objective c
stuff in particular, where there are no easy work-arounds), it's my plan to
cook up some proxy headers to allow us to continue to test what *does* work.
* from my investigations, it seems that the underlying issue can be solved by
including the relevant headers (but because of the points above "relevant
headers" depends on the SDK version). So, it might be that there' a small
number of tests for which a workaround will be better.. e.g at present, I have
the following to fix the test
diff --git a/gcc/testsuite/g++.dg/other/darwin-cfstring1.C
b/gcc/testsuite/g++.dg/other/darwin-cfstring1.C
index b2def1e858..7c08ef9c91 100644
--- a/gcc/testsuite/g++.dg/other/darwin-cfstring1.C
+++ b/gcc/testsuite/g++.dg/other/darwin-cfstring1.C
@@ -6,6 +6,12 @@
/* { dg-do compile { target *-*-darwin* } } */
/* { dg-options "-ftrack-macro-expansion=0 -mconstant-cfstrings" } */
+#if __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ >= 101300
+# include <CoreFoundation/CoreFoundation.h>
+#elif __ENVIRONMENT_MAC_OS_X_VERSION_MIN_REQUIRED__ >= 101000
+# include <CoreFoundation/CFAvailability.h>
+#endif
+
#include <CoreFoundation/CFString.h>
#ifdef __CONSTANT_CFSTRINGS__
>From gcc-bugs-return-629490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:14:16 2019
Return-Path: <gcc-bugs-return-629490-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47213 invoked by alias); 16 Jan 2019 20:14: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 47134 invoked by uid 55); 16 Jan 2019 20:14:10 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Wed, 16 Jan 2019 20:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88861-4-0aXi36mc0r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02299.txt.bz2
Content-length: 1663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
--- Comment #7 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Author: dmalcolm
Date: Wed Jan 16 20:13:23 2019
New Revision: 267984
URL: https://gcc.gnu.org/viewcvs?rev=267984&root=gcc&view=rev
Log:
Fix ICE due to "combine" creating unreachable EH blocks (PR target/88861)
PR target/88861 reports an ICE in "ce2" due to an unreachable
basic block.
The block becomes unreachable in "combine" when delete_noop_moves
deletes an insn with a REG_EH_REGION, deleting the EH edge, the
only edge leading to the basic block.
Normally, rest_of_handle_combine would call cleanup_cfg, deleting
unreachable blocks, if combine_instructions returns true, and
combine_instructions does return true for some cases of edge-removal,
but it doesn't for this case, leading to the ICE.
This patch updates delete_noop_moves so that it returns true if
it deletes any edges, and passes that through to combine_instructions,
so that it too will return true if any edges were deleted, ensuring that
cleanup_cfg will be called by rest_of_handle_combine for this case,
deleting the now-unreachable block, and fixing the ICE.
gcc/ChangeLog:
PR target/88861
* combine.c (delete_noop_moves): Convert to "bool" return,
returning true if any edges are eliminated.
(combine_instructions): Also return true if delete_noop_moves
returns true.
gcc/testsuite/ChangeLog:
PR target/88861
* g++.dg/torture/pr88861.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/torture/pr88861.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/combine.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:14:40 2019
Return-Path: <gcc-bugs-return-629491-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48038 invoked by alias); 16 Jan 2019 20:14:39 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47998 invoked by uid 48); 16 Jan 2019 20:14:35 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88886] New: ice in get_constant, at c-family/c-format.c:292
Date: Wed, 16 Jan 2019 20: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-88886-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02300.txt.bz2
Content-length: 931
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88886
Bug ID: 88886
Summary: ice in get_constant, at c-family/c-format.c:292
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: dcb314 at hotmail dot com
Target Milestone: ---
For this broken C code:
int sscanf(long, unsigned[], ...);
void a() { sscanf(0, ""); }
recent gcc trunk with flag -Wall does this:
bug496.c:2:1: internal compiler error: in get_constant, at
c-family/c-format.c:2
92
0x5e97e1 get_constant
../../trunk/gcc/c-family/c-format.c:292
0x5e97e1 get_constant
../../trunk/gcc/c-family/c-format.c:280
0x5e97e1 decode_format_attr
../../trunk/gcc/c-family/c-format.c:346
This seems to have been going wrong since sometime before revision 267000.
>From gcc-bugs-return-629492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:17:36 2019
Return-Path: <gcc-bugs-return-629492-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55094 invoked by alias); 16 Jan 2019 20:17: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 52209 invoked by uid 48); 16 Jan 2019 20:17:30 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/88861] [9 Regression] ICE in calc_dfs_tree, at dominance.c:458
Date: Wed, 16 Jan 2019 20:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88861-4-6JmxxZZgl1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02301.txt.bz2
Content-length: 450
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88861
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed by r267984.
>From gcc-bugs-return-629493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:27:45 2019
Return-Path: <gcc-bugs-return-629493-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79907 invoked by alias); 16 Jan 2019 20:27:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 79839 invoked by uid 48); 16 Jan 2019 20:27:40 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88886] [9 Regression] ice in get_constant, at c-family/c-format.c:292
Date: Wed, 16 Jan 2019 20:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc version short_desc everconfirmed
Message-ID: <bug-88886-4-RIOpaykJDL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88886-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88886-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02302.txt.bz2
Content-length: 2146
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88886
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |ice-on-invalid-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2019-01-16
CC| |msebor at gcc dot gnu.org
Version|8.0 |9.0
Summary|ice in get_constant, at |[9 Regression] ice in
|c-family/c-format.c:292 |get_constant, at
| |c-family/c-format.c:292
Ever confirmed|0 |1
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
The ICE was introduced in r266195 (GCC 9):
r266195 | msebor | 2018-11-15 17:53:57 -0500 (Thu, 15 Nov 2018) | 50 lines
PR c++/87541 - ICE using a constant decl as an attribute alloc_size argument
PR c++/87542 - bogus error on attribute format with a named constant argument
gcc/ChangeLog:
PR c++/87541
PR c++/87542
* tree.c (type_argument_type): New function.
* tree.h (type_argument_type): Declare it.
* gcc/doc/extend.texi (alloc_align): Update and clarify.
(alloc_size, nonnull, sentinel): Same.
gcc/c-family/ChangeLog:
PR c++/87541
PR c++/87542
* c-attribs.c (positional_argument): New function.
(handle_alloc_size_attribute): Use it and simplify.
(handle_alloc_align_attribute): Same.
(handle_assume_aligned_attribute): Same.
(handle_nonnull_attribute): Same.
* c-common.c (check_function_arguments): Pass fntype to
check_function_format.
* c-common.h (check_function_format): Add an argument.
(PosArgFlags, positional_argument): Declare new type and function.
* c-format.c (decode_format_attr): Add arguments.
(check_format_string, get_constant): Same.
(convert_format_name_to_system_name): Adjust.
>From gcc-bugs-return-629494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:32:22 2019
Return-Path: <gcc-bugs-return-629494-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83327 invoked by alias); 16 Jan 2019 20:32:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83238 invoked by uid 48); 16 Jan 2019 20:32:17 -0000
From: "will_schmidt at vnet dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/87532] bad results from vec_extract(unsigned char, foo) dependent upon function inline
Date: Wed, 16 Jan 2019 20:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: will_schmidt at vnet dot ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-87532-4-JLJWM8YXVI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87532-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87532-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02303.txt.bz2
Content-length: 853
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87532
Will Schmidt <will_schmidt at vnet dot ibm.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |will_schmidt at vnet dot ibm.com
--- Comment #2 from Will Schmidt <will_schmidt at vnet dot ibm.com> ---
Created attachment 45446
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45446&action=edit
another testcase variation...
Another testcase variation.
I've cleaned up/removed some casts that may have been adding to the confusion
earlier.
This test variation exercises the vec_extract against char, short, int types.
Per inspection, both char and short types appear to show incorrect results when
built with -O2 for power8 or newer.
>From gcc-bugs-return-629495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:40:59 2019
Return-Path: <gcc-bugs-return-629495-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95529 invoked by alias); 16 Jan 2019 20:40:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95419 invoked by uid 55); 16 Jan 2019 20:40:55 -0000
From: "ibuclaw at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug d/87824] x86_64-linux multilib issues
Date: Wed, 16 Jan 2019 20:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: d
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ibuclaw at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ibuclaw at gdcproject dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-87824-4-dRIB1QDRyO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-87824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-87824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02304.txt.bz2
Content-length: 939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87824
--- Comment #18 from ibuclaw at gcc dot gnu.org ---
Author: ibuclaw
Date: Wed Jan 16 20:40:21 2019
New Revision: 267985
URL: https://gcc.gnu.org/viewcvs?rev=267985&root=gcc&view=rev
Log:
[D] Fix failing EH execution test on i386.
Turn off partitioning unless it was explicitly requested, as it doesn't
work with D exception chaining, where personality routines use LSDA to
determine whether two thrown exceptions are in the same context.
The following distills what was failing in the D testsuite.
```
try {
try {
fn(); // throws "1"
}
finally {
throw new Exception("2");
}
}
catch (Exception e) {
assert(e.msg == "1");
assert(e.next.msg == "2");
}
```
gcc/d/ChangeLog:
PR d/87824
* d-lang.cc (d_post_options): Disable implicit
-forder-blocks-and-partition.
Modified:
trunk/gcc/d/ChangeLog
trunk/gcc/d/d-lang.cc
>From gcc-bugs-return-629496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 20:56:44 2019
Return-Path: <gcc-bugs-return-629496-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116540 invoked by alias); 16 Jan 2019 20:56: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 116483 invoked by uid 48); 16 Jan 2019 20:56:40 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/88699] [9 Regression] tree check fail: expected function_decl, have using_decl in add_method, at cp/class.c:1137
Date: Wed, 16 Jan 2019 20:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: dmalcolm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-88699-4-YLfCLlxqi3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88699-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02305.txt.bz2
Content-length: 384
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88699
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
>From gcc-bugs-return-629499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 21:41:55 2019
Return-Path: <gcc-bugs-return-629499-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99849 invoked by alias); 16 Jan 2019 21:41: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 99796 invoked by uid 48); 16 Jan 2019 21:41:50 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] [7 Regression] Strange error message about nested function declared but not defined when using inline.
Date: Wed, 16 Jan 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
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: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88720-4-n3gMBcdV0y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02308.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Also now fixed for GCC 7.5.
>From gcc-bugs-return-629498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 21:41:11 2019
Return-Path: <gcc-bugs-return-629498-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98148 invoked by alias); 16 Jan 2019 21:41: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 98071 invoked by uid 55); 16 Jan 2019 21:41:05 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88720] [7 Regression] Strange error message about nested function declared but not defined when using inline.
Date: Wed, 16 Jan 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88720-4-2S0uQPF1VC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02307.txt.bz2
Content-length: 2575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88720
--- Comment #5 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Wed Jan 16 21:40:33 2019
New Revision: 267987
URL: https://gcc.gnu.org/viewcvs?rev=267987&root=gcc&view=rev
Log:
Fix diagnostics for never-defined inline and nested functions (PR c/88720, PR
c/88726).
Bugs 88720 and 88726 report issues where a function is declared inline
in an inner scope, resulting in spurious diagnostics about it being
declared but never defined when that scope is left (possibly in some
cases also wrongly referring to the function as a nested function).
These are regressions that were introduced with the support for C99
inline semantics in 4.3 (they don't appear with 4.2; it's possible
some aspects of the bugs might have been introduced later than 4.3).
For the case of functions being wrongly referred to as nested,
DECL_EXTERNAL was not the right condition for a function being
non-nested; TREE_PUBLIC is appropriate for the case of non-nested
functions with external linkage, while !b->nested means this is the
outermost scope in which the function was declared and so avoids
catching the case of a file-scope static being redeclared inline
inside a function.
For the non-nested, external-linkage case, the code attempts to avoid
duplicate diagnostics by diagnosing only when scope != external_scope,
but actually scope == external_scope is more appropriate, as it's only
when the file and external scopes are popped that the code can
actually tell whether a function ended up being defined, and all such
functions will appear in the (GCC-internal) external scope.
Bootstrapped with no regressions on x86_64-pc-linux-gnu.
gcc/c:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* c-decl.c (pop_scope): Use TREE_PUBLIC and b->nested to determine
whether a function is nested, not DECL_EXTERNAL. Diagnose inline
functions declared but never defined only for external scope, not
for other scopes.
gcc/testsuite:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* gcc.dg/inline-40.c, gcc.dg/inline-41.c: New tests.
Added:
branches/gcc-7-branch/gcc/testsuite/gcc.dg/inline-40.c
branches/gcc-7-branch/gcc/testsuite/gcc.dg/inline-41.c
Modified:
branches/gcc-7-branch/gcc/c/ChangeLog
branches/gcc-7-branch/gcc/c/c-decl.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 21:41:10 2019
Return-Path: <gcc-bugs-return-629497-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98136 invoked by alias); 16 Jan 2019 21:41: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 98063 invoked by uid 55); 16 Jan 2019 21:41:05 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] [7 Regression] GCC thinks that translation unit does not contain a definition of inline function.
Date: Wed, 16 Jan 2019 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88726-4-QZmEgeMp20@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02306.txt.bz2
Content-length: 2575
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
--- Comment #5 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Author: jsm28
Date: Wed Jan 16 21:40:33 2019
New Revision: 267987
URL: https://gcc.gnu.org/viewcvs?rev=267987&root=gcc&view=rev
Log:
Fix diagnostics for never-defined inline and nested functions (PR c/88720, PR
c/88726).
Bugs 88720 and 88726 report issues where a function is declared inline
in an inner scope, resulting in spurious diagnostics about it being
declared but never defined when that scope is left (possibly in some
cases also wrongly referring to the function as a nested function).
These are regressions that were introduced with the support for C99
inline semantics in 4.3 (they don't appear with 4.2; it's possible
some aspects of the bugs might have been introduced later than 4.3).
For the case of functions being wrongly referred to as nested,
DECL_EXTERNAL was not the right condition for a function being
non-nested; TREE_PUBLIC is appropriate for the case of non-nested
functions with external linkage, while !b->nested means this is the
outermost scope in which the function was declared and so avoids
catching the case of a file-scope static being redeclared inline
inside a function.
For the non-nested, external-linkage case, the code attempts to avoid
duplicate diagnostics by diagnosing only when scope != external_scope,
but actually scope == external_scope is more appropriate, as it's only
when the file and external scopes are popped that the code can
actually tell whether a function ended up being defined, and all such
functions will appear in the (GCC-internal) external scope.
Bootstrapped with no regressions on x86_64-pc-linux-gnu.
gcc/c:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* c-decl.c (pop_scope): Use TREE_PUBLIC and b->nested to determine
whether a function is nested, not DECL_EXTERNAL. Diagnose inline
functions declared but never defined only for external scope, not
for other scopes.
gcc/testsuite:
Backport from mainline
2019-01-07 Joseph Myers <joseph@codesourcery.com>
PR c/88720
PR c/88726
* gcc.dg/inline-40.c, gcc.dg/inline-41.c: New tests.
Added:
branches/gcc-7-branch/gcc/testsuite/gcc.dg/inline-40.c
branches/gcc-7-branch/gcc/testsuite/gcc.dg/inline-41.c
Modified:
branches/gcc-7-branch/gcc/c/ChangeLog
branches/gcc-7-branch/gcc/c/c-decl.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-629500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 21:42:27 2019
Return-Path: <gcc-bugs-return-629500-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100853 invoked by alias); 16 Jan 2019 21:42: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 100768 invoked by uid 48); 16 Jan 2019 21:42:21 -0000
From: "jsm28 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88726] [7 Regression] GCC thinks that translation unit does not contain a definition of inline function.
Date: Wed, 16 Jan 2019 21:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jsm28 at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-88726-4-ZEARuWTdPn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02309.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88726
Joseph S. Myers <jsm28 at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from Joseph S. Myers <jsm28 at gcc dot gnu.org> ---
Also now fixed for GCC 7.5.
>From gcc-bugs-return-629501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 21:53:22 2019
Return-Path: <gcc-bugs-return-629501-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120226 invoked by alias); 16 Jan 2019 21:53:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120113 invoked by uid 48); 16 Jan 2019 21:53:16 -0000
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug go/88500] [SH]: SETCONTEXT_CLOBBERS_TLS needs to be handled in libgo
Date: Wed, 16 Jan 2019 21:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: go
X-Bugzilla-Version: 8.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ian at airs dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ian at airs dot com
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88500-4-1hG3hvSZzA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88500-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88500-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02310.txt.bz2
Content-length: 1337
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88500
--- Comment #1 from Ian Lance Taylor <ian at airs dot com> ---
SETCONTEXT_CLOBBERS_TLS is set by libgo/configure.ac if this program fails to
exit successfully. So the first step in fixing this bug is finding out why
this program fails on SH.
#include <pthread.h>
#include <stdlib.h>
#include <ucontext.h>
#include <unistd.h>
__thread int tls;
static char stack[[10 * 1024 * 1024]];
static ucontext_t c;
/* Called via makecontext/setcontext. */
static void
cfn (void)
{
exit (tls);
}
/* Called via pthread_create. */
static void *
tfn (void *dummy)
{
/* The thread should still see this value after calling
setcontext. */
tls = 0;
setcontext (&c);
/* The call to setcontext should not return. */
abort ();
}
int
main ()
{
pthread_t tid;
/* The thread should not see this value. */
tls = 1;
if (getcontext (&c) < 0)
abort ();
c.uc_stack.ss_sp = stack;
#ifdef MAKECONTEXT_STACK_TOP
c.uc_stack.ss_sp += sizeof stack;
#endif
c.uc_stack.ss_flags = 0;
c.uc_stack.ss_size = sizeof stack;
c.uc_link = NULL;
makecontext (&c, cfn, 0);
if (pthread_create (&tid, NULL, tfn, NULL) != 0)
abort ();
if (pthread_join (tid, NULL) != 0)
abort ();
/* The thread should have called exit. */
abort ();
}
>From gcc-bugs-return-629502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 22:00:05 2019
Return-Path: <gcc-bugs-return-629502-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17041 invoked by alias); 16 Jan 2019 22:00:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16866 invoked by uid 48); 16 Jan 2019 21:59:57 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/88423] [9 Regression] ICE in begin_move_insn, at sched-ebb.c:175
Date: Wed, 16 Jan 2019 22:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-checking, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-88423-4-jQWoyQCTbj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-88423-4@http.gcc.gnu.org/bugzilla/>
References: <bug-88423-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02311.txt.bz2
Content-length: 199
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88423
--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
The code_label is for a tablejump_p, immediately before the jump_table_data.
>From gcc-bugs-return-629503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 22:04:47 2019
Return-Path: <gcc-bugs-return-629503-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38211 invoked by alias); 16 Jan 2019 22:04:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38155 invoked by uid 48); 16 Jan 2019 22:04:42 -0000
From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/88887] New: Warn on unexpected continuation of 'return' to new line in if statement.
Date: Wed, 16 Jan 2019 22:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jgreenhalgh at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-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-88887-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-01/txt/msg02312.txt.bz2
Content-length: 977
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88887
Bug ID: 88887
Summary: Warn on unexpected continuation of 'return' to new
line in if statement.
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: jgreenhalgh at gcc dot gnu.org
Target Milestone: ---
A colleague tripped up on this typo:
void bar();
void
foo (int x)
{
if (x) return
bar ();
}
Their intention was to return immediately if (x) holds, but they missed the
semicolon after 'return' and because bar() is declared with a void return type
didn't hit any warnings.
In my opinion, it would be reasonable for -wmisleading-indentation to cover a
case like this. The related case:
void
foo2 (int x)
{
if (x)
return
bar ();
}
Could also be warned.
>From gcc-bugs-return-629504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Jan 16 22:10:24 2019
Return-Path: <gcc-bugs-return-629504-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82202 invoked by alias); 16 Jan 2019 22:10:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82185 invoked by uid 89); 16 Jan 2019 22:10:23 -0000
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.9 required=5.0 testsºYES_00,SPF_PASS autolearn=ham version=3.3.2 spammy=Broadway, broadway, tiny, centos
X-HELO: key0.esi.com.au
Received: from key0.esi.com.au (HELO key0.esi.com.au) (192.84.230.32) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 16 Jan 2019 22:10:21 +0000
Received: from key0.esi.com.au (key0l.esi.com.au [127.0.0.1]) by key0.esi.com.au (Postfix) with ESMTP id 95A2712000E for <gcc-bugs@gcc.gnu.org>; Thu, 17 Jan 2019 09:10:19 +1100 (AEDT)
Received: from localhost (damianm@localhost) by key0.esi.com.au (8.14.4/8.14.4/Submit) with ESMTP id x0GMAI0A027179 for <gcc-bugs@gcc.gnu.org>; Thu, 17 Jan 2019 09:10:19 +1100
Date: Wed, 16 Jan 2019 22:10:00 -0000
From: Damian McGuckin <damianm@esi.com.au>
To: gcc-bugs@gcc.gnu.org
Subject: Optimizer (-O3) Disabling IEEE Exception Handling
Message-ID: <alpine.LRH.2.02.1901170859280.26903@key0.esi.com.au>
User-Agent: Alpine 2.02 (LRH 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
X-IsSubscribed: yes
X-SW-Source: 2019-01/txt/msg02313.txt.bz2
Content-length: 1427
Hi,
I hope this has not been addressed before but my search returned nothing
the same. I found vaguely related stuff but not this.
I am talking is straightforward optimization, i.e. -O3 (say), which I read
the manual page to say, does not affect IEEE 754 stuff at all.
The following code
#include <fenv.h>
#include <stdio.h>
int bug()
{
double z;
int test;
feclearexcept(FE_ALL_EXCEPT);
printf("Except %x\n", fetestexcept(FE_ALL_EXCEPT));
z = 1.0 - Tiny;
test = fetestexcept(FE_ALL_EXCEPT);
printf("TEST says %x @%.9e should be %x\n", test, z, FE_INEXACT);
return(0);
}
int main()
{
bug();
return(0);
}
When compiled as just
gcc bug.c -lm
correctly raised the FP_INEXACT (0x20) flag. It produces
Except 0
TEST says 20 @1.000000000e+00 should be 20
where the first line notes that it starts cleared.
When compiled as
gcc -O3 bug.c -lm
or even
g++ bug.c
The second line produced says
TEST says 0 @1.000000000e+00 should be 20
There is no exception raised.
What did I do wrong. The -O flags is not supposed to affect that.
Does it need some extra flag? Do I need a much newer version?
The version is 4.8.5-16 (on CentOS 7.4)
Thanks - Damian
Pacific Engineering Systems International, 277-279 Broadway, Glebe NSW 2037
Ph:+61-2-8571-0847 .. Fx:+61-2-9692-9623 | unsolicited email not wanted here
Views & opinions here are mine and not those of any past or present employer
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2019-01-09 19:16 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-01-09 19:16 [Bug c/88774] New: Qualification of parameters does not change a function type: Bug or standard defect? anders.granlund.0 at gmail dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).