public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/85809] SFINAE code compiles that shouldn't be able to compile.
[not found] <bug-85809-4@http.gcc.gnu.org/bugzilla/>
@ 2018-05-16 14:59 ` redi at gcc dot gnu.org
2021-07-23 22:25 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 2+ messages in thread
From: redi at gcc dot gnu.org @ 2018-05-16 14:59 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: 1328580 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85809
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-16
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is not a valid bug report, please read https://gcc.gnu.org/bugs/ (as
requested when creating a reprot) and provide the missing information.
>From gcc-bugs-return-604836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 15:04:45 2018
Return-Path: <gcc-bugs-return-604836-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83149 invoked by alias); 16 May 2018 15: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 83039 invoked by uid 48); 16 May 2018 15:04:36 -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: Wed, 16 May 2018 15: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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to target_milestone
Message-ID: <bug-83306-4-IVoLZRkY5t@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: 2018-05/txt/msg01731.txt.bz2
Content-length: 644
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83306
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Target Milestone|--- |9.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I think I should also avoid storing the extra std::string and just do the
concatenation before passing the string to the system_error base class.
>From gcc-bugs-return-604837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 15:08:03 2018
Return-Path: <gcc-bugs-return-604837-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86084 invoked by alias); 16 May 2018 15:08: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 85955 invoked by uid 48); 16 May 2018 15:07:58 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Wed, 16 May 2018 15:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85801-4-7xqAqN0krt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01732.txt.bz2
Content-length: 718
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
--- Comment #5 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
> ld: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `progname' which may bind externally can not be used when making a shared object; recompile with -fPIC
So this is the start of the problem. Changing the behaviour to remove this
would involve disabling section anchors for all code (rather than just PIC): we
wouldn't know when a symbol might be pre-empted during linking.
I don't think we want to fix this, even if we could... there would be a large
performance penalty for lazy build systems.
That this works on X86 is not enough, IMO. x86 doesn't use section anchors.
>From gcc-bugs-return-604839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 16:23:21 2018
Return-Path: <gcc-bugs-return-604839-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121431 invoked by alias); 16 May 2018 16:23: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 121309 invoked by uid 55); 16 May 2018 16:23:16 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Wed, 16 May 2018 16: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85801-4-UuuMVm1QVF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01734.txt.bz2
Content-length: 1059
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> ---
On May 16, 2018 5:07:57 PM GMT+02:00, "rearnsha at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
>
>--- Comment #5 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>> ld: relocation R_AARCH64_ADR_PREL_PG_HI21 against symbol `progname'
>which may bind externally can not be used when making a shared object;
>recompile with -fPIC
>
>So this is the start of the problem. Changing the behaviour to remove
>this
>would involve disabling section anchors for all code (rather than just
>PIC): we
>wouldn't know when a symbol might be pre-empted during linking.
>
>I don't think we want to fix this, even if we could... there would be
>a large
>performance penalty for lazy build systems.
>
>That this works on X86 is not enough, IMO. x86 doesn't use section
>anchors.
Can't we decide that per symbol? Or somehow force the dynamic linker to use
the program symbol?
>From gcc-bugs-return-604838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 16:23:02 2018
Return-Path: <gcc-bugs-return-604838-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120502 invoked by alias); 16 May 2018 16:23:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120208 invoked by uid 48); 16 May 2018 16:22:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85670] `std::filesystem` does not compile on mingw-w64
Date: Wed, 16 May 2018 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.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-85670-4-PNvH3jOPSl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85670-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01733.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85670
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Oh I see, that line isn't compiled except on Windows, and does need a
declaration of operator!=.
I've fixed it locally now anyway.
>From gcc-bugs-return-604840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 16:27:43 2018
Return-Path: <gcc-bugs-return-604840-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129473 invoked by alias); 16 May 2018 16:27:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129245 invoked by uid 48); 16 May 2018 16:27:39 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Wed, 16 May 2018 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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85801-4-87CnXMY0vj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01735.txt.bz2
Content-length: 723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #6)
> Can't we decide that per symbol? Or somehow force the dynamic linker to use
> the program symbol?
At what point? We've no idea during compilation which code would go in a
shared library if its not built with -fPIC, and we've no idea which symbols
might then need to be ripped out of an anchor group. Once in an anchor group
it isn't possible to undo that during linking (since the reference is to the
entire group and individual symbols are no longer referenced).
So this is a decision the compiler makes which the linker can never undo.
>From gcc-bugs-return-604841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 16:36:25 2018
Return-Path: <gcc-bugs-return-604841-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21143 invoked by alias); 16 May 2018 16:36:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20243 invoked by uid 55); 16 May 2018 16:36:18 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Wed, 16 May 2018 16: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85801-4-t7JRGIFgKM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01736.txt.bz2
Content-length: 1147
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
--- Comment #8 from rguenther at suse dot de <rguenther at suse dot de> ---
On May 16, 2018 6:27:37 PM GMT+02:00, "rearnsha at gcc dot gnu.org"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
>
>--- Comment #7 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
>(In reply to rguenther@suse.de from comment #6)
>
>> Can't we decide that per symbol? Or somehow force the dynamic linker
>to use
>> the program symbol?
>
>At what point? We've no idea during compilation which code would go in
>a
>shared library if its not built with -fPIC, and we've no idea which
>symbols
>might then need to be ripped out of an anchor group. Once in an anchor
>group
>it isn't possible to undo that during linking (since the reference is
>to the
>entire group and individual symbols are no longer referenced).
>
>So this is a decision the compiler makes which the linker can never
>undo.
Sure. So I'd say common symbols that are exported may not be in an anchor
group?
What do we do with weak globals? Or generally with interposable symbols in
non-PIC code?
>From gcc-bugs-return-604842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 16:39:58 2018
Return-Path: <gcc-bugs-return-604842-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110290 invoked by alias); 16 May 2018 16: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 102322 invoked by uid 48); 16 May 2018 16:39:53 -0000
From: "ed at catmur dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))
Date: Wed, 16 May 2018 16:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: ed at catmur dot uk
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-66425-4-WCkzQwmGn2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66425-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01737.txt.bz2
Content-length: 542
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
Ed Catmur <ed at catmur dot uk> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ed at catmur dot uk
--- Comment #34 from Ed Catmur <ed at catmur dot uk> ---
Note that a logical negation prior to cast to void is sufficient to suppress
the warning:
int void_cast_should_not_warn() {
(void) !foo();
// ^-- here
return 0;
}
>From gcc-bugs-return-604843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 16:44:53 2018
Return-Path: <gcc-bugs-return-604843-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75096 invoked by alias); 16 May 2018 16: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 72365 invoked by uid 48); 16 May 2018 16:44:48 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Wed, 16 May 2018 16: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: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85801-4-myRDXMxSy0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01738.txt.bz2
Content-length: 578
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
--- Comment #9 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to rguenther@suse.de from comment #8)
>
> Sure. So I'd say common symbols that are exported may not be in an anchor
> group?
In the shared library this isn't a common symbol: it has an initializer.
>
> What do we do with weak globals? Or generally with interposable symbols in
> non-PIC code?
weak symbols (definitions, or references) can't go in anchor groups. But
they're quite rare and we just have to live with the overhead.
>From gcc-bugs-return-604844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 17:12:23 2018
Return-Path: <gcc-bugs-return-604844-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69584 invoked by alias); 16 May 2018 17:12:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66826 invoked by uid 48); 16 May 2018 17:12:17 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))
Date: Wed, 16 May 2018 17: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: 4.9.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66425-4-FzMHxmB7Hu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66425-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01739.txt.bz2
Content-length: 167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #35 from Jason Merrill <jason at gcc dot gnu.org> ---
Is there a reason you can't use [[nodiscard]]?
>From gcc-bugs-return-604845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 17:13:04 2018
Return-Path: <gcc-bugs-return-604845-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109311 invoked by alias); 16 May 2018 17:13: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 105417 invoked by uid 48); 16 May 2018 17:13:00 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66425] (void) cast doesn't suppress __attribute__((warn_unused_result))
Date: Wed, 16 May 2018 17:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66425-4-Jf3OfddfIY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66425-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66425-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01740.txt.bz2
Content-length: 275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66425
--- Comment #36 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #35)
> Is there a reason you can't use [[nodiscard]]?
...ah, because this is a bug report against the C compiler.
>From gcc-bugs-return-604846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 18:31:50 2018
Return-Path: <gcc-bugs-return-604846-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25210 invoked by alias); 16 May 2018 18:31: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 25149 invoked by uid 48); 16 May 2018 18:31:45 -0000
From: "jgreenhalgh at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85682] Regression: gcc.dg/tree-ssa/prefetch-5.c at r259995
Date: Wed, 16 May 2018 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jgreenhalgh at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: luis.machado at linaro dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85682-4-J8Xt9BFLbO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01741.txt.bz2
Content-length: 668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85682
--- Comment #3 from James Greenhalgh <jgreenhalgh at gcc dot gnu.org> ---
The bisect robot doesn't bootstrap, only build a stage 1 compiler.
I've checked your most recent patch against these testcases, and they execute
and complete fine.
(In reply to Luis Machado from comment #2)
> I did a fresh x86-64 bootstrap with the changes in and those prefetch tests
> are not executed as part of dg.exp. Running by hand they look sane to me.
I'm sure this is just a typo, but you probably didn't mean "dg.exp" in this
case - the prefetch tests are in tree-ssa.exp and the opt-1 and opt-2 tests are
in i386.exp .
>From gcc-bugs-return-604847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 18:49:47 2018
Return-Path: <gcc-bugs-return-604847-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113242 invoked by alias); 16 May 2018 18:49: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 112334 invoked by uid 48); 16 May 2018 18:49:43 -0000
From: "roland at gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85662] [8/9 Regression] "error: non-constant condition for static assertion" from __builtin_offsetof in C++
Date: Wed, 16 May 2018 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: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: roland at gnu dot org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jakub at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85662-4-a75C8NTUOS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85662-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85662-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01742.txt.bz2
Content-length: 174
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85662
--- Comment #6 from roland at gnu dot org ---
Thanks for the fix. What's the status on backporting this to 8 and/or 7?
>From gcc-bugs-return-604848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 18:52:45 2018
Return-Path: <gcc-bugs-return-604848-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115723 invoked by alias); 16 May 2018 18:52:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115608 invoked by uid 48); 16 May 2018 18:52:36 -0000
From: "cookevillain at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85810] New: gcc incorrectly handles declarations inside parameter lists of function declarators.
Date: Wed, 16 May 2018 18: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: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cookevillain at yahoo 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-85810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01743.txt.bz2
Content-length: 1226
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85810
Bug ID: 85810
Summary: gcc incorrectly handles declarations inside parameter
lists of function declarators.
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: cookevillain at yahoo dot com
Target Milestone: ---
Clause 6.2.1(2) of the C11 ISO Standard (draft) defines a function prototype as
follows:
A function prototype is a declaration of a function that declares the types of
its parameters.
In the following translation unit
int (*func)( struct tag { int mem; } );
struct tag array[42];
the declaration for f is a declaration of a pointer, not a function, hence
there is no function prototype involved. Therefore, 'tag' should have file
scope and the translation unit should be conforming. Instead gcc diagnoses an
`array of incomplete types' error for 'a'.
The discussion in
https://stackoverflow.com/questions/50371169/do-parameter-declarations-in-function-declarators-have-function-prototype-scope
is relevant here, as well.
>From gcc-bugs-return-604849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 19:09:13 2018
Return-Path: <gcc-bugs-return-604849-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15748 invoked by alias); 16 May 2018 19:09:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15714 invoked by uid 48); 16 May 2018 19:09:07 -0000
From: "thomas.otto@pdv-fs.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85714] -Wimplicit-fallthrough and nested exhaustive switch statements with enum classes and return
Date: Wed, 16 May 2018 19:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: thomas.otto@pdv-fs.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-85714-4-K9q8PyDBjE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01744.txt.bz2
Content-length: 536
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85714
--- Comment #3 from Thomas Otto <thomas.otto@pdv-fs.de> ---
I thought forcing out-of-range enum values is no longer unspecified but now
undefined behavior in C++17:
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1766
http://obiwahn.org/c++draft/expr.static.cast/#10
> The value is unchanged if the original value is within the range of the
> enumeration values ([dcl.enum]). Otherwise, the behavior is undefined.
And this warning also shows up with -std=c++17
>From gcc-bugs-return-604850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 19:16:04 2018
Return-Path: <gcc-bugs-return-604850-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24980 invoked by alias); 16 May 2018 19:16:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24372 invoked by uid 48); 16 May 2018 19:15:06 -0000
From: "rs2740 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85714] -Wimplicit-fallthrough and nested exhaustive switch statements with enum classes and return
Date: Wed, 16 May 2018 19: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.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rs2740 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-85714-4-xZAQ5EXnHh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01745.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85714
--- Comment #4 from TC <rs2740 at gmail dot com> ---
[dcl.enum]p4:
The underlying type can be explicitly specified using an enum-base. For a
scoped enumeration type, the underlying type is int if it is not explicitly
specified. In both of these cases, the underlying type is said to be fixed.
p8:
For an enumeration whose underlying type is fixed, the values of the
enumeration are the values of the underlying type.
>From gcc-bugs-return-604851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 19:23:58 2018
Return-Path: <gcc-bugs-return-604851-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41735 invoked by alias); 16 May 2018 19:23:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41667 invoked by uid 48); 16 May 2018 19:23:54 -0000
From: "luis.machado at linaro dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85682] Regression: gcc.dg/tree-ssa/prefetch-5.c at r259995
Date: Wed, 16 May 2018 19:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: luis.machado at linaro dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: luis.machado at linaro dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85682-4-idPFkTBHem@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85682-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85682-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01746.txt.bz2
Content-length: 897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85682
--- Comment #4 from Luis Machado <luis.machado at linaro dot org> ---
(In reply to James Greenhalgh from comment #3)
> The bisect robot doesn't bootstrap, only build a stage 1 compiler.
>
> I've checked your most recent patch against these testcases, and they
> execute and complete fine.
>
Thanks for checking it.
> (In reply to Luis Machado from comment #2)
> > I did a fresh x86-64 bootstrap with the changes in and those prefetch tests
> > are not executed as part of dg.exp. Running by hand they look sane to me.
>
> I'm sure this is just a typo, but you probably didn't mean "dg.exp" in this
> case - the prefetch tests are in tree-ssa.exp and the opt-1 and opt-2 tests
> are in i386.exp .
Correct. I had the prefetch-* tests in mind when i mentioned dg.exp, but then
noticed they were grouped within tree-ssa.exp.
>From gcc-bugs-return-604852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 19:36:53 2018
Return-Path: <gcc-bugs-return-604852-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17458 invoked by alias); 16 May 2018 19:36:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17401 invoked by uid 48); 16 May 2018 19:36:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85714] -Wimplicit-fallthrough and nested exhaustive switch statements with enum classes and return
Date: Wed, 16 May 2018 19: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: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85714-4-eFrqKNV39S@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85714-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85714-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01747.txt.bz2
Content-length: 635
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85714
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The enumeration type can take any value from (Foo)INT_MIN to (Foo)INT_MAX, and
likewise for Bar. Your switches are not exhaustive.
I think we need a FAQ about this, we have so many invalid bug reports like
this.
>From gcc-bugs-return-604853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 20:14:10 2018
Return-Path: <gcc-bugs-return-604853-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116107 invoked by alias); 16 May 2018 20: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 116032 invoked by uid 48); 16 May 2018 20:14:05 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled
Date: Wed, 16 May 2018 20: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.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc see_also
Message-ID: <bug-85783-4-XaVCd53FYi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01748.txt.bz2
Content-length: 754
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=82063
--- Comment #11 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Alexander Monakov from comment #10)
> Reopening: the request to be able to disable the warning (via
> -Wno-alloc-size-larger-than) is valid and should be addressed.
I think that part is bug 82063
>From gcc-bugs-return-604854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 20:32:11 2018
Return-Path: <gcc-bugs-return-604854-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92476 invoked by alias); 16 May 2018 20: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 89658 invoked by uid 55); 16 May 2018 20:32:06 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85810] gcc incorrectly handles declarations inside parameter lists of function declarators.
Date: Wed, 16 May 2018 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.1.1
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-85810-4-eGAvRpFQQI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01749.txt.bz2
Content-length: 707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85810
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
This is an obviously perverse interpretation of the standard that is
inconsistent with the intent expressed explicitly if non-normatively in
6.7.6.3#18 ("The identifiers x and y are declared for descriptive purposes
only and go out of scope at the end of the declaration of apfi.", in the
context of an example declaring an array of pointers to function).
When you have editorial issues where the wording of the standard could
more clearly express the intent you should take them direct to the editors
of the standard, not to implementors.
>From gcc-bugs-return-604855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 20:38:22 2018
Return-Path: <gcc-bugs-return-604855-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48314 invoked by alias); 16 May 2018 20:38:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48269 invoked by uid 55); 16 May 2018 20:38:17 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85363] Throwing exception from member constructor (brace initializer vs initializer list)
Date: Wed, 16 May 2018 20: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.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85363-4-UkIAVvrtmq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01750.txt.bz2
Content-length: 788
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85363
--- Comment #7 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Wed May 16 20:37:45 2018
New Revision: 260300
URL: https://gcc.gnu.org/viewcvs?rev=260300&root=gcc&view=rev
Log:
PR c++/85363
* call.c (set_flags_from_callee): Handle AGGR_INIT_EXPRs too.
* tree.c (bot_manip): Call set_flags_from_callee for
AGGR_INIT_EXPRs too.
* g++.dg/cpp0x/initlist-throw1.C: New test.
* g++.dg/cpp0x/initlist-throw2.C: New test.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/initlist-throw1.C
trunk/gcc/testsuite/g++.dg/cpp0x/initlist-throw2.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/cp/tree.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 20:38:58 2018
Return-Path: <gcc-bugs-return-604856-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49440 invoked by alias); 16 May 2018 20:38: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 49162 invoked by uid 48); 16 May 2018 20:38:53 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85363] Throwing exception from member constructor (brace initializer vs initializer list)
Date: Wed, 16 May 2018 20: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.2.1
X-Bugzilla-Keywords: wrong-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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85363-4-mi0mF1EoAI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85363-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01751.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85363
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed for GCC 9.
>From gcc-bugs-return-604857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:18:30 2018
Return-Path: <gcc-bugs-return-604857-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24936 invoked by alias); 16 May 2018 21: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 24873 invoked by uid 48); 16 May 2018 21:18:25 -0000
From: "mpeddie at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] New: Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 21:18: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpeddie 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-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01752.txt.bz2
Content-length: 8541
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
Bug ID: 85811
Summary: Invalid optimization with fmax, fabs and nan
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: mpeddie at gmail dot com
Target Milestone: ---
Created attachment 44139
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44139&action=edit
Preprocessed source file
I apologize in advance if I've chosen the wrong category for this bug; I have
to choose a category and don't know what's correct.
The output from my small test program varies depending on whether I enable
optimizations with -O. The un-preprocessed program is the following
(preprocessed output attached):
#include <math.h>
#include <stdio.h>
#include <stdlib.h>
int main(int argc __attribute__((unused)), char **argv
__attribute__((unused))) {
const double negval = -1.0;
const double nanval = 0.0 / 0.0;
const double val = fmax(negval, nanval);
const double absval = fabs(val);
printf("fabs(%.16e) = %.16e\n", val, absval);
return absval >= 0 ? 0 : 1;
}
With optimizations enabled, this prints
fabs(-1.0000000000000000e+00) = -1.0000000000000000e+00
and returns 1. This result is wrong (the absolute value must be positive).
Without optimizations, it prints
fabs(1.0000000000000000e+00) = 1.0000000000000000e+00
and returns 0 as expected. If I make the arguments to fmax() depend on inputs,
for example the value of argc, the program behaves correctly. If I call fmin()
instead of fmax(), the program behaves correctly. If neither of the arguments
to fmax() is NaN, the program behaves correctly; the correct behavior happens
if one argument is -NaN, INFINITY or -INFINITY. The order of arguments to
fmax() does not affect the result of the program.
If I look at the generated assembly, substituting fmin() for fmax() in the test
program results in an andpd instruction immediately after fmin() that isn't
emitted when fmax() is called.
The attached file test.i is the preprocessed source file. The test program
compiles without errors or warnings and never triggers the undefined-behavior
sanitizer. I've observed the same problem with gcc version 7.3.0 and 6.4.0 for
x86_64 as well as gcc version 6.3.0 for arm32. I don't see the problem with
gcc version 5.5.0 for x86_64. Below is the command-line invocation of gcc
along with its complete output.
gcc-8 -v -save-temps -O -Wall -Wextra -Werror -fsanitize=undefined
-fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations -lm test.c -o
test
Using built-in specs.
COLLECT_GCC=gcc-8
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.1.0-3'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.1.0 (Debian 8.1.0-3)
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O' '-Wall' '-Wextra' '-Werror'
'-fsanitize=undefined' '-fno-strict-aliasing' '-fwrapv'
'-fno-aggressive-loop-optimizations' '-o' 'test' '-mtune=generic'
'-march=x86-64'
/usr/lib/gcc/x86_64-linux-gnu/8/cc1 -E -quiet -v -imultiarch x86_64-linux-gnu
test.c -mtune=generic -march=x86-64 -Wall -Wextra -Werror -fsanitize=undefined
-fno-strict-aliasing -fwrapv -fno-aggressive-loop-optimizations -O
-fpch-preprocess -o test.i
ignoring nonexistent directory "/usr/local/include/x86_64-linux-gnu"
ignoring nonexistent directory
"/usr/lib/gcc/x86_64-linux-gnu/8/../../../../x86_64-linux-gnu/include"
#include "..." search starts here:
#include <...> search starts here:
/usr/lib/gcc/x86_64-linux-gnu/8/include
/usr/local/include
/usr/lib/gcc/x86_64-linux-gnu/8/include-fixed
/usr/include/x86_64-linux-gnu
/usr/include
End of search list.
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O' '-Wall' '-Wextra' '-Werror'
'-fsanitize=undefined' '-fno-strict-aliasing' '-fwrapv'
'-fno-aggressive-loop-optimizations' '-o' 'test' '-mtune=generic'
'-march=x86-64'
/usr/lib/gcc/x86_64-linux-gnu/8/cc1 -fpreprocessed test.i -quiet -dumpbase
test.c -mtune=generic -march=x86-64 -auxbase test -O -Wall -Wextra -Werror
-version -fsanitize=undefined -fno-strict-aliasing -fwrapv
-fno-aggressive-loop-optimizations -o test.s
GNU C17 (Debian 8.1.0-3) version 8.1.0 (x86_64-linux-gnu)
compiled by GNU C version 8.1.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
GNU C17 (Debian 8.1.0-3) version 8.1.0 (x86_64-linux-gnu)
compiled by GNU C version 8.1.0, GMP version 6.1.2, MPFR version 4.0.1,
MPC version 1.1.0, isl version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=100 --param ggc-min-heapsize=131072
Compiler executable checksum: bbc65a5a9118b9b79402871f4ead4543
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O' '-Wall' '-Wextra' '-Werror'
'-fsanitize=undefined' '-fno-strict-aliasing' '-fwrapv'
'-fno-aggressive-loop-optimizations' '-o' 'test' '-mtune=generic'
'-march=x86-64'
as -v --64 -o test.o test.s
GNU assembler version 2.30 (x86_64-linux-gnu) using BFD version (GNU Binutils
for Debian) 2.30
COMPILER_PATH=/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/
LIBRARY_PATH=/usr/lib/gcc/x86_64-linux-gnu/8/:/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/:/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib/:/lib/x86_64-linux-gnu/:/lib/../lib/:/usr/lib/x86_64-linux-gnu/:/usr/lib/../lib/:/usr/lib/gcc/x86_64-linux-gnu/8/../../../:/lib/:/usr/lib/
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O' '-Wall' '-Wextra' '-Werror'
'-fsanitize=undefined' '-fno-strict-aliasing' '-fwrapv'
'-fno-aggressive-loop-optimizations' '-o' 'test' '-mtune=generic'
'-march=x86-64'
/usr/lib/gcc/x86_64-linux-gnu/8/collect2 -plugin
/usr/lib/gcc/x86_64-linux-gnu/8/liblto_plugin.so
-plugin-opt=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
-plugin-opt=-fresolution=test.res -plugin-opt=-pass-through=-lgcc
-plugin-opt=-pass-through=-lgcc_s -plugin-opt=-pass-through=-lc
-plugin-opt=-pass-through=-lgcc -plugin-opt=-pass-through=-lgcc_s --sysroot=/
--build-id --eh-frame-hdr -m elf_x86_64 --hash-style=gnu -dynamic-linker
/lib64/ld-linux-x86-64.so.2 -pie -o test
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/Scrt1.o
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crti.o
/usr/lib/gcc/x86_64-linux-gnu/8/crtbeginS.o -L/usr/lib/gcc/x86_64-linux-gnu/8
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../../../lib -L/lib/x86_64-linux-gnu
-L/lib/../lib -L/usr/lib/x86_64-linux-gnu -L/usr/lib/../lib
-L/usr/lib/gcc/x86_64-linux-gnu/8/../../.. -lm test.o -lubsan -lgcc
--push-state --as-needed -lgcc_s --pop-state -lc -lgcc --push-state --as-needed
-lgcc_s --pop-state /usr/lib/gcc/x86_64-linux-gnu/8/crtendS.o
/usr/lib/gcc/x86_64-linux-gnu/8/../../../x86_64-linux-gnu/crtn.o
COLLECT_GCC_OPTIONS='-v' '-save-temps' '-O' '-Wall' '-Wextra' '-Werror'
'-fsanitize=undefined' '-fno-strict-aliasing' '-fwrapv'
'-fno-aggressive-loop-optimizations' '-o' 'test' '-mtune=generic'
'-march=x86-64'
>From gcc-bugs-return-604858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:34:02 2018
Return-Path: <gcc-bugs-return-604858-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40752 invoked by alias); 16 May 2018 21:34:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40649 invoked by uid 55); 16 May 2018 21:33:55 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Function need not be evaluated in logical expression
Date: Wed, 16 May 2018 21:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-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-85599-4-plKu1rcJ8F@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01753.txt.bz2
Content-length: 892
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #17 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Wed, May 16, 2018 at 08:41:42AM +0000, janus at gcc dot gnu.org wrote:
>
> > and implement it to transform
> > result = op1 binop op2
> >
> > into
> >
> > tmp1 = op1
> > tmp2 = op2
> > result = tmp1 BINOP tmp2
>
> That's not what I had in mind. I'd rather make a change from
>
> result = op1 && op2
>
> to
>
> result = op1 & op1
>
Then you are only interest in the special case of .and.
binop above is the entire collection of all binary
operators (e.g., +,-,*,/ etc as well as .and.).
What about
real x, ping, pong
external ping, pong
x = ping() + pong()
where both ping() and pong() have competing side effects.
The order of the evaluation of ping() and pong() is
not specified by the Fortran standard.
>From gcc-bugs-return-604859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:37:33 2018
Return-Path: <gcc-bugs-return-604859-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44263 invoked by alias); 16 May 2018 21:37:32 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44216 invoked by uid 48); 16 May 2018 21:37:27 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 21:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-UaPaXc0hDw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01754.txt.bz2
Content-length: 407
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
tree_binary_nonnegative_warnv_p for RDIV_EXPR does RECURSE (op0) && RECURSE
(op1), but that doesn't work so well when the denominator can be 0. I guess it
is still ok when finite-math-only (or no-nans and no-signed-zeros maybe?), or
when we can prove that the denominator is non-zero.
>From gcc-bugs-return-604860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:46:36 2018
Return-Path: <gcc-bugs-return-604860-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58738 invoked by alias); 16 May 2018 21: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 58672 invoked by uid 48); 16 May 2018 21:46:31 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 21:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-rV1nVyiw9I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01755.txt.bz2
Content-length: 220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Applying pattern match.pd:832, gimple-match.c:11245
Match-and-simplified ABS_EXPR <val_5> to val_5
>From gcc-bugs-return-604861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:48:04 2018
Return-Path: <gcc-bugs-return-604861-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83985 invoked by alias); 16 May 2018 21: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 77810 invoked by uid 48); 16 May 2018 21:47:58 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 21: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-NquzgAbmxZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01756.txt.bz2
Content-length: 327
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> Applying pattern match.pd:832, gimple-match.c:11245
> Match-and-simplified ABS_EXPR <val_5> to val_5
Which is:
(simplify
(abs tree_expr_nonnegative_p@0)
@0)
>From gcc-bugs-return-604862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:53:42 2018
Return-Path: <gcc-bugs-return-604862-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110522 invoked by alias); 16 May 2018 21:53:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 110492 invoked by uid 48); 16 May 2018 21:53:38 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 21:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-ZGAsgM68bD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01757.txt.bz2
Content-length: 220
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
case MAX_EXPR:
return RECURSE (op0) || RECURSE (op1);
This is not true if one is a NAN.
>From gcc-bugs-return-604863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:56:09 2018
Return-Path: <gcc-bugs-return-604863-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112293 invoked by alias); 16 May 2018 21: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 112232 invoked by uid 48); 16 May 2018 21:56:04 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 21: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-CJl1oazVS5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01758.txt.bz2
Content-length: 410
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #4)
> case MAX_EXPR:
> return RECURSE (op0) || RECURSE (op1);
>
> This is not true if one is a NAN.
And the reason why it is not true for NAN is simple:
If one of the two arguments is NaN, the value of the other argument is returned
>From gcc-bugs-return-604864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 21:59:13 2018
Return-Path: <gcc-bugs-return-604864-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114975 invoked by alias); 16 May 2018 21:59: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 114884 invoked by uid 48); 16 May 2018 21:59:07 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Function need not be evaluated in logical expression
Date: Wed, 16 May 2018 21:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-8t0zAG7Fzj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01759.txt.bz2
Content-length: 254
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #18 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This PR is now about a missed optimization in the middle-end.
Would it possible to move further discussions to pr57160? TIA.
>From gcc-bugs-return-604865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 22:24:58 2018
Return-Path: <gcc-bugs-return-604865-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46361 invoked by alias); 16 May 2018 22:24: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 46320 invoked by uid 48); 16 May 2018 22:24:53 -0000
From: "cookevillain at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85810] gcc incorrectly handles declarations inside parameter lists of function declarators.
Date: Wed, 16 May 2018 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.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cookevillain at yahoo 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-85810-4-q0Tbx8YMta@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01760.txt.bz2
Content-length: 905
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85810
--- Comment #2 from cookevillain at yahoo dot com ---
There is nothing obvious about the intent of the Standard here (see the
definition of type name scope introduced into the standard to handle a similar
formal issue). Grammatically, parameter declarations are not identical to
ordinary declarations so 6.7.6.3(18) is only tangentially relevant here (where
tag declarations are considered).
The Standard is supposed to be a formal specification of the language, so if
the implementors feel they implement what is intended and not what is written
this creates a problem for compiler users (especially those of us who write
formal verification tools). I have no problem accepting that gcc implements a
version of C11 that is better than the standard one, however 'perverse' is bit
too strong a term, maybe 'literal' is more appropriate.
>From gcc-bugs-return-604866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 22:50:39 2018
Return-Path: <gcc-bugs-return-604866-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6960 invoked by alias); 16 May 2018 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 130194 invoked by uid 48); 16 May 2018 22:50:33 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85811] Invalid optimization with fmax, fabs and nan
Date: Wed, 16 May 2018 22: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-gVdQlj0rga@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01761.txt.bz2
Content-length: 268
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #6 from Marc Glisse <glisse at gcc dot gnu.org> ---
What does tree_expr_nonnegative_p call non-negative? A natural definition would
exclude NaN, but for REAL_CST we just return ! REAL_VALUE_NEGATIVE.
>From gcc-bugs-return-604867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 23:08:00 2018
Return-Path: <gcc-bugs-return-604867-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56569 invoked by alias); 16 May 2018 23:08:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56512 invoked by uid 48); 16 May 2018 23:07:55 -0000
From: "andreas.molzer at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69905] Digit separators break literal operators
Date: Wed, 16 May 2018 23: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andreas.molzer 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: cc
Message-ID: <bug-69905-4-Sm2EaGrWKP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01762.txt.bz2
Content-length: 1422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69905
andreas.molzer at gmx dot de changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andreas.molzer at gmx dot de
--- Comment #7 from andreas.molzer at gmx dot de ---
Leaving out the overload for operator""s(long double) will silently break valid
code. Consider:
#include <chrono>
int main() {
using std::chrono_literals;
auto time = operator""s(0x8000'0000'0000'0000'0000'0000ULL);
}
According to standard, this should select the overload with unsigned long long
argument, which does not exist. It will instead silently perform a numeric
conversion to long double, resulting in loss of accuracy on targets where gcc
does not use extended 80-bit double. Any other integer arguments, which should
lead to overload resolution failure, will also be double durations albeit with
less immediately catastrophic results.
However, that doesn't mean the long term effects are no issue. Consider that
the type of time.count() also unexpectedly resolves as long double. Or even
worse that assigning decltype(time)::max() to unsigned long long is undefined
behaviour.
It might be more fitting to open the missing declarations as a separately
tracked bug, improving visibility of the standard issue as well.
>From gcc-bugs-return-604868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed May 16 23:23:30 2018
Return-Path: <gcc-bugs-return-604868-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66531 invoked by alias); 16 May 2018 23: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 66508 invoked by uid 55); 16 May 2018 23:23:25 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85810] gcc incorrectly handles declarations inside parameter lists of function declarators.
Date: Wed, 16 May 2018 23:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.1
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-85810-4-P1OWsy0YOU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01763.txt.bz2
Content-length: 449
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85810
--- Comment #3 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 16 May 2018, cookevillain at yahoo dot com wrote:
> The Standard is supposed to be a formal specification of the language, so if
No, it isn't. It's for humans, who need to interpret things in an
appropriate context. As I said, editorial issues should go direct to the
project editors.
>From gcc-bugs-return-604869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 00:56:17 2018
Return-Path: <gcc-bugs-return-604869-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42588 invoked by alias); 17 May 2018 00: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 42510 invoked by uid 48); 17 May 2018 00:56:11 -0000
From: "jhb.chat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT
Date: Thu, 17 May 2018 00:56: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jhb.chat 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-85760-4-YLh4MMfJx8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01764.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #4 from Jere <jhb.chat at gmail dot com> ---
I only filed the report here once (at least purposely). The website was laggy
when I submitted so perhaps it got submitted twice accidentally? My side of
the interface only shows 2 bugs from me that are completely different from each
other (one from Jan and this one). I am unfamiliar with gnatchop, so I'll look
into it and update this one when I figure out how to do it.
>From gcc-bugs-return-604870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 01:11:28 2018
Return-Path: <gcc-bugs-return-604870-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56658 invoked by alias); 17 May 2018 01:11: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 56627 invoked by uid 48); 17 May 2018 01:11:23 -0000
From: "jhb.chat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT
Date: Thu, 17 May 2018 01:11: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jhb.chat 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: attachments.created
Message-ID: <bug-85760-4-3248S1Imrn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01765.txt.bz2
Content-length: 270
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #5 from Jere <jhb.chat at gmail dot com> ---
Created attachment 44140
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44140&action=edit
combined ada files in (hopefully) gnatchop friendly format
>From gcc-bugs-return-604871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 03:12:58 2018
Return-Path: <gcc-bugs-return-604871-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24455 invoked by alias); 17 May 2018 03:12: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 24167 invoked by uid 48); 17 May 2018 03:12:43 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Thu, 17 May 2018 03:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 8.0.1
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:
Message-ID: <bug-85801-4-T5xazKkhec@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01766.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
--- Comment #10 from H.J. Lu <hjl.tools at gmail dot com> ---
For LDPR_PREVAILING_DEF_IRONLY_EXP, if the IR definition is common,
compiler can't assume that the IR definition will prevail during the
final link. This is another COMMON symbol issue like
https://sourceware.org/bugzilla/show_bug.cgi?id=23079
>From gcc-bugs-return-604872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 03:27:38 2018
Return-Path: <gcc-bugs-return-604872-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109862 invoked by alias); 17 May 2018 03:27: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 109750 invoked by uid 48); 17 May 2018 03:27:27 -0000
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] New: make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 03:27: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: 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-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01767.txt.bz2
Content-length: 690
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
Bug ID: 85812
Summary: make_exception_ptr can leak the allocated exception if
construction throws
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redbeard0531 at gmail dot com
Target Milestone: ---
I think if this line throws the exception allocated on line 185 will leak:
https://github.com/gcc-mirror/gcc/blob/3474beffb1fd23da44a752763e648d5d1ffa4d0f/libstdc%2B%2B-v3/libsupc%2B%2B/exception_ptr.h#L189.
>From gcc-bugs-return-604873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 03:41:37 2018
Return-Path: <gcc-bugs-return-604873-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117559 invoked by alias); 17 May 2018 03: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 117535 invoked by uid 48); 17 May 2018 03:41:32 -0000
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] New: make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 03:41: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: 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-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01768.txt.bz2
Content-length: 1565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
Bug ID: 85813
Summary: make_exception_ptr should support
__cxa_init_primary_exception path even with
-fno-exceptions
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redbeard0531 at gmail dot com
Target Milestone: ---
It looks like nothing in that path actually needs exception support. This would
allow make_exception_ptr to produce a valid exception_ptr even in TUs that
don't support exceptions. While that may not sound valuable, the exception_ptr
could be handed to TUs that do support exceptions where it can be rethrown (a
misnomer in this case...) and caught.
Also, if my paper http://wg21.link/p1066 is accepted, that would provide full
support for handling the exception without ever throwing it. And if this ticket
is impossible to implement for some reason, I'd love to know that before
Rapperswil ;)
The nullptr return was added in response to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64241, but it looks like that was
done before the __cxa_init_primary_exception path existed. When that was added
in
https://github.com/gcc-mirror/gcc/commit/cce8e59224e18858749a2324bce583bcfd160d6c#diff-e1b5856b8cc940de58c12ef252d63c34R188,
I can't tell if it was put in the #if __cpp_exceptions block for a good reason
or just by default.
>From gcc-bugs-return-604874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 05:01:46 2018
Return-Path: <gcc-bugs-return-604874-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15786 invoked by alias); 17 May 2018 05:01: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 15763 invoked by uid 48); 17 May 2018 05:01:40 -0000
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85814] New: ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 05:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zeccav at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost attachments.created
Message-ID: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01769.txt.bz2
Content-length: 2258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Bug ID: 85814
Summary: ICE Segmentation fault during GIMPLE pass: strlen -O3
and above
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: zeccav at gmail dot com
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Created attachment 44141
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44141&action=edit
Preprocessed C source to be compiled with -O3 or above
// gcc 9.0.0 trunk 260152 ICE Segmentation fault during GIMPLE pass: strlen
// must be compiled with option -O3 or above
//gcc -S ~/f95/cc/gccerr68.c -O3
//during GIMPLE pass: strlen
///home/vitti/f95/cc/gccerr68.c: In function
‘cp_units_MP_cp_basic_unit_desc.constprop’:
///home/vitti/f95/cc/gccerr68.c:6388:6: internal compiler error: Segmentation
fault
// void
cp_units_MP_cp_basic_unit_desc(res_,res_Len,basic_kind_,basic_unit_,power_,accept_undefined_)
// ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
//0xc74eaf crash_signal
// ../../gcc-260152/gcc/toplev.c:325
//0x15440fa5ffcf ???
//
/usr/src/debug/glibc-2.27-37-g39071a5539/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
//0xe2b8ee unshare_strinfo
// ../../gcc-260152/gcc/tree-ssa-strlen.c:721
//0xe2dd5c get_stridx_plus_constant
// ../../gcc-260152/gcc/tree-ssa-strlen.c:800
//0xe2e2c4 get_stridx
// ../../gcc-260152/gcc/tree-ssa-strlen.c:325
//0xe3343b handle_pointer_plus
// ../../gcc-260152/gcc/tree-ssa-strlen.c:2777
//0xe3343b strlen_check_and_optimize_stmt
// ../../gcc-260152/gcc/tree-ssa-strlen.c:3237
//0xe3343b strlen_dom_walker::before_dom_children(basic_block_def*)
// ../../gcc-260152/gcc/tree-ssa-strlen.c:3521
//0x13d1c02 dom_walker::walk(basic_block_def*)
// ../../gcc-260152/gcc/domwalk.c:353
//0xe34822 execute
// ../../gcc-260152/gcc/tree-ssa-strlen.c:3601
//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-604875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 05:36:50 2018
Return-Path: <gcc-bugs-return-604875-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 49383 invoked by alias); 17 May 2018 05: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 49170 invoked by uid 48); 17 May 2018 05:36:44 -0000
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/71181] Reserving in unordered_map doesn't reserve enough
Date: Thu, 17 May 2018 05:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fdumont at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fdumont at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-71181-4-R2zMjWzGc3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-71181-4@http.gcc.gnu.org/bugzilla/>
References: <bug-71181-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01770.txt.bz2
Content-length: 461
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71181
François Dumont <fdumont at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from François Dumont <fdumont at gcc dot gnu.org> ---
Indeed, it has been fixed.
>From gcc-bugs-return-604876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 05:38:09 2018
Return-Path: <gcc-bugs-return-604876-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54242 invoked by alias); 17 May 2018 05: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 51239 invoked by uid 48); 17 May 2018 05:37:52 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Function need not be evaluated in logical expression
Date: Thu, 17 May 2018 05:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus at gcc dot gnu.org
X-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-85599-4-wl208SWE3r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01771.txt.bz2
Content-length: 864
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #19 from janus at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #17)
> Then you are only interest in the special case of .and.
>
> binop above is the entire collection of all binary
> operators (e.g., +,-,*,/ etc as well as .and.).
The original problem of ill-posed short-circuiting does not apply to all binary
operators, but only to things like:
* X = .false. .and. Y()
* X = .true. .or. Y()
and possibly:
* X = 0 * Y()
* X = 0 / Y()
(in case gfortran applies 'short-circuiting' for such cases, which I haven't
checked).
There might be other cases as well, but it certainly does not apply to + and -.
> The order of the evaluation of ping() and pong() is
> not specified by the Fortran standard.
This PR is not about reordering, but about short-circuiting.
>From gcc-bugs-return-604877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 05:48:55 2018
Return-Path: <gcc-bugs-return-604877-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88470 invoked by alias); 17 May 2018 05:48:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88251 invoked by uid 48); 17 May 2018 05:48:46 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 05:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus at gcc dot gnu.org
X-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 short_desc
Message-ID: <bug-85599-4-0BNm3PwzHU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01772.txt.bz2
Content-length: 1058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|diagnostic, |wrong-code
|missed-optimization |
Summary|Function need not be |Prevent short-circuiting of
|evaluated in logical |logical expressions for
|expression |non-pure functions
--- Comment #20 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #18)
> This PR is now about a missed optimization in the middle-end.
Well, that was absolutely not my intention when I opened this PR, and it still
isn't. Quite the opposite: I don't think gfortran should apply more
optimizations, but less. I'm changing the title and keyword again to reflect
that.
If anyone is interested in fixing some possible missed-optimization problem,
please open a new PR for that.
>From gcc-bugs-return-604878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 05:58:37 2018
Return-Path: <gcc-bugs-return-604878-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95185 invoked by alias); 17 May 2018 05:58: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 95146 invoked by uid 48); 17 May 2018 05:58:33 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT
Date: Thu, 17 May 2018 05:58: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: 7.3.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-85760-4-MVIjFBNxck@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01773.txt.bz2
Content-length: 240
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #6 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> I only filed the report here once (at least purposely).
Didn't you file exactly the same bug report with AdaCore?
>From gcc-bugs-return-604879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 06:26:53 2018
Return-Path: <gcc-bugs-return-604879-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79983 invoked by alias); 17 May 2018 06:26: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 79905 invoked by uid 48); 17 May 2018 06:26:39 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 06:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-scJfcXiIPq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01774.txt.bz2
Content-length: 798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #21 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
> Well, that was absolutely not my intention when I opened this PR, and it
> still isn't. Quite the opposite: I don't think gfortran should apply more
> optimizations, but less. I'm changing the title and keyword again to reflect
> that.
I am strictly opposed to that.
If we make guarantees that the standard does not, we will be
creating our own language (and people will get problems moving
code to another compiler). F has tried that, and failed.
Warn, yes. This is the kind of thing that -Wsurprising is for,
so people will get something with -Wall. (I volunteer for that).
Optimize, yes. This could also be integrated with the warning.
Change the language, no.
>From gcc-bugs-return-604880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 06:41:41 2018
Return-Path: <gcc-bugs-return-604880-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116809 invoked by alias); 17 May 2018 06: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 116756 invoked by uid 48); 17 May 2018 06:41:35 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 06:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-mLim4WLRdg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01775.txt.bz2
Content-length: 295
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #22 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
I don't think the middle end can even change. the semantics of TRUTH_ANDIF_EXPR
is always to short circuit. If you want a non short circuit you need to use
TRUTH_AND_EXPR
>From gcc-bugs-return-604881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 06:53:03 2018
Return-Path: <gcc-bugs-return-604881-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124346 invoked by alias); 17 May 2018 06: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 124265 invoked by uid 48); 17 May 2018 06:52:57 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 06:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus at gcc dot gnu.org
X-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-85599-4-V8YWVUfdW6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01776.txt.bz2
Content-length: 957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #23 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #21)
> If we make guarantees that the standard does not, we will be
> creating our own language
I certainly don't want to create my own language. I'm trying to use the freedom
that the Fortran standard (unfortunately) gives in this area in a reasonable
way.
> (and people will get problems moving
> code to another compiler).
We do have problems with compiler-dependent behavior already. The behavior I'm
proposing is consistent with what ifort, PGI and flang do.
> Warn, yes. This is the kind of thing that -Wsurprising is for,
> so people will get something with -Wall. (I volunteer for that).
What do you want to warn about? And how?
> Optimize, yes. This could also be integrated with the warning.
Optimize, yes, but not at the price of changing results.
> Change the language, no.
Agreed.
>From gcc-bugs-return-604882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 06:58:21 2018
Return-Path: <gcc-bugs-return-604882-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128325 invoked by alias); 17 May 2018 06:58:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 128243 invoked by uid 55); 17 May 2018 06:58:17 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85757] tree optimizers fail to fully clean up fixed-size memcpy
Date: Thu, 17 May 2018 06:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: 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-85757-4-crfEgDR6eD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01777.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85757
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Author: rguenth
Date: Thu May 17 06:57:45 2018
New Revision: 260306
URL: https://gcc.gnu.org/viewcvs?rev=260306&root=gcc&view=rev
Log:
2018-05-17 Richard Biener <rguenther@suse.de>
PR tree-optimization/85757
* tree-ssa-dse.c (dse_classify_store): Record a PHI def and
remove defs that only feed that PHI from further processing.
* gcc.dg/tree-ssa/ssa-dse-34.c: New testcase.
Added:
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-dse-34.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-dse.c
>From gcc-bugs-return-604883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 06:59:13 2018
Return-Path: <gcc-bugs-return-604883-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8592 invoked by alias); 17 May 2018 06:59: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 4703 invoked by uid 48); 17 May 2018 06:59:08 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85757] tree optimizers fail to fully clean up fixed-size memcpy
Date: Thu, 17 May 2018 06:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85757-4-6P9bR2GDvt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85757-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85757-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01778.txt.bz2
Content-length: 438
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85757
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 on trunk.
>From gcc-bugs-return-604884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:06:08 2018
Return-Path: <gcc-bugs-return-604884-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72339 invoked by alias); 17 May 2018 07: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 72310 invoked by uid 48); 17 May 2018 07:06:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 07:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection, needs-reduction
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-85814-4-OogY7BVXsG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01779.txt.bz2
Content-length: 1223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Known to work| |7.3.1
Keywords| |ice-on-valid-code,
| |needs-bisection,
| |needs-reduction
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
Summary|ICE Segmentation fault |[8/9 Regression] ICE
|during GIMPLE pass: strlen |Segmentation fault during
|-O3 and above |GIMPLE pass: strlen -O3 and
| |above
Target Milestone|--- |8.2
Known to fail| |8.1.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
I can reproduce this on the GCC 8 branch but not on trunk.
>From gcc-bugs-return-604885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:11:40 2018
Return-Path: <gcc-bugs-return-604885-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87648 invoked by alias); 17 May 2018 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 87602 invoked by uid 48); 17 May 2018 07:11:36 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 07:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus at gcc dot gnu.org
X-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-85599-4-ucGoQPgi2Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01780.txt.bz2
Content-length: 860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #24 from janus at gcc dot gnu.org ---
(In reply to Andrew Pinski from comment #22)
> the semantics of TRUTH_ANDIF_EXPR is always to short circuit.
> If you want a non short circuit you need to use TRUTH_AND_EXPR
I haven't looked at the actual code yet, but pr57160 comment 1 sounds like we
already use TRUTH_AND_EXPR:
> GCC (the middle end) has TRUTH_AND_EXPR (matching Fortran's .AND.) and
> TRUTH_ANDIF_EXPR (matching C's &&) - besides the IAND/& which is
> BIT_AND_EXPR.
>
> Currently, the code generation directly translates all .AND. into
> TRUTH_AND_EXPR.
If that's indeed the case, and TRUTH_AND_EXPR actually results in
short-circuiting, then I'm not sure I understand the difference to
TRUTH_ANDIF_EXPR.
Probably BIT_AND_EXPR can be used to fully prevent short-circuiting?
>From gcc-bugs-return-604886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:12:51 2018
Return-Path: <gcc-bugs-return-604886-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88898 invoked by alias); 17 May 2018 07:12:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 88840 invoked by uid 48); 17 May 2018 07:12:48 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT
Date: Thu, 17 May 2018 07:12: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-85760-4-fTSIG1oH9x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01781.txt.bz2
Content-length: 495
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.0
--- Comment #7 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Upgrade to GCC 8.
>From gcc-bugs-return-604887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:17:05 2018
Return-Path: <gcc-bugs-return-604887-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102775 invoked by alias); 17 May 2018 07:17: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 102685 invoked by uid 48); 17 May 2018 07:16:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85811] Invalid optimization with fmax, fabs and nan
Date: Thu, 17 May 2018 07:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc component everconfirmed
Message-ID: <bug-85811-4-bCGygBAwNU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01782.txt.bz2
Content-length: 1938
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
CC| |rguenth at gcc dot gnu.org
Component|rtl-optimization |middle-end
Ever confirmed|0 |1
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #6)
> What does tree_expr_nonnegative_p call non-negative? A natural definition
> would exclude NaN, but for REAL_CST we just return ! REAL_VALUE_NEGATIVE.
Is there sth like -NaN?!
Anyway, the bug is clearly in tree_expr_nonnegative_p and siblings. Btw,
tree_binary_nonzero_warnv_p looks similarly suspicious.
I guess first of all
diff --git a/gcc/fold-const.c b/gcc/fold-const.c
index faa184a2bbd..cb3de26f9f1 100644
--- a/gcc/fold-const.c
+++ b/gcc/fold-const.c
@@ -12949,7 +12949,8 @@ tree_single_nonnegative_warnv_p (tree t, bool
*strict_overflow_p, int depth)
return tree_int_cst_sgn (t) >= 0;
case REAL_CST:
- return ! REAL_VALUE_NEGATIVE (TREE_REAL_CST (t));
+ return (! REAL_VALUE_ISNAN (TREE_REAL_CST (t))
+ && ! REAL_VALUE_NEGATIVE (TREE_REAL_CST (t)));
case FIXED_CST:
return ! FIXED_VALUE_NEGATIVE (TREE_FIXED_CST (t));
but then how do we want to deal with MAX_EXPR (and MIN_EXPR which after the
above could see an optimization for min (NaN, x)?). We'd have to special
case real-type MAX_EXPR (what about real complex/vector?
tree_single_nonnegative_warnv_p doesn't handle complex/vector constants
but at least we should be correct in the uplevel treatment).
>From gcc-bugs-return-604889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:18:53 2018
Return-Path: <gcc-bugs-return-604889-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115316 invoked by alias); 17 May 2018 07:18: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 115267 invoked by uid 48); 17 May 2018 07:18:49 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85810] gcc incorrectly handles declarations inside parameter lists of function declarators.
Date: Thu, 17 May 2018 07:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85810-4-90SM9azhox@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01784.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85810
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |MOVED
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
moved.
>From gcc-bugs-return-604888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:18:09 2018
Return-Path: <gcc-bugs-return-604888-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113853 invoked by alias); 17 May 2018 07:18: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 113749 invoked by uid 48); 17 May 2018 07:18:02 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 07:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-8myRgxor4f@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01783.txt.bz2
Content-length: 1565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #25 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to janus from comment #23)
> (In reply to Thomas Koenig from comment #21)
> > If we make guarantees that the standard does not, we will be
> > creating our own language
>
> I certainly don't want to create my own language. I'm trying to use the
> freedom that the Fortran standard (unfortunately) gives in this area in a
> reasonable way.
>
>
> > (and people will get problems moving
> > code to another compiler).
>
> We do have problems with compiler-dependent behavior already. The behavior
> I'm proposing is consistent with what ifort, PGI and flang do.
But that is something not guaranteed by the standard...
>
> > Warn, yes. This is the kind of thing that -Wsurprising is for,
> > so people will get something with -Wall. (I volunteer for that).
>
> What do you want to warn about? And how?
A front end pass (what else did you expect? :-)
If an impure function is found (recursively) in the operands of an .AND.
expression, issue a
gfc_warning(OPT_Wsurprising, "Impure function %qs at %L may not be
evaluated", ...)
So,
if (flag .and. f(x) > 0.)
would also be warned about.
>
> > Optimize, yes. This could also be integrated with the warning.
>
> Optimize, yes, but not at the price of changing results.
Not against what the standard guarantees.
> > Change the language, no.
>
> Agreed.
But that is what you are proposing - we would make a guarantee that
the standard does not make.
>From gcc-bugs-return-604890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:27:28 2018
Return-Path: <gcc-bugs-return-604890-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7680 invoked by alias); 17 May 2018 07: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 7614 invoked by uid 48); 17 May 2018 07:27:21 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63185] Improve DSE with branches
Date: Thu, 17 May 2018 07:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: missed-optimization
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-63185-4-OQGdhWzWkJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01785.txt.bz2
Content-length: 390
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #7 from Marc Glisse <glisse at gcc dot gnu.org> ---
This PR is messy. To sum up, comment #0 was recently fixed, comment #5 is not
(not noticing that the writes in the loop are dead), and comment #6 asks for
increasing the alignment of VLAs the same way we sometimes increase the
alignment of arrays to help vectorization.
>From gcc-bugs-return-604891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:28:07 2018
Return-Path: <gcc-bugs-return-604891-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8831 invoked by alias); 17 May 2018 07:28: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 8764 invoked by uid 48); 17 May 2018 07:28:03 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/85801] LTO linking fails to reconcile symbol from common an data sections (-fPIE -Wl,--as-needed -flto): unresolvable R_ARM_REL32 relocation against symbol `progname'
Date: Thu, 17 May 2018 07: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: 8.0.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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85801-4-8tGiX8F4EM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85801-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01786.txt.bz2
Content-length: 1943
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85801
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
CC| |hubicka at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to H.J. Lu from comment #10)
> For LDPR_PREVAILING_DEF_IRONLY_EXP, if the IR definition is common,
> compiler can't assume that the IR definition will prevail during the
> final link. This is another COMMON symbol issue like
>
> https://sourceware.org/bugzilla/show_bug.cgi?id=23079
So the following might help (and shows bad abstraction of
resolution_to_local_definition_p which depends on symbol type).
Similar fixes would be needed for decl_binds_to_current_def_p
(somehow split out code computing defined_locally and resolved_locally
based on resolution from the former function).
In other places the cgraph code seems to honor the fact that a
common might be prevailed.
Honza?
diff --git a/gcc/varasm.c b/gcc/varasm.c
index 85296b4a2ec..1021237389e 100644
--- a/gcc/varasm.c
+++ b/gcc/varasm.c
@@ -7075,7 +7075,9 @@ default_binds_local_p_3 (const_tree exp, bool shlib, bool
weak_dominate,
defined_locally = true;
if (node->can_be_discarded_p ())
;
- else if (resolution_to_local_definition_p (node->resolution))
+ else if (resolution_to_local_definition_p (node->resolution)
+ && (defined_locally
+ || node->resolution != LDPR_PREVAILING_DEF_IRONLY_EXP))
defined_locally = resolved_locally = true;
else if (resolution_local_p (node->resolution))
resolved_locally = true;
>From gcc-bugs-return-604893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:44:45 2018
Return-Path: <gcc-bugs-return-604893-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15326 invoked by alias); 17 May 2018 07:44: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 10642 invoked by uid 48); 17 May 2018 07:44:41 -0000
From: "m.diehl at mpie dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85816] New: nested spread fails with "Integer overflow in xmallocarray"
Date: Thu, 17 May 2018 07:44: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: m.diehl at mpie 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-85816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01788.txt.bz2
Content-length: 1939
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
Bug ID: 85816
Summary: nested spread fails with "Integer overflow in
xmallocarray"
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: m.diehl at mpie dot de
Target Milestone: ---
I'm having trouble with nested spread statements on GCC 8.1.0 (Linux
4.16.8-1-ARCH). The same code runs on GCC 7.3.0 (Linux 4.4.0-98-generic). A
seemingly unnecessary set of brackets cures the following error:
Operating system error: Cannot allocate memory
Integer overflow in xmallocarray
when running the following code
program test
implicit none
real(8), dimension(3,3) :: tensor = 4.0
integer, dimension(3) :: grid= 16
write(6,*) spread(spread(tensor,3,grid(1)),4,grid(2)) ! ok
write(6,*) spread((spread(spread(tensor,3,grid(1)),4,grid(2))),5,grid(3)) !
ok (note the brackets)
write(6,*) spread(spread(spread(tensor,3,grid(1)),4,grid(2)),5,grid(3)) ! not
ok
end program
>From gcc-bugs-return-604892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 07:44:45 2018
Return-Path: <gcc-bugs-return-604892-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15203 invoked by alias); 17 May 2018 07:44: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 8330 invoked by uid 48); 17 May 2018 07:44:39 -0000
From: "v at vsamko dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85815] New: incorrect "invalid use of incomplete type" in a lambda on valid code
Date: Thu, 17 May 2018 07: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.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: v at vsamko 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-85815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01787.txt.bz2
Content-length: 983
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85815
Bug ID: 85815
Summary: incorrect "invalid use of incomplete type" in a lambda
on valid code
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: v at vsamko dot com
Target Milestone: ---
This valid code:
template<class T>
class A {
static A* INSTANCE;
void foobar();
void moo() {}
};
template<class T>
A<T>* A<T>::INSTANCE = nullptr;
template<class T>
void A<T>::foobar() {
auto x = []() {
INSTANCE->moo();
};
}
(compiled with -Wall)
Gives error:
<source>: In lambda function:
<source>:14:17: error: invalid use of incomplete type 'class A<T>' [-Werror]
INSTANCE->moo();
This compiles fine with Clang and GCC 6, but fails with the error above with
GCC 7 and 8.
>From gcc-bugs-return-604894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:05:03 2018
Return-Path: <gcc-bugs-return-604894-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7969 invoked by alias); 17 May 2018 08:05:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7904 invoked by uid 48); 17 May 2018 08:04:56 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63185] Improve DSE with branches
Date: Thu, 17 May 2018 08: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: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63185-4-qlDBkB6KFI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01789.txt.bz2
Content-length: 1668
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
comment#5 runs into the fact that we cannot reliably compute kills for
loop-variant stores and thus we give up completely:
if (gimple_code (temp) == GIMPLE_PHI)
{
/* If we visit this PHI by following a backedge then we have to
make sure ref->ref only refers to SSA names that are invariant
with respect to the loop represented by this PHI node. */
if (dominated_by_p (CDI_DOMINATORS, gimple_bb (stmt),
gimple_bb (temp))
&& !for_each_index (ref->ref ? &ref->ref : &ref->base,
check_name, gimple_bb (temp)))
return DSE_STORE_LIVE;
but what we could do is somehow massage the ref to not get false
positive stmt_kills_ref_p or false negative ref_maybe_used_by_stmt_p
results. That could for example involve stripping all components
with variable names in them (and then also disabling byte-tracking).
For varying bases we still need to give up completely.
A backward data-flow algorithm might have an easier time dealing with this
case.
As for the value-numbering issue we currently do not use number of iteration
analysis / range-info to constrain the ao_ref max_size/offset. That's probably
a useful thing to add and might already help. In this case it doesn't
because the range is one too large (head controlled loop). And VRP doesn't
run after CH when FRE/PRE still runs afterwards. And value-numbering visiting
memset doesn't handle pointer destinations (that's easy to fix).
>From gcc-bugs-return-604895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:33:06 2018
Return-Path: <gcc-bugs-return-604895-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12784 invoked by alias); 17 May 2018 08:33:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12662 invoked by uid 48); 17 May 2018 08:33:01 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85811] Invalid optimization with fmax, fabs and nan
Date: Thu, 17 May 2018 08:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-WJU1ypeH64@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01790.txt.bz2
Content-length: 167
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #8 from Andreas Schwab <schwab@linux-m68k.org> ---
> Is there sth like -NaN?!
signbit can tell you.
>From gcc-bugs-return-604896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:39:43 2018
Return-Path: <gcc-bugs-return-604896-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24324 invoked by alias); 17 May 2018 08:39: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 24280 invoked by uid 48); 17 May 2018 08:39:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63185] Improve DSE with branches
Date: Thu, 17 May 2018 08: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: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63185-4-ryANppkiSj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01791.txt.bz2
Content-length: 4305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> ---
So the following incomplete patch solves the value-numbering issue in FRE2.
diff --git a/gcc/tree-dfa.c b/gcc/tree-dfa.c
index a121b880bb0..745d60cbda5 100644
--- a/gcc/tree-dfa.c
+++ b/gcc/tree-dfa.c
@@ -529,6 +529,31 @@ get_ref_base_and_extent (tree exp, poly_int64_pod
*poffset,
/* Remember that we have seen an array ref with a variable
index. */
seen_variable_array_ref = true;
+
+ wide_int min, max;
+ if (TREE_CODE (index) == SSA_NAME
+ && integer_zerop (array_ref_low_bound (exp))
+ && (unit_size = array_ref_element_size (exp),
+ TREE_CODE (unit_size) == INTEGER_CST)
+ && get_range_info (index, &min, &max) == VR_RANGE
+ && wi::gts_p (max, 0))
+ {
+ poly_offset_int rmaxsize;
+ rmaxsize = offset_int::from (max, UNSIGNED) * wi::to_offset
(unit_size);
+ if (known_size_p (maxsize))
+ {
+ if (known_lt (rmaxsize, maxsize))
+ {
+ maxsize = rmaxsize;
+ seen_variable_array_ref = false;
+ }
+ }
+ else
+ {
+ maxsize = rmaxsize;
+ seen_variable_array_ref = false;
+ }
+ }
}
}
break;
diff --git a/gcc/tree-ssa-sccvn.c b/gcc/tree-ssa-sccvn.c
index 1463c1d4116..dad4e4fecdf 100644
--- a/gcc/tree-ssa-sccvn.c
+++ b/gcc/tree-ssa-sccvn.c
@@ -1960,19 +1960,46 @@ vn_reference_lookup_3 (ao_ref *ref, tree vuse, void
*vr_,
&& gimple_call_builtin_p (def_stmt, BUILT_IN_MEMSET)
&& integer_zerop (gimple_call_arg (def_stmt, 1))
&& poly_int_tree_p (gimple_call_arg (def_stmt, 2))
- && TREE_CODE (gimple_call_arg (def_stmt, 0)) == ADDR_EXPR)
+ && (TREE_CODE (gimple_call_arg (def_stmt, 0)) == ADDR_EXPR
+ || TREE_CODE (gimple_call_arg (def_stmt, 0)) == SSA_NAME))
{
- tree ref2 = TREE_OPERAND (gimple_call_arg (def_stmt, 0), 0);
tree base2;
poly_int64 offset2, size2, maxsize2;
bool reverse;
- base2 = get_ref_base_and_extent (ref2, &offset2, &size2, &maxsize2,
- &reverse);
+ tree ref2 = gimple_call_arg (def_stmt, 0);
+ if (TREE_CODE (ref2) == SSA_NAME)
+ {
+ ref2 = SSA_VAL (ref2);
+ if (TREE_CODE (ref2) == SSA_NAME
+ && (TREE_CODE (base) != MEM_REF
+ || TREE_OPERAND (base, 0) != ref2))
+ {
+ gimple *def_stmt = SSA_NAME_DEF_STMT (ref2);
+ if (gimple_assign_single_p (def_stmt)
+ && gimple_assign_rhs_code (def_stmt) == ADDR_EXPR)
+ ref2 = gimple_assign_rhs1 (def_stmt);
+ }
+ }
+ if (TREE_CODE (ref2) == ADDR_EXPR)
+ {
+ ref2 = TREE_OPERAND (ref2, 0);
+ base2 = get_ref_base_and_extent (ref2, &offset2, &size2, &maxsize2,
+ &reverse);
+ if (!known_size_p (maxsize2)
+ || !operand_equal_p (base, base2, 0))
+ return (void *)-1;
+ }
+ else
+ {
+ if (TREE_CODE (base) != MEM_REF
+ || TREE_OPERAND (base, 0) != ref2
+ || !integer_zerop (TREE_OPERAND (base, 1)))
+ return (void *)-1;
+ offset2 = 0;
+ }
tree len = gimple_call_arg (def_stmt, 2);
- if (known_size_p (maxsize2)
- && operand_equal_p (base, base2, 0)
- && known_subrange_p (offset, maxsize, offset2,
- wi::to_poly_offset (len) << LOG2_BITS_PER_UNIT))
+ if (known_subrange_p (offset, maxsize, offset2,
+ wi::to_poly_offset (len) << LOG2_BITS_PER_UNIT))
{
tree val = build_zero_cst (vr->type);
return vn_reference_lookup_or_insert_for_pieces
>From gcc-bugs-return-604897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:41:31 2018
Return-Path: <gcc-bugs-return-604897-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29201 invoked by alias); 17 May 2018 08:41: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 29120 invoked by uid 48); 17 May 2018 08:41:25 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 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: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection, needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85814-4-LMavZagHD8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01792.txt.bz2
Content-length: 408
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
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> ---
I'm reducing that..
>From gcc-bugs-return-604898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:47:44 2018
Return-Path: <gcc-bugs-return-604898-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38628 invoked by alias); 17 May 2018 08:47:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38578 invoked by uid 55); 17 May 2018 08:47:39 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85811] Invalid optimization with fmax, fabs and nan
Date: Thu, 17 May 2018 08:47: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.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85811-4-x4LVeqSRQ0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85811-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01793.txt.bz2
Content-length: 674
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
--- Comment #9 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 17 May 2018, schwab@linux-m68k.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85811
>
> --- Comment #8 from Andreas Schwab <schwab@linux-m68k.org> ---
> > Is there sth like -NaN?!
>
> signbit can tell you.
True. I guess that also asks for the guarantee on the operand
for tree_single_nonnegative_warnv_p returning true. Does it
guarantee that OP >= 0 compares as true? Or merely !(OP < 0)?
So does it make sense for the function to return true for +NaN
or should we err on the side of caution and not do that?
>From gcc-bugs-return-604899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:55:37 2018
Return-Path: <gcc-bugs-return-604899-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81810 invoked by alias); 17 May 2018 08:55: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 81727 invoked by uid 48); 17 May 2018 08:55:33 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 08:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code, needs-bisection
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-85814-4-gB3rNxaRMS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01794.txt.bz2
Content-length: 555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-reduction |
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Reduced test-case:
int a;
void b(c, d, e, f, g, h) char *c;
int d;
int e;
int f;
int g;
int h;
{
int i;
c++;
c++;
c++;
c++;
i = 0;
for (; i < 10; i++)
a = *c++ = 2;
}
>From gcc-bugs-return-604900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 08:57:24 2018
Return-Path: <gcc-bugs-return-604900-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85345 invoked by alias); 17 May 2018 08:57:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85220 invoked by uid 48); 17 May 2018 08:57:20 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 08:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-85814-4-rvwZ7gqAXx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01795.txt.bz2
Content-length: 621
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|needs-bisection |
CC| |jakub at gcc dot gnu.org,
| |msebor at gcc dot gnu.org,
| |rdsandiford at googlemail dot com
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Started with r249880.
>From gcc-bugs-return-604901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:05:50 2018
Return-Path: <gcc-bugs-return-604901-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27124 invoked by alias); 17 May 2018 09:05:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25577 invoked by uid 48); 17 May 2018 09:05:41 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 09:05: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 everconfirmed
Message-ID: <bug-85812-4-elI4BIkOtp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01796.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
>From gcc-bugs-return-604902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:17:59 2018
Return-Path: <gcc-bugs-return-604902-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20527 invoked by alias); 17 May 2018 09:17:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20228 invoked by uid 48); 17 May 2018 09:17:55 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 09: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:
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-85813-4-pWdaIlRQsx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01797.txt.bz2
Content-length: 468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
As you pointed out in PR 85812 the constructor of the exception can throw. That
can happen even if the current translation unit is not built with exceptions,
if the constructor is defined in a different translation unit.
Since make_exception_ptr is noexcept, we simply avoid the possibility of
termination by returning an empty exception_ptr.
>From gcc-bugs-return-604904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:18:44 2018
Return-Path: <gcc-bugs-return-604904-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 22332 invoked by alias); 17 May 2018 09:18:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 22306 invoked by uid 48); 17 May 2018 09:18:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 09:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85813-4-ZdRYfbte0l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01799.txt.bz2
Content-length: 240
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
... because if that constructor throws and the current translation unit is
built without exceptions, we can't catch it.
>From gcc-bugs-return-604903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:18:34 2018
Return-Path: <gcc-bugs-return-604903-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21646 invoked by alias); 17 May 2018 09:18: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 21592 invoked by uid 55); 17 May 2018 09:18:29 -0000
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85713] [9 Regression] ICE in dependent_type_p, at cp/pt.c:24582 on valid code
Date: Thu, 17 May 2018 09: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85713-4-MAJNqBDvSA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85713-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85713-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01798.txt.bz2
Content-length: 514
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85713
--- Comment #8 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Thu May 17 09:17:56 2018
New Revision: 260308
URL: https://gcc.gnu.org/viewcvs?rev=260308&root=gcc&view=rev
Log:
2018-05-17 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/85713
* g++.dg/cpp1y/lambda-generic-85713-2.C: New.
Added:
trunk/gcc/testsuite/g++.dg/cpp1y/lambda-generic-85713-2.C
Modified:
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:27:13 2018
Return-Path: <gcc-bugs-return-604905-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45532 invoked by alias); 17 May 2018 09:27: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 44915 invoked by uid 48); 17 May 2018 09:27:06 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69905] Digit separators break literal operators
Date: Thu, 17 May 2018 09:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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-69905-4-Emn7Q9mFqJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01800.txt.bz2
Content-length: 532
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69905
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The testcase in comment 2 (the only one in the bug that's actually correct!)
works now, fixed by r258157 for Bug 84671.
The problem in comment 7 still exists, the corrected testcase is:
#include <chrono>
int main() {
using namespace std::chrono_literals;
auto time = operator""s(0x8000'0000'0000'0000'0000'0000ULL);
static_assert(std::is_same<decltype(time)::rep, unsigned long long>(), "");
}
>From gcc-bugs-return-604906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:33:05 2018
Return-Path: <gcc-bugs-return-604906-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82209 invoked by alias); 17 May 2018 09:33:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82119 invoked by uid 48); 17 May 2018 09:33:01 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85815] [7/8/9 Regression] incorrect "invalid use of incomplete type" in a lambda on valid code
Date: Thu, 17 May 2018 09:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: diagnostic, 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: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on everconfirmed short_desc target_milestone
Message-ID: <bug-85815-4-dco877okLF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85815-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85815-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01801.txt.bz2
Content-length: 1003
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85815
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P2
Status|UNCONFIRMED |NEW
Known to work| |6.4.0
Keywords| |diagnostic, rejects-valid
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
Summary|incorrect "invalid use of |[7/8/9 Regression]
|incomplete type" in a |incorrect "invalid use of
|lambda on valid code |incomplete type" in a
| |lambda on valid code
Target Milestone|--- |7.4
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-604907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:44:25 2018
Return-Path: <gcc-bugs-return-604907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96353 invoked by alias); 17 May 2018 09:44: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 96288 invoked by uid 48); 17 May 2018 09:44:20 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 09: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: wrong-code
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus at gcc dot gnu.org
X-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-85599-4-a9btcLL1IR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01802.txt.bz2
Content-length: 1360
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #26 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #25)
> > We do have problems with compiler-dependent behavior already. The behavior
> > I'm proposing is consistent with what ifort, PGI and flang do.
>
> But that is something not guaranteed by the standard...
Does not make too much difference in the end, does it? You still have code that
gives different results with different compilers, which is always a bad thing.
That's exactly why I think it was a bad decision for the standard to leave this
decision to the compiler.
> > > Optimize, yes. This could also be integrated with the warning.
> >
> > Optimize, yes, but not at the price of changing results.
>
> Not against what the standard guarantees.
Does. Not. Matter.
It is still an optimization that changes the end result, which is generally a
bad thing IMHO. Even if some standards document says "it's not illegal", I
would say "it's still a bad idea"!
> > > Change the language, no.
> >
> > Agreed.
>
> But that is what you are proposing - we would make a guarantee that
> the standard does not make.
Disagree. We wouldn't make a guarantee, we would just choose one of two
possible implementations that are allowed by the standard. That's not "changing
the language".
>From gcc-bugs-return-604908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 09:55:14 2018
Return-Path: <gcc-bugs-return-604908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2325 invoked by alias); 17 May 2018 09: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 130128 invoked by uid 55); 17 May 2018 09:55:09 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85323] SSE/AVX/AVX512 shift by 0 not optimized away
Date: Thu, 17 May 2018 09:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
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-85323-4-v7OP8Fpn0C@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01803.txt.bz2
Content-length: 918
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu May 17 09:54:36 2018
New Revision: 260311
URL: https://gcc.gnu.org/viewcvs?rev=260311&root=gcc&view=rev
Log:
PR target/85323
* config/i386/i386.c: Include tree-vector-builder.h.
(ix86_vector_shift_count): New function.
(ix86_fold_builtin): Fold shift builtins by scalar count.
(ix86_gimple_fold_builtin): Likewise.
* gcc.target/i386/pr85323-1.c: New test.
* gcc.target/i386/pr85323-2.c: New test.
* gcc.target/i386/pr85323-3.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr85323-1.c
trunk/gcc/testsuite/gcc.target/i386/pr85323-2.c
trunk/gcc/testsuite/gcc.target/i386/pr85323-3.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:02:14 2018
Return-Path: <gcc-bugs-return-604909-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85547 invoked by alias); 17 May 2018 10: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 85461 invoked by uid 55); 17 May 2018 10:02:06 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85323] SSE/AVX/AVX512 shift by 0 not optimized away
Date: Thu, 17 May 2018 10:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
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-85323-4-Si361rPtwj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01804.txt.bz2
Content-length: 831
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu May 17 10:01:33 2018
New Revision: 260312
URL: https://gcc.gnu.org/viewcvs?rev=260312&root=gcc&view=rev
Log:
PR target/85323
* config/i386/i386.c (ix86_fold_builtin): Fold shift builtins by
vector.
(ix86_gimple_fold_builtin): Likewise.
* gcc.target/i386/pr85323-4.c: New test.
* gcc.target/i386/pr85323-5.c: New test.
* gcc.target/i386/pr85323-6.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr85323-4.c
trunk/gcc/testsuite/gcc.target/i386/pr85323-5.c
trunk/gcc/testsuite/gcc.target/i386/pr85323-6.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:07:49 2018
Return-Path: <gcc-bugs-return-604912-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99213 invoked by alias); 17 May 2018 10: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 99125 invoked by uid 55); 17 May 2018 10:07:45 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85323] SSE/AVX/AVX512 shift by 0 not optimized away
Date: Thu, 17 May 2018 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
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-85323-4-mS4n0sVVzC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85323-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85323-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01807.txt.bz2
Content-length: 809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85323
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Thu May 17 10:07:12 2018
New Revision: 260313
URL: https://gcc.gnu.org/viewcvs?rev=260313&root=gcc&view=rev
Log:
PR target/85323
* config/i386/i386.c (ix86_fold_builtin): Handle masked shifts
even if the mask is not all ones.
* gcc.target/i386/pr85323-7.c: New test.
* gcc.target/i386/pr85323-8.c: New test.
* gcc.target/i386/pr85323-9.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr85323-7.c
trunk/gcc/testsuite/gcc.target/i386/pr85323-8.c
trunk/gcc/testsuite/gcc.target/i386/pr85323-9.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/i386/i386.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:07:08 2018
Return-Path: <gcc-bugs-return-604911-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96064 invoked by alias); 17 May 2018 10:07: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 95886 invoked by uid 48); 17 May 2018 10:07:04 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/84671] [6/7 Regression] Chrono literals don't accept apostrophe as separator
Date: Thu, 17 May 2018 10: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: 8.0.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: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84671-4-RbYW9bBt0o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84671-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84671-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01806.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84671
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |alisdairm at me dot com
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 69905 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:07:07 2018
Return-Path: <gcc-bugs-return-604910-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95946 invoked by alias); 17 May 2018 10:07:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95850 invoked by uid 48); 17 May 2018 10:07:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/69905] Digit separators break literal operators
Date: Thu, 17 May 2018 10:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 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: 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-69905-4-EBqaydycTc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-69905-4@http.gcc.gnu.org/bugzilla/>
References: <bug-69905-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01805.txt.bz2
Content-length: 2425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69905
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #9 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to andreas.molzer from comment #7)
> Leaving out the overload for operator""s(long double) will silently break
We provide that overload though. What do you mean?
> valid code. Consider:
>
> #include <chrono>
> int main() {
> using std::chrono_literals;
> auto time = operator""s(0x8000'0000'0000'0000'0000'0000ULL);
> }
>
> According to standard, this should select the overload with unsigned long
> long argument, which does not exist.
No, according to the standard this is ill-formed because the value doesn't fit
in an unsigned long long (assuming 64 bits). GCC accepts it unless you use
-pedantic-errors, but this isn't valid code.
> It will instead silently perform a
> numeric conversion to long double, resulting in loss of accuracy on targets
> where gcc does not use extended 80-bit double. Any other integer arguments,
> which should lead to overload resolution failure, will also be double
> durations albeit with less immediately catastrophic results.
Again, this doesn't silently break valid code, because what you're doing should
be ill-formed according to the standard. So not valid code.
> However, that doesn't mean the long term effects are no issue. Consider
> that the type of time.count() also unexpectedly resolves as long double. Or
> even worse that assigning decltype(time)::max() to unsigned long long is
> undefined behaviour.
>
> It might be more fitting to open the missing declarations as a separately
> tracked bug, improving visibility of the standard issue as well.
Feel free to open a new bug (but this is not the place to report problems in
the standard, see https://cplusplus.github.io/LWG/lwg-active.html#submit_issue
for that).
I'm going to close this one as a dup of Bug 84671 because I don't think there's
any compiler bug here. The original problem was due to the library not handling
digit separators in its UDL operators, which is fixed.
*** This bug has been marked as a duplicate of bug 84671 ***
>From gcc-bugs-return-604913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:08:47 2018
Return-Path: <gcc-bugs-return-604913-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100463 invoked by alias); 17 May 2018 10:08: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 100433 invoked by uid 48); 17 May 2018 10:08:42 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85817] New: [9 Regression] ICE in expand_call at gcc/calls.c:4291
Date: Thu, 17 May 2018 10:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 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-85817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01808.txt.bz2
Content-length: 13223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
Bug ID: 85817
Summary: [9 Regression] ICE in expand_call at gcc/calls.c:4291
Product: gcc
Version: unknown
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: ipa
Assignee: unassigned at gcc dot gnu.org
Reporter: marxin at gcc dot gnu.org
CC: marxin at gcc dot gnu.org, prathamesh3492 at gcc dot gnu.org
Target Milestone: ---
Starting from r260250 I see ICE in GIMP being built with -O3 and -flto.
Unfortunately it happens in ltrans, thus it's hard to reduce a reproducer. So:
$ ./lto1 -quiet -dumpdir .libs/ -dumpbase gimp-2.9.ltrans3 -mtune=generic
-march=x86-64 -mtune=generic -march=x86-64 -auxbase-strip
gimp-2.9.ltrans3.ltrans.o -O3 -O3 -O3 -Werror=missing-prototypes -Wtype-limits
-version -fno-openacc -fno-common -fdiagnostics-show-option -fopenmp -fltrans
/home/marxin/BIG/buildbot/slave/source/gimp/app/gimp-2.9.ltrans3.o -o
gimp-2.9.ltrans3.s
GNU GIMPLE (GCC) version 9.0.0 20180515 (experimental) (x86_64-pc-linux-gnu)
compiled by GNU C version 7.3.1 20180323 [gcc-7-branch revision
258812], GMP version 6.1.2, MPFR version 4.0.1-p6, MPC version 1.1.0, isl
version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
GNU GIMPLE (GCC) version 9.0.0 20180515 (experimental) (x86_64-pc-linux-gnu)
compiled by GNU C version 7.3.1 20180323 [gcc-7-branch revision
258812], GMP version 6.1.2, MPFR version 4.0.1-p6, MPC version 1.1.0, isl
version isl-0.19-GMP
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
during RTL pass: expand
gimpwindow.c: In function ‘gimp_window_key_press_event’:
gimpwindow.c:200:9: internal compiler error: Segmentation fault
0xf336c9 crash_signal
../../gcc/toplev.c:325
0x8d2290 expand_call(tree_node*, rtx_def*, int)
../../gcc/calls.c:4287
0xa954be expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../gcc/expr.c:11011
0xa8734c expand_expr_real(tree_node*, rtx_def*, machine_mode, expand_modifier,
rtx_def**, bool)
../../gcc/expr.c:8235
0x8e4c27 expand_expr
../../gcc/expr.h:280
0x8ede19 expand_call_stmt
../../gcc/cfgexpand.c:2690
0x8f1661 expand_gimple_stmt_1
../../gcc/cfgexpand.c:3644
0x8f1dbb expand_gimple_stmt
../../gcc/cfgexpand.c:3810
0x8fab6e expand_gimple_basic_block
../../gcc/cfgexpand.c:5839
0x8fc7f9 execute
../../gcc/cfgexpand.c:6445
(gdb) p valreg
$2 = (rtx) 0x0
(gdb) p debug_tree(exp)
<call_expr 0x7ffff648a2d0
type <void_type 0x7ffff67bbf18 void VOID
align:8 warn_if_not_align:0 symtab:0 alias-set -1 structural-equality
pointer_to_this <pointer_type 0x7ffff67c20a8>>
side-effects nothrow
fn <addr_expr 0x7ffff64adc40
type <pointer_type 0x7ffff65ea150 type <function_type 0x7ffff65dd348>
unsigned DI
size <integer_cst 0x7ffff67a7be8 constant 64>
unit-size <integer_cst 0x7ffff67a7c00 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1
structural-equality context <translation_unit_decl 0x7ffff67b1168 app.c>>
constant
arg:0 <function_decl 0x7ffff6699300 gimp_lebl_dialog type
<function_type 0x7ffff65e11f8>
addressable used nothrow public external function-specific-target
function-specific-opt QI lebl-dialog.c:774:1 align:8 warn_if_not_align:0
context <translation_unit_decl 0x7ffff67b1348 lebl-dialog.c>
(mem:QI (symbol_ref:DI ("gimp_lebl_dialog") [flags 0x43]
<function_decl 0x7ffff6699300 gimp_lebl_dialog>) [0 S1 A8])>>
gimpwindow.c:200:9 start: gimpwindow.c:200:9 finish: gimpwindow.c:200:9>
Optimized dump looks as follows:
;; Function gimp_window_key_press_event (gimp_window_key_press_event,
funcdef_no=194, decl_uid=6164, cgraph_uid=264, symbol_order=54507)
gimp_window_key_press_event (struct GtkWidget * widget, struct GdkEventKey *
event)
{
struct GtkWidgetClass * widget_class;
static guint32 val = 0;
gboolean __r;
GType __t;
gboolean __r;
GType __t;
gboolean __r;
GType __t;
static const char __func__[28] = <<< error >>>;
gboolean handled;
gboolean enable_mnemonics;
GdkModifierType accel_mods;
struct GtkWidget * focus;
struct GtkWindow * window;
struct GimpWindow * gimp_window;
long unsigned int _1;
long unsigned int _2;
struct GTypeClass * _3;
long unsigned int _4;
struct GtkWidget * _9;
<unnamed type> _10;
unsigned int _11;
unsigned int _12;
unsigned int _13;
unsigned int _14;
unsigned int _15;
unsigned int _16;
unsigned int _17;
struct GimpWindowPrivate * _19;
struct GtkWidget * _20;
unsigned int _23;
unsigned int _24;
<unnamed type> _25;
unsigned int _26;
<unnamed type> _27;
unsigned int _28;
unsigned int _29;
unsigned int _30;
<unnamed type> _31;
unsigned int _32;
long unsigned int _33;
gboolean (*<T879>) (struct GtkWidget *, struct GdkEventKey *) _34;
<unnamed type> _35;
unsigned int _36;
int _41;
<unnamed type> _187;
unsigned int prephitmp_189;
unsigned int pretmp_191;
struct GtkSettings * _195;
int _197;
unsigned int pretmp_199;
struct GtkSettings * _205;
int _207;
<bb 2> [local count: 1073741825]:
_1 = gimp_window_get_type ();
gimp_window_54 = g_type_check_instance_cast (widget_52(D), _1);
_2 = gtk_window_get_type ();
window_56 = g_type_check_instance_cast (widget_52(D), _2);
focus_58 = gtk_window_get_focus (window_56);
if (focus_58 != 0B)
goto <bb 3>; [70.00%]
else
goto <bb 11>; [30.00%]
<bb 3> [local count: 751619277]:
__t_59 = gtk_editable_get_type ();
_3 = MEM[(struct GTypeInstance *)focus_58].g_class;
if (_3 != 0B)
goto <bb 4>; [70.00%]
else
goto <bb 43>; [30.00%]
<bb 4> [local count: 526133494]:
_4 = _3->g_type;
if (_4 == __t_59)
goto <bb 5>; [34.00%]
else
goto <bb 41>; [66.00%]
<bb 5> [local count: 743388553]:
handled_71 = gtk_window_propagate_key_event (window_56, event_69(D));
if (handled_71 != 0)
goto <bb 9>; [50.00%]
else
goto <bb 8>; [50.00%]
<bb 6> [local count: 83138624]:
# __t_219 = PHI <__t_212(39), __t_210(37)>
__r_66 = g_type_check_instance_is_a (focus_58, __t_219);
if (__r_66 != 0)
goto <bb 5>; [67.00%]
else
goto <bb 7>; [33.00%]
<bb 7> [local count: 27435746]:
_9 = gtk_widget_get_ancestor (focus_58, __t_219);
if (_9 != 0B)
goto <bb 5>; [70.00%]
else
goto <bb 11>; [30.00%]
<bb 8> [local count: 371694277]:
pretmp_199 = event_69(D)->keyval;
goto <bb 13>; [100.00%]
<bb 9> [local count: 371694276]:
_10 = gimp_log_flags;
_11 = _10 & 16384;
if (_11 != 0)
goto <bb 10>; [33.00%]
else
goto <bb 36>; [67.00%]
<bb 10> [local count: 122659111]:
gimp_log (16384, &__func__, 193, "handled by
gtk_window_propagate_key_event(text_widget)");
goto <bb 36>; [100.00%]
<bb 11> [local count: 330353271]:
_12 = val;
_13 = _12 << 8;
_14 = event_69(D)->keyval;
_15 = _14 & 255;
_16 = _13 | _15;
val = _16;
_17 = _16 % 141650939;
if (_17 == 62515060)
goto <bb 12>; [20.24%]
else
goto <bb 13>; [79.76%]
<bb 12> [local count: 66863502]:
gimp_lebl_dialog ();
pretmp_191 = event_69(D)->keyval;
<bb 13> [local count: 702047548]:
# prephitmp_189 = PHI <pretmp_199(8), pretmp_191(12), _14(11)>
if (prephitmp_189 == 65307)
goto <bb 14>; [34.00%]
else
goto <bb 35>; [66.00%]
<bb 14> [local count: 238696166]:
_19 = gimp_window_54->private;
_20 = _19->primary_focus_widget;
if (_20 != 0B)
goto <bb 15>; [54.59%]
else
goto <bb 35>; [45.41%]
<bb 15> [local count: 130304237]:
if (_20 != focus_58)
goto <bb 16>; [70.00%]
else
goto <bb 17>; [30.00%]
<bb 16> [local count: 91212966]:
gtk_widget_grab_focus (_20);
goto <bb 33>; [100.00%]
<bb 17> [local count: 39091271]:
gtk_widget_error_bell (widget_52(D));
goto <bb 33>; [100.00%]
<bb 18> [local count: 188675290]:
_187 = gtk_window_get_mnemonic_modifier (window_56);
accel_mods_186 = _187 | accel_mods_203;
goto <bb 20>; [100.00%]
<bb 19> [local count: 122659114]:
gtk_window_get_mnemonic_modifier (window_56);
goto <bb 33>; [100.00%]
<bb 20> [local count: 471718793]:
# accel_mods_218 = PHI <accel_mods_186(18), accel_mods_203(35)>
_23 = event_69(D)->state;
_24 = _23 & accel_mods_218;
if (_24 != 0)
goto <bb 21>; [33.00%]
else
goto <bb 24>; [67.00%]
<bb 21> [local count: 155667202]:
handled_86 = gtk_window_activate_key (window_56, event_69(D));
if (handled_86 != 0)
goto <bb 22>; [50.00%]
else
goto <bb 24>; [50.00%]
<bb 22> [local count: 77833601]:
_25 = gimp_log_flags;
_26 = _25 & 16384;
if (_26 != 0)
goto <bb 23>; [33.00%]
else
goto <bb 33>; [67.00%]
<bb 23> [local count: 25685088]:
gimp_log (16384, &__func__, 233, "handled by
gtk_window_activate_key(modified)");
goto <bb 33>; [100.00%]
<bb 24> [local count: 393885193]:
handled_89 = gtk_window_propagate_key_event (window_56, event_69(D));
if (handled_89 != 0)
goto <bb 25>; [50.00%]
else
goto <bb 34>; [50.00%]
<bb 25> [local count: 155667202]:
_27 = gimp_log_flags;
_28 = _27 & 16384;
if (_28 != 0)
goto <bb 26>; [33.00%]
else
goto <bb 33>; [67.00%]
<bb 26> [local count: 51370177]:
gimp_log (16384, &__func__, 243, "handled by
gtk_window_propagate_key_event(other_widget)");
goto <bb 33>; [100.00%]
<bb 27> [local count: 155667202]:
handled_92 = gtk_window_activate_key (window_56, event_69(D));
if (handled_92 != 0)
goto <bb 28>; [50.00%]
else
goto <bb 30>; [50.00%]
<bb 28> [local count: 77833601]:
_31 = gimp_log_flags;
_32 = _31 & 16384;
if (_32 != 0)
goto <bb 29>; [33.00%]
else
goto <bb 33>; [67.00%]
<bb 29> [local count: 25685088]:
gimp_log (16384, &__func__, 253, "handled by
gtk_window_activate_key(unmodified)");
goto <bb 33>; [100.00%]
<bb 30> [local count: 393885193]:
_33 = g_type_parent (_2);
widget_class_96 = g_type_class_peek_static (_33);
_34 = widget_class_96->key_press_event;
handled_98 = _34 (widget_52(D), event_69(D));
if (handled_98 != 0)
goto <bb 31>; [50.00%]
else
goto <bb 33>; [50.00%]
<bb 31> [local count: 155667202]:
_35 = gimp_log_flags;
_36 = _35 & 16384;
if (_36 != 0)
goto <bb 32>; [33.00%]
else
goto <bb 33>; [67.00%]
<bb 32> [local count: 51370177]:
gimp_log (16384, &__func__, 267, "handled by
widget_class->key_press_event()");
<bb 33> [local count: 1073741825]:
# _41 = PHI <1(17), 1(16), handled_92(29), handled_86(22), handled_98(32),
handled_92(28), handled_86(23), handled_89(26), handled_89(25), handled_71(19),
handled_98(30), handled_98(31), handled_71(36)>
enable_mnemonics ={v} {CLOBBER};
return _41;
<bb 34> [local count: 471718793]:
_29 = event_69(D)->state;
_30 = _29 & accel_mods_218;
if (_30 == 0)
goto <bb 27>; [33.00%]
else
goto <bb 30>; [67.00%]
<bb 35> [local count: 571743307]:
accel_mods_203 = gtk_widget_get_modifier_mask (widget_52(D), 0);
_205 = gtk_widget_get_settings (widget_52(D));
g_object_get (_205, "gtk-enable-mnemonics", &enable_mnemonics, 0B);
_207 = enable_mnemonics;
if (_207 != 0)
goto <bb 18>; [33.00%]
else
goto <bb 20>; [67.00%]
<bb 36> [local count: 371694277]:
gtk_widget_get_modifier_mask (widget_52(D), 0);
_195 = gtk_widget_get_settings (widget_52(D));
g_object_get (_195, "gtk-enable-mnemonics", &enable_mnemonics, 0B);
_197 = enable_mnemonics;
if (_197 != 0)
goto <bb 19>; [33.00%]
else
goto <bb 33>; [67.00%]
<bb 37> [local count: 76374065]:
__t_210 = gimp_canvas_get_type ();
if (_4 == __t_210)
goto <bb 5>; [34.00%]
else
goto <bb 6>; [66.00%]
<bb 38> [local count: 132301528]:
__r_211 = g_type_check_instance_is_a (focus_58, __t_214);
if (__r_211 != 0)
goto <bb 5>; [42.27%]
else
goto <bb 37>; [57.73%]
<bb 39> [local count: 32731741]:
__t_212 = gimp_canvas_get_type ();
goto <bb 6>; [100.00%]
<bb 40> [local count: 200456862]:
__t_214 = gtk_text_view_get_type ();
if (_4 == __t_214)
goto <bb 5>; [34.00%]
else
goto <bb 38>; [66.00%]
<bb 41> [local count: 347248104]:
__r_215 = g_type_check_instance_is_a (focus_58, __t_59);
if (__r_215 != 0)
goto <bb 5>; [42.27%]
else
goto <bb 40>; [57.73%]
<bb 42> [local count: 85910083]:
__t_216 = gtk_text_view_get_type ();
__r_213 = g_type_check_instance_is_a (focus_58, __t_216);
if (__r_213 != 0)
goto <bb 5>; [61.90%]
else
goto <bb 39>; [38.10%]
<bb 43> [local count: 225485781]:
__r_217 = g_type_check_instance_is_a (focus_58, __t_59);
if (__r_217 != 0)
goto <bb 5>; [61.90%]
else
goto <bb 42>; [38.10%]
}
Is it related to fact that the function is void and does not return?
>From gcc-bugs-return-604914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:19:27 2018
Return-Path: <gcc-bugs-return-604914-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16116 invoked by alias); 17 May 2018 10: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 5716 invoked by uid 48); 17 May 2018 10:19:22 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] [7/8/9 Regression] make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 10:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-85812-4-QSh28oNNvB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01809.txt.bz2
Content-length: 1755
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Known to work| |6.4.0
Target Milestone|--- |7.4
Summary|make_exception_ptr can leak |[7/8/9 Regression]
|the allocated exception if |make_exception_ptr can leak
|construction throws |the allocated exception if
| |construction throws
Known to fail| |7.3.0, 8.1.0, 9.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Testcase:
#include <exception>
struct E {
E() = default;
E(const E&) { throw 1; }
};
int main()
{
std::make_exception_ptr(E{});
}
=================================================================
==23465==ERROR: LeakSanitizer: detected memory leaks
Direct leak of 129 byte(s) in 1 object(s) allocated from:
#0 0x7f0ae56eb2d0 in __interceptor_malloc
/home/jwakely/src/gcc/gcc-7/libsanitizer/asan/asan_malloc_linux.cc:62
#1 0x7f0ae531f8cf in __cxa_allocate_exception
/home/jwakely/src/gcc/gcc-7/libstdc++-v3/libsupc++/eh_alloc.cc:272
#2 0x400d5f in main /tmp/ex.cc:10
#3 0x7f0ae499af29 in __libc_start_main (/lib64/libc.so.6+0x20f29)
SUMMARY: AddressSanitizer: 129 byte(s) leaked in 1 allocation(s).
This started with 7.1 due to r239664 for Bug 68297
>From gcc-bugs-return-604915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:50:37 2018
Return-Path: <gcc-bugs-return-604915-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80722 invoked by alias); 17 May 2018 10: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 80676 invoked by uid 48); 17 May 2018 10:50:33 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85817] [9 Regression] ICE in expand_call at gcc/calls.c:4291
Date: Thu, 17 May 2018 10: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: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-85817-4-RAFeel2aHK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01810.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
--- Comment #1 from prathamesh3492 at gcc dot gnu.org ---
Created attachment 44142
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44142&action=edit
Untested fix
Oops, sorry about that.
I put the condition
if (integer_zerop (retval))
continue;
at the wrong place -;)
Can also be reproduced with:
_Bool f()
{
return 0;
}
In that the pure-const dump shows the function marked as malloc -:(
Could you check if the attached patch fixes the GIMP issue ?
Thanks,
Prathamesh
>From gcc-bugs-return-604916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 10:58:44 2018
Return-Path: <gcc-bugs-return-604916-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112942 invoked by alias); 17 May 2018 10: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 112844 invoked by uid 48); 17 May 2018 10:58:40 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/77810] provide format_inform_at_substring to go with format_warning_at_substring
Date: Thu, 17 May 2018 10:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: preprocessor
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: 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: keywords bug_status cf_reconfirmed_on see_also everconfirmed
Message-ID: <bug-77810-4-Datq644Wni@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-77810-4@http.gcc.gnu.org/bugzilla/>
References: <bug-77810-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01811.txt.bz2
Content-length: 893
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77810
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=77690,
| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=77696
Ever confirmed|0 |1
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
Confirmed since a bug that this blocks is confirmed.
>From gcc-bugs-return-604917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 11:10:27 2018
Return-Path: <gcc-bugs-return-604917-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119840 invoked by alias); 17 May 2018 11:10: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 119774 invoked by uid 48); 17 May 2018 11:10:23 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85817] [9 Regression] ICE in expand_call at gcc/calls.c:4291
Date: Thu, 17 May 2018 11:10:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85817-4-XEe8ZrREDz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01812.txt.bz2
Content-length: 967
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to prathamesh3492 from comment #1)
> Created attachment 44142 [details]
> Untested fix
>
> Oops, sorry about that.
It easily happens.
> I put the condition
> if (integer_zerop (retval))
> continue;
> at the wrong place -;)
>
> Can also be reproduced with:
> _Bool f()
> {
> return 0;
> }
> In that the pure-const dump shows the function marked as malloc -:(
> Could you check if the attached patch fixes the GIMP issue ?
Yes, it helps ;)
>
> Thanks,
> Prathamesh
>From gcc-bugs-return-604918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 11:26:19 2018
Return-Path: <gcc-bugs-return-604918-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93767 invoked by alias); 17 May 2018 11:26: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 93728 invoked by uid 55); 17 May 2018 11:26:15 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85793] [8/9 Regression][AARCH64] ICE in verify_gimple during GIMPLE pass vect.
Date: Thu, 17 May 2018 11:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85793-4-IpRDQ1DoAj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85793-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85793-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01813.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85793
--- Comment #3 from bin cheng <amker at gcc dot gnu.org> ---
Author: amker
Date: Thu May 17 11:25:43 2018
New Revision: 260317
URL: https://gcc.gnu.org/viewcvs?rev=260317&root=gcc&view=rev
Log:
PR tree-optimization/85793
* tree-vect-stmts.c (vectorizable_load): Handle 1 element-wise load
for VMAT_ELEMENTWISE.
gcc/testsuite
* gcc.dg/vect/pr85793.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/vect/pr85793.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-vect-stmts.c
>From gcc-bugs-return-604919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 11:39:10 2018
Return-Path: <gcc-bugs-return-604919-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58563 invoked by alias); 17 May 2018 11:39:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 58392 invoked by uid 48); 17 May 2018 11:39:04 -0000
From: "jhb.chat at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT
Date: Thu, 17 May 2018 11:39: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jhb.chat 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: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85760-4-ihGnNsRFAl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01814.txt.bz2
Content-length: 2041
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #8 from Jere <jhb.chat at gmail dot com> ---
OH! I thought you meant here. I wasn't sure this was the same bug internally.
They have different results in the two different versions of GNAT. The
AdaCore GNAT Community put out a crash report while the FSF GNAT only returned
quietly with no compilation results. If they acted exactly the same, I would
have only reported to AdaCore as I am guessing AdaCore's fixes would eventually
end up here (this is only a guess on my part though). However, since it acted
differently in FSF GNAT I didn't know if AdaCore fixed it in GNAT Community if
it would fix the same issue or if this happend to be a different bug triggered
by the same code. I've seen multiple times in the past where a bug was fixed
in a earlier version of GNAT GPL/Community but not in a later version of FSF
GNAT, which probably means they weren't actually the same bug internally. Also
there is no guarantee they'll even look at my report as it was for the
community edition (this is not a knock against them, they have their own
priorities that they must manage first). I was just trying to be nice to help
them find bugs as well. I wasn't meaning to cause trouble, just help
contribute to making GNAT the best it can be in all versions.
Keep in mind it is difficult on my end to know what is going on internally. I
don't always receive responses from AdaCore when I submit bugs (again, I'm not
expecting them to when they have bigger priorities). When they have responded,
they have not indicated they will push those fixes to FSF GNAT (I am guessing
that they do eventually, but it is only a guess on my part) and it isn't fair
for me to probe them further. I have no clue on my end if I am duplicating the
triage work or not, especially in the case where the bug acts different in
different versions.
So my apologies on the trouble. I was not intending to cause any. I hope you
will forgive me.
>From gcc-bugs-return-604920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 11:43:58 2018
Return-Path: <gcc-bugs-return-604920-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71251 invoked by alias); 17 May 2018 11:43:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 70655 invoked by uid 48); 17 May 2018 11:43:52 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85804] [8/9 Regression][AArch64] Mis-compilation of loop with strided array access and xor reduction
Date: Thu, 17 May 2018 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: 8.1.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85804-4-qvmB8NNVRw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85804-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85804-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01815.txt.bz2
Content-length: 564
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85804
bin cheng <amker at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
CC| |amker at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from bin cheng <amker at gcc dot gnu.org> ---
Confirmed. I will have a look
>From gcc-bugs-return-604921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 11:53:51 2018
Return-Path: <gcc-bugs-return-604921-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48338 invoked by alias); 17 May 2018 11:53:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 48245 invoked by uid 48); 17 May 2018 11:53:45 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 11:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-QWoDF870Y8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01816.txt.bz2
Content-length: 671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #27 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
[Replying to myself now]
> A front end pass (what else did you expect? :-)
>
> If an impure function is found (recursively) in the operands of an .AND.
> expression, issue a
>
> gfc_warning(OPT_Wsurprising, "Impure function %qs at %L may not be
> evaluated", ...)
>
> So,
>
> if (flag .and. f(x) > 0.)
>
> would also be warned about.
I think I will start working on that warning; this should lead to
users being made aware of a potential problem in their code.
I am, of course, open to suggestions about the text of the warning.
>From gcc-bugs-return-604922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 12:02:42 2018
Return-Path: <gcc-bugs-return-604922-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109575 invoked by alias); 17 May 2018 12:02: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 109533 invoked by uid 48); 17 May 2018 12:02:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] New: [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Thu, 17 May 2018 12:02: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.1.1
X-Bugzilla-Keywords: link-failure
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 keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01817.txt.bz2
Content-length: 1230
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Bug ID: 85818
Summary: [8/9 Regression] undefined reference to
`std::experimental::filesystem::v1::__cxx11::path::pre
ferred_separator'
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Keywords: link-failure
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
This fails to link when compiled as C++11 or C++14 with GCC 8 or 9:
#include <experimental/filesystem>
int main()
{
auto& sep = std::experimental::filesystem::path::preferred_separator;
}
/tmp/ccxrMmnw.o: In function `main':
/tmp/ps.cc:5: undefined reference to
`std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
collect2: error: ld returned 1 exit status
The variable is defined in src/filesystem/path.cc:
constexpr path::value_type path::preferred_separator;
But that file is compiled with -std=gnu++17 and so the variable is implicitly
inline, and because it isn't used in that file its definition isn't emitted in
path.o
>From gcc-bugs-return-604923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 12:03:32 2018
Return-Path: <gcc-bugs-return-604923-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119086 invoked by alias); 17 May 2018 12:03: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 119022 invoked by uid 48); 17 May 2018 12:03:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Thu, 17 May 2018 12:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
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-85818-4-GqZDCChRj4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01818.txt.bz2
Content-length: 664
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-17
Known to work| |6.4.0, 7.3.0
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Target Milestone|--- |8.2
Ever confirmed|0 |1
Known to fail| |8.1.0, 9.0
>From gcc-bugs-return-604924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 12:18:42 2018
Return-Path: <gcc-bugs-return-604924-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39158 invoked by alias); 17 May 2018 12: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 39097 invoked by uid 55); 17 May 2018 12:18:37 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85655] [8/9 Regression] ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault
Date: Thu, 17 May 2018 12:18: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.1.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85655-4-QCOYGY0pWw@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01819.txt.bz2
Content-length: 650
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
--- Comment #9 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Thu May 17 12:18:06 2018
New Revision: 260319
URL: https://gcc.gnu.org/viewcvs?rev=260319&root=gcc&view=rev
Log:
Check is_single_const in intersect_with_plats
2018-05-17 Martin Jambor <mjambor@suse.cz>
Backport from mainline
2018-05-11 Martin Jambor <mjambor@suse.cz>
PR ipa/85655
* ipa-cp.c (intersect_with_plats): Check that the lattice contains
single const.
Modified:
branches/gcc-6-branch/gcc/ChangeLog
branches/gcc-6-branch/gcc/ipa-cp.c
>From gcc-bugs-return-604925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 12:24:46 2018
Return-Path: <gcc-bugs-return-604925-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47161 invoked by alias); 17 May 2018 12:24:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 46716 invoked by uid 55); 17 May 2018 12:24:20 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85655] [8/9 Regression] ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault
Date: Thu, 17 May 2018 12: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: 8.1.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85655-4-LxTPfqT82r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01820.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
--- Comment #10 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Author: jamborm
Date: Thu May 17 12:23:34 2018
New Revision: 260320
URL: https://gcc.gnu.org/viewcvs?rev=260320&root=gcc&view=rev
Log:
Check is_single_const in intersect_with_plats
2018-05-17 Martin Jambor <mjambor@suse.cz>
Backport from mainline
2018-05-11 Martin Jambor <mjambor@suse.cz>
PR ipa/85655
* ipa-cp.c (intersect_with_plats): Check that the lattice contains
single const.
Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/ipa-cp.c
>From gcc-bugs-return-604926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 12:25:09 2018
Return-Path: <gcc-bugs-return-604926-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48178 invoked by alias); 17 May 2018 12:25: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 48110 invoked by uid 48); 17 May 2018 12:25:04 -0000
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85655] [8/9 Regression] ICE with -flto and -O2 during IPA pass: cp lto1: internal compiler error: Segmentation fault
Date: Thu, 17 May 2018 12:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: ice-on-valid-code, lto
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jamborm at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85655-4-fXd1eCy4Gj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85655-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01821.txt.bz2
Content-length: 428
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85655
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Martin Jambor <jamborm at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-604927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 13:08:06 2018
Return-Path: <gcc-bugs-return-604927-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116135 invoked by alias); 17 May 2018 13:08:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 116024 invoked by uid 48); 17 May 2018 13:07:59 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 13: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: 8.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority component
Message-ID: <bug-85599-4-Y9zBUPVpwg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01822.txt.bz2
Content-length: 1484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|wrong-code |
Priority|P3 |P5
Component|middle-end |fortran
--- Comment #28 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > This PR is now about a missed optimization in the middle-end.
>
> Well, that was absolutely not my intention when I opened this PR,
> and it still isn't. Quite the opposite: I don't think gfortran should apply
> more optimizations, but less. I'm changing the title and keyword again
> to reflect that.
Then I strongly opposed any change to the gfortran default behavior. Why should
we take a chance to break valid codes to allow invalid or at best questionable
ones? See Steve Lionel comment at
https://groups.google.com/forum/#!topic/comp.lang.fortran/fXP1c0u57So:
"All in all, functions that have side-effects are to be avoided."
> If an impure function is found (recursively) in the operands of an .AND.
> expression, issue a
>
> gfc_warning(OPT_Wsurprising, "Impure function %qs at %L may not be
> evaluated", ...)
>
> So,
>
> if (flag .and. f(x) > 0.)
>
> would also be warned about.
Why recursively? If this PR is going this way, pr57160 should be closed as a
duplicate.
>From gcc-bugs-return-604928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 13:09:43 2018
Return-Path: <gcc-bugs-return-604928-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119001 invoked by alias); 17 May 2018 13:09: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 118937 invoked by uid 48); 17 May 2018 13:09:38 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/85760] Using generic function to initialize a type created by a generic package crashes GNAT
Date: Thu, 17 May 2018 13:09: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85760-4-hMURnHVvTM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85760-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01823.txt.bz2
Content-length: 2225
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85760
--- Comment #9 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> OH! I thought you meant here. I wasn't sure this was the same bug
> internally. They have different results in the two different versions of
> GNAT. The AdaCore GNAT Community put out a crash report while the FSF GNAT
> only returned quietly with no compilation results.
Here's what I get:
eric@polaris:~/build/gcc/native> ~/install/gcc-7-branch/bin/gcc -c main.adb
+===========================GNAT BUG DETECTED==============================+
| 7.3.1 20180407 [gcc-7-branch revision 259208] (x86_64-suse-linux) |
| Storage_Error stack overflow or erroneous memory access |
| Error detected at main.adb:11:4 |
| Please submit a bug report; see https://gcc.gnu.org/bugs/ . |
eric@polaris:~/build/gcc/native> ~/install/gcc-8-branch/bin/gcc -c main.adb
eric@polaris:~/build/gcc/native>
> I've seen multiple times in the past where a bug was fixed in a earlier
> version of GNAT GPL/Community but not in a later version of FSF GNAT, which
> probably means they weren't actually the same bug internally.
The chance that the same code triggers 2 different bugs in the compiler is
virtually zero; what you experienced is only a discrepancy in release cycles.
> Also there is no guarantee they'll even look at my report as it was for the
> community edition (this is not a knock against them, they have their own
> priorities that they must manage first). I was just trying to be nice to
> help them find bugs as well. I wasn't meaning to cause trouble, just help
> contribute to making GNAT the best it can be in all versions.
There is a single GNAT codebase so there is no need to duplicate bug reports
for all the different variants, they will eventually be resynced at some point.
> So my apologies on the trouble. I was not intending to cause any. I hope
> you will forgive me.
Not sure if there is anything to forgive given your explanation.
>From gcc-bugs-return-604930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 13:46:37 2018
Return-Path: <gcc-bugs-return-604930-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106176 invoked by alias); 17 May 2018 13:46: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 106037 invoked by uid 48); 17 May 2018 13:46:32 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85620] Missing ENDBR after swapcontext
Date: Thu, 17 May 2018 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85620-4-hKFDFvGgWQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01825.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
It has been fixed in glibc.
>From gcc-bugs-return-604929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 13:46:37 2018
Return-Path: <gcc-bugs-return-604929-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106135 invoked by alias); 17 May 2018 13:46: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 106063 invoked by uid 48); 17 May 2018 13:46:33 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/81652] [meta-bug] -fcf-protection=full bugs
Date: Thu, 17 May 2018 13:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.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_status resolution
Message-ID: <bug-81652-4-HCOaf9BdTH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81652-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81652-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01824.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81652
Bug 81652 depends on bug 85620, which changed state.
Bug 85620 Summary: Missing ENDBR after swapcontext
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-604931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 13:47:09 2018
Return-Path: <gcc-bugs-return-604931-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107729 invoked by alias); 17 May 2018 13:47: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 107542 invoked by uid 48); 17 May 2018 13:47:00 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85620] Missing ENDBR after swapcontext
Date: Thu, 17 May 2018 13:47: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: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WONTFIX
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-85620-4-4nuqgqF5JS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85620-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85620-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01826.txt.bz2
Content-length: 290
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85620
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |WONTFIX
>From gcc-bugs-return-604932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 13:48:51 2018
Return-Path: <gcc-bugs-return-604932-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117470 invoked by alias); 17 May 2018 13:48: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 114925 invoked by uid 48); 17 May 2018 13:48:21 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 13: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-cb2CcHqI7w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01827.txt.bz2
Content-length: 989
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #29 from janus at gcc dot gnu.org ---
(In reply to Thomas Koenig from comment #27)
> > If an impure function is found (recursively) in the operands of an .AND.
> > expression, issue a
> >
> > gfc_warning(OPT_Wsurprising, "Impure function %qs at %L may not be
> > evaluated", ...)
> >
> > So,
> >
> > if (flag .and. f(x) > 0.)
> >
> > would also be warned about.
>
> I think I will start working on that warning; this should lead to
> users being made aware of a potential problem in their code.
That's not my favorite way of fixing it, but it's certainly an improvement upon
the current state of things, so I'm fine with it.
The warning text basically sounds good to me, although you could possibly
replace 'may' by 'might'. I'm not a native speaker, but I think that is clearer
and sounds less like "... is not allowed to be evaluated".
In addition to .and., a treatment of .or. is needed as well.
>From gcc-bugs-return-604933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 14:01:16 2018
Return-Path: <gcc-bugs-return-604933-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27085 invoked by alias); 17 May 2018 14:01:16 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 26701 invoked by uid 48); 17 May 2018 14:01:10 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85819] New: conversion from __v[48]su to __v[48]sf should use FMA
Date: Thu, 17 May 2018 14: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: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01828.txt.bz2
Content-length: 1041
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85819
Bug ID: 85819
Summary: conversion from __v[48]su to __v[48]sf should use FMA
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: ---
Testcase (cf. https://godbolt.org/g/UoU3zj):
using T = float;
using To [[gnu::vector_size(32)]] = T;
using From [[gnu::vector_size(32)]] = unsigned;
#define A2(I) (T)a[I], (T)a[1+I]
#define A4(I) A2(I), A2(2+I)
#define A8(I) A4(I), A4(4+I)
To f(From a) {
return To{A8(0)};
}
This compiles to:
vpand .LC0(%rip), %ymm0, %ymm1
vpsrld $16, %ymm0, %ymm0
vcvtdq2ps %ymm0, %ymm0
vcvtdq2ps %ymm1, %ymm1
vmulps .LC1(%rip), %ymm0, %ymm0
vaddps %ymm0, %ymm1, %ymm0
ret
The last vmulps and vaddps can be contracted to vfmadd132ps .LC1(%rip), %ymm1,
%ymm0.
The same is true for vector_size(16).
>From gcc-bugs-return-604934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 14:24:06 2018
Return-Path: <gcc-bugs-return-604934-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54350 invoked by alias); 17 May 2018 14:24:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53600 invoked by uid 48); 17 May 2018 14:23:54 -0000
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 14:24: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: 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:
Message-ID: <bug-85813-4-hl0NULR96x@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01829.txt.bz2
Content-length: 1166
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #3 from Mathias Stearn <redbeard0531 at gmail dot com> ---
My assumption was that if E(...) throws and it can't be caught, it should be
treated as any other case when an -fno-exceptions TU calls a throwing function.
In this case that would mean calling terminate() due to the noexcept, which
seems better than returning a null exception_ptr.
However, while testing the behavior of mixing -fno-exceptions TUs with normal
ones, I realized there may be a bigger problem due to ODR violations. In
particular, if you link these TUs without optimizations, one of the asserts
will trip depending on the link order:
// g++ -fno-exceptions -c
#include <exception>
#include <cassert>
void no_exceptions() {
assert(!std::make_exception_ptr(1));
}
// g++ -fexceptions
#include <exception>
#include <cassert>
void no_exceptions();
int main() {
assert(std::make_exception_ptr(1));
no_exceptions();
}
Is that just accepted, implying the the whole program must be compiled with
either -fexceptions or -fno-exeptions, rather than allowing mix-and-match? If
so, I guess this whole point is moot.
>From gcc-bugs-return-604935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:00:51 2018
Return-Path: <gcc-bugs-return-604935-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56409 invoked by alias); 17 May 2018 15: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 47829 invoked by uid 48); 17 May 2018 15:00:20 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85783] alloc-size-larger-than fires incorrectly with new[] and can't be disabled
Date: Thu, 17 May 2018 15:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-85783-4-tGYjtKNp1r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85783-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85783-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01830.txt.bz2
Content-length: 589
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85783
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |WONTFIX
--- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> ---
That's right, bug 82063 tracks the inability to turn off the warning. This
report is about the false positive (only). Hopefully, that will go away once
we fix 85795.
>From gcc-bugs-return-604936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:04:06 2018
Return-Path: <gcc-bugs-return-604936-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59977 invoked by alias); 17 May 2018 15:04:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59903 invoked by uid 55); 17 May 2018 15:04:02 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] [7/8/9 Regression] make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 15:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85812-4-rAnp9ybFt2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01831.txt.bz2
Content-length: 844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 17 15:03:29 2018
New Revision: 260323
URL: https://gcc.gnu.org/viewcvs?rev=260323&root=gcc&view=rev
Log:
PR libstdc++/85812 fix memory leak in std::make_exception_ptr
PR libstdc++/85812
* libsupc++/cxxabi_init_exception.h (__cxa_free_exception): Declare.
* libsupc++/exception_ptr.h (make_exception_ptr) [__cpp_exceptions]:
Refactor to separate non-throwing and throwing implementations.
[__cpp_rtti && !_GLIBCXX_HAVE_CDTOR_CALLABI]: Deallocate the memory
if constructing the object throws.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/libsupc++/cxxabi_init_exception.h
trunk/libstdc++-v3/libsupc++/exception_ptr.h
>From gcc-bugs-return-604937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:05:47 2018
Return-Path: <gcc-bugs-return-604937-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73883 invoked by alias); 17 May 2018 15: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 73771 invoked by uid 55); 17 May 2018 15:05:42 -0000
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 15: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zeccav at gmail 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85814-4-KgX1JZ4Ccz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01832.txt.bz2
Content-length: 364
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
--- Comment #5 from Vittorio Zecca <zeccav at gmail dot com> ---
I confirm I get the ICE on trunk 260152 and on a sanitized version I also get
../../gcc/gcc/tree-ssa-strlen.c:721:11: runtime error: member access
within null pointer of type 'struct strinfo'
Thank you for the very useful reduction, Martin.
>From gcc-bugs-return-604938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:13:34 2018
Return-Path: <gcc-bugs-return-604938-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81729 invoked by alias); 17 May 2018 15:13:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 81572 invoked by uid 48); 17 May 2018 15:13:26 -0000
From: "joshua.r.marshall.1991 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function
Date: Thu, 17 May 2018 15:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.r.marshall.1991 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: attachments.created
Message-ID: <bug-85763-4-lQjIsUSXYf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01833.txt.bz2
Content-length: 372
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763
--- Comment #2 from Josh Marshall <joshua.r.marshall.1991 at gmail dot com> ---
Created attachment 44143
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44143&action=edit
Example file
I got to making an example, but it seems that this is no longer a problem. I'm
going to close this one out as invalid.
>From gcc-bugs-return-604939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:13:50 2018
Return-Path: <gcc-bugs-return-604939-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82503 invoked by alias); 17 May 2018 15:13: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 82466 invoked by uid 48); 17 May 2018 15:13:45 -0000
From: "joshua.r.marshall.1991 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function
Date: Thu, 17 May 2018 15:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joshua.r.marshall.1991 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-85763-4-kLaZeX3RH4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01834.txt.bz2
Content-length: 367
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763
Josh Marshall <joshua.r.marshall.1991 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-604940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:15:40 2018
Return-Path: <gcc-bugs-return-604940-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121965 invoked by alias); 17 May 2018 15:15: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 121865 invoked by uid 48); 17 May 2018 15:15:34 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Thu, 17 May 2018 15: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.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66694-4-YNd65oQt2s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01835.txt.bz2
Content-length: 296
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This PR seems fixed by the patch at
https://gcc.gnu.org/ml/fortran/2018-05/msg00046.html, likely a duplicate of
pr82923.
On darwin the executable hangs due to pr30617.
>From gcc-bugs-return-604941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:18:20 2018
Return-Path: <gcc-bugs-return-604941-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127902 invoked by alias); 17 May 2018 15:18: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 127854 invoked by uid 55); 17 May 2018 15:18:15 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82814] ICE from submodule character function
Date: Thu, 17 May 2018 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.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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-82814-4-L3Wp8nunlr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01836.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Thu May 17 15:17:43 2018
New Revision: 260324
URL: https://gcc.gnu.org/viewcvs?rev=260324&root=gcc&view=rev
Log:
2017-05-17 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82814
* gfortran.dg/submodule_31.f08: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/submodule_31.f08
Modified:
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:18:37 2018
Return-Path: <gcc-bugs-return-604942-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128811 invoked by alias); 17 May 2018 15:18: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 128728 invoked by uid 48); 17 May 2018 15:18:32 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Thu, 17 May 2018 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: 8.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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85599-4-xgaltJLjSJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01837.txt.bz2
Content-length: 521
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Joost.VandeVondele at mat dot ethz
| |.ch
--- Comment #30 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
*** Bug 57160 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:18:37 2018
Return-Path: <gcc-bugs-return-604943-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 128830 invoked by alias); 17 May 2018 15:18: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 128687 invoked by uid 48); 17 May 2018 15:18:31 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/57160] short-circuit IF only with -ffrontend-optimize
Date: Thu, 17 May 2018 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: 4.9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-57160-4-MjoFMsJHry@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-57160-4@http.gcc.gnu.org/bugzilla/>
References: <bug-57160-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01838.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=57160
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #5 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Duplicate of pr85599.
*** This bug has been marked as a duplicate of bug 85599 ***
>From gcc-bugs-return-604944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:32:26 2018
Return-Path: <gcc-bugs-return-604944-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6685 invoked by alias); 17 May 2018 15:32:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6506 invoked by uid 55); 17 May 2018 15:32:14 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82814] ICE from submodule character function
Date: Thu, 17 May 2018 15:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: WAITING
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-82814-4-JBDI66K79H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01839.txt.bz2
Content-length: 516
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Thu May 17 15:31:42 2018
New Revision: 260325
URL: https://gcc.gnu.org/viewcvs?rev=260325&root=gcc&view=rev
Log:
2017-05-17 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82814
* gfortran.dg/submodule_31.f08: New test.
Added:
branches/gcc-6-branch/gcc/testsuite/gfortran.dg/submodule_31.f08
Modified:
branches/gcc-6-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:34:25 2018
Return-Path: <gcc-bugs-return-604945-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16865 invoked by alias); 17 May 2018 15: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 16792 invoked by uid 48); 17 May 2018 15:34:20 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82814] ICE from submodule character function
Date: Thu, 17 May 2018 15: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: 7.2.0
X-Bugzilla-Keywords:
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-82814-4-PwN3o2pWUu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01840.txt.bz2
Content-length: 565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82814
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
The PR was already fixed on 6- and 7-branches in the course of fixing another
bug. All that was needed was the testcase.
Thanks for the report.
Paul
>From gcc-bugs-return-604946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:37:03 2018
Return-Path: <gcc-bugs-return-604946-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37391 invoked by alias); 17 May 2018 15:37:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 37343 invoked by uid 55); 17 May 2018 15:36:57 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Thu, 17 May 2018 15:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85818-4-bbElGgu0q0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01841.txt.bz2
Content-length: 1035
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 17 15:36:25 2018
New Revision: 260326
URL: https://gcc.gnu.org/viewcvs?rev=260326&root=gcc&view=rev
Log:
PR libstdc++/85818 ensure path::preferred_separator is defined
Because path.cc is compiled with -std=gnu++17 the static constexpr
data member is implicitly 'inline' and so no definition gets emitted
unless it gets used in that translation unit. Other translation units
built as C++11 or C++14 still require a namespace-scope definition of
the variable, so mark the definition as used.
PR libstdc++/85818
* src/filesystem/path.cc (path::preferred_separator): Add used
attribute.
* testsuite/experimental/filesystem/path/preferred_separator.cc: New.
Added:
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/preferred_separator.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/filesystem/path.cc
>From gcc-bugs-return-604947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:42:59 2018
Return-Path: <gcc-bugs-return-604947-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52640 invoked by alias); 17 May 2018 15:42: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 52180 invoked by uid 48); 17 May 2018 15:42:54 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file
Date: Thu, 17 May 2018 15:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.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: priority cc component
Message-ID: <bug-82617-4-wtGEIXy9qH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01842.txt.bz2
Content-length: 627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
CC| |pault at gcc dot gnu.org
Component|middle-end |fortran
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
AFAICT this seems fixed by the patch at
https://gcc.gnu.org/ml/fortran/2018-05/msg00046.html, likely a duplicate of
pr82923.
>From gcc-bugs-return-604948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 15:59:07 2018
Return-Path: <gcc-bugs-return-604948-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46315 invoked by alias); 17 May 2018 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 39250 invoked by uid 48); 17 May 2018 15:59:01 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85816] [8/9 Regression] nested spread fails with "Integer overflow in xmallocarray"
Date: Thu, 17 May 2018 15:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-85816-4-t4XrCnaE2R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85816-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85816-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01843.txt.bz2
Content-length: 1198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85816
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Known to work| |7.3.0
Keywords| |wrong-code
Last reconfirmed| |2018-05-17
CC| |pault at gcc dot gnu.org
Ever confirmed|0 |1
Summary|nested spread fails with |[8/9 Regression] nested
|"Integer overflow in |spread fails with "Integer
|xmallocarray" |overflow in xmallocarray"
Target Milestone|--- |8.2
Known to fail| |8.1.0, 9.0
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> Operating system error: Cannot allocate memory
> Integer overflow in xmallocarray
Confirmed at run time.
Caused by revision r257065.
>From gcc-bugs-return-604949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:10:58 2018
Return-Path: <gcc-bugs-return-604949-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78528 invoked by alias); 17 May 2018 16:10: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 78439 invoked by uid 55); 17 May 2018 16:10:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] [7/8 Regression] make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 16: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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85812-4-izQo3zO0YV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01844.txt.bz2
Content-length: 892
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 17 16:10:20 2018
New Revision: 260327
URL: https://gcc.gnu.org/viewcvs?rev=260327&root=gcc&view=rev
Log:
PR libstdc++/85812 fix memory leak in std::make_exception_ptr
PR libstdc++/85812
* libsupc++/cxxabi_init_exception.h (__cxa_free_exception): Declare.
* libsupc++/exception_ptr.h (make_exception_ptr) [__cpp_exceptions]:
Refactor to separate non-throwing and throwing implementations.
[__cpp_rtti && !_GLIBCXX_HAVE_CDTOR_CALLABI]: Deallocate the memory
if constructing the object throws.
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/libsupc++/cxxabi_init_exception.h
branches/gcc-8-branch/libstdc++-v3/libsupc++/exception_ptr.h
>From gcc-bugs-return-604950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:11:04 2018
Return-Path: <gcc-bugs-return-604950-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79226 invoked by alias); 17 May 2018 16: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 78579 invoked by uid 55); 17 May 2018 16:10:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Thu, 17 May 2018 16: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: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85818-4-c09mDdo55D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01845.txt.bz2
Content-length: 1083
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 17 16:10:26 2018
New Revision: 260328
URL: https://gcc.gnu.org/viewcvs?rev=260328&root=gcc&view=rev
Log:
PR libstdc++/85818 ensure path::preferred_separator is defined
Because path.cc is compiled with -std=gnu++17 the static constexpr
data member is implicitly 'inline' and so no definition gets emitted
unless it gets used in that translation unit. Other translation units
built as C++11 or C++14 still require a namespace-scope definition of
the variable, so mark the definition as used.
PR libstdc++/85818
* src/filesystem/path.cc (path::preferred_separator): Add used
attribute.
* testsuite/experimental/filesystem/path/preferred_separator.cc: New.
Added:
branches/gcc-8-branch/libstdc++-v3/testsuite/experimental/filesystem/path/preferred_separator.cc
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/src/filesystem/path.cc
>From gcc-bugs-return-604951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:18:41 2018
Return-Path: <gcc-bugs-return-604951-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 79388 invoked by alias); 17 May 2018 16: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 76676 invoked by uid 48); 17 May 2018 16:18:36 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85820] New: [9 Regression] internal compiler error: Segmentation fault
Date: Thu, 17 May 2018 16:18: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: 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-85820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01846.txt.bz2
Content-length: 5713
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820
Bug ID: 85820
Summary: [9 Regression] internal compiler error: Segmentation
fault
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: prathamesh3492 at gcc dot gnu.org
Target Milestone: ---
On x86-64, r260250 caused:
gfortran -O3 -funroll-loops -ffast-math -fwhole-program -flto=jobserver
-fuse-linker-plugin -DSPEC_CPU_LINUX -DSPEC_CPU_CASE_FLAG
-DSPEC_CPU_LOGICAL_STRICT -frecord-marker=4 wrf_num_bytes_between.o
pack_utils.o module_driver_constants.fppized.o module_domain.fppized.o
module_integrate.fppized.o module_timing.fppized.o module_configure.fppized.o
module_tiles.fppized.o module_machine.fppized.o module_nesting.fppized.o
module_wrf_error.fppized.o module_state_description.fppized.o
module_sm.fppized.o module_io.fppized.o module_dm_stubs.fppized.o
module_quilt_outbuf_ops.fppized.o module_io_quilt.fppized.o module_bc.fppized.o
module_io_wrf.fppized.o module_date_time.fppized.o module_io_domain.fppized.o
module_bc_time_utilities.fppized.o module_model_constants.fppized.o
module_soil_pre.fppized.o module_bl_mrf.fppized.o module_sf_myjsfc.fppized.o
module_bl_myjpbl.fppized.o module_bl_ysu.fppized.o module_cu_bmj.fppized.o
module_mp_kessler.fppized.o module_mp_ncloud5.fppized.o module_ra_sw.fppized.o
module_sf_sfclay.fppized.o module_cu_kf.fppized.o module_cu_kfeta.fppized.o
module_mp_lin.fppized.o module_mp_wsm3.fppized.o module_mp_wsm5.fppized.o
module_mp_wsm6.fppized.o module_surface_driver.fppized.o module_cu_gd.fppized.o
module_sf_sfcdiags.fppized.o module_ra_gsfcsw.fppized.o
module_sf_slab.fppized.o module_sf_noahlsm.fppized.o module_sf_ruclsm.fppized.o
module_mp_ncloud3.fppized.o module_mp_etanew.fppized.o module_ra_rrtm.fppized.o
module_ra_gfdleta.fppized.o module_physics_init.fppized.o
module_physics_addtendc.fppized.o module_solvedebug_em.fppized.o
module_bc_em.fppized.o module_advect_em.fppized.o module_diffusion_em.fppized.o
module_small_step_em.fppized.o module_big_step_utilities_em.fppized.o
module_em.fppized.o module_init_utilities.fppized.o
module_optional_si_input.fppized.o ESMF_Alarm.fppized.o ESMF_Base.fppized.o
ESMF_BaseTime.fppized.o ESMF_Calendar.fppized.o ESMF_Clock.fppized.o
ESMF_Fraction.fppized.o ESMF_Mod.fppized.o ESMF_Time.fppized.o
ESMF_TimeInterval.fppized.o Meat.fppized.o wrf_shutdown.fppized.o
collect_on_comm.o mediation_integrate.fppized.o
mediation_feedback_domain.fppized.o mediation_force_domain.fppized.o
mediation_interp_domain.fppized.o mediation_wrfmain.fppized.o
wrf_auxhist1in.fppized.o wrf_auxhist1out.fppized.o wrf_auxhist2in.fppized.o
wrf_auxhist2out.fppized.o wrf_auxhist3in.fppized.o wrf_auxhist3out.fppized.o
wrf_auxhist4in.fppized.o wrf_auxhist4out.fppized.o wrf_auxhist5in.fppized.o
wrf_auxhist5out.fppized.o wrf_auxinput1in.fppized.o wrf_auxinput1out.fppized.o
wrf_auxinput2in.fppized.o wrf_auxinput2out.fppized.o wrf_auxinput3in.fppized.o
wrf_auxinput3out.fppized.o wrf_auxinput4in.fppized.o wrf_auxinput4out.fppized.o
wrf_auxinput5in.fppized.o wrf_auxinput5out.fppized.o wrf_bdyin.fppized.o
wrf_bdyout.fppized.o wrf_histin.fppized.o wrf_histout.fppized.o
wrf_inputin.fppized.o wrf_inputout.fppized.o wrf_restartin.fppized.o
wrf_restartout.fppized.o couple_or_uncouple_em.fppized.o
interp_domain_em.fppized.o interp_fcn.fppized.o nest_init_utils.fppized.o
set_timekeeping.fppized.o sint.fppized.o solve_interface.fppized.o
start_domain.fppized.o module_pbl_driver.fppized.o
module_radiation_driver.fppized.o module_cumulus_driver.fppized.o
module_microphysics_driver.fppized.o solve_em.fppized.o start_em.fppized.o
internal_header_util.fppized.o io_int.fppized.o init_modules_em.fppized.o
init_modules.fppized.o wrf_io.o field_routines.o wrf.fppized.o netcdf/attr.o
netcdf/dim.o netcdf/error.o netcdf/fort-attio.o netcdf/fort-control.o
netcdf/fort-dim.o netcdf/fort-genatt.o netcdf/fort-geninq.o
netcdf/fort-genvar.o netcdf/fort-lib.o netcdf/fort-misc.o
netcdf/fort-v2compat.o netcdf/fort-var1io.o netcdf/fort-varaio.o
netcdf/fort-vario.o netcdf/fort-varmio.o netcdf/fort-varsio.o netcdf/libvers.o
netcdf/nc.o netcdf/ncx.o netcdf/posixio.o netcdf/putget.o netcdf/string.o
netcdf/v1hpg.o netcdf/v2i.o netcdf/var.o netcdf/typeSizes.o netcdf/netcdf.o
-o wrf
...
during RTL pass: expand
internal_header_util.fppized.f90: In function
'int_get_ti_header_char.constprop':
internal_header_util.fppized.f90:372:1: internal compiler error: Segmentation
fault
DataHandle, dummyData, DummyCount, code )
^
0xbb1a4f crash_signal
../../src-trunk/gcc/toplev.c:325
0x7a679b expand_call(tree_node*, rtx_def*, int)
../../src-trunk/gcc/calls.c:4287
0x8b6c7b expand_expr_real_1(tree_node*, rtx_def*, machine_mode,
expand_modifier, rtx_def**, bool)
../../src-trunk/gcc/expr.c:11011
0x7b78ee expand_expr
../../src-trunk/gcc/expr.h:280
0x7b78ee expand_call_stmt
../../src-trunk/gcc/cfgexpand.c:2690
0x7b78ee expand_gimple_stmt_1
../../src-trunk/gcc/cfgexpand.c:3644
0x7b78ee expand_gimple_stmt
../../src-trunk/gcc/cfgexpand.c:3810
0x7b8a7f expand_gimple_basic_block
../../src-trunk/gcc/cfgexpand.c:5839
0x7bd6b7 execute
../../src-trunk/gcc/cfgexpand.c:6445
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-604952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:19:52 2018
Return-Path: <gcc-bugs-return-604952-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82015 invoked by alias); 17 May 2018 16:19: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 81909 invoked by uid 55); 17 May 2018 16:19:48 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
Date: Thu, 17 May 2018 16:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85698-4-xqewjdGEhh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01847.txt.bz2
Content-length: 586
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #9 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
Author: pthaugen
Date: Thu May 17 16:19:16 2018
New Revision: 260329
URL: https://gcc.gnu.org/viewcvs?rev=260329&root=gcc&view=rev
Log:
PR target/85698
* config/rs6000/rs6000.c (rs6000_output_move_128bit): Check dest
operand.
* gcc.target/powerpc/pr85698.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/powerpc/pr85698.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/rs6000/rs6000.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:26:03 2018
Return-Path: <gcc-bugs-return-604953-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 100332 invoked by alias); 17 May 2018 16:26:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100182 invoked by uid 48); 17 May 2018 16:25:58 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
Date: Thu, 17 May 2018 16:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85698-4-ZSLnaspEiC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01848.txt.bz2
Content-length: 424
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
Pat Haugen <pthaugen at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #10 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-604954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:28:50 2018
Return-Path: <gcc-bugs-return-604954-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106582 invoked by alias); 17 May 2018 16:28: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 106471 invoked by uid 48); 17 May 2018 16:28:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 16:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.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-85813-4-FDIQz5ZQVX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01849.txt.bz2
Content-length: 2195
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Mathias Stearn from comment #3)
> My assumption was that if E(...) throws and it can't be caught, it should be
> treated as any other case when an -fno-exceptions TU calls a throwing
> function. In this case that would mean calling terminate() due to the
> noexcept, which seems better than returning a null exception_ptr.
Simply returning an empty exception_ptr is what happened before the PR 64241
change, so what we do now retains that behaviour. That might be the main reason
for it.
It would be possible to use the new throw-less implementation for the
-fno-exceptions case. It would be fine for types with a non-throwing move, at
least:
--- a/libstdc++-v3/libsupc++/exception_ptr.h
+++ b/libstdc++-v3/libsupc++/exception_ptr.h
@@ -185,7 +185,7 @@ namespace std
__exception_ptr::__dest_thunk<_Ex>);
try
{
- ::new (__e) _Ex(__ex);
+ ::new (__e) _Ex(std::forward<_Ex>(__ex));
return exception_ptr(__e);
}
catch(...)
@@ -203,7 +203,19 @@ namespace std
return current_exception();
}
#else // no RTTI and no exceptions
+#if __cplusplus >= 201103L
+ if _GLIBCXX17_CONSTEXPR (std::is_nothrow_move_constructible<_Ex>::value)
+ {
+ void* __e = __cxxabiv1::__cxa_allocate_exception(sizeof(_Ex));
+ (void) __cxxabiv1::__cxa_init_primary_exception(
+ __e, const_cast<std::type_info*>(&typeid(__ex)),
+ __exception_ptr::__dest_thunk<_Ex>);
+ ::new (__e) _Ex(std::forward<_Ex>(__ex));
+ return exception_ptr(__e);
+ }
+#else
return exception_ptr();
+#endif
#endif
}
> Is that just accepted, implying the the whole program must be compiled with
> either -fexceptions or -fno-exeptions, rather than allowing mix-and-match?
> If so, I guess this whole point is moot.
Mix-and-match works if the function gets inlined.
But if you mix -fexceptions and -fno-exceptions then you do have to accept that
the resulting ODR violations might give surprising or undesirable results.
>From gcc-bugs-return-604955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:29:56 2018
Return-Path: <gcc-bugs-return-604955-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107694 invoked by alias); 17 May 2018 16:29: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 107629 invoked by uid 48); 17 May 2018 16:29:49 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85820] [9 Regression] internal compiler error: Segmentation fault
Date: Thu, 17 May 2018 16:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: prathamesh3492 at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85820-4-DMa4YUC7k9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01850.txt.bz2
Content-length: 262
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820
--- Comment #1 from prathamesh3492 at gcc dot gnu.org ---
This is most likely dup of PR85817. Could you check if the fix in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817#c1 works ?
Thanks,
Prathamesh
>From gcc-bugs-return-604956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:31:00 2018
Return-Path: <gcc-bugs-return-604956-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114301 invoked by alias); 17 May 2018 16:31:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114213 invoked by uid 48); 17 May 2018 16:30:55 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 16: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: 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-85813-4-i4ixx2Lc38@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01851.txt.bz2
Content-length: 798
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> (In reply to Mathias Stearn from comment #3)
> > My assumption was that if E(...) throws and it can't be caught, it should be
> > treated as any other case when an -fno-exceptions TU calls a throwing
> > function. In this case that would mean calling terminate() due to the
> > noexcept, which seems better than returning a null exception_ptr.
>
> Simply returning an empty exception_ptr is what happened before the PR 64241
> change, so what we do now retains that behaviour. That might be the main
> reason for it.
Oops, wrong PR number, I meant PR 68297.
Before the PR 64241 change we just returned undefined garbage!
>From gcc-bugs-return-604957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:33:58 2018
Return-Path: <gcc-bugs-return-604957-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9616 invoked by alias); 17 May 2018 16:33: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 9546 invoked by uid 48); 17 May 2018 16:33:54 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 16:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed bug_severity
Message-ID: <bug-85813-4-u6oCGHQI33@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01852.txt.bz2
Content-length: 588
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
Severity|normal |enhancement
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Let's confirm this as a valid enhancement request anyway.
>From gcc-bugs-return-604958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:34:43 2018
Return-Path: <gcc-bugs-return-604958-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12796 invoked by alias); 17 May 2018 16:34: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 12622 invoked by uid 48); 17 May 2018 16:34:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85763] Feature request: Add a suggestion when compilation fails dues to ambiguous templated friend function
Date: Thu, 17 May 2018 16: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: 7.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85763-4-LujkGVldH0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85763-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85763-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01853.txt.bz2
Content-length: 148
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85763
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
OK thanks for following up.
>From gcc-bugs-return-604959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 16:43:34 2018
Return-Path: <gcc-bugs-return-604959-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26001 invoked by alias); 17 May 2018 16:43: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 25969 invoked by uid 48); 17 May 2018 16:43:29 -0000
From: "andreas.molzer at gmx dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85821] New: Chrono literal operators do not follow the standard declarataions
Date: Thu, 17 May 2018 16:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andreas.molzer 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-85821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01854.txt.bz2
Content-length: 1812
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85821
Bug ID: 85821
Summary: Chrono literal operators do not follow the standard
declarataions
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: andreas.molzer at gmx dot de
Target Milestone: ---
The literal operators provided by std::literals::chrono_literals are missing
their overloads for unsigned long long arguments. They instead provide a
declaration for long double and a non-standard declaration with template
argument list. This silently breaks valid code:
#include <chrono>
int main() {
using namespace std::chrono_literals;
auto time = operator""s(1ull);
}
Name resolution will only find the single matching overload and convert the
argument to long double. This will result in a duration with unspecified
representation, in libstdc++ case a long double. The standard would instead
require the result to be std::chrono::seconds with representation of an
unspecified integral type with a minimum number of bits.
This can have various additional effects, including decltype(time)::max()
returning an invalid result, so that the normally perfectly valid
std::chrono::seconds::rep max = decltype(time)::max()
will result in undefined behaviour due to the long double maximum value not
fitting inside the unsigned long long.
The following code should be rejected because overload resolution should not be
able to determine a best match:
#include <chrono>
int main() {
using namespace std::chrono_literals;
auto time = operator""s(0); // int, no priority for conversion to ull or
ld
}
>From gcc-bugs-return-604960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:01:01 2018
Return-Path: <gcc-bugs-return-604960-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76413 invoked by alias); 17 May 2018 17:01: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 76285 invoked by uid 48); 17 May 2018 17:00:55 -0000
From: "redbeard0531 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 17: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redbeard0531 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-85813-4-ANUZp41KGm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01855.txt.bz2
Content-length: 1735
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #7 from Mathias Stearn <redbeard0531 at gmail dot com> ---
> Simply returning an empty exception_ptr is what happened before the PR 64241
> change, so what we do now retains that behaviour. That might be the main
> reason for it.
Silently dropping errors always skeeves me out. I'm not sure if anyone is well
served by the current behavior. If it were up to me (and I know it isn't) I'd
make that case call std::terminate() or similar rather than returning the "no
error" value. That seems consistent with the behavior of the __throw*
functions, but it is a breaking change. Or even better, since gcc seems fine
throwing through functions marked noexcept in -fno-exceptions TUs, maybe in the
(very rare) case where copying/moving an exception throws inside an
-fno-exceptions TU, just let it bubble out.
> ::new (__e) _Ex(std::forward<_Ex>(__ex));
Should that be std::move(__ex)? I don't know why, but make_exception_ptr takes
the exception by value rather than forwarding ref. I guess forward<_Ex> is fine
either way, and will stay correct if that defect gets fixed. It just seemed odd
to forward a value so I thought I'd mention it.
> Mix-and-match works if the function gets inlined.
Do you think this case warrants a [[gnu::always_inline]]? Given the sensitive
nature of error handling, it seems pretty bad if a correct usage of
make_exception_ptr() could be silently transformed to return the "no error"
value just by linking in a bad library. Even if that library never dynamically
executes make_exception_ptr(). I know I'd hate to be called in to debug that
issue...
I'm going to go make sure no code we link with uses -fno-exceptions!
>From gcc-bugs-return-604961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:15:50 2018
Return-Path: <gcc-bugs-return-604961-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93876 invoked by alias); 17 May 2018 17:15: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 93659 invoked by uid 48); 17 May 2018 17:15:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85813] make_exception_ptr should support __cxa_init_primary_exception path even with -fno-exceptions
Date: Thu, 17 May 2018 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: 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-85813-4-dtQe2rS2xy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85813-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01856.txt.bz2
Content-length: 2726
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85813
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Mathias Stearn from comment #7)
> > Simply returning an empty exception_ptr is what happened before the PR 64241
> > change, so what we do now retains that behaviour. That might be the main
> > reason for it.
>
> Silently dropping errors always skeeves me out. I'm not sure if anyone is
> well served by the current behavior. If it were up to me (and I know it
> isn't) I'd make that case call std::terminate() or similar rather than
> returning the "no error" value. That seems consistent with the behavior of
> the __throw* functions, but it is a breaking change. Or even better, since
> gcc seems fine throwing through functions marked noexcept in -fno-exceptions
> TUs, maybe in the (very rare) case where copying/moving an exception throws
> inside an -fno-exceptions TU, just let it bubble out.
>
> > ::new (__e) _Ex(std::forward<_Ex>(__ex));
>
> Should that be std::move(__ex)?
That would move from an lvalue if called as:
E e;
std::make_exception_ptr<E&>(e);
I don't know if that's valid (I sent an email to the LWG reflector about that a
few minutes ago).
> I don't know why, but make_exception_ptr
> takes the exception by value rather than forwarding ref.
Probably so it decays (which "throw e;" will do anyway).
> I guess
> forward<_Ex> is fine either way, and will stay correct if that defect gets
> fixed. It just seemed odd to forward a value so I thought I'd mention it.
>
> > Mix-and-match works if the function gets inlined.
>
> Do you think this case warrants a [[gnu::always_inline]]? Given the
Without thinking about it too deeply, no I don't think it should have that. It
could have negative consequences on the optimization of other code around the
call to make_exception_ptr (which might be more important, non-error handling
code, that should be inlined in preference to the error-handling path).
> sensitive nature of error handling, it seems pretty bad if a correct usage
> of make_exception_ptr() could be silently transformed to return the "no
> error" value just by linking in a bad library. Even if that library never
> dynamically executes make_exception_ptr(). I know I'd hate to be called in
> to debug that issue...
>
> I'm going to go make sure no code we link with uses -fno-exceptions!
Rather than always_inline a better option might be to give it a different
mangled name when exceptions are disabled (or just not declare it at all, but
it might be too late for that as it would be a breaking change). That would
ensure the return-null version never gets chosen by the linker to replace the
real version.
>From gcc-bugs-return-604962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:18:34 2018
Return-Path: <gcc-bugs-return-604962-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97125 invoked by alias); 17 May 2018 17:18: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 97064 invoked by uid 48); 17 May 2018 17:18:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85821] Chrono literal operators do not follow the standard declarataions
Date: Thu, 17 May 2018 17: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85821-4-9yqUOPRoV9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85821-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85821-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01857.txt.bz2
Content-length: 247
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85821
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The simple answer is of course "don't do that". Writing 1s works fine, or if
you want to be explicit, std::chrono::seconds(1).
>From gcc-bugs-return-604963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:20:52 2018
Return-Path: <gcc-bugs-return-604963-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99091 invoked by alias); 17 May 2018 17:20:52 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 99056 invoked by uid 48); 17 May 2018 17:20:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Thu, 17 May 2018 17: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: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85818-4-xMPvQH0Jmg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01858.txt.bz2
Content-length: 432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed for 8.2
>From gcc-bugs-return-604964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:26:52 2018
Return-Path: <gcc-bugs-return-604964-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120290 invoked by alias); 17 May 2018 17:26: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 120253 invoked by uid 48); 17 May 2018 17:26:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] [7/8 Regression] make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 17:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 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: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85812-4-Kn2KQVFigZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01859.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
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 7.4 and 8.2
>From gcc-bugs-return-604965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:27:20 2018
Return-Path: <gcc-bugs-return-604965-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121212 invoked by alias); 17 May 2018 17:27:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 121176 invoked by uid 55); 17 May 2018 17:27:16 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85812] [7/8 Regression] make_exception_ptr can leak the allocated exception if construction throws
Date: Thu, 17 May 2018 17:27: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: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85812-4-EseHiGbWjE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85812-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01860.txt.bz2
Content-length: 892
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85812
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Thu May 17 17:26:44 2018
New Revision: 260331
URL: https://gcc.gnu.org/viewcvs?rev=260331&root=gcc&view=rev
Log:
PR libstdc++/85812 fix memory leak in std::make_exception_ptr
PR libstdc++/85812
* libsupc++/cxxabi_init_exception.h (__cxa_free_exception): Declare.
* libsupc++/exception_ptr.h (make_exception_ptr) [__cpp_exceptions]:
Refactor to separate non-throwing and throwing implementations.
[__cpp_rtti && !_GLIBCXX_HAVE_CDTOR_CALLABI]: Deallocate the memory
if constructing the object throws.
Modified:
branches/gcc-7-branch/libstdc++-v3/ChangeLog
branches/gcc-7-branch/libstdc++-v3/libsupc++/cxxabi_init_exception.h
branches/gcc-7-branch/libstdc++-v3/libsupc++/exception_ptr.h
>From gcc-bugs-return-604966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 17:44:50 2018
Return-Path: <gcc-bugs-return-604966-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94804 invoked by alias); 17 May 2018 17:44:50 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94744 invoked by uid 48); 17 May 2018 17:44:45 -0000
From: "atarasevich at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/41475] common variables cannot be expected to be aligned
Date: Thu, 17 May 2018 17:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 4.4.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: atarasevich at comcast dot net
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-41475-4-yonnNFZvj3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-41475-4@http.gcc.gnu.org/bugzilla/>
References: <bug-41475-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01861.txt.bz2
Content-length: 881
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=41475
Andrey Tarasevich <atarasevich at comcast dot net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |atarasevich at comcast dot net
--- Comment #10 from Andrey Tarasevich <atarasevich at comcast dot net> ---
(In reply to Andrew Pinski from comment #8)
> This code is undefined I think (and really it is not valid C90/C99 code).
You are absolutely right - this code is not valid from the point of view of
formal standard C language. It is illegal to provide multiple definitions of
external objects with the same name.
However, this is a popular extension in C implementations with Unix heritage.
So, this entry is about the intended non-standard behavior of GCC
compiler/linker.
>From gcc-bugs-return-604967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 18:32:03 2018
Return-Path: <gcc-bugs-return-604967-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89096 invoked by alias); 17 May 2018 18:32: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 88969 invoked by uid 48); 17 May 2018 18:31:59 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/78969] bogus snprintf truncation warning due to missing range info
Date: Thu, 17 May 2018 18:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: diagnostic, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-78969-4-NKZjbRML3e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78969-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78969-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01862.txt.bz2
Content-length: 3234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78969
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |aldyh at gcc dot gnu.org
--- Comment #12 from Martin Sebor <msebor at gcc dot gnu.org> ---
Thanks for the test case. Here's a slightly reduced version of it:
$ cat pr78969.c && gcc -O2 -S -Wall pr78969.c
void f (int, ...);
char d[4];
void g (unsigned i)
{
if (i >= 1000 && i < 10000)
__builtin_snprintf (d, 4, "%3d", i / 10); // bogus -Wformat-truncation
else
f (i / 10 % 10);
}
pr78969.c: In function ‘g’:
pr78969.c:8:32: warning: ‘%3d’ directive output may be truncated writing
between 3 and 9 bytes into a region of size 4 [-Wformat-truncation=]
__builtin_snprintf (d, 4, "%3d", i / 10); // bogus -Wformat-truncation
^~~
pr78969.c:8:31: note: directive argument in the range [0, 429496729]
__builtin_snprintf (d, 4, "%3d", i / 10); // bogus -Wformat-truncation
^~~~~
pr78969.c:8:5: note: ‘__builtin_snprintf’ output between 4 and 10 bytes into a
destination of size 4
__builtin_snprintf (d, 4, "%3d", i / 10); // bogus -Wformat-truncation
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
It does look like the false positive is due to the same underlying limitation
(the range not being reflected accurately outside the VRP pass). GCC 7 doesn't
warn but GCC 8 does. That's because in GCC 7 the result of the
get_range_info() function is VR_VARYING for the argument while in GCC 8 it
reports a VR_RANGE of [0, 429496729]. So ironically, the false positive is a
side-effect of the improvement in GCC 8's range tracking.
There is work underway to improve the accuracy of the range information even
further that should reduce the rate of these kinds of false positives.
That being said, a few comments:
1) The problem doesn't affect just -Wstringop-truncation but other warnings as
well, including -Wformat-overflow. The latter warning, especially, has proven
to be useful enough despite this limitation that removing either from -Wall
doesn't seem a like good solution.
2) The philosophy behind -Wstringop-truncation is based on the assumption that
snprintf() is being called because truncation is possible, and that most
programs aren't prepared to handle it correctly.
In the test case, since truncation isn't possible, calling snprintf() is
unnecessary (and sprintf() would be sufficient -- though calling sprintf with a
fixed-size buffer just big enough for the output would also cause a false
positive). Otherwise, if truncation were possible, the expectation is that the
caller should detect it by testing the return value from the function and
taking some action (e.g., by aborting).
Until the range improvements I mention above are made, I suggest to assume that
snprintf can truncate and handle the truncation somehow. In comparison to the
runtime cost of the snprintf call, the overhead of checking the return value
and aborting is negligible.
>From gcc-bugs-return-604968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 18:53:00 2018
Return-Path: <gcc-bugs-return-604968-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109010 invoked by alias); 17 May 2018 18: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 108948 invoked by uid 48); 17 May 2018 18:52:55 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] New: [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Thu, 17 May 2018 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: 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-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01863.txt.bz2
Content-length: 1062
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Bug ID: 85822
Summary: [8/9 Regression] Maybe wrong code in VRP since r249150
Product: gcc
Version: unknown
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, ygribov at gcc dot gnu.org
Target Milestone: ---
I've saw that in qtscript, isolated test-case looks as follows:
$ cat vrp.c
static const long int TagTypeNumber = 0xffff000000000000ll;
long int x;
void foo(void)
{
x = TagTypeNumber + 1;
}
int main(int argc, char **argv)
{
if (argc > 0)
foo ();
if ((x & TagTypeNumber) == TagTypeNumber)
{
unsigned y = (unsigned)x;
__builtin_printf ("v: %u\n", y);
if (y != 1)
__builtin_abort ();
}
return 0;
}
$ gcc -O2 vrp.c && ./a.out
v: 0
Aborted (core dumped)
$
>From gcc-bugs-return-604969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 18:53:40 2018
Return-Path: <gcc-bugs-return-604969-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 131026 invoked by alias); 17 May 2018 18:53: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 128415 invoked by uid 48); 17 May 2018 18:53:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Thu, 17 May 2018 18:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on version everconfirmed
Message-ID: <bug-85822-4-eayvtzdZgY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01864.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Version|unknown |9.0
Ever confirmed|0 |1
>From gcc-bugs-return-604970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 18:57:04 2018
Return-Path: <gcc-bugs-return-604970-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116809 invoked by alias); 17 May 2018 18:57: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 116706 invoked by uid 48); 17 May 2018 18:57:01 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85820] [9 Regression] internal compiler error: Segmentation fault
Date: Thu, 17 May 2018 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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-85820-4-2R9JMDeQL5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85820-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85820-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01865.txt.bz2
Content-length: 685
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85820
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to prathamesh3492 from comment #1)
> This is most likely dup of PR85817. Could you check if the fix in
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817#c1 works ?
Yes, the patch works. Thanks.
*** This bug has been marked as a duplicate of bug 85817 ***
>From gcc-bugs-return-604971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 18:57:05 2018
Return-Path: <gcc-bugs-return-604971-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116902 invoked by alias); 17 May 2018 18:57: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 116729 invoked by uid 48); 17 May 2018 18:57:01 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85817] [9 Regression] ICE in expand_call at gcc/calls.c:4291
Date: Thu, 17 May 2018 18:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-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: cc
Message-ID: <bug-85817-4-UI2IPcEZxM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01866.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
*** Bug 85820 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 19:31:41 2018
Return-Path: <gcc-bugs-return-604972-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111321 invoked by alias); 17 May 2018 19:31: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 108258 invoked by uid 48); 17 May 2018 19:31:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85823] New: Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression
Date: Thu, 17 May 2018 19: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: 8.1.1
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: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01867.txt.bz2
Content-length: 1275
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
Bug ID: 85823
Summary: Boost.Tribool fails to compile: error:
'(tribool::dummy::nonnull != 0)' is not a constant
expression
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Keywords: rejects-valid
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
Reduced from
https://github.com/boostorg/logic/pull/5#issuecomment-389965834
struct B {
struct dummy {
void nonnull() { }
};
using safe_bool = void (dummy::*)();
constexpr B() : value(false) {}
constexpr B(int) : value(true) {}
constexpr operator safe_bool() const
{
return value ? &dummy::nonnull : 0;
}
bool value;
};
constexpr B operator!(B x)
{
return x.value ? B() : B(1);
}
constexpr B tb_f{};
static_assert(!tb_f, "");
tribool.cc:25:15: error: non-constant condition for static assertion
static_assert(!tb_f, "");
^~~~~
tribool.cc:25:25: error: '(B::dummy::nonnull != 0)' is not a constant
expression
static_assert(!tb_f, "");
^
>From gcc-bugs-return-604973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 19:36:34 2018
Return-Path: <gcc-bugs-return-604973-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19106 invoked by alias); 17 May 2018 19:36: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 19064 invoked by uid 48); 17 May 2018 19:36:30 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85823] Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression
Date: Thu, 17 May 2018 19: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.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85823-4-1tbVDJGDM3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01868.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
CC| |mpolacek at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Seems this never worked, thus not a regression.
>From gcc-bugs-return-604974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 19:38:55 2018
Return-Path: <gcc-bugs-return-604974-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21768 invoked by alias); 17 May 2018 19:38: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 21705 invoked by uid 48); 17 May 2018 19:38:50 -0000
From: "krzysio.kurek at wp dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/82229] GCC7's LTO underperforms compared to GCC6
Date: Thu, 17 May 2018 19:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: lto, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: krzysio.kurek at wp dot pl
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-82229-4-0bqaaCb2J7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82229-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82229-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01869.txt.bz2
Content-length: 204
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82229
--- Comment #28 from krzysio.kurek at wp dot pl ---
I mean the relative performance is worse but still Profiled GCC6 is faster than
GCC 7 or GCC 8.
>From gcc-bugs-return-604975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 19:50:16 2018
Return-Path: <gcc-bugs-return-604975-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103491 invoked by alias); 17 May 2018 19:50:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103345 invoked by uid 48); 17 May 2018 19:50:09 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Thu, 17 May 2018 19: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: 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-85822-4-lsensQaQC9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01870.txt.bz2
Content-length: 553
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
_2 = x.0_1 & -281474976710656;
if (_2 == -281474976710656)
goto <bb 5>; [20.24%]
[...]
x.0_11 = ASSERT_EXPR <x.0_1, (unsigned long) x.0_1 + 281474976710656 <=
281474976710655>;
x.0_12 = ASSERT_EXPR <x.0_11, x.0_11 <= -281474976710656>;
x.0_13 = ASSERT_EXPR <x.0_12, x.0_12 >= -1>;
y_7 = (unsigned intD.9) x.0_13;
Those ASSERT_EXPR look strange, possibly the last 2 inequalities are inverted.
>From gcc-bugs-return-604976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 19:55:24 2018
Return-Path: <gcc-bugs-return-604976-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123908 invoked by alias); 17 May 2018 19:55:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118076 invoked by uid 48); 17 May 2018 19:55:20 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Thu, 17 May 2018 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-85814-4-G8nbiK1OZF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01871.txt.bz2
Content-length: 566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |rsandifo at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #6 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-604977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 20:31:31 2018
Return-Path: <gcc-bugs-return-604977-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11234 invoked by alias); 17 May 2018 20:31:30 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11120 invoked by uid 48); 17 May 2018 20:31:26 -0000
From: "wanyingloo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] New: regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class
Date: Thu, 17 May 2018 20:31: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: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wanyingloo 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-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01872.txt.bz2
Content-length: 3608
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
Bug ID: 85824
Summary: regex constructor crashes under UTF-8 locale on
Solaris-sparc when parsing a simple character class
Product: gcc
Version: 4.9.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: wanyingloo at gmail dot com
Target Milestone: ---
$ cat test.cpp
#include <locale.h>
#include <regex>
int main (int argc, char *argv[]) {
setlocale(LC_ALL, "");
std::regex("[0-9]");
}
$ echo $LANG
en_US.UTF-8
$ g++ -std=c++11 test.cpp
$ ./a.out
terminate called after throwing an instance of 'std::length_error'
what(): basic_string::append
Abort (core dumped)
$ uname -a
SunOS t-solaris11sparc-02 5.11 11.3 sun4v sparc sun4v Solaris
$ g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/tmp/wluo/othello/solaris-sparc-packages/bin/../libexec/gcc/sparc-sun-solaris2.10/4.9.2/lto-wrapper
Target: sparc-sun-solaris2.10
Configured with: ../gcc-4.9.2/configure --prefix=/usr
--with-local-prefix=/usr/local --enable-languages=c,c++ --disable-nls
--disable-lto --enable-clocale=generic
--with-stage1-ldflags='-L/data00/builds/trprince/platform-packages-build/idir/solaris-sparc/stage1-packages/lib
-static-libgcc -static-libstdc++ -laio -lmd'
--with-boot-ldflags='-L/data00/builds/trprince/platform-packages-build/idir/solaris-sparc/stage1-packages/lib
-static-libgcc -static-libstdc++ -laio -lmd' --disable-werror
--with-libiconv-prefix=/data00/builds/trprince/platform-packages-build/idir/solaris-sparc/stage1-packages
--with-gnu-ld --with-gnu-as --disable-multiarch --disable-bootstrap
Thread model: posix
gcc version 4.9.2 (GCC)
I can't reproduce it on Linux using the same GCC version. I did some
investigation and it seems to be because regex compiler doesn't account for
implementation-defined behavior of strxfrm(). I ran the following test on the
same Solaris SPARC machine.
$ cat more_test.cpp
#include <locale.h>
#include <errno.h>
#include <stdio.h>
#include <string.h>
int main (int argc, char *argv[]) {
setlocale(LC_ALL, "");
char a[] = { 0x80, '\0' };
printf("%lu\n", strxfrm(NULL, a, 0));
printf("%s\n", strerror(errno));
}
$ g++ -std=c++11 -w more_test.cpp
$ ./a.out
4294967295
Illegal byte sequence
In libstdc++-v3/include/bits/locale_classes.tcc, do_transform() is defined as
follows:
do_transform(const _CharT* __lo, const _CharT* __hi) const
{
...
size_t __res = _M_transform(__c, __p, __len);
...
__ret.append(__c, __res);
When _M_transform() calls strxfrm() and gets -1 when converting 0x80 under the
UTF-8 locale on Solaris SPARC, it simply assigns -1 to __res of type size_t
which creates a very large number. This causes __ret.append(__c, __res) to
crash. I think it would be nice if the code checks errno and issues a better
error message than the one above.
When I ran this test on a Linux machine with GCC 4.9.2, glibc's strxfrm()
converts 0x80 to 6 bytes. I tend to think Solaris SPARC's libc behavior makes
more sense here since 0x80 on its own isn't a valid UTF-8 code point even
though it's a valid UTF-8 code unit. I have no idea why glibc converts it to 6
bytes. In any event, how strxfrm() converts 0x80 under UTF-8 is
implementation-defined, and I'm not sure do_transform() accounts for that. At
the very least, it can be more defensive by checking errno, I think.
>From gcc-bugs-return-604978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 20:33:30 2018
Return-Path: <gcc-bugs-return-604978-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29841 invoked by alias); 17 May 2018 20:33: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 29711 invoked by uid 48); 17 May 2018 20:33:24 -0000
From: "wanyingloo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class
Date: Thu, 17 May 2018 20:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wanyingloo 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-85824-4-8bVOZveXNr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01873.txt.bz2
Content-length: 3299
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
--- Comment #1 from Wanying Luo <wanyingloo at gmail dot com> ---
Here's GDB backtrace at the time of crash.
#0 0xf56fe7a0 in __lwp_sigqueue () from /lib/libc.so.1
#1 0xf56a1e90 in raise () from /lib/libc.so.1
#2 0xf567a274 in abort () from /lib/libc.so.1
#3 0xff2f2d70 in __gnu_cxx::__verbose_terminate_handler ()
at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#4 0xff2ef844 in __cxxabiv1::__terminate (handler=0xff2f2bac
<__gnu_cxx::__verbose_terminate_handler()>)
at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:47
#5 0xff2ef8e8 in std::terminate () at
../../../../libstdc++-v3/libsupc++/eh_terminate.cc:57
#6 0xff2efc68 in __cxxabiv1::__cxa_rethrow () at
../../../../libstdc++-v3/libsupc++/eh_throw.cc:125
#7 0xff29c974 in std::collate<char>::do_transform (this=0xff34d9f8 <(anonymous
namespace)::collate_c>,
__lo=0x4fb3c "\200", __hi=0x4fb3d "")
at
/tmp/wluo/gcc-4.9.2/build/sparc-sun-solaris2.11/libstdc++-v3/include/bits/locale_classes.tcc:245
#8 0xff29c25c in std::collate<char>::transform (this=0xff34d9f8 <(anonymous
namespace)::collate_c>,
__lo=0x4fb3c "\200", __hi=0x4fb3d "")
at
/tmp/wluo/gcc-4.9.2/build/sparc-sun-solaris2.11/libstdc++-v3/include/bits/locale_classes.h:662
#9 0x0002ead4 in std::string std::regex_traits<char>::transform<char*>(char*,
char*) const ()
#10 0x0002c634 in std::string
std::regex_traits<char>::transform_primary<char*>(char*, char*) const ()
#11 0x000275f8 in std::__detail::_BracketMatcher<std::regex_traits<char>,
false, false>::_M_apply(char, std::integral_constant<bool, false>) const ()
#12 0x00022bb4 in std::__detail::_BracketMatcher<std::regex_traits<char>,
false, false>::_M_make_cache(std::integral_constant<bool, true>) ()
#13 0x0001ed70 in std::__detail::_BracketMatcher<std::regex_traits<char>,
false, false>::_M_ready() ()
#14 0x0001f958 in void std::__detail::_Compiler<std::regex_traits<char>
>::_M_insert_bracket_matcher<false, false>(bool) ()
#15 0x0001c630 in std::__detail::_Compiler<std::regex_traits<char>
>::_M_bracket_expression() ()
#16 0x000192e8 in std::__detail::_Compiler<std::regex_traits<char> >::_M_atom()
()
#17 0x00017910 in std::__detail::_Compiler<std::regex_traits<char> >::_M_term()
()
#18 0x00015868 in std::__detail::_Compiler<std::regex_traits<char>
>::_M_alternative() ()
#19 0x000141dc in std::__detail::_Compiler<std::regex_traits<char>
>::_M_disjunction() ()
#20 0x0001381c in std::__detail::_Compiler<std::regex_traits<char>
>::_Compiler(char const*, char const*, std::regex_traits<char> const&,
std::regex_constants::syntax_option_type) ()
#21 0x00013340 in std::shared_ptr<std::__detail::_NFA<std::regex_traits<char> >
> std::__detail::__compile_nfa<std::regex_traits<char>
>(std::regex_traits<char>::char_type const*, std::regex_traits<char>::char_type
const*, std::regex_traits<char> const&,
std::regex_constants::syntax_option_type) ()
#22 0x0001307c in std::basic_regex<char, std::regex_traits<char>
>::basic_regex<char const*>(char const*, char const*,
std::regex_constants::syntax_option_type) ()
#23 0x00012d84 in std::basic_regex<char, std::regex_traits<char>
>::basic_regex(char const*, std::regex_constants::syntax_option_type) ()
#24 0x000120d0 in main ()
>From gcc-bugs-return-604979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 20:37:30 2018
Return-Path: <gcc-bugs-return-604979-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119263 invoked by alias); 17 May 2018 20:37: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 113013 invoked by uid 48); 17 May 2018 20:37:25 -0000
From: "wanyingloo at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris-sparc when parsing a simple character class
Date: Thu, 17 May 2018 20: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: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wanyingloo 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-85824-4-1JcgZeZZf8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01874.txt.bz2
Content-length: 1980
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
--- Comment #2 from Wanying Luo <wanyingloo at gmail dot com> ---
(In reply to Wanying Luo from comment #0)
> When I ran this test on a Linux machine with GCC 4.9.2, glibc's strxfrm()
> converts 0x80 to 6 bytes.
Pasting my test on Linux with the same version of GCC for completeness.
$ cat test.cpp
#include <locale.h>
#include <regex>
int main (int argc, char *argv[]) {
setlocale(LC_ALL, "");
std::regex("[0-9]");
}
$ echo $LANG
en_US.UTF-8
$ g++ -std=c++11 test.cpp
$ ./a.out
$ cat more_test.cpp
#include <locale.h>
#include <errno.h>
#include <stdio.h>
#include <string.h>
int main (int argc, char *argv[]) {
setlocale(LC_ALL, "");
char a[] = { 0x80, '\0' };
printf("%lu\n", strxfrm(NULL, a, 0));
printf("%s\n", strerror(errno));
}
$ g++ -std=c++11 -w more_test.cpp
$ ./a.out
6
Success
$ uname -a
Linux d-ubuntu12x64-11 3.2.0-126-generic #169-Ubuntu SMP Fri Mar 31 14:15:21
UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/home/wluo/othello/linux64-packages/bin/../libexec/gcc/x86_64-unknown-linux-gnu/4.9.2/lto-wrapper
Target: x86_64-unknown-linux-gnu
Configured with: ../gcc-4.9.2/configure --prefix=/usr
--with-local-prefix=/usr/local --enable-languages=c,c++,fortran --disable-nls
--disable-libcilkrts --disable-lto --enable-libstdcxx-time
--enable-clocale=generic
--with-stage1-ldflags='-L/slowfs/sighome/calebs/working/platform-packages-build/idir/linux64/stage1-packages/lib64
-L/slowfs/sighome/calebs/working/platform-packages-build/idir/linux64/stage1-packages/lib'
--with-boot-ldflags='-L/slowfs/sighome/calebs/working/platform-packages-build/idir/linux64/stage1-packages/lib64
-L/slowfs/sighome/calebs/working/platform-packages-build/idir/linux64/stage1-packages/lib'
--disable-werror --disable-multiarch --disable-bootstrap
Thread model: posix
gcc version 4.9.2 (GCC)
>From gcc-bugs-return-604980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 20:58:15 2018
Return-Path: <gcc-bugs-return-604980-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69415 invoked by alias); 17 May 2018 20:58:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69323 invoked by uid 48); 17 May 2018 20:58:10 -0000
From: "tetra2005 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Thu, 17 May 2018 20: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: tetra2005 at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85822-4-Zl7qCTkbM8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01875.txt.bz2
Content-length: 389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Yuri Gribov <tetra2005 at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tetra2005 at gmail dot com
--- Comment #2 from Yuri Gribov <tetra2005 at gmail dot com> ---
Checking.
>From gcc-bugs-return-604981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 21:21:39 2018
Return-Path: <gcc-bugs-return-604981-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6342 invoked by alias); 17 May 2018 21: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 6269 invoked by uid 48); 17 May 2018 21:21:34 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/78797] It is time perhaps to implement -stdò015
Date: Thu, 17 May 2018 21:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-78797-4-Ew3wd7rypT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-78797-4@http.gcc.gnu.org/bugzilla/>
References: <bug-78797-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01876.txt.bz2
Content-length: 628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78797
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |8.0
--- Comment #10 from janus at gcc dot gnu.org ---
(In reply to Harald Anlauf from comment #8)
> As -std=f2018 will be available in 8.0 and replaces -std=f2015,
> shouldn't this bug be closed?
Yes, gfortran 8 has -std=f2018. Closing.
>From gcc-bugs-return-604982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 21:29:44 2018
Return-Path: <gcc-bugs-return-604982-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74712 invoked by alias); 17 May 2018 21:29: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 74659 invoked by uid 48); 17 May 2018 21:29:38 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85823] Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression
Date: Thu, 17 May 2018 21:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85823-4-KIy9hD4hxl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01877.txt.bz2
Content-length: 174
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485
>From gcc-bugs-return-604983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 21:51:47 2018
Return-Path: <gcc-bugs-return-604983-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117570 invoked by alias); 17 May 2018 21: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 117465 invoked by uid 48); 17 May 2018 21:51:41 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85803] [6/7/8/9 Regression] DSE removes live global store
Date: Thu, 17 May 2018 21:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou 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: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85803-4-dQb8NUrenM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01878.txt.bz2
Content-length: 1219
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85803
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
(> I think the only in-tree language eventually specifying behavior for stuff
> like above is Ada - so, any comments / attempts for testcases where we do
> not follow language specified behavior?
I don't think that the language fully does it, it's quite borderline.
But something changed in DSE yesterday, the following procedure compiled with
-gnatp -O used to print "SEGV Handler" and now it runs quietly.
with Ada.Text_IO;
procedure p is
procedure leaf is
type Int_Ptr is access all Integer;
function n return Int_Ptr is
begin return null; end;
Data : Int_Ptr := n;
begin
Data.all := 0;
end;
begin
leaf;
exception
when others =>
Ada.Text_IO.Put_Line ("SEGV Handler");
end;
>From gcc-bugs-return-604984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 21:52:29 2018
Return-Path: <gcc-bugs-return-604984-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25784 invoked by alias); 17 May 2018 21:52:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21449 invoked by uid 48); 17 May 2018 21:52:25 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Thu, 17 May 2018 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-85822-4-pD0wL350vW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01879.txt.bz2
Content-length: 292
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |8.2
>From gcc-bugs-return-604985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 22:02:35 2018
Return-Path: <gcc-bugs-return-604985-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121152 invoked by alias); 17 May 2018 22:02: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 120832 invoked by uid 48); 17 May 2018 22:02:30 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85823] Boost.Tribool fails to compile: error: '(tribool::dummy::nonnull != 0)' is not a constant expression
Date: Thu, 17 May 2018 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.1.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: 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-85823-4-7JMtFmE6MF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85823-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01880.txt.bz2
Content-length: 500
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85823
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Thanks, Andrew.
*** This bug has been marked as a duplicate of bug 80485 ***
>From gcc-bugs-return-604987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 22:02:52 2018
Return-Path: <gcc-bugs-return-604987-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123024 invoked by alias); 17 May 2018 22:02:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 122933 invoked by uid 48); 17 May 2018 22:02:48 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80485] rejects-valid: constexpr static_cast of pointer-to-member-function to bool
Date: Thu, 17 May 2018 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: 7.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-80485-4-wHqrRgLtKb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80485-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80485-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01881.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
>From gcc-bugs-return-604986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 22:02:35 2018
Return-Path: <gcc-bugs-return-604986-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121201 invoked by alias); 17 May 2018 22:02: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 120849 invoked by uid 48); 17 May 2018 22:02:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80485] rejects-valid: constexpr static_cast of pointer-to-member-function to bool
Date: Thu, 17 May 2018 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: 7.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: cc
Message-ID: <bug-80485-4-TwKgIAjyOn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80485-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80485-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01882.txt.bz2
Content-length: 440
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80485
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |redi at gcc dot gnu.org
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 85823 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 22:36:44 2018
Return-Path: <gcc-bugs-return-604988-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98041 invoked by alias); 17 May 2018 22:36: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 98001 invoked by uid 48); 17 May 2018 22:36:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris SPARC when parsing a simple character class
Date: Thu, 17 May 2018 22:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85824-4-LfVXXhY51R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01883.txt.bz2
Content-length: 1528
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-17
Ever confirmed|0 |1
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Wanying Luo from comment #0)
> gcc version 4.9.2 (GCC)
The earliest currently supported release is GCC 6.4, but this doesn't appear to
have been fixed already.
> In libstdc++-v3/include/bits/locale_classes.tcc, do_transform() is defined
> as follows:
>
> do_transform(const _CharT* __lo, const _CharT* __hi) const
> {
> ...
> size_t __res = _M_transform(__c, __p, __len);
> ...
> __ret.append(__c, __res);
>
>
> When _M_transform() calls strxfrm() and gets -1 when converting 0x80 under
> the UTF-8 locale on Solaris SPARC, it simply assigns -1 to __res of type
> size_t which creates a very large number. This causes __ret.append(__c,
> __res) to crash.
Well the value returned is already a size_t, so it's already a very large
number (not -1), and we do check for larger values than expected, but we don't
check for errors.
> I think it would be nice if the code checks errno and
> issues a better error message than the one above.
Yes, we need to check errno for errors from strxfrm.
>From gcc-bugs-return-604989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 22:58:48 2018
Return-Path: <gcc-bugs-return-604989-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84963 invoked by alias); 17 May 2018 22:58:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84931 invoked by uid 48); 17 May 2018 22:58:43 -0000
From: "christosstratopoulos1 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85825] New: Incorrect selection of method in template<auto> class specialization.
Date: Thu, 17 May 2018 22:58: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: christosstratopoulos1 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-85825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01884.txt.bz2
Content-length: 3555
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85825
Bug ID: 85825
Summary: Incorrect selection of method in template<auto> class
specialization.
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: christosstratopoulos1 at gmail dot com
Target Milestone: ---
Created attachment 44144
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44144&action=edit
The output of compilation with -save-temps
Here is the full sample code that causes the issue:
#include <cassert>
enum class Frac : unsigned { half = 2, quarter = 4 };
enum class Whole : unsigned { two = 2, five = 5 };
template<unsigned, auto enumVal>
class A;
template<unsigned m, Frac f>
class A<m, f> {
public:
constexpr double val() const noexcept { return 2.0; }
};
template<unsigned m, Whole w>
class A<m, w> {
public:
constexpr double val() const noexcept { return 1.0; }
};
int main()
{
auto frac4 = A<100, Frac::quarter>{}.val();
auto whole5 = A<100, Whole::five>{}.val();
assert(frac4 != whole5); // passes
auto frac2 = A<100, Frac::half>{}.val();
auto whole2 = A<100, Whole::two>{}.val();
assert(frac2 != whole2); // fails on g++ 7.x, fine on 8.1, 9 HEAD
}
This is a heavily reduced version of something I encountered at work today,
originally when compiling some code for g++-7.3.0 on a Bash subsystem of a
windows 10 install. I've attached a .ii for that file, and marked this as a
g++-7.3 bug, but testing on wandbox.org has shown this holds for other g++ 7.x,
but seems fine on 8 and 9.
I first ran into this as a compile-time error when trying to compile with the
windows version of clang 6, which reports "definition with same mangled name as
other definition". I have not been able to repro this with online (Linux)
versions of clang.
Here is the output of g++-7 -v:
Using built-in specs.
COLLECT_GCC=g++-7
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
7.3.0-16ubuntu3~16.04.1' --with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --with-as=/usr/bin/x86_64-linux-gnu-as
--with-ld=/usr/bin/x86_64-linux-gnu-ld --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3~16.04.1)
and the command line invocation is
g++-7 -std=c++17 gcc_bug_simple.cpp && ./a.out
>From gcc-bugs-return-604990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 22:59:00 2018
Return-Path: <gcc-bugs-return-604990-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85746 invoked by alias); 17 May 2018 22:59:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85665 invoked by uid 55); 17 May 2018 22:58:56 -0000
From: "andrew at sifive dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85492] riscv64: endless loop when throwing an exception from a constructor
Date: Thu, 17 May 2018 22:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: andrew at sifive dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: palmer at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85492-4-MhHDxPq1wx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85492-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85492-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01885.txt.bz2
Content-length: 1511
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85492
--- Comment #10 from Andrew Waterman <andrew at sifive dot com> ---
Thanks for the suggestion. Let's go with the CFI-directive approach.
On Sat, Apr 28, 2018 at 5:45 AM, aurelien at aurel32 dot net
<gcc-bugzilla@gcc.gnu.org> wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85492
>
> --- Comment #7 from Aurelien Jarno <aurelien at aurel32 dot net> ---
> (In reply to Jim Wilson from comment #3)
> Thanks a lot Jim for finding out the issue without using gdb, that was quite a
> challenge.
>
> (In reply to Jim Wilson from comment #6)
>> I suggest you handle the glibc patch.
>
> Should I just close this bug and open a new one on the glibc side?
>
>> Note that you can probably also fix this by adding unwind direcives to
>> _start to say that the return address is in x0. This would avoid the minor
>> code size increase, but takes a little more effort to figure out how to add
>> the right unwind directives to assembly code to make this work. I haven't
>> tried that.
>
> I think this should be done with the cfi_undefined directive, like in the patch
> below:
>
> --- a/sysdeps/riscv/start.S
> +++ b/sysdeps/riscv/start.S
> @@ -43,6 +43,8 @@
> __libc_start_main wants this in a5. */
>
> ENTRY (ENTRY_POINT)
> + /* Mark ra as undefined in order to stop unwinding here! */
> + cfi_undefined (ra)
> call .Lload_gp
> mv a5, a0 /* rtld_fini. */
> /* main may be in a shared library. */
>From gcc-bugs-return-604991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 17 23:11:55 2018
Return-Path: <gcc-bugs-return-604991-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6977 invoked by alias); 17 May 2018 23:11:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6912 invoked by uid 48); 17 May 2018 23:11:50 -0000
From: "tetra2005 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Thu, 17 May 2018 23: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: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tetra2005 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85822-4-SfPnUvF0hJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01886.txt.bz2
Content-length: 381
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #3 from Yuri Gribov <tetra2005 at gmail dot com> ---
It seems these lines in is_masked_range_test should be removed:
if (wi::neg_p (val, TYPE_SIGN (type)))
std::swap (*low, *high);
Sadly there were no tests which tested negative constants. I'll bootstrap and
send patch tomorrow (hope there's no urgency?).
>From gcc-bugs-return-604992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 02:02:17 2018
Return-Path: <gcc-bugs-return-604992-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4904 invoked by alias); 18 May 2018 02:02:17 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1521 invoked by uid 48); 18 May 2018 02:02:11 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85602] -Wsizeof-pointer-memaccess for strncat with size of source
Date: Fri, 18 May 2018 02: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.0.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: P2
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-85602-4-OSb6MJP1zm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85602-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85602-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01887.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85602
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #5 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00869.html
>From gcc-bugs-return-604993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 07:24:56 2018
Return-Path: <gcc-bugs-return-604993-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97345 invoked by alias); 18 May 2018 07: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 96950 invoked by uid 55); 18 May 2018 07:24:37 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Fri, 18 May 2018 07:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85822-4-3Qtf8jEuop@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01888.txt.bz2
Content-length: 803
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #4 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 17 May 2018, tetra2005 at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
>
> --- Comment #3 from Yuri Gribov <tetra2005 at gmail dot com> ---
> It seems these lines in is_masked_range_test should be removed:
> if (wi::neg_p (val, TYPE_SIGN (type)))
> std::swap (*low, *high);
> Sadly there were no tests which tested negative constants. I'll bootstrap and
> send patch tomorrow (hope there's no urgency?).
Well, iff then you should replace the above with
if (wi::neg_p (val, TYPE_SIGN (type)))
return false;
(possibly earlier as soon as val is computed). At least w/o more
exhaustive test coverage or explanation.
>From gcc-bugs-return-604994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 07:54:44 2018
Return-Path: <gcc-bugs-return-604994-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52124 invoked by alias); 18 May 2018 07:54:43 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52078 invoked by uid 48); 18 May 2018 07:54:39 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68950] [fortran] gfc_format_decoder cannot handle %qE
Date: Fri, 18 May 2018 07: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: 6.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: minor
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68950-4-YnGw8ZxUCW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01889.txt.bz2
Content-length: 362
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68950
--- Comment #11 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to kargl from comment #10)
> If you're looking for a Fortran maintainer's approval, then
> one may want to submit the patch to fortran@gcc.gnu.org.
Both the original submission and the ping where to both gcc-patches@ and
fortran@.
>From gcc-bugs-return-604995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:08:04 2018
Return-Path: <gcc-bugs-return-604995-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112668 invoked by alias); 18 May 2018 08:08: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 111884 invoked by uid 48); 18 May 2018 08:07:57 -0000
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68950] [fortran] gfc_format_decoder cannot handle %qE
Date: Fri, 18 May 2018 08: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: 6.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: minor
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-68950-4-i1bvf697sn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68950-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01890.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68950
--- Comment #12 from Tom de Vries <vries at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #9)
> (In reply to Tom de Vries from comment #8)
> > (In reply to vries from comment #6)
> > > posted RFC: https://gcc.gnu.org/ml/gcc-patches/2015-12/msg01749.html
> >
> > pinged: https://gcc.gnu.org/ml/gcc-patches/2016-01/msg00831.html
>
> Please keep pinging!
ping^2: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00876.html
>From gcc-bugs-return-604996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:09:49 2018
Return-Path: <gcc-bugs-return-604996-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120666 invoked by alias); 18 May 2018 08:09:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 120631 invoked by uid 48); 18 May 2018 08:09:44 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85826] New: [9 Regression] ICE in builtin_memref in gcc/gimple-ssa-warn-restrict.c:281 starting with r260280
Date: Fri, 18 May 2018 08:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
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-85826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01891.txt.bz2
Content-length: 2941
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85826
Bug ID: 85826
Summary: [9 Regression] ICE in builtin_memref in
gcc/gimple-ssa-warn-restrict.c:281 starting with
r260280
Product: gcc
Version: unknown
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: msebor at gcc dot gnu.org
Target Milestone: ---
Following ICEs:
$ gcc /home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr66817.c
-Warray-bounds -O3
during GIMPLE pass: wrestrict
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr66817.c: In
function ‘retframe_block’:
/home/marxin/Programming/gcc/gcc/testsuite/gcc.target/i386/pr66817.c:16:3:
internal compiler error: tree check: expected integer_cst, have var_decl in
get_len, at tree.h:5571
retframe_block ()
^~~~~~~~~~~~~~
0x5d5f98 tree_check_failed(tree_node const*, char const*, int, char const*,
...)
../../gcc/tree.c:9337
0x95e3fb tree_check(tree_node const*, char const*, int, char const*, tree_code)
../../gcc/tree.h:3391
0x95e3fb wi::extended_tree<128>::get_len() const
../../gcc/tree.h:5571
0x95e3fb wi::int_traits<generic_wide_int<wi::extended_tree<128> >
>::decompose(long*, unsigned int, generic_wide_int<wi::extended_tree<128> >
const&)
../../gcc/wide-int.h:934
0x95e3fb wide_int_ref_storage<true,
false>::wide_int_ref_storage<generic_wide_int<wi::extended_tree<128> >
>(generic_wide_int<wi::extended_tree<128> > const&, unsigned int)
../../gcc/wide-int.h:983
0x95e3fb generic_wide_int<wide_int_ref_storage<true, false>
>::generic_wide_int<generic_wide_int<wi::extended_tree<128> >
>(generic_wide_int<wi::extended_tree<128> > const&, unsigned int)
../../gcc/wide-int.h:758
0x95e3fb
fixed_wide_int_storage<128>::fixed_wide_int_storage<generic_wide_int<wi::extended_tree<128>
> >(generic_wide_int<wi::extended_tree<128> > const&)
../../gcc/wide-int.h:1211
0x95e3fb generic_wide_int<fixed_wide_int_storage<128> >&
generic_wide_int<fixed_wide_int_storage<128>
>::operator=<generic_wide_int<wi::extended_tree<128> >
>(generic_wide_int<wi::extended_tree<128> > const&)
../../gcc/wide-int.h:886
0x95e3fb builtin_memref
../../gcc/gimple-ssa-warn-restrict.c:281
0x95fac2 check_bounds_or_overlap(gcall*, tree_node*, tree_node*, tree_node*,
tree_node*, bool)
../../gcc/gimple-ssa-warn-restrict.c:1855
0x96270b check_call
../../gcc/gimple-ssa-warn-restrict.c:1826
0x96270b before_dom_children
../../gcc/gimple-ssa-warn-restrict.c:106
0x146bd9f dom_walker::walk(basic_block_def*)
../../gcc/domwalk.c:353
0x957071 execute
../../gcc/gimple-ssa-warn-restrict.c:120
>From gcc-bugs-return-604997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:10:16 2018
Return-Path: <gcc-bugs-return-604997-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121613 invoked by alias); 18 May 2018 08:10: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 121494 invoked by uid 48); 18 May 2018 08:10:04 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85826] [9 Regression] ICE in builtin_memref in gcc/gimple-ssa-warn-restrict.c:281 starting with r260280
Date: Fri, 18 May 2018 08: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cf_known_to_work version everconfirmed cf_known_to_fail
Message-ID: <bug-85826-4-jAPV9vNWKE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01892.txt.bz2
Content-length: 567
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85826
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-18
Known to work| |8.1.0
Version|unknown |9.0
Ever confirmed|0 |1
Known to fail| |9.0
>From gcc-bugs-return-604998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:19:59 2018
Return-Path: <gcc-bugs-return-604998-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28056 invoked by alias); 18 May 2018 08:19: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 27977 invoked by uid 48); 18 May 2018 08:19:54 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Fri, 18 May 2018 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: 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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to attachments.created
Message-ID: <bug-85822-4-K8ZAn7qECN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01893.txt.bz2
Content-length: 697
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
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 #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 44145
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44145&action=edit
patch I am testing
I am testing the attached. Please check how negative values can be handled
correctly or why exactly the handling was wrong.
>From gcc-bugs-return-604999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:21:56 2018
Return-Path: <gcc-bugs-return-604999-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33654 invoked by alias); 18 May 2018 08: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 33233 invoked by uid 48); 18 May 2018 08:21:35 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85817] [9 Regression] ICE in expand_call at gcc/calls.c:4291
Date: Fri, 18 May 2018 08:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_gcctarget priority component version target_milestone
Message-ID: <bug-85817-4-msa4VPTgDy@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01894.txt.bz2
Content-length: 518
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target| |x86_64-*-*
Priority|P3 |P1
Component|tree-optimization |middle-end
Version|unknown |9.0
Target Milestone|--- |9.0
>From gcc-bugs-return-605000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:25:46 2018
Return-Path: <gcc-bugs-return-605000-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38770 invoked by alias); 18 May 2018 08:25: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 37733 invoked by uid 48); 18 May 2018 08:24:45 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85819] conversion from __v[48]su to __v[48]sf should use FMA
Date: Fri, 18 May 2018 08:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-85819-4-ZLkdtVlmeW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85819-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85819-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01895.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85819
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-18
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-605001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:26:35 2018
Return-Path: <gcc-bugs-return-605001-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40390 invoked by alias); 18 May 2018 08: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 39822 invoked by uid 48); 18 May 2018 08:26:00 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85826] [9 Regression] ICE in builtin_memref in gcc/gimple-ssa-warn-restrict.c:281 starting with r260280
Date: Fri, 18 May 2018 08:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority target_milestone
Message-ID: <bug-85826-4-lKdUvjdzdF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01896.txt.bz2
Content-length: 345
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85826
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
Target Milestone|--- |9.0
>From gcc-bugs-return-605002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:35:52 2018
Return-Path: <gcc-bugs-return-605002-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 70499 invoked by alias); 18 May 2018 08:35: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 70404 invoked by uid 48); 18 May 2018 08:35:46 -0000
From: "tetra2005 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Fri, 18 May 2018 08:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tetra2005 at gmail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85822-4-m03Vfv4oi5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01897.txt.bz2
Content-length: 471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #6 from Yuri Gribov <tetra2005 at gmail dot com> ---
(In reply to Richard Biener from comment #5)
> Created attachment 44145 [details]
> patch I am testing
>
> I am testing the attached. Please check how negative values can be handled
> correctly or why exactly the handling was wrong.
I think just removing the hunk I mentioned should fix it (I'll test and post to
gcc-patches today hopefully).
>From gcc-bugs-return-605003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:41:40 2018
Return-Path: <gcc-bugs-return-605003-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101483 invoked by alias); 18 May 2018 08:41: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 100786 invoked by uid 48); 18 May 2018 08:41:32 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63185] Improve DSE with branches
Date: Fri, 18 May 2018 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: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-63185-4-wkFPPJLEZg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01898.txt.bz2
Content-length: 1468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #10 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 44146
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44146&action=edit
testresults
Related I checked
Index: gcc/passes.def
===================================================================
--- gcc/passes.def (revision 260317)
+++ gcc/passes.def (working copy)
@@ -209,8 +209,6 @@ along with GCC; see the file COPYING3.
NEXT_PASS (pass_return_slot);
NEXT_PASS (pass_fre);
NEXT_PASS (pass_merge_phi);
- NEXT_PASS (pass_thread_jumps);
- NEXT_PASS (pass_vrp, true /* warn_array_bounds_p */);
NEXT_PASS (pass_chkp_opt);
NEXT_PASS (pass_dce);
NEXT_PASS (pass_stdarg);
@@ -224,6 +222,7 @@ along with GCC; see the file COPYING3.
NEXT_PASS (pass_ch);
NEXT_PASS (pass_lower_complex);
NEXT_PASS (pass_sra);
+ NEXT_PASS (pass_vrp, true /* warn_array_bounds_p */);
/* The dom pass will also resolve all __builtin_constant_p calls
that are still there to 0. This has to be done after some
propagations have already run, but before some more dead code
which as quite some regressions (attached). Ignore any auto-fdo fails.
Will check w/o the removal of pass_thread_jumps.
>From gcc-bugs-return-605004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:43:55 2018
Return-Path: <gcc-bugs-return-605004-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111942 invoked by alias); 18 May 2018 08:43:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111811 invoked by uid 55); 18 May 2018 08:43:50 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85822] [8/9 Regression] Maybe wrong code in VRP since r249150
Date: Fri, 18 May 2018 08: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: wrong-code
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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85822-4-nDx0Zoc0FK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85822-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01899.txt.bz2
Content-length: 773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
--- Comment #7 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 18 May 2018, tetra2005 at gmail dot com wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85822
>
> --- Comment #6 from Yuri Gribov <tetra2005 at gmail dot com> ---
> (In reply to Richard Biener from comment #5)
> > Created attachment 44145 [details]
> > patch I am testing
> >
> > I am testing the attached. Please check how negative values can be handled
> > correctly or why exactly the handling was wrong.
>
> I think just removing the hunk I mentioned should fix it (I'll test and post to
> gcc-patches today hopefully).
Ok, please make sure to say why not doing anything special for negative
numbers is ok.
>From gcc-bugs-return-605005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:50:42 2018
Return-Path: <gcc-bugs-return-605005-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17272 invoked by alias); 18 May 2018 08:50:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 15467 invoked by uid 48); 18 May 2018 08:50:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85825] Incorrect selection of method in template<auto> class specialization.
Date: Fri, 18 May 2018 08: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-85825-4-LuRa6Wo95R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85825-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85825-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01900.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85825
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> ---
This was fixed on trunk by r254843 which makes it a dup of PR 79092.
C++17 bugs are unlikely to get backported to gcc-7-branch, use gcc-8 for better
C++17 support.
*** This bug has been marked as a duplicate of bug 79092 ***
>From gcc-bugs-return-605006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 08:50:42 2018
Return-Path: <gcc-bugs-return-605006-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17325 invoked by alias); 18 May 2018 08:50:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16405 invoked by uid 48); 18 May 2018 08:50:35 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/79092] template<auto>: type ignored if value already instantiated
Date: Fri, 18 May 2018 08: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: 7.0
X-Bugzilla-Keywords: wrong-code
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: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-79092-4-Ivj7vlBDfH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-79092-4@http.gcc.gnu.org/bugzilla/>
References: <bug-79092-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01901.txt.bz2
Content-length: 498
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79092
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christosstratopoulos1@gmail
| |.com
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 85825 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-605007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 10:06:13 2018
Return-Path: <gcc-bugs-return-605007-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98055 invoked by alias); 18 May 2018 10: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 97993 invoked by uid 48); 18 May 2018 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/63185] Improve DSE with branches
Date: Fri, 18 May 2018 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: 5.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-63185-4-F3NEJCMSgG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01902.txt.bz2
Content-length: 1257
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #5)
> Another example:
>
> #include <time.h>
> void f(){
> const int n=1<<14;
> double a[n];
> double b[n];
> double c[n];
> __builtin_memset(a,0,n);
> __builtin_memset(b,0,n);
> __builtin_memset(c,0,n);
> for(int i=0;i<n;++i)
> c[i]=a[i]+b[i];
> time(0);
> }
I guess you meant (notice the bogus memset size above):
#include <time.h>
void f(){
const int n=1<<14;
double a[n];
double b[n];
double c[n];
__builtin_memset(a,0,n*sizeof(double));
__builtin_memset(b,0,n*sizeof(double));
__builtin_memset(c,0,n*sizeof(double));
for(int i=0;i<n;++i)
c[i]=a[i]+b[i];
time(0)
}
> If I make n a constant (using #define), DCE knows that c is not
> ref_may_be_aliased (that test could probably be weakened) and removes almost
> everything. We don't replace alloca_with_align with an array because the
> size is larger than 256 (with a more limited scope the limit would even be
> 25...). DSE is likely confused by the loop. And PRE and others don't know
> that a[i] is always 0. (llvm removes everything but the final call)
>From gcc-bugs-return-605008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 10:12:05 2018
Return-Path: <gcc-bugs-return-605008-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117456 invoked by alias); 18 May 2018 10:12:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117335 invoked by uid 48); 18 May 2018 10:11:55 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Fri, 18 May 2018 10:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66694-4-ytSQ2iinjb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01903.txt.bz2
Content-length: 261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> On darwin the executable hangs due to pr30617.
Commenting the line 118 allows the executable to run and to give a sensible
output.
>From gcc-bugs-return-605009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 10:28:15 2018
Return-Path: <gcc-bugs-return-605009-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91452 invoked by alias); 18 May 2018 10:28:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91381 invoked by uid 48); 18 May 2018 10:28:11 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/63185] Improve DSE with branches
Date: Fri, 18 May 2018 10:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: missed-optimization
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-63185-4-SRMnfWYFW7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63185-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01904.txt.bz2
Content-length: 544
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63185
--- Comment #12 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #11)
> I guess you meant (notice the bogus memset size above):
True. And while it shouldn't make a difference in checking if the stores to c
are dead, it could (but doesn't, symbolic bounds are not so easy to handle)
make a difference for the reads since we could notice that the reads from a and
b are necessarily 0 (thus we write 0 to c[i], thus this loop is a memset, etc).
>From gcc-bugs-return-605010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 10:32:54 2018
Return-Path: <gcc-bugs-return-605010-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94092 invoked by alias); 18 May 2018 10:32:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94055 invoked by uid 48); 18 May 2018 10:32:49 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85537] [7/8/9 Regression] Invalid memory reference at runtime when calling subroutine through procedure pointer
Date: Fri, 18 May 2018 10: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.8.5
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85537-4-j7zRSSOigv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85537-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85537-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01905.txt.bz2
Content-length: 698
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85537
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |janus at gcc dot gnu.org
--- Comment #4 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #2)
> The test works for me with 4.8.5. The change occurred between revisions
> r2370089 (2016-06-04, OK) and r237310 + one patch (2016-06-10, wrong code).
I see runtime segfaults with every gfortran version that I tried, starting from
4.6.
4.4 does not compile the example due to the proc-ptr init.
>From gcc-bugs-return-605011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 10:36:15 2018
Return-Path: <gcc-bugs-return-605011-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104116 invoked by alias); 18 May 2018 10:36: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 104088 invoked by uid 48); 18 May 2018 10:36:10 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85537] [7/8/9 Regression] Invalid memory reference at runtime when calling subroutine through procedure pointer
Date: Fri, 18 May 2018 10: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.8.5
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85537-4-Dij5g4unjP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85537-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85537-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01906.txt.bz2
Content-length: 565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85537
--- Comment #5 from janus at gcc dot gnu.org ---
However I don't see any failures with this variant:
program main
call foo()
contains
subroutine foo()
integer :: a
abstract interface
subroutine ibar()
end subroutine
end interface
procedure(ibar), pointer :: bar_ptr => bar_impl
a = 0
call bar_impl()
call bar_ptr()
end subroutine
subroutine bar_impl()
write (*,*) "foo"
a = a + 1
end subroutine
end program
>From gcc-bugs-return-605012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 11:17:36 2018
Return-Path: <gcc-bugs-return-605012-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8861 invoked by alias); 18 May 2018 11: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 8731 invoked by uid 48); 18 May 2018 11:17:30 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/45582] gcda file names collision when profiling
Date: Fri, 18 May 2018 11:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 4.5.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status
Message-ID: <bug-45582-4-mANGObYA0e@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45582-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45582-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01907.txt.bz2
Content-length: 463
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45582
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
This should help for the scenario:
https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00729.html
>From gcc-bugs-return-605013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 11:17:39 2018
Return-Path: <gcc-bugs-return-605013-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9212 invoked by alias); 18 May 2018 11:17: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 8797 invoked by uid 55); 18 May 2018 11:17:32 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85803] [6/7/8/9 Regression] DSE removes live global store
Date: Fri, 18 May 2018 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: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85803-4-LgWjUST5Ht@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85803-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85803-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01908.txt.bz2
Content-length: 1775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85803
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On Thu, 17 May 2018, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85803
>
> Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |NEW
> Last reconfirmed| |2018-05-17
> Ever confirmed|0 |1
>
> --- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
> (> I think the only in-tree language eventually specifying behavior for stuff
> > like above is Ada - so, any comments / attempts for testcases where we do
> > not follow language specified behavior?
>
> I don't think that the language fully does it, it's quite borderline.
>
> But something changed in DSE yesterday, the following procedure compiled with
> -gnatp -O used to print "SEGV Handler" and now it runs quietly.
>
> with Ada.Text_IO;
>
> procedure p is
>
> procedure leaf is
> type Int_Ptr is access all Integer;
> function n return Int_Ptr is
> begin return null; end;
>
> Data : Int_Ptr := n;
> begin
> Data.all := 0;
> end;
>
> begin
> leaf;
> exception
> when others =>
> Ada.Text_IO.Put_Line ("SEGV Handler");
> end;
I think that's because we now annotate p.leaf.n with malloc() and
then DSE will remove the store as dead as the result of p.leaf.n
doesn't escape. Note this will change again once Pratamesh commits
a followup change (that malloc annotation isn't really useful).
>From gcc-bugs-return-605014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 11:24:00 2018
Return-Path: <gcc-bugs-return-605014-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17584 invoked by alias); 18 May 2018 11:24: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 17388 invoked by uid 48); 18 May 2018 11:23:55 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38087] g++ accepts invalid destructor call
Date: Fri, 18 May 2018 11:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: see_also short_desc
Message-ID: <bug-38087-4-v5JI6xyEqX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38087-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38087-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01909.txt.bz2
Content-length: 2433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38087
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
See Also| |https://gcc.gnu.org/bugzill
| |a/show_bug.cgi?id=12333
Summary|Pseudo destructor call |g++ accepts invalid
| |destructor call
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> Redoing lost comments:
>
> https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01624.html
>
> Eric Gallager <egallager at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |WAITING
> Last reconfirmed| |2017-08-14
> CC| |egallager at gcc dot gnu.org
> Ever confirmed|0 |1
>
> --- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
> (In reply to Andrew Pinski from comment #1)
> > I still think this is valid code ... There are defect reports against this
> > area too.
>
> Which ones do you mean?
>
> https://gcc.gnu.org/ml/gcc-bugs/2017-08/msg01637.html
>
> Jonathan Wakely <redi at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Keywords| |accepts-invalid
> Status|WAITING |NEW
>
> --- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> There's https://wg21.link/cwg555 but I don't think it changes anything here.
>
> [expr.pseudo] definitely doesn't apply, as that only applies to non-class
> types. (The bug title is wrong for the same reason, this is a destructor
> call, not a pseudo destructor call.)
>
> The current wording in [basic.lookup.classref] says "At least one of the
> lookups shall find a name that refers to cv T." The object expression has
> type C, but the lookup result for B does not find that type, so the code is
> invalid.
Retitling then.
>From gcc-bugs-return-605015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 11:32:15 2018
Return-Path: <gcc-bugs-return-605015-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29361 invoked by alias); 18 May 2018 11:32:14 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29302 invoked by uid 48); 18 May 2018 11:32:06 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85827] New: false positive for -Wunused-but-set-variable because of constexpr-if
Date: Fri, 18 May 2018 11:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kretz at kde dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01910.txt.bz2
Content-length: 1519
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85827
Bug ID: 85827
Summary: false positive for -Wunused-but-set-variable because
of constexpr-if
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kretz at kde dot org
Target Milestone: ---
Testcase `-std=c++17 -Wall` (cf. https://godbolt.org/g/kfgN2V):
template <int N> int f()
{
constexpr bool _1 = N == 1;
constexpr bool _2 = N == 2;
constexpr bool _3 = N == 3;
if constexpr (_1) {
return 5;
} else if constexpr (_2) {
return 1;
} else if constexpr (_3) {
return 7;
}
}
int a() {
return f<1>();
}
int b() {
return f<2>();
}
int c() {
return f<3>();
}
Yes, I see how one can argue that _2 and _3 are unused in f<1>. However, this
makes use of constexpr-if cumbersome. E.g. when a variable is required in all
but one branch, then it'll warn for specializations that take this one branch.
So you'll have to reorder the code such that the variable is only defined
inside the else branch where all the other branches are handled. But what if
you have two variables and their uses are disjunct? This leads to code
duplication, just for silencing the warning.
I believe, -Wunused-but-set-variable needs to consider all constexpr branches
to be useful here.
>From gcc-bugs-return-605016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 11:39:10 2018
Return-Path: <gcc-bugs-return-605016-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12348 invoked by alias); 18 May 2018 11:39:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 12303 invoked by uid 48); 18 May 2018 11:39:05 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85827] false positive for -Wunused-but-set-variable because of constexpr-if
Date: Fri, 18 May 2018 11:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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:
Message-ID: <bug-85827-4-n0RPVp3zGr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01911.txt.bz2
Content-length: 149
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85827
--- Comment #1 from Matthias Kretz <kretz at kde dot org> ---
Same issue for -Wunused-variable
>From gcc-bugs-return-605017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:06:12 2018
Return-Path: <gcc-bugs-return-605017-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6291 invoked by alias); 18 May 2018 12: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 6212 invoked by uid 48); 18 May 2018 12:06:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris SPARC when parsing a simple character class
Date: Fri, 18 May 2018 12: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: 4.9.2
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: cc
Message-ID: <bug-85824-4-SOEc9XTMZF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01912.txt.bz2
Content-length: 2218
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |timshen at gcc dot gnu.org
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Wanying Luo from comment #0)
> When _M_transform() calls strxfrm() and gets -1 when converting 0x80 under
> the UTF-8 locale on Solaris SPARC, it simply assigns -1 to __res of type
> size_t which creates a very large number. This causes __ret.append(__c,
> __res) to crash. I think it would be nice if the code checks errno and
> issues a better error message than the one above.
N.B. it doesn't just crash, it throws an exception because it can't append
4294967295 bytes to a std::string. Any fix to check errno in
collate<char>::do_transform is still going to involve throwing an exception,
just a slightly different one.
The real problem is that std::regex wants to build a cache of every value from
CHAR_MIN to CHAR_MAX, to decide if it matches the bracket expression "[0-9]".
If calling strxfrm on any 8-bit char value produces an error then we're going
to get an exception. I think something in the regex compiler (maybe in
transform_primary) needs to handle those exceptions (and either decide the
characters that produce errors do not match, or maybe disable the cache?)
Tim, I'll take care of checking errno in collate<>::_M_transform but could you
advise what to do about the regex compiler? Maybe:
--- a/libstdc++-v3/include/bits/regex.h
+++ b/libstdc++-v3/include/bits/regex.h
@@ -257,7 +257,11 @@ _GLIBCXX_BEGIN_NAMESPACE_CXX11
const __ctype_type& __fctyp(use_facet<__ctype_type>(_M_locale));
std::vector<char_type> __s(__first, __last);
__fctyp.tolower(__s.data(), __s.data() + __s.size());
- return this->transform(__s.data(), __s.data() + __s.size());
+ __try {
+ return this->transform(__s.data(), __s.data() + __s.size());
+ } catch(const std::runtime_error&) {
+ return string_type();
+ }
}
/**
>From gcc-bugs-return-605018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:09:47 2018
Return-Path: <gcc-bugs-return-605018-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43203 invoked by alias); 18 May 2018 12: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 43031 invoked by uid 48); 18 May 2018 12:09:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/38087] g++ accepts invalid destructor call
Date: Fri, 18 May 2018 12:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.4.0
X-Bugzilla-Keywords: accepts-invalid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cf_reconfirmed_on
Message-ID: <bug-38087-4-eR77Vxc2wG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-38087-4@http.gcc.gnu.org/bugzilla/>
References: <bug-38087-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01913.txt.bz2
Content-length: 797
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=38087
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed|2017-08-17 00:00:00 |2018-5-18
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Clang gives this error:
d.cc:4:11: error: destructor type 'B' in object destruction expression does not
match the type 'C' of the object being destroyed
this->~B();
^
d.cc:1:7: note: type 'B' is declared here
class B { };
^
1 error generated.
And EDG gives this error:
"d.cc", line 4: error: invalid destructor name for type "C"
this->~B();
^
1 error detected in the compilation of "d.cc".
>From gcc-bugs-return-605019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:10:22 2018
Return-Path: <gcc-bugs-return-605019-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44292 invoked by alias); 18 May 2018 12:10: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 44166 invoked by uid 48); 18 May 2018 12:10:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85827] false positive for -Wunused-but-set-variable because of constexpr-if
Date: Fri, 18 May 2018 12: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85827-4-qst7NshmCj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01914.txt.bz2
Content-length: 462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85827
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-18
Ever confirmed|0 |1
>From gcc-bugs-return-605020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:29:30 2018
Return-Path: <gcc-bugs-return-605020-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109932 invoked by alias); 18 May 2018 12:29: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 109842 invoked by uid 48); 18 May 2018 12:29:25 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85827] false positive for -Wunused-but-set-variable because of constexpr-if
Date: Fri, 18 May 2018 12:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
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-85827-4-07b8XPdA2P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01915.txt.bz2
Content-length: 425
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85827
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
I think that's going to be hard. The same issue always existed with macros. The
whole point of "if constexpr" is not to look at the other branches, as they may
not even compile. Sure, some minimal "safe" attempt at looking at those
branches would be possible, but I am not sure it is worth the trouble.
>From gcc-bugs-return-605021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:31:42 2018
Return-Path: <gcc-bugs-return-605021-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115757 invoked by alias); 18 May 2018 12: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 115671 invoked by uid 55); 18 May 2018 12:31:38 -0000
From: "prathamesh3492 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85817] [9 Regression] ICE in expand_call at gcc/calls.c:4291
Date: Fri, 18 May 2018 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
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-85817-4-XA7Rs1Ynca@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85817-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01916.txt.bz2
Content-length: 787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85817
--- Comment #4 from prathamesh3492 at gcc dot gnu.org ---
Author: prathamesh3492
Date: Fri May 18 12:31:04 2018
New Revision: 260358
URL: https://gcc.gnu.org/viewcvs?rev=260358&root=gcc&view=rev
Log:
2018-05-18 Prathamesh Kulkarni <prathamesh.kulkarni@linaro.org>
PR middle-end/85817
* ipa-pure-const.c (malloc_candidate_p): Remove the check integer_zerop
for retval and return false if all args to phi are zero.
testsuite/
* gcc.dg/tree-ssa/pr83648.c: Change scan-tree-dump to
scan-tree-dump-not for h.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/ipa-pure-const.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-ssa/pr83648.c
>From gcc-bugs-return-605022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:45:47 2018
Return-Path: <gcc-bugs-return-605022-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25942 invoked by alias); 18 May 2018 12:45: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 25834 invoked by uid 48); 18 May 2018 12:45:42 -0000
From: "soap at gentoo dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85828] New: std::shuffle tries to swap element with itself
Date: Fri, 18 May 2018 12:45: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: soap at gentoo dot org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01917.txt.bz2
Content-length: 1047
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85828
Bug ID: 85828
Summary: std::shuffle tries to swap element with itself
Product: gcc
Version: 7.3.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: soap at gentoo dot org
Target Milestone: ---
This bug is related to a previous one in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59603. For a full description, see
https://stackoverflow.com/questions/22915325/avoiding-self-assignment-in-stdshuffle.
The problem boils down to the fact that in std::shuffle, self-assignment in
some std::swap(x, x) will happen eventually. This will cause an "Error: attempt
to self move assign." failure to occur and kill the program when compiled in
debug mode. A chat on IRC with Jonathan Wakely confirmed that this is an
implementation bug, and that the likely correct fix for this is to avoid
self-swap in std::shuffle.
>From gcc-bugs-return-605024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:47:34 2018
Return-Path: <gcc-bugs-return-605024-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30589 invoked by alias); 18 May 2018 12: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 30343 invoked by uid 48); 18 May 2018 12:47:30 -0000
From: "kretz at kde dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85827] false positive for -Wunused-but-set-variable because of constexpr-if
Date: Fri, 18 May 2018 12:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: diagnostic
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-85827-4-LX2VmASLBY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85827-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01919.txt.bz2
Content-length: 717
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85827
--- Comment #3 from Matthias Kretz <kretz at kde dot org> ---
But macros are different. They remove the code before the C++ parser sees it
(at least as-if). One great improvement of constexpr-if over macros is that all
the other branches are parsed and their syntax checked. E.g. it requires the
mentioned names to exist. This doesn't compile (cf.
https://godbolt.org/g/iCRPDv):
#ifdef HAVE_FOO
constexpr bool have_foo = true;
void foo();
#else
constexpr bool have_foo = false;
#endif
void f() {
if constexpr (have_foo) {
foo();
}
}
So, the frontend parses all branches anyway. It should be able to see that _2
and _3 are referenced in f<1>().
>From gcc-bugs-return-605023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:47:11 2018
Return-Path: <gcc-bugs-return-605023-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29474 invoked by alias); 18 May 2018 12:47:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 29414 invoked by uid 55); 18 May 2018 12:47:05 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/84846] GCOV intermediate format improvements
Date: Fri, 18 May 2018 12:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 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:
Message-ID: <bug-84846-4-VLw5KM7toO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01918.txt.bz2
Content-length: 854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84846
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Fri May 18 12:46:32 2018
New Revision: 260359
URL: https://gcc.gnu.org/viewcvs?rev=260359&root=gcc&view=rev
Log:
Print working directory to gcov files (PR gcov-profile/84846).
2018-05-18 Martin Liska <mliska@suse.cz>
PR gcov-profile/84846
* coverage.c (coverage_init): Write PWD to .gcno file.
* doc/gcov.texi: Document how working directory is printed.
* gcov-dump.c (dump_gcov_file): Print PWD.
* gcov.c (output_intermediate_file): Likewise.
(read_graph_file): Read PWD string.
(output_lines): Print PWD.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/coverage.c
trunk/gcc/doc/gcov.texi
trunk/gcc/gcov-dump.c
trunk/gcc/gcov.c
>From gcc-bugs-return-605025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 12:53:02 2018
Return-Path: <gcc-bugs-return-605025-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38449 invoked by alias); 18 May 2018 12:53: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 38357 invoked by uid 48); 18 May 2018 12:52:58 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85828] std::shuffle tries to swap element with itself
Date: Fri, 18 May 2018 12:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: 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-85828-4-4y6eoDe6FG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01920.txt.bz2
Content-length: 1191
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85828
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-18
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> ---
#include <vector>
#include <random>
#include <algorithm>
struct Type {
std::vector<int> ints;
};
int main() {
std::vector<Type> intVectors = {{{1}}, {{1, 2}}};
std::shuffle(intVectors.begin(), intVectors.end(), std::mt19937());
}
$ g++ self.cc -D_GLIBCXX_DEBUG
$ ./a.out
/usr/include/c++/7/debug/safe_container.h:83:
Error: attempt to self move assign.
Objects involved in the operation:
sequence "this" @ 0x0x12e7ee8 {
type = __gnu_debug::_Safe_container<std::__debug::vector<int,
std::allocator<int> >, std::allocator<int>, __gnu_debug::_Safe_sequence, true>;
}
Aborted (core dumped)
>From gcc-bugs-return-605026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 13:07:10 2018
Return-Path: <gcc-bugs-return-605026-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23604 invoked by alias); 18 May 2018 13:07:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16705 invoked by uid 55); 18 May 2018 13:07:04 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/84846] GCOV intermediate format improvements
Date: Fri, 18 May 2018 13:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: 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:
Message-ID: <bug-84846-4-VmH4mwL6LJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01921.txt.bz2
Content-length: 817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84846
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Fri May 18 13:06:31 2018
New Revision: 260361
URL: https://gcc.gnu.org/viewcvs?rev=260361&root=gcc&view=rev
Log:
gcov: add new option -t that prints output to stdout (PR gcov-profile/84846).
2018-05-18 Martin Liska <mliska@suse.cz>
PR gcov-profile/84846
* gcov.c (print_usage): Add new -t option.
(process_args): Handle the option.
(generate_results): Use stdout as output when requested by
the option.
2018-05-18 Martin Liska <mliska@suse.cz>
PR gcov-profile/84846
* doc/gcov.texi: Document -t option of gcov tool.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/doc/gcov.texi
trunk/gcc/gcov.c
>From gcc-bugs-return-605027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 13:09:15 2018
Return-Path: <gcc-bugs-return-605027-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94371 invoked by alias); 18 May 2018 13:09: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 87956 invoked by uid 55); 18 May 2018 13:09:09 -0000
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85656] gcc.dg/ipa/ipa-icf-38.c FAILs
Date: Fri, 18 May 2018 13:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: ipa
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: WAITING
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-85656-4-QPlYIS3tCs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85656-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85656-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01922.txt.bz2
Content-length: 3432
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85656
--- Comment #7 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-Bielefeld.DE> ---
> --- Comment #6 from Martin Liška <marxin at gcc dot gnu.org> ---
[...]
> So can you please debug why we go into following branch:
> 1277 if (!create_wrapper
> 1278 && !alias->call_for_symbol_and_aliases
> (cgraph_node::has_thunk_p,
> 1279 NULL, true)
> 1280 && !alias->can_remove_if_no_direct_calls_p ())
> 1281 {
> 1282 if (dump_file)
> 1283 fprintf (dump_file, "Not unifying; can not make wrapper and
> "
> 1284 "function has other uses than direct calls\n\n");
> 1285 return false;
> 1286 }
>
> I'm curious why can_remove_if_no_direct_calls_p returns false.
It took me a bit figuring out which of the two lto1 invocations was the
interesting one, then rebuilding with -g3 -O0 to be able to see anything
useful in gdb.
Here's what I found:
ipa-icf.c:1280 (sem_function::merge)
&& !alias->can_remove_if_no_direct_calls_p ())
cgraph.c:2848 (cgraph_node::can_remove_if_no_direct_calls_p)
return !call_for_symbol_and_aliases (nonremovable_p, NULL, true);
cgraph.h:3213 (cgraph_node::call_for_symbol_and_aliases)
if (callback (this, data))
return true;
cgraph.c:2829 (nonremovable_p)
return !node->can_remove_if_no_direct_calls_and_refs_p ();
cgraph.h:2924 (cgraph_node::can_remove_if_no_direct_calls_and_refs_p)
/* Only COMDAT functions can be removed if externally visible. */
if (externally_visible
&& (!DECL_COMDAT (decl)
|| forced_by_abi
|| used_from_object_file_p ()))
return false;
externally_visible = 1 and If I'm not mistaken, decl is not comdat, thus
return false:
<function_decl fa527880 bar
type <function_type fa524ea0
type <integer_type faefb3c0 int public SI
size <integer_cst fa405910 constant 32>
unit-size <integer_cst fa405924 constant 4>
align:32 warn_if_not_align:0 symtab:0 alias-set 1 canonical-type
faefb3c0 precision:32 min <integer_cst fa405af0 -2147483648> max <integer_cst
fa405b04 2147483647>
pointer_to_this <pointer_type fa419060>>
QI
size <integer_cst fa405a14 constant 8>
unit-size <integer_cst fa405a28 constant 1>
align:8 warn_if_not_align:0 symtab:0 alias-set -1 structural-equality
arg-types <tree_list fa41c000 value <void_type faefb9c0 void>>
pointer_to_this <pointer_type fa524120>>
readonly addressable nothrow public static function-specific-target
function-specific-opt uninlinable QI
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.dg/ipa/ipa-icf-38a.c:6:5 align:8
warn_if_not_align:0 context <translation_unit_decl fa40f63c
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.dg/ipa/ipa-icf-38a.c>
attributes <tree_list fa526390
purpose <identifier_node fa5239f4 noinline>> initial <block fa52a0e0>
result <result_decl fa40f6d4 D.4264 type <integer_type faefb3c0 int>
ignored SI
/vol/gcc/src/hg/trunk/local/gcc/testsuite/gcc.dg/ipa/ipa-icf-38a.c:6:5 size
<integer_cst fa405910 32> unit-size <integer_cst fa405924 4>
align:32 warn_if_not_align:0 context <function_decl fa527880 bar>>
struct-function fa52b1a0>
>From gcc-bugs-return-605028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 13:14:04 2018
Return-Path: <gcc-bugs-return-605028-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 648 invoked by alias); 18 May 2018 13:14:04 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 539 invoked by uid 48); 18 May 2018 13:13:59 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug gcov-profile/84846] GCOV intermediate format improvements
Date: Fri, 18 May 2018 13:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: gcov-profile
X-Bugzilla-Version: unknown
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-84846-4-yKeimoYHQn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01923.txt.bz2
Content-length: 448
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84846
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Martin Liška <marxin at gcc dot gnu.org> ---
Implemented on trunk.
>From gcc-bugs-return-605029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 13:36:53 2018
Return-Path: <gcc-bugs-return-605029-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35784 invoked by alias); 18 May 2018 13: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 35725 invoked by uid 48); 18 May 2018 13:36:49 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] New: [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Fri, 18 May 2018 13:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcctarget
Message-ID: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01924.txt.bz2
Content-length: 780
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
Bug ID: 85829
Summary: [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were
disabled for Haswell and newer processors
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: hubicka at ucw dot cz
Target Milestone: ---
Target: x86_64-*-*, i?86-*-*
r254152 disabled PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell
and newer processors. r258972 restored them for skylake-avx512. We may need
them back for all Haswell and newer processors.
>From gcc-bugs-return-605030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 14:42:44 2018
Return-Path: <gcc-bugs-return-605030-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112806 invoked by alias); 18 May 2018 14:42:44 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 112729 invoked by uid 55); 18 May 2018 14:42:39 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Fri, 18 May 2018 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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-V2lH6Usow4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01925.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #31 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Thu, May 17, 2018 at 05:37:51AM +0000, janus at gcc dot gnu.org wrote:
>
> > The order of the evaluation of ping() and pong() is
> > not specified by the Fortran standard.
>
> This PR is not about reordering, but about short-circuiting.
>
AFAICT this PR is about a function with side-effects,
and re-ordering can have an potentially undesirable
result.
>From gcc-bugs-return-605031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 15:08:29 2018
Return-Path: <gcc-bugs-return-605031-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61860 invoked by alias); 18 May 2018 15:08:29 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 61796 invoked by uid 48); 18 May 2018 15:08:23 -0000
From: "snowfed at mail dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80931] ICE on move_alloc in gimplify_expr, at gimplify.c:11335
Date: Fri, 18 May 2018 15: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: 6.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: snowfed at mail dot ru
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80931-4-wwl3Rc9pim@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80931-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80931-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01926.txt.bz2
Content-length: 925
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80931
snowfed <snowfed at mail dot ru> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |snowfed at mail dot ru
--- Comment #3 from snowfed <snowfed at mail dot ru> ---
Just stumbled upon this bug as well.
Here is my minimal example (slightly smaller than Tiziano's).
module buggy
implicit none
type type_t
character(:), dimension(:), allocatable :: characters
contains
procedure :: mover
end type type_t
contains
subroutine mover (self)
implicit none
class(type_t), intent(in out) :: self
character(:), dimension(:), allocatable :: new
allocate(character(5) :: new(2018))
call move_alloc(new, self%characters)
end subroutine mover
end module buggy
>From gcc-bugs-return-605032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 15:11:50 2018
Return-Path: <gcc-bugs-return-605032-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68140 invoked by alias); 18 May 2018 15:11:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 67991 invoked by uid 48); 18 May 2018 15:11:45 -0000
From: "ams at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82089] emit_cstore sign-extends BImode result for STORE_FLAG_VALUE == 1
Date: Fri, 18 May 2018 15:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ams at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-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-82089-4-x7LilCz8IG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82089-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82089-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01927.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82089
Andrew Stubbs <ams at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ams at gcc dot gnu.org
--- Comment #5 from Andrew Stubbs <ams at gcc dot gnu.org> ---
Any reason not to get this committed?
>From gcc-bugs-return-605033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 15:39:36 2018
Return-Path: <gcc-bugs-return-605033-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74484 invoked by alias); 18 May 2018 15:39:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 74241 invoked by uid 48); 18 May 2018 15:39:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85828] std::shuffle tries to swap element with itself
Date: Fri, 18 May 2018 15: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: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85828-4-NWjLkwuXdc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85828-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85828-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01928.txt.bz2
Content-length: 1350
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85828
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is ugly but it works:
--- a/libstdc++-v3/include/bits/stl_algo.h
+++ b/libstdc++-v3/include/bits/stl_algo.h
@@ -3827,7 +3827,9 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
if ((__urange % 2) == 0)
{
__distr_type __d{0, 1};
- std::iter_swap(__i++, __first + __d(__g));
+ if (__d(__g) == 0)
+ std::iter_swap(__i, __first);
+ ++__i;
}
// Now we know that __last - __i is even, so we do the rest in pairs,
@@ -3841,8 +3843,14 @@ _GLIBCXX_BEGIN_NAMESPACE_VERSION
const pair<__uc_type, __uc_type> __pospos =
__gen_two_uniform_ints(__swap_range, __swap_range + 1, __g);
- std::iter_swap(__i++, __first + __pospos.first);
- std::iter_swap(__i++, __first + __pospos.second);
+ _RandomAccessIterator __pos1 = __first + __pospos.first;
+ _RandomAccessIterator __pos2 = __first + __pospos.second;
+ if (__i != __pos1)
+ std::iter_swap(__i, __pos1);
+ ++__i;
+ if (__i != __pos2)
+ std::iter_swap(__i, __pos2);
+ ++__i;
}
return;
I think we also want to remove the __glibcxx_check_self_move_assign assertions
completely.
>From gcc-bugs-return-605034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 15:43:45 2018
Return-Path: <gcc-bugs-return-605034-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81366 invoked by alias); 18 May 2018 15:43: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 81343 invoked by uid 55); 18 May 2018 15:43:41 -0000
From: "cesar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85782] acc loops with continue statements ICE in c++
Date: Fri, 18 May 2018 15:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cesar at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: cesar at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85782-4-UCnEj81SBz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01929.txt.bz2
Content-length: 783
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85782
--- Comment #1 from cesar at gcc dot gnu.org ---
Author: cesar
Date: Fri May 18 15:43:09 2018
New Revision: 260369
URL: https://gcc.gnu.org/viewcvs?rev=260369&root=gcc&view=rev
Log:
PR c++/85782
gcc/cp/
* cp-gimplify.c (cp_genericize_r): Call genericize_omp_for_stmt for
OACC_LOOPs.
gcc/testsuite/
* c-c++-common/goacc/pr85782.c: New test.
libgomp/
* testsuite/libgomp.oacc-c-c++-common/pr85782.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/goacc/pr85782.c
trunk/libgomp/testsuite/libgomp.oacc-c-c++-common/pr85782.c
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-gimplify.c
trunk/gcc/testsuite/ChangeLog
trunk/libgomp/ChangeLog
>From gcc-bugs-return-605035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 15:47:32 2018
Return-Path: <gcc-bugs-return-605035-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85969 invoked by alias); 18 May 2018 15: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 85903 invoked by uid 55); 18 May 2018 15:47:28 -0000
From: "cesar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85782] acc loops with continue statements ICE in c++
Date: Fri, 18 May 2018 15:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: openacc
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cesar at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: cesar at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85782-4-MsMiHuuiJ5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85782-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85782-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01930.txt.bz2
Content-length: 1000
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85782
--- Comment #2 from cesar at gcc dot gnu.org ---
Author: cesar
Date: Fri May 18 15:46:56 2018
New Revision: 260370
URL: https://gcc.gnu.org/viewcvs?rev=260370&root=gcc&view=rev
Log:
PR c++/85782
Backport from mainline
2018-05-18 Cesar Philippidis <cesar@codesourcery.com>
PR c++/85782
gcc/cp/
* cp-gimplify.c (cp_genericize_r): Call genericize_omp_for_stmt for
OACC_LOOPs.
gcc/testsuite/
* c-c++-common/goacc/pr85782.c: New test.
libgomp/
* testsuite/libgomp.oacc-c-c++-common/pr85782.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/c-c++-common/goacc/pr85782.c
branches/gcc-8-branch/libgomp/testsuite/libgomp.oacc-c-c++-common/pr85782.c
Modified:
branches/gcc-8-branch/gcc/cp/ChangeLog
branches/gcc-8-branch/gcc/cp/cp-gimplify.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/libgomp/ChangeLog
>From gcc-bugs-return-605036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 15:58:42 2018
Return-Path: <gcc-bugs-return-605036-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36394 invoked by alias); 18 May 2018 15:58: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 36381 invoked by uid 48); 18 May 2018 15:58:38 -0000
From: "munroesj at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85830] New: vec_popcntd is improperly defined in altivec.h
Date: Fri, 18 May 2018 15:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: munroesj at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-85830-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01931.txt.bz2
Content-length: 2037
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85830
Bug ID: 85830
Summary: vec_popcntd is improperly defined in altivec.h
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: munroesj at gcc dot gnu.org
Target Milestone: ---
Created attachment 44147
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44147&action=edit
compile test case for vec_popcntd.
Altivec.h should define either the generic vec_popcnt or the specific
vec_vpopcntd.
In GCC-8.1 altivec.h defines the expected vec_popcnt (as defined in the ABI)
and the PIM style specific vec_vpopcntd. these are OK.
However it also defines vec_popcntd which generates __builtin_vec_vpopcntud.
This gives compile errors.
vector unsigned long long
__test_popcntd_2 (vector unsigned long long a)
{
return (vec_popcntd (a));
}
vector unsigned int
__test_popcntw_2 (vector unsigned int a)
{
return (vec_popcntw (a));
}
vec_popcnt-2.c: In function ‘__test_popcntd_2’:
vec_popcnt-2.c:31:3: error: invalid parameter combination for AltiVec intrinsic
‘__builtin_vec_vpopcntud’
return (vec_popcntd (a));
^~~~~~
vec_popcnt-2.c: In function ‘__test_popcntw_2’:
vec_popcnt-2.c:37:3: error: invalid parameter combination for AltiVec intrinsic
‘__builtin_vec_vpopcntuw’
return (vec_popcntw (a));
^~~~~~
There are two problems here;
1) You would expect a __builtin_vec_vpopcntud to accept a unsigned input and it
does not. I am not sure what it does accept.
2) The vec_popcntd define fits neither the ABI generic specific (vec_popcnt())
or the old PIM specific style (vec_vpopcntd() which follows the PowerISA
mnemonic.
This 3rd style should be removed from altivec.h ( vec_popcntb, vec_popcnth,
vec_popcntw, vec_popcntd)
While retaining the ABI generic and PIM specific definitions.
>From gcc-bugs-return-605037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:14:43 2018
Return-Path: <gcc-bugs-return-605037-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74327 invoked by alias); 18 May 2018 16:14: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 74267 invoked by uid 55); 18 May 2018 16:14:37 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85098] undefined reference to std::regex::extended
Date: Fri, 18 May 2018 16: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: 7.3.1
X-Bugzilla-Keywords: link-failure
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-85098-4-tjDSaHj02A@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85098-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85098-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01932.txt.bz2
Content-length: 1419
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85098
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Fri May 18 16:14:04 2018
New Revision: 260371
URL: https://gcc.gnu.org/viewcvs?rev=260371&root=gcc&view=rev
Log:
PR libstdc++/85098 add missing definitions for static constants
In C++11 and C++14 any odr-use of these constants requires a definition
at namespace-scope. In C++17 they are implicitly inline and so the
namespace-scope redeclarations are redundant (and allowing them is
deprecated).
PR libstdc++/85098
* include/bits/regex.h [__cplusplus < 201703L] (basic_regex::icase)
(basic_regex::nosubs, basic_regex::optimize, basic_regex::collate)
(basic_regex::ECMAScript, basic_regex::basic, basic_regex::extended)
(basic_regex::awk, basic_regex::grep, basic_regex::egrep): Add
definitions.
* include/bits/regex_automaton.h (_NFA::_M_insert_state): Adjust
whitespace.
* include/bits/regex_compiler.tcc (__INSERT_REGEX_MATCHER): Add
braces around body of do-while.
* testsuite/28_regex/basic_regex/85098.cc: New
Added:
trunk/libstdc++-v3/testsuite/28_regex/basic_regex/85098.cc
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/regex.h
trunk/libstdc++-v3/include/bits/regex_automaton.h
trunk/libstdc++-v3/include/bits/regex_compiler.tcc
>From gcc-bugs-return-605038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:15:55 2018
Return-Path: <gcc-bugs-return-605038-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80744 invoked by alias); 18 May 2018 16:15:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80594 invoked by uid 48); 18 May 2018 16:15:45 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85098] undefined reference to std::regex::extended
Date: Fri, 18 May 2018 16:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: link-failure
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-85098-4-1zBZxUvSSQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85098-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85098-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01933.txt.bz2
Content-length: 185
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85098
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed on trunk but I'll keep this open as I plan to backport it.
>From gcc-bugs-return-605039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:16:41 2018
Return-Path: <gcc-bugs-return-605039-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81882 invoked by alias); 18 May 2018 16: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 81797 invoked by uid 48); 18 May 2018 16:16:36 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85831] New: <stdexcept> types should have move constructors and move assignment operators
Date: Fri, 18 May 2018 16: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: 8.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85831-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01934.txt.bz2
Content-length: 1179
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85831
Bug ID: 85831
Summary: <stdexcept> types should have move constructors and
move assignment operators
Product: gcc
Version: 8.1.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
Target Milestone: ---
The standard says:
namespace std {
class logic_error : public exception {
public:
explicit logic_error(const string& what_arg);
explicit logic_error(const char* what_arg);
};
}
The lack of user-declared special members means that a move constructor and
move assignment operator should be implicitly declared.
But we define:
class logic_error : public exception
{
[...]
virtual ~logic_error() _GLIBCXX_TXN_SAFE_DYN _GLIBCXX_USE_NOEXCEPT;
[...]
};
The user-declared destructor means there is no move constructor or move
assignment operator.
(The user-defined destructor is the key function and ensures the vtable and
RTTI are only emitted in the library, not in every TU).
>From gcc-bugs-return-605040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:18:19 2018
Return-Path: <gcc-bugs-return-605040-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85857 invoked by alias); 18 May 2018 16:18:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85813 invoked by uid 48); 18 May 2018 16:18:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85298] relocation errors on windows when linking C code to libstdc++ built with weakrefs
Date: Fri, 18 May 2018 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: 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: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85298-4-KbMibCYlcS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85298-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85298-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01935.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85298
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-18
CC| |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-605041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:32:26 2018
Return-Path: <gcc-bugs-return-605041-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7937 invoked by alias); 18 May 2018 16:32:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 7890 invoked by uid 48); 18 May 2018 16:32:21 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85832] New: [AVX512] possible shorter code when comparing with vector of zeros
Date: Fri, 18 May 2018 16:32: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: 7.3.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-85832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01936.txt.bz2
Content-length: 1182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85832
Bug ID: 85832
Summary: [AVX512] possible shorter code when comparing with
vector of zeros
Product: gcc
Version: 7.3.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: ---
Consider this simple function, which yields mask fors non-zero elements:
---cat cmp.c---
#include <immintrin.h>
int fun(__m512i x) {
return _mm512_cmpeq_epi32_mask(x, _mm512_setzero_si512());
}
---eof
$ gcc --version
gcc (Debian 7.3.0-16) 7.3.0
$ gcc -O2 -S -mavx512f cmp.c && cat cmp.s
fun:
vpxord %zmm1, %zmm1, %zmm1 # <<< HERE
vpcmpeqd %zmm1, %zmm0, %k1 # <<<
kmovw %k1, %eax
vzeroupper
ret
Also 8.1.0 generates the same code (as checked on godbolt.org).
The pair of instructions VPXORD/VPCMPEQD can be replaced with single
VPTESTMD %zmm0, %zmm0. VPTESTMD performs k1 := zmm0 AND zmm0, so to
compare zmm0 with zeros it's sufficient.
>From gcc-bugs-return-605042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:47:24 2018
Return-Path: <gcc-bugs-return-605042-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60473 invoked by alias); 18 May 2018 16:47: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 60423 invoked by uid 48); 18 May 2018 16:47:20 -0000
From: "wojciech_mula at poczta dot onet.pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85833] New: [AVX512] use mask registers instructions instead of scalar code
Date: Fri, 18 May 2018 16:47: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: 7.3.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-85833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01937.txt.bz2
Content-length: 1695
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85833
Bug ID: 85833
Summary: [AVX512] use mask registers instructions instead of
scalar code
Product: gcc
Version: 7.3.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: ---
There is a simple function, which checks if there is any non-zero element
in a vector:
---ktest.c---
#include <immintrin.h>
int anynonzero_epi32(__m512i x) {
const __m512i zero = _mm512_setzero_si512();
const __mmask16 mask = _mm512_cmpneq_epi32_mask(x, zero);
return mask != 0;
}
---eof---
$ gcc --version
gcc (Debian 7.3.0-16) 7.3.0
$ gcc -O2 -S -mavx512f ktest.c && cat ktest.s
anynonzero_epi32:
vpxord %zmm1, %zmm1, %zmm1
vpcmpd $4, %zmm1, %zmm0, %k1
kmovw %k1, %eax # <<< HERE
testw %ax, %ax #
setne %al
movzbl %al, %eax
vzeroupper
ret
The problem is that GCC copies content of the mask register k1 into
GPR (using KMOV instruction), and then perform test. AVX512F has got
instruction KTEST kx, ky which sets ZF and CF:
ZF = (kx AND ky) == 0
CF = (kx AND NOT ky) == 0
In this case we might use KTEST k1, k1 to set ZF when k1 == 0.
The procedure might be then compiled as:
anynonzero_epi32:
vpxord %zmm1, %zmm1, %zmm1
vpcmpd $4, %zmm1, %zmm0, %k1
xor %eax, %eax #
ktestw %k1, %k1 #
setne %al #
vzeroupper
ret
>From gcc-bugs-return-605043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:49:40 2018
Return-Path: <gcc-bugs-return-605043-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64271 invoked by alias); 18 May 2018 16:49:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64233 invoked by uid 48); 18 May 2018 16:49:36 -0000
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Fri, 18 May 2018 16:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85829-4-MlVFgrBRXq@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01938.txt.bz2
Content-length: 933
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-18
CC| |hubicka at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
It would be nice to have an examples where they are needed. The motivation to
disable them was optimization manuals claiming that Haswell+ handles partial
reg stalls better than old cores.
Also PARTIAL_REG_DEPENDENCY does not really fit the hardware design of cores
which are partial reg stall architecture. So in theory if we enable something
it should be the PARTIAL_REG_STALL flag.
>From gcc-bugs-return-605044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 16:57:47 2018
Return-Path: <gcc-bugs-return-605044-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91368 invoked by alias); 18 May 2018 16:57: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 91326 invoked by uid 48); 18 May 2018 16:57:42 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Fri, 18 May 2018 16:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85829-4-KyI5wtK5sf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01939.txt.bz2
Content-length: 277
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Haswell tuning was done many years ago. We really shouldn't change it.
For newer processors, we need to investigate PARTIAL_REG_DEPENDENCY vs
PARTIAL_REG_STALL.
>From gcc-bugs-return-605045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 17:05:00 2018
Return-Path: <gcc-bugs-return-605045-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23866 invoked by alias); 18 May 2018 17:05:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23735 invoked by uid 55); 18 May 2018 17:04:56 -0000
From: "hubicka at ucw dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Fri, 18 May 2018 17: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.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hubicka at ucw dot cz
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85829-4-IRhnXlXsbB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01940.txt.bz2
Content-length: 981
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #3 from Jan Hubicka <hubicka at ucw dot cz> ---
> Haswell tuning was done many years ago. We really shouldn't change it.
> For newer processors, we need to investigate PARTIAL_REG_DEPENDENCY vs
> PARTIAL_REG_STALL.
I have revisited the tunning options primarily to define more reasonable
generic.
For that I have revisited some flags which seems to have been set incorrectly.
We run regular benchmarks on Haswell at
https://gcc.opensuse.org/gcc-old/index.html
(Czerny) and especially specfp2000 has improved noticeably past release cycle.
https://gcc.opensuse.org/gcc-old/SPEC/CFP/sb-czerny-head-64/mean-fp_big.png
There are quite few haswell chips around so I do not see why we should stop
trying to improve code generated there plus it would be good to have fewer
combinations enabled for differnt generations.
So I would suggest to revisit PARTIAL_REG_DEPENDENCY wrt PARTIAL_REG_STALL
for Haswell+
Honza
>From gcc-bugs-return-605046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 17:15:58 2018
Return-Path: <gcc-bugs-return-605046-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58080 invoked by alias); 18 May 2018 17:15: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 57941 invoked by uid 48); 18 May 2018 17:15:50 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85826] [9 Regression] ICE in builtin_memref in gcc/gimple-ssa-warn-restrict.c:281 starting with r260280
Date: Fri, 18 May 2018 17:15:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-85826-4-67wT1OyW8D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01941.txt.bz2
Content-length: 379
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85826
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-605047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 17:59:57 2018
Return-Path: <gcc-bugs-return-605047-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104279 invoked by alias); 18 May 2018 17:59:56 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104231 invoked by uid 48); 18 May 2018 17:59:52 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85834] New: ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Fri, 18 May 2018 17:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 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-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01942.txt.bz2
Content-length: 1598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
Bug ID: 85834
Summary: ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
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: ---
../../trunk/gcc/asan.c: In function ‘rtx_insn* asan_emit_stack_protection(rtx,
rtx, unsigned int, long int*, tree_node**, int)’:
../../trunk/gcc/asan.c:1252:1: internal compiler error: in set_ssa_val_to, at
tree-ssa-sccvn.c:3396
asan_emit_stack_protection (rtx base, rtx pbase, unsigned int alignb,
^~~~~~~~~~~~~~~~~~~~~~~~~~
0x10391dd set_ssa_val_to(tree_node*, tree_node*)
../../trunk/gcc/tree-ssa-sccvn.c:3393
0x103a3c5 visit_use(tree_node*)
../../trunk/gcc/tree-ssa-sccvn.c:0
0x102fdcb process_scc(vec<tree_node*, va_heap, vl_ptr>)
../../trunk/gcc/tree-ssa-sccvn.c:4416
0x102fdcb extract_and_process_scc_for_name(tree_node*)
../../trunk/gcc/tree-ssa-sccvn.c:4487
This fault can be demonstrated by bootstrapping gcc with the following
commands:
../trunk/configure --prefix=/home/dcb/gcc/results.260370 \
--disable-multilib \
--disable-werror \
--enable-checking=df,extra,fold,rtl,yes \
--enable-languages=c,c++,fortran
sed 's/-O2/-O3/' < Makefile > Makefile.tmp
mv Makefile.tmp Makefile
This command used to work at revision 260281, but now at revision
260370, it doesn't work.
>From gcc-bugs-return-605048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:02:37 2018
Return-Path: <gcc-bugs-return-605048-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107097 invoked by alias); 18 May 2018 18: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 107048 invoked by uid 48); 18 May 2018 18:02:33 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85834] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Fri, 18 May 2018 18: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85834-4-EvmSZQ0sMr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01943.txt.bz2
Content-length: 280
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
--- Comment #1 from David Binderman <dcb314 at hotmail dot com> ---
Removing the last two lines of commands which replace -O2 with -O3
also make it work, so it looks like someone's broken some part
of -O3 since Wed 16 May.
>From gcc-bugs-return-605049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:11:55 2018
Return-Path: <gcc-bugs-return-605049-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129477 invoked by alias); 18 May 2018 18:11:55 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129397 invoked by uid 48); 18 May 2018 18:11:51 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85835] New: libsanitizer includes <sys/ustat.h> unconditionally
Date: Fri, 18 May 2018 18:11: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: 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-85835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01944.txt.bz2
Content-length: 1726
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85835
Bug ID: 85835
Summary: libsanitizer includes <sys/ustat.h> unconditionally
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: adhemerval.zanella at linaro dot org, 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: ---
libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc has
#include <sys/ustat.h>
...
#if SANITIZER_LINUX && !SANITIZER_ANDROID
unsigned struct_ustat_sz = sizeof(struct ustat);
unsigned struct_rlimit64_sz = sizeof(struct rlimit64);
unsigned struct_statvfs64_sz = sizeof(struct statvfs64);
#endif // SANITIZER_LINUX && !SANITIZER_ANDROID
But <sys/ustat.h> has been removed from glibc 2.28 by
commit cf2478d53ad7071e84c724a986b56fe17f4f4ca7
Author: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Date: Sun Mar 18 11:28:59 2018 +0800
Deprecate ustat syscall interface
As for sysctl, ustat has been deprecated in favor of {f}statfs. Also
some newer ports which uses generic interface builds a stub version that
returns ENOSYS.
This patch deprecates ustat interface by removing ustat.h related headers,
adding a compatibility symbol, and avoiding new ports to build and provide
the symbol.
Checked on x86_64-linux-gnu and i686-linux-gnu. Also checked with a
check-abi on all affected ABIs.
>From gcc-bugs-return-605050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:17:00 2018
Return-Path: <gcc-bugs-return-605050-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7975 invoked by alias); 18 May 2018 18:17: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 7159 invoked by uid 48); 18 May 2018 18:16:54 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85826] [9 Regression] ICE in builtin_memref in gcc/gimple-ssa-warn-restrict.c:281 starting with r260280
Date: Fri, 18 May 2018 18: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: ice-on-valid-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: P1
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords
Message-ID: <bug-85826-4-KrTHHHpmtF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85826-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01945.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85826
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00939.html
>From gcc-bugs-return-605051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:23:46 2018
Return-Path: <gcc-bugs-return-605051-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15948 invoked by alias); 18 May 2018 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 15827 invoked by uid 48); 18 May 2018 18:23:42 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Fri, 18 May 2018 18: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: janus 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-0JYHhKAcM7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01946.txt.bz2
Content-length: 684
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #32 from janus at gcc dot gnu.org ---
(In reply to Steve Kargl from comment #31)
> > This PR is not about reordering, but about short-circuiting.
>
> AFAICT this PR is about a function with side-effects,
> and re-ordering can have an potentially undesirable
> result.
Yah, I guess you can dream up all kinds of possible issues with non-pure
functions, but that is really beyond the scope of this PR. I feel like I have
already opened up a barrel large enough, and have gotten sufficient flak for
that. I'm really not interested in taking this discussion any further. If you
are, please open a new PR for that.
>From gcc-bugs-return-605052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:25:09 2018
Return-Path: <gcc-bugs-return-605052-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31674 invoked by alias); 18 May 2018 18:25: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 31599 invoked by uid 48); 18 May 2018 18:25:05 -0000
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris SPARC when parsing a simple character class
Date: Fri, 18 May 2018 18: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: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: timshen at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85824-4-ZhJ1Oy50Di@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01947.txt.bz2
Content-length: 2049
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
--- Comment #5 from Tim Shen <timshen at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #4)
> Tim, I'll take care of checking errno in collate<>::_M_transform but could
> you advise what to do about the regex compiler? Maybe:
>
> --- a/libstdc++-v3/include/bits/regex.h
> +++ b/libstdc++-v3/include/bits/regex.h
> @@ -257,7 +257,11 @@ _GLIBCXX_BEGIN_NAMESPACE_CXX11
> const __ctype_type& __fctyp(use_facet<__ctype_type>(_M_locale));
> std::vector<char_type> __s(__first, __last);
> __fctyp.tolower(__s.data(), __s.data() + __s.size());
> - return this->transform(__s.data(), __s.data() + __s.size());
> + __try {
> + return this->transform(__s.data(), __s.data() + __s.size());
> + } catch(const std::runtime_error&) {
> + return string_type();
> + }
> }
>
> /**
First of all, std::regex("[0-9]") shouldn't be locale sensitive, as
regex_constants::collate is set. If somehow a locale-related exception was
thrown without collate being set, it's a bug in the regex implementation and we
should fix it. We probably have a bug in _BracketMatcher::_M_apply().
When collate is set, we still don't want to eagerly forward exceptions in regex
ctor. I think regex_traits<>::transform_primary should be exception neutral
(unless it's specified otherwise). Instead, we some how fix regex's constructor
not to generate exceptions from _BracketMatcher::_M_make_cache().
Regarding the compile-time variable __collate in _BracketMatcher, I suggest to
fix _BracketMatcher to the following definition:
* If !__collate or -fno-exceptions, nothing needs to be changed; otherwise
* change the element of cache from bool to a 3-state enum, e.g. enum { MATCHED,
NOT_MATCHED, NOT_CACHED }. When an exception happens in _M_make_cache, catch it
and set the cache result to NOT_CACHED. During regex matching, non-cached
result requires a full run of _M_apply() and it likely throws.
>From gcc-bugs-return-605053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:29:33 2018
Return-Path: <gcc-bugs-return-605053-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35672 invoked by alias); 18 May 2018 18:29: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 35501 invoked by uid 48); 18 May 2018 18:29:29 -0000
From: "timshen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85824] regex constructor crashes under UTF-8 locale on Solaris SPARC when parsing a simple character class
Date: Fri, 18 May 2018 18:29: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: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: timshen at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85824-4-msM53v6q7Q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85824-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01948.txt.bz2
Content-length: 315
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85824
--- Comment #6 from Tim Shen <timshen at gcc dot gnu.org> ---
(In reply to Tim Shen from comment #5)
> First of all, std::regex("[0-9]") shouldn't be locale sensitive, as
> regex_constants::collate is set.
Correction: as regex_constants::collate is *not* set.
>From gcc-bugs-return-605054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:31:18 2018
Return-Path: <gcc-bugs-return-605054-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48581 invoked by alias); 18 May 2018 18:31:18 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 45457 invoked by uid 48); 18 May 2018 18:31:13 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85836] New: [meta-bug] Fortran 2018 support
Date: Fri, 18 May 2018 18:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-85836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01949.txt.bz2
Content-length: 473
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
Bug ID: 85836
Summary: [meta-bug] Fortran 2018 support
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: janus at gcc dot gnu.org
Target Milestone: ---
meta bug to track all PRs related to the Fortran 2018 standard
>From gcc-bugs-return-605055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:34:08 2018
Return-Path: <gcc-bugs-return-605055-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62805 invoked by alias); 18 May 2018 18:34: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 59042 invoked by uid 48); 18 May 2018 18:33:35 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Fri, 18 May 2018 18: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: build, ice-on-valid-code
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: cc
Message-ID: <bug-85834-4-SEOpSvguvZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01950.txt.bz2
Content-length: 491
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
David Binderman <dcb314 at hotmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
Revision 260318, dated 17 May, is the most recent change to file
tree-ssa-sccvn.c
Adding Richard Biener.
>From gcc-bugs-return-605056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:35:10 2018
Return-Path: <gcc-bugs-return-605056-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98773 invoked by alias); 18 May 2018 18: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 96394 invoked by uid 48); 18 May 2018 18:35:05 -0000
From: "eyalroz at technion dot ac.il" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] New: Listing of all error and warning messages
Date: Fri, 18 May 2018 18:35: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eyalroz at technion dot ac.il
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01951.txt.bz2
Content-length: 1472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
Bug ID: 85837
Summary: Listing of all error and warning messages
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: web
Assignee: unassigned at gcc dot gnu.org
Reporter: eyalroz at technion dot ac.il
Target Milestone: ---
Compiler error and warning messages are sometimes difficult to understand -
especially (but not exclusively) for novice developers. They are also typically
concise, and assume some knowledge of relevant terms, which the program author
may not know, despite being able to write a program.
I also note that many users repeatedly ask questions on web forums and Q&A
sites (e.g. StackOverflow) regarding specific error messages they get - not
just asking "what's wrong with my code which causes the error?", but rather
"What does this message mean? I don't understand what it says."
Now, the GCC manual does not seem include such a listing, and I could not find
it on the Wiki either. Assuming it indeed doesn't exist - I believe that it
should. If it does exist, then the bug is that it's difficult to notice/locate.
Note that to realize such a listing it should be possible to harness more than
just the GCC developers, if it's done through the Wiki. (Of course people would
need to be attracted to the Wiki to assist in doing this.)
>From gcc-bugs-return-605057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:40:05 2018
Return-Path: <gcc-bugs-return-605057-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122205 invoked by alias); 18 May 2018 18:40: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 122119 invoked by uid 48); 18 May 2018 18:40:00 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 18:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
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: keywords
Message-ID: <bug-85837-4-vdKtT5yzXR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01952.txt.bz2
Content-length: 944
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |documentation
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
We try to improve error messages rather than list all of the error messages
out.
For an example the following URL links of the improvements to all of the
diagnostic in GCC 8 (that was recorded as a bugzilla entry):
https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=RESOLVED&cf_known_to_fail_type=allwords&cf_known_to_work_type=allwords&component=c%2B%2B&keywords=diagnostic%2C%20&keywords_type=allwords&list_id=210084&product=gcc&query_format=advanced&resolution=FIXED&short_desc=Regression&short_desc_type=notregexp&target_milestone=8.0
>From gcc-bugs-return-605058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:40:50 2018
Return-Path: <gcc-bugs-return-605058-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123424 invoked by alias); 18 May 2018 18:40:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 123346 invoked by uid 48); 18 May 2018 18:40:45 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85838] New: -Wmaybe-uninitialized warning in sparc.c (sparc_expand_builtin) breaks SPARC bootstrap
Date: Fri, 18 May 2018 18:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter cc target_milestone cf_gcchost cf_gcctarget cf_gccbuild
Message-ID: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01953.txt.bz2
Content-length: 1872
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85838
Bug ID: 85838
Summary: -Wmaybe-uninitialized warning in sparc.c
(sparc_expand_builtin) breaks SPARC bootstrap
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: ro at gcc dot gnu.org
CC: ebotcazou at gcc dot gnu.org, rguenth at gcc dot gnu.org
Target Milestone: ---
Host: sparc-sun-solaris2.*
Target: sparc-sun-solaris2.*
Build: sparc-sun-solaris2.*
Between 20180517 (r260326) and 20180518 (r260354), Solaris/SPARC bootstrap got
broken. Compiling sparc.c in stage2 gives
In file included from /vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c:42:
/vol/gcc/src/hg/trunk/local/gcc/recog.h: In function 'rtx_def*
sparc_expand_builtin(tree, rtx, rtx, machine_mode, int)':
/vol/gcc/src/hg/trunk/local/gcc/recog.h:303:85: error: 'op[0]' may be used
uninitialized in this function [-Werror=maybe-uninitialized]
rtx_insn * operator () (rtx a0, rtx a1, rtx a2, rtx a3) const { return
((f4)func) (a0, a1, a2, a3); }
~~~~~~~~~~~^~~~~~~~~~~~~~~~
/vol/gcc/src/hg/trunk/local/gcc/config/sparc/sparc.c:11595:12: note: 'op[0]'
was declared here
rtx pat, op[4];
^~
A reghunt identified this patch
2018-05-18 Richard Biener <rguenther@suse.de>
* tree-dfa.c (get_ref_base_and_extent): Use range-info to refine
results when processing array refs with variable index.
as the culprit.
>From gcc-bugs-return-605059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:41:02 2018
Return-Path: <gcc-bugs-return-605059-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 124236 invoked by alias); 18 May 2018 18: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 124086 invoked by uid 48); 18 May 2018 18:40:58 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85838] -Wmaybe-uninitialized warning in sparc.c (sparc_expand_builtin) breaks SPARC bootstrap
Date: Fri, 18 May 2018 18:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone
Message-ID: <bug-85838-4-tmBWkyZcya@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01954.txt.bz2
Content-length: 285
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85838
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
>From gcc-bugs-return-605060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:49:57 2018
Return-Path: <gcc-bugs-return-605060-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19380 invoked by alias); 18 May 2018 18:49: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 19073 invoked by uid 55); 18 May 2018 18:49:53 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85838] -Wmaybe-uninitialized warning in sparc.c (sparc_expand_builtin) breaks SPARC bootstrap
Date: Fri, 18 May 2018 18: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85838-4-6FoXLTe1ox@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01955.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85838
--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
Author: ebotcazou
Date: Fri May 18 18:49:20 2018
New Revision: 260374
URL: https://gcc.gnu.org/viewcvs?rev=260374&root=gcc&view=rev
Log:
PR bootstrap/85838
* config/sparc/sparc.c (sparc_expand_builtin): Always initialize op[0].
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/sparc/sparc.c
>From gcc-bugs-return-605061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:50:26 2018
Return-Path: <gcc-bugs-return-605061-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20914 invoked by alias); 18 May 2018 18:50:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 20341 invoked by uid 48); 18 May 2018 18:50:22 -0000
From: "ebotcazou at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85838] -Wmaybe-uninitialized warning in sparc.c (sparc_expand_builtin) breaks SPARC bootstrap
Date: Fri, 18 May 2018 18:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ebotcazou at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status version resolution
Message-ID: <bug-85838-4-ECZ82ROiMk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85838-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01956.txt.bz2
Content-length: 501
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85838
Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Version|8.0 |9.0
Resolution|--- |FIXED
--- Comment #2 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
This should work again.
>From gcc-bugs-return-605062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 18:52:16 2018
Return-Path: <gcc-bugs-return-605062-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23987 invoked by alias); 18 May 2018 18:52: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 23936 invoked by uid 48); 18 May 2018 18:52:12 -0000
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85833] [AVX512] use mask registers instructions instead of scalar code
Date: Fri, 18 May 2018 18:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ubizjak at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85833-4-kGCEvPiUR1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01957.txt.bz2
Content-length: 646
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85833
--- Comment #1 from Uroš Bizjak <ubizjak at gmail dot com> ---
(In reply to Wojciech Mula from comment #0)
> There is a simple function, which checks if there is any non-zero element
> in a vector:
>
> ---ktest.c---
> #include <immintrin.h>
>
> int anynonzero_epi32(__m512i x) {
> const __m512i zero = _mm512_setzero_si512();
> const __mmask16 mask = _mm512_cmpneq_epi32_mask(x, zero);
> return mask != 0;
> }
> ---eof---
>
> $ gcc --version
> gcc (Debian 7.3.0-16) 7.3.0
>
> $ gcc -O2 -S -mavx512f ktest.c && cat ktest.s
ktestw is AVX512DQ instruction.
>From gcc-bugs-return-605063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 19:09:29 2018
Return-Path: <gcc-bugs-return-605063-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122521 invoked by alias); 18 May 2018 19: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 115369 invoked by uid 48); 18 May 2018 19:09:25 -0000
From: "eyalroz at technion dot ac.il" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 19:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eyalroz at technion dot ac.il
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85837-4-XGRvipGagx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01958.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
--- Comment #2 from Eyal Rozenberg <eyalroz at technion dot ac.il> ---
(In reply to Andrew Pinski from comment #1)
> We try to improve error messages rather than list all of the error messages
> out.
But the listed error messages must balance readability/accessibility with
conciseness. Specifically, an error message will never have a short example of
a typical error and a correction. Or an explanation, in a few sentences, of a
some concept referred to by the message, or a quotation of a paragraph from the
language standard and so on.
>From gcc-bugs-return-605064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 19:13:22 2018
Return-Path: <gcc-bugs-return-605064-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3966 invoked by alias); 18 May 2018 19:13:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3889 invoked by uid 55); 18 May 2018 19:13:17 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85599] Prevent short-circuiting of logical expressions for non-pure functions
Date: Fri, 18 May 2018 19: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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85599-4-ZapM19RI1J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85599-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01959.txt.bz2
Content-length: 3163
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
--- Comment #33 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Fri, May 18, 2018 at 06:23:41PM +0000, janus at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85599
>
> --- Comment #32 from janus at gcc dot gnu.org ---
> (In reply to Steve Kargl from comment #31)
> > > This PR is not about reordering, but about short-circuiting.
> >
> > AFAICT this PR is about a function with side-effects,
> > and re-ordering can have an potentially undesirable
> > result.
>
> Yah, I guess you can dream up all kinds of possible issues with non-pure
> functions, but that is really beyond the scope of this PR. I feel like I have
> already opened up a barrel large enough, and have gotten sufficient flak for
> that. I'm really not interested in taking this discussion any further. If you
> are, please open a new PR for that.
>
I don't think you're getting flak. I think you're
getting discussion, where both Thomas and I disagree
with you on whether this is a bug or not. This has
nothing to do with a pure or impure function. This
has to do with special casing a binop to explicitly
require that both arguments must be evaluated, because
one of the operands may have a side-effect. The Fortran
standard explicitly allows the current behavior.
Thomas is willing to compromise to at least issue a
warning that in '.false. .and. check()' check()
may not be evaluated. I've suggested a new option
-fno-short-circuit and a review of all binops to
force evaluation of both operands.
If I were to give you flak, I would have suggested
that you contact the other Fortran vendors with
bug reports for a missed optimization. It could
take a very long time to evaluate check(). Why
bother with the evaluation when the result for
'.false. .and. check()' is known regardless of the
result for check()? Yes, it is a rhetorical
question as I know your answer that check() may
have side-effects.
And, if I were really to give you flak, I would
suggest that a patch is louder than words.
svn diff gcc/fortran/trans-expr.c
Index: gcc/fortran/trans-expr.c
===================================================================
--- gcc/fortran/trans-expr.c (revision 260235)
+++ gcc/fortran/trans-expr.c (working copy)
@@ -3446,6 +3446,12 @@ gfc_conv_expr_op (gfc_se * se, gfc_expr * expr)
if (lop)
{
+ if (expr->value.op.op == INTRINSIC_AND
+ || expr->value.op.op == INTRINSIC_OR)
+ {
+ lse.expr = gfc_evaluate_now (lse.expr, &se->pre);
+ rse.expr = gfc_evaluate_now (rse.expr, &se->pre);
+ }
/* The result of logical ops is always logical_type_node. */
tmp = fold_build2_loc (input_location, code, logical_type_node,
lse.expr, rse.expr);
% gfcx -o z a.f90 && ./z
check 1
check 2
I completely disagree with this patch without -fno-short-circuit.
You're welcomed.
>From gcc-bugs-return-605065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 19:22:14 2018
Return-Path: <gcc-bugs-return-605065-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 77357 invoked by alias); 18 May 2018 19: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 76137 invoked by uid 48); 18 May 2018 19:22:10 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82275] gfortran rejects valid & accepts invalid reference to dimension-remapped type SELECT TYPE selector
Date: Fri, 18 May 2018 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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82275-4-guyNQ9Vsem@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01960.txt.bz2
Content-length: 466
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82275
--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Damian Rouson from comment #3)
> Thanks for looking at this. Once there's a fix, it would be great if it
> could be back-ported to GCC 7 as well.
Hi Damian,
Now I have found a bit of time, I am working through the bugs that I have
taken. I have just arrived at this one. Sorry to have taken so long.
Let's see how it goes :-)
Paul
>From gcc-bugs-return-605066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 19:44:25 2018
Return-Path: <gcc-bugs-return-605066-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50425 invoked by alias); 18 May 2018 19:44: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 50381 invoked by uid 48); 18 May 2018 19:44:21 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 19:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
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-85837-4-xLdhqASIPW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01961.txt.bz2
Content-length: 912
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Eyal Rozenberg from comment #0)
> Now, the GCC manual does not seem include such a listing, and I could not
> find it on the Wiki either. Assuming it indeed doesn't exist - I believe
> that it should. If it does exist, then the bug is that it's difficult to
> notice/locate.
There's https://gcc.gnu.org/wiki/VerboseDiagnostics for a few such errors.
> Note that to realize such a listing it should be possible to harness more
> than just the GCC developers, if it's done through the Wiki. (Of course
> people would need to be attracted to the Wiki to assist in doing this.)
This absolutely should be done by users, not the GCC developers. We're all busy
working on GCC already, and if we knew how to make the diagnostics easier to
understand then we'd already have done it.
>From gcc-bugs-return-605067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 19:54:43 2018
Return-Path: <gcc-bugs-return-605067-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 81851 invoked by alias); 18 May 2018 19:54: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 81725 invoked by uid 48); 18 May 2018 19:54:38 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85792] #include <variant> triggers Wctor-dtor-privcay
Date: Fri, 18 May 2018 19:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on component everconfirmed
Message-ID: <bug-85792-4-DpXAHn2Byk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01962.txt.bz2
Content-length: 988
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85792
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords|diagnostic |
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-18
Component|libstdc++ |c++
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
The warning is bogus, because that type inherits a default constructor from its
base class (also it probably shouldn't give a warning for code in system
headers).
Minimal testcase:
template<typename T> struct A { };
template<typename T> struct B : A<T> {
using A<T>::A;
B(const B&) { }
};
It's probably related to constructors in dependent base classes not being seen
at the point the warning is given.
>From gcc-bugs-return-605068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 19:58:28 2018
Return-Path: <gcc-bugs-return-605068-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 110424 invoked by alias); 18 May 2018 19:58: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 110365 invoked by uid 48); 18 May 2018 19:58:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85792] [8/9 Regression] #include <variant> triggers Wctor-dtor-privcay
Date: Fri, 18 May 2018 19:58:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-85792-4-0cqR3EHiSW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85792-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85792-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01963.txt.bz2
Content-length: 957
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85792
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
CC| |nathan at gcc dot gnu.org
Known to work| |7.3.0
Summary|#include <variant> triggers |[8/9 Regression] #include
|Wctor-dtor-privcay |<variant> triggers
| |Wctor-dtor-privcay
Known to fail| |8.1.0, 9.0
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Regression starting with r250281:
* class.c (maybe_warn_about_overly_private_class): Ignore public
copy ctors.
* g++.dg/warn/ctor-dtor-privacy-3.C: New.
>From gcc-bugs-return-605069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 20:03:26 2018
Return-Path: <gcc-bugs-return-605069-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10761 invoked by alias); 18 May 2018 20: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 10314 invoked by uid 55); 18 May 2018 20:03:19 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58407] [C++11] Should warn about deprecated implicit generation of copy constructor/assignment
Date: Fri, 18 May 2018 20: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: 4.8.1
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-58407-4-h2V8xzD0HY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58407-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58407-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01964.txt.bz2
Content-length: 1628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58407
--- Comment #15 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Fri May 18 20:02:48 2018
New Revision: 260381
URL: https://gcc.gnu.org/viewcvs?rev=260381&root=gcc&view=rev
Log:
PR c++/58407 - deprecated implicit copy ops.
gcc/c-family/
* c.opt (Wdeprecated-copy): New flag.
gcc/cp/
* call.c (build_over_call): Warn about deprecated trivial fns.
* class.c (classtype_has_user_copy_or_dtor): New.
(type_build_ctor_call): Check TREE_DEPRECATED.
(type_build_dtor_call): Likewise.
* decl2.c (cp_warn_deprecated_use): Move from tree.c.
Add checks. Return bool. Handle -Wdeprecated-copy.
(mark_used): Use it.
* decl.c (grokdeclarator): Remove redundant checks.
* typeck2.c (build_functional_cast): Likewise.
* method.c (lazily_declare_fn): Mark deprecated copy ops.
* init.c (build_aggr_init): Only set TREE_USED if there are
side-effects.
libitm/
* beginend.cc (save): Disable -Werror=deprecated-copy.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/depr-copy1.C
Modified:
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c.opt
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/call.c
trunk/gcc/cp/class.c
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/decl.c
trunk/gcc/cp/decl2.c
trunk/gcc/cp/init.c
trunk/gcc/cp/method.c
trunk/gcc/cp/tree.c
trunk/gcc/cp/typeck2.c
trunk/gcc/doc/invoke.texi
trunk/gcc/testsuite/g++.old-deja/g++.other/warn6.C
trunk/libitm/ChangeLog
trunk/libitm/beginend.cc
>From gcc-bugs-return-605070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 20:18:46 2018
Return-Path: <gcc-bugs-return-605070-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29666 invoked by alias); 18 May 2018 20: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 29610 invoked by uid 48); 18 May 2018 20:18:39 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85839] New: [F2018] warn for obsolescent features
Date: Fri, 18 May 2018 20:18: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: janus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-85839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01965.txt.bz2
Content-length: 671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85839
Bug ID: 85839
Summary: [F2018] warn for obsolescent features
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: janus at gcc dot gnu.org
Target Milestone: ---
Fortran 2018 introduces several new obsolescences:
* COMMON
* EQUIVALENCE
* BLOCK DATA
* labelled DO statements
* specific names for standard intrinsic functions
* FORALL
(see also PR 40881, where the same has been done for the F03 obsolenscences)
>From gcc-bugs-return-605071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 20:21:12 2018
Return-Path: <gcc-bugs-return-605071-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33324 invoked by alias); 18 May 2018 20:21: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 33289 invoked by uid 48); 18 May 2018 20:21:06 -0000
From: "jjcogliati-r1 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] New: Memory leak in write.c
Date: Fri, 18 May 2018 20:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jjcogliati-r1 at yahoo 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-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01966.txt.bz2
Content-length: 2272
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
Bug ID: 85840
Summary: Memory leak in write.c
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: jjcogliati-r1 at yahoo dot com
Target Milestone: ---
This bug comes from trying to find a memory leak in my own program.
gfortran --version
GNU Fortran (GCC) 7.3.1 20180303 (Red Hat 7.3.1-5)
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
The line in my code was:
print '(A16,I7,6E25.16E3)',"start line print",i,a,b,c,d,e,f
where a,b,c,d,e,f are complicated real kinds.
The valgrind trace was:
==23064== 142,120 bytes in 440 blocks are definitely lost in loss record 39 of
49
==23064== at 0x4C2CB6B: malloc (vg_replace_malloc.c:299)
==23064== by 0x4E53454: _gfortrani_xmalloc (memory.c:42)
==23064== by 0x4FD637A: write_float_0 (write.c:1593)
==23064== by 0x4FCD98C: formatted_transfer_scalar_write (transfer.c:2041)
==23064== by 0x4FCDF9C: formatted_transfer (transfer.c:2279)
Looking at write.c, we have:
/* String buffer to hold final result. */
result = select_string (dtp, f, str_buf, &res_len, kind); //line 1593
buffer = select_buffer (dtp, f, precision, buf_stack, &buf_size, kind);
get_float_string (dtp, f, source , kind, 0, buffer,
precision, buf_size, result, &res_len);
write_float_string (dtp, result, res_len);
if (buf_size > BUF_STACK_SZ)
free (buffer);
if (res_len > BUF_STACK_SZ)
free (result);
Notice that we assign to the value of res_len from select_string AND from
get_float_string, and get_float_string can assign to the length in functions
called from it such as in build_float_string
So I think what is happening is res_len is getting assigned a number that is
smaller than BUF_STACK_SZ, and then result is not getting freed.
I haven't come up with a small test case yet, but I certainly can if needed.
>From gcc-bugs-return-605072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 20:38:22 2018
Return-Path: <gcc-bugs-return-605072-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58060 invoked by alias); 18 May 2018 20: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 57991 invoked by uid 48); 18 May 2018 20:38:17 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] New: [F018] reject deleted features
Date: Fri, 18 May 2018 20:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
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-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01967.txt.bz2
Content-length: 591
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
Bug ID: 85841
Summary: [F018] reject deleted features
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: janus at gcc dot gnu.org
Target Milestone: ---
Fortran 2018 removes the following features:
* arithmetic IF statement
* nonblock DO construct
They have been obsolescent since F90, and should now be rejected with
-std=f2018.
>From gcc-bugs-return-605073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 21:01:31 2018
Return-Path: <gcc-bugs-return-605073-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114130 invoked by alias); 18 May 2018 21:01: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 114009 invoked by uid 48); 18 May 2018 21:01:25 -0000
From: "eyalroz at technion dot ac.il" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 21:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eyalroz at technion dot ac.il
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85837-4-iJGsrEntaJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01968.txt.bz2
Content-length: 1222
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
--- Comment #4 from Eyal Rozenberg <eyalroz at technion dot ac.il> ---
(In reply to Jonathan Wakely from comment #3)
> There's https://gcc.gnu.org/wiki/VerboseDiagnostics for a few such errors.
Well, that's a (tiny) start... however:
* I wouldn't have found it if you wouldn't have provided the link - and I did
search the Wiki (albeit not very thoroughly)
* I think that has low search engine visibility
* I believe there should be some auto-generated skeleton of that (either a
single page or multiple pages) which collects all error messages.
* I would definitely separate the language-specific errors for different
languages (perhaps an even finer separation into pages is called for, but
certainly at least that)
> This absolutely should be done by users, not the GCC developers. We're all
> busy working on GCC already, and if we knew how to make the diagnostics
> easier to understand then we'd already have done it.
Fair enough, but, honestly - if the page says "Please, feel free to suggest new
content in gcc-help mailing list" - practically nobody will contribute.
Also, I'm sure that some of this could be adapted from from other sources
online.
>From gcc-bugs-return-605074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 21:03:36 2018
Return-Path: <gcc-bugs-return-605074-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 116998 invoked by alias); 18 May 2018 21: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 116442 invoked by uid 48); 18 May 2018 21:03:31 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 21:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
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-85837-4-nAI1EZ4OLY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01969.txt.bz2
Content-length: 507
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Eyal Rozenberg from comment #4)
> Fair enough, but, honestly - if the page says "Please, feel free to suggest
> new content in gcc-help mailing list" - practically nobody will contribute.
Why not?
> Also, I'm sure that some of this could be adapted from from other sources
> online.
Be the change that you want to see in the world.
If you want this, make it happen.
>From gcc-bugs-return-605075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 21:08:22 2018
Return-Path: <gcc-bugs-return-605075-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 129130 invoked by alias); 18 May 2018 21:08:22 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 129074 invoked by uid 48); 18 May 2018 21:08:17 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 21:08:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc
Message-ID: <bug-85837-4-QoVOySOuJl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01970.txt.bz2
Content-length: 1474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
CC| |dmalcolm at gcc dot gnu.org,
| |egallager at gcc dot gnu.org
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #3)
> (In reply to Eyal Rozenberg from comment #0)
> > Now, the GCC manual does not seem include such a listing, and I could not
> > find it on the Wiki either. Assuming it indeed doesn't exist - I believe
> > that it should. If it does exist, then the bug is that it's difficult to
> > notice/locate.
>
> There's https://gcc.gnu.org/wiki/VerboseDiagnostics for a few such errors.
>
> > Note that to realize such a listing it should be possible to harness more
> > than just the GCC developers, if it's done through the Wiki. (Of course
> > people would need to be attracted to the Wiki to assist in doing this.)
>
> This absolutely should be done by users, not the GCC developers. We're all
> busy working on GCC already, and if we knew how to make the diagnostics
> easier to understand then we'd already have done it.
This is something David Malcolm sometimes focuses on; cc-ing him.
>From gcc-bugs-return-605076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 21:20:40 2018
Return-Path: <gcc-bugs-return-605076-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85454 invoked by alias); 18 May 2018 21:20: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 79621 invoked by uid 48); 18 May 2018 21:20:35 -0000
From: "eyalroz at technion dot ac.il" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 21:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic, documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eyalroz at technion dot ac.il
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85837-4-gzixA7cBWM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01971.txt.bz2
Content-length: 1297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
--- Comment #7 from Eyal Rozenberg <eyalroz at technion dot ac.il> ---
(In reply to Jonathan Wakely from comment #5)
> Be the change that you want to see in the world.
>
> If you want this, make it happen.
Well, I already started by filing this bug, but point taken.
> (In reply to Eyal Rozenberg from comment #4)
> > Fair enough, but, honestly - if the page says "Please, feel free to suggest
> > new content in gcc-help mailing list" - practically nobody will contribute.
>
> Why not?
Really? Ok, I'll explain: Many/most people familiar with collaboratively-edited
resources such as Wikis or Q&A sites expect either immediate ability to edit
content, or a requirement of at most website registration. What this line is
telling visitors is (with slight over-dramatization): "Don't expect to be able
to edit existing content on this page, ever. Don't expect to easily add content
to this page, ever. If you want to even add anything to this page, you have to
increase your level of commitment to that of being a mailing list member.
You'll have to talk to people on that mailing list. You'll have to convince
them your addition is important. Then maybe it'll be added." - this amounts to
telling most people to go away.
>From gcc-bugs-return-605077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 22:02:36 2018
Return-Path: <gcc-bugs-return-605077-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44896 invoked by alias); 18 May 2018 22: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 44831 invoked by uid 48); 18 May 2018 22:02:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83891] std::filesystem::path::is_absolute for Windows
Date: Fri, 18 May 2018 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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83891-4-RVshxqPOrf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83891-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83891-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01972.txt.bz2
Content-length: 255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83891
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This is still wrong, for Windows it should be:
return has_root_name() && has_root_directory();
But I'll fix it as part of PR 78870
>From gcc-bugs-return-605078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 22:21:58 2018
Return-Path: <gcc-bugs-return-605078-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48885 invoked by alias); 18 May 2018 22:21:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41946 invoked by uid 55); 18 May 2018 22:21:52 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type
Date: Fri, 18 May 2018 22:21:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: alias, 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-82899-4-cCjTcltQkh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01973.txt.bz2
Content-length: 731
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
--- Comment #24 from Marc Glisse <glisse at gcc dot gnu.org> ---
Author: glisse
Date: Fri May 18 22:21:20 2018
New Revision: 260383
URL: https://gcc.gnu.org/viewcvs?rev=260383&root=gcc&view=rev
Log:
Aliasing 'this' in a C++ constructor
2018-05-18 Marc Glisse <marc.glisse@inria.fr>
PR c++/82899
gcc/
* tree-ssa-structalias.c (create_variable_info_for_1): Extra argument.
(intra_create_variable_infos): Handle C++ constructors.
gcc/testsuite/
* g++.dg/pr82899.C: New testcase.
Added:
trunk/gcc/testsuite/g++.dg/pr82899.C
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-structalias.c
>From gcc-bugs-return-605079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 22:25:20 2018
Return-Path: <gcc-bugs-return-605079-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 64612 invoked by alias); 18 May 2018 22:25:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 64537 invoked by uid 48); 18 May 2018 22:25:15 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82899] *this in constructors could not alias with reference input parameters of the same type
Date: Fri, 18 May 2018 22:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: alias, missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-82899-4-aRMbHuy9aD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82899-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01974.txt.bz2
Content-length: 472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
Marc Glisse <glisse at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #25 from Marc Glisse <glisse at gcc dot gnu.org> ---
.
>From gcc-bugs-return-605080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 23:39:31 2018
Return-Path: <gcc-bugs-return-605080-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35885 invoked by alias); 18 May 2018 23:39: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 35659 invoked by uid 48); 18 May 2018 23:39:25 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug web/85837] Listing of all error and warning messages
Date: Fri, 18 May 2018 23:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: web
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic, 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-85837-4-N1lyhC6FCT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85837-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01975.txt.bz2
Content-length: 2469
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85837
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Eyal Rozenberg from comment #7)
> (In reply to Jonathan Wakely from comment #5)
> > Be the change that you want to see in the world.
> >
> > If you want this, make it happen.
>
> Well, I already started by filing this bug, but point taken.
So far you're just asking for other people to do the work. Speaking for myself,
I already know what GCC's diagnostics mean, and so what you're suggesting
wouldn't be useful to me* and that's probably true for most GCC developers.
You're asking busy people to do a ton of work.
* before you say I should do it anyway to help users, note that I did already
add most of the content to the wiki page.
> > (In reply to Eyal Rozenberg from comment #4)
> > > Fair enough, but, honestly - if the page says "Please, feel free to suggest
> > > new content in gcc-help mailing list" - practically nobody will contribute.
> >
> > Why not?
>
> Really? Ok, I'll explain: Many/most people familiar with
> collaboratively-edited resources such as Wikis or Q&A sites expect either
> immediate ability to edit content, or a requirement of at most website
> registration. What this line is telling visitors is (with slight
> over-dramatization): "Don't expect to be able to edit existing content on
> this page, ever. Don't expect to easily add content to this page, ever. If
This isn't a slight over-dramatization, this is nonsense.
"Please feel free to suggest new content" does not mean "you can not add new
content, ever".
> you want to even add anything to this page, you have to increase your level
> of commitment to that of being a mailing list member.
Nobody has to be a member of anything to send an email to the list. You don't
have to subscribe, you just have to send an email.
> You'll have to talk to
> people on that mailing list.
The horror!
> You'll have to convince them your addition is
> important. Then maybe it'll be added."
I don't think that's unreasonable, otherwise the page would descend into total
garbage very rapidly. Sites like Wikipedia and StackOverflow depend on
thousands of active contributors to keep the signal to noise ratio high and we
don't have the resources.
> - this amounts to telling most people
> to go away.
I've tried to improve the info at the top of the page. If you think it can
still be improved please make suggestions.
>From gcc-bugs-return-605081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 23:43:56 2018
Return-Path: <gcc-bugs-return-605081-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42661 invoked by alias); 18 May 2018 23:43: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 42543 invoked by uid 48); 18 May 2018 23:43:52 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/58407] [C++11] Should warn about deprecated implicit generation of copy constructor/assignment
Date: Fri, 18 May 2018 23:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 4.8.1
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-58407-4-zcX3pZoFpl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-58407-4@http.gcc.gnu.org/bugzilla/>
References: <bug-58407-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01976.txt.bz2
Content-length: 969
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58407
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #16 from Jason Merrill <jason at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #14)
> An interesting subcategory I noticed when I had the warning on by default is
> classes with a virtual destructor, such as the exception hierarchy. The
> warning calls attention to potential slicing problems, and so I think we
> don't want to add defaulted copy ops; it's good for users to be encouraged
> to e.g. catch by reference.
For the record, I changed my mind about this; a slicing warning should only
apply to copies from an object of unknown dynamic type.
-Wdeprecated-copy added for GCC 9.
>From gcc-bugs-return-605082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 18 23:43:57 2018
Return-Path: <gcc-bugs-return-605082-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42849 invoked by alias); 18 May 2018 23:43:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42585 invoked by uid 48); 18 May 2018 23:43:53 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81930] [meta-bug] Issues with -Weffc++
Date: Fri, 18 May 2018 23:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-81930-4-qoKp1dBWY3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01977.txt.bz2
Content-length: 515
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81930
Bug 81930 depends on bug 58407, which changed state.
Bug 58407 Summary: [C++11] Should warn about deprecated implicit generation of copy constructor/assignment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58407
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-605083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 01:31:20 2018
Return-Path: <gcc-bugs-return-605083-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52765 invoked by alias); 19 May 2018 01:31:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52502 invoked by uid 48); 19 May 2018 01:30:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/82063] issues with arguments enabled by -Wall
Date: Sat, 19 May 2018 01:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-82063-4-942WWMqlzv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82063-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82063-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01978.txt.bz2
Content-length: 471
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82063
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |middle-end
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch for -Walloc-alloc-size-larger-than problems:
https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00950.html
>From gcc-bugs-return-605084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 06:21:16 2018
Return-Path: <gcc-bugs-return-605084-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76537 invoked by alias); 19 May 2018 06:21: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 76463 invoked by uid 55); 19 May 2018 06:21:10 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Sat, 19 May 2018 06: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: build, ice-on-valid-code
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-85834-4-KsAvXel7Tk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01979.txt.bz2
Content-length: 790
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
--- Comment #3 from rguenther at suse dot de <rguenther at suse dot de> ---
On May 18, 2018 8:33:35 PM GMT+02:00, dcb314 at hotmail dot com
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
>
>David Binderman <dcb314 at hotmail dot com> changed:
>
> What |Removed |Added
>----------------------------------------------------------------------------
> CC| |rguenth at gcc dot gnu.org
>
>--- Comment #2 from David Binderman <dcb314 at hotmail dot com> ---
>Revision 260318, dated 17 May, is the most recent change to file
>tree-ssa-sccvn.c
>
>Adding Richard Biener.
If you have preprocessed source available that would help.
>From gcc-bugs-return-605085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 07:35:02 2018
Return-Path: <gcc-bugs-return-605085-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44024 invoked by alias); 19 May 2018 07:35:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43913 invoked by uid 48); 19 May 2018 07:34:49 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Sat, 19 May 2018 07:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, ice-on-valid-code
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: attachments.created
Message-ID: <bug-85834-4-PCO1RUACxN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01980.txt.bz2
Content-length: 342
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
--- Comment #4 from David Binderman <dcb314 at hotmail dot com> ---
Created attachment 44148
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44148&action=edit
gzipped C++ source code
This C++ source code is taking a long time to creduce,
so here is the original.
-O3 required.
>From gcc-bugs-return-605086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 07:38:10 2018
Return-Path: <gcc-bugs-return-605086-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53230 invoked by alias); 19 May 2018 07: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 51944 invoked by uid 48); 19 May 2018 07:38:03 -0000
From: "ensadc at mailnesia dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85842] New: Bogus -Wreturn-type with generic lambda and constexpr if
Date: Sat, 19 May 2018 07:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ensadc at mailnesia dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01981.txt.bz2
Content-length: 1119
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85842
Bug ID: 85842
Summary: Bogus -Wreturn-type with generic lambda and constexpr
if
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: ensadc at mailnesia dot com
Target Milestone: ---
https://wandbox.org/permlink/qSgjLEWzpsJmkHNU
----
template<class T>
auto f = [](auto&& arg) -> T* {
if constexpr (sizeof(arg) == 1) {
return nullptr;
} else {
return static_cast<T*>(&arg);
}
};
auto p = f<int>(0);
----
prog.cc: In instantiation of 'auto f<int>':
prog.cc:10:10: required from here
prog.cc:2:6: warning: no return statement in function returning non-void
[-Wreturn-type]
auto f = [](auto&& arg) -> T* {
^
----
This warning is bogus because both branches of `if constexpr` have a return
statement.
The warning will disappear when `if constexpr` is changed to `if`.
>From gcc-bugs-return-605087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 09:25:51 2018
Return-Path: <gcc-bugs-return-605087-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6609 invoked by alias); 19 May 2018 09:25: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 6560 invoked by uid 48); 19 May 2018 09:25:46 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sat, 19 May 2018 09:25:00 -0000
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.2.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: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82923-4-xlHEpZ8pP2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01982.txt.bz2
Content-length: 306
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #6 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> I can't believe that this isn't a duplicate although I can't find it. ...
PRs 66694 and 82617 are "fixed" by the patch at
https://gcc.gnu.org/ml/fortran/2018-05/msg00046.html.
>From gcc-bugs-return-605088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 09:46:35 2018
Return-Path: <gcc-bugs-return-605088-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91163 invoked by alias); 19 May 2018 09: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 91120 invoked by uid 48); 19 May 2018 09:46:31 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85839] [F2018] warn for obsolescent features
Date: Sat, 19 May 2018 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: 8.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: P5
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 target_milestone everconfirmed
Message-ID: <bug-85839-4-r4IdGpSjMZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85839-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85839-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01983.txt.bz2
Content-length: 606
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85839
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-19
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Not an emergency!
>From gcc-bugs-return-605089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 09:47:27 2018
Return-Path: <gcc-bugs-return-605089-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92212 invoked by alias); 19 May 2018 09:47: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 92184 invoked by uid 48); 19 May 2018 09:47:23 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Sat, 19 May 2018 09:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.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: 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 cf_reconfirmed_on everconfirmed
Message-ID: <bug-85841-4-TWCdEbjXDI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01984.txt.bz2
Content-length: 579
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P5
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-19
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
This PR could probably merged with pr85839.
>From gcc-bugs-return-605090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 09:49:35 2018
Return-Path: <gcc-bugs-return-605090-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95061 invoked by alias); 19 May 2018 09:49:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 95020 invoked by uid 48); 19 May 2018 09:49:27 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Sat, 19 May 2018 09: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: 7.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 cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85840-4-B3MXP2GZFc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01985.txt.bz2
Content-length: 923
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-19
CC| |jvdelisle at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> where a,b,c,d,e,f are complicated real kinds.
What is "complicated real kinds"? This should not matter.
I cannot reproduce the problem with
integer :: i
real :: a,b,c,d,e,f
a = 1.0
b = 2.0
c = 3.0
d = 4.0
e = 5.0
f = 6.0
i = 1000
print '(A16,I7,6E25.16E3)',"start line print",i,a,b,c,d,e,f
end
Could you please provide a reproducer?
>From gcc-bugs-return-605091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 10:50:28 2018
Return-Path: <gcc-bugs-return-605091-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54652 invoked by alias); 19 May 2018 10:50:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54486 invoked by uid 55); 19 May 2018 10:50:22 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sat, 19 May 2018 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82923-4-ENciucyoqT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01986.txt.bz2
Content-length: 1015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 10:49:50 2018
New Revision: 260392
URL: https://gcc.gnu.org/viewcvs?rev=260392&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 10:50:29 2018
Return-Path: <gcc-bugs-return-605093-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54791 invoked by alias); 19 May 2018 10: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 54489 invoked by uid 55); 19 May 2018 10:50:22 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Sat, 19 May 2018 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66694-4-Hug67i0lB3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01988.txt.bz2
Content-length: 1015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #4 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 10:49:50 2018
New Revision: 260392
URL: https://gcc.gnu.org/viewcvs?rev=260392&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 10:50:29 2018
Return-Path: <gcc-bugs-return-605092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54713 invoked by alias); 19 May 2018 10:50:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54548 invoked by uid 55); 19 May 2018 10:50:24 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file
Date: Sat, 19 May 2018 10:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
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:
Message-ID: <bug-82617-4-C9jjrEJjdV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01987.txt.bz2
Content-length: 1015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 10:49:50 2018
New Revision: 260392
URL: https://gcc.gnu.org/viewcvs?rev=260392&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 11:05:14 2018
Return-Path: <gcc-bugs-return-605094-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76686 invoked by alias); 19 May 2018 11:05: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 76597 invoked by uid 48); 19 May 2018 11:05:07 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/65024] [OOP] unlimited polymorphic pointer structure not built when it should be
Date: Sat, 19 May 2018 11:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: FIXME
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-65024-4-Jv2hlYRhM7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-65024-4@http.gcc.gnu.org/bugzilla/>
References: <bug-65024-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01989.txt.bz2
Content-length: 610
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65024
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #18 from Paul Thomas <pault at gcc dot gnu.org> ---
I have taken another look at the underlying problem and still do not see the
source. Since the fix has withstood the test of time, I will close this PR as
resolved.
Thanks for the report.
Paul
>From gcc-bugs-return-605095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 11:22:31 2018
Return-Path: <gcc-bugs-return-605095-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21336 invoked by alias); 19 May 2018 11:22: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 18440 invoked by uid 48); 19 May 2018 11:22:25 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49636] [F03] ASSOCIATE construct confused with slightly complicated case
Date: Sat, 19 May 2018 11:22:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-49636-4-yrldUZYqlJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01990.txt.bz2
Content-length: 1115
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49636
--- Comment #11 from Paul Thomas <pault at gcc dot gnu.org> ---
This has transformed itself into an ICE:
associate (i=>t2%j%i)
internal compiler error: in gfc_get_element_type, at fortran/trans-types.c:1278
0x5bb622 gfc_get_element_type(tree_node*)
../../trunk/gcc/fortran/trans-types.c:1278
0x895a50 trans_associate_var
../../trunk/gcc/fortran/trans-stmt.c:1741
0x89b1b1 gfc_trans_block_construct(gfc_code*)
../../trunk/gcc/fortran/trans-stmt.c:2065
0x81ed07 trans_code
../../trunk/gcc/fortran/trans.c:1924
0x84a7bd gfc_generate_function_code(gfc_namespace*)
../../trunk/gcc/fortran/trans-decl.c:6507
0x7d5ade translate_all_program_units
../../trunk/gcc/fortran/parse.c:6121
0x7d5ade gfc_parse_file()
../../trunk/gcc/fortran/parse.c:6324
0x81bf0f gfc_be_parse_file
../../trunk/gcc/fortran/f95-lang.c:204
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-605096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 11:33:10 2018
Return-Path: <gcc-bugs-return-605096-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82210 invoked by alias); 19 May 2018 11:33:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82030 invoked by uid 55); 19 May 2018 11:33:02 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sat, 19 May 2018 11:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82923-4-BL5BLcAFNo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01991.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 11:32:30 2018
New Revision: 260395
URL: https://gcc.gnu.org/viewcvs?rev=260395&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-array.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 11:33:10 2018
Return-Path: <gcc-bugs-return-605097-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82310 invoked by alias); 19 May 2018 11:33:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82038 invoked by uid 55); 19 May 2018 11:33:02 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Sat, 19 May 2018 11: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.9.2
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66694-4-Nf1m4o9Men@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01992.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 11:32:30 2018
New Revision: 260395
URL: https://gcc.gnu.org/viewcvs?rev=260395&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-array.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 11:33:11 2018
Return-Path: <gcc-bugs-return-605098-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82377 invoked by alias); 19 May 2018 11:33:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82042 invoked by uid 55); 19 May 2018 11:33:02 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file
Date: Sat, 19 May 2018 11:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
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:
Message-ID: <bug-82617-4-TTWEyFmxU5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01993.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 11:32:30 2018
New Revision: 260395
URL: https://gcc.gnu.org/viewcvs?rev=260395&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-array.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 12:40:03 2018
Return-Path: <gcc-bugs-return-605099-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111773 invoked by alias); 19 May 2018 12:40:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 111624 invoked by uid 48); 19 May 2018 12:39:58 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85836] [meta-bug] Fortran 2018 support
Date: Sat, 19 May 2018 12: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: 8.0
X-Bugzilla-Keywords: meta-bug
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-85836-4-LBujOBPnhY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01994.txt.bz2
Content-length: 499
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-19
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Marking as NEW.
>From gcc-bugs-return-605100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 13:57:07 2018
Return-Path: <gcc-bugs-return-605100-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 38795 invoked by alias); 19 May 2018 13:57: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 38705 invoked by uid 48); 19 May 2018 13:57:03 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/67958] The tests changed by r223498 now FAILs on darwin
Date: Sat, 19 May 2018 13:57: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67958-4-slrsR1VCnx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67958-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01995.txt.bz2
Content-length: 318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67958
--- Comment #3 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #1)
> Created attachment 39731 [details]
> Patch fixing the failures with the patches for pr71767
please send this patch to gcc-patches for review
>From gcc-bugs-return-605102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:54:35 2018
Return-Path: <gcc-bugs-return-605102-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69683 invoked by alias); 19 May 2018 14: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 69477 invoked by uid 55); 19 May 2018 14:54:31 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Sat, 19 May 2018 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.2
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66694-4-HrpHvHWflO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01997.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 14:53:58 2018
New Revision: 260399
URL: https://gcc.gnu.org/viewcvs?rev=260399&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/trans-array.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:54:36 2018
Return-Path: <gcc-bugs-return-605103-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69756 invoked by alias); 19 May 2018 14: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 69568 invoked by uid 55); 19 May 2018 14:54:31 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file
Date: Sat, 19 May 2018 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: 7.2.0
X-Bugzilla-Keywords:
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:
Message-ID: <bug-82617-4-RlzKGOSjQG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01998.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 14:53:58 2018
New Revision: 260399
URL: https://gcc.gnu.org/viewcvs?rev=260399&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/trans-array.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:54:35 2018
Return-Path: <gcc-bugs-return-605101-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69669 invoked by alias); 19 May 2018 14: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 69212 invoked by uid 55); 19 May 2018 14:54:30 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sat, 19 May 2018 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: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82923-4-4afpPFkG2c@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01996.txt.bz2
Content-length: 1087
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sat May 19 14:53:58 2018
New Revision: 260399
URL: https://gcc.gnu.org/viewcvs?rev=260399&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/allocate_assumed_charlen_4.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/trans-array.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:56:34 2018
Return-Path: <gcc-bugs-return-605104-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74277 invoked by alias); 19 May 2018 14:56: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 74227 invoked by uid 48); 19 May 2018 14:56:29 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sat, 19 May 2018 14:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82923-4-iOVfyGZY3y@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01999.txt.bz2
Content-length: 215
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #10 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on 7-branch through to trunk.
Thanks for the report and sorry that it took so long.
Paul
>From gcc-bugs-return-605105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:57:08 2018
Return-Path: <gcc-bugs-return-605105-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75268 invoked by alias); 19 May 2018 14:57:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 75192 invoked by uid 48); 19 May 2018 14:57:02 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sat, 19 May 2018 14:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
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-82923-4-nzI1B93MSa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02000.txt.bz2
Content-length: 462
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #11 from Paul Thomas <pault at gcc dot gnu.org> ---
I suppose that I have to mark it as resolved :-)
>From gcc-bugs-return-605106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:58:45 2018
Return-Path: <gcc-bugs-return-605106-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76886 invoked by alias); 19 May 2018 14:58:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 76785 invoked by uid 48); 19 May 2018 14:58:41 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Sat, 19 May 2018 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.2
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-66694-4-gPcXr5hZ1p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02001.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on 7-branch through to trunk.
Thanks for the report and sorry that it took so long.
Paul
>From gcc-bugs-return-605107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 14:59:26 2018
Return-Path: <gcc-bugs-return-605107-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78005 invoked by alias); 19 May 2018 14:59:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 77926 invoked by uid 48); 19 May 2018 14:59:22 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file
Date: Sat, 19 May 2018 14:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-82617-4-11RxskKD1M@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02002.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on 7-branch through to trunk.
Thanks for the report and sorry that it took so long.
Paul
>From gcc-bugs-return-605108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 20:56:58 2018
Return-Path: <gcc-bugs-return-605108-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42377 invoked by alias); 19 May 2018 20:56:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 42322 invoked by uid 48); 19 May 2018 20:56:53 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85643] attribute nonstring fails to squash -Wstringop-truncation warning at an offset
Date: Sat, 19 May 2018 20: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: 8.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85643-4-0kS4NrjBm1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02003.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #6 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #5)
> Committed into trunk in r260271.
So... FIXED then?
>From gcc-bugs-return-605109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 21:21:27 2018
Return-Path: <gcc-bugs-return-605109-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20693 invoked by alias); 19 May 2018 21:21: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 20643 invoked by uid 48); 19 May 2018 21:21:23 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/81693] FAIL: gcc.dg/torture/pr25967-*.c -O* execution test on darwin
Date: Sat, 19 May 2018 21: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: 8.0
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dominiq at lps dot ens.fr
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-81693-4-k0iR5841HY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02004.txt.bz2
Content-length: 860
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81693
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |dominiq at lps dot ens.fr
--- Comment #31 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #30)
> I have submitted a patch some time ago at
>
> https://gcc.gnu.org/ml/gcc-patches/2017-11/msg00939.html
>
> Mike asked for some changes and I got distracted before being able to
> fulfill the requests.
>
> I can do it in the coming week, but if someone want to do it sooner, there
> is no problem.
Moving from WAITING to assigned to you then.
>From gcc-bugs-return-605110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 21:26:32 2018
Return-Path: <gcc-bugs-return-605110-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24386 invoked by alias); 19 May 2018 21:26: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 24330 invoked by uid 48); 19 May 2018 21:26:27 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63545] ICE when building GCC for ia64-hp-hpux11.23 in hash_table<cselib_hasher,xcallocator>::find_slot_with_hash
Date: Sat, 19 May 2018 21: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: 4.9.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status everconfirmed
Message-ID: <bug-63545-4-kh4FgyXjVQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63545-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63545-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02005.txt.bz2
Content-length: 706
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63545
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |UNCONFIRMED
Ever confirmed|1 |0
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
Changing from WAITING back to UNCONFIRMED because the reporter provided the
materials requested, it was just that no one was able to confirm that they
trigger the bug in question. Thus the ball isn't in the reporter's court (which
is what WAITING implies), but rather GCC's court.
>From gcc-bugs-return-605111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 21:41:10 2018
Return-Path: <gcc-bugs-return-605111-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48160 invoked by alias); 19 May 2018 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 48070 invoked by uid 48); 19 May 2018 21:41:06 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85643] attribute nonstring fails to squash -Wstringop-truncation warning at an offset
Date: Sat, 19 May 2018 21:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, patch
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85643-4-eEn9LwMNzW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85643-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85643-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02006.txt.bz2
Content-length: 196
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85643
--- Comment #7 from Martin Sebor <msebor at gcc dot gnu.org> ---
Not yet. It needs to be backported to GCC 8 next week. I'll close it then.
>From gcc-bugs-return-605112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 21:51:42 2018
Return-Path: <gcc-bugs-return-605112-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54809 invoked by alias); 19 May 2018 21:51:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54787 invoked by uid 48); 19 May 2018 21:51:37 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] New: Invalide C++ in libstd++
Date: Sat, 19 May 2018 21:51: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: blocker
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02007.txt.bz2
Content-length: 3972
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
Bug ID: 85843
Summary: Invalide C++ in libstd++
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: blocker
Priority: P3
Component: bootstrap
Assignee: unassigned at gcc dot gnu.org
Reporter: kargl at gcc dot gnu.org
Target Milestone: ---
gmake[6]: Entering directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src/c++11'
/bin/sh ../../libtool --tag CXX --tag disable-shared --mode=compile
/safe/sgk/gcc/obj/./gcc/xgcc -shared-libgcc -B/safe/sgk/gcc/obj/./gcc
-nostdinc++ -L/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src
-L/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src/.libs
-L/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/libsupc++/.libs
-B/safe/sgk/work/x/x86_64-unknown-freebsd12.0/bin/
-B/safe/sgk/work/x/x86_64-unknown-freebsd12.0/lib/ -isystem
/safe/sgk/work/x/x86_64-unknown-freebsd12.0/include -isystem
/safe/sgk/work/x/x86_64-unknown-freebsd12.0/sys-include -fno-checking
-I/safe/sgk/gcc/gcc/libstdc++-v3/../libgcc
-I/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/include/x86_64-unknown-freebsd12.0
-I/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/include
-I/safe/sgk/gcc/gcc/libstdc++-v3/libsupc++ -std=gnu++11 -prefer-pic
-D_GLIBCXX_SHARED -fno-implicit-templates -Wall -Wextra -Wwrite-strings
-Wcast-qual -Wabi -Werror -fdiagnostics-show-location=once
-ffunction-sections -fdata-sections -frandom-seed=cow-stdexcept.lo -g -O2 -c
-o cow-stdexcept.lo ../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc
libtool: compile: /safe/sgk/gcc/obj/./gcc/xgcc -shared-libgcc
-B/safe/sgk/gcc/obj/./gcc -nostdinc++
-L/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src
-L/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src/.libs
-L/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/libsupc++/.libs
-B/safe/sgk/work/x/x86_64-unknown-freebsd12.0/bin/
-B/safe/sgk/work/x/x86_64-unknown-freebsd12.0/lib/ -isystem
/safe/sgk/work/x/x86_64-unknown-freebsd12.0/include -isystem
/safe/sgk/work/x/x86_64-unknown-freebsd12.0/sys-include -fno-checking
-I/safe/sgk/gcc/gcc/libstdc++-v3/../libgcc
-I/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/include/x86_64-unknown-freebsd12.0
-I/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/include
-I/safe/sgk/gcc/gcc/libstdc++-v3/libsupc++ -std=gnu++11 -D_GLIBCXX_SHARED
-fno-implicit-templates -Wall -Wextra -Wwrite-strings -Wcast-qual -Wabi -Werror
-fdiagnostics-show-location=once -ffunction-sections -fdata-sections
-frandom-seed=cow-stdexcept.lo -g -O2 -c
../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc -fPIC -DPIC
-D_GLIBCXX_SHARED -o cow-stdexcept.o
../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc: In copy constructor
'std::logic_error::logic_error(const std::logic_error&)':
../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc:58:3: error: base
class 'class std::exception' should be explicitly initialized in the copy
constructor
[-Werror=extra]
logic_error::logic_error(const logic_error& e) noexcept
^~~~~~~~~~~
../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc: In copy constructor
'std::runtime_error::runtime_error(const std::runtime_error&)':
../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc:64:3: error: base
class 'class std::exception' should be explicitly initialized in the copy
constructor [-Werror=extra]
runtime_error::runtime_error(const runtime_error& e) noexcept
^~~~~~~~~~~~~
cc1plus: all warnings being treated as errors
gmake[6]: *** [Makefile:562: cow-stdexcept.lo] Error 1
gmake[6]: Leaving directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src/c++11'
Making all in filesystem
gmake[6]: Entering directory
'/safe/sgk/gcc/obj/x86_64-unknown-freebsd12.0/libstdc++-v3/src/filesystem'
>From gcc-bugs-return-605113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 21:53:01 2018
Return-Path: <gcc-bugs-return-605113-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56061 invoked by alias); 19 May 2018 21: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 56023 invoked by uid 48); 19 May 2018 21:52:57 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] Invalid C++ in libstd++
Date: Sat, 19 May 2018 21:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: target_milestone short_desc
Message-ID: <bug-85843-4-raWuUEsIAz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02008.txt.bz2
Content-length: 347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |9.0
Summary|Invalide C++ in libstd++ |Invalid C++ in libstd++
>From gcc-bugs-return-605114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 22:46:27 2018
Return-Path: <gcc-bugs-return-605114-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101866 invoked by alias); 19 May 2018 22: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 101640 invoked by uid 48); 19 May 2018 22:45:59 -0000
From: "grgoffe at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85844] New: compile of "latest" dev branch
Date: Sat, 19 May 2018 22:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: grgoffe at yahoo 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-85844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02009.txt.bz2
Content-length: 1652
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85844
Bug ID: 85844
Summary: compile of "latest" dev branch
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: sanitizer
Assignee: unassigned at gcc dot gnu.org
Reporter: grgoffe at yahoo dot 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: ---
Hi,
This is a partial "snip" of the build log. I have a full log available if
necessary. This is VERY close to the latest code in the gcc tree.
Os is Fedora 28 (x86_64)
yes
checking for ceill... yes
checking for copysignf...
../../../../gcc/libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cc:160:10:
fatal error: sys/ustat.h: No such file or directory
#include <sys/ustat.h>
^~~~~~~~~~~~~
compilation terminated.
make[4]: *** [Makefile:539: sanitizer_platform_limits_posix.lo] Error 1
make[4]: Leaving directory
'/export/home/tools/gcc/obj-x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/libsanitizer/sanitizer_common'
make[3]: *** [Makefile:472: all-recursive] Error 1
make[3]: Leaving directory
'/export/home/tools/gcc/obj-x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/libsanitizer'
make[2]: *** [Makefile:342: all] Error 2
make[2]: Leaving directory
'/export/home/tools/gcc/obj-x86_64-pc-linux-gnu/x86_64-pc-linux-gnu/libsanitizer'
make[1]: *** [Makefile:16696: all-target-libsanitizer] Error 2
make[1]: *** Waiting for unfinished jobs....
>From gcc-bugs-return-605116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 22:50:20 2018
Return-Path: <gcc-bugs-return-605116-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108197 invoked by alias); 19 May 2018 22:50: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 107909 invoked by uid 48); 19 May 2018 22:50:16 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85835] libsanitizer includes <sys/ustat.h> unconditionally
Date: Sat, 19 May 2018 22: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: 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: cc
Message-ID: <bug-85835-4-YKFlscHaGY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02011.txt.bz2
Content-length: 443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85835
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |grgoffe at yahoo dot com
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 85844 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-605115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 22:50:18 2018
Return-Path: <gcc-bugs-return-605115-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107991 invoked by alias); 19 May 2018 22: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 107827 invoked by uid 48); 19 May 2018 22:50:14 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85844] compile of "latest" dev branch
Date: Sat, 19 May 2018 22:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85844-4-mm73r2SEjc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85844-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85844-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02010.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85844
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
dup of bug 85835.
*** This bug has been marked as a duplicate of bug 85835 ***
>From gcc-bugs-return-605117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 22:50:56 2018
Return-Path: <gcc-bugs-return-605117-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109815 invoked by alias); 19 May 2018 22: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 109711 invoked by uid 48); 19 May 2018 22:50:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85835] libsanitizer includes <sys/ustat.h> unconditionally
Date: Sat, 19 May 2018 22: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85835-4-5vyg43ImQl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02012.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85835
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-19
Ever confirmed|0 |1
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Did someone report this upstream?
>From gcc-bugs-return-605118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 23:06:06 2018
Return-Path: <gcc-bugs-return-605118-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127337 invoked by alias); 19 May 2018 23: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 127251 invoked by uid 48); 19 May 2018 23:06:01 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85835] libsanitizer includes <sys/ustat.h> unconditionally
Date: Sat, 19 May 2018 23:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: sanitizer
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: 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-85835-4-R2OGaxdGf0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85835-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02013.txt.bz2
Content-length: 242
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85835
--- Comment #3 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Andrew Pinski from comment #2)
> Did someone report this upstream?
https://bugs.llvm.org/show_bug.cgi?id=37418
>From gcc-bugs-return-605119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sat May 19 23:16:16 2018
Return-Path: <gcc-bugs-return-605119-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6756 invoked by alias); 19 May 2018 23:16: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 6633 invoked by uid 48); 19 May 2018 23:16:11 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85845] New: [9 Regression] Many libstdc++ test failures
Date: Sat, 19 May 2018 23: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: 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-85845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02014.txt.bz2
Content-length: 4366
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85845
Bug ID: 85845
Summary: [9 Regression] Many libstdc++ test failures
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
Assignee: unassigned at gcc dot gnu.org
Reporter: hjl.tools at gmail dot com
CC: fdumont at gcc dot gnu.org
Target Milestone: ---
On x86, r260382 caused:
FAIL: 23_containers/map/59872.cc (test for excess errors)
FAIL: 23_containers/map/allocator/minimal.cc (test for excess errors)
FAIL: 23_containers/map/allocator/move.cc (test for excess errors)
FAIL: 23_containers/map/debug/construct5_neg.cc (test for excess errors)
FAIL: 23_containers/map/debug/move_neg.cc (test for excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/1_c++0x.cc (test
for excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/1.cc (test for
excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/2.cc (test for
excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/3.cc (test for
excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/4.cc (test for
excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/5_c++0x.cc (test
for excess errors)
FAIL: 23_containers/map/requirements/explicit_instantiation/5.cc (test for
excess errors)
FAIL: 23_containers/multimap/allocator/minimal.cc (test for excess errors)
FAIL: 23_containers/multimap/allocator/move.cc (test for excess errors)
FAIL: 23_containers/multimap/debug/construct5_neg.cc (test for excess errors)
FAIL: 23_containers/multimap/debug/move_neg.cc (test for excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/1_c++0x.cc
(test for excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/1.cc (test for
excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/2.cc (test for
excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/3.cc (test for
excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/4.cc (test for
excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/5_c++0x.cc
(test for excess errors)
FAIL: 23_containers/multimap/requirements/explicit_instantiation/5.cc (test for
excess errors)
FAIL: 23_containers/multiset/allocator/minimal.cc (test for excess errors)
FAIL: 23_containers/multiset/allocator/move.cc (test for excess errors)
FAIL: 23_containers/multiset/debug/construct5_neg.cc (test for excess errors)
FAIL: 23_containers/multiset/debug/move_neg.cc (test for excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/1_c++0x.cc
(test for excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/1.cc (test for
excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/2.cc (test for
excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/3.cc (test for
excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/4.cc (test for
excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/5_c++0x.cc
(test for excess errors)
FAIL: 23_containers/multiset/requirements/explicit_instantiation/5.cc (test for
excess errors)
FAIL: 23_containers/set/allocator/minimal.cc (test for excess errors)
FAIL: 23_containers/set/allocator/move.cc (test for excess errors)
FAIL: 23_containers/set/debug/construct5_neg.cc (test for excess errors)
FAIL: 23_containers/set/debug/move_neg.cc (test for excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/1_c++0x.cc (test
for excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/1.cc (test for
excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/2.cc (test for
excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/3.cc (test for
excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/4.cc (test for
excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/5_c++0x.cc (test
for excess errors)
FAIL: 23_containers/set/requirements/explicit_instantiation/5.cc (test for
excess errors)
>From gcc-bugs-return-605120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 00:51:43 2018
Return-Path: <gcc-bugs-return-605120-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80654 invoked by alias); 20 May 2018 00: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 76089 invoked by uid 48); 20 May 2018 00:51:39 -0000
From: "hstong at ca dot ibm.com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85846] New: [Concepts] Concept as value in initializer: bogus declared-as-implicit-template error
Date: Sun, 20 May 2018 00:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hstong at ca dot ibm.com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02015.txt.bz2
Content-length: 1877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85846
Bug ID: 85846
Summary: [Concepts] Concept as value in initializer: bogus
declared-as-implicit-template error
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: hstong at ca dot ibm.com
Target Milestone: ---
When a concept with a non-type prototype parameter is used as a variable
template in a context where the most vexing parse would prefer interpretation
of an ambiguous construct as naming a type, GCC produces a bogus message
about creating an implicit non-function template.
In the case below, either f is being declared as a function, or Foo<> cannot
be considered a type (and therefore, it cannot cause formation of an implicit
template through the abbreviated function template mechanism).
### SOURCE (<stdin>):
template <int = 0> concept bool Foo = true;
bool f(Foo<>);
### COMPILER INVOCATION:
g++ -fsyntax-only -xc++ -fconcepts -
### ACTUAL OUTPUT:
<stdin>:2:6: error: non-function 'f' declared as implicit template
### EXPECTED OUTPUT:
(Clean compile).
### COMPILER VERSION INFO (g++ -v):
Using built-in specs.
COLLECT_GCC=/opt/wandbox/gcc-head/bin/g++
COLLECT_LTO_WRAPPER=/opt/wandbox/gcc-head/libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: ../source/configure --prefix=/opt/wandbox/gcc-head
--enable-languages=c,c++ --disable-multilib --without-ppl --without-cloog-ppl
--enable-checking=release --disable-nls --enable-lto
LDFLAGS=-Wl,-rpath,/opt/wandbox/gcc-head/lib,-rpath,/opt/wandbox/gcc-head/lib64,-rpath,/opt/wandbox/gcc-head/lib32
Thread model: posix
gcc version 9.0.0 20180518 (experimental) (GCC)
>From gcc-bugs-return-605121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 03:47:08 2018
Return-Path: <gcc-bugs-return-605121-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55305 invoked by alias); 20 May 2018 03:47: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 54520 invoked by uid 55); 20 May 2018 03:47:00 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] Invalid C++ in libstd++
Date: Sun, 20 May 2018 03:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85843-4-5IhDRQZ59z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02016.txt.bz2
Content-length: 630
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
--- Comment #1 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sat, May 19, 2018 at 09:52:57PM +0000, kargl at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
>
> kargl at gcc dot gnu.org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Target Milestone|--- |9.0
> Summary|Invalide C++ in libstd++ |Invalid C++ in libstd++
>
This is fixed by
svn merge -rhead:260263 .
>From gcc-bugs-return-605122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 04:12:27 2018
Return-Path: <gcc-bugs-return-605122-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72359 invoked by alias); 20 May 2018 04:12: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 72217 invoked by uid 48); 20 May 2018 04:12:18 -0000
From: "tpearson at raptorengineering dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85216] Performance issue with PHP on ppc64 systems
Date: Sun, 20 May 2018 04:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tpearson at raptorengineering dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85216-4-eqchWVHx9r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02017.txt.bz2
Content-length: 764
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85216
--- Comment #12 from Timothy Pearson <tpearson at raptorengineering dot com> ---
After quite a bit of investigation, this is down to the Spectre v2 user mode
protections on POWER9, which (from what I understand) involve completely
disabling the branch predictor.
My question then comes down to, why wasn't the retpoline style mitigation used
on ppc64el? Nuking hardware elements seems extreme and is obviously causing
serious problems for direct branching code (like that being seen here).
What would be involved in creating a retpoline-type mitigation for ppc64el, so
that we can run with the branch predictor turned back on (already verified to
fix much of the performance issues seen on POWER9)?
>From gcc-bugs-return-605123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 04:19:10 2018
Return-Path: <gcc-bugs-return-605123-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76150 invoked by alias); 20 May 2018 04: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 75978 invoked by uid 48); 20 May 2018 04:18:51 -0000
From: "adrienstalain at hotmail dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85847] New: unexpected expression of kind template_id_expr
Date: Sun, 20 May 2018 04:19:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: adrienstalain at hotmail dot fr
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-85847-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02018.txt.bz2
Content-length: 1771
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85847
Bug ID: 85847
Summary: unexpected expression of kind template_id_expr
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: adrienstalain at hotmail dot fr
Target Milestone: ---
Created attachment 44149
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44149&action=edit
test source
* command to reproduce
$ g++ test.cc
* Compiler output:
```
test.cc: In function ‘void g()’:
test.cc:7:32: internal compiler error: unexpected expression ‘f<int>’ of kind
template_id_expr
auto a = new int[f<int>(2), 2];
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
```
* gcc version 8.1.0 (GCC)
*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
>From gcc-bugs-return-605124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 04:39:34 2018
Return-Path: <gcc-bugs-return-605124-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92835 invoked by alias); 20 May 2018 04:39: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 92799 invoked by uid 55); 20 May 2018 04:39:27 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] Invalid C++ in libstd++
Date: Sun, 20 May 2018 04:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: blocker
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85843-4-iLyroX6p5K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02019.txt.bz2
Content-length: 415
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
--- Comment #2 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, May 20, 2018 at 03:46:59AM +0000, sgk at troutmask dot
apl.washington.edu wrote:
>
> svn merge -rhead:260263 .
>
Further bisection.
svn merge -r260380:260379 .
So, r260380 is the cause of the bootstrap issue.
Can someone please fix the issue or revert the patch?
>From gcc-bugs-return-605125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 04:43:24 2018
Return-Path: <gcc-bugs-return-605125-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95454 invoked by alias); 20 May 2018 04:43: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 95366 invoked by uid 48); 20 May 2018 04:43:14 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] Invalid C++ in libstd++
Date: Sun, 20 May 2018 04:43: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: blocker
X-Bugzilla-Who: kargl 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-85843-4-85Ug3geyqV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02020.txt.bz2
Content-length: 346
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P1
CC| |jason at redhat dot com
>From gcc-bugs-return-605126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 09:05:53 2018
Return-Path: <gcc-bugs-return-605126-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30035 invoked by alias); 20 May 2018 09: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 29920 invoked by uid 48); 20 May 2018 09:05:47 -0000
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85845] [9 Regression] Many libstdc++ test failures
Date: Sun, 20 May 2018 09:05: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: ro at gcc dot gnu.org
X-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 everconfirmed
Message-ID: <bug-85845-4-tVWKSksu5J@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02021.txt.bz2
Content-length: 1520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85845
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-20
CC| |ro at gcc dot gnu.org
Target Milestone|--- |9.0
Ever confirmed|0 |1
--- Comment #1 from Rainer Orth <ro at gcc dot gnu.org> ---
E.g. on i386-pc-solaris2.11, I get
FAIL: 23_containers/map/59872.cc (test for excess errors)
Excess errors:
/var/gcc/regression/trunk/11.4-gcc/build/i386-pc-solaris2.11/libstdc++-v3/include/bits/stl_tree.h:983:
error: no matching function for call to 'std::_Rb_tree<int, std::pair<const
int, MoveOnly>, std::_Select1st<std::pair<const int, MoveOnly> >,
std::less<int>, std::allocator<std::pair<const int, MoveOnly> >
>::_Rb_tree(std::_Rb_tree<int, std::pair<const int, MoveOnly>,
std::_Select1st<std::pair<const int, MoveOnly> >, std::less<int>,
std::allocator<std::pair<const int, MoveOnly> > >, std::_Rb_tree<int,
std::pair<const int, MoveOnly>, std::_Select1st<std::pair<const int, MoveOnly>
>, std::less<int>, std::allocator<std::pair<const int, MoveOnly> > >,
std::_Rb_tree<int, std::pair<const int, MoveOnly>,
std::_Select1st<std::pair<const int, MoveOnly> >, std::less<int>,
std::allocator<std::pair<const int, MoveOnly> > >)'
>From gcc-bugs-return-605127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 09:06:52 2018
Return-Path: <gcc-bugs-return-605127-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31151 invoked by alias); 20 May 2018 09:06: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 30997 invoked by uid 48); 20 May 2018 09:06:40 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/67958] The tests changed by r223498 now FAILs on darwin
Date: Sun, 20 May 2018 09:06: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: 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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-67958-4-GEBnmEsGHb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-67958-4@http.gcc.gnu.org/bugzilla/>
References: <bug-67958-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02022.txt.bz2
Content-length: 385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67958
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> > Created attachment 39731 [details]
> > Patch fixing the failures with the patches for pr71767
>
> please send this patch to gcc-patches for review
This patch has never been intended to be submitted for review: it does not take
into account comment 2.
>From gcc-bugs-return-605128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:01:33 2018
Return-Path: <gcc-bugs-return-605128-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3425 invoked by alias); 20 May 2018 10: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 3056 invoked by uid 55); 20 May 2018 10:01:01 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sun, 20 May 2018 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
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:
Message-ID: <bug-82923-4-elrcVrUPdP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02023.txt.bz2
Content-length: 998
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #12 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 09:59:54 2018
New Revision: 260413
URL: https://gcc.gnu.org/viewcvs?rev=260413&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/select_type_42.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/match.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:01:33 2018
Return-Path: <gcc-bugs-return-605130-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3591 invoked by alias); 20 May 2018 10:01: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 3053 invoked by uid 55); 20 May 2018 10:01:01 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Sun, 20 May 2018 10: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.2
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66694-4-W2Zkix6r7P@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02024.txt.bz2
Content-length: 997
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 09:59:54 2018
New Revision: 260413
URL: https://gcc.gnu.org/viewcvs?rev=260413&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/select_type_42.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/match.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:01:34 2018
Return-Path: <gcc-bugs-return-605129-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 3534 invoked by alias); 20 May 2018 10:01:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 3059 invoked by uid 55); 20 May 2018 10:01:01 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82617] Internal compiler error in expand_expr_real_1 when compiling the attached file
Date: Sun, 20 May 2018 10:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords:
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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82617-4-COaF4mKQRH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02025.txt.bz2
Content-length: 997
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82617
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 09:59:54 2018
New Revision: 260413
URL: https://gcc.gnu.org/viewcvs?rev=260413&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/select_type_42.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/match.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:05:26 2018
Return-Path: <gcc-bugs-return-605131-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8743 invoked by alias); 20 May 2018 10:05:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8584 invoked by uid 55); 20 May 2018 10:05:18 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49636] [F03] ASSOCIATE construct confused with slightly complicated case
Date: Sun, 20 May 2018 10:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-49636-4-vjl56BdM80@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02026.txt.bz2
Content-length: 1091
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49636
--- Comment #12 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 10:04:46 2018
New Revision: 260414
URL: https://gcc.gnu.org/viewcvs?rev=260414&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/49636
* trans-array.c (gfc_get_array_span): Renamed from
'get_array_span'.
(gfc_conv_expr_descriptor): Change references to above.
* trans-array.h : Add prototype for 'gfc_get_array_span'.
* trans-stmt.c (trans_associate_var): If the associate name is
a subref array pointer, use gfc_get_array_span for the span.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/49636
* gfortran.dg/associate_38.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/associate_38.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/trans-array.c
trunk/gcc/fortran/trans-array.h
trunk/gcc/fortran/trans-intrinsic.c
trunk/gcc/fortran/trans-stmt.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:09:02 2018
Return-Path: <gcc-bugs-return-605132-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16524 invoked by alias); 20 May 2018 10:09:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16433 invoked by uid 55); 20 May 2018 10:08:56 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80657] [7/8/9 Regression] Loop in character function declaration
Date: Sun, 20 May 2018 10: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: 7.1.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80657-4-4Lo94ntzlj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02027.txt.bz2
Content-length: 872
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80657
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 10:08:24 2018
New Revision: 260415
URL: https://gcc.gnu.org/viewcvs?rev=260415&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/80657
* resolve.c (flag_fn_result_spec): Use the 'sym' argument to
test for self refs to the function result in the character len
expression. If a self reference is found, emit an error and
return true.
(resolve_fntype): Use the function symbol in the calls to the
above.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/80657
* gfortran.dg/char_result_18.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/char_result_18.f90
Modified:
trunk/gcc/fortran/resolve.c
>From gcc-bugs-return-605133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:18:49 2018
Return-Path: <gcc-bugs-return-605133-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 35092 invoked by alias); 20 May 2018 10:18:49 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 35037 invoked by uid 48); 20 May 2018 10:18:44 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82923] Automatic allocation of deferred length character using function result
Date: Sun, 20 May 2018 10: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.2.0
X-Bugzilla-Keywords:
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:
Message-ID: <bug-82923-4-UDLDvlfU7n@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02028.txt.bz2
Content-length: 355
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82923
--- Comment #13 from Paul Thomas <pault at gcc dot gnu.org> ---
>
> Added:
> trunk/gcc/testsuite/gfortran.dg/select_type_42.f90
> Modified:
> trunk/gcc/fortran/ChangeLog
> trunk/gcc/fortran/match.c
> trunk/gcc/testsuite/ChangeLog
Sorry, this last was the patch for PR80657
Paul.
>From gcc-bugs-return-605134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:46:31 2018
Return-Path: <gcc-bugs-return-605134-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95969 invoked by alias); 20 May 2018 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 95835 invoked by uid 48); 20 May 2018 10:46:26 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/83146] [6/7/8/9 Regression] ICE on SELECT CASE statement with associate name
Date: Sun, 20 May 2018 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: 8.0
X-Bugzilla-Keywords: ice-on-valid-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: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-83146-4-EFqBiHHo6h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83146-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83146-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02029.txt.bz2
Content-length: 464
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83146
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |pault at gcc dot gnu.org
--- Comment #4 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
AFAICT this seems fixed by a recent patch, likely r260414 for pr49636.
>From gcc-bugs-return-605135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 10:55:01 2018
Return-Path: <gcc-bugs-return-605135-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104651 invoked by alias); 20 May 2018 10:55: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 104546 invoked by uid 55); 20 May 2018 10:54:56 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82275] gfortran rejects valid & accepts invalid reference to dimension-remapped type SELECT TYPE selector
Date: Sun, 20 May 2018 10:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82275-4-Oy51NJAAIs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02030.txt.bz2
Content-length: 725
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82275
--- Comment #5 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 10:54:24 2018
New Revision: 260416
URL: https://gcc.gnu.org/viewcvs?rev=260416&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82275
Correcting ChangeLogs
* match.c (gfc_match_type_spec): Go through the array ref and
decrement 'rank' for every dimension that is an element.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82275
Correcting ChangeLogs
* gfortran.dg/select_type_42.f90: New test.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 11:04:51 2018
Return-Path: <gcc-bugs-return-605136-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114672 invoked by alias); 20 May 2018 11:04:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114612 invoked by uid 55); 20 May 2018 11:04:47 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82275] gfortran rejects valid & accepts invalid reference to dimension-remapped type SELECT TYPE selector
Date: Sun, 20 May 2018 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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82275-4-EM74gzlp5s@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02031.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82275
--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 11:04:14 2018
New Revision: 260417
URL: https://gcc.gnu.org/viewcvs?rev=260417&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82275
Backport from trunk
* match.c (gfc_match_type_spec): Go through the array ref and
decrement 'rank' for every dimension that is an element.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82275
Backport from trunk
* gfortran.dg/select_type_42.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/select_type_42.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/match.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 11:08:22 2018
Return-Path: <gcc-bugs-return-605137-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117763 invoked by alias); 20 May 2018 11:08:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 117679 invoked by uid 55); 20 May 2018 11:08:17 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49636] [F03] ASSOCIATE construct confused with slightly complicated case
Date: Sun, 20 May 2018 11: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.6.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-49636-4-9miC84cgRi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02032.txt.bz2
Content-length: 1203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49636
--- Comment #13 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 11:07:44 2018
New Revision: 260418
URL: https://gcc.gnu.org/viewcvs?rev=260418&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/49636
Backport from trunk
* trans-array.c (gfc_get_array_span): Renamed from
'get_array_span'.
(gfc_conv_expr_descriptor): Change references to above.
* trans-array.h : Add prototype for 'gfc_get_array_span'.
* trans-stmt.c (trans_associate_var): If the associate name is
a subref array pointer, use gfc_get_array_span for the span.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/49636
Backport from trunk
* gfortran.dg/associate_38.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/associate_38.f90
Modified:
branches/gcc-8-branch/gcc/fortran/ChangeLog
branches/gcc-8-branch/gcc/fortran/trans-array.c
branches/gcc-8-branch/gcc/fortran/trans-array.h
branches/gcc-8-branch/gcc/fortran/trans-stmt.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 11:13:32 2018
Return-Path: <gcc-bugs-return-605138-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4385 invoked by alias); 20 May 2018 11:13: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 4296 invoked by uid 55); 20 May 2018 11:13:25 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80657] [7/8/9 Regression] Loop in character function declaration
Date: Sun, 20 May 2018 11: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.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80657-4-b3N0U2E97K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02033.txt.bz2
Content-length: 1058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80657
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 11:12:53 2018
New Revision: 260419
URL: https://gcc.gnu.org/viewcvs?rev=260419&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/80657
Backport from trunk
* resolve.c (flag_fn_result_spec): Use the 'sym' argument to
test for self refs to the function result in the character len
expression. If a self reference is found, emit an error and
return true.
(resolve_fntype): Use the function symbol in the calls to the
above.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/80657
Backport from trunk
* gfortran.dg/char_result_18.f90: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/char_result_18.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-605139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 11:57:57 2018
Return-Path: <gcc-bugs-return-605139-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33586 invoked by alias); 20 May 2018 11: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 33551 invoked by uid 48); 20 May 2018 11:57:52 -0000
From: "kot.tom97 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85848] New: Incorrect handling of explicit casting to move-only types
Date: Sun, 20 May 2018 11: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kot.tom97 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-85848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02034.txt.bz2
Content-length: 561
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85848
Bug ID: 85848
Summary: Incorrect handling of explicit casting to move-only
types
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: kot.tom97 at gmail dot com
Target Milestone: ---
See
https://stackoverflow.com/questions/50430149/clang-vs-gcc-when-static-casting-to-a-move-only-type.
>From gcc-bugs-return-605140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 12:11:23 2018
Return-Path: <gcc-bugs-return-605140-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87232 invoked by alias); 20 May 2018 12:11: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 87139 invoked by uid 48); 20 May 2018 12:11:18 -0000
From: "glaubitz at physik dot fu-berlin.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/81084] [8 Regression] powerpcspe port full of confusing configury / command-line options not related to SPE
Date: Sun, 20 May 2018 12:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: andrewjenner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81084-4-FUZV96r4MS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81084-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81084-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02035.txt.bz2
Content-length: 244
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81084
--- Comment #57 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> ---
Andrew, could you refresh your patch for the current trunk branch?
It doesn't fully apply for me.
>From gcc-bugs-return-605141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 12:18:54 2018
Return-Path: <gcc-bugs-return-605141-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 93329 invoked by alias); 20 May 2018 12:18:54 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93303 invoked by uid 48); 20 May 2018 12:18:49 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Sun, 20 May 2018 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: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus 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-85841-4-EfNkwo8o3L@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02036.txt.bz2
Content-length: 269
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
--- Comment #2 from janus at gcc dot gnu.org ---
(In reply to Dominique d'Humieres from comment #1)
> This PR could probably merged with pr85839.
They're somewhat related, but I opened two separate PRs on purpose!
>From gcc-bugs-return-605142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 12:53:37 2018
Return-Path: <gcc-bugs-return-605142-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40757 invoked by alias); 20 May 2018 12:53:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 40700 invoked by uid 48); 20 May 2018 12:53:33 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85849] New: [9 Regression] -O3 bootstrap failure
Date: Sun, 20 May 2018 12:53: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 cc target_milestone
Message-ID: <bug-85849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02037.txt.bz2
Content-length: 3406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85849
Bug ID: 85849
Summary: [9 Regression] -O3 bootstrap failure
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
CC: rguenther at suse dot de
Target Milestone: ---
On x86-64, r260318 caused:
/export/gnu/import/git/gcc-test/bld/./prev-gcc/xg++
-B/export/gnu/import/git/gcc-test/bld/./prev-gcc/
-B/usr/9.0.0/x86_64-pc-linux-gnu/bin/ -nostdinc++
-B/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-B/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-I/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
-I/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/include
-I/export/gnu/import/git/gcc-test/src-trunk/libstdc++-v3/libsupc++
-L/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
-L/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
-fno-PIE -c -O3 -g -fno-checking -gtoggle -DIN_GCC -fno-exceptions
-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings
-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common
-DHAVE_CONFIG_H -I. -I. -I../../src-trunk/gcc -I../../src-trunk/gcc/.
-I../../src-trunk/gcc/../include -I../../src-trunk/gcc/../libcpp/include
-I../../src-trunk/gcc/../libdecnumber -I../../src-trunk/gcc/../libdecnumber/bid
-I../libdecnumber -I../../src-trunk/gcc/../libbacktrace -o asan.o -MT asan.o
-MMD -MP -MF ./.deps/asan.TPo ../../src-trunk/gcc/asan.c
during GIMPLE pass: fre
../../src-trunk/gcc/asan.c: In function \u2018rtx_insn*
asan_emit_stack_protection(rtx, rtx, unsigned int, long int*, tree_node**,
int)\u2019:
../../src-trunk/gcc/asan.c:1252:1: internal compiler error: in set_ssa_val_to,
at tree-ssa-sccvn.c:3396
asan_emit_stack_protection (rtx base, rtx pbase, unsigned int alignb,
^~~~~~~~~~~~~~~~~~~~~~~~~~
0x14b6002 set_ssa_val_to
../../src-trunk/gcc/tree-ssa-sccvn.c:3393
0x14b783d visit_reference_op_load
../../src-trunk/gcc/tree-ssa-sccvn.c:3827
0x14b851c visit_use
../../src-trunk/gcc/tree-ssa-sccvn.c:4154
0x14b9169 process_scc
../../src-trunk/gcc/tree-ssa-sccvn.c:4416
0x14b95ad extract_and_process_scc_for_name
../../src-trunk/gcc/tree-ssa-sccvn.c:4487
0x14b9756 DFS
../../src-trunk/gcc/tree-ssa-sccvn.c:4537
0x14baf68 sccvn_dom_walker::before_dom_children(basic_block_def*)
../../src-trunk/gcc/tree-ssa-sccvn.c:4970
0x1da2b13 dom_walker::walk(basic_block_def*)
../../src-trunk/gcc/domwalk.c:353
0x14bb58b run_scc_vn(vn_lookup_kind)
../../src-trunk/gcc/tree-ssa-sccvn.c:5086
0x14bec9a execute
../../src-trunk/gcc/tree-ssa-sccvn.c:6068
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.
when GCC is configured with
--with-build-config='bootstrap-O3 bootstrap-debug' --disable-werror
>From gcc-bugs-return-605143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 13:09:53 2018
Return-Path: <gcc-bugs-return-605143-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73626 invoked by alias); 20 May 2018 13:09: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 73580 invoked by uid 55); 20 May 2018 13:09:48 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85849] [9 Regression] -O3 bootstrap failure
Date: Sun, 20 May 2018 13:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenther at suse dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85849-4-3JsgaIwin9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02038.txt.bz2
Content-length: 3733
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85849
--- Comment #1 from rguenther at suse dot de <rguenther at suse dot de> ---
On May 20, 2018 2:53:31 PM GMT+02:00, "hjl.tools at gmail dot com"
<gcc-bugzilla@gcc.gnu.org> wrote:
>https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85849
>
> Bug ID: 85849
> Summary: [9 Regression] -O3 bootstrap failure
> 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
> CC: rguenther at suse dot de
> Target Milestone: ---
>
>On x86-64, r260318 caused:
>
>/export/gnu/import/git/gcc-test/bld/./prev-gcc/xg++
>-B/export/gnu/import/git/gcc-test/bld/./prev-gcc/
>-B/usr/9.0.0/x86_64-pc-linux-gnu/bin/ -nostdinc++
>-B/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
>-B/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
>
>-I/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/include/x86_64-pc-linux-gnu
>
>-I/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/include
> -I/export/gnu/import/git/gcc-test/src-trunk/libstdc++-v3/libsupc++
>-L/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/src/.libs
>-L/export/gnu/import/git/gcc-test/bld/prev-x86_64-pc-linux-gnu/libstdc++-v3/libsupc++/.libs
>-fno-PIE -c -O3 -g -fno-checking -gtoggle -DIN_GCC
>-fno-exceptions
>-fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing
>-Wwrite-strings
>-Wcast-qual -Wmissing-format-attribute -Woverloaded-virtual -pedantic
>-Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -fno-common
>
>-DHAVE_CONFIG_H -I. -I. -I../../src-trunk/gcc -I../../src-trunk/gcc/.
>-I../../src-trunk/gcc/../include
>-I../../src-trunk/gcc/../libcpp/include
>-I../../src-trunk/gcc/../libdecnumber
>-I../../src-trunk/gcc/../libdecnumber/bid
>-I../libdecnumber -I../../src-trunk/gcc/../libbacktrace -o asan.o -MT
>asan.o
>-MMD -MP -MF ./.deps/asan.TPo ../../src-trunk/gcc/asan.c
>during GIMPLE pass: fre
>../../src-trunk/gcc/asan.c: In function \u2018rtx_insn*
>asan_emit_stack_protection(rtx, rtx, unsigned int, long int*,
>tree_node**,
>int)\u2019:
>../../src-trunk/gcc/asan.c:1252:1: internal compiler error: in
>set_ssa_val_to,
>at tree-ssa-sccvn.c:3396
> asan_emit_stack_protection (rtx base, rtx pbase, unsigned int alignb,
> ^~~~~~~~~~~~~~~~~~~~~~~~~~
>0x14b6002 set_ssa_val_to
> ../../src-trunk/gcc/tree-ssa-sccvn.c:3393
>0x14b783d visit_reference_op_load
> ../../src-trunk/gcc/tree-ssa-sccvn.c:3827
>0x14b851c visit_use
> ../../src-trunk/gcc/tree-ssa-sccvn.c:4154
>0x14b9169 process_scc
> ../../src-trunk/gcc/tree-ssa-sccvn.c:4416
>0x14b95ad extract_and_process_scc_for_name
> ../../src-trunk/gcc/tree-ssa-sccvn.c:4487
>0x14b9756 DFS
> ../../src-trunk/gcc/tree-ssa-sccvn.c:4537
>0x14baf68 sccvn_dom_walker::before_dom_children(basic_block_def*)
> ../../src-trunk/gcc/tree-ssa-sccvn.c:4970
>0x1da2b13 dom_walker::walk(basic_block_def*)
> ../../src-trunk/gcc/domwalk.c:353
>0x14bb58b run_scc_vn(vn_lookup_kind)
> ../../src-trunk/gcc/tree-ssa-sccvn.c:5086
>0x14bec9a execute
> ../../src-trunk/gcc/tree-ssa-sccvn.c:6068
>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.
>
>when GCC is configured with
>
>--with-build-config='bootstrap-O3 bootstrap-debug' --disable-werror
Dup of PR85834
>From gcc-bugs-return-605144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 13:11:50 2018
Return-Path: <gcc-bugs-return-605144-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76851 invoked by alias); 20 May 2018 13:11: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 76781 invoked by uid 48); 20 May 2018 13:11:45 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85786] [8/9 Regression] Segfault in associated intrinsic
Date: Sun, 20 May 2018 13:11:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dominiq at lps dot ens.fr
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85786-4-wbUuyO5zjT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02039.txt.bz2
Content-length: 259
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786
--- Comment #9 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
If I am not mistaken (problem with the change log entry), the patch in comment
5 has been included in revision r260414 (pr49636).
>From gcc-bugs-return-605145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 13:43:34 2018
Return-Path: <gcc-bugs-return-605145-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27011 invoked by alias); 20 May 2018 13:43: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 26345 invoked by uid 48); 20 May 2018 13:43:28 -0000
From: "jjcogliati-r1 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Sun, 20 May 2018 13:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jjcogliati-r1 at yahoo 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
Message-ID: <bug-85840-4-Ev9kw8HMae@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02040.txt.bz2
Content-length: 1897
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
Joshua Cogliati <jjcogliati-r1 at yahoo dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jjcogliati-r1 at yahoo dot com
--- Comment #2 from Joshua Cogliati <jjcogliati-r1 at yahoo dot com> ---
I haven't found a short reproducer yet.
Here is how I can reproduce it.
Get marbles from:
http://jjc.freeshell.org/marbles/marbles.tar.gz
tar -xzf marbles.tar.gz
cd marbles/src
cat > short <<EOF
runs 100
done
EOF
make
valgrind --leak-check=full ./marbles9 short
and with that you get output like:
==15790== 646,000 bytes in 2,000 blocks are definitely lost in loss record 65
of 70
==15790== at 0x4C2CB6B: malloc (vg_replace_malloc.c:299)
==15790== by 0x4E53454: _gfortrani_xmalloc (memory.c:42)
==15790== by 0x4FD637A: write_float_0 (write.c:1593)
==15790== by 0x4FCD98C: formatted_transfer_scalar_write (transfer.c:2041)
==15790== by 0x4FCDF9C: formatted_transfer (transfer.c:2279)
==15790== by 0x421CC6:
__marbles9_common_module_MOD_display_pebble_info.constprop.72
(marbles9_common_module.f90:1058)
==15790== by 0x4061EA: do_runs.3497 (marbles9.f90:611)
==15790== by 0x40CB2D: MAIN__ (marbles9.f90:497)
==15790== by 0x4011EC: main (marbles9.f90:42)
The line marbles9_common_module.f90:1058
is
PRINT '(A3,I6,9(1X,F0.11))',"P:
",j,pp(j)%x,pp(j)%y,pp(j)%z,pv(j)%x,pv(j)%y,pv(j)%z,pw(j)%x,pw(j)%y,pw(j)%z
with inputs that take longer to run, I can also get it to trigger on other
lines such as 1124:
print '(A16,I7,6E25.16E3)',"#P_surface_slip ",i,&
current_state%pss(i)%x,current_state%pss(i)%y,&
current_state%pss(i)%z,0.0,0.0,0.0
>From gcc-bugs-return-605146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 14:12:36 2018
Return-Path: <gcc-bugs-return-605146-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102721 invoked by alias); 20 May 2018 14:12:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 100294 invoked by uid 48); 20 May 2018 14:12:32 -0000
From: "jjcogliati-r1 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Sun, 20 May 2018 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: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jjcogliati-r1 at yahoo 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: attachments.created
Message-ID: <bug-85840-4-UU31vQckF4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02041.txt.bz2
Content-length: 265
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
--- Comment #3 from Joshua Cogliati <jjcogliati-r1 at yahoo dot com> ---
Created attachment 44150
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44150&action=edit
simple program to demonstrate problem
>From gcc-bugs-return-605148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 14:34:53 2018
Return-Path: <gcc-bugs-return-605148-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103326 invoked by alias); 20 May 2018 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 103208 invoked by uid 48); 20 May 2018 14:34:49 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Sun, 20 May 2018 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: build, ice-on-valid-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: cc
Message-ID: <bug-85834-4-QHKnDWcLWK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02043.txt.bz2
Content-length: 433
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |hjl.tools at gmail dot com
--- Comment #5 from H.J. Lu <hjl.tools at gmail dot com> ---
*** Bug 85849 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-605147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 14:34:53 2018
Return-Path: <gcc-bugs-return-605147-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103266 invoked by alias); 20 May 2018 14:34: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 103177 invoked by uid 48); 20 May 2018 14:34:48 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85849] [9 Regression] -O3 bootstrap failure
Date: Sun, 20 May 2018 14:34: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: hjl.tools at gmail dot com
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85849-4-gJ4AwUBAfL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85849-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85849-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02042.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85849
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from H.J. Lu <hjl.tools at gmail dot com> ---
Dup.
*** This bug has been marked as a duplicate of bug 85834 ***
>From gcc-bugs-return-605149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 14:35:25 2018
Return-Path: <gcc-bugs-return-605149-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105385 invoked by alias); 20 May 2018 14:35: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 105262 invoked by uid 48); 20 May 2018 14:35:18 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] [9 regression] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Sun, 20 May 2018 14:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, ice-on-valid-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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone short_desc everconfirmed
Message-ID: <bug-85834-4-RlwuWTLLE3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02044.txt.bz2
Content-length: 660
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
H.J. Lu <hjl.tools at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-20
Target Milestone|--- |9.0
Summary|ice in set_ssa_val_to, at |[9 regression] ice in
|tree-ssa-sccvn.c:3396 |set_ssa_val_to, at
| |tree-ssa-sccvn.c:3396
Ever confirmed|0 |1
>From gcc-bugs-return-605150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 14:38:33 2018
Return-Path: <gcc-bugs-return-605150-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 108505 invoked by alias); 20 May 2018 14:38: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 108426 invoked by uid 48); 20 May 2018 14:38:28 -0000
From: "jjcogliati-r1 at yahoo dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Sun, 20 May 2018 14:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jjcogliati-r1 at yahoo 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-85840-4-FLKythkfss@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02045.txt.bz2
Content-length: 837
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
--- Comment #4 from Joshua Cogliati <jjcogliati-r1 at yahoo dot com> ---
And to replicate it with the simple program:
gfortran -Wall -g -o simple simple.f90
valgrind --leak-check=full ./simple
and you get things like:
==19171== 323 bytes in 1 blocks are definitely lost in loss record 4 of 4
==19171== at 0x4C2CB6B: malloc (vg_replace_malloc.c:299)
==19171== by 0x4E53454: _gfortrani_xmalloc (memory.c:42)
==19171== by 0x4FD637A: write_float_0 (write.c:1593)
==19171== by 0x4FCD98C: formatted_transfer_scalar_write (transfer.c:2041)
==19171== by 0x4FCDF9C: formatted_transfer (transfer.c:2279)
==19171== by 0x4008A5: MAIN__ (simple.f90:10)
==19171== by 0x4008EB: main (simple.f90:11)
>From gcc-bugs-return-605151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 15:54:20 2018
Return-Path: <gcc-bugs-return-605151-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80697 invoked by alias); 20 May 2018 15:54:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 80608 invoked by uid 48); 20 May 2018 15:54:10 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85829] [8/9 Regression] PARTIAL_REG_DEPENDENCY and MOVX were disabled for Haswell and newer processors
Date: Sun, 20 May 2018 15: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85829-4-sEq3jmUq0R@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02046.txt.bz2
Content-length: 334
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85829
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Jan Hubicka from comment #3)
>
> So I would suggest to revisit PARTIAL_REG_DEPENDENCY wrt PARTIAL_REG_STALL
> for Haswell+
We should do that for GCC 9. For GCC 8, we should restore what we had
before.
>From gcc-bugs-return-605152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 16:47:57 2018
Return-Path: <gcc-bugs-return-605152-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1814 invoked by alias); 20 May 2018 16:47:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1718 invoked by uid 48); 20 May 2018 16:47:52 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/28689] Cross compile internal error.
Date: Sun, 20 May 2018 16:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.1.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: WORKSFORME
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-28689-4-sQu7kX6c9K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-28689-4@http.gcc.gnu.org/bugzilla/>
References: <bug-28689-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02047.txt.bz2
Content-length: 784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=28689
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #9 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #7)
> (In reply to Lee Adamson from comment #6)
> > Same thing also happens if I build a sparc-sun-solaris2.8 to
> > i686-pc-linux-gnu cross compiler.
>
> Does it still happen with newer versions of gcc?
No reply in 3 months since being put in WAITING; guess I'll close it...
(feel free to reopen if necessary)
>From gcc-bugs-return-605153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 16:50:57 2018
Return-Path: <gcc-bugs-return-605153-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4371 invoked by alias); 20 May 2018 16: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 4309 invoked by uid 48); 20 May 2018 16:50:52 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/72769] ifstream Optimed Out ?
Date: Sun, 20 May 2018 16: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: 6.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager 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-72769-4-eV4iZNtwH3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-72769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-72769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02048.txt.bz2
Content-length: 715
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72769
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> (In reply to Roy Bellingan from comment #3)
> > No wait I was quite busy -.-
> > Ok to keep close for now, I will try to provide better info soon.
>
> Putting in WAITING until then
...and closing again, since there's still no better info.
>From gcc-bugs-return-605154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 16:57:57 2018
Return-Path: <gcc-bugs-return-605154-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8698 invoked by alias); 20 May 2018 16: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 8624 invoked by uid 48); 20 May 2018 16:57:52 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85786] [8/9 Regression] Segfault in associated intrinsic
Date: Sun, 20 May 2018 16: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: 8.1.0
X-Bugzilla-Keywords: wrong-code
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:
Message-ID: <bug-85786-4-qs3uisaPVu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02049.txt.bz2
Content-length: 711
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786
--- Comment #10 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #9)
> If I am not mistaken (problem with the change log entry), the patch in
> comment 5 has been included in revision r260414 (pr49636).
Yes, you are right. I totally bolloxed up the the commits that I made this
morning. I scrambled the ChangeLogs and accidentally included the patch in
comment 5. I left the latter since it is required for generality and cannot do
any harm. In fact, it might even do some good!
By the way, I am totally unable to reproduce the segfault of this PR and
consistently get the correct output.
***sigh***
Paul
>From gcc-bugs-return-605155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 17:01:10 2018
Return-Path: <gcc-bugs-return-605155-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11155 invoked by alias); 20 May 2018 17:01:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11100 invoked by uid 48); 20 May 2018 17:01:06 -0000
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] [9 regression] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Sun, 20 May 2018 17:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build, ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dcb314 at hotmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85834-4-J6XmJUnfWg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02050.txt.bz2
Content-length: 707
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
--- Comment #6 from David Binderman <dcb314 at hotmail dot com> ---
Reduced C++ code:
typedef long unsigned a;
extern "C" void *memset(void *, int, a);
typedef struct b c;
enum d { e };
template <int, typename> class f {
public:
template <typename g> f(g);
};
typedef f<1, long> h;
template <typename> struct j {
enum k {};
};
class l {
public:
typedef j<l>::k k;
l(k);
operator d();
};
struct b {};
class m {};
c q(h, d);
c n(unsigned char o[]) {
int i;
long r;
for (i = 0; i < 4; i++)
r = o[i];
return q(r, l((l::k)e));
}
m p() {
unsigned char o[4], s = 1;
for (;;) {
memset(o, s, 4);
n(o);
s = 2;
}
}
>From gcc-bugs-return-605156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 17:06:37 2018
Return-Path: <gcc-bugs-return-605156-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17539 invoked by alias); 20 May 2018 17:06: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 16676 invoked by uid 48); 20 May 2018 17:06:33 -0000
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85845] [9 Regression] Many libstdc++ test failures
Date: Sun, 20 May 2018 17: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: fdumont at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fdumont 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-85845-4-W91TNEvuy7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02051.txt.bz2
Content-length: 389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85845
François Dumont <fdumont at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |fdumont at gcc dot gnu.org
>From gcc-bugs-return-605157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 17:16:51 2018
Return-Path: <gcc-bugs-return-605157-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120708 invoked by alias); 20 May 2018 17:16: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 120611 invoked by uid 55); 20 May 2018 17:16:46 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82275] gfortran rejects valid & accepts invalid reference to dimension-remapped type SELECT TYPE selector
Date: Sun, 20 May 2018 17:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
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-82275-4-JSxHqkMFSt@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02052.txt.bz2
Content-length: 877
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82275
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 17:16:09 2018
New Revision: 260423
URL: https://gcc.gnu.org/viewcvs?rev=260423&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82275
Backport from trunk
* match.c (gfc_match_type_spec): Go through the array ref and
decrement 'rank' for every dimension that is an element.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82275
Backport from trunk
* gfortran.dg/select_type_42.f90: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/select_type_42.f90
Modified:
branches/gcc-7-branch/gcc/fortran/ChangeLog
branches/gcc-7-branch/gcc/fortran/match.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 17:37:55 2018
Return-Path: <gcc-bugs-return-605158-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47968 invoked by alias); 20 May 2018 17:37: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 47922 invoked by uid 48); 20 May 2018 17:37:51 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85216] Performance issue with PHP on ppc64 systems
Date: Sun, 20 May 2018 17: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: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85216-4-8xc6I677ZM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02053.txt.bz2
Content-length: 386
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85216
--- Comment #13 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
This was prototyped and measured against the firmware fixes with
indistinguishable results. So the complexity of a software solution, with its
impacts on Linux distributions, was not warranted. (That is, the firmware
workarounds are already tightly targeted.)
>From gcc-bugs-return-605159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 18:08:41 2018
Return-Path: <gcc-bugs-return-605159-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114838 invoked by alias); 20 May 2018 18:08:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 114779 invoked by uid 55); 20 May 2018 18:08:37 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80657] [7/8/9 Regression] Loop in character function declaration
Date: Sun, 20 May 2018 18: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: 7.1.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80657-4-JAlCPzmt5I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02054.txt.bz2
Content-length: 1058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80657
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 18:08:04 2018
New Revision: 260424
URL: https://gcc.gnu.org/viewcvs?rev=260424&root=gcc&view=rev
Log:
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/80657
Backport from trunk
* resolve.c (flag_fn_result_spec): Use the 'sym' argument to
test for self refs to the function result in the character len
expression. If a self reference is found, emit an error and
return true.
(resolve_fntype): Use the function symbol in the calls to the
above.
2018-05-20 Paul Thomas <pault@gcc.gnu.org>
PR fortran/80657
Backport from trunk
* gfortran.dg/char_result_18.f90: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gfortran.dg/char_result_18.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-605160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 18:09:21 2018
Return-Path: <gcc-bugs-return-605160-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115762 invoked by alias); 20 May 2018 18:09: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 115716 invoked by uid 48); 20 May 2018 18:09:17 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/82275] gfortran rejects valid & accepts invalid reference to dimension-remapped type SELECT TYPE selector
Date: Sun, 20 May 2018 18: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: 8.0
X-Bugzilla-Keywords:
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-82275-4-ExOFTbvnXp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82275-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02055.txt.bz2
Content-length: 486
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82275
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on 7-branch through to trunk.
Thanks for the report, Damian.
Paul
>From gcc-bugs-return-605161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 18:11:10 2018
Return-Path: <gcc-bugs-return-605161-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118224 invoked by alias); 20 May 2018 18:11: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 118165 invoked by uid 48); 20 May 2018 18:11:04 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80657] [7/8/9 Regression] Loop in character function declaration
Date: Sun, 20 May 2018 18: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: 7.1.0
X-Bugzilla-Keywords: ice-on-invalid-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: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-80657-4-RPrUtVSGpc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02056.txt.bz2
Content-length: 478
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80657
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on 7-branch through to trunk.
Thanks for the report.
Paul
>From gcc-bugs-return-605162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 18:49:12 2018
Return-Path: <gcc-bugs-return-605162-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76860 invoked by alias); 20 May 2018 18:49: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 76613 invoked by uid 48); 20 May 2018 18:48:46 -0000
From: "koenigni at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25829] [F03] Asynchronous IO support
Date: Sun, 20 May 2018 18:49:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: koenigni at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: koenigni at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.isobsolete attachments.created
Message-ID: <bug-25829-4-mK0FjTysD6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-25829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-25829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02057.txt.bz2
Content-length: 1526
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829
Nicolas Koenig <koenigni at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #44106|0 |1
is obsolete| |
--- Comment #41 from Nicolas Koenig <koenigni at gcc dot gnu.org> ---
Created attachment 44151
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44151&action=edit
Next version of patch.
Yet another patch version.
Error handling is partially implemented, iostat and iomsg work for WAIT.
This patch drops all pending I/O requests when an error occurs. Given that
trying to flush corrupted data almost always is a bad idea, this seems like the
only sensible way.
Timing data:
With
program main
implicit none
integer, parameter :: n = 10**7
character(3), parameter :: yes = "no"
real, dimension(n) :: a,b,c
call random_number(a)
call random_number(b)
call random_number(c)
open (10, file="a.dat",asynchronous=yes)
open (20, file="b.dat",asynchronous=yes)
open (30, file="c.dat",asynchronous=yes)
write (10,*,asynchronous=yes) a
write (20,*,asynchronous=yes) b
write (30,*,asynchronous=yes) c
wait (10)
wait (20)
wait (30)
end program main
real 0m15.465s
user 0m15.313s
sys 0m0.152s
With the "no" replaced by "yes":
real 0m5.558s
user 0m16.253s
sys 0m0.152s
If you ask me, that's quite nice :)
>From gcc-bugs-return-605163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 18:54:09 2018
Return-Path: <gcc-bugs-return-605163-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84400 invoked by alias); 20 May 2018 18:54:09 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84272 invoked by uid 48); 20 May 2018 18:54:05 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/49636] [F03] ASSOCIATE construct confused with slightly complicated case
Date: Sun, 20 May 2018 18:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.6.0
X-Bugzilla-Keywords: 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: 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-49636-4-e8sLPsm4Db@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
References: <bug-49636-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02058.txt.bz2
Content-length: 534
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49636
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #14 from Paul Thomas <pault at gcc dot gnu.org> ---
Fixed on 8-branch and trunk. The required support is just not there on 7-branch
- sorry.
Thanks for the report.
Paul
>From gcc-bugs-return-605164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 18:54:11 2018
Return-Path: <gcc-bugs-return-605164-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84677 invoked by alias); 20 May 2018 18:54: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 84342 invoked by uid 48); 20 May 2018 18:54:06 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/20585] [meta-bug] Fortran 2003 support
Date: Sun, 20 May 2018 18:54: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.1.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pault 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-20585-4-YV62n1kOz5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-20585-4@http.gcc.gnu.org/bugzilla/>
References: <bug-20585-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02059.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=20585
Bug 20585 depends on bug 49636, which changed state.
Bug 49636 Summary: [F03] ASSOCIATE construct confused with slightly complicated case
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=49636
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-605165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:12:15 2018
Return-Path: <gcc-bugs-return-605165-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6439 invoked by alias); 20 May 2018 19:12:15 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6381 invoked by uid 48); 20 May 2018 19:12:11 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85842] Bogus -Wreturn-type with generic lambda and constexpr if
Date: Sun, 20 May 2018 19: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.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85842-4-VaELhZ0iDl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85842-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02060.txt.bz2
Content-length: 402
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85842
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-20
Ever confirmed|0 |1
>From gcc-bugs-return-605166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:16:06 2018
Return-Path: <gcc-bugs-return-605166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 9704 invoked by alias); 20 May 2018 19:16: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 9394 invoked by uid 48); 20 May 2018 19:15:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85842] [8/9 Regression] Bogus -Wreturn-type with generic lambda and constexpr if
Date: Sun, 20 May 2018 19: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.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-85842-4-W8PCVyeI4q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85842-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85842-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02061.txt.bz2
Content-length: 997
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85842
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
Known to work| |7.3.0
Summary|Bogus -Wreturn-type with |[8/9 Regression] Bogus
|generic lambda and |-Wreturn-type with generic
|constexpr if |lambda and constexpr if
Known to fail| |8.1.0, 9.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Started with r259043
PR c++/85149 - generic lambda and constexpr if.
* pt.c (build_extra_args, add_extra_args): Split from
tsubst_pack_expansion.
(tsubst_expr) [IF_STMT]: Use them.
* cp-tree.h (IF_STMT_EXTRA_ARGS): New.
>From gcc-bugs-return-605167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:22:16 2018
Return-Path: <gcc-bugs-return-605167-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17950 invoked by alias); 20 May 2018 19:22: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 17877 invoked by uid 48); 20 May 2018 19:22:12 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] Invalid C++ in libstd++
Date: Sun, 20 May 2018 19: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:
X-Bugzilla-Severity: blocker
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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on assigned_to everconfirmed
Message-ID: <bug-85843-4-C6LVZ5gnNp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02062.txt.bz2
Content-length: 489
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-20
Assignee|unassigned at gcc dot gnu.org |redi at gcc dot gnu.org
Ever confirmed|0 |1
>From gcc-bugs-return-605168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:26:08 2018
Return-Path: <gcc-bugs-return-605168-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24638 invoked by alias); 20 May 2018 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 24564 invoked by uid 48); 20 May 2018 19:26:03 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/85843] Invalid C++ in libstd++
Date: Sun, 20 May 2018 19:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
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: priority bug_severity
Message-ID: <bug-85843-4-NzsAw7aRFx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02063.txt.bz2
Content-length: 504
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P1 |P3
Severity|blocker |normal
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
This isn't P1, because you can just stop using -Werror and it will build with a
warning.
>From gcc-bugs-return-605169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:27:33 2018
Return-Path: <gcc-bugs-return-605169-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26342 invoked by alias); 20 May 2018 19:27: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 26295 invoked by uid 48); 20 May 2018 19:27:29 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Sun, 20 May 2018 19:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords component short_desc
Message-ID: <bug-85843-4-8X7mLRFd63@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02064.txt.bz2
Content-length: 887
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |build
Component|bootstrap |libstdc++
Summary|Invalid C++ in libstd++ |warning: base class ‘class
| |std::exception’ should be
| |explicitly initialized in
| |the copy constructor
| |[-Wextra]
--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
i.e. there's no invalid C++ at all, you're just asking for all warnings to
break your build.
>From gcc-bugs-return-605170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:28:16 2018
Return-Path: <gcc-bugs-return-605170-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27768 invoked by alias); 20 May 2018 19:28: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 27711 invoked by uid 48); 20 May 2018 19:28:12 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85848] Incorrect handling of explicit casting to move-only types
Date: Sun, 20 May 2018 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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85848-4-owDpzhEAhC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02065.txt.bz2
Content-length: 538
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85848
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-20
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
See https://gcc.gnu.org/bugs/
(This is not a valid bug report).
>From gcc-bugs-return-605172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:41:36 2018
Return-Path: <gcc-bugs-return-605172-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72005 invoked by alias); 20 May 2018 19:41: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 70213 invoked by uid 48); 20 May 2018 19:41:31 -0000
From: "kot.tom97 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85848] Incorrect handling of explicit casting to move-only types
Date: Sun, 20 May 2018 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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kot.tom97 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: attachments.created
Message-ID: <bug-85848-4-AwC6Hc2Nv9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02067.txt.bz2
Content-length: 255
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85848
--- Comment #2 from Tom Westerhout <kot.tom97 at gmail dot com> ---
Created attachment 44152
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44152&action=edit
Sample code triggering the error
>From gcc-bugs-return-605171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:41:25 2018
Return-Path: <gcc-bugs-return-605171-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69541 invoked by alias); 20 May 2018 19:41:25 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69443 invoked by uid 55); 20 May 2018 19:41:21 -0000
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/80657] [7/8/9 Regression] Loop in character function declaration
Date: Sun, 20 May 2018 19:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords: ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zeccav at gmail dot com
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: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80657-4-hW5BP8ug2V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02066.txt.bz2
Content-length: 239
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80657
--- Comment #10 from Vittorio Zecca <zeccav at gmail dot com> ---
Just applied the fix: gfortran delivers an error message and exits. In
10 milliseconds!
Thank you for fixing this one.
>From gcc-bugs-return-605173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:43:37 2018
Return-Path: <gcc-bugs-return-605173-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111501 invoked by alias); 20 May 2018 19:43: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 111421 invoked by uid 48); 20 May 2018 19:43:33 -0000
From: "kot.tom97 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85848] Incorrect handling of explicit casting to move-only types
Date: Sun, 20 May 2018 19:43:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kot.tom97 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: attachments.created
Message-ID: <bug-85848-4-eycDrTYFZ8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02068.txt.bz2
Content-length: 279
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85848
--- Comment #3 from Tom Westerhout <kot.tom97 at gmail dot com> ---
Created attachment 44153
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44153&action=edit
Preprocessed source
Result after preprocessing test.cpp
>From gcc-bugs-return-605174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 19:55:09 2018
Return-Path: <gcc-bugs-return-605174-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 87840 invoked by alias); 20 May 2018 19:55:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 84541 invoked by uid 48); 20 May 2018 19:55:04 -0000
From: "kot.tom97 at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85848] Incorrect handling of explicit casting to move-only types
Date: Sun, 20 May 2018 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kot.tom97 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-85848-4-6SsBitESxv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02069.txt.bz2
Content-length: 4846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85848
--- Comment #4 from Tom Westerhout <kot.tom97 at gmail dot com> ---
A few configurations on which the attached example fails to compile:
$ g++-6 -v
Using built-in specs.
COLLECT_GCC=g++-6
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 6.4.0-12'
--with-bugurl=file:///usr/share/doc/gcc-6/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-6 --program-prefix=x86_64-linux-gnu- --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --disable-browser-plugin --enable-java-awt=gtk
--enable-gtk-cairo --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-6-amd64/jre
--enable-java-home --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-6-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-6-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch
--with-arch-32=i686 --with-abi=m64 --with-multilib-list=m32,m64,mx32
--enable-multilib --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 6.4.0 20180123 (Debian 6.4.0-12)
$ g++-7 -v
Using built-in specs.
COLLECT_GCC=g++-7
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/7/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 7.3.0-18'
--with-bugurl=file:///usr/share/doc/gcc-7/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-7
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 7.3.0 (Debian 7.3.0-18)
$ g++-8 -v
Using built-in specs.
COLLECT_GCC=g++-8
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 8.1.0-3'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --enable-default-pie
--with-system-zlib --with-target-system-zlib --enable-objc-gc=auto
--enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic
--enable-offload-targets=nvptx-none --without-cuda-driver
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.1.0 (Debian 8.1.0-3)
All three versions produce the following error message:
test.cpp: In function ‘int main()’:
test.cpp:13:29: error: invalid static_cast from type ‘box’ to type ‘bar&&’
static_cast<bar&&>(box{});
The exact build command used:
g++ -std=c++14 -Wall -Wextra -pedantic test.cpp
@Jonathan Wakely, does this qualify as a valid bug report now? or should I add
something else?
>From gcc-bugs-return-605175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 20:01:53 2018
Return-Path: <gcc-bugs-return-605175-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125226 invoked by alias); 20 May 2018 20:01:53 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125171 invoked by uid 48); 20 May 2018 20:01:49 -0000
From: "tpearson at raptorengineering dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85216] Performance issue with PHP on ppc64 systems
Date: Sun, 20 May 2018 20: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: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tpearson at raptorengineering dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85216-4-5I1VTu1cnz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02070.txt.bz2
Content-length: 671
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85216
--- Comment #14 from Timothy Pearson <tpearson at raptorengineering dot com> ---
(In reply to Bill Schmidt from comment #13)
> This was prototyped and measured against the firmware fixes with
> indistinguishable results. So the complexity of a software solution, with
> its impacts on Linux distributions, was not warranted. (That is, the
> firmware workarounds are already tightly targeted.)
Good to know, thank you. Was about to test it on this end. I guess the main
takeway then is that POWER9 handles interpreted workloads quite badly, or is
there still some possibility of additional optimization here?
>From gcc-bugs-return-605176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 20:14:10 2018
Return-Path: <gcc-bugs-return-605176-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13360 invoked by alias); 20 May 2018 20: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 13316 invoked by uid 48); 20 May 2018 20:14:05 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85537] [7/8/9 Regression] Invalid memory reference at runtime when calling subroutine through procedure pointer
Date: Sun, 20 May 2018 20: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.8.5
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85537-4-I8yhKdCAeL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85537-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85537-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02071.txt.bz2
Content-length: 1058
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85537
--- Comment #6 from janus at gcc dot gnu.org ---
(In reply to janus from comment #5)
> However I don't see any failures with this variant:
Sorry, I was a bit too quick in submitting this. It's really not a good
example, since it's missing an "implicit none", so "bar_impl" supposedly gets
its own private version of "a".
The following variant fails again in the same way as the original test case:
program main
implicit none
integer :: a
call foo()
contains
subroutine foo()
abstract interface
subroutine ibar()
end subroutine
end interface
procedure(ibar), pointer :: bar_ptr => bar_impl
a = 0
call bar_impl()
call bar_ptr()
end subroutine
subroutine bar_impl()
write (*,*) "foo"
a = a + 1
end subroutine
end program
I don't quite understand what's going on. Apparently the reference to the
variable 'a' somehow goes wrong. But I don't see how the procedure pointer
makes a difference here.
>From gcc-bugs-return-605177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 20:20:55 2018
Return-Path: <gcc-bugs-return-605177-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24518 invoked by alias); 20 May 2018 20:20: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 24499 invoked by uid 48); 20 May 2018 20:20:50 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85850] New: [9.0 Regression] gcc 9.0 doesn't compile with Xcode 9.3.1
Date: Sun, 20 May 2018 20:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02072.txt.bz2
Content-length: 2840
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85850
Bug ID: 85850
Summary: [9.0 Regression] gcc 9.0 doesn't compile with Xcode
9.3.1
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: juergen.reuter at desy dot de
Target Milestone: ---
gcc doesn't compile any more under Darwin 17.5 with Xcode 9.3.1 producing the
following error (cf. below).
# g++ --version
Configured with: --prefix=/Applications/Xcode.app/Contents/Developer/usr
--with-gxx-include-dir=/usr/include/c++/4.2.1
Apple LLVM version 9.1.0 (clang-902.0.39.1)
Target: x86_64-apple-darwin17.5.0
Thread model: posix
InstalledDir:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin
mkdir -p -- .deps
g++ -std=gnu++98 -I../../../libcpp -I. -I../../../libcpp/../include
-I../../../libcpp/include -g -O2 -W -Wall -Wno-narrowing -Wwrite-strings
-Wmissing-format-attribute -pedantic -Wno-long-long -fno-exceptions -fno-rtti
-I../../../libcpp -I. -I../../../libcpp/../include -I../../../libcpp/include
-c -o charset.o -MT charset.o -MMD -MP -MF .deps/charset.Tpo
../../../libcpp/charset.c
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is
deprecated [-Wdeprecated]
In file included from ../../../libcpp/charset.c:21:
../../../libcpp/system.h:435:9: warning: keyword is hidden by macro definition
[-Wkeyword-macro]
#define true 1
^
../../../libcpp/system.h:436:9: warning: keyword is hidden by macro definition
[-Wkeyword-macro]
#define false 0
^
In file included from ../../../libcpp/charset.c:21:
In file included from ../../../libcpp/system.h:442:
In file included from
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/new:89:
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/exception:180:5:
error: no member named
'fancy_abort' in namespace 'std::__1'; did you mean simply 'fancy_abort'?
_VSTD::abort();
^~~~~~~
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/include/c++/v1/__config:441:15:
note: expanded from macro
'_VSTD'
#define _VSTD std::_LIBCPP_NAMESPACE
^
../../../libcpp/system.h:399:13: note: 'fancy_abort' declared here
extern void fancy_abort (const char *, int, const char *) ATTRIBUTE_NORETURN;
^
In file included from ../../../libcpp/charset.c:22:
../../../libcpp/include/cpplib.h:789:14: warning: private field 'm_line_table'
is not used [-Wunused-private-field]
line_maps *m_line_table;
^
3 warnings and 1 error generated.
>From gcc-bugs-return-605178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 20:25:02 2018
Return-Path: <gcc-bugs-return-605178-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26902 invoked by alias); 20 May 2018 20: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 26738 invoked by uid 48); 20 May 2018 20:24:32 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/82091] [5 only] Build failure on macOS 10.13 with Xcode 9
Date: Sun, 20 May 2018 20:24:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: bootstrap
X-Bugzilla-Version: 5.4.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: 5.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82091-4-aVGQIbrpJ2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82091-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82091-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02073.txt.bz2
Content-length: 229
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82091
--- Comment #6 from Jürgen Reuter <juergen.reuter at desy dot de> ---
I do see this error now also with the trunk version [r260425] under Darwin 17.5
with Xcode 9.3.1.
>From gcc-bugs-return-605179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 20:44:13 2018
Return-Path: <gcc-bugs-return-605179-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73755 invoked by alias); 20 May 2018 20:44:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 73718 invoked by uid 48); 20 May 2018 20:44:08 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85850] [9.0 Regression] gcc 9.0 doesn't compile with Xcode 9.3.1
Date: Sun, 20 May 2018 20:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85850-4-7amVlTR7Rh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02074.txt.bz2
Content-length: 318
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85850
--- Comment #1 from Marc Glisse <glisse at gcc dot gnu.org> ---
In libcpp/system.h, <new> is included too late, after messing with macros, it
should move earlier with the other includes. We could probably also avoid
#defining true/false in C++ (just a warning).
>From gcc-bugs-return-605180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 20:48:51 2018
Return-Path: <gcc-bugs-return-605180-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82516 invoked by alias); 20 May 2018 20:48:47 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 82408 invoked by uid 48); 20 May 2018 20:48:35 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85850] [9.0 Regression] gcc 9.0 doesn't compile with Xcode 9.3.1
Date: Sun, 20 May 2018 20: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:
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-85850-4-38pL9jbN4I@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02075.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85850
--- Comment #2 from Jürgen Reuter <juergen.reuter at desy dot de> ---
So is there a quick workaround for this?
>From gcc-bugs-return-605181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 21:09:06 2018
Return-Path: <gcc-bugs-return-605181-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115786 invoked by alias); 20 May 2018 21:09:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 115717 invoked by uid 48); 20 May 2018 21:09:01 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85216] Performance issue with PHP on ppc64 systems
Date: Sun, 20 May 2018 21:09:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85216-4-gDAcq2Rx5X@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02076.txt.bz2
Content-length: 569
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85216
--- Comment #15 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
PHP's reliance on frequent indirect branches makes it essentially the worst
case for this sort of thing. When Spectre v2 CVE mitigations are in place for
user code, you will see performance issues on all architectures that rely on
speculation for indirect branch performance. When user code is running in an
"unsafe" configuration, you will not see those issues. (We have seen similar
issues on x86 when retpoline is used for user code.)
>From gcc-bugs-return-605182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 21:12:19 2018
Return-Path: <gcc-bugs-return-605182-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117669 invoked by alias); 20 May 2018 21: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 117606 invoked by uid 48); 20 May 2018 21:12:14 -0000
From: "tpearson at raptorengineering dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85216] Performance issue with PHP on ppc64 systems
Date: Sun, 20 May 2018 21:12:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tpearson at raptorengineering dot com
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85216-4-HXjYesddB0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02077.txt.bz2
Content-length: 1129
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85216
--- Comment #16 from Timothy Pearson <tpearson at raptorengineering dot com> ---
(In reply to Bill Schmidt from comment #15)
> PHP's reliance on frequent indirect branches makes it essentially the worst
> case for this sort of thing. When Spectre v2 CVE mitigations are in place
> for user code, you will see performance issues on all architectures that
> rely on speculation for indirect branch performance. When user code is
> running in an "unsafe" configuration, you will not see those issues. (We
> have seen similar issues on x86 when retpoline is used for user code.)
What's most puzzling is that we're looking at benchmarks on x86 systems that
are supposed to be mitigated, but the performance drop isn't really showing up.
At this point I'm wondering if:
a.) The user/user attack isn't actually mitigated on these systems, only the
user/kernel attack
b.) Intel/AMD found some way to update the microcode so as not to have a heavy
performance loss
In any case, we'll continue to investigate / run benchmarks to see if any light
can be shed on this.
>From gcc-bugs-return-605183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 21:21:22 2018
Return-Path: <gcc-bugs-return-605183-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5525 invoked by alias); 20 May 2018 21:21: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 5457 invoked by uid 48); 20 May 2018 21:21:17 -0000
From: "wschmidt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85216] Performance issue with PHP on ppc64 systems
Date: Sun, 20 May 2018 21: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: 7.3.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wschmidt at gcc dot gnu.org
X-Bugzilla-Status: REOPENED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85216-4-mpHnKwZADI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85216-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02078.txt.bz2
Content-length: 188
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85216
--- Comment #17 from Bill Schmidt <wschmidt at gcc dot gnu.org> ---
OK, thanks! I'd be very interested in hearing what you discover.
>From gcc-bugs-return-605184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 21:52:14 2018
Return-Path: <gcc-bugs-return-605184-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66112 invoked by alias); 20 May 2018 21:52:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66051 invoked by uid 55); 20 May 2018 21:52:08 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Sun, 20 May 2018 21:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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-85843-4-lEjB73dk1o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02079.txt.bz2
Content-length: 802
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
--- Comment #5 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, May 20, 2018 at 07:27:28PM +0000, redi at gcc dot gnu.org wrote:
>
> --- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> i.e. there's no invalid C++ at all, you're just asking for all warnings to
> break your build.
>
% cd gcc/
% svn update
% cd ../obj
% rm -rf *
% cat ../conf
#! /bin/sh
CC=/usr/local/bin/gcc7
export CC
CXX=/usr/local/bin/g++7
export CXX
../gcc/configure --prefix=$HOME/work/x --enable-languages=c,fortran \
--enable-bootstrap --disable-nls --enable-checking=yes \
--enable-maintainer-mode
% ../conf
% gmake -j7 bootstrap
<boom>
Boostrap is broken.
Waste a day trying to identify issue.
Ergo P1.
>From gcc-bugs-return-605185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 22:03:32 2018
Return-Path: <gcc-bugs-return-605185-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112265 invoked by alias); 20 May 2018 22:03: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 112213 invoked by uid 48); 20 May 2018 22:03:26 -0000
From: "slyfox at inbox dot ru" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85666] gcc-8.0.1 fails to build mmix target: gcc/libgcc/libgcc2.h:203:20: internal compiler error: in leaf_function_p, at final.c:4488
Date: Sun, 20 May 2018 22: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: 8.0.1
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: slyfox at inbox dot ru
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85666-4-rjpXZiCQXr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02080.txt.bz2
Content-length: 1203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666
--- Comment #6 from Sergei Trofimovich <slyfox at inbox dot ru> ---
An observation (does not pretend to be a fix) to make gcc compile standard
library and be able to build runnable hello world on gcc master:
1. MMIX_CFUN_NEEDS_SAVED_EH_RETURN_ADDRESS can be unoptimised
2. assemble_integer has to be tweaked to avoid failure in dwarf generation
--- a/gcc/config/mmix/mmix.c
+++ b/gcc/config/mmix/mmix.c
@@ -72,7 +72,7 @@ along with GCC; see the file COPYING3. If not see
#define MMIX_CFUN_NEEDS_SAVED_EH_RETURN_ADDRESS \
(flag_exceptions \
&& ((reload_completed && df_regs_ever_live_p (MMIX_rJ_REGNUM)) \
- || !leaf_function_p ()))
+ || true))
#define IS_MMIX_EH_RETURN_DATA_REG(REGNO) \
(crtl->calls_eh_return \
diff --git a/gcc/varasm.c b/gcc/varasm.c
index 85296b4a2ec..e8d26bd1623 100644
--- a/gcc/varasm.c
+++ b/gcc/varasm.c
@@ -2816,7 +2816,7 @@ assemble_integer (rtx x, unsigned int size, unsigned int
align, int force)
gcc_assert (!i);
}
- gcc_assert (!force);
+ //gcc_assert (!force);
return false;
}
>From gcc-bugs-return-605186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 22:36:37 2018
Return-Path: <gcc-bugs-return-605186-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37947 invoked by alias); 20 May 2018 22:36: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 37871 invoked by uid 48); 20 May 2018 22:36:33 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Sun, 20 May 2018 22:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85840-4-r0Fih6dnUe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02081.txt.bz2
Content-length: 208
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
--- Comment #5 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I will see if I can reproduce this here with you example and if so will get on
it.
>From gcc-bugs-return-605187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 22:42:07 2018
Return-Path: <gcc-bugs-return-605187-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42134 invoked by alias); 20 May 2018 22:42:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 41431 invoked by uid 48); 20 May 2018 22:42:02 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85840] Memory leak in write.c
Date: Sun, 20 May 2018 22:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: jvdelisle at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-85840-4-v7beh4Oowg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85840-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02082.txt.bz2
Content-length: 520
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85840
Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |jvdelisle at gcc dot gnu.org
--- Comment #6 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
That did not take long. Thanks for simple test case. Confirmed.
>From gcc-bugs-return-605188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 22:49:07 2018
Return-Path: <gcc-bugs-return-605188-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51864 invoked by alias); 20 May 2018 22:49:07 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51803 invoked by uid 48); 20 May 2018 22:49:02 -0000
From: "zeccav at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85851] New: trunk 260152 ICE in gfc_conv_structure Segmentation fault at trans-expr.c:7810
Date: Sun, 20 May 2018 22:49: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: zeccav at gmail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone cf_gcchost
Message-ID: <bug-85851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02083.txt.bz2
Content-length: 2556
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85851
Bug ID: 85851
Summary: trunk 260152 ICE in gfc_conv_structure Segmentation
fault at trans-expr.c:7810
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: zeccav at gmail dot com
Target Milestone: ---
Host: x86_64-pc-linux-gnu
! trunk 260152 ICE in gfc_conv_structure Segmentation fault at
trans-expr.c:7810
! must be compiled with -finit-derived
! from test case pr35983
use ISO_C_BINDING
type, bind(C) :: descr
type(C_PTR) :: address
end type descr
type(descr) :: DD
double precision, target :: buf(1)
DD = descr(c_loc(buf))
end
!p.f90:4:0:
!
! use ISO_C_BINDING
!
!internal compiler error: Segmentation fault
!0xcedddf crash_signal
! ../../gcc-260152/gcc/toplev.c:325
!0x153cd5c78fcf ???
!
/usr/src/debug/glibc-2.27-37-g39071a5539/signal/../sysdeps/unix/sysv/linux/x86_64/sigaction.c:0
!0x855b53 gfc_conv_structure(gfc_se*, gfc_expr*, int)
! ../../gcc-260152/gcc/fortran/trans-expr.c:7810
!0x855527 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool,
bool, bool)
! ../../gcc-260152/gcc/fortran/trans-expr.c:6951
!0x855aa5 gfc_conv_structure(gfc_se*, gfc_expr*, int)
! ../../gcc-260152/gcc/fortran/trans-expr.c:7818
!0x855527 gfc_conv_initializer(gfc_expr*, gfc_typespec*, tree_node*, bool,
bool, bool)
! ../../gcc-260152/gcc/fortran/trans-expr.c:6951
!0x83cca4 gfc_get_symbol_decl(gfc_symbol*)
! ../../gcc-260152/gcc/fortran/trans-decl.c:1835
!0x83fe37 generate_local_decl
! ../../gcc-260152/gcc/fortran/trans-decl.c:5595
!0x8003e2 do_traverse_symtree
! ../../gcc-260152/gcc/fortran/symbol.c:4165
!0x840b12 generate_local_vars
! ../../gcc-260152/gcc/fortran/trans-decl.c:5795
!0x840b12 gfc_generate_function_code(gfc_namespace*)
! ../../gcc-260152/gcc/fortran/trans-decl.c:6442
!0x7cc1c6 translate_all_program_units
! ../../gcc-260152/gcc/fortran/parse.c:6121
!0x7cc1c6 gfc_parse_file()
! ../../gcc-260152/gcc/fortran/parse.c:6324
!0x81243f gfc_be_parse_file
! ../../gcc-260152/gcc/fortran/f95-lang.c:204
!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-605189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 22:56:59 2018
Return-Path: <gcc-bugs-return-605189-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80670 invoked by alias); 20 May 2018 22:56: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 74220 invoked by uid 48); 20 May 2018 22:56:55 -0000
From: "angus at agibson dot me" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85786] [8/9 Regression] Segfault in associated intrinsic
Date: Sun, 20 May 2018 22: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: 8.1.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: angus at agibson dot me
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-85786-4-1K8DKXix59@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85786-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85786-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02084.txt.bz2
Content-length: 1663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85786
--- Comment #11 from Angus Gibson <angus at agibson dot me> ---
Apologies if this is unrelated to the issue at hand (I don't quite understand
how everything is inter-related yet), but maybe it helps. First up, here's what
valgrind says about the segfault:
...
loc(cs%v(2)%p) = 101158160
==4100== Use of uninitialised value of size 8
==4100== at 0x109820: query_ptr.3790 (test_verb.f90:49)
==4100== by 0x109FE3: MAIN__ (test_verb.f90:27)
==4100== by 0x10A108: main (test_verb.f90:27)
==4100==
==4100== Invalid read of size 8
==4100== at 0x109820: query_ptr.3790 (test_verb.f90:49)
==4100== by 0x109FE3: MAIN__ (test_verb.f90:27)
==4100== by 0x10A108: main (test_verb.f90:27)
==4100== Address 0x20050786e0 is not stack'd, malloc'd or (recently) free'd
==4100==
And with an even simpler example, gdb encounters an internal error (it's
actually very easy to trigger with pointers).
program test
type t
real, dimension(:,:), pointer :: p => null()
end type t
real, dimension(2,2), target :: e
type(t), pointer :: cs
allocate(cs)
cs%p => e
e = 42
print *, 'done'
end program test
In gdb:
(gdb) info locals
cs = 0x55555575a850
e = (( 42, 42) ( 42, 42) )
(gdb) print cs
$1 = (PTR TO -> ( Type t )) 0x55555575a850
(gdb) print cs%p
value.c:3116: internal-error: value* value_primitive_field(value*, LONGEST,
int, type*): Assertion `PROP_CONST == TYPE_DATA_LOCATION_KIND (type)' failed.
>From gcc-bugs-return-605190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 23:11:31 2018
Return-Path: <gcc-bugs-return-605190-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103932 invoked by alias); 20 May 2018 23:11:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 103879 invoked by uid 48); 20 May 2018 23:11:26 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85851] [8/9 Regression] ICE in gfc_conv_structure Segmentation fault at trans-expr.c:7810
Date: Sun, 20 May 2018 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: ice-on-valid-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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: priority bug_status cf_known_to_work keywords cf_reconfirmed_on cc everconfirmed short_desc target_milestone cf_known_to_fail
Message-ID: <bug-85851-4-qH29JZPtob@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02085.txt.bz2
Content-length: 1161
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85851
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P3 |P4
Status|UNCONFIRMED |NEW
Known to work| |7.3.0
Keywords| |ice-on-valid-code
Last reconfirmed| |2018-05-20
CC| |foreese at gcc dot gnu.org
Ever confirmed|0 |1
Summary|trunk 260152 ICE in |[8/9 Regression] ICE in
|gfc_conv_structure |gfc_conv_structure
|Segmentation fault at |Segmentation fault at
|trans-expr.c:7810 |trans-expr.c:7810
Target Milestone|--- |8.2
Known to fail| |8.1.0, 9.0
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Likely revision r 254648 (pr82886).
>From gcc-bugs-return-605192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 23:50:59 2018
Return-Path: <gcc-bugs-return-605192-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46919 invoked by alias); 20 May 2018 23:50: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 46826 invoked by uid 48); 20 May 2018 23:50:55 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Sun, 20 May 2018 23:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85843-4-Lm3hHZKHv3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02087.txt.bz2
Content-length: 1015
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Steve Kargl from comment #5)
> ../gcc/configure --prefix=$HOME/work/x --enable-languages=c,fortran \
> --enable-bootstrap --disable-nls --enable-checking=yes \
> --enable-maintainer-mode
^^^^^^^^^^^^^^^^^^^^^^^^
../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc:58:3: error: base
class 'class std::exception' should be explicitly initialized in the copy
constructor
[-Werror=extra]
^^^^^^^^^^^^^^^
The "error" is a warning, that fails the build because you're using -Werror
(via maintainer-mode) so you can save yourself a day next time.
It's fixed now.
>From gcc-bugs-return-605191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 23:50:44 2018
Return-Path: <gcc-bugs-return-605191-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 46115 invoked by alias); 20 May 2018 23:50: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 46021 invoked by uid 55); 20 May 2018 23:50:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Sun, 20 May 2018 23:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85843-4-dUC3PGX3Sj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02086.txt.bz2
Content-length: 577
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Sun May 20 23:50:08 2018
New Revision: 260427
URL: https://gcc.gnu.org/viewcvs?rev=260427&root=gcc&view=rev
Log:
PR libstdc++/85843 fix "should be explicitly initialized" warnings
PR libstdc++/85843
* src/c++11/cow-stdexcept.cc (logic_error, runtime_error): Explicitly
initialize base class to avoid warnings.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/src/c++11/cow-stdexcept.cc
>From gcc-bugs-return-605193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun May 20 23:54:12 2018
Return-Path: <gcc-bugs-return-605193-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 53782 invoked by alias); 20 May 2018 23:54:12 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 53739 invoked by uid 48); 20 May 2018 23:54:08 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85848] Incorrect handling of explicit casting to move-only types
Date: Sun, 20 May 2018 23:54:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status
Message-ID: <bug-85848-4-KZLMHsnu5w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85848-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02088.txt.bz2
Content-length: 728
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85848
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Status|WAITING |NEW
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Yes, thanks for providing the necessary info.
Reduced:
using bar = int;
struct box
{
explicit operator bar();
} b;
bar&& b1 = static_cast<bar&&>(b);
bar&& b2( b );
GCC rejects the conversion in the initializer for both b1 and b2.
EDG rejects b1 only. MSVC rejects both.
Clang accepts both.
>From gcc-bugs-return-605194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 00:20:03 2018
Return-Path: <gcc-bugs-return-605194-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 98694 invoked by alias); 21 May 2018 00:20:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 98575 invoked by uid 55); 21 May 2018 00:19:58 -0000
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Mon, 21 May 2018 00:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sgk at troutmask dot apl.washington.edu
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-85843-4-4P4UZ7cnjE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02089.txt.bz2
Content-length: 1907
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
--- Comment #8 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sun, May 20, 2018 at 11:50:54PM +0000, redi at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
>
> Jonathan Wakely <redi at gcc dot gnu.org> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|ASSIGNED |RESOLVED
> Resolution|--- |FIXED
>
> --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
> (In reply to Steve Kargl from comment #5)
> > ../gcc/configure --prefix=$HOME/work/x --enable-languages=c,fortran \
> > --enable-bootstrap --disable-nls --enable-checking=yes \
> > --enable-maintainer-mode
> ^^^^^^^^^^^^^^^^^^^^^^^^
> ../../../../../gcc/libstdc++-v3/src/c++11/cow-stdexcept.cc:58:3: error: base
> class 'class std::exception' should be explicitly initialized in the copy
> constructor
> [-Werror=extra]
> ^^^^^^^^^^^^^^^
--enable-maintainer-mode is required when adding a new intrinsic
subprogram to libgfortran.
IMNSHO, every committer should be required to include -Werror
and -Werro-extra. Introducing a patch and new code that causes
a new warning is broken by definition.
> The "error" is a warning, that fails the build because you're using -Werror
> (via maintainer-mode) so you can save yourself a day next time.
I have weekends to work on gfortran. Yeah, I know, it's only
Fortran. It's good to know you've volunteer to implement Fortran
2018's RANDOM_INIT, so that I won't need to use --enable-maintainer-mode.
IOW, it is disrespectful to blame one's mistakes on others because
they need to use functionality to get their work done.
> It's fixed now.
Should have never been broken.
>From gcc-bugs-return-605195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 01:47:33 2018
Return-Path: <gcc-bugs-return-605195-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 119534 invoked by alias); 21 May 2018 01:47:33 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 119458 invoked by uid 55); 21 May 2018 01:47:26 -0000
From: "urbanjost at comcast dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/66694] Failure in function returning an allocated CHARACTER array
Date: Mon, 21 May 2018 01:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.2
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: urbanjost at comcast dot net
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-66694-4-m3zmr54H86@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66694-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02090.txt.bz2
Content-length: 1358
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #9 from urbanjost at comcast dot net ---
Thanks!
-----Original Message-----
From: pault at gcc dot gnu.org [mailto:gcc-bugzilla@gcc.gnu.org]
Sent: Sunday, May 20, 2018 6:00 AM
To: urbanjost@comcast.net
Subject: [Bug fortran/66694] Failure in function returning an allocated
CHARACTER array
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66694
--- Comment #8 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Sun May 20 09:59:54 2018
New Revision: 260413
URL: https://gcc.gnu.org/viewcvs?rev=260413&root=gcc&view=rev
Log:
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
PR fortran/66694
PR fortran/82617
* trans-array.c (gfc_alloc_allocatable_for_assignment): Set the
charlen backend_decl of the rhs expr to ss->info->string_length
so that the value in the current scope is used.
2018-05-19 Paul Thomas <pault@gcc.gnu.org>
PR fortran/82923
* gfortran.dg/allocate_assumed_charlen_4.f90: New test. Note
that the patch fixes PR66694 & PR82617, although the testcases
are not explicitly included.
Added:
trunk/gcc/testsuite/gfortran.dg/select_type_42.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/match.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 02:36:44 2018
Return-Path: <gcc-bugs-return-605196-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 36747 invoked by alias); 21 May 2018 02: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 36683 invoked by uid 48); 21 May 2018 02:36:37 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Mon, 21 May 2018 02:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85843-4-YQ5iy3AMnh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02091.txt.bz2
Content-length: 889
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at gcc dot gnu.org
--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Thanks for fixing this, sorry I didn't notice the warnings in my testing.
I think it's a mistake for maintainer mode to imply -Werror; it's only
documented to mean that the build can rely on esoteric tools that end users
don't need to have, and since many developers don't use
--enable-maintainer-mode we can get problems like this one.
I also think that it makes sense for libstdc++ to use -Werror by default, if
it's compiling with the just-built current GCC. I guess I'll add
--enable-werror to my builds.
>From gcc-bugs-return-605197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 03:53:39 2018
Return-Path: <gcc-bugs-return-605197-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 75019 invoked by alias); 21 May 2018 03:53: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 74965 invoked by uid 55); 21 May 2018 03:53:35 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: =?UTF-8?B?W0J1ZyBsaWJzdGRjKysvODU4NDNdIHdhcm5pbmc6IGJhc2UgY2xhc3Mg4oCY?= =?UTF-8?B?Y2xhc3Mgc3RkOjpleGNlcHRpb27igJkgc2hvdWxkIGJlIGV4cGxpY2l0bHkg?= =?UTF-8?B?aW5pdGlhbGl6ZWQgaW4gdGhlIGNvcHkgY29uc3RydWN0b3IgWy1XZXh0cmFd?Date: Mon, 21 May 2018 03:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: redi at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85843-4-5kC5OUny8g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85843-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02092.txt.bz2
Content-length: 565
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85843
--- Comment #10 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Mon May 21 03:53:00 2018
New Revision: 260432
URL: https://gcc.gnu.org/viewcvs?rev=260432&root=gcc&view=rev
Log:
PR libstdc++/85843 - warning in logic_error copy constructor.
* class.c (type_has_user_nondefault_constructor): Check for a
user-provided ctor, not user-declared.
Added:
trunk/gcc/testsuite/g++.dg/warn/Wextra-4.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/class.c
>From gcc-bugs-return-605198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 04:02:22 2018
Return-Path: <gcc-bugs-return-605198-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 85632 invoked by alias); 21 May 2018 04:02:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 85462 invoked by uid 48); 21 May 2018 04:02:13 -0000
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85666] gcc-8.0.1 fails to build mmix target: gcc/libgcc/libgcc2.h:203:20: internal compiler error: in leaf_function_p, at final.c:4488
Date: Mon, 21 May 2018 04: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.1
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hp at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85666-4-At8vD63jXf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02093.txt.bz2
Content-length: 1836
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666
--- Comment #7 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
Thank you for your interest in the MMIX port.
(In reply to Wilco from comment #3)
> (In reply to Sergei Trofimovich from comment #1)
>
> > #define MMIX_CFUN_NEEDS_SAVED_EH_RETURN_ADDRESS \
> > (flag_exceptions \
> > && ((reload_completed && df_regs_ever_live_p (MMIX_rJ_REGNUM)) \
> > || !leaf_function_p ())) /// <- here
>
>
> Yes that looks like a bug. leaf_function_p cannot be called on a sequence as
> it will incorrectly return true on non-leaf functions. So
> MMIX_CFUN_NEEDS_SAVED_EH_RETURN_ADDRESS will randomly change its result if
> called again later. starting_frame_offset should however return a fixed
> value, so the reload_completed part also looks wrong.
Kindly refer to the comment above that macro:
/* We have no means to tell DWARF 2 about the register stack, so we need
to store the return address on the stack if an exception can get into
this function. FIXME: Narrow condition. Before any whole-function
analysis, df_regs_ever_live_p () isn't initialized. We know it's up-to-date
after reload_completed; it may contain incorrect information some time
before that. Within a RTL sequence (after a call to start_sequence,
such as in RTL expanders), leaf_function_p doesn't see all insns
(perhaps any insn). But regs_ever_live is up-to-date when
leaf_function_p () isn't, so we "or" them together to get accurate
information. FIXME: Some tweak to leaf_function_p might be
preferable. */
So, it looks like the time has come for "some tweak to leaf_function_p",
or...some other tweak. Yes, this was a brittle solution and someone saw fit to
pull the rug. Maybe I'll have to compute the starting frame offset some other
way.
>From gcc-bugs-return-605199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 04:11:13 2018
Return-Path: <gcc-bugs-return-605199-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96258 invoked by alias); 21 May 2018 04: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 96218 invoked by uid 48); 21 May 2018 04:11:08 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85852] New: ICE: Segmentation fault (in contains_struct_check)
Date: Mon, 21 May 2018 04:11: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: 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-85852-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02094.txt.bz2
Content-length: 2389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85852
Bug ID: 85852
Summary: ICE: Segmentation fault (in contains_struct_check)
Product: gcc
Version: 9.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-alpha20180520 snapshot (r260425) ICEs when compiling the following
snippet w/ -mfma -O2 (-O3, -Os) -fexceptions -fnon-call-exceptions:
void
q3 (double mo)
{
mo = (mo / 0.0) * mo - mo;
}
% gcc-9.0.0-alpha20180520 -mfma -O2 -fexceptions -fnon-call-exceptions -c
hpyrkugn.c
during RTL pass: expand
hpyrkugn.c: In function 'q3':
hpyrkugn.c:4:6: internal compiler error: Segmentation fault
mo = (mo / 0.0) * mo - mo;
~~~^~~~~~~~~~~~~~~~~~~~~~
0xc9b59f crash_signal
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/toplev.c:325
0xa95733 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/tree.h:3248
0xa95733 expand_direct_optab_fn
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/internal-fn.c:2894
0x87e757 expand_call_stmt
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:2598
0x87e757 expand_gimple_stmt_1
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:3644
0x87e757 expand_gimple_stmt
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:3810
0x87fd9c expand_gimple_tailcall
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:3856
0x87fd9c expand_gimple_basic_block
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:5812
0x884837 execute
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:6441
This is not target-specific and also reproduces on powerpc (w/ appropriate
-mcpu) at least.
>From gcc-bugs-return-605200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 04:31:07 2018
Return-Path: <gcc-bugs-return-605200-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113204 invoked by alias); 21 May 2018 04:31:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113068 invoked by uid 48); 21 May 2018 04:30:50 -0000
From: "asolokha at gmx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85852] ICE: Segmentation fault (in contains_struct_check)
Date: Mon, 21 May 2018 04:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
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:
Message-ID: <bug-85852-4-0v4vCepYDQ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85852-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85852-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02095.txt.bz2
Content-length: 1820
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85852
--- Comment #1 from Arseny Solokha <asolokha at gmx dot com> ---
Here's a testcase w/o zero division:
void
ki (double nq)
{
double zo = 1.1 * nq - nq;
}
% gcc-9.0.0-alpha20180520 -mfma -O2 -fexceptions -fnon-call-exceptions -c
pr85852-1.c
during RTL pass: expand
pr85852-1.c: In function 'ki':
pr85852-1.c:4:10: internal compiler error: Segmentation fault
double zo = 1.1 * nq - nq;
^~
0xc9b59f crash_signal
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/toplev.c:325
0xa95733 contains_struct_check(tree_node*, tree_node_structure_enum, char
const*, int, char const*)
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/tree.h:3248
0xa95733 expand_direct_optab_fn
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/internal-fn.c:2894
0x87e757 expand_call_stmt
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:2598
0x87e757 expand_gimple_stmt_1
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:3644
0x87e757 expand_gimple_stmt
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:3810
0x87fd9c expand_gimple_tailcall
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:3856
0x87fd9c expand_gimple_basic_block
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:5812
0x884837 execute
/var/tmp/portage/sys-devel/gcc-9.0.0_alpha20180520/work/gcc-9-20180520/gcc/cfgexpand.c:6441
>From gcc-bugs-return-605201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 04:42:31 2018
Return-Path: <gcc-bugs-return-605201-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125492 invoked by alias); 21 May 2018 04:42: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 125323 invoked by uid 48); 21 May 2018 04:42:26 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/82914] 'struct __attribute__ ((aligned (N))) s' ignores 'aligned' attribute
Date: Mon, 21 May 2018 04: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.2.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: msebor at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-82914-4-XM6CpNoGOJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82914-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82914-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02096.txt.bz2
Content-length: 973
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82914
--- Comment #7 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Martin Sebor from comment #5)
> (In reply to Paul Eggert from comment #4)
> > Here, GCC says the alignment of 'b' is 1, not 8. What happened to the
> > attribute?
>
> GCC silently drops it, without validating it. For instance, this is
> accepted as well:
>
> struct s { char mem; };
>
> struct __attribute__ ((foobar))
> s b;
>
> I view it as a bug. At a minimum, GCC should point out that it's ignoring
> the attribute like other compilers do, such as Clang:
>
> warning: unknown attribute 'foobar' ignored [-Wunknown-attributes]
>
> I happened to notice this bug while testing a fix for pr84108. It seems
> that a simple fix is fairly straightforward so hopefully Richard won't be
> offended if I reopen this bug, assign it to myself, and submit my patch in
> stage 1 of GCC 9.
It's stage 1 of gcc 9 now.
>From gcc-bugs-return-605202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 06:36:06 2018
Return-Path: <gcc-bugs-return-605202-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 121469 invoked by alias); 21 May 2018 06:36: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 121319 invoked by uid 48); 21 May 2018 06:35:51 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Mon, 21 May 2018 06: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: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status assigned_to
Message-ID: <bug-85841-4-AqG7K07afW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02097.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid, diagnostic
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |janus at gcc dot gnu.org
>From gcc-bugs-return-605203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 06:46:34 2018
Return-Path: <gcc-bugs-return-605203-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118486 invoked by alias); 21 May 2018 06:46: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 118406 invoked by uid 55); 21 May 2018 06:46:28 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Mon, 21 May 2018 06: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.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85841-4-MLNvsTMRgO@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02098.txt.bz2
Content-length: 3347
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
--- Comment #3 from janus at gcc dot gnu.org ---
Author: janus
Date: Mon May 21 06:45:55 2018
New Revision: 260433
URL: https://gcc.gnu.org/viewcvs?rev=260433&root=gcc&view=rev
Log:
2018-05-21 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
* libgfortran.h: New macros GFC_STD_OPT_*.
* error.c (notify_std_msg): New function.
(gfc_notify_std): Adjust such that it can handle combinations of
GFC_STD_* flags in the 'std' argument, not just a single one.
* match.c (match_arithmetic_if, gfc_match_if): Reject arithmetic if
in Fortran 2018.
(gfc_match_stopcode): Use GFC_STD_OPT_* macros.
* options.c (set_default_std_flags): Warn for F2018 deleted features
by default.
(gfc_handle_option): F2018 deleted features are allowed in earlier
standards.
* symbol.c (gfc_define_st_label, gfc_reference_st_label): Reject
nonblock do constructs in Fortran 2018.
2018-05-21 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
* gfortran.dg/g77/19990826-3.f: Add option "-std=legacy".
* gfortran.dg/g77/20020307-1.f: Ditto.
* gfortran.dg/g77/980310-3.f: Ditto.
* gfortran.dg/goacc/loop-1-2.f95: Ditto.
* gfortran.dg/goacc/loop-1.f95: Ditto.
* gfortran.dg/gomp/appendix-a/a.6.1.f90: Ditto.
* gfortran.dg/gomp/appendix-a/a.6.2.f90: Ditto.
* gfortran.dg/gomp/do-1.f90: Ditto.
* gfortran.dg/gomp/omp_do1.f90: Ditto.
* gfortran.dg/pr17229.f: Ditto.
* gfortran.dg/pr37243.f: Ditto.
* gfortran.dg/pr49721-1.f: Ditto.
* gfortran.dg/pr58484.f: Ditto.
* gfortran.dg/pr81175.f: Ditto.
* gfortran.dg/pr81723.f: Ditto.
* gfortran.dg/predcom-2.f: Ditto.
* gfortran.dg/vect/Ofast-pr50414.f90: Ditto.
* gfortran.dg/vect/cost-model-pr34445a.f: Ditto.
* gfortran.dg/vect/fast-math-mgrid-resid.f: Ditto.
* gfortran.dg/vect/pr52580.f: Ditto.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/error.c
trunk/gcc/fortran/libgfortran.h
trunk/gcc/fortran/match.c
trunk/gcc/fortran/options.c
trunk/gcc/fortran/symbol.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/g77/19990826-3.f
trunk/gcc/testsuite/gfortran.dg/g77/20020307-1.f
trunk/gcc/testsuite/gfortran.dg/g77/980310-3.f
trunk/gcc/testsuite/gfortran.dg/goacc/loop-1-2.f95
trunk/gcc/testsuite/gfortran.dg/goacc/loop-1.f95
trunk/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.6.1.f90
trunk/gcc/testsuite/gfortran.dg/gomp/appendix-a/a.6.2.f90
trunk/gcc/testsuite/gfortran.dg/gomp/do-1.f90
trunk/gcc/testsuite/gfortran.dg/gomp/omp_do1.f90
trunk/gcc/testsuite/gfortran.dg/pr17229.f
trunk/gcc/testsuite/gfortran.dg/pr37243.f
trunk/gcc/testsuite/gfortran.dg/pr49721-1.f
trunk/gcc/testsuite/gfortran.dg/pr58484.f
trunk/gcc/testsuite/gfortran.dg/pr81175.f
trunk/gcc/testsuite/gfortran.dg/pr81723.f
trunk/gcc/testsuite/gfortran.dg/predcom-2.f
trunk/gcc/testsuite/gfortran.dg/vect/Ofast-pr50414.f90
trunk/gcc/testsuite/gfortran.dg/vect/cost-model-pr34445a.f
trunk/gcc/testsuite/gfortran.dg/vect/fast-math-mgrid-resid.f
trunk/gcc/testsuite/gfortran.dg/vect/pr52580.f
>From gcc-bugs-return-605204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 07:07:57 2018
Return-Path: <gcc-bugs-return-605204-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76866 invoked by alias); 21 May 2018 07: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 73686 invoked by uid 48); 21 May 2018 07:07:52 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Mon, 21 May 2018 07:07:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85841-4-s75izSJwmT@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02099.txt.bz2
Content-length: 303
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
--- Comment #4 from janus at gcc dot gnu.org ---
The diagnostics for the deleted features have been implemented in r260433.
As a minor follow-up, one should get rid of the GFC_STD_F2008_TS macro and make
-std=f2008ts an alias for -std=f2018.
>From gcc-bugs-return-605205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 07:35:57 2018
Return-Path: <gcc-bugs-return-605205-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 51960 invoked by alias); 21 May 2018 07:35:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 51858 invoked by uid 48); 21 May 2018 07:35:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85852] [9 Regression] ICE: Segmentation fault (in contains_struct_check)
Date: Mon, 21 May 2018 07:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc cf_known_to_work short_desc everconfirmed cf_known_to_fail
Message-ID: <bug-85852-4-tkzgqieVi9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85852-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85852-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02100.txt.bz2
Content-length: 992
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85852
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-21
CC| |marxin at gcc dot gnu.org,
| |rdsandiford at googlemail dot com
Known to work| |8.1.0
Summary|ICE: Segmentation fault (in |[9 Regression] ICE:
|contains_struct_check) |Segmentation fault (in
| |contains_struct_check)
Ever confirmed|0 |1
Known to fail| |9.0
--- Comment #2 from Martin Liška <marxin at gcc dot gnu.org> ---
Confirmed, started with r260348.
>From gcc-bugs-return-605207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 07:38:57 2018
Return-Path: <gcc-bugs-return-605207-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69241 invoked by alias); 21 May 2018 07: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 69083 invoked by uid 48); 21 May 2018 07:38:52 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85853] ICE in vect_is_simple_use, at tree-vect-stmts.c:10233 on ppc64le
Date: Mon, 21 May 2018 07:38:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on target_milestone everconfirmed
Message-ID: <bug-85853-4-SEZiuOraEo@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02102.txt.bz2
Content-length: 459
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85853
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-21
Target Milestone|--- |9.0
Ever confirmed|0 |1
>From gcc-bugs-return-605206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 07:38:47 2018
Return-Path: <gcc-bugs-return-605206-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68423 invoked by alias); 21 May 2018 07:38:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68263 invoked by uid 48); 21 May 2018 07:38:36 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85853] New: ICE in vect_is_simple_use, at tree-vect-stmts.c:10233 on ppc64le
Date: Mon, 21 May 2018 07: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: unknown
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-85853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02101.txt.bz2
Content-length: 1729
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85853
Bug ID: 85853
Summary: ICE in vect_is_simple_use, at tree-vect-stmts.c:10233
on ppc64le
Product: gcc
Version: unknown
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-linux-gnu
Target: ppc64le-linux-gnu
Following ICEs with current trunk:
$ ppc64-linux-gnu-gfortran
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.fortran-torture/execute/where_2.f90
-O3 -fno-tree-loop-vectorize
during GIMPLE pass: slp
/home/marxin/Programming/gcc/gcc/testsuite/gfortran.fortran-torture/execute/where_2.f90:22:0:
end program
internal compiler error: in vect_is_simple_use, at tree-vect-stmts.c:10233
0xe6d140 vect_is_simple_use(tree_node*, vec_info*, gimple**, vect_def_type*,
tree_node**)
.././../gcc/tree-vect-stmts.c:10233
0xe701d7 vect_get_mask_type_for_stmt(_stmt_vec_info*)
.././../gcc/tree-vect-stmts.c:10904
0xeae87c vect_slp_analyze_node_operations
.././../gcc/tree-vect-slp.c:2540
0xeae5a0 vect_slp_analyze_node_operations
.././../gcc/tree-vect-slp.c:2517
0xeb0fbf vect_slp_analyze_operations(vec_info*)
.././../gcc/tree-vect-slp.c:2613
0xeb1d7f vect_slp_analyze_bb_1
.././../gcc/tree-vect-slp.c:2919
0xeb1d7f vect_slp_bb(basic_block_def*)
.././../gcc/tree-vect-slp.c:3006
0xeb42d5 execute
.././../gcc/tree-vectorizer.c:1069
>From gcc-bugs-return-605208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 07:44:48 2018
Return-Path: <gcc-bugs-return-605208-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96238 invoked by alias); 21 May 2018 07:44: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 96060 invoked by uid 48); 21 May 2018 07:44:42 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85850] [9.0 Regression] gcc 9.0 doesn't compile with Xcode 9.3.1
Date: Mon, 21 May 2018 07: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: 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-85850-4-JlIFuRp0Sz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02103.txt.bz2
Content-length: 899
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85850
--- Comment #3 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Indeed, Janne is correct, this change in libcpp/system.h solves the problem,
i.e. moving the <new> definition up:
# diff -u system.h system.h.260425
--- system.h 2018-05-20 23:00:01.000000000 +0200
+++ system.h.260425 2018-05-20 22:55:27.000000000 +0200
@@ -370,10 +370,6 @@
#include "libiberty.h"
#include "safe-ctype.h"
-#ifdef __cplusplus
-#include <new>
-#endif
-
/* 1 if we have C99 designated initializers.
??? C99 designated initializers are not supported by most C++
@@ -442,6 +438,10 @@
/* Some compilers do not allow the use of unsigned char in bitfields. */
#define BOOL_BITFIELD unsigned int
+#ifdef __cplusplus
+#include <new>
+#endif
+
/* Poison identifiers we do not want to use. */
#if (GCC_VERSION >= 3000)
#undef calloc
>From gcc-bugs-return-605209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 10:25:39 2018
Return-Path: <gcc-bugs-return-605209-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44594 invoked by alias); 21 May 2018 10: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 43604 invoked by uid 48); 21 May 2018 10:25:33 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85833] [AVX512] use mask registers instructions instead of scalar code
Date: Mon, 21 May 2018 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: DUPLICATE
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-85833-4-S9LaOKcyTn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85833-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85833-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02104.txt.bz2
Content-length: 616
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85833
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jakub at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
And with -mavx512dq this is a dup of already fixed PR82855.
*** This bug has been marked as a duplicate of bug 82855 ***
>From gcc-bugs-return-605210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 10:25:40 2018
Return-Path: <gcc-bugs-return-605210-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45398 invoked by alias); 21 May 2018 10: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 43635 invoked by uid 48); 21 May 2018 10:25:34 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/82855] AVX512: replace OP+movemask with OP_mask+ktest
Date: Mon, 21 May 2018 10:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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: cc
Message-ID: <bug-82855-4-gYykmw9RY8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02105.txt.bz2
Content-length: 502
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82855
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |wojciech_mula at poczta dot onet.p
| |l
--- Comment #8 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
*** Bug 85833 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-605211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 11:37:23 2018
Return-Path: <gcc-bugs-return-605211-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59347 invoked by alias); 21 May 2018 11:37:23 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 59287 invoked by uid 48); 21 May 2018 11:37:18 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85850] [9.0 Regression] gcc 9.0 doesn't compile with Xcode 9.3.1
Date: Mon, 21 May 2018 11: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: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85850-4-SgQ2Gk54R8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85850-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02106.txt.bz2
Content-length: 1076
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85850
--- Comment #4 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Sorry, I meant Marc, of course. Confused this was another PR.
(In reply to Jürgen Reuter from comment #3)
> Indeed, Janne is correct, this change in libcpp/system.h solves the problem,
> i.e. moving the <new> definition up:
> # diff -u system.h system.h.260425
> --- system.h 2018-05-20 23:00:01.000000000 +0200
> +++ system.h.260425 2018-05-20 22:55:27.000000000 +0200
> @@ -370,10 +370,6 @@
> #include "libiberty.h"
> #include "safe-ctype.h"
>
> -#ifdef __cplusplus
> -#include <new>
> -#endif
> -
> /* 1 if we have C99 designated initializers.
>
> ??? C99 designated initializers are not supported by most C++
> @@ -442,6 +438,10 @@
> /* Some compilers do not allow the use of unsigned char in bitfields. */
> #define BOOL_BITFIELD unsigned int
>
> +#ifdef __cplusplus
> +#include <new>
> +#endif
> +
> /* Poison identifiers we do not want to use. */
> #if (GCC_VERSION >= 3000)
> #undef calloc
>From gcc-bugs-return-605212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:10:23 2018
Return-Path: <gcc-bugs-return-605212-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54605 invoked by alias); 21 May 2018 12:10: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 54441 invoked by uid 48); 21 May 2018 12:10:15 -0000
From: "wilco at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85666] gcc-8.0.1 fails to build mmix target: gcc/libgcc/libgcc2.h:203:20: internal compiler error: in leaf_function_p, at final.c:4488
Date: Mon, 21 May 2018 12: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: 8.0.1
X-Bugzilla-Keywords: build
X-Bugzilla-Severity: normal
X-Bugzilla-Who: wilco at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85666-4-FpXebvD0jB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85666-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85666-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02107.txt.bz2
Content-length: 2366
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85666
--- Comment #8 from Wilco <wilco at gcc dot gnu.org> ---
(In reply to Hans-Peter Nilsson from comment #7)
> Thank you for your interest in the MMIX port.
>
> (In reply to Wilco from comment #3)
> > (In reply to Sergei Trofimovich from comment #1)
> >
> > > #define MMIX_CFUN_NEEDS_SAVED_EH_RETURN_ADDRESS \
> > > (flag_exceptions \
> > > && ((reload_completed && df_regs_ever_live_p (MMIX_rJ_REGNUM)) \
> > > || !leaf_function_p ())) /// <- here
> >
> >
> > Yes that looks like a bug. leaf_function_p cannot be called on a sequence as
> > it will incorrectly return true on non-leaf functions. So
> > MMIX_CFUN_NEEDS_SAVED_EH_RETURN_ADDRESS will randomly change its result if
> > called again later. starting_frame_offset should however return a fixed
> > value, so the reload_completed part also looks wrong.
>
> Kindly refer to the comment above that macro:
>
> /* We have no means to tell DWARF 2 about the register stack, so we need
> to store the return address on the stack if an exception can get into
> this function. FIXME: Narrow condition. Before any whole-function
> analysis, df_regs_ever_live_p () isn't initialized. We know it's
> up-to-date
> after reload_completed; it may contain incorrect information some time
> before that. Within a RTL sequence (after a call to start_sequence,
> such as in RTL expanders), leaf_function_p doesn't see all insns
> (perhaps any insn). But regs_ever_live is up-to-date when
> leaf_function_p () isn't, so we "or" them together to get accurate
> information. FIXME: Some tweak to leaf_function_p might be
> preferable. */
>
> So, it looks like the time has come for "some tweak to leaf_function_p",
> or...some other tweak. Yes, this was a brittle solution and someone saw fit
> to pull the rug. Maybe I'll have to compute the starting frame offset some
> other way.
I don't think that comment is accurate. The failure happens in cfgexpand before
any RTL has been generated, so leaf_function_p must not be called this early.
If starting_frame_offset doesn't remain constant things can go badly wrong.
The easiest fix is to always allocate an extra stack slot with exceptions and
then avoid generating extra code in the prolog/epilog if it happens to be a
leaf function.
>From gcc-bugs-return-605213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:19:14 2018
Return-Path: <gcc-bugs-return-605213-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 78648 invoked by alias); 21 May 2018 12: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 75850 invoked by uid 48); 21 May 2018 12:19:09 -0000
From: "sudi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 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: 8.1.1
X-Bugzilla-Keywords: link-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sudi 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85818-4-pqgzWRtyD4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02108.txt.bz2
Content-length: 840
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
sudi at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sudi at gcc dot gnu.org
--- Comment #4 from sudi at gcc dot gnu.org ---
I have observed the following failures on baremetals aarch64-none-elf,
aarch64_be-none-elf and arm-none-eabi nightly tests for both trunk and gcc-8
branch.
FAIL: experimental/filesystem/path/preferred_separator.cc (test for excess
errors)
with
compilation terminated.
compiler exited with status 1
output is:
/build/src/gcc/libstdc++-v3/testsuite/experimental/filesystem/path/preferred_separator.cc:21:
fatal error: experimental/filesystem: No such file or directory
compilation terminated.
>From gcc-bugs-return-605214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:20:38 2018
Return-Path: <gcc-bugs-return-605214-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84009 invoked by alias); 21 May 2018 12:20:37 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83568 invoked by uid 48); 21 May 2018 12:20:33 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 12: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: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85818-4-DC9y34nwTz@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02109.txt.bz2
Content-length: 466
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |---
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Oops, the test should be disabled on that target.
>From gcc-bugs-return-605215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:22:49 2018
Return-Path: <gcc-bugs-return-605215-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89087 invoked by alias); 21 May 2018 12:22: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 89030 invoked by uid 48); 21 May 2018 12:22:44 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85832] [AVX512] possible shorter code when comparing with vector of zeros
Date: Mon, 21 May 2018 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: 7.3.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: 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-85832-4-KnuiDCTRLg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02110.txt.bz2
Content-length: 3019
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85832
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-21
CC| |jakub at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Untested fix:
--- gcc/config/i386/sse.md.jj 2018-05-21 13:15:43.478581765 +0200
+++ gcc/config/i386/sse.md 2018-05-21 14:15:00.523635533 +0200
@@ -11210,26 +11210,30 @@
"ix86_fixup_binary_operands_no_copy (EQ, <MODE>mode, operands);")
(define_insn "<avx512>_eq<mode>3<mask_scalar_merge_name>_1"
- [(set (match_operand:<avx512fmaskmode> 0 "register_operand" "=Yk")
+ [(set (match_operand:<avx512fmaskmode> 0 "register_operand" "=Yk,Yk")
(unspec:<avx512fmaskmode>
- [(match_operand:VI12_AVX512VL 1 "nonimmediate_operand" "%v")
- (match_operand:VI12_AVX512VL 2 "nonimmediate_operand" "vm")]
+ [(match_operand:VI12_AVX512VL 1 "nonimmediate_operand" "%v,v")
+ (match_operand:VI12_AVX512VL 2 "vector_move_operand" "vm,C")]
UNSPEC_MASKED_EQ))]
- "TARGET_AVX512F && !(MEM_P (operands[1]) && MEM_P (operands[2]))"
- "vpcmpeq<ssemodesuffix>\t{%2, %1,
%0<mask_scalar_merge_operand3>|%0<mask_scalar_merge_operand3>, %1, %2}"
+ "TARGET_AVX512BW && !(MEM_P (operands[1]) && MEM_P (operands[2]))"
+ "@
+ vpcmpeq<ssemodesuffix>\t{%2, %1,
%0<mask_scalar_merge_operand3>|%0<mask_scalar_merge_operand3>, %1, %2}
+ vptestm<ssemodesuffix>\t{%1, %1,
%0<mask_scalar_merge_operand3>|%0<mask_scalar_merge_operand3>, %1, %1}"
[(set_attr "type" "ssecmp")
(set_attr "prefix_extra" "1")
(set_attr "prefix" "evex")
(set_attr "mode" "<sseinsnmode>")])
(define_insn "<avx512>_eq<mode>3<mask_scalar_merge_name>_1"
- [(set (match_operand:<avx512fmaskmode> 0 "register_operand" "=Yk")
+ [(set (match_operand:<avx512fmaskmode> 0 "register_operand" "=Yk,Yk")
(unspec:<avx512fmaskmode>
- [(match_operand:VI48_AVX512VL 1 "nonimmediate_operand" "%v")
- (match_operand:VI48_AVX512VL 2 "nonimmediate_operand" "vm")]
+ [(match_operand:VI48_AVX512VL 1 "nonimmediate_operand" "%v,v")
+ (match_operand:VI48_AVX512VL 2 "vector_move_operand" "vm,C")]
UNSPEC_MASKED_EQ))]
"TARGET_AVX512F && !(MEM_P (operands[1]) && MEM_P (operands[2]))"
- "vpcmpeq<ssemodesuffix>\t{%2, %1,
%0<mask_scalar_merge_operand3>|%0<mask_scalar_merge_operand3>, %1, %2}"
+ "@
+ vpcmpeq<ssemodesuffix>\t{%2, %1,
%0<mask_scalar_merge_operand3>|%0<mask_scalar_merge_operand3>, %1, %2}
+ vptestm<ssemodesuffix>\t{%1, %1,
%0<mask_scalar_merge_operand3>|%0<mask_scalar_merge_operand3>, %1, %1}"
[(set_attr "type" "ssecmp")
(set_attr "prefix_extra" "1")
(set_attr "prefix" "evex")
>From gcc-bugs-return-605216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:27:37 2018
Return-Path: <gcc-bugs-return-605216-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 99094 invoked by alias); 21 May 2018 12:27: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 99046 invoked by uid 55); 21 May 2018 12:27:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 12:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85818-4-m0D7SkoLZ2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02111.txt.bz2
Content-length: 595
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon May 21 12:27:00 2018
New Revision: 260439
URL: https://gcc.gnu.org/viewcvs?rev=260439&root=gcc&view=rev
Log:
PR libstdc++/85818 make new test require Filesystem support
PR libstdc++/85818
* testsuite/experimental/filesystem/path/preferred_separator.cc: Add
dg-require-filesystem-ts.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/testsuite/experimental/filesystem/path/preferred_separator.cc
>From gcc-bugs-return-605217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:30:47 2018
Return-Path: <gcc-bugs-return-605217-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 104700 invoked by alias); 21 May 2018 12:30: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 104271 invoked by uid 55); 21 May 2018 12:30:06 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 12:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85818-4-WWPoCdooV5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02112.txt.bz2
Content-length: 627
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Author: redi
Date: Mon May 21 12:29:33 2018
New Revision: 260440
URL: https://gcc.gnu.org/viewcvs?rev=260440&root=gcc&view=rev
Log:
PR libstdc++/85818 make new test require Filesystem support
PR libstdc++/85818
* testsuite/experimental/filesystem/path/preferred_separator.cc: Add
dg-require-filesystem-ts.
Modified:
branches/gcc-8-branch/libstdc++-v3/ChangeLog
branches/gcc-8-branch/libstdc++-v3/testsuite/experimental/filesystem/path/preferred_separator.cc
>From gcc-bugs-return-605219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:31:23 2018
Return-Path: <gcc-bugs-return-605219-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105165 invoked by alias); 21 May 2018 12:31:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 104706 invoked by uid 55); 21 May 2018 12:30:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85818-4-Uq6wzj2CXM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02114.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Should be OK now.
>From gcc-bugs-return-605218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 12:31:11 2018
Return-Path: <gcc-bugs-return-605218-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105134 invoked by alias); 21 May 2018 12:31: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 104709 invoked by uid 48); 21 May 2018 12:30:43 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 12:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.1.1
X-Bugzilla-Keywords: link-failure
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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85818-4-oXYlX2UN4r@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02113.txt.bz2
Content-length: 436
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution|--- |FIXED
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Should be OK now.
>From gcc-bugs-return-605220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 13:06:30 2018
Return-Path: <gcc-bugs-return-605220-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 86848 invoked by alias); 21 May 2018 13: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 86807 invoked by uid 48); 21 May 2018 13:06:25 -0000
From: "beldmit at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85854] New: Performance regression from gcc 4.9.2
Date: Mon, 21 May 2018 13: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: beldmit 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-85854-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02115.txt.bz2
Content-length: 4118
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85854
Bug ID: 85854
Summary: Performance regression from gcc 4.9.2
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: beldmit at gmail dot com
Target Milestone: ---
Created attachment 44154
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44154&action=edit
Preprocessing file.
I got a serious (10%) performance degradation using cross-compiler for ARM.
Compiler version:
arm-linux-gnueabihf-gcc-8 -v
Using built-in specs.
COLLECT_GCC=arm-linux-gnueabihf-gcc-8
COLLECT_LTO_WRAPPER=/usr/lib/gcc-cross/arm-linux-gnueabihf/8/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Debian 8.1.0-3'
--with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs
--enable-languages=c,ada,c++,go,d,fortran,objc,obj-c++ --prefix=/usr
--with-gcc-major-version-only --program-suffix=-8 --enable-shared
--enable-linker-build-id --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --libdir=/usr/lib --enable-nls --with-sysroot=/
--enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object --disable-libitm
--disable-libquadmath --disable-libquadmath-support --enable-plugin
--enable-default-pie --with-system-zlib --with-target-system-zlib
--enable-multiarch --disable-sjlj-exceptions --with-arch=armv7-a
--with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb --disable-werror
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu
--target=arm-linux-gnueabihf --program-prefix=arm-linux-gnueabihf-
--includedir=/usr/arm-linux-gnueabihf/include
Thread model: posix
gcc version 8.1.0 (Debian 8.1.0-3)
System: Linux x-debian 4.16.0-1-amd64 #1 SMP Debian 4.16.5-1 (2018-04-29)
x86_64 GNU/Linux
Compiler options:
arm-linux-gnueabihf-gcc-8 -c -DSTRICT_OFFSET -mfpu=neon -O1 -D_REENTRANT
-DTHREAD_TYPE=THREAD_TYPE_PTHREADS -fPIC -DNDEBUG -DCC_NO_RDS_SOCKET
-DCC_NO_RDS_FILECNT -DCC_NO_RDS_NP -D_GNU_SOURCE -pedantic -Wall -Wextra
-Wno-long-long -g -save-temps gosthash2012.c
The preprocessed file is attached. The most time-taking part of the code is the
function named g.
The new version does not use neon vector ops (such as veor) at all, but the
4.9.2 on native ARM system does.
The system withoud degradation is
Linux odroid 3.10.107 #1 SMP PREEMPT Wed Sep 13 18:48:10 CEST 2017 armv7l
GNU/Linux
gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/arm-linux-gnueabihf/4.9/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../src/configure -v --with-pkgversion='Debian 4.9.2-10'
--with-bugurl=file:///usr/share/doc/gcc-4.9/README.Bugs
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-4.9 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--with-gxx-include-dir=/usr/include/c++/4.9 --libdir=/usr/lib --enable-nls
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libitm
--disable-libquadmath --enable-plugin --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf/jre --enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.9-armhf
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.9-armhf
--with-arch-directory=arm --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-sjlj-exceptions
--with-arch=armv7-a --with-fpu=vfpv3-d16 --with-float=hard --with-mode=thumb
--enable-checking=release --build=arm-linux-gnueabihf
--host=arm-linux-gnueabihf --target=arm-linux-gnueabihf
Thread model: posix
gcc version 4.9.2 (Debian 4.9.2-10)
>From gcc-bugs-return-605221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 13:22:23 2018
Return-Path: <gcc-bugs-return-605221-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54363 invoked by alias); 21 May 2018 13:22: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 54313 invoked by uid 48); 21 May 2018 13:22:19 -0000
From: "sudi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85818] [8/9 Regression] undefined reference to `std::experimental::filesystem::v1::__cxx11::path::preferred_separator'
Date: Mon, 21 May 2018 13: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: 8.1.1
X-Bugzilla-Keywords: link-failure
X-Bugzilla-Severity: normal
X-Bugzilla-Who: sudi 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85818-4-VS6Ob4mOat@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85818-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02116.txt.bz2
Content-length: 110
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85818
--- Comment #9 from sudi at gcc dot gnu.org ---
Thanks!
>From gcc-bugs-return-605222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 13:23:58 2018
Return-Path: <gcc-bugs-return-605222-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62158 invoked by alias); 21 May 2018 13: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 61999 invoked by uid 48); 21 May 2018 13:23:52 -0000
From: "vda.linux at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66240] RFE: extend -falign-xyz syntax
Date: Mon, 21 May 2018 13:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 5.1.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vda.linux at googlemail dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-66240-4-9MfmsLwYsc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66240-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66240-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02117.txt.bz2
Content-length: 365
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66240
--- Comment #7 from Denis Vlasenko <vda.linux at googlemail dot com> ---
Patch v8
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00792.html
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00793.html
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00794.html
https://gcc.gnu.org/ml/gcc-patches/2017-04/msg00795.html
>From gcc-bugs-return-605223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 13:28:14 2018
Return-Path: <gcc-bugs-return-605223-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66361 invoked by alias); 21 May 2018 13:28: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 66286 invoked by uid 48); 21 May 2018 13:28:10 -0000
From: "vda.linux at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/45996] -falign-functions=X does not work
Date: Mon, 21 May 2018 13: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vda.linux at googlemail dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-45996-4-4RqoCyGywX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-45996-4@http.gcc.gnu.org/bugzilla/>
References: <bug-45996-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02118.txt.bz2
Content-length: 416
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=45996
Denis Vlasenko <vda.linux at googlemail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vda.linux at googlemail dot com
--- Comment #8 from Denis Vlasenko <vda.linux at googlemail dot com> ---
See bug 66240
>From gcc-bugs-return-605224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 13:37:41 2018
Return-Path: <gcc-bugs-return-605224-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 82805 invoked by alias); 21 May 2018 13:37: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 82759 invoked by uid 48); 21 May 2018 13:37:37 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85832] [AVX512] possible shorter code when comparing with vector of zeros
Date: Mon, 21 May 2018 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: 7.3.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: assigned_to attachments.created
Message-ID: <bug-85832-4-iEJ2SpOmYj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85832-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85832-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02119.txt.bz2
Content-length: 527
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85832
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
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 44155
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44155&action=edit
gcc8-pr85832.patch
Untested full patch.
>From gcc-bugs-return-605226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 14:33:57 2018
Return-Path: <gcc-bugs-return-605226-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94446 invoked by alias); 21 May 2018 14:33:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94367 invoked by uid 48); 21 May 2018 14:33:53 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/81771] __basic_file::sys_open is not a reserved name
Date: Mon, 21 May 2018 14:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-81771-4-lDsBWT46CB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81771-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81771-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02121.txt.bz2
Content-length: 182
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81771
--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 70727 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-605225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 14:33:57 2018
Return-Path: <gcc-bugs-return-605225-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94437 invoked by alias); 21 May 2018 14:33:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 94351 invoked by uid 48); 21 May 2018 14:33:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/70727] Non-reserved names in std::__basic_file
Date: Mon, 21 May 2018 14:33:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.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-70727-4-DMUc2vJMcD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70727-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70727-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02120.txt.bz2
Content-length: 488
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70727
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
.
*** This bug has been marked as a duplicate of bug 81771 ***
>From gcc-bugs-return-605227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 14:37:51 2018
Return-Path: <gcc-bugs-return-605227-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107031 invoked by alias); 21 May 2018 14:37: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 106954 invoked by uid 48); 21 May 2018 14:37:45 -0000
From: "vladimir.fuka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85855] New: [7 Regression] (Maybe) uninitialized descriptor fields of an allocatable array component of a function result
Date: Mon, 21 May 2018 14:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vladimir.fuka 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-85855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02122.txt.bz2
Content-length: 3468
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
Bug ID: 85855
Summary: [7 Regression] (Maybe) uninitialized descriptor fields
of an allocatable array component of a function result
Product: gcc
Version: 7.3.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: vladimir.fuka at gmail dot com
Target Milestone: ---
This code does not issue any warning in GCC 4.8 to 6 but does for GCC 7.3.1:
module test
implicit none
type grid
integer, allocatable :: mask(:,:,:)
end type
contains
function reduce(g) result(res)
type(grid) :: res
class(grid), intent(in) :: g
res%mask = g%mask
end function
end module
> gfortran-7 -c uninit2.f90 -fbacktrace -g -Wall
uninit2.f90:14:0:
res%mask = g%mask
Warning: ‘res.mask.offset’ is used uninitialized in this function
[-Wuninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[0].lbound’ is used uninitialized in
this function [-Wuninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[0].ubound’ is used uninitialized in
this function [-Wuninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[1].lbound’ is used uninitialized in
this function [-Wuninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[1].ubound’ is used uninitialized in
this function [-Wuninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[2].lbound’ is used uninitialized in
this function [-Wuninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[2].ubound’ is used uninitialized in
this function [-Wuninitialized]
uninit2.f90:14:0:
res%mask = g%mask
Warning: ‘res.mask.dim[0].lbound’ may be used uninitialized in this function
[-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[0].ubound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[1].lbound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[1].ubound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[2].lbound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[2].ubound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[0].ubound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[0].lbound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[1].ubound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[1].lbound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[2].ubound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
uninit2.f90:14:0: Warning: ‘res.mask.dim[2].lbound’ may be used uninitialized
in this function [-Wmaybe-uninitialized]
>From gcc-bugs-return-605228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 15:01:32 2018
Return-Path: <gcc-bugs-return-605228-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5606 invoked by alias); 21 May 2018 15:01: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 4370 invoked by uid 48); 21 May 2018 15:00:57 -0000
From: "msharov at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85856] New: -Weffc++ can't see implicitly deleted constructor
Date: Mon, 21 May 2018 15:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msharov at users dot sourceforge.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-85856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02123.txt.bz2
Content-length: 1258
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85856
Bug ID: 85856
Summary: -Weffc++ can't see implicitly deleted constructor
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: msharov at users dot sourceforge.net
Target Milestone: ---
#include <stdio.h>
struct A {
A (void) {}
virtual ~A (void) {}
A (const A&) = delete;
void operator= (const A&) = delete;
};
struct B : public A {
B (const char* p) :A(),_p(p) {}
const char* _p;
};
int main (void)
{
B b ("hello");
puts (b._p);
return 0;
}
When compiling with -Weffc++ enabled, generates:
t.cc:10:8: warning: ‘struct B’ has pointer data members [-Weffc++]
struct B : public A {
^
t.cc:10:8: warning: but does not override ‘B(const B&)’ [-Weffc++]
t.cc:10:8: warning: or ‘operator=(const B&)’ [-Weffc++]
B already has an implicitly deleted copy constructor and operator= because A
implements them deleted. The compiler will correctly give a warning about it on
B b2=b, for example.
>From gcc-bugs-return-605229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 15:28:04 2018
Return-Path: <gcc-bugs-return-605229-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109183 invoked by alias); 21 May 2018 15:28: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 109101 invoked by uid 48); 21 May 2018 15:27:59 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/85857] New: configure problem using local mpfr and gmp
Date: Mon, 21 May 2018 15:28: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: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85857-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02124.txt.bz2
Content-length: 2193
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85857
Bug ID: 85857
Summary: configure problem using local mpfr and gmp
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
There is a problem with configure if you use a local copy of mpfr and gmp
(grabbed via contrib/download_prerequisites) and then use
--enable-decimal-float on the configure for gcc itself. It occurs in gcc 7 as
well as in trunk (didn't try 6 or 8 but probably there, too).
$ $GCC_SRC/configure --prefix=$GCC_INSTALL --enable-languages=c,fortran,c++
--disable-bootstrap --disable-multilib --enable-decimal-float
$ make
. . .
configure: error: decimal float support requires --with-gmp-build
make[1]: *** [configure-mpfr] Error 1
I ran into this on a powerpc64 system but have duplicated it on an x86 system.
Adding --with-gmp-build as suggested doesn't work, either:
configure: error: in `/home/seurer/gcc/build/gcc-test/mpfr':
configure: error: Do not use --with-gmp-build and other --with-gmp options
simultaneously.
make[1]: *** [configure-mpfr] Error 1
Details from the config.log for mpfr:
$ cat mpfr/config.log
. . .
$ /home/seurer/gcc/gcc-test/mpfr/configure
--srcdir=/home/seurer/gcc/gcc-test/mpfr --cache-file=./config.cache
--prefix=/home/seurer/gcc/install/gcc-test --disable-bootstrap
--disable-multilib --enable-decimal-float --enable-languages=c,c++,fortran,lto
--program-transform-name=s,y,y, --disable-option-checking
--build=x86_64-pc-linux-gnu --host=x86_64-pc-linux-gnu
--target=x86_64-pc-linux-gnu --disable-shared
--with-gmp-include=/home/seurer/gcc/build/gcc-test/./gmp
--with-gmp-lib=/home/seurer/gcc/build/gcc-test/./gmp/.libs
. . .
configure:5164: checking if compiler knows _Decimal64
configure:5177: /usr/bin/gcc -c -g -O2 -I/home/seurer/gcc/build/gcc-test/gmp
conftest.c >&5
configure:5177: $? = 0
configure:5178: result: yes
configure:5181: error: decimal float support requires --with-gmp-build
>From gcc-bugs-return-605230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 15:28:12 2018
Return-Path: <gcc-bugs-return-605230-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109836 invoked by alias); 21 May 2018 15:28: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 109195 invoked by uid 48); 21 May 2018 15:28:04 -0000
From: "msharov at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] New: -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 15: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: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msharov at users dot sourceforge.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-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02125.txt.bz2
Content-length: 810
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
Bug ID: 85858
Summary: -Weffc++ should not require copy ctor for const
pointers
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: msharov at users dot sourceforge.net
Target Milestone: ---
-Weffc++ warns about missing operator= and copy ctor in a class containing a
const pointer. The intent of the warning is to detect manually allocated memory
owned by the class, and to ensure copying operation was explicitly considered.
When the pointer is const, it can not point to owned memory and so should not
result in a warning.
>From gcc-bugs-return-605231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 15:29:16 2018
Return-Path: <gcc-bugs-return-605231-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111032 invoked by alias); 21 May 2018 15:29: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 111006 invoked by uid 48); 21 May 2018 15:29:12 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85859] New: [6/7/8/9 Regression] wrong code with -fno-isolate-erroneous-paths-dereference
Date: Mon, 21 May 2018 15:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget attachments.created
Message-ID: <bug-85859-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02126.txt.bz2
Content-length: 1887
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85859
Bug ID: 85859
Summary: [6/7/8/9 Regression] wrong code with
-fno-isolate-erroneous-paths-dereference
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: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Created attachment 44156
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44156&action=edit
reduced testcase
Output:
$ x86_64-pc-linux-gnu-gcc -O2 -fno-dce -fno-isolate-erroneous-paths-dereference
-fno-tree-dce -fno-tree-vrp testcase.c
testcase.c: In function 'foo':
testcase.c:6:5: warning: division by zero [-Wdiv-by-zero]
f %= 0;
^~
$ ./a.out
Floating point exception
The division by zero should not be executed.
$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-260408-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-260408-checking-yes-rtl-df-extra-amd64
Thread model: posix
gcc version 9.0.0 20180520 (experimental) (GCC)
>From gcc-bugs-return-605232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 15:49:06 2018
Return-Path: <gcc-bugs-return-605232-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19884 invoked by alias); 21 May 2018 15: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 19528 invoked by uid 48); 21 May 2018 15:48:53 -0000
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85860] New: [8/9 Regression] ICE: in lra_split_hard_reg_for, at lra-assigns.c:1810: unable to find a register to spill with -flive-range-shrinkage -mbmi2
Date: Mon, 21 May 2018 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: zsojka at seznam dot cz
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status keywords bug_severity priority component assigned_to reporter target_milestone cf_gcchost cf_gcctarget attachments.created
Message-ID: <bug-85860-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02127.txt.bz2
Content-length: 2737
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85860
Bug ID: 85860
Summary: [8/9 Regression] ICE: in lra_split_hard_reg_for, at
lra-assigns.c:1810: unable to find a register to spill
with -flive-range-shrinkage -mbmi2
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: zsojka at seznam dot cz
Target Milestone: ---
Host: x86_64-pc-linux-gnu
Target: x86_64-pc-linux-gnu
Created attachment 44157
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44157&action=edit
reduced testcase
Compiler output:
$ x86_64-pc-linux-gnu-gcc -O2 -fno-guess-branch-probability
-flive-range-shrinkage -mbmi2 testcase.c
testcase.c: In function 'foo':
testcase.c:20:1: error: unable to find a register to spill
}
^
testcase.c:20:1: error: this is the insn:
(insn 214 65 201 3 (set (reg:DI 208)
(reg:DI 1 dx)) "testcase.c":15 85 {*movdi_internal}
(expr_list:REG_DEAD (reg:DI 1 dx)
(nil)))
during RTL pass: reload
testcase.c:20:1: internal compiler error: in lra_split_hard_reg_for, at
lra-assigns.c:1810
0x67a94c _fatal_insn(char const*, rtx_def const*, char const*, int, char
const*)
/repo/gcc-trunk/gcc/rtl-error.c:108
0xc47293 lra_split_hard_reg_for()
/repo/gcc-trunk/gcc/lra-assigns.c:1810
0xc40ee9 lra(_IO_FILE*)
/repo/gcc-trunk/gcc/lra.c:2507
0xbef719 do_reload
/repo/gcc-trunk/gcc/ira.c:5465
0xbef719 execute
/repo/gcc-trunk/gcc/ira.c:5649
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.
$ x86_64-pc-linux-gnu-gcc -v
Using built-in specs.
COLLECT_GCC=/repo/gcc-trunk/binary-latest-amd64/bin/x86_64-pc-linux-gnu-gcc
COLLECT_LTO_WRAPPER=/repo/gcc-trunk/binary-trunk-260408-checking-yes-rtl-df-extra-amd64/bin/../libexec/gcc/x86_64-pc-linux-gnu/9.0.0/lto-wrapper
Target: x86_64-pc-linux-gnu
Configured with: /repo/gcc-trunk//configure --enable-languages=c,c++
--enable-valgrind-annotations --disable-nls --enable-checking=yes,rtl,df,extra
--with-cloog --with-ppl --with-isl --build=x86_64-pc-linux-gnu
--host=x86_64-pc-linux-gnu --target=x86_64-pc-linux-gnu
--with-ld=/usr/bin/x86_64-pc-linux-gnu-ld
--with-as=/usr/bin/x86_64-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-260408-checking-yes-rtl-df-extra-amd64
Thread model: posix
gcc version 9.0.0 20180520 (experimental) (GCC)
>From gcc-bugs-return-605233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:18:21 2018
Return-Path: <gcc-bugs-return-605233-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39022 invoked by alias); 21 May 2018 16:18:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 38982 invoked by uid 48); 21 May 2018 16:18:15 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] New: g++ -Wconversion misses int to size_t
Date: Mon, 21 May 2018 16:18:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
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 attachments.created
Message-ID: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02128.txt.bz2
Content-length: 1775
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
Bug ID: 85861
Summary: g++ -Wconversion misses int to size_t
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jg at jguk dot org
Target Milestone: ---
Created attachment 44158
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44158&action=edit
C code example
g++ has a missing warning that gcc does display. please see below
Sorry I do not have a newer version of GCC myself. Although I did test online
with G++ 8.1 here: https://godbolt.org/ and same issue
jonny@asus:~$ gcc --version
gcc (Ubuntu 5.4.0-6ubuntu1~16.04.9) 5.4.0 20160609
jonny@asus:~$ g++ -o main main.c -Wall -Werror -Wconversion
main.c: In function ‘int main()’:
main.c:11:12: error: conversion to ‘int’ from ‘size_t {aka long unsigned int}’
may alter its value [-Werror=conversion]
return converted;
^
cc1plus: all warnings being treated as errors
jonny@asus:~$
jonny@asus:~$
jonny@asus:~$
jonny@asus:~$ gcc -o main main.c -Wall -Werror -Wconversion
main.c: In function ‘main’:
main.c:9:24: error: conversion to ‘size_t {aka long unsigned int}’ from ‘int’
may change the sign of the result [-Werror=sign-conversion]
size_t converted = value;
^
main.c:11:12: error: conversion to ‘int’ from ‘size_t {aka long unsigned int}’
may alter its value [-Werror=conversion]
return converted;
^
cc1: all warnings being treated as errors
>From gcc-bugs-return-605234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:23:59 2018
Return-Path: <gcc-bugs-return-605234-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72322 invoked by alias); 21 May 2018 16:23:59 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 69904 invoked by uid 55); 21 May 2018 16:23:53 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
Date: Mon, 21 May 2018 16:23:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85698-4-7TExse5xhK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02129.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #11 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
Author: pthaugen
Date: Mon May 21 16:23:20 2018
New Revision: 260475
URL: https://gcc.gnu.org/viewcvs?rev=260475&root=gcc&view=rev
Log:
PR target/85698
* config/rs6000/rs6000.c (rs6000_output_move_128bit): Check dest
operand.
* gcc.target/powerpc/pr85698.c: New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gcc.target/powerpc/pr85698.c
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/rs6000/rs6000.c
branches/gcc-8-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:35:22 2018
Return-Path: <gcc-bugs-return-605235-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6783 invoked by alias); 21 May 2018 16:35: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 6701 invoked by uid 55); 21 May 2018 16:35:16 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
Date: Mon, 21 May 2018 16:35:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85698-4-fR7L191Uha@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02130.txt.bz2
Content-length: 651
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #12 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
Author: pthaugen
Date: Mon May 21 16:34:44 2018
New Revision: 260476
URL: https://gcc.gnu.org/viewcvs?rev=260476&root=gcc&view=rev
Log:
PR target/85698
* config/rs6000/rs6000.c (rs6000_output_move_128bit): Check dest
operand.
* gcc.target/powerpc/pr85698.c: New test.
Added:
branches/gcc-7-branch/gcc/testsuite/gcc.target/powerpc/pr85698.c
Modified:
branches/gcc-7-branch/gcc/ChangeLog
branches/gcc-7-branch/gcc/config/rs6000/rs6000.c
branches/gcc-7-branch/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:41:46 2018
Return-Path: <gcc-bugs-return-605236-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 15150 invoked by alias); 21 May 2018 16:41: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 15064 invoked by uid 55); 21 May 2018 16:41:41 -0000
From: "pthaugen at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85698] [8/9 Regression] CPU2017 525.x264_r fails starting with r257581
Date: Mon, 21 May 2018 16:41:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pthaugen 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.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85698-4-pIpF38khpl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85698-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02131.txt.bz2
Content-length: 494
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85698
--- Comment #13 from Pat Haugen <pthaugen at gcc dot gnu.org> ---
Author: pthaugen
Date: Mon May 21 16:41:09 2018
New Revision: 260477
URL: https://gcc.gnu.org/viewcvs?rev=260477&root=gcc&view=rev
Log:
PR target/85698
* gcc.target/powerpc/vec-setup-be-long.c: Remove XFAIL.
Modified:
branches/gcc-8-branch/gcc/testsuite/ChangeLog
branches/gcc-8-branch/gcc/testsuite/gcc.target/powerpc/vec-setup-be-long.c
>From gcc-bugs-return-605237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:52:24 2018
Return-Path: <gcc-bugs-return-605237-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111933 invoked by alias); 21 May 2018 16: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 110159 invoked by uid 55); 21 May 2018 16:52:20 -0000
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85845] [9 Regression] Many libstdc++ test failures
Date: Mon, 21 May 2018 16:52:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fdumont at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fdumont at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85845-4-wX7XJE7qoP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02132.txt.bz2
Content-length: 576
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85845
--- Comment #2 from François Dumont <fdumont at gcc dot gnu.org> ---
Author: fdumont
Date: Mon May 21 16:51:47 2018
New Revision: 260478
URL: https://gcc.gnu.org/viewcvs?rev=260478&root=gcc&view=rev
Log:
2018-05-21 François Dumont <fdumont@gcc.gnu.org>
PR libstdc++/85845
* include/bits/stl_tree.h
(_Rb_tree_impl(_Rb_tree_impl&&, _Node_allocator&&)): Fix noexcept
qualification.
Modified:
trunk/libstdc++-v3/ChangeLog
trunk/libstdc++-v3/include/bits/stl_tree.h
>From gcc-bugs-return-605238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:57:25 2018
Return-Path: <gcc-bugs-return-605238-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 30708 invoked by alias); 21 May 2018 16:57: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 29888 invoked by uid 48); 21 May 2018 16:57:18 -0000
From: "tnfchris at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85769] [8/9 Regression] ICE in extract_constrain_insn, at recog.c:2205 for -mcpu=thunderx
Date: Mon, 21 May 2018 16:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tnfchris at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: tnfchris at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85769-4-cSeFH3qcew@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85769-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85769-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02133.txt.bz2
Content-length: 261
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85769
--- Comment #4 from Tamar Christina <tnfchris at gcc dot gnu.org> ---
I have a patch to add the missing case, but that'll just mask the reload bug,
so I'm holding up on posting it while looking at reload.
>From gcc-bugs-return-605239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:58:18 2018
Return-Path: <gcc-bugs-return-605239-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 37498 invoked by alias); 21 May 2018 16: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 37410 invoked by uid 48); 21 May 2018 16:58:14 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] g++ -Wconversion misses int to size_t
Date: Mon, 21 May 2018 16: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: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85861-4-rv9Y3siA8z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02134.txt.bz2
Content-length: 1169
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-21
Ever confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
You didn't provide the output of `gcc -v` as required, but I suspect you're
compiling for 32-bit, otherwise you'd get a warning:
mozilla_jwakely0/main.c: In function 'int main()':
mozilla_jwakely0/main.c:11:12: error: conversion to 'int' from 'size_t {aka
long unsigned int}' may alter its value [-Werror=conversion]
return converted;
^
cc1plus: all warnings being treated as errors
For 32-bit where int and size_t are the same size you need to use
-Wsign-conversion, as documented in the manual:
Warnings about conversions between signed and unsigned integers are
disabled by default in C++ unless -Wsign-conversion is explicitly enabled.
https://godbolt.org/g/6J4rtS
>From gcc-bugs-return-605240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 16:59:39 2018
Return-Path: <gcc-bugs-return-605240-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44361 invoked by alias); 21 May 2018 16:59: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 43615 invoked by uid 48); 21 May 2018 16:59:32 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 16:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
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-85858-4-V58x9lhS8K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02135.txt.bz2
Content-length: 234
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Mike Sharov from comment #0)
> When the pointer is const, it can not point to owned memory
Why not?
>From gcc-bugs-return-605241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 17:03:29 2018
Return-Path: <gcc-bugs-return-605241-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54501 invoked by alias); 21 May 2018 17: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 54353 invoked by uid 48); 21 May 2018 17:03:24 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85856] -Weffc++ can't see implicitly deleted constructor
Date: Mon, 21 May 2018 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: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: 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-85856-4-FY44RHL42V@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85856-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85856-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02136.txt.bz2
Content-length: 663
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85856
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> ---
There are loads of problems with -Weffc++, all related to the fact they are
outdated rules based on the first edition of a book based on C++98.
This seems like a dup of PR 22406
*** This bug has been marked as a duplicate of bug 22406 ***
>From gcc-bugs-return-605243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 17:03:32 2018
Return-Path: <gcc-bugs-return-605243-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54921 invoked by alias); 21 May 2018 17:03: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 54470 invoked by uid 48); 21 May 2018 17:03:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81930] [meta-bug] Issues with -Weffc++
Date: Mon, 21 May 2018 17:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-81930-4-0OSj2JlUlc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02138.txt.bz2
Content-length: 479
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81930
Bug 81930 depends on bug 85856, which changed state.
Bug 85856 Summary: -Weffc++ can't see implicitly deleted constructor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85856
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
>From gcc-bugs-return-605242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 17:03:32 2018
Return-Path: <gcc-bugs-return-605242-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54870 invoked by alias); 21 May 2018 17:03: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 54442 invoked by uid 48); 21 May 2018 17:03:27 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/22406] -Weffc++ warns about missing op= and copy ctor, even when base classes have already disabled these
Date: Mon, 21 May 2018 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: 4.0.1
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: P2
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-22406-4-TB9gQGEe3U@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-22406-4@http.gcc.gnu.org/bugzilla/>
References: <bug-22406-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02137.txt.bz2
Content-length: 505
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=22406
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |msharov at users dot sourceforge.n
| |et
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
*** Bug 85856 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-605244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 17:57:26 2018
Return-Path: <gcc-bugs-return-605244-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5697 invoked by alias); 21 May 2018 17:57:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5640 invoked by uid 48); 21 May 2018 17:57:22 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85855] [7 Regression] (Maybe) uninitialized descriptor fields of an allocatable array component of a function result
Date: Mon, 21 May 2018 17:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords: 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 cf_reconfirmed_on everconfirmed
Message-ID: <bug-85855-4-sPle5FxFdW@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02139.txt.bz2
Content-length: 587
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-21
Ever confirmed|0 |1
--- Comment #1 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
I am pretty sure that it is a duplicate, but I don't have the energy to hunt it
down right now!-(
>From gcc-bugs-return-605245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 18:05:06 2018
Return-Path: <gcc-bugs-return-605245-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40973 invoked by alias); 21 May 2018 18:05: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 40032 invoked by uid 48); 21 May 2018 18:04:59 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] g++ -Wconversion misses int to size_t
Date: Mon, 21 May 2018 18:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85861-4-ZKSHTeYQzf@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02140.txt.bz2
Content-length: 298
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
--- Comment #2 from Jonny Grant <jg at jguk dot org> ---
Thank you for your replies.
I tested on 64bit ubuntu. But yes with -Wsign-conversion I now see the
warnings/errors.
Could it be enabled by default? to match C behaviour visible in GCC.
>From gcc-bugs-return-605246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 18:48:57 2018
Return-Path: <gcc-bugs-return-605246-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11465 invoked by alias); 21 May 2018 18:48:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 11343 invoked by uid 48); 21 May 2018 18:48:49 -0000
From: "matthew.weber at rockwellcollins dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85862] New: infinite loop in find_base_term()
Date: Mon, 21 May 2018 18:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: rtl-optimization
X-Bugzilla-Version: 6.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: matthew.weber at rockwellcollins 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-85862-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02141.txt.bz2
Content-length: 2982
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85862
Bug ID: 85862
Summary: infinite loop in find_base_term()
Product: gcc
Version: 6.4.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: matthew.weber at rockwellcollins dot com
Target Milestone: ---
Posted a comment on this
(https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85180#c20) bug as the patch
proposed their resolved this issue as well.
libnss 3.35 fails to build on the microblaze arch (uclibc) with any of the 6.x
series and this patch resolves that
(https://github.com/gcc-mirror/gcc/commit/df03ebc3574a0d7893127e3b9754a01abf2d8b70).
microblazeel-buildroot-linux-uclibc-gcc -o
Linux2.6_microblazeel_microblazeel-buildroot-linux-uclibc-gcc.br_real_glibc_PTH_OPT.OBJ/sslgrp.o
-c -O2 -fPIC -pipe -ffunction-sections -fdata-sections -DHAVE_STRERROR
-DLINUX -Dlinux -Wall -Werror -DXP_UNIX -UDEBUG -DNDEBUG -D_REENTRANT
-DNSS_NO_INIT_SUPPORT -DUSE_UTIL_DIRECTLY -DNO_NSPR_10_SUPPORT
-DSSL_DISABLE_DEPRECATED_CIPHER_SUITE_NAMES -Isysroot/usr/include/nspr
-Ilibnss-3.35/dist/include -I../../../dist/public/nss
-I../../../dist/private/nss sslgrp.c
(Buildroot failure link:
http://autobuild.buildroot.net/results/158e8ebb39713e1b436a5cc1a1916f46c30694df)
However the libnss build works fine with the 7.x branch and master. I've been
bisecting all 3 branches for a few days and figured I should just try that
patch before debugging the 6.x branch further. I even went back and tried to
find common ancestors between the 6.x and 7.x and couldn't get a point where
the good/bad builds matched up. Guessing backports on 6.x from master
introduced the libnss bug variant, as the gcc/cse* and gcc/alias.x files had a
lot of updates from 5.x to 7.x.
Here's the stack trace on cc1 when its hung building a libnss sslgrp.c
file.......
( A lot more find_base_terms() before this one)
#71 0x00000000005ae67d in find_base_term(rtx_def*) ()
#72 0x00000000005ae532 in find_base_term(rtx_def*) ()
#73 0x00000000005ae67d in find_base_term(rtx_def*) ()
#74 0x00000000005ae532 in find_base_term(rtx_def*) ()
#75 0x00000000005ae67d in find_base_term(rtx_def*) ()
#76 0x00000000005ae568 in find_base_term(rtx_def*) ()
#77 0x00000000005b137d in write_dependence_p(rtx_def const*, rtx_def const*,
machine_mode, rtx_def*, bool, bool, bool) ()
#78 0x00000000005b1585 in canon_anti_dependence(rtx_def const*, bool, rtx_def
const*, machine_mode, rtx_def*) ()
#79 0x000000000061c5e3 in cselib_invalidate_mem(rtx_def*) ()
#80 0x000000000061d32d in cselib_record_sets(rtx_insn*) ()
#81 0x000000000061e5c8 in cselib_process_insn(rtx_insn*) ()
#82 0x00000000008774b8 in reload_cse_regs_1() ()
#83 0x00000000008777dc in (anonymous
namespace)::pass_postreload_cse::execute(function*) ()
#84 0x000000000086714d in execute_one_pass(opt_pass*) ()
>From gcc-bugs-return-605247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:01:12 2018
Return-Path: <gcc-bugs-return-605247-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63306 invoked by alias); 21 May 2018 19:01: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 62576 invoked by uid 48); 21 May 2018 19:01:02 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85863] New: [9 Regression] ICE in compiling spec2006 fortran test case solib.fppized.f starting with r260283
Date: Mon, 21 May 2018 19:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02142.txt.bz2
Content-length: 2924
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85863
Bug ID: 85863
Summary: [9 Regression] ICE in compiling spec2006 fortran test
case solib.fppized.f starting with r260283
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
I think the test case (part of 416.gamess) is generated by the spec2006 test
run as it appears in the build directory. Unfortunately it is a large test
case and I don't know fortran well enough to extract a smaller example of
failing code.
I see this with both powerpc64 BE and LE.
seurer@genoa:~/gcc/cpu2006$ /home/seurer/gcc/install/gcc-test2/bin/gfortran -c
-o solib.fppized.o -m64 -O3 -mcpu=power8 -ffast-math -funroll-loops
-fpeel-loops -fvect-cost-model -mpopcntd -mrecip=rsqrt -funconstrained-commons
-std=legacy
./benchspec/CPU2006/416.gamess/build/build_base_ppc64.0000/solib.fppized.f
./benchspec/CPU2006/416.gamess/build/build_base_ppc64.0000/solib.fppized.f:1300:72:
CALL GETSTSYM(X(LSTSYM),X(JSODA),IROOTS)
1
Warning: Type mismatch in argument 'istsym' at (1); passed REAL(8) to
INTEGER(4) [-Wargument-mismatch]
./benchspec/CPU2006/416.gamess/build/build_base_ppc64.0000/solib.fppized.f:1301:72:
CALL ASSORCI(X(LSTSYM),X(LNCIOR),X(LIRCIOR),IROOTS)
1
Warning: Type mismatch in argument 'istsym' at (1); passed REAL(8) to
INTEGER(4) [-Wargument-mismatch]
./benchspec/CPU2006/416.gamess/build/build_base_ppc64.0000/solib.fppized.f:1303:72:
CALL INTSYM(MULST,IROOTS,X(LSTSYM),IRRL,GSYLYES)
1
Warning: Type mismatch in argument 'istsym' at (1); passed REAL(8) to
INTEGER(4) [-Wargument-mismatch]
./benchspec/CPU2006/416.gamess/build/build_base_ppc64.0000/solib.fppized.f:1488:0:
SUBROUTINE SOBOOK(IW,ICI1,ICI2,IROOTS,SOL1MUL,SOL2MUL,STMMUL,
Error: invalid vector comparison resulting type
vector(2) <unnamed type>
vect__ifc__995.2248_892 = VEC_COND_EXPR <vect_cst__896 == vect_cst__895,
vect_cst__893, vect__ifc__1001.2247_929>;
during GIMPLE pass: vect
./benchspec/CPU2006/416.gamess/build/build_base_ppc64.0000/solib.fppized.f:1488:0:
internal compiler error: verify_gimple failed
0x10ae2d37 verify_gimple_in_cfg(function*, bool)
/home/seurer/gcc/gcc-test2/gcc/tree-cfg.c:5361
0x1094d5c3 execute_function_todo
/home/seurer/gcc/gcc-test2/gcc/passes.c:1994
0x1094edab do_per_function
/home/seurer/gcc/gcc-test2/gcc/passes.c:1659
0x1094efbb execute_todo
/home/seurer/gcc/gcc-test2/gcc/passes.c:2048
>From gcc-bugs-return-605248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:20:26 2018
Return-Path: <gcc-bugs-return-605248-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97799 invoked by alias); 21 May 2018 19: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 94487 invoked by uid 48); 21 May 2018 19:20:20 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] g++ -Wconversion misses int to size_t
Date: Mon, 21 May 2018 19:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status bug_severity
Message-ID: <bug-85861-4-S4bz9juqcK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02143.txt.bz2
Content-length: 723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|WAITING |NEW
Severity|normal |enhancement
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonny Grant from comment #2)
> Could it be enabled by default? to match C behaviour visible in GCC.
Confirming as a request for that. I have no idea what the history behind the
difference is (but it's intentional and documented).
>From gcc-bugs-return-605249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:26:32 2018
Return-Path: <gcc-bugs-return-605249-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 50399 invoked by alias); 21 May 2018 19:26: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 50295 invoked by uid 55); 21 May 2018 19:26:25 -0000
From: "paolo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84588] [8/9 Regression] internal compiler error: Segmentation fault (contains_struct_check())
Date: Mon, 21 May 2018 19:26:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84588-4-7hxp8djZXM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84588-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84588-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02144.txt.bz2
Content-length: 1713
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84588
--- Comment #13 from paolo at gcc dot gnu.org <paolo at gcc dot gnu.org> ---
Author: paolo
Date: Mon May 21 19:25:50 2018
New Revision: 260482
URL: https://gcc.gnu.org/viewcvs?rev=260482&root=gcc&view=rev
Log:
/cp
2018-05-21 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/84588
* parser.c (cp_parser_maybe_commit_to_declaration,
cp_parser_check_condition_declarator): New.
(cp_parser_simple_declaration): Use the first above.
(cp_parser_condition): Use both the above; enforce
[stmt.stmt]/2 about the declarator not specifying
a function or an array; improve error-recovery.
/testsuite
2018-05-21 Paolo Carlini <paolo.carlini@oracle.com>
PR c++/84588
* g++.dg/cpp0x/cond1.C: New.
* g++.dg/cpp1y/pr84588-1.C: Likewise.
* g++.dg/cpp1y/pr84588-2.C: Likewise.
* g++.dg/cpp1y/pr84588-3.C: Likewise.
* g++.dg/parse/cond6.C: Likewise.
* g++.dg/parse/cond7.C: Likewise.
* g++.dg/parse/cond8.C: Likewise.
* g++.dg/cpp1z/decomp16.C: Update.
* g++.old-deja/g++.jason/cond.C: Likewise.
Added:
trunk/gcc/testsuite/g++.dg/cpp0x/cond1.C
trunk/gcc/testsuite/g++.dg/cpp1y/pr84588-1.C
trunk/gcc/testsuite/g++.dg/cpp1y/pr84588-2.C
trunk/gcc/testsuite/g++.dg/cpp1y/pr84588-3.C
trunk/gcc/testsuite/g++.dg/parse/cond6.C
trunk/gcc/testsuite/g++.dg/parse/cond7.C
trunk/gcc/testsuite/g++.dg/parse/cond8.C
Modified:
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/parser.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/g++.dg/cpp1z/decomp16.C
trunk/gcc/testsuite/g++.old-deja/g++.jason/cond.C
>From gcc-bugs-return-605250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:28:28 2018
Return-Path: <gcc-bugs-return-605250-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52946 invoked by alias); 21 May 2018 19:28:28 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52910 invoked by uid 48); 21 May 2018 19:28:22 -0000
From: "jg at jguk dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] g++ -Wconversion misses int to size_t
Date: Mon, 21 May 2018 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: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jg at jguk dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85861-4-8WKAaIpV0z@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02145.txt.bz2
Content-length: 1592
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
--- Comment #4 from Jonny Grant <jg at jguk dot org> ---
$ gcc -v
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/5/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu
5.4.0-6ubuntu1~16.04.9' --with-bugurl=file:///usr/share/doc/gcc-5/README.Bugs
--enable-languages=c,ada,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr
--program-suffix=-5 --enable-shared --enable-linker-build-id
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix
--libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu
--enable-libstdcxx-debug --enable-libstdcxx-time=yes
--with-default-libstdcxx-abi=new --enable-gnu-unique-object
--disable-vtable-verify --enable-libmpx --enable-plugin --with-system-zlib
--disable-browser-plugin --enable-java-awt=gtk --enable-gtk-cairo
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-5-amd64/jre --enable-java-home
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-5-amd64
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-5-amd64
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --enable-multilib
--with-tune=generic --enable-checking=release --build=x86_64-linux-gnu
--host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
>From gcc-bugs-return-605251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:29:18 2018
Return-Path: <gcc-bugs-return-605251-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54095 invoked by alias); 21 May 2018 19: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 54035 invoked by uid 48); 21 May 2018 19:29:12 -0000
From: "msharov at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 19: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: normal
X-Bugzilla-Who: msharov at users dot sourceforge.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-85858-4-Az9o2x8AOm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02146.txt.bz2
Content-length: 764
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #2 from Mike Sharov <msharov at users dot sourceforge.net> ---
(In reply to Jonathan Wakely from comment #1)
> (In reply to Mike Sharov from comment #0)
> > When the pointer is const, it can not point to owned memory
> Why not?
Because a const pointer can not be freed. By "owned memory" I mean memory that
was explicitly allocated by the object, which I assume was the situation that
Effective C++ rule was referring to, or memory the ownership of which was
passed to the object. In both cases the object has to keep a non-const pointer
in order to be able to free it or to pass on the ability to free it to some
other object. I can't think of any case for an owned const pointer; can you?
>From gcc-bugs-return-605252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:29:35 2018
Return-Path: <gcc-bugs-return-605252-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 54854 invoked by alias); 21 May 2018 19:29:34 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 54773 invoked by uid 48); 21 May 2018 19:29:27 -0000
From: "paolo.carlini at oracle dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84588] [8 Regression] internal compiler error: Segmentation fault (contains_struct_check())
Date: Mon, 21 May 2018 19:29:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords: error-recovery, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paolo.carlini at oracle dot com
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: paolo.carlini at oracle dot com
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-84588-4-fAtVj6TGJY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84588-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84588-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02147.txt.bz2
Content-length: 807
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84588
Paolo Carlini <paolo.carlini at oracle dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9 Regression] internal |[8 Regression] internal
|compiler error: |compiler error:
|Segmentation fault |Segmentation fault
|(contains_struct_check()) |(contains_struct_check())
--- Comment #14 from Paolo Carlini <paolo.carlini at oracle dot com> ---
Should be really fixed in trunk. Note, what I applied doesn't have much to do
with the idea posted in Comment 12 and goes well beyond handling correctly the
testcase originally provided by bug submitter.
>From gcc-bugs-return-605254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:40:47 2018
Return-Path: <gcc-bugs-return-605254-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24513 invoked by alias); 21 May 2018 19:40: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 24407 invoked by uid 48); 21 May 2018 19:40:42 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 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: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85858-4-o6xMCUiQZe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02149.txt.bz2
Content-length: 406
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Last reconfirmed| |2018-05-21
Ever confirmed|0 |1
>From gcc-bugs-return-605253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:40:23 2018
Return-Path: <gcc-bugs-return-605253-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23428 invoked by alias); 21 May 2018 19: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 23296 invoked by uid 48); 21 May 2018 19:40:15 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 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: 8.1.0
X-Bugzilla-Keywords: diagnostic
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-85858-4-ySQ83VpKyr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02148.txt.bz2
Content-length: 1103
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Mike Sharov from comment #2)
> (In reply to Jonathan Wakely from comment #1)
> > (In reply to Mike Sharov from comment #0)
> > > When the pointer is const, it can not point to owned memory
> > Why not?
>
> Because a const pointer can not be freed.
That's what I thought you meant, and it's wrong.
> By "owned memory" I mean memory
> that was explicitly allocated by the object, which I assume was the
> situation that Effective C++ rule was referring to, or memory the ownership
> of which was passed to the object. In both cases the object has to keep a
> non-const pointer in order to be able to free it or to pass on the ability
> to free it to some other object.
Nothing stops you deallocating a const pointer.
struct X {
const int* const p;
X() : p(new int[10]) { }
~X() { delete[] p; }
};
This type should have a user-defined copy constructor (it doesn't need a
user-defined assignment operator though, because it's implicitly defined as
deleted).
>From gcc-bugs-return-605255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:44:41 2018
Return-Path: <gcc-bugs-return-605255-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 105745 invoked by alias); 21 May 2018 19:44: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 105598 invoked by uid 48); 21 May 2018 19:44:36 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85852] [9 Regression] ICE: Segmentation fault (in contains_struct_check)
Date: Mon, 21 May 2018 19: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc assigned_to
Message-ID: <bug-85852-4-unUlc2Cjdk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85852-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85852-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02150.txt.bz2
Content-length: 566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85852
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |rsandifo at gcc dot gnu.org
Assignee|unassigned at gcc dot gnu.org |rsandifo at gcc dot gnu.org
--- Comment #3 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Mine.
>From gcc-bugs-return-605256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:53:49 2018
Return-Path: <gcc-bugs-return-605256-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95904 invoked by alias); 21 May 2018 19:53:48 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 93451 invoked by uid 48); 21 May 2018 19:53:43 -0000
From: "dummyddd at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85864] New: template argument string literal operator with default argument doesnt work in templates
Date: Mon, 21 May 2018 19:53:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dummyddd 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-85864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02151.txt.bz2
Content-length: 1472
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85864
Bug ID: 85864
Summary: template argument string literal operator with default
argument doesnt work in templates
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: dummyddd at gmail dot com
Target Milestone: ---
The following code compiles with GCC 7.3.0 and earlier, but errors with GCC
8.1.0 and trunk.
template<class T, T... S> struct String_template {};
template<class C, C... S>
constexpr String_template<C, S...> operator""_template() {
return String_template<C, S...> {};
}
template<class prefix = decltype("0x"_template), class T>
int hex(T v) { return 1; }
template<int v>
void tt2() {
auto h2 = hex<decltype("0x"_template)>(1);
auto h = hex(2);
}
int main() {
auto h = hex(2);
return h;
}
<source>: In function 'void tt2()':
<source>:14:19: error: no matching function for call to 'hex(int)'
auto h = hex(2);
^
<source>:9:5: note: candidate: 'template<class prefix, class T> int hex(T)'
int hex(T v) { return 1; }
^~~
<source>:9:5: note: template argument deduction/substitution failed:
The error is only triggered by hex(2).
The error may be related to https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85731
>From gcc-bugs-return-605257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 19:55:50 2018
Return-Path: <gcc-bugs-return-605257-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 127553 invoked by alias); 21 May 2018 19:55: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 127163 invoked by uid 48); 21 May 2018 19:55:43 -0000
From: "msharov at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 19:55:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msharov at users dot sourceforge.net
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-85858-4-RRunBj1Hvi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02152.txt.bz2
Content-length: 661
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #4 from Mike Sharov <msharov at users dot sourceforge.net> ---
(In reply to Jonathan Wakely from comment #3)
> Nothing stops you deallocating a const pointer.
According to http://en.cppreference.com/w/cpp/memory/new/operator_delete
The delete operator takes a void* and attempting to delete a const pointer
would require a const_cast. This is logical, since freeing a memory block is a
modification operation that changes the block's contents by marking it invalid.
To my surprise, I found that g++ actually does currently accept delete of a
const pointer. I believe that should be a bug.
>From gcc-bugs-return-605258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:04:45 2018
Return-Path: <gcc-bugs-return-605258-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14938 invoked by alias); 21 May 2018 20: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 14870 invoked by uid 48); 21 May 2018 20:04:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 20: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: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85858-4-hc7CtAgZTl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02153.txt.bz2
Content-length: 513
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Nope, see the C++ standard:
[ Note: A pointer to a const type can be the operand of a delete-expression;
it is not necessary to cast away the constness (8.5.1.11) of the pointer
expression before it is used as the operand of the delete-expression. — end
note ]
The deallocation function 'operator delete(void*)' is not the same as a
delete-expression such as delete[] p.
>From gcc-bugs-return-605260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:31:43 2018
Return-Path: <gcc-bugs-return-605260-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115747 invoked by alias); 21 May 2018 20: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 115675 invoked by uid 48); 21 May 2018 20:31:38 -0000
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84923] [8 regression] gcc.dg/attr-weakref-1.c failed on aarch64
Date: Mon, 21 May 2018 20:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.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: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc short_desc
Message-ID: <bug-84923-4-Pcl7pt241l@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02155.txt.bz2
Content-length: 597
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84923
Jeffrey A. Law <law at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |law at redhat dot com
Summary|[8/9 regression] |[8 regression]
|gcc.dg/attr-weakref-1.c |gcc.dg/attr-weakref-1.c
|failed on aarch64 |failed on aarch64
--- Comment #9 from Jeffrey A. Law <law at redhat dot com> ---
Fixed on trunk so far.
>From gcc-bugs-return-605259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:31:16 2018
Return-Path: <gcc-bugs-return-605259-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 113556 invoked by alias); 21 May 2018 20:31:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 113181 invoked by uid 55); 21 May 2018 20:30:47 -0000
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/84923] [8/9 regression] gcc.dg/attr-weakref-1.c failed on aarch64
Date: Mon, 21 May 2018 20:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: law at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-84923-4-cxkHETCHWl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84923-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84923-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02154.txt.bz2
Content-length: 390
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84923
--- Comment #8 from Jeffrey A. Law <law at gcc dot gnu.org> ---
Author: law
Date: Mon May 21 20:30:00 2018
New Revision: 260485
URL: https://gcc.gnu.org/viewcvs?rev=260485&root=gcc&view=rev
Log:
PR gcc/84923
* varasm.c (weak_finish): Clean up weak_decls.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/varasm.c
>From gcc-bugs-return-605261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:39:06 2018
Return-Path: <gcc-bugs-return-605261-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 126437 invoked by alias); 21 May 2018 20:39:05 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 126351 invoked by uid 48); 21 May 2018 20:39:00 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85865] New: [9 regression] Many libgomp fortran test cases fails starting with r260433
Date: Mon, 21 May 2018 20:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02156.txt.bz2
Content-length: 16002
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85865
Bug ID: 85865
Summary: [9 regression] Many libgomp fortran test cases fails
starting with r260433
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: testsuite
Assignee: unassigned at gcc dot gnu.org
Reporter: seurer at gcc dot gnu.org
Target Milestone: ---
There are a whole bunch of fortran tests that fail starting with r260433. This
is (I believe) the whole list:
FAIL: libgomp.fortran/collapse2.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/collapse2.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/collapse2.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/collapse2.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/collapse2.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/collapse2.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/omp_atomic2.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/omp_atomic2.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/omp_atomic2.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/omp_atomic2.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/omp_atomic2.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/omp_atomic2.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/omp_parse1.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/omp_parse1.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/omp_parse1.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/omp_parse1.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/omp_parse1.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/omp_parse1.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/omp_parse3.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/omp_parse3.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/omp_parse3.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/omp_parse3.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/omp_parse3.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/omp_parse3.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/task2.f90 -O (test for excess errors)
FAIL: libgomp.fortran/vla1.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla1.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla1.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla1.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla1.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla1.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/vla2.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla2.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla2.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla2.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla2.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla2.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/vla3.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla3.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla3.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla3.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla3.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla3.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/vla4.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla4.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla4.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla4.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla4.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla4.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/vla5.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla5.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla5.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla5.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla5.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla5.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/vla6.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla6.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla6.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla6.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla6.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla6.f90 -Os (test for excess errors)
FAIL: libgomp.fortran/vla8.f90 -O0 (test for excess errors)
FAIL: libgomp.fortran/vla8.f90 -O1 (test for excess errors)
FAIL: libgomp.fortran/vla8.f90 -O2 (test for excess errors)
FAIL: libgomp.fortran/vla8.f90 -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions (test for excess errors)
FAIL: libgomp.fortran/vla8.f90 -O3 -g (test for excess errors)
FAIL: libgomp.fortran/vla8.f90 -Os (test for excess errors)
FAIL: libgomp.oacc-fortran/collapse-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O0 (test for excess errors)
FAIL: libgomp.oacc-fortran/collapse-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O1 (test for excess errors)
FAIL: libgomp.oacc-fortran/collapse-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O2 (test for excess errors)
FAIL: libgomp.oacc-fortran/collapse-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops
-ftracer -finline-functions (test for excess errors)
FAIL: libgomp.oacc-fortran/collapse-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O3 -g (test for excess errors)
FAIL: libgomp.oacc-fortran/collapse-2.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -Os (test for excess errors)
FAIL: libgomp.oacc-fortran/nested-function-1.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O0 (test for excess errors)
FAIL: libgomp.oacc-fortran/nested-function-1.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O1 (test for excess errors)
FAIL: libgomp.oacc-fortran/nested-function-1.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O2 (test for excess errors)
FAIL: libgomp.oacc-fortran/nested-function-1.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O3 -fomit-frame-pointer -funroll-loops -fpeel-loops
-ftracer -finline-functions (test for excess errors)
FAIL: libgomp.oacc-fortran/nested-function-1.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -O3 -g (test for excess errors)
FAIL: libgomp.oacc-fortran/nested-function-1.f90 -DACC_DEVICE_TYPE_host=1
-DACC_MEM_SHARED=1 -Os (test for excess errors)
Looking at one in details:
spawn -ignore SIGHUP /home/seurer/gcc/build/gcc-trunk/gcc/xgcc
-B/home/seurer/gcc/build/gcc-trunk/gcc/
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90
-B/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/
-B/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/.libs
-I/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp
-I/home/seurer/gcc/gcc-trunk/libgomp/testsuite/../../include
-I/home/seurer/gcc/gcc-trunk/libgomp/testsuite/.. -fmessage-length=0
-fno-diagnostics-show-caret -Wno-hsa -fdiagnostics-color=never -fopenmp
-B/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/../libquadmath/.libs/
-O0
-B/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/../libgfortran/.libs
-fintrinsic-modules-path=/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp
-L/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/.libs
-L/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/../libquadmath/.libs/
-L/home/seurer/gcc/build/gcc-trunk/powerpc64-unknown-linux-gnu/./libgomp/../libgfortran/.libs
-lgfortran -foffload=-lgfortran -lm -o ./vla8.exe
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:77:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 103 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:78:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 103 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:91:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 104 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:92:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 104 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:97:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 105 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:152:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 113 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:153:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 113 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:166:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 114 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:167:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 114 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:172:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 115 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:215:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 123 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:216:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 123 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:229:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 124 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:230:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 124 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:235:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 125 at (1)
output is:
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:77:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 103 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:78:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 103 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:91:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 104 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:92:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 104 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:97:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 105 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:152:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 113 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:153:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 113 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:166:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 114 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:167:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 114 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:172:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 115 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:215:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 123 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:216:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 123 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:229:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 124 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:230:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 124 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:235:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 125 at (1)
FAIL: libgomp.fortran/vla8.f90 -O0 (test for excess errors)
Excess errors:
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:77:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 103 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:78:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 103 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:91:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 104 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:92:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 104 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:97:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 105 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:152:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 113 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:153:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 113 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:166:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 114 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:167:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 114 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:172:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 115 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:215:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 123 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:216:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 123 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:229:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 124 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:230:17:
Warning: Fortran 2018 deleted feature: Shared DO termination label 124 at (1)
/home/seurer/gcc/gcc-trunk/libgomp/testsuite/libgomp.fortran/vla8.f90:235:22:
Warning: Fortran 2018 deleted feature: Shared DO termination label 125 at (1)
>From gcc-bugs-return-605262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:43:36 2018
Return-Path: <gcc-bugs-return-605262-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 10515 invoked by alias); 21 May 2018 20:43: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 10473 invoked by uid 48); 21 May 2018 20:43:32 -0000
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85865] [9 regression] Many libgomp fortran test cases fails starting with r260433
Date: Mon, 21 May 2018 20:43: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: seurer at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85865-4-ACFF5icfS0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02157.txt.bz2
Content-length: 442
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85865
--- Comment #1 from seurer at gcc dot gnu.org ---
r260433 | janus | 2018-05-21 01:45:55 -0500 (Mon, 21 May 2018) | 42 lines
2018-05-21 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
* gfortran.dg/g77/19990826-3.f: Add option "-std=legacy".
* gfortran.dg/g77/20020307-1.f: Ditto.
...
Probably this just needs to be added to all the failing test cases, too.
>From gcc-bugs-return-605263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:46:52 2018
Return-Path: <gcc-bugs-return-605263-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17630 invoked by alias); 21 May 2018 20:46:51 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16700 invoked by uid 48); 21 May 2018 20:46:43 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85865] [9 regression] Many libgomp fortran test cases fails starting with r260433
Date: Mon, 21 May 2018 20:46: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: 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-85865-4-HHZSf0ECx6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02158.txt.bz2
Content-length: 905
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85865
kargl at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |kargl at gcc dot gnu.org
--- Comment #2 from kargl at gcc dot gnu.org ---
(In reply to seurer from comment #1)
> r260433 | janus | 2018-05-21 01:45:55 -0500 (Mon, 21 May 2018) | 42 lines
>
> 2018-05-21 Janus Weil <janus@gcc.gnu.org>
>
> PR fortran/85841
> * gfortran.dg/g77/19990826-3.f: Add option "-std=legacy".
> * gfortran.dg/g77/20020307-1.f: Ditto.
> ...
>
> Probably this just needs to be added to all the failing test cases, too.
Yes, Janus and I are aware of the failures. Unfortunately,
make check-fortran
does not run over the Fortran code in libgomp.fortran, so the
above list of failures were missed.
>From gcc-bugs-return-605264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:47:46 2018
Return-Path: <gcc-bugs-return-605264-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 20479 invoked by alias); 21 May 2018 20:47: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 19712 invoked by uid 48); 21 May 2018 20:47:39 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85865] [9 regression] Many libgomp fortran test cases fails starting with r260433
Date: Mon, 21 May 2018 20:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: testsuite
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: janus 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-85865-4-BhUcC7waBx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02159.txt.bz2
Content-length: 788
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85865
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-21
Assignee|unassigned at gcc dot gnu.org |janus at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #3 from janus at gcc dot gnu.org ---
(In reply to seurer from comment #1)
> PR fortran/85841
> * gfortran.dg/g77/19990826-3.f: Add option "-std=legacy".
> * gfortran.dg/g77/20020307-1.f: Ditto.
> ...
>
> Probably this just needs to be added to all the failing test cases, too.
Yes, I'm on it.
>From gcc-bugs-return-605265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:49:47 2018
Return-Path: <gcc-bugs-return-605265-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29659 invoked by alias); 21 May 2018 20:49:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 24065 invoked by uid 55); 21 May 2018 20:49:35 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85865] [9 regression] Many libgomp fortran test cases fails starting with r260433
Date: Mon, 21 May 2018 20: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85865-4-mDsDXEEpN3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02160.txt.bz2
Content-length: 1994
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85865
--- Comment #4 from janus at gcc dot gnu.org ---
Author: janus
Date: Mon May 21 20:48:59 2018
New Revision: 260487
URL: https://gcc.gnu.org/viewcvs?rev=260487&root=gcc&view=rev
Log:
2018-05-21 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
PR testsuite/85865
* testsuite/libgomp.fortran/collapse2.f90: Add option "-std=legacy".
* testsuite/libgomp.fortran/omp_atomic2.f90: Ditto.
* testsuite/libgomp.fortran/omp_parse1.f90: Ditto.
* testsuite/libgomp.fortran/omp_parse3.f90: Ditto.
* testsuite/libgomp.fortran/task2.f90: Ditto.
* testsuite/libgomp.fortran/vla1.f90: Ditto.
* testsuite/libgomp.fortran/vla2.f90: Ditto.
* testsuite/libgomp.fortran/vla3.f90: Ditto.
* testsuite/libgomp.fortran/vla4.f90: Ditto.
* testsuite/libgomp.fortran/vla5.f90: Ditto.
* testsuite/libgomp.fortran/vla6.f90: Ditto.
* testsuite/libgomp.fortran/vla8.f90: Ditto.
* testsuite/libgomp.oacc-fortran/collapse-2.f90: Ditto.
* testsuite/libgomp.oacc-fortran/nested-function-1.f90: Ditto.
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/testsuite/libgomp.fortran/collapse2.f90
trunk/libgomp/testsuite/libgomp.fortran/omp_atomic2.f90
trunk/libgomp/testsuite/libgomp.fortran/omp_parse1.f90
trunk/libgomp/testsuite/libgomp.fortran/omp_parse3.f90
trunk/libgomp/testsuite/libgomp.fortran/task2.f90
trunk/libgomp/testsuite/libgomp.fortran/vla1.f90
trunk/libgomp/testsuite/libgomp.fortran/vla2.f90
trunk/libgomp/testsuite/libgomp.fortran/vla3.f90
trunk/libgomp/testsuite/libgomp.fortran/vla4.f90
trunk/libgomp/testsuite/libgomp.fortran/vla5.f90
trunk/libgomp/testsuite/libgomp.fortran/vla6.f90
trunk/libgomp/testsuite/libgomp.fortran/vla8.f90
trunk/libgomp/testsuite/libgomp.oacc-fortran/collapse-2.f90
trunk/libgomp/testsuite/libgomp.oacc-fortran/nested-function-1.f90
>From gcc-bugs-return-605266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:49:47 2018
Return-Path: <gcc-bugs-return-605266-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 29848 invoked by alias); 21 May 2018 20:49: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 25101 invoked by uid 55); 21 May 2018 20:49:39 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Mon, 21 May 2018 20: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: 8.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85841-4-jyalkCMOs8@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02161.txt.bz2
Content-length: 1994
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
--- Comment #5 from janus at gcc dot gnu.org ---
Author: janus
Date: Mon May 21 20:48:59 2018
New Revision: 260487
URL: https://gcc.gnu.org/viewcvs?rev=260487&root=gcc&view=rev
Log:
2018-05-21 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
PR testsuite/85865
* testsuite/libgomp.fortran/collapse2.f90: Add option "-std=legacy".
* testsuite/libgomp.fortran/omp_atomic2.f90: Ditto.
* testsuite/libgomp.fortran/omp_parse1.f90: Ditto.
* testsuite/libgomp.fortran/omp_parse3.f90: Ditto.
* testsuite/libgomp.fortran/task2.f90: Ditto.
* testsuite/libgomp.fortran/vla1.f90: Ditto.
* testsuite/libgomp.fortran/vla2.f90: Ditto.
* testsuite/libgomp.fortran/vla3.f90: Ditto.
* testsuite/libgomp.fortran/vla4.f90: Ditto.
* testsuite/libgomp.fortran/vla5.f90: Ditto.
* testsuite/libgomp.fortran/vla6.f90: Ditto.
* testsuite/libgomp.fortran/vla8.f90: Ditto.
* testsuite/libgomp.oacc-fortran/collapse-2.f90: Ditto.
* testsuite/libgomp.oacc-fortran/nested-function-1.f90: Ditto.
Modified:
trunk/libgomp/ChangeLog
trunk/libgomp/testsuite/libgomp.fortran/collapse2.f90
trunk/libgomp/testsuite/libgomp.fortran/omp_atomic2.f90
trunk/libgomp/testsuite/libgomp.fortran/omp_parse1.f90
trunk/libgomp/testsuite/libgomp.fortran/omp_parse3.f90
trunk/libgomp/testsuite/libgomp.fortran/task2.f90
trunk/libgomp/testsuite/libgomp.fortran/vla1.f90
trunk/libgomp/testsuite/libgomp.fortran/vla2.f90
trunk/libgomp/testsuite/libgomp.fortran/vla3.f90
trunk/libgomp/testsuite/libgomp.fortran/vla4.f90
trunk/libgomp/testsuite/libgomp.fortran/vla5.f90
trunk/libgomp/testsuite/libgomp.fortran/vla6.f90
trunk/libgomp/testsuite/libgomp.fortran/vla8.f90
trunk/libgomp/testsuite/libgomp.oacc-fortran/collapse-2.f90
trunk/libgomp/testsuite/libgomp.oacc-fortran/nested-function-1.f90
>From gcc-bugs-return-605267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 20:50:14 2018
Return-Path: <gcc-bugs-return-605267-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33078 invoked by alias); 21 May 2018 20:50:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 33037 invoked by uid 48); 21 May 2018 20:50:09 -0000
From: "foreese at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85851] [8/9 Regression] ICE in gfc_conv_structure Segmentation fault at trans-expr.c:7810
Date: Mon, 21 May 2018 20:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: foreese at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: foreese at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on dependson assigned_to
Message-ID: <bug-85851-4-1OEUm5LyW6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85851-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85851-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02162.txt.bz2
Content-length: 1232
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85851
Fritz Reese <foreese at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Last reconfirmed|2018-05-20 00:00:00 |2018-5-21
Depends on| |82972
Assignee|unassigned at gcc dot gnu.org |foreese at gcc dot gnu.org
--- Comment #2 from Fritz Reese <foreese at gcc dot gnu.org> ---
Probable duplicate of pr82972 and pr83088. Sorry I have not tracked this issue
down yet. My solution for -finit-derived requires special consideration for the
iso-c-binding structures such as c_ptr since the structure intialization
expression currently generated is invalid for those structures. Something in
the middle-end changed with 8.x that has further invalidated my solution for
-finit-derived. I am [still] working on this and a few other issues with
-finit-derived.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82972
[Bug 82972] [8/9 Regression] ICE with -finit-derived in gfc_conv_structure, at
fortran/trans-expr.c:7733 (and others)
>From gcc-bugs-return-605268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 21:01:17 2018
Return-Path: <gcc-bugs-return-605268-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 111016 invoked by alias); 21 May 2018 21:01: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 108379 invoked by uid 48); 21 May 2018 21:01:12 -0000
From: "msharov at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 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: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msharov at users dot sourceforge.net
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-85858-4-RPiTjCvj4k@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02163.txt.bz2
Content-length: 487
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #6 from Mike Sharov <msharov at users dot sourceforge.net> ---
(In reply to Jonathan Wakely from comment #5)
> Nope, see the C++ standard:
>
> [ Note: A pointer to a const type can be the operand of a
> delete-expression;
Ok, I guess; you have to follow the standard, after all. But I would like to
see the rationale for this, because it sure looks like a violation of const
correctness. I certainly feel violated.
>From gcc-bugs-return-605269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 21:23:09 2018
Return-Path: <gcc-bugs-return-605269-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 40714 invoked by alias); 21 May 2018 21:23: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 40687 invoked by uid 48); 21 May 2018 21:23:04 -0000
From: "vladimir.fuka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85855] [7 Regression] (Maybe) uninitialized descriptor fields of an allocatable array component of a function result
Date: Mon, 21 May 2018 21: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: 7.3.1
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: vladimir.fuka 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-85855-4-qbzZHgz6Jl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85855-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85855-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02164.txt.bz2
Content-length: 400
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85855
--- Comment #2 from Vladimir Fuka <vladimir.fuka at gmail dot com> ---
Yes, that is quite possible, although I tried to search first, because I had
this problem without reporting for a long time, but may main compiler version
to use was an older one so I didn't car that much for just a warning and hoped
it will be gone when I move to 7.
>From gcc-bugs-return-605270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:03:17 2018
Return-Path: <gcc-bugs-return-605270-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103757 invoked by alias); 21 May 2018 22:03: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 103621 invoked by uid 55); 21 May 2018 22:03:11 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8/9 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Mon, 21 May 2018 22: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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85814-4-Ijt6k0p13a@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02165.txt.bz2
Content-length: 2570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
--- Comment #7 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Author: rsandifo
Date: Mon May 21 22:02:35 2018
New Revision: 260488
URL: https://gcc.gnu.org/viewcvs?rev=260488&root=gcc&view=rev
Log:
Fix tree-ssa-strlen handling of partial clobbers (PR85814)
In this PR we have:
c_5 = c_4(D) + 4;
c_12 = c_5 + 1;
*c_5 = 2;
a = 2; // A
c_21 = c_12 + 1;
*c_12 = 2;
a = 2; // B
c_28 = c_21 + 1;
*c_21 = 2;
a = 2;
c_7 = c_28 + 1;
*c_28 = 2;
where a is a global int. We decide that A can't clobber *c_5 == c_4[4]
because the latter implies that c_4 is an object of 5 bytes or more,
whereas a has exactly 4 bytes.
The assumption for B and *c_5 is the same, but when considering B and
*c_12, we only follow the definition of c_12 to c_5 + 1 (for good
reason) and so have *c_12 == c_5[1]. We then don't have the same
size guarantee and so assume that B could clobber *c_12. This leads
to a situation in which the strinfo for c_5 is still valid but the
next strinfo (c_12) isn't. We then segfaulted while trying to get
the strinfo for c_21 + 1 == c_5 + 3 because get_stridx_plus_constant
assumed that c_5's next strinfo (c_12) would be valid too.
And of course it should be valid really. It doesn't make sense for the
string based at c_5 to be valid but a substring of it to be invalid.
I don't think we can guarantee that such weird corner cases never
happen though, even if we tried to avoid this one.
One possibility would be to mark c_12 as valid on the basis that c_5
is valid, but I'm not sure the complication is worth it given that it
seems to trigger very rarely. A better optimisation would be to get
the unroller to clean up after itself a bit more...
Although this particular instance of the bug relies on r249880, I think
we could have similar problems in GCC 7. It would be much harder to
trigger though, especially since it relies on unfolded IR like the above.
2018-05-21 Richard Sandiford <richard.sandiford@linaro.org>
gcc/
PR tree-optimization/85814
* tree-ssa-strlen.c (get_stridx_plus_constant): Cope with
a null return from get_strinfo when unsharing the next
strinfo in the chain.
gcc/testsuite/
PR tree-optimization/85814
* gcc.dg/torture/pr85814.c: New test.
Added:
trunk/gcc/testsuite/gcc.dg/torture/pr85814.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-strlen.c
>From gcc-bugs-return-605271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:04:01 2018
Return-Path: <gcc-bugs-return-605271-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106218 invoked by alias); 21 May 2018 22:04:01 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 106103 invoked by uid 48); 21 May 2018 22:03:57 -0000
From: "rsandifo at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85814] [8 Regression] ICE Segmentation fault during GIMPLE pass: strlen -O3 and above
Date: Mon, 21 May 2018 22:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rsandifo at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rsandifo at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: short_desc
Message-ID: <bug-85814-4-BhJyszImUg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85814-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02166.txt.bz2
Content-length: 673
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85814
rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|[8/9 Regression] ICE |[8 Regression] ICE
|Segmentation fault during |Segmentation fault during
|GIMPLE pass: strlen -O3 and |GIMPLE pass: strlen -O3 and
|above |above
--- Comment #8 from rsandifo at gcc dot gnu.org <rsandifo at gcc dot gnu.org> ---
Fixed on trunk so far. Will apply to the branch tomorrow.
>From gcc-bugs-return-605272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:13:36 2018
Return-Path: <gcc-bugs-return-605272-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117807 invoked by alias); 21 May 2018 22:13: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 117770 invoked by uid 48); 21 May 2018 22:13:31 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85861] g++ -Wconversion misses int to size_t
Date: Mon, 21 May 2018 22:13:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85861-4-p1hFh2DFsR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85861-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02167.txt.bz2
Content-length: 694
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85861
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |egallager at gcc dot gnu.org
--- Comment #5 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Jonny Grant from comment #2)
> Thank you for your replies.
>
> I tested on 64bit ubuntu. But yes with -Wsign-conversion I now see the
> warnings/errors.
>
> Could it be enabled by default? to match C behaviour visible in GCC.
I think you mean by -Wconversion, not by default, right?
>From gcc-bugs-return-605273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:22:18 2018
Return-Path: <gcc-bugs-return-605273-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 123721 invoked by alias); 21 May 2018 22: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 123649 invoked by uid 55); 21 May 2018 22:22:13 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85657] Make __ibm128 a separate type, even if long double uses the IBM double-double format
Date: Mon, 21 May 2018 22: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: major
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85657-4-UQGPXyyqCE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02168.txt.bz2
Content-length: 2198
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85657
--- Comment #2 from Michael Meissner <meissner at gcc dot gnu.org> ---
Author: meissner
Date: Mon May 21 22:21:40 2018
New Revision: 260489
URL: https://gcc.gnu.org/viewcvs?rev=260489&root=gcc&view=rev
Log:
[gcc]
2018-05-21 Michael Meissner <meissner@linux.ibm.com>
PR target/85657
* config/rs6000/rs6000-c.c (rs6000_cpu_cpp_builtins): Do not
define __ibm128 as long double.
* config/rs6000/rs6000.c (rs6000_init_builtins): Always create
__ibm128 as a distinct type.
(init_float128_ieee): Fix up conversions between IFmode and IEEE
128-bit types to use the correct functions.
(rs6000_expand_float128_convert): Use explicit FLOAT_EXTEND to
convert between 128-bit floating point types that have different
modes but the same representation, instead of using gen_lowpart to
makean alias.
* config/rs6000/rs6000.md (IFKF): New iterator for IFmode and
KFmode.
(IFKF_reg): New attributes to give the register constraints for
IFmode and KFmode.
(extend<mode>tf2_internal): New insns to mark an explicit
conversion between 128-bit floating point types that have a
different mode but share the same representation.
[gcc/testsuite]
2018-05-21 Michael Meissner <meissner@linux.ibm.com>
PR target/85657
* gcc.target/powerpc/pr85657-1.c: New test for converting between
__float128, __ibm128, and long double.
* gcc.target/powerpc/pr85657-2.c: Likewise.
* gcc.target/powerpc/pr85657-3.c: Likewise.
* g++.dg/pr85667.C: New test to make sure __ibm128 is
implementated as a separate type internally, and is not just an
alias for long double.
Added:
trunk/gcc/testsuite/g++.dg/pr85657.C
trunk/gcc/testsuite/gcc.target/powerpc/pr85657-1.c
trunk/gcc/testsuite/gcc.target/powerpc/pr85657-2.c
trunk/gcc/testsuite/gcc.target/powerpc/pr85657-3.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/rs6000/rs6000-c.c
trunk/gcc/config/rs6000/rs6000.c
trunk/gcc/config/rs6000/rs6000.md
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-605274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:25:45 2018
Return-Path: <gcc-bugs-return-605274-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 52605 invoked by alias); 21 May 2018 22:25:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 52286 invoked by uid 55); 21 May 2018 22:25:41 -0000
From: "meissner at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85657] Make __ibm128 a separate type, even if long double uses the IBM double-double format
Date: Mon, 21 May 2018 22:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: major
X-Bugzilla-Who: meissner at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: meissner at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85657-4-CPjpsMjoYs@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85657-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85657-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02169.txt.bz2
Content-length: 1870
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85657
--- Comment #3 from Michael Meissner <meissner at gcc dot gnu.org> ---
Author: meissner
Date: Mon May 21 22:25:03 2018
New Revision: 260490
URL: https://gcc.gnu.org/viewcvs?rev=260490&root=gcc&view=rev
Log:
2018-05-21 Michael Meissner <meissner@linux.ibm.com>
PR target/85657
* config/rs6000/rs6000-c.c (rs6000_cpu_cpp_builtins): Do not
define __ibm128 as long double.
* config/rs6000/rs6000.c (rs6000_init_builtins): Create __ibm128
as a distinct type with IEEE 128-bit floating point is supported.
(init_float128_ieee): Fix up conversions between IFmode and IEEE
128-bit types to use the correct functions.
(rs6000_expand_float128_convert): Use explicit FLOAT_EXTEND to
convert between 128-bit floating point types that have different
modes but the same representation, instead of using gen_lowpart to
makean alias.
* config/rs6000/rs6000.md (IFKF): New iterator for IFmode and
KFmode.
(IFKF_reg): New attributes to give the register constraints for
IFmode and KFmode.
(extend<mode>tf2_internal): New insns to mark an explicit
conversion between 128-bit floating point types that have a
different mode but share the same representation.
[gcc/testsuite]
2018-05-21 Michael Meissner <meissner@linux.ibm.com>
PR target/85657
* gcc.target/powerpc/pr85657-1.c: New test for converting between
__float128, __ibm128, and long double.
* gcc.target/powerpc/pr85657-2.c: Likewise.
* gcc.target/powerpc/pr85657-3.c: Likewise.
* g++.dg/pr85667.C: New test to make sure __ibm128 is
implementated as a separate type internally, and is not just an
alias for long double.
Modified:
trunk/gcc/ChangeLog
>From gcc-bugs-return-605276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:50:47 2018
Return-Path: <gcc-bugs-return-605276-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6267 invoked by alias); 21 May 2018 22: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 6172 invoked by uid 48); 21 May 2018 22:50:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/81930] [meta-bug] Issues with -Weffc++
Date: Mon, 21 May 2018 22:50:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: dep_changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: diagnostic, meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-81930-4-zBYGfgrTam@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-81930-4@http.gcc.gnu.org/bugzilla/>
References: <bug-81930-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02171.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81930
Bug 81930 depends on bug 85858, which changed state.
Bug 85858 Summary: -Weffc++ should not require copy ctor for const pointers
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
>From gcc-bugs-return-605275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 22:50:47 2018
Return-Path: <gcc-bugs-return-605275-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6256 invoked by alias); 21 May 2018 22:50:46 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 6135 invoked by uid 48); 21 May 2018 22:50:39 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 22: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: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85858-4-t8iyNeCsup@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02170.txt.bz2
Content-length: 866
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
It's completely logical.
using const_int = const int;
const int* p = new const_int();
Do you expect to never be able to delete this object, instead being forced to
leak it?
What about:
void f() { const int i = 0; }
Do you think this stack variable can't be destroyed, because it's const?
The const qualifier affects modification of the object, not its destruction.
Your mental model of C++ is simply not how the language works.
>From gcc-bugs-return-605277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 23:17:05 2018
Return-Path: <gcc-bugs-return-605277-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92138 invoked by alias); 21 May 2018 23:17: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 92073 invoked by uid 48); 21 May 2018 23:17:00 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85864] [8/9 Regression] template argument string literal operator with default argument doesnt work in templates
Date: Mon, 21 May 2018 23: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: 8.1.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: keywords cc cf_known_to_work short_desc cf_known_to_fail
Message-ID: <bug-85864-4-Triat8eT86@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02172.txt.bz2
Content-length: 1135
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85864
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
CC| |jason at gcc dot gnu.org
Known to work| |7.3.0
Summary|template argument string |[8/9 Regression] template
|literal operator with |argument string literal
|default argument doesnt |operator with default
|work in templates |argument doesnt work in
| |templates
Known to fail| |8.1.0, 9.0
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I'm not sure if this is valid, but it started to be rejected with with r258039
PR c++/84489 - dependent default template argument
* pt.c (type_unification_real): Handle early substitution failure.
>From gcc-bugs-return-605278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 21 23:40:51 2018
Return-Path: <gcc-bugs-return-605278-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45236 invoked by alias); 21 May 2018 23: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 45204 invoked by uid 48); 21 May 2018 23:40:46 -0000
From: "msharov at users dot sourceforge.net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85858] -Weffc++ should not require copy ctor for const pointers
Date: Mon, 21 May 2018 23:40:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msharov at users dot sourceforge.net
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85858-4-SJlKztbrU3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85858-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02173.txt.bz2
Content-length: 2622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85858
--- Comment #8 from Mike Sharov <msharov at users dot sourceforge.net> ---
(In reply to Jonathan Wakely from comment #7)
> Your mental model of C++ is simply not how the language works.
My mental model here is actually of const correctness, not C++ specifically.
When I pass around a const object I expect it to stay unmodified. Consider a
function that takes a const T* argument. The signature suggests that the
passed-in object will only be read and will not be modified. If that function
deletes the pointer, "bad things" will likely happen. Suddenly the object
contains garbage and you can't figure out how it happened. All called functions
took it as const, so they shouldn't have messed with it. You assume memory
corruption and onto valgrind we go.
> The const qualifier affects modification of the object, not its destruction.
This is precisely the part I have a problem with. It seems downright loony to
state that destruction is not modification when the object is most definitely
modified by it. It's like saying that if I break into your house and take
stuff, I am a criminal, but if I burn it down, it's all perfectly fine.
> void f() { const int i = 0; }
>
> Do you think this stack variable can't be destroyed, because it's const?
What it boils down to is this: const restricts access, and so prevents
ownership. If you can't destroy a thing, you don't really own it. The standard
appears to have taken the position that ownership beats const correctness. I
instead argue in favor of const correctness, and its guarantee of invariance.
The stack variable in the example illustrates the difference between access and
ownership. f() has read-only access to i, and therefore does not own it. Who
owns i? The stack does. The stack passes i to f() with limited access, and
then, when f() terminates, the stack destroys i. This way ownership is clearly
delineated. If f() were to say delete i (assuming i were a pointer), it should
be prevented from doing so.
> using const_int = const int;
> const int* p = new const_int();
>
> Do you expect to never be able to delete this object,
> instead being forced to leak it?
Consequently, const objects created with new are owned by nobody, and simply do
not make sense. Somebody has to own the allocated object, so creating a const
object should be an invalid operation.
I suppose it doesn't really matter what my opinion is in this matter. Neither I
nor you write the standard, so I'll just leave this as a closing footnote in a
bug correctly resolved INVALID.
>From gcc-bugs-return-605279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 02:17:45 2018
Return-Path: <gcc-bugs-return-605279-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47688 invoked by alias); 22 May 2018 02: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 41477 invoked by uid 48); 22 May 2018 02:17:26 -0000
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/25829] [F03] Asynchronous IO support
Date: Tue, 22 May 2018 02:17:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.2.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: jvdelisle at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: koenigni at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-25829-4-DZ3MqjGek4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-25829-4@http.gcc.gnu.org/bugzilla/>
References: <bug-25829-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02174.txt.bz2
Content-length: 474
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=25829
--- Comment #42 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
(In reply to Nicolas Koenig from comment #41)
> Created attachment 44151 [details]
> Next version of patch.
--- snip ---
> real 0m15.465s
> user 0m15.313s
> sys 0m0.152s
>
> With the "no" replaced by "yes":
>
> real 0m5.558s
> user 0m16.253s
> sys 0m0.152s
>
> If you ask me, that's quite nice :)
Yes, very impressive.
>From gcc-bugs-return-605280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 03:45:03 2018
Return-Path: <gcc-bugs-return-605280-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 39842 invoked by alias); 22 May 2018 03:45:02 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 39779 invoked by uid 48); 22 May 2018 03:44:57 -0000
From: "gufideg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85866] New: [8 Regression] too few arguments to function when sfinae on calling pointer to member function
Date: Tue, 22 May 2018 03:45:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gufideg 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-85866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02175.txt.bz2
Content-length: 1028
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85866
Bug ID: 85866
Summary: [8 Regression] too few arguments to function when
sfinae on calling pointer to member function
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: gufideg at gmail dot com
Target Milestone: ---
This code fails under GCC 8:
#include <utility>
template<typename...>
using void_t = void;
template<typename U, typename V,
void_t<decltype(
(std::declval<U>().*std::declval<V>())()
)>* = nullptr>
void boom(){}
struct Foo {
void bar(){}
};
int main() {
boom<Foo, decltype(&Foo::bar)>();
}
This particular code compiles on all other GCC versions since 4.7
It also compiles on all versions of clang since version 3.4
Live example: https://godbolt.org/g/viHnMn
>From gcc-bugs-return-605281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 04:08:17 2018
Return-Path: <gcc-bugs-return-605281-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 73670 invoked by alias); 22 May 2018 04:08: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 73631 invoked by uid 48); 22 May 2018 04:08:12 -0000
From: "gufideg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85866] [8 Regression] too few arguments to function when sfinae on calling pointer to member function
Date: Tue, 22 May 2018 04: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:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: gufideg 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-85866-4-VDl343WtkX@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85866-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85866-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02176.txt.bz2
Content-length: 700
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85866
--- Comment #1 from Guillaume Racicot <gufideg at gmail dot com> ---
I tried some similar cases, and It seems it only happens when the expression
`(std::declval<U>().*std::declval<V>())()` is inside template parameters. In
the return type and normal function parameter it works as usual:
#include <utility>
template<typename...>
using void_t = void;
template<typename U, typename V>
void_t<decltype(
(std::declval<U>().*std::declval<V>())()
)> boom(){}
struct Foo {
void bar(){}
};
int main() {
boom<Foo, decltype(&Foo::bar)>();
}
Live example: https://godbolt.org/g/vTE9Sr
>From gcc-bugs-return-605282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 04:27:18 2018
Return-Path: <gcc-bugs-return-605282-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91242 invoked by alias); 22 May 2018 04:27: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 91208 invoked by uid 48); 22 May 2018 04:27:09 -0000
From: "yaghmour.shafik at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85867] New: Subscript operator applied to an temporary array results in an lvalue
Date: Tue, 22 May 2018 04:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: yaghmour.shafik 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-85867-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02177.txt.bz2
Content-length: 1125
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85867
Bug ID: 85867
Summary: Subscript operator applied to an temporary array
results in an lvalue
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: yaghmour.shafik at gmail dot com
Target Milestone: ---
This Stackoverflow question https://stackoverflow.com/q/33161003/1708801
provides the following code:
using Y = int[10];
int main() {
(Y { })[0] = 1;
}
which compiles without diagnostic, CWG defect report 1213:
http://www.open-std.org/jtc1/sc22/wg21/docs/cwg_defects.html#1213 says the
result of the subscript operator should be an xvalue and therefore not
assignable to.
Also see the following clang bug report on the same issue, which was resolved
at the end of 2017: https://bugs.llvm.org/show_bug.cgi?id=25357
I have a godbolt for it here: https://godbolt.org/g/AmzbFh
We can see that clang no longer allows this but gcc does.
>From gcc-bugs-return-605283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 05:57:59 2018
Return-Path: <gcc-bugs-return-605283-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67510 invoked by alias); 22 May 2018 05:57:58 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 49510 invoked by uid 48); 22 May 2018 05:52:01 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug testsuite/85865] [9 regression] Many libgomp fortran test cases fails starting with r260433
Date: Tue, 22 May 2018 05:57: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: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-85865-4-LNryjJuEql@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85865-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02178.txt.bz2
Content-length: 493
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85865
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #5 from janus at gcc dot gnu.org ---
All the failures should be fixed with r260487. Closing.
>From gcc-bugs-return-605284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 05:58:45 2018
Return-Path: <gcc-bugs-return-605284-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 72482 invoked by alias); 22 May 2018 05:58:45 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 71650 invoked by uid 55); 22 May 2018 05:58:35 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Tue, 22 May 2018 05: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: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85841-4-UF0ZRlYiHb@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02179.txt.bz2
Content-length: 3615
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
--- Comment #6 from janus at gcc dot gnu.org ---
Author: janus
Date: Tue May 22 05:41:45 2018
New Revision: 260499
URL: https://gcc.gnu.org/viewcvs?rev=260499&root=gcc&view=rev
Log:
2018-05-22 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
* libgfortran.h: Remove the macros GFC_STD_F2008_TS and
GFC_STD_OPT_F08TS.
* error.c (notify_std_msg): Remove GFC_STD_F2008_TS.
* options.c (set_default_std_flags): Ditto.
(gfc_handle_option): Make -std=f2008ts an alias for -std=f2018.
* array.c (gfc_match_array_spec): Replace GFC_STD_F2008_TS by
GFC_STD_F2018.
* check.c (gfc_check_atomic, gfc_check_event_query,
gfc_check_c_f_pointer, gfc_check_c_f_procpointer, gfc_check_c_funloc,
gfc_check_c_loc, gfc_check_num_images, gfc_check_this_image): Ditto.
* decl.c (gfc_verify_c_interop_param, gfc_match_decl_type_spec): Ditto.
* intrinsic.c (add_functions, add_subroutines,
gfc_check_intrinsic_standard): Ditto.
* iso-c-binding.def: Ditto.
* iso-fortran-env.def: Ditto.
* match.c (gfc_match_event_post, gfc_match_event_wait,
gfc_match_fail_image, gfc_match_form_team, gfc_match_change_team,
gfc_match_end_team, gfc_match_sync_team): Ditto.
* gfortran.texi: Remove mention of -std=f2008ts.
Move TSs into F2018 section.
* invoke.texi: Update documentation of -std=f2008ts.
2018-05-22 Janus Weil <janus@gcc.gnu.org>
PR fortran/85841
* gfortran.dg/assumed_rank_5.f90: Update error message.
* gfortran.dg/assumed_type_4.f90: Ditto.
* gfortran.dg/bind_c_array_params.f03: Ditto.
* gfortran.dg/bind_c_usage_28.f90: Ditto.
* gfortran.dg/c_funloc_tests_5.f03: Ditto.
* gfortran.dg/c_funloc_tests_6.f90: Ditto.
* gfortran.dg/c_loc_tests_11.f03: Ditto.
* gfortran.dg/coarray_atomic_2.f90: Ditto.
* gfortran.dg/coarray_collectives_2.f90: Ditto.
* gfortran.dg/coarray_collectives_10.f90: Ditto.
* gfortran.dg/coarray_collectives_13.f90: Ditto.
* gfortran.dg/rank_3.f90: Ditto.
* gfortran.dg/error_stop_4.f90: Replace -std=f2008ts by -std=f2008.
* gfortran.dg/implicit_14.f90: Ditto.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/array.c
trunk/gcc/fortran/check.c
trunk/gcc/fortran/decl.c
trunk/gcc/fortran/error.c
trunk/gcc/fortran/gfortran.texi
trunk/gcc/fortran/intrinsic.c
trunk/gcc/fortran/invoke.texi
trunk/gcc/fortran/iso-c-binding.def
trunk/gcc/fortran/iso-fortran-env.def
trunk/gcc/fortran/libgfortran.h
trunk/gcc/fortran/match.c
trunk/gcc/fortran/options.c
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gfortran.dg/assumed_rank_5.f90
trunk/gcc/testsuite/gfortran.dg/assumed_type_4.f90
trunk/gcc/testsuite/gfortran.dg/bind_c_array_params.f03
trunk/gcc/testsuite/gfortran.dg/bind_c_usage_28.f90
trunk/gcc/testsuite/gfortran.dg/c_funloc_tests_5.f03
trunk/gcc/testsuite/gfortran.dg/c_funloc_tests_6.f90
trunk/gcc/testsuite/gfortran.dg/c_loc_tests_11.f03
trunk/gcc/testsuite/gfortran.dg/coarray_atomic_2.f90
trunk/gcc/testsuite/gfortran.dg/coarray_collectives_10.f90
trunk/gcc/testsuite/gfortran.dg/coarray_collectives_13.f90
trunk/gcc/testsuite/gfortran.dg/coarray_collectives_2.f90
trunk/gcc/testsuite/gfortran.dg/error_stop_4.f90
trunk/gcc/testsuite/gfortran.dg/implicit_14.f90
trunk/gcc/testsuite/gfortran.dg/rank_3.f90
>From gcc-bugs-return-605285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 05:59:02 2018
Return-Path: <gcc-bugs-return-605285-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74317 invoked by alias); 22 May 2018 05: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 73706 invoked by uid 48); 22 May 2018 05:58:55 -0000
From: "fdumont at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85845] [9 Regression] Many libstdc++ test failures
Date: Tue, 22 May 2018 05:59:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: fdumont at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: fdumont at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85845-4-CHJHkeRK3H@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85845-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02180.txt.bz2
Content-length: 452
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85845
François Dumont <fdumont at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from François Dumont <fdumont at gcc dot gnu.org> ---
Regression fixed.
>From gcc-bugs-return-605286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 07:09:22 2018
Return-Path: <gcc-bugs-return-605286-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17678 invoked by alias); 22 May 2018 07:09:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17600 invoked by uid 48); 22 May 2018 07:09:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85834] [9 regression] ice in set_ssa_val_to, at tree-ssa-sccvn.c:3396
Date: Tue, 22 May 2018 07: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: build, 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: cc bug_status assigned_to attachments.created
Message-ID: <bug-85834-4-JHB9k4WVbv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85834-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02181.txt.bz2
Content-length: 958
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85834
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |marxin at gcc dot gnu.org
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 #7 from Martin Liška <marxin at gcc dot gnu.org> ---
Really started with r260318.
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
Created attachment 44159
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44159&action=edit
patch I am testing
Mine. Testing patch.
>From gcc-bugs-return-605288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 07:13:33 2018
Return-Path: <gcc-bugs-return-605288-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32026 invoked by alias); 22 May 2018 07:13: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 31889 invoked by uid 48); 22 May 2018 07:13:29 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85836] [meta-bug] Fortran 2018 support
Date: Tue, 22 May 2018 07:13: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: 8.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85836-4-i1T76l8vdK@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85836-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85836-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02183.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85836
Bug 85836 depends on bug 85841, which changed state.
Bug 85841 Summary: [F2018] reject deleted features
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
>From gcc-bugs-return-605287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 07:13:33 2018
Return-Path: <gcc-bugs-return-605287-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31942 invoked by alias); 22 May 2018 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 31880 invoked by uid 48); 22 May 2018 07:13:28 -0000
From: "janus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85841] [F2018] reject deleted features
Date: Tue, 22 May 2018 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: 8.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: janus at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P5
X-Bugzilla-Assigned-To: janus at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution target_milestone
Message-ID: <bug-85841-4-AP9yLBxlZL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85841-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02182.txt.bz2
Content-length: 703
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85841
janus at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #7 from janus at gcc dot gnu.org ---
(In reply to janus from comment #4)
> As a minor follow-up, one should get rid of the GFC_STD_F2008_TS macro and
> make -std=f2008ts an alias for -std=f2018.
This has been done in r260499 and also some libgomp failures have been
corrected in r260487.
Closing.
>From gcc-bugs-return-605289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 07:46:38 2018
Return-Path: <gcc-bugs-return-605289-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 84724 invoked by alias); 22 May 2018 07:46: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 74472 invoked by uid 48); 22 May 2018 07:46:29 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85863] [9 Regression] ICE in compiling spec2006 fortran test case solib.fppized.f starting with r260283
Date: Tue, 22 May 2018 07:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: 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: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on cc assigned_to target_milestone everconfirmed
Message-ID: <bug-85863-4-GVEMngggWv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85863-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85863-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02184.txt.bz2
Content-length: 5084
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85863
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2018-05-22
CC| |jakub at gcc dot gnu.org
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> ---
gamess works fine here (x86_64). The test that triggers is
if (maybe_ne (TYPE_VECTOR_SUBPARTS (type),
TYPE_VECTOR_SUBPARTS (op0_type)))
{
error ("invalid vector comparison resulting type");
debug_generic_expr (type);
return true;
that means the IL is bogus and the issue likely latent. Reduced testcase:
SUBROUTINE SOBOOK(MHSO,HSOMAX)
IMPLICIT DOUBLE PRECISION(A-H,O-Z)
COMPLEX*16 HSOT,HSO1(2)
PARAMETER (ZERO=0.0D+00,TWO=2.0D+00)
DIMENSION SOL1(3,2),SOL2(3)
SQRT2=SQRT(TWO)
DO IH=1,MHSO
IF(MS.EQ.0) THEN
HSO1(IH) = DCMPLX(ZERO,-SOL1(3,IH))
HSOT = DCMPLX(ZERO,-SOL2(3))
ELSE
HSO1(IH) = DCMPLX(-SOL1(2,IH),SOL1(1,IH))/SQRT2
HSOT = DCMPLX(-SOL2(2),SOL2(1))/SQRT2
ENDIF
ENDDO
HSOT=HSOT+HSO1(1)
HSOMAX=MAX(HSOMAX,ABS(HSOT))
RETURN
END
The bogus comparison is built here:
0x0000000001378d87 in vectorizable_condition (stmt=
<gimple_assign 0x7ffff69aa4e0>, gsi=0x7fffffffcf30,
vec_stmt=0x7fffffffcbf0, reduc_def=<tree 0x0>, reduc_index=0,
slp_node=0x2928520, cost_vec=0x0) at /tmp/trunk/gcc/tree-vect-stmts.c:9000
9000 vec_cond_lhs, vec_cond_rhs);
Value returned is $7 = (tree_node *) 0x7ffff69cc870
(gdb) l
8995 else
8996 {
8997 vec_cond_rhs = vec_oprnds1[i];
8998 if (bitop1 == NOP_EXPR)
8999 vec_compare = build2 (cond_code, vec_cmp_type,
9000 vec_cond_lhs, vec_cond_rhs);
9001 else
9002 {
9003 new_temp = make_ssa_name (vec_cmp_type);
9004 if (bitop1 == BIT_NOT_EXPR)
so we face a conversion that isn't NOP. Which looks somewhat weird.
The stmt we try to vectorize is
_ifc__74 = ms_36(D) == 0 ? _ifc__75 : _ifc__76;
where _ifc__75 is DFmode and the comparison is a SImode comparison.
Nothing in vectorizable_condition seems to verify we need no
widening/shortening
of the comparison result... I guess pattern recognition usually deals with
this but doesn't in this case. Ah, and it is that we run into
the following vect_is_simple_cond code:
/* Invariant comparison. */
if (! *comp_vectype)
{
tree scalar_type = TREE_TYPE (lhs);
/* If we can widen the comparison to match vectype do so. */
if (INTEGRAL_TYPE_P (scalar_type)
&& tree_int_cst_lt (TYPE_SIZE (scalar_type),
TYPE_SIZE (TREE_TYPE (vectype))))
scalar_type = build_nonstandard_integer_type
(tree_to_uhwi (TYPE_SIZE (TREE_TYPE (vectype))),
TYPE_UNSIGNED (scalar_type));
*comp_vectype = get_vectype_for_scalar_type (scalar_type);
which widens the vector type. But nothing in code-generation deals
with this in the SLP case since only vect_get_vec_def_for_operand
gets the extra invariant vector type argument but vect_get_slp_defs
knows nothing about such requirement.
Jakub ventured last in this area of the code but obviously a patch like
the following would help to reflect that reality. I'm testing that patch.
Index: gcc/tree-vect-stmts.c
===================================================================
--- gcc/tree-vect-stmts.c (revision 260499)
+++ gcc/tree-vect-stmts.c (working copy)
@@ -8661,7 +8661,7 @@ vect_is_simple_cond (tree cond, vec_info
*comp_vectype = vectype1 ? vectype1 : vectype2;
/* Invariant comparison. */
- if (! *comp_vectype)
+ if (! *comp_vectype && vectype)
{
tree scalar_type = TREE_TYPE (lhs);
/* If we can widen the comparison to match vectype do so. */
@@ -8773,7 +8773,7 @@ vectorizable_condition (gimple *stmt, gi
else_clause = gimple_assign_rhs3 (stmt);
if (!vect_is_simple_cond (cond_expr, stmt_info->vinfo,
- &comp_vectype, &dts[0], vectype)
+ &comp_vectype, &dts[0], slp_node ? NULL : vectype)
|| !comp_vectype)
return false;
>From gcc-bugs-return-605290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 08:07:42 2018
Return-Path: <gcc-bugs-return-605290-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125403 invoked by alias); 22 May 2018 08: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 125191 invoked by uid 48); 22 May 2018 08:07:26 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85853] [9 Regression] ICE in vect_is_simple_use, at tree-vect-stmts.c:10233 on ppc64
Date: Tue, 22 May 2018 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: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc version short_desc
Message-ID: <bug-85853-4-Qs6AinWMDA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85853-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85853-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg02185.txt.bz2
Content-length: 854
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85853
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rsandifo at gcc dot gnu.org
Version|unknown |9.0
Summary|ICE in vect_is_simple_use, |[9 Regression] ICE in
|at tree-vect-stmts.c:10233 |vect_is_simple_use, at
|on ppc64le |tree-vect-stmts.c:10233 on
| |ppc64
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed with a cross. This is probably Richards recent changes that exposes
that vector types are not set reliably during SLP analysis.
>From gcc-bugs-return-605291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue May 22 08:10:57 2018
Return-Path: <gcc-bugs-return-605291-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1484 invoked by alias); 22 May 2018 08:10:57 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 1050 invoked by uid 89); 22 May 2018 08:10:53 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=0.1 required=5.0 testsºYES_50,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,TIME_LIMIT_EXCEEDED autolearn=unavailable version=3.3.2 spammy¾autiful, tax, sa, WILL
X-HELO: smtp01-smtpout04.rb.za.mtnbusiness.net
Received: from smtp01-smtpout04.rb.za.mtnbusiness.net (HELO smtp01-smtpout04.rb.za.mtnbusiness.net) (41.181.159.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 22 May 2018 08:10:42 +0000
Received: from [41.115.11.175] (helo\x169-0-244-214.ip.mtnbusiness.co.za) by smtp.mtnbusiness.co.za with esmtp (Blowfish SMTP) (envelope-from <botha.l@helpsa2018.co.za>) id 1fL2MP-0008Oh-H9 for gcc-bugs@gcc.gnu.org; Tue, 22 May 2018 10:09:37 +0200
From: "Leonie Botha" <botha.l@helpsa2018.co.za>
Subject: Hope for Warmth
To: gcc-bugs@gcc.gnu.org
MIME-Version: 1.0
Reply-To: "Leonie Botha" <leonie.b@helpingsa.co.za>
Date: Tue, 22 May 2018 08:10:00 -0000
X-Spam-Score: 0.0 (/)
X-Spam-Report: BAYES_00=-1.9,CK_HELO_DYNAMIC_SPLIT_IP=0.388,HELO_MISC_IP=0.25,HTML_MESSAGE=0.001,MISSING_MID=0.497,RDNS_NONE=0.793, * 0.4 CK_HELO_DYNAMIC_SPLIT_IP Relay HELO'd using suspicious hostname * (Split IP) * -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% * [score: 0.0000] * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.8 RDNS_NONE Delivered to internal network by a host with no rDNS * 0.5 MISSING_MID Missing Message-Id: header * 0.2 HELO_MISC_IP Looking for more Dynamic IP Relays
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2018-05/txt/msg02186.txt.bz2
Content-length: 5357
Helping SA’s Hope for Warmth
Many children have to go through this winter with blankets that’s torn and has holes in it they have to share 1 blanket with their siblings, some has no blanket at all and has to rely on a plastic bag or box to cover themselves, for these families it’s a difficulty just to have bread to eat, not to mention to be able to take a few rand and buy a blanket, we have situations where children gets in to fights with their brothers or sisters over a jersey, the elderly suffers just as much we have elderly staying in garages, shacks back rooms with raw cement floors, holes in the walls, broken windows, this is elderly that the state feels do not qualify for a pension grant, they also cannot find employment due to their age and illnesses.
In a lot of elderly care centres the number of death rises in the winter time as the cold makes it difficult to fight against viruses and already illnesses, the one thing we seldom hear about is the number of deaths of elderly during winter time, who has been forgotten by their children, who lives on their own in this cold back rooms and garages, who mostly suffers because they do not have warm clothing and bedding most have illnesses such as arthritis, which is already very painful and gets worse with the cold, they will roll up in balls and just try and keep warm ending up not to be able to get up and find something to eat, most not having a proper meal to start with resulting in them getting weaker and weaker.
Winter is a beautiful season but a dreadful one for all destitute families, children and elderly, it’s the longest 3 months of your life if you have no warm clothes, no warm bedding, live in a room with raw cement floors, holes in your roof and still on top of this you have to fight off the hunger that overcomes you, where can they find the strength that they need to overcome all of this?
We need to be the change, we can give them the strength we can lift them up by providing blankets, warm clothing and warm food, please help us to make this difference in the lives of the ones who suffers so much already. The children, families and elderly that we assist is located across South Africa, there is so many that need assistance that we have start this drive as soon as possible and not wait for when the coldest days is upon us.
It Cost us +/- R1800 per month per family for their food parcel this includes healthy balanced meals.
It Cost us R 800- R1200 for a family of 3 for blankets and at least 2 jerseys and pants for each
The fundraising will be done by asking for a R 100 donation towards our hope for warmth project you can do a bank transfer to help us save on cost so we can help many more in return you will receive a tax (Section 18A) invoice to claim back from tax and a Helping Sa Warmth Hope ribbon that we hope you will wear with pride knowing what a difference you have made.
Examples of what your R 100 donation WILL do:
Feed a child / elderly for 3 days /
1 pair of warm shoes and socks
1 Winter pants / 1 Jersey
1 Jacket
Warm bedding/ Blankets
1 Child will be able to take the bus to school for a week and no need to walk over 6 km
You can give hope where there is none!!
If you are doing a donation through the bank for this worthy project, please reply to this email with your details and postal address to ensure you receive your Invoice and special Ribbon.
To view our NPO and Section 18A certificates please visit our website, while you are visiting please enjoy our photos and videos.
(To receive copies of our certificates / proof of registration, accounting letters etc. you can also email admin (@) hsa-team.co.za or reply to this email requesting documents)
Hope you can find it your heart to assist with this project.
ABSA
HELPING SA
ACC NR; 4080925296
BRANCH: 632005
CURRENT ACCOUNT
PLEASE USE REFERENCE LC AND YOUR NAME OR COMPANY NAME
WHEN DOING A TRANSFER - THANKING YOU IN ADVANCE
OR
NEDBANK
HELPING SA
ACC NR; 1162381620
BRANCH: 198765
CURRENT ACCOUNT
We would like this project to go on for a long time, so that it can really make an impact on the ones we assist, thus we do have debit facilities now, if you would like to assist this project more than once we would really appreciate it, you can request a debit order form by email.
Yours Faithfully
Leonie Botha
Vice-Chairperson/Fundraiser
Helping SA
081 703 6774
Fax: 086 509 9871
Alternative email: leonie (@) helpingsa.co.za / leonie (@) hsa-team.co.za
Web: (www) helping-sa.co.za
NPO: 115-333
PBO: 930043138
"Generosity consists not the sum given, but the manner in which it is bestowed"
If you wish not to receive emails from me, please reply with a blank email and I will never email you again, we do not mean to spam anyone we are just trying to assist as many as possible. Thanking you in advance. OR UNSUBSCRIBE We rather email than trouble you on the phone while you are busy this way you can decide when you have time to go through our email.
^ permalink raw reply [flat|nested] 2+ messages in thread
* [Bug c++/85809] SFINAE code compiles that shouldn't be able to compile.
[not found] <bug-85809-4@http.gcc.gnu.org/bugzilla/>
2018-05-16 14:59 ` [Bug c++/85809] SFINAE code compiles that shouldn't be able to compile redi at gcc dot gnu.org
@ 2021-07-23 22:25 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 2+ messages in thread
From: pinskia at gcc dot gnu.org @ 2021-07-23 22:25 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85809
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |FIXED
Target Milestone|--- |9.0
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Fixed in GCC 9.0.
In file included from <source>:1:
/opt/compiler-explorer/gcc-9.1.0/include/c++/9.1.0/type_traits: In substitution
of 'template<bool _Cond, class _Tp> using enable_if_t = typename
std::enable_if::type [with bool _Cond = (0 == 1); _Tp = float]':
<source>:20:10: required from 'class MyClass<FOO>'
<source>:27:26: required from here
/opt/compiler-explorer/gcc-9.1.0/include/c++/9.1.0/type_traits:2426:11: error:
no type named 'type' in 'struct std::enable_if<false, float>'
2426 | using enable_if_t = typename enable_if<_Cond, _Tp>::type;
| ^~~~~~~~~~~
ASM generation compiler returned: 1
-------------------------
The original testcase:
#include <type_traits>
enum MyEnum
{
FOO,
BAR
};
template <MyEnum E>
void do_stuff(std::enable_if_t<E == FOO, float> a) { /*do foo logic*/ }
template <MyEnum E>
void do_stuff(std::enable_if_t<E == BAR, float> a) { /*do bar logic*/ }
template <MyEnum E>
class MyClass
{
public:
void go(std::enable_if_t<E == MyEnum::FOO, int>) {}
void go(std::enable_if_t<E == MyEnum::BAR, float>) {}
};
int main()
{
do_stuff<MyEnum::BAR>(2.f); // Comment this line out and it doesn't compile
anymore.
MyClass<MyEnum::FOO> q;
q.go(1);
}
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-07-23 22:25 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-85809-4@http.gcc.gnu.org/bugzilla/>
2018-05-16 14:59 ` [Bug c++/85809] SFINAE code compiles that shouldn't be able to compile redi at gcc dot gnu.org
2021-07-23 22:25 ` pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).