public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/85732] use_facet<moneypunct<char, true>>(mylocale) retrieving wrong locale information
[not found] <bug-85732-4@http.gcc.gnu.org/bugzilla/>
@ 2018-05-10 18:14 ` gnu-org at bignm dot com
0 siblings, 0 replies; only message in thread
From: gnu-org at bignm dot com @ 2018-05-10 18:14 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: 265739 bytes --]
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85732
--- Comment #7 from Tom Straub <gnu-org at bignm dot com> ---
Hi Jonathan,
Thanks for really tracking that down. Looks like a really deep and subtle bug.
I hope somebody knows where to look to fix it in the glibc code.
Best, Tom
>From gcc-bugs-return-604323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:16:20 2018
Return-Path: <gcc-bugs-return-604323-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 91809 invoked by alias); 10 May 2018 18:16:20 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 91755 invoked by uid 48); 10 May 2018 18:16: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: Thu, 10 May 2018 18: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.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-g5GFZugogB@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/msg01218.txt.bz2
Content-length: 368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
--- Comment #13 from Marc Glisse <glisse at gcc dot gnu.org> ---
Explicitly marking the constructor with __restrict lets it optimize also the
testcase in comment #12. I have no idea what was changed in gcc-8 that helped
the original testcase, but it wasn't equivalent to marking constructors with
__restrict :-(
>From gcc-bugs-return-604324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:30:41 2018
Return-Path: <gcc-bugs-return-604324-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 14975 invoked by alias); 10 May 2018 18:30: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 115964 invoked by uid 48); 10 May 2018 18:30:04 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85737] gfortran 8.1.0 false positive with -Wdo-subscript
Date: Thu, 10 May 2018 18:30:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: INVALID
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cc resolution
Message-ID: <bug-85737-4-pBoWeqCDw5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85737-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85737-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01219.txt.bz2
Content-length: 1118
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85737
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |tkoenig at gcc dot gnu.org
Resolution|--- |INVALID
--- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
It is working as (currently) designed.
To quote from the description:
`-Wdo-subscript'
Warn if an array subscript inside a DO loop could lead to an
out-of-bounds access even if the compiler can not prove that the
statement is actually executed, in cases like
real a(3)
do i=1,4
if (condition(i)) then
a(i) = 1.2
end if
end do
This option is implied by `-Wextra'.
Some more extensive data flow analysis may be possible in
future versions of gfortran.
It is always possible to turn this off via -Wno-do-subscript.
>From gcc-bugs-return-604325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:33:58 2018
Return-Path: <gcc-bugs-return-604325-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 27664 invoked by alias); 10 May 2018 18: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 27614 invoked by uid 55); 10 May 2018 18:33:54 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85735] f951 crashes on empty input
Date: Thu, 10 May 2018 18: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85735-4-N9QaoPFcbP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01220.txt.bz2
Content-length: 430
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85735
--- Comment #2 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Author: mpolacek
Date: Thu May 10 18:33:22 2018
New Revision: 260120
URL: https://gcc.gnu.org/viewcvs?rev=260120&root=gcc&view=rev
Log:
PR fortran/85735
* options.c (gfc_post_options): Set main_input_filename.
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/options.c
>From gcc-bugs-return-604326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:34:09 2018
Return-Path: <gcc-bugs-return-604326-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 28438 invoked by alias); 10 May 2018 18:34: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 28368 invoked by uid 48); 10 May 2018 18:34:05 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85735] f951 crashes on empty input
Date: Thu, 10 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: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: mpolacek at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 9.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85735-4-CAgGrbJcfh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85735-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85735-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01221.txt.bz2
Content-length: 429
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85735
Marek Polacek <mpolacek at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-604327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:42:02 2018
Return-Path: <gcc-bugs-return-604327-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103891 invoked by alias); 10 May 2018 18:42: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 103860 invoked by uid 48); 10 May 2018 18:41:58 -0000
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85738] New: internal compiler error: verify_gimple failed
Date: Thu, 10 May 2018 18:42: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: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01222.txt.bz2
Content-length: 1696
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85738
Bug ID: 85738
Summary: internal compiler error: verify_gimple failed
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: mpolacek at gcc dot gnu.org
Target Milestone: ---
With this invalid code:
module test
contains
function gx(l)
implicit none
integer, intent(in) :: l
integer, external :: fx
real(8) :: gx
gx=fx(l)**2/(2*(2*l + 1))
end function gx
end module test
function fx(l)
implicit none
integer, intent(in) :: l
real(8) :: fx
fx = l
end function fx
I get
$ ./f951 -quiet z.f90
z.f90:3:0:
function gx(l)
Error: type mismatch in binary expression
integer(kind=4)
real(kind=8)
integer(kind=4)
_5 = D.3778 / _4;
z.f90:3:0: internal compiler error: verify_gimple failed
0xf9791e verify_gimple_in_seq(gimple*)
/home/marek/src/gcc/gcc/tree-cfg.c:5021
0xc13c82 gimplify_body(tree_node*, bool)
/home/marek/src/gcc/gcc/gimplify.c:12715
0xc14162 gimplify_function_tree(tree_node*)
/home/marek/src/gcc/gcc/gimplify.c:12805
0x9d7e94 cgraph_node::analyze()
/home/marek/src/gcc/gcc/cgraphunit.c:670
0x9d9779 analyze_functions
/home/marek/src/gcc/gcc/cgraphunit.c:1131
0x9de439 symbol_table::finalize_compilation_unit()
/home/marek/src/gcc/gcc/cgraphunit.c:2691
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-604328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:47:16 2018
Return-Path: <gcc-bugs-return-604328-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 112303 invoked by alias); 10 May 2018 18:47: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 112206 invoked by uid 48); 10 May 2018 18:47:10 -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: Thu, 10 May 2018 18: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.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-umSiSaMz9C@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/msg01223.txt.bz2
Content-length: 699
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
--- Comment #14 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #13)
> I have no idea what was changed in gcc-8 that
> helped the original testcase,
(optimization happens in FRE1)
It could be an optimization that says that either the objects don't alias and
we are writing _1, or they are the same object and we are writing _1, so just
write _1 without caring about aliasing. This was definitely discussed, but I
didn't remember that it had been committed (bug 80617 is still open).
Anyway, if you want to experiment, the function build_this_parm (in
gcc/cp/decl.c) seems like a good starting point.
>From gcc-bugs-return-604329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:48:46 2018
Return-Path: <gcc-bugs-return-604329-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 117287 invoked by alias); 10 May 2018 18:48: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 114621 invoked by uid 48); 10 May 2018 18:48:03 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/82893] Bad diagnostic on negative sized array
Date: Thu, 10 May 2018 18: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: 8.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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-82893-4-Tm4zbPq3ED@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-82893-4@http.gcc.gnu.org/bugzilla/>
References: <bug-82893-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01224.txt.bz2
Content-length: 584
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82893
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jason at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed by patches for 80227.
*** This bug has been marked as a duplicate of bug 80227 ***
>From gcc-bugs-return-604331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:49:32 2018
Return-Path: <gcc-bugs-return-604331-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19927 invoked by alias); 10 May 2018 18:49: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 15070 invoked by uid 48); 10 May 2018 18:49:22 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/68280] dependent arrays of excessive size not diagnosed
Date: Thu, 10 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: 6.0
X-Bugzilla-Keywords: accepts-invalid, diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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-68280-4-ZLqDaBozQA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68280-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68280-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01226.txt.bz2
Content-length: 582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68280
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |jason at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #2 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed by patch for 80227.
*** This bug has been marked as a duplicate of bug 80227 ***
>From gcc-bugs-return-604330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:49:15 2018
Return-Path: <gcc-bugs-return-604330-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 13960 invoked by alias); 10 May 2018 18:49: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 120240 invoked by uid 48); 10 May 2018 18:48:33 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80227] [6/7 Regression] SFINAE ambiguity with a pointer to array argument
Date: Thu, 10 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: 7.0
X-Bugzilla-Keywords: accepts-invalid, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80227-4-FNwMYZvb8o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80227-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80227-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01225.txt.bz2
Content-length: 446
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80227
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |barry.revzin at gmail dot com
--- Comment #6 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 82893 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:49:37 2018
Return-Path: <gcc-bugs-return-604332-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21274 invoked by alias); 10 May 2018 18:49: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 19538 invoked by uid 48); 10 May 2018 18:49:31 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80227] [6/7 Regression] SFINAE ambiguity with a pointer to array argument
Date: Thu, 10 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: 7.0
X-Bugzilla-Keywords: accepts-invalid, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80227-4-C7nWnUePaj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80227-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80227-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01227.txt.bz2
Content-length: 181
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80227
--- Comment #7 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 68280 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:53:51 2018
Return-Path: <gcc-bugs-return-604333-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63603 invoked by alias); 10 May 2018 18: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 63475 invoked by uid 48); 10 May 2018 18:53:47 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80169] G++ (cc1plus) hangs forever compiling template when size of array is enormous
Date: Thu, 10 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: c++
X-Bugzilla-Version: 6.3.1
X-Bugzilla-Keywords: compile-time-hog, ice-on-invalid-code, memory-hog
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason 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-80169-4-AsrE5m2tz5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80169-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80169-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01228.txt.bz2
Content-length: 582
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80169
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
CC| |jason at gcc dot gnu.org
Resolution|--- |DUPLICATE
--- Comment #1 from Jason Merrill <jason at gcc dot gnu.org> ---
Fixed by patch for 80227.
*** This bug has been marked as a duplicate of bug 80227 ***
>From gcc-bugs-return-604334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:53:53 2018
Return-Path: <gcc-bugs-return-604334-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63812 invoked by alias); 10 May 2018 18:53: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 63507 invoked by uid 48); 10 May 2018 18:53:48 -0000
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/80227] [6/7 Regression] SFINAE ambiguity with a pointer to array argument
Date: Thu, 10 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: c++
X-Bugzilla-Version: 7.0
X-Bugzilla-Keywords: accepts-invalid, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jason at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: jason at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-80227-4-oY7g1HMemB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80227-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80227-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01229.txt.bz2
Content-length: 439
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80227
Jason Merrill <jason at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dawid_jurek at vp dot pl
--- Comment #8 from Jason Merrill <jason at gcc dot gnu.org> ---
*** Bug 80169 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 18:56:08 2018
Return-Path: <gcc-bugs-return-604335-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66832 invoked by alias); 10 May 2018 18:56: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 66743 invoked by uid 48); 10 May 2018 18:56:03 -0000
From: "freddie_chopin at op dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85739] New: internal compiler error: in finish_member_declaration, at cp/semantics.c:3057
Date: Thu, 10 May 2018 18:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: freddie_chopin at op dot 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 attachments.created
Message-ID: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01230.txt.bz2
Content-length: 2454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85739
Bug ID: 85739
Summary: internal compiler error: in finish_member_declaration,
at cp/semantics.c:3057
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: freddie_chopin at op dot pl
Target Milestone: ---
Created attachment 44111
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44111&action=edit
preprocessed source code
Attached preprocessed source code.
Trying to build it:
-- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 --
$ arm-none-eabi-g++ -fno-use-cxa-atexit -fno-rtti -fno-exceptions
-mcpu=cortex-m4 -mthumb -mfloat-abi=hard -mfpu=fpv4-sp-d16 -g -ggdb3 -O2
-ffunction-sections -fdata-sections -Wall -Wextra -Wshadow -std=gnu++17 -o
Scheduler.cpp.o -c Scheduler.ii
In file included from
../include/distortos/internal/scheduler/ThreadListNode.hpp:15,
from
../include/distortos/internal/scheduler/ThreadControlBlock.hpp:17,
from ../include/distortos/internal/scheduler/Scheduler.hpp:15,
from ../source/scheduler/Scheduler.cpp:12:
../include/estd/IntrusiveList.hpp: In instantiation of 'class
estd::IntrusiveListConstIterator<distortos::internal::ThreadListNode,
&distortos::internal::ThreadListNode::threadListNode,
distortos::internal::ThreadControlBlock>':
../source/scheduler/Scheduler.cpp:345:31: required from here
../include/estd/IntrusiveList.hpp:650:1: internal compiler error: in
finish_member_declaration, at cp/semantics.c:3057
{
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://gcc.gnu.org/bugs/> for instructions.
$ arm-none-eabi-g++ --version
arm-none-eabi-g++ (bleeding-edge-toolchain) 8.1.0
Copyright (C) 2018 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.
-- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 --
The exact same thing happens for gcc 7.3.0 and 6.3.0. There is no error when
using `-std=gnu++11` or `-std=gnu++14`. Whether or not GNU extensions are
enabled makes no difference.
Let me know if I should try to narrow the problem down, as the preprocessed
test case is indeed a bit huge.
>From gcc-bugs-return-604336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 19:00:59 2018
Return-Path: <gcc-bugs-return-604336-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 88105 invoked by alias); 10 May 2018 19:00: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 80900 invoked by uid 48); 10 May 2018 19:00:45 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80617] [missed optimization] Storing constant in two possibly-aliased locations
Date: Thu, 10 May 2018 19:00:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-80617-4-a5M1aJjCk9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01231.txt.bz2
Content-length: 628
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80617
--- Comment #9 from Marc Glisse <glisse at gcc dot gnu.org> ---
The testcases from comment #6 and comment #7 are now (gcc-8) properly
optimized. The original has lost one of the 2 calls to free, one remains:
__old_val_4 = MEM[(void * &)a_2(D)];
MEM[(void * &)a_2(D)] = 0B;
__old_val_5 = MEM[(void * &)b_3(D)];
MEM[(void * &)b_3(D)] = 0B;
MEM[(void * &)a_2(D)] = __old_val_5;
_6 = MEM[(void * &)b_3(D)];
MEM[(void * &)b_3(D)] = __old_val_4;
if (_6 != 0B)
(whether a is the same as b or disjoint, _6 is always 0, but that's not easy to
see)
>From gcc-bugs-return-604337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 19:04:08 2018
Return-Path: <gcc-bugs-return-604337-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 130169 invoked by alias); 10 May 2018 19:04:08 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 125530 invoked by uid 48); 10 May 2018 19:04:04 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80617] [missed optimization] Storing constant in two possibly-aliased locations
Date: Thu, 10 May 2018 19:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_severity
Message-ID: <bug-80617-4-FIMguYY0E4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01232.txt.bz2
Content-length: 1055
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80617
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|normal |enhancement
--- Comment #10 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Marc Glisse from comment #9)
> The testcases from comment #6 and comment #7 are now (gcc-8) properly
> optimized. The original has lost one of the 2 calls to free, one remains:
>
> __old_val_4 = MEM[(void * &)a_2(D)];
> MEM[(void * &)a_2(D)] = 0B;
> __old_val_5 = MEM[(void * &)b_3(D)];
> MEM[(void * &)b_3(D)] = 0B;
> MEM[(void * &)a_2(D)] = __old_val_5;
> _6 = MEM[(void * &)b_3(D)];
> MEM[(void * &)b_3(D)] = __old_val_4;
> if (_6 != 0B)
>
> (whether a is the same as b or disjoint, _6 is always 0, but that's not easy
> to see)
Do to the above analysis, there is another bug which this is a dup of but I
can't find it right now.
>From gcc-bugs-return-604338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 19:27:19 2018
Return-Path: <gcc-bugs-return-604338-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 21822 invoked by alias); 10 May 2018 19:27:19 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 21343 invoked by uid 48); 10 May 2018 19:27:12 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85623] strncmp() warns about attribute 'nonstring' incorrectly in -Wstringop-overflow
Date: Thu, 10 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: c
X-Bugzilla-Version: 8.1.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: keywords
Message-ID: <bug-85623-4-qmou5yp3HI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85623-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85623-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01233.txt.bz2
Content-length: 422
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85623
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |patch
--- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> ---
Patch: https://gcc.gnu.org/ml/gcc-patches/2018-05/msg00509.html
>From gcc-bugs-return-604339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 19:43:40 2018
Return-Path: <gcc-bugs-return-604339-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 83721 invoked by alias); 10 May 2018 19:43:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 83637 invoked by uid 48); 10 May 2018 19:43:35 -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: Thu, 10 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.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: attachments.created
Message-ID: <bug-82899-4-FcDUF2kdzk@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/msg01234.txt.bz2
Content-length: 378
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82899
--- Comment #15 from Marc Glisse <glisse at gcc dot gnu.org> ---
Created attachment 44112
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44112&action=edit
Untested patch
Something like this, but I haven't tested, and other calls to build_this_parm
need auditing to check if "being a constructor" is set before.
>From gcc-bugs-return-604340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 20:03:23 2018
Return-Path: <gcc-bugs-return-604340-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55180 invoked by alias); 10 May 2018 20:03: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 55101 invoked by uid 55); 10 May 2018 20:03:18 -0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] ARM -mbe8 behaviour doesn't match documentation
Date: Thu, 10 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: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85733-4-iK3NYW0096@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01235.txt.bz2
Content-length: 263
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
Sounds like a regression if this is the case, since bpabi.h in GCC 7 does
include march=armv8-a in BE8_LINK_SPEC.
>From gcc-bugs-return-604341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 20:24:54 2018
Return-Path: <gcc-bugs-return-604341-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115584 invoked by alias); 10 May 2018 20:24: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 115143 invoked by uid 48); 10 May 2018 20:24:21 -0000
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/70693] valgrind error in get_visual_column
Date: Thu, 10 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: c++
X-Bugzilla-Version: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: dmalcolm at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: dmalcolm 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-70693-4-uAwOt0QW7h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70693-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70693-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01236.txt.bz2
Content-length: 888
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70693
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-10
Assignee|unassigned at gcc dot gnu.org |dmalcolm at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #5 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Confirmed on trunk.
I believe it's trying to access column 8 of line 55, which I think is just 4
space characters.
(In reply to David Binderman from comment #2)
> Problem seems to have come back, somewhere between revisions 259747 and
> 259789
Probably r259768, which added some extra checking when accessing source lines.
>From gcc-bugs-return-604342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 20:34:05 2018
Return-Path: <gcc-bugs-return-604342-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7956 invoked by alias); 10 May 2018 20:34: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 7868 invoked by uid 48); 10 May 2018 20:33:59 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] New: Non-optimal determining maximum in a loop
Date: Thu, 10 May 2018 20:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01237.txt.bz2
Content-length: 3458
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
Bug ID: 85740
Summary: Non-optimal determining maximum in a loop
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: tkoenig at gcc dot gnu.org
Target Milestone: ---
There is a problem with loops determining the maximum (or minimum)
of a value. I noticed this when looking at inline code generated
by gfortran for maxloc/minloc.
Consider the two programs which select the position of a
maximum from a rather large integer array. They are identical,
except that b.c uses __builtin_expect in the inner loop:
$ cat b.c
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <x86intrin.h>
#define N (1<<28)
int foo(int *a, int n)
{
int m, nm;
int i;
m = -20000;
nm = -1;
for (i=0; i<n; i++)
{
if (__builtin_expect (a[i] > m, 0))
{
m = a[i];
nm = i;
}
}
return nm;
}
int
main(int argc, char **argv) {
unsigned long long t1, t2;
int *p = malloc(N * sizeof(int));
for (int i=0; i<N; i++)
p[i] = random();
t1 = __rdtsc();
int res = foo(p, N);
t2 = __rdtsc();
printf("%d\n", res);
printf("time used: %llu cycles\n", t2-t1);
return 0;
}
$ cat c.c
#include <stdio.h>
#include <stdlib.h>
#include <time.h>
#include <x86intrin.h>
#define N (1<<28)
int foo(int *a, int n)
{
int m, nm;
int i;
m = -20000;
nm = -1;
for (i=0; i<n; i++)
{
if (a[i] > m)
{
m = a[i];
nm = i;
}
}
return nm;
}
int
main(int argc, char **argv) {
unsigned long long t1, t2;
int *p = malloc(N * sizeof(int));
for (int i=0; i<N; i++)
p[i] = random();
t1 = __rdtsc();
int res = foo(p, N);
t2 = __rdtsc();
printf("%d\n", res);
printf("time used: %llu cycles\n", t2-t1);
return 0;
}
$ gcc -Ofast b.c && ./a.out
13068230
time used: 281813216 cycles
$ gcc -Ofast c.c && ./a.out
13068230
time used: 492848802 cycles
So, the program using the __builtin_expect is faster by
a factor of around 1.75, quite significant.
The problem is obvious from the assembly. The inner loop has, for
the version without the hint,
.L6:
movq %rcx, %rdx
.L4:
movl (%rdi,%rdx,4), %ecx
cmpl %ecx, %esi
jge .L3
movl %edx, %eax
movl %ecx, %esi
.L3:
leaq 1(%rdx), %rcx
cmpq %rdx, %r8
jne .L6
.L1:
ret
so what is likely to be the most common case (not finding a higher
maximum) leads to a jump over two instrucitons. On the other hand,
the assembly for the version with the hint is
.L6:
movq %rcx, %rdx
.L4:
movl (%rdi,%rdx,4), %ecx
cmpl %ecx, %esi
jl .L8
.L3:
leaq 1(%rdx), %rcx
cmpq %rdx, %r8
jne .L6
.L1:
ret
.p2align 4,,10
.p2align 3
.L8:
movl %edx, %eax
movl %ecx, %esi
jmp .L3
so the control flow is not interrupted in the most common case.
The version with the hint becomes even faster when unrolling
the loop:
$ gcc -Ofast -funroll-loops b.c && ./a.out
13068230
time used: 254444202 cycles
another speed gain of around 15%.
This is for an AMD Ryzen 7 1700X.
>From gcc-bugs-return-604343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 20:57:39 2018
Return-Path: <gcc-bugs-return-604343-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41585 invoked by alias); 10 May 2018 20:57: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 41516 invoked by uid 48); 10 May 2018 20:57:33 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85598] [7/8/9 Regression] Incorrect warning only at -O2 and -O3
Date: Thu, 10 May 2018 20:57:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: 7.3.0
X-Bugzilla-Keywords: diagnostic
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor 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:
Message-ID: <bug-85598-4-c7LvzYlHgL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85598-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85598-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01238.txt.bz2
Content-length: 457
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85598
--- Comment #2 from Martin Sebor <msebor at gcc dot gnu.org> ---
The problem is that the warning pass sees x as having the range of [0, 256]
rather than [0, 255]. The incorrect range can also be seen in EVRP. There is
no warning at -O1 because the range determined at that level is that of
unsigned int which is considered to be the same as unknown. The warning does
not trigger for such ranges.
>From gcc-bugs-return-604344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 21:04:06 2018
Return-Path: <gcc-bugs-return-604344-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 60723 invoked by alias); 10 May 2018 21: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 60612 invoked by uid 48); 10 May 2018 21:03:58 -0000
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85741] New: [meta-bug] bogus/missing -Wformat-overflow
Date: Thu, 10 May 2018 21:04:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: msebor at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01239.txt.bz2
Content-length: 509
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85741
Bug ID: 85741
Summary: [meta-bug] bogus/missing -Wformat-overflow
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: msebor at gcc dot gnu.org
Target Milestone: ---
A meta-bug to group -Wstringop-overflow false positives and false negatives.
>From gcc-bugs-return-604345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 21:25:55 2018
Return-Path: <gcc-bugs-return-604345-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 125280 invoked by alias); 10 May 2018 21:25: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 123342 invoked by uid 48); 10 May 2018 21:25:51 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Thu, 10 May 2018 21:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85740-4-MY3L6RR05g@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01240.txt.bz2
Content-length: 336
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
These functions are not functional equivalent.
In the b.c, it records the max location but it is the last element which
contains that value. While in c.c, the first element which contains the value
is recorded.
>From gcc-bugs-return-604346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 21:27:26 2018
Return-Path: <gcc-bugs-return-604346-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 8659 invoked by alias); 10 May 2018 21:27:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 8038 invoked by uid 48); 10 May 2018 21:27:20 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Thu, 10 May 2018 21:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85740-4-dXPJs7dsmI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01241.txt.bz2
Content-length: 276
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> These functions are not functional equivalent.
To get them equivalent, you either need to use >= or <=.
>From gcc-bugs-return-604347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 21:47:36 2018
Return-Path: <gcc-bugs-return-604347-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 43170 invoked by alias); 10 May 2018 21:47:36 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 43042 invoked by uid 48); 10 May 2018 21:47:32 -0000
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85741] [meta-bug] bogus/missing -Wformat-overflow
Date: Thu, 10 May 2018 21:47:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: meta-bug
X-Bugzilla-Severity: normal
X-Bugzilla-Who: egallager at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85741-4-V3bXhk1Wu7@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85741-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85741-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01242.txt.bz2
Content-length: 598
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85741
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-10
CC| |egallager at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Eric Gallager <egallager at gcc dot gnu.org> ---
Confirming that this is a useful meta-bug.
>From gcc-bugs-return-604348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 22:43:36 2018
Return-Path: <gcc-bugs-return-604348-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94007 invoked by alias); 10 May 2018 22: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 93916 invoked by uid 55); 10 May 2018 22:43:32 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70870] Segmentation violation in gfc_assign_data_value
Date: Thu, 10 May 2018 22: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: 6.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-70870-4-brMT5WHBvg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70870-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01243.txt.bz2
Content-length: 723
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70870
--- Comment #10 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu May 10 22:43:00 2018
New Revision: 260138
URL: https://gcc.gnu.org/viewcvs?rev=260138&root=gcc&view=rev
Log:
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
* data.c (gfc_assign_data_value): Check that a data object does
not also have default initialization.
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/70870
* gfortran.dg/pr70870_1.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr70870_1.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/data.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 22:46:25 2018
Return-Path: <gcc-bugs-return-604349-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 97731 invoked by alias); 10 May 2018 22:46:24 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 97439 invoked by uid 55); 10 May 2018 22:46:20 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85521] [8/9 Regression] ICE in gfc_resolve_character_array_constructor, at fortran/array.c:2049
Date: Thu, 10 May 2018 22: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: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: kargl at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85521-4-3LnLalpVX2@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85521-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01244.txt.bz2
Content-length: 849
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85521
--- Comment #6 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu May 10 22:45:38 2018
New Revision: 260139
URL: https://gcc.gnu.org/viewcvs?rev=260139&root=gcc&view=rev
Log:
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
* array.c (gfc_resolve_character_array_constructor): Substrings
with upper bound smaller than lower bound are zero length strings.
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85521
* gfortran.dg/pr85521_1.f90: New test.
* gfortran.dg/pr85521_2.f90: New test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr85521_1.f90
trunk/gcc/testsuite/gfortran.dg/pr85521_2.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/array.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 22:50:20 2018
Return-Path: <gcc-bugs-return-604350-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 103654 invoked by alias); 10 May 2018 22:50: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 103612 invoked by uid 55); 10 May 2018 22:50:16 -0000
From: "kargl at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85687] ICE in gfc_sym_identifier, at fortran/trans-decl.c:351
Date: Thu, 10 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: fortran
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: kargl at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85687-4-JxM5QyVjPZ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01245.txt.bz2
Content-length: 681
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85687
--- Comment #3 from kargl at gcc dot gnu.org ---
Author: kargl
Date: Thu May 10 22:49:44 2018
New Revision: 260141
URL: https://gcc.gnu.org/viewcvs?rev=260141&root=gcc&view=rev
Log:
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
* check.c (gfc_check_rank): Check that the argument is a data object.
2018-05-10 Steven G. Kargl <kargl@gcc.gnu.org>
PR fortran/85687
* gfortran.dg/pr85687.f90: new test.
Added:
trunk/gcc/testsuite/gfortran.dg/pr85687.f90
Modified:
trunk/gcc/fortran/ChangeLog
trunk/gcc/fortran/check.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 22:54:22 2018
Return-Path: <gcc-bugs-return-604351-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 106159 invoked by alias); 10 May 2018 22:54: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 106079 invoked by uid 48); 10 May 2018 22:54:18 -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: Thu, 10 May 2018 22: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: 7.2.1
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: mpolacek at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85363-4-EfdB7ZG8JD@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/msg01246.txt.bz2
Content-length: 533
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85363
--- Comment #6 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
P::P () is marked as TREE_NOTHROW because when we're processing X::X ((struct X
*) <<< Unknown tree: void_cst >>>, 20) (which can throw) in
set_flags_from_callee, cfun is null in this case, so we don't mark P::P() as
can_throw.
If struct P were
struct P {
P () : x {5} {}
X x;
};
it would work as expected, because when processing X::X(), cfun would be
non-null, so it would be marked as can_throw.
>From gcc-bugs-return-604352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 23:01:46 2018
Return-Path: <gcc-bugs-return-604352-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 114944 invoked by alias); 10 May 2018 23:01: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 114906 invoked by uid 48); 10 May 2018 23:01:40 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/85732] use_facet<moneypunct<char, true>>(mylocale) retrieving wrong locale information
Date: Thu, 10 May 2018 23:01:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 6.4.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: MOVED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85732-4-GuJrmwe75K@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85732-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85732-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01247.txt.bz2
Content-length: 564
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85732
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
I don't think we can do anything to fix this in libstdc++ so I've reported it
to glibc:
https://sourceware.org/bugzilla/show_bug.cgi?id=23164
>From gcc-bugs-return-604353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 23:39:35 2018
Return-Path: <gcc-bugs-return-604353-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5184 invoked by alias); 10 May 2018 23:39: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 5150 invoked by uid 48); 10 May 2018 23:39:31 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Thu, 10 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: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: dominiq at lps dot ens.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:
Message-ID: <bug-85740-4-XNuUFGr4ht@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01248.txt.bz2
Content-length: 795
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #3 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> These functions are not functional equivalent.
>
> In the b.c, it records the max location but it is the last element which
> contains that value. While in c.c, the first element which contains
> the value is recorded.
> (In reply to Andrew Pinski from comment #1)
> > These functions are not functional equivalent.
>
> To get them equivalent, you either need to use >= or <=.
Could you please elaborate?
The results seem to depend on the processor. On my Core i7 I get around
430000000 cycles for both tests and -O2 or above, except -Ofast -funroll-loops
which gives around 260000000 cycles for the first test and 580000000 cycles for
the second one.
>From gcc-bugs-return-604354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Thu May 10 23:42:03 2018
Return-Path: <gcc-bugs-return-604354-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 7526 invoked by alias); 10 May 2018 23:42: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 7450 invoked by uid 48); 10 May 2018 23:41:59 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Thu, 10 May 2018 23:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85740-4-g7R4wB8fMA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01249.txt.bz2
Content-length: 170
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(a<b) == 0 is not the same as (b > a) != 0
>From gcc-bugs-return-604355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 01:27:25 2018
Return-Path: <gcc-bugs-return-604355-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 96695 invoked by alias); 11 May 2018 01:27: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 96674 invoked by uid 48); 11 May 2018 01:27:21 -0000
From: "cesar at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85742] New: sizeof allocatable arrays returning wrong value
Date: Fri, 11 May 2018 01:27:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
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: unassigned 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-85742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01250.txt.bz2
Content-length: 1073
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85742
Bug ID: 85742
Summary: sizeof allocatable arrays returning wrong value
Product: gcc
Version: 8.0.1
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
Assignee: unassigned at gcc dot gnu.org
Reporter: cesar at gcc dot gnu.org
Target Milestone: ---
Created attachment 44113
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44113&action=edit
sizeof test
As of trunk revision 257065, the sizeof function is returning incorrect results
on assume-sized allocated arrays and scalars. See the attached test case for
more details.
I hit this problem while rebasing openacc-gcc-7-branch Fortran changes to GCC
8. Basically, OpenACC provides a Fortran module which contains an
acc_is_present routine, which passes the sizeof an array along with the pointer
to the array to the runtime to determine if that array is resident on the
device. However, now sizeof is returning bogus results.
>From gcc-bugs-return-604356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 01:44:42 2018
Return-Path: <gcc-bugs-return-604356-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118844 invoked by alias); 11 May 2018 01:44:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118767 invoked by uid 55); 11 May 2018 01:44:38 -0000
From: "emsr at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/83140] assoc_legendre returns negated value when m is odd
Date: Fri, 11 May 2018 01:44:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libstdc++
X-Bugzilla-Version: 7.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: emsr at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: emsr at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83140-4-BkS9b8lLaG@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83140-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83140-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01251.txt.bz2
Content-length: 784
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83140
--- Comment #5 from emsr at gcc dot gnu.org ---
Author: emsr
Date: Fri May 11 01:44:05 2018
New Revision: 260149
URL: https://gcc.gnu.org/viewcvs?rev=260149&root=gcc&view=rev
Log:
correct changelog!
2018-05-10 Edward Smith-Rowland <3dw4rd@verizon.net>
PR libstdc++/83140 - assoc_legendre returns negated value when m is odd
* include/tr1/legendre_function.tcc (__assoc_legendre_p): Add __phase
argument defaulted to +1. Doxy comments on same.
* testsuite/special_functions/02_assoc_legendre/
check_value.cc: Regen.
* testsuite/tr1/5_numerical_facilities/special_functions/
02_assoc_legendre/check_value.cc: Regen.
Modified:
trunk/libstdc++-v3/ChangeLog
>From gcc-bugs-return-604357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 03:31:08 2018
Return-Path: <gcc-bugs-return-604357-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 5504 invoked by alias); 11 May 2018 03:31: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 5418 invoked by uid 48); 11 May 2018 03:30:57 -0000
From: "gufideg at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85743] New: Cannot call template member function inside a variadic lambda unless specifying `this`
Date: Fri, 11 May 2018 03: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.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-85743-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01252.txt.bz2
Content-length: 1880
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85743
Bug ID: 85743
Summary: Cannot call template member function inside a variadic
lambda unless specifying `this`
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: ---
When using a particular pattern to expand a variadic template inside a member
function, `this->` need to be specified before calling other member functions.
Here is the most reduced repro I can come with at the moment:
#include <type_traits>
#include <tuple>
template<typename>
struct tuple_sequence;
template<typename I, I... S>
struct tuple_sequence<std::integer_sequence<I, S...>> {
using type = std::tuple<std::integral_constant<I, S>...>;
};
template<typename... Types, typename F>
constexpr auto apply_sequence_for(F function) -> decltype(auto) {
return std::apply(function, typename
tuple_sequence<std::index_sequence_for<Types...>>::type{});
}
template<typename... Ts>
struct Foo {
template<typename T, typename...>
constexpr void boom(int i) const {}
constexpr auto foo(std::array<int, sizeof...(Ts)> data) const {
apply_sequence_for<Ts...>([this, &data](auto... s) {
(boom<Ts>(data[s]), ...);
});
}
};
int main() {
Foo<int, float, char> f;
f.foo({0, 1, 2});
}
Notice the particular expansion pattern `boom<Ts>(data[s])`. The bug won't
trigger if the pattern is replaced by `boom<Ts...>(data[s])` or even
`boom<Ts>(data[0])`.
This code compiles under Clang 6.0.0
Live example: https://godbolt.org/g/n6wMUS
>From gcc-bugs-return-604358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 05:05:29 2018
Return-Path: <gcc-bugs-return-604358-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 120417 invoked by alias); 11 May 2018 05:05: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 120360 invoked by uid 48); 11 May 2018 05:05:24 -0000
From: "cerlane at nscc dot sg" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85744] New: Returning INT_FAST64_MIN become zero
Date: Fri, 11 May 2018 05:05:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 4.8.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cerlane at nscc dot sg
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned 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-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01253.txt.bz2
Content-length: 624
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
Bug ID: 85744
Summary: Returning INT_FAST64_MIN become zero
Product: gcc
Version: 4.8.5
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: cerlane at nscc dot sg
Target Milestone: ---
When returning the value 0x8000000000000000LL from a function (return type
int_fast64_t), the value becomes zero (0x0).
Is this a feature to guard against underflowing? If so, how can I return
0x8000000000000000LL?
>From gcc-bugs-return-604359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 05:10:08 2018
Return-Path: <gcc-bugs-return-604359-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12447 invoked by alias); 11 May 2018 05:10: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 12364 invoked by uid 48); 11 May 2018 05:10:04 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 May 2018 05: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: 4.8.5
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-85744-4-knT3hNDnlN@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01254.txt.bz2
Content-length: 147
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Try 0x8000000000000000ULL
>From gcc-bugs-return-604360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 05:17:50 2018
Return-Path: <gcc-bugs-return-604360-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17964 invoked by alias); 11 May 2018 05:17: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 17886 invoked by uid 48); 11 May 2018 05:17:46 -0000
From: "cerlane at nscc dot sg" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 May 2018 05: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: 4.8.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cerlane at nscc dot sg
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85744-4-fEy3cyxa90@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01255.txt.bz2
Content-length: 224
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
--- Comment #2 from cerlane <cerlane at nscc dot sg> ---
(In reply to Andrew Pinski from comment #1)
> Try 0x8000000000000000ULL
No unfortunately, it still returns 0x0.
>From gcc-bugs-return-604361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 05:20:19 2018
Return-Path: <gcc-bugs-return-604361-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 26007 invoked by alias); 11 May 2018 05:20: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 25972 invoked by uid 48); 11 May 2018 05:20:15 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 May 2018 05:20:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 4.8.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: component
Message-ID: <bug-85744-4-xTLGmevPHh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01256.txt.bz2
Content-length: 409
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|c |target
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Can you provide the preprocessed source then?
>From gcc-bugs-return-604362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 06:30:00 2018
Return-Path: <gcc-bugs-return-604362-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19263 invoked by alias); 11 May 2018 06:30: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 19129 invoked by uid 48); 11 May 2018 06:29:44 -0000
From: "bernd.edlinger at hotmail dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/85745] New: variable with asm register assignment allocated in wrong reg
Date: Fri, 11 May 2018 06:30: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.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: bernd.edlinger at hotmail dot de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created
Message-ID: <bug-85745-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01257.txt.bz2
Content-length: 2622
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85745
Bug ID: 85745
Summary: variable with asm register assignment allocated in
wrong reg
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: rtl-optimization
Assignee: unassigned at gcc dot gnu.org
Reporter: bernd.edlinger at hotmail dot de
Target Milestone: ---
Created attachment 44114
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44114&action=edit
reduced test case
This prevents linux v4.7 and before to be built with gcc-8.1.0 on armv7
targets.
$ arm-linux-gnueabihf-gcc -v
Using built-in specs.
COLLECT_GCC=arm-linux-gnueabihf-gcc
COLLECT_LTO_WRAPPER=/home/ed/gnu/arm-linux-gnueabihf-linux64/libexec/gcc/arm-linux-gnueabihf/8.1.0/lto-wrapper
Target: arm-linux-gnueabihf
Configured with: ../gcc-8.1.0/configure
--prefix=/home/ed/gnu/arm-linux-gnueabihf-linux64 --target=arm-linux-gnueabihf
--enable-languages=all --with-arch=armv7-a --with-tune=cortex-a9
--with-fpu=vfpv3-d16 --with-float=hard
Thread model: posix
gcc version 8.1.0 (GCC)
$ arm-linux-gnueabihf-gcc -save-temps -Os -c test.c
test.s: Assembler messages:
test.s:39: Error: .err encountered
in test.s we see, that __r2 is allocated in r3 but that is unexpected,
it should have been r2:
sys_oabi_sendmsg:
@ args = 0, pretend = 0, frame = 0
@ frame_needed = 0, uses_anonymous_args = 0
cmp r1, #0
bxeq lr
uxth r2, r2
cmp r2, #1
cmpeq r0, #0
bxne lr
mov r3, #0
str lr, [sp, #-4]!
ldr r3, [r3]
mov r0, r1
sub r1, r3, #1
mov r3, #110
.syntax divided
@ 37 "000.c" 1
.ifnc r0,r0; .ifnc r0r0,fpr11; .ifnc r0r0,r11fp; .ifnc r0r0,ipr12;
.ifnc r0r0,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r3,r2; .ifnc r3r2,fpr11; .ifnc r3r2,r11fp; .ifnc r3r2,ipr12;
.ifnc r3r2,r12ip; .err; .endif; .endif; .endif; .endif; .endif
.ifnc r1,r1; .ifnc r1r1,fpr11; .ifnc r1r1,r11fp; .ifnc r1r1,ipr12;
.ifnc r1r1,r12ip; .err; .endif; .endif; .endif; .endif; .endif
bl __put_user_4
@ 0 "" 2
.arm
.syntax unified
ldr pc, [sp], #4
The after v4.8 this macro was a bit simplified, and causes less register
pressure, but I think it works only by chance.
I am not sure if that is a wrong expectation or a compiler bug.
It would be fixed when __r2 is declared volatile for instance.
>From gcc-bugs-return-604363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 06:39:13 2018
Return-Path: <gcc-bugs-return-604363-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 107268 invoked by alias); 11 May 2018 06:39: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 107054 invoked by uid 48); 11 May 2018 06:39:05 -0000
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Fri, 11 May 2018 06:39:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: tkoenig at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85740-4-bRqS2Vem4E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01258.txt.bz2
Content-length: 846
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> These functions are not functional equivalent.
>
> In the b.c, it records the max location but it is the last element which
> contains that value. While in c.c, the first element which contains the
> value is recorded.
I do not understand.
The only difference between the files is
$ diff -u -b b.c c.c
--- b.c 2018-05-10 22:22:06.276904322 +0200
+++ c.c 2018-05-10 22:21:50.028801008 +0200
@@ -14,7 +14,7 @@
nm = -1;
for (i=0; i<n; i++)
{
- if (__builtin_expect (a[i] > m, 0))
+ if (a[i] > m)
{
m = a[i];
nm = i;
Does this change the semantics of the comparison? If it does, it
would be a bug in __builtin_expect.
>From gcc-bugs-return-604365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 06:48:57 2018
Return-Path: <gcc-bugs-return-604365-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115978 invoked by alias); 11 May 2018 06:48: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 115753 invoked by uid 48); 11 May 2018 06:48:40 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23094] store ccp, or store copy prop misses an optimization
Date: Fri, 11 May 2018 06:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.1.0
X-Bugzilla-Keywords: alias, missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: rguenth at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-23094-4-vgixrM8JOV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-23094-4@http.gcc.gnu.org/bugzilla/>
References: <bug-23094-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01260.txt.bz2
Content-length: 445
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=23094
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |herring at lanl dot gov
--- Comment #20 from Richard Biener <rguenth at gcc dot gnu.org> ---
*** Bug 80617 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 06:48:57 2018
Return-Path: <gcc-bugs-return-604364-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 115964 invoked by alias); 11 May 2018 06: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 115718 invoked by uid 48); 11 May 2018 06:48:39 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80617] [missed optimization] Storing constant in two possibly-aliased locations
Date: Fri, 11 May 2018 06:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenth 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-80617-4-BYbj9JGdN6@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01259.txt.bz2
Content-length: 517
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80617
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #11 from Richard Biener <rguenth at gcc dot gnu.org> ---
Dup of PR23094 (and fixed).
*** This bug has been marked as a duplicate of bug 23094 ***
>From gcc-bugs-return-604366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 06:51:06 2018
Return-Path: <gcc-bugs-return-604366-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 118531 invoked by alias); 11 May 2018 06:51:06 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 118495 invoked by uid 48); 11 May 2018 06:51:01 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Fri, 11 May 2018 06:51:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords:
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85740-4-I0E05v6T5w@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01261.txt.bz2
Content-length: 1443
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Thomas Koenig from comment #5)
> (In reply to Andrew Pinski from comment #1)
> > These functions are not functional equivalent.
> >
> > In the b.c, it records the max location but it is the last element which
> > contains that value. While in c.c, the first element which contains the
> > value is recorded.
>
> I do not understand.
>
> The only difference between the files is
>
> $ diff -u -b b.c c.c
> --- b.c 2018-05-10 22:22:06.276904322 +0200
> +++ c.c 2018-05-10 22:21:50.028801008 +0200
> @@ -14,7 +14,7 @@
> nm = -1;
> for (i=0; i<n; i++)
> {
> - if (__builtin_expect (a[i] > m, 0))
> + if (a[i] > m)
> {
> m = a[i];
> nm = i;
>
> Does this change the semantics of the comparison? If it does, it
> would be a bug in __builtin_expect.
The documentation is hard to understand but you are correct that it just says
we are expecting the value of the comparison to be false.
Anyways the problem here is a bit more complex than just marking the edge as
expect.
For aarch64 we produce csel (which is basically cmov) for both loops:
.L11:
ldr w4, [x5, x2, lsl 2]
cmp w3, w4
csel w0, w0, w2, ge
add x2, x2, 1
csel w3, w3, w4, ge
cmp w1, w2
bgt .L11
>From gcc-bugs-return-604367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:03:31 2018
Return-Path: <gcc-bugs-return-604367-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 24084 invoked by alias); 11 May 2018 07:03: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 24018 invoked by uid 48); 11 May 2018 07:03:26 -0000
From: "cerlane at nscc dot sg" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 May 2018 07: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: 4.8.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cerlane at nscc dot sg
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-85744-4-4l3huIAx0h@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01262.txt.bz2
Content-length: 945
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
cerlane <cerlane at nscc dot sg> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |INVALID
--- Comment #4 from cerlane <cerlane at nscc dot sg> ---
(In reply to Andrew Pinski from comment #3)
> Can you provide the preprocessed source then?
To provide the preprocessed source, I extracted the function and call it
directly from the same file. It then returns the correct value. However, when I
called the "actual" function, which is in an archive, I reproduce the error.
This means it is not a gcc standard error, but a compilation or some other
issues. I am unsure if this is the correct place to continue the discussion.
Thanks very much for your very quick response in any case.
>From gcc-bugs-return-604368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:04:42 2018
Return-Path: <gcc-bugs-return-604368-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25572 invoked by alias); 11 May 2018 07:04:42 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 25466 invoked by uid 48); 11 May 2018 07:04:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/19808] miss a warning about uninitialized member usage in member initializer list in constructor
Date: Fri, 11 May 2018 07: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: 3.4.4
X-Bugzilla-Keywords: diagnostic, easyhack, patch
X-Bugzilla-Severity: enhancement
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: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-19808-4-Lrrvswg3cl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-19808-4@http.gcc.gnu.org/bugzilla/>
References: <bug-19808-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01263.txt.bz2
Content-length: 2773
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=19808
--- Comment #44 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Jason Merrill from comment #40)
> (In reply to Richard Biener from comment #39)
> > so - how do I make X::X used and thus prevail? It looks like it doesn't
> > really exist
>
> True, for C++14 and up, "X x{};" does aggregate initialization rather than
> calling the constructor. We ought to warn about this at function scope, but
> we clear the object first, so it isn't actually uninitialized.
>
> As you found, removing the {} makes it use the constructor.
>
> > OK, doing void foo() { X x; } shows
> >
> > X::X (struct X * const this)
> > {
> > _1 = this->x2;
> > this->x1 = _1;
> > this->x2 = 0;
> > }
> >
> > foo ()
> > {
> > struct X x;
> >
> > try
> > {
> > X::X (&x);
> > }
> > finally
> > {
> > x = {CLOBBER};
> > }
> > }
> >
> > warning would need inlining of the constructor which only happens after
> > the early warning pass, the late one isn't run at -O0 and with optimization
> > everything of course vanishes.
>
> I was wondering about a maybe-uninitialized warning for the constructor
> without considering where it's called from; even if a particular object is
> zero-initialized when we enter the implicit constructor, the constructor
> shouldn't rely on that. Basically, warn as if there were a clobber, without
> there actually being one.
Interesting suggestion but that's IMHO a bit too much information from
the outside to pack into the middle-end code. That we're dealing with
accesses to *this and that we are inside a constructor. You'd need to
add that here, tree-ssa-uninit.c:warn_uninitialized_vars
/* Do not warn if it can be initialized outside this function.
If we did not reach function entry then we found killing
clobbers on all paths to entry. */
if (fentry_reached
/* ??? We'd like to use ref_may_alias_global_p but that
excludes global readonly memory and thus we get bougs
warnings from p = cond ? "a" : "b" for example. */
&& (!VAR_P (base)
|| is_global_var (base)))
continue;
given we have to constrain this to must-aliases of *this the easiest
check would be sth like
&& (!eligible-constructor (cfun)
|| TREE_CODE (base) != MEM_REF
|| TREE_OPERAND (base, 0) != default-def-of-this-parm))
and then elide the warning to maybe-uninit. I guess we now have a flag
whether a function is a constructor and we also can get at the this
parm-decl so in theory "enhancing" the warning this way would be possible.
>From gcc-bugs-return-604369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:06:57 2018
Return-Path: <gcc-bugs-return-604369-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 55103 invoked by alias); 11 May 2018 07:06: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 55072 invoked by uid 48); 11 May 2018 07:06:52 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 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: target
X-Bugzilla-Version: 4.8.5
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 resolution everconfirmed
Message-ID: <bug-85744-4-RhXrCDKOc5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01264.txt.bz2
Content-length: 832
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |WAITING
Last reconfirmed| |2018-05-11
Resolution|INVALID |---
Ever confirmed|0 |1
--- Comment #5 from Jonathan Wakely <redi at gcc dot gnu.org> ---
You should have read https://gcc.gnu.org/bugs/ which explains what we need for
a valid bug report, and would have done that before reporting it.
You probably forgot to declare the function in the calling code so the compiler
assumed it returned int, and only used the low 32 bits, which are all zero.
>From gcc-bugs-return-604370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:07:27 2018
Return-Path: <gcc-bugs-return-604370-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56018 invoked by alias); 11 May 2018 07:07: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 55982 invoked by uid 48); 11 May 2018 07:07:23 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 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: target
X-Bugzilla-Version: 4.8.5
X-Bugzilla-Keywords:
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-85744-4-LjqzDw9Iq9@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01265.txt.bz2
Content-length: 475
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |RESOLVED
Resolution|--- |INVALID
--- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Sorry, I didn't mean to change the status, re-closing.
>From gcc-bugs-return-604371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:10:14 2018
Return-Path: <gcc-bugs-return-604371-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66234 invoked by alias); 11 May 2018 07:10: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 64637 invoked by uid 48); 11 May 2018 07:10:10 -0000
From: "cerlane at nscc dot sg" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85744] Returning INT_FAST64_MIN become zero
Date: Fri, 11 May 2018 07: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: 4.8.5
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cerlane at nscc dot sg
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-85744-4-vuRv0Ap3R3@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85744-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01266.txt.bz2
Content-length: 826
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85744
--- Comment #7 from cerlane <cerlane at nscc dot sg> ---
(In reply to Jonathan Wakely from comment #5)
> You should have read https://gcc.gnu.org/bugs/ which explains what we need
> for a valid bug report, and would have done that before reporting it.
>
> You probably forgot to declare the function in the calling code so the
> compiler assumed it returned int, and only used the low 32 bits, which are
> all zero.
No that is not true. I have the function declared in the header file. It is
included everywhere.
The problem is harder to debug. For all other #values, they work correctly. I
still can't figure out the issue. I tested every combination including compiler
flags before my last reply. If it turns out to be a compiler issue, I will
resubmit. Thanks.
>From gcc-bugs-return-604372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:16:41 2018
Return-Path: <gcc-bugs-return-604372-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92261 invoked by alias); 11 May 2018 07:16:40 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 92130 invoked by uid 48); 11 May 2018 07:16:36 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85715] internal compiler error: in reshape_init_class ( in anonymous union )
Date: Fri, 11 May 2018 07: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: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth 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: 7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85715-4-cgr4ARugzH@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85715-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85715-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01267.txt.bz2
Content-length: 506
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85715
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Thus a duplicate.
*** This bug has been marked as a duplicate of bug 84874 ***
>From gcc-bugs-return-604373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:16:41 2018
Return-Path: <gcc-bugs-return-604373-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 92407 invoked by alias); 11 May 2018 07: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 92179 invoked by uid 48); 11 May 2018 07:16:37 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/84874] [6/7 Regression] internal compiler error: in reshape_init_class, at cp/decl.c:5800
Date: Fri, 11 May 2018 07: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: 7.3.1
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-84874-4-Bflv7dNKfa@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-84874-4@http.gcc.gnu.org/bugzilla/>
References: <bug-84874-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01268.txt.bz2
Content-length: 454
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84874
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |daffra.claudio at gmail dot com
--- Comment #8 from Richard Biener <rguenth at gcc dot gnu.org> ---
*** Bug 85715 has been marked as a duplicate of this bug. ***
>From gcc-bugs-return-604374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:18:20 2018
Return-Path: <gcc-bugs-return-604374-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 94622 invoked by alias); 11 May 2018 07: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 94425 invoked by uid 48); 11 May 2018 07:18:16 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85717] anonymous union in initializer list : do not handle the types correctly
Date: Fri, 11 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: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85717-4-eXsyju17Rn@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01269.txt.bz2
Content-length: 223
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85717
--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Given that integer literals are convertible to FP (or even are also FP
literals) what do you expect?
>From gcc-bugs-return-604375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:25:17 2018
Return-Path: <gcc-bugs-return-604375-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 2150 invoked by alias); 11 May 2018 07:25: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 2056 invoked by uid 48); 11 May 2018 07:25:12 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85720] bad codegen for looped assignment of primitives at -O2
Date: Fri, 11 May 2018 07:25:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords cc component
Message-ID: <bug-85720-4-ZMAhv5tu0E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85720-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85720-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01270.txt.bz2
Content-length: 1719
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85720
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
CC| |amker at gcc dot gnu.org
Component|middle-end |tree-optimization
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
(In reply to Mathias Stearn from comment #4)
> (In reply to Marc Glisse from comment #3)
> > Again, you are ignoring aliasing issues (just like in your other PR the
> > function copy isn't equivalent to memmove). Does adding __restrict change
> > the result? Also, B[i]=B[i]+1 doesn't look like a memset...
>
> Sorry, I typoed. It was supposed to be B[i] = A[i] + 1. That still does
> basically the same thing though: https://godbolt.org/g/dtmU5t. Good point
> about aliasing though. I guess the right code gen in that case would
> actually be something that detected the overlap and did the right calls to
> memset to only set each byte once. Or just do the simple thing:
>
> if (b > a && b < a + n) {
> memset(b, 1, n);
> memset(a, 0, n);
> } else {
> memset(a, 0, n);
> memset(b, 1, n);
> }
>
> Yes, __restrict helps, but that isn't part of standard c++, and it seems
> like it never will be.
GCC supports it since forever... but yes, currently loop distribution
doesn't consider runtime aliasing in this case (it can do it now but
is keyed to vectorization). It also doesn't have a way to distinguish
forward vs. backward dependence and split the case like you propose.
>From gcc-bugs-return-604376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:29:26 2018
Return-Path: <gcc-bugs-return-604376-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16858 invoked by alias); 11 May 2018 07:29:26 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16495 invoked by uid 48); 11 May 2018 07:29:21 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85721] bad codegen for looped copy of primitives at -O2 and -O3 (differently bad)
Date: Fri, 11 May 2018 07: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: 8.1.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc component everconfirmed
Message-ID: <bug-85721-4-PyHP8iGip5@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85721-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85721-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01271.txt.bz2
Content-length: 716
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85721
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
CC| |amker at gcc dot gnu.org
Component|middle-end |tree-optimization
Ever confirmed|0 |1
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
Indeed loop distribution doesn't consider to alias-version the loop this way
for pattern recognition.
>From gcc-bugs-return-604377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:34:00 2018
Return-Path: <gcc-bugs-return-604377-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56280 invoked by alias); 11 May 2018 07:34:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 56192 invoked by uid 48); 11 May 2018 07:33:55 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/85722] testsuite failure in libffi
Date: Fri, 11 May 2018 07:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85722-4-bvj2BlZayc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01272.txt.bz2
Content-length: 363
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85722
--- Comment #5 from Richard Biener <rguenth at gcc dot gnu.org> ---
You are building gmp/mpfr in-tree - what versions? __i386__ isn't defined on
x86_64 so the issue looks in whatever does those "testcases". The log isn't
helpful as it seems to be produced with -jN and isn't part of the libffi
testsuite.
>From gcc-bugs-return-604378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:36:26 2018
Return-Path: <gcc-bugs-return-604378-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 59584 invoked by alias); 11 May 2018 07:36: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 59382 invoked by uid 48); 11 May 2018 07:36:13 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85724] strspn of one-element arrays can be assumed to return zero
Date: Fri, 11 May 2018 07:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 8.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-85724-4-5TsRJa8QVe@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85724-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85724-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01273.txt.bz2
Content-length: 484
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85724
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-604380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:38:28 2018
Return-Path: <gcc-bugs-return-604380-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 62190 invoked by alias); 11 May 2018 07:38: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 62103 invoked by uid 48); 11 May 2018 07:38:24 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85725] strchr and strstr of a one-element array with a non-empty string can be assumed to return null
Date: Fri, 11 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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85725-4-wBWnQlKxqU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01275.txt.bz2
Content-length: 267
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85725
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
doesn't strchr (a, '1') return a if a[0] == '1'? You seem to read
"in the string s" as imposing s to be properly null-terminated. I don't.
>From gcc-bugs-return-604379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:38:14 2018
Return-Path: <gcc-bugs-return-604379-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 61447 invoked by alias); 11 May 2018 07:38: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 61372 invoked by uid 55); 11 May 2018 07:38:09 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/85556] attribute no_sanitize does not accept multiple options as documented
Date: Fri, 11 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: sanitizer
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: documentation, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85556-4-ezv43ocKTj@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85556-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85556-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01274.txt.bz2
Content-length: 1005
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85556
--- Comment #3 from Martin Liška <marxin at gcc dot gnu.org> ---
Author: marxin
Date: Fri May 11 07:37:35 2018
New Revision: 260154
URL: https://gcc.gnu.org/viewcvs?rev=260154&root=gcc&view=rev
Log:
Support LLVM style of no_sanitize attribute (PR sanitizer/85556).
2018-05-11 Martin Liska <mliska@suse.cz>
PR sanitizer/85556
* doc/extend.texi: Document LLVM style format for no_sanitize
attribute.
2018-05-11 Martin Liska <mliska@suse.cz>
PR sanitizer/85556
* c-attribs.c (handle_no_sanitize_attribute): Iterate all
TREE_LIST values.
2018-05-11 Martin Liska <mliska@suse.cz>
PR sanitizer/85556
* c-c++-common/ubsan/attrib-6.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/ubsan/attrib-6.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-attribs.c
trunk/gcc/doc/extend.texi
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:39:26 2018
Return-Path: <gcc-bugs-return-604381-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 63670 invoked by alias); 11 May 2018 07:39: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 63576 invoked by uid 55); 11 May 2018 07:39:21 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85692] Two source permute not used for vector initialization
Date: Fri, 11 May 2018 07: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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85692-4-8oCInPDitk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01276.txt.bz2
Content-length: 603
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85692
--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri May 11 07:38:49 2018
New Revision: 260155
URL: https://gcc.gnu.org/viewcvs?rev=260155&root=gcc&view=rev
Log:
PR tree-optimization/85692
* tree-ssa-forwprop.c (simplify_vector_constructor): Try two
source permute as well.
* gcc.target/i386/pr85692.c: New test.
Added:
trunk/gcc/testsuite/gcc.target/i386/pr85692.c
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/tree-ssa-forwprop.c
>From gcc-bugs-return-604382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:41:39 2018
Return-Path: <gcc-bugs-return-604382-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65597 invoked by alias); 11 May 2018 07:41: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 65517 invoked by uid 48); 11 May 2018 07:41:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85726] [6/7/8/9 Regression] div C1 to div C2 match.pd suboptimization
Date: Fri, 11 May 2018 07: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: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: hp at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority target_milestone
Message-ID: <bug-85726-4-VZZIiaTGHV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85726-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85726-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01277.txt.bz2
Content-length: 1300
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85726
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Priority|P3 |P2
Target Milestone|--- |6.5
--- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. On x86 the diff from GCC 4.8 to GCC 7 at -O2 is
@@ -6,8 +6,16 @@
x:
.LFB0:
.cfi_startproc
+ movl %edi, %eax
+ movl $715827883, %edx
+ imull %edx
+ movl %edi, %eax
+ sarl $31, %eax
+ sarl $3, %edx
+ subl %eax, %edx
leal 15(%rdi), %eax
testl %edi, %edi
+ movl %edx, ww(%rip)
movl $1431655766, %edx
cmovs %eax, %edi
movl %edi, %ecx
@@ -15,9 +23,9 @@
sarl $4, %ecx
movl %ecx, %eax
imull %edx
- subl %edi, %edx
- leal (%rdx,%rdx,2), %eax
- movl %edx, ww(%rip)
+ movl %edx, %eax
+ subl %edi, %eax
+ leal (%rax,%rax,2), %eax
subl %eax, %ecx
movl %ecx, %eax
ret
>From gcc-bugs-return-604383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:42:10 2018
Return-Path: <gcc-bugs-return-604383-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 66485 invoked by alias); 11 May 2018 07:42:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 66432 invoked by uid 48); 11 May 2018 07:42:06 -0000
From: "chrisgiorgi at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/85722] testsuite failure in libffi
Date: Fri, 11 May 2018 07:42:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: chrisgiorgi 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-85722-4-A5CMsyMAjp@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01278.txt.bz2
Content-length: 203
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85722
--- Comment #6 from Chris Giorgi <chrisgiorgi at gmail dot com> ---
Sorry, only pasted one link, here's the libffi test log:
http://termbin.com/vzy5
>From gcc-bugs-return-604384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:43:41 2018
Return-Path: <gcc-bugs-return-604384-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 68311 invoked by alias); 11 May 2018 07:43:41 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 68128 invoked by uid 55); 11 May 2018 07:43:25 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85696] OpenMP with variably modified and default(none) won't compile
Date: Fri, 11 May 2018 07: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: openmp, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85696-4-85o05Y1Zc1@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01279.txt.bz2
Content-length: 1141
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85696
--- Comment #4 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Author: jakub
Date: Fri May 11 07:42:50 2018
New Revision: 260156
URL: https://gcc.gnu.org/viewcvs?rev=260156&root=gcc&view=rev
Log:
PR c/85696
* c-omp.c (c_omp_predetermined_sharing): Return
OMP_CLAUSE_DEFAULT_SHARED for artificial vars with integral type.
* cp-tree.h (cxx_omp_predetermined_sharing_1): New prototype.
* cp-gimplify.c (cxx_omp_predetermined_sharing): New wrapper around
cxx_omp_predetermined_sharing_1. Rename old function to ...
(cxx_omp_predetermined_sharing_1): ... this.
* semantics.c (finish_omp_clauses): Use cxx_omp_predetermined_sharing_1
instead of cxx_omp_predetermined_sharing.
* c-c++-common/gomp/pr85696.c: New test.
Added:
trunk/gcc/testsuite/c-c++-common/gomp/pr85696.c
Modified:
trunk/gcc/c-family/ChangeLog
trunk/gcc/c-family/c-omp.c
trunk/gcc/cp/ChangeLog
trunk/gcc/cp/cp-gimplify.c
trunk/gcc/cp/cp-tree.h
trunk/gcc/cp/semantics.c
trunk/gcc/testsuite/ChangeLog
>From gcc-bugs-return-604385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:47:06 2018
Return-Path: <gcc-bugs-return-604385-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 71521 invoked by alias); 11 May 2018 07:47: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 70571 invoked by uid 48); 11 May 2018 07:45:58 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85731] [8/9 Regression] Inner class method declaration changes meaning of outer template class template method
Date: Fri, 11 May 2018 07: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.0
X-Bugzilla-Keywords: rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords target_milestone
Message-ID: <bug-85731-4-sbs7b9PQwx@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85731-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85731-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01280.txt.bz2
Content-length: 356
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85731
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |rejects-valid
Target Milestone|--- |8.2
>From gcc-bugs-return-604386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:49:49 2018
Return-Path: <gcc-bugs-return-604386-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 74573 invoked by alias); 11 May 2018 07:49: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 74256 invoked by uid 48); 11 May 2018 07:49:33 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/85734] --suggest-attribute=malloc misdiagnoses static functions
Date: Fri, 11 May 2018 07:49: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.1
X-Bugzilla-Keywords: diagnostic
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-85734-4-S9WYd65HC4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85734-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85734-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01281.txt.bz2
Content-length: 809
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85734
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
CC| |hubicka at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Component|c |ipa
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed. I guess this applies to all attribute suggestions. Honza?
>From gcc-bugs-return-604387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:50:44 2018
Return-Path: <gcc-bugs-return-604387-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 76721 invoked by alias); 11 May 2018 07: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 76352 invoked by uid 48); 11 May 2018 07:50:23 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85738] internal compiler error: verify_gimple failed
Date: Fri, 11 May 2018 07: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: accepts-invalid, ice-on-invalid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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 cf_known_to_fail
Message-ID: <bug-85738-4-DbkNnM1EgY@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85738-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85738-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01282.txt.bz2
Content-length: 844
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85738
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |accepts-invalid
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
Ever confirmed|0 |1
Known to fail| |7.3.1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
And with -fno-checking:
t.f90:8:0:
gx=fx(l)**2/(2*(2*l + 1))
internal compiler error: in convert_move, at expr.c:229
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://bugs.opensuse.org/> for instructions.
>From gcc-bugs-return-604388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 07:53:40 2018
Return-Path: <gcc-bugs-return-604388-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 80021 invoked by alias); 11 May 2018 07: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 79982 invoked by uid 48); 11 May 2018 07:53:35 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] New: Premature evaluation of __builtin_constant_p?
Date: Fri, 11 May 2018 07: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: 9.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01283.txt.bz2
Content-length: 1132
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
Bug ID: 85746
Summary: Premature evaluation of __builtin_constant_p?
Product: gcc
Version: 9.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: glisse at gcc dot gnu.org
Target Milestone: ---
int f(int a,int b){
int c = __builtin_constant_p(a < b);
return c;
}
In C or C++98, __builtin_constant_p is passed to the middle-end for further
optimization. In C++11, the front-end produces "c = 0;". That's because C++11
says we should check if the initializer can be constexpr-evaluated, and inside
constexpr evaluation we force the early (pessimistic) evaluation of
__builtin_constant_p.
Maybe we should only evaluate __builtin_constant_p to false when we are
committed to a constexpr evaluation, not for tentative ones as in initializers?
Or maybe we need different versions of __builtin_constant_p for people who want
to use it as if constexpr() and for those who want late optimization?
>From gcc-bugs-return-604389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:03:10 2018
Return-Path: <gcc-bugs-return-604389-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16941 invoked by alias); 11 May 2018 08:03:10 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 16484 invoked by uid 48); 11 May 2018 08:02:55 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80617] [missed optimization] Storing constant in two possibly-aliased locations
Date: Fri, 11 May 2018 08: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: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: glisse 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-80617-4-6IHwkCRqOr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01284.txt.bz2
Content-length: 371
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80617
--- Comment #12 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #11)
> Dup of PR23094 (and fixed).
Richard, comment #9 shows that the original testcase is only half-fixed (though
the other half seems hard to fix). Does this mean you consider the second half
as WONTFIX?
>From gcc-bugs-return-604390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:06:44 2018
Return-Path: <gcc-bugs-return-604390-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56872 invoked by alias); 11 May 2018 08:06: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 53767 invoked by uid 48); 11 May 2018 08:06:38 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Fri, 11 May 2018 08:06:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
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: keywords cf_gcctarget bug_status cf_reconfirmed_on cc everconfirmed
Message-ID: <bug-85740-4-kthiIlCDrE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01285.txt.bz2
Content-length: 1305
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Target| |x86_64-*-*, i?86-*-*
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
CC| |hubicka at gcc dot gnu.org,
| |marxin at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #7 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed with a Haswell CPU as well. Without the __builtin_expect we
rightfully predict the branch to be 50%/50% which means BB re-ordering will do
either nothing to pre-existing order or apply some other magic. CFG
construction makes the
flow exactly as visible in the source.
So not sure what you are asking here, but annotating the libgfortran routines
or inline expansion from the FE with __builtin_expect is probably a good idea.
At least I can't really see how to easily derive a new predictor that would
match
this case...
>From gcc-bugs-return-604391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:23:02 2018
Return-Path: <gcc-bugs-return-604391-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 89144 invoked by alias); 11 May 2018 08: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 88712 invoked by uid 55); 11 May 2018 08:22:57 -0000
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/80617] [missed optimization] Storing constant in two possibly-aliased locations
Date: Fri, 11 May 2018 08: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: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: rguenther at suse dot de
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-80617-4-nWRzbsVbVl@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
References: <bug-80617-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01286.txt.bz2
Content-length: 1590
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80617
--- Comment #13 from rguenther at suse dot de <rguenther at suse dot de> ---
On Fri, 11 May 2018, glisse at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80617
>
> --- Comment #12 from Marc Glisse <glisse at gcc dot gnu.org> ---
> (In reply to Richard Biener from comment #11)
> > Dup of PR23094 (and fixed).
>
> Richard, comment #9 shows that the original testcase is only half-fixed (though
> the other half seems hard to fix). Does this mean you consider the second half
> as WONTFIX?
So ...
__old_val_5 = MEM[(void * &)a_2(D)];
MEM[(void * &)a_2(D)] = 0B;
__old_val_6 = MEM[(void * &)b_3(D)];
MEM[(void * &)b_3(D)] = 0B;
MEM[(void * &)a_2(D)] = __old_val_6;
_7 = MEM[(void * &)b_3(D)];
MEM[(void * &)b_3(D)] = __old_val_5;
if (_7 != 0B)
.. the logic is that if a and b alias they have to exactly overlap
and thus _7 is __old_val_6 which is then 0.
While it might be quite interesting to try considering this
it requires a bit too much magic for the current machinery ;)
We've already value-numbered __old_val_6 but we would need to
re-visit its def with the constraint a_2 == b_3 so this would
add some back-propagation to the forward-working value-numbering.
The PR23094 fix is already somewhat limited and I'm not holding
my breath on the above given it doesn't fit any existing
optimization algorithm very well... (complexity also explodes
once you need to consider any combination of exact-overlap
aliases).
We can re-open this to track the issue.
>From gcc-bugs-return-604392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:25:21 2018
Return-Path: <gcc-bugs-return-604392-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 4852 invoked by alias); 11 May 2018 08:25:21 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 4679 invoked by uid 48); 11 May 2018 08:25:06 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85746] Premature evaluation of __builtin_constant_p?
Date: Fri, 11 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: c++
X-Bugzilla-Version: 9.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-85746-4-dRYJ3A9yGm@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85746-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01287.txt.bz2
Content-length: 553
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85746
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |missed-optimization
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
Ever confirmed|0 |1
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.
>From gcc-bugs-return-604393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:26:13 2018
Return-Path: <gcc-bugs-return-604393-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 6080 invoked by alias); 11 May 2018 08:26:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 5882 invoked by uid 48); 11 May 2018 08:26:09 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/85722] testsuite failure in libffi
Date: Fri, 11 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: libffi
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: attachments.created
Message-ID: <bug-85722-4-zVw179Wreh@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01288.txt.bz2
Content-length: 385
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85722
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Created attachment 44115
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44115&action=edit
libffi test log
(In reply to Chris Giorgi from comment #6)
> Sorry, only pasted one link, here's the libffi test log:
> http://termbin.com/vzy5
Now also attached.
>From gcc-bugs-return-604394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:32:32 2018
Return-Path: <gcc-bugs-return-604394-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 16095 invoked by alias); 11 May 2018 08:32: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 15774 invoked by uid 48); 11 May 2018 08:32:26 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libffi/85722] testsuite failure in libffi
Date: Fri, 11 May 2018 08:32:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libffi
X-Bugzilla-Version: 7.3.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85722-4-SWCcXKrAxD@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85722-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01289.txt.bz2
Content-length: 368
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85722
--- Comment #8 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(Based on discussion on IRC these log files are just copy&pasted from the
terminal connected to the machines where gcc is being built, because of some
weird restricted system with limited access which also prevents attaching files
here properly)
>From gcc-bugs-return-604395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:33:44 2018
Return-Path: <gcc-bugs-return-604395-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 31300 invoked by alias); 11 May 2018 08:33: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 31258 invoked by uid 48); 11 May 2018 08:33:40 -0000
From: "freddie_chopin at op dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85739] internal compiler error: in finish_member_declaration, at cp/semantics.c:3057
Date: Fri, 11 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: c++
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: freddie_chopin at op dot pl
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85739-4-mkvpCTugK0@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01290.txt.bz2
Content-length: 359
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85739
--- Comment #1 from Freddie Chopin <freddie_chopin at op dot pl> ---
I'm currently in the process of reducing the test case with the wonderful tool
that I've found yesterday - C-Reduce (; I hope that I'll be able to upload
something short and generic (not requiring arm-none-eabi) within a few hours.
>From gcc-bugs-return-604396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:34:31 2018
Return-Path: <gcc-bugs-return-604396-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 32669 invoked by alias); 11 May 2018 08:34:31 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 32574 invoked by uid 48); 11 May 2018 08:34:27 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/85696] OpenMP with variably modified and default(none) won't compile
Date: Fri, 11 May 2018 08:34:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: c
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: openmp, rejects-valid
X-Bugzilla-Severity: normal
X-Bugzilla-Who: jakub at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: 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-85696-4-SNap3HCqMv@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85696-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85696-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01291.txt.bz2
Content-length: 160
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85696
--- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9.1+ so far, backports queued.
>From gcc-bugs-return-604397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:34:55 2018
Return-Path: <gcc-bugs-return-604397-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 33547 invoked by alias); 11 May 2018 08:34: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 33486 invoked by uid 48); 11 May 2018 08:34:51 -0000
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85692] Two source permute not used for vector initialization
Date: Fri, 11 May 2018 08: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: 8.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: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-85692-4-I7XMrUR9mi@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85692-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85692-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01292.txt.bz2
Content-length: 465
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85692
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Fixed for 9.1+, thanks for the patch and report.
>From gcc-bugs-return-604398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:36:35 2018
Return-Path: <gcc-bugs-return-604398-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44776 invoked by alias); 11 May 2018 08:36:35 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 44681 invoked by uid 48); 11 May 2018 08:36:29 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] [8 regression] ARM -mbe8 behaviour doesn't match documentation
Date: Fri, 11 May 2018 08:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on cc target_milestone short_desc everconfirmed
Message-ID: <bug-85733-4-bS4c4mDINk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01293.txt.bz2
Content-length: 747
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
CC| |ramana at gcc dot gnu.org
Target Milestone|--- |8.2
Summary|ARM -mbe8 behaviour doesn't |[8 regression] ARM -mbe8
|match documentation |behaviour doesn't match
| |documentation
Ever confirmed|0 |1
>From gcc-bugs-return-604399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:36:57 2018
Return-Path: <gcc-bugs-return-604399-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45672 invoked by alias); 11 May 2018 08:36: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 45582 invoked by uid 48); 11 May 2018 08:36:53 -0000
From: "ramana at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85733] [8 regression] ARM -mbe8 behaviour doesn't match documentation
Date: Fri, 11 May 2018 08:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords: documentation
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ramana at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: rearnsha at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status assigned_to
Message-ID: <bug-85733-4-MtbJnsOoXg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85733-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01294.txt.bz2
Content-length: 389
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85733
Ramana Radhakrishnan <ramana at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
Assignee|unassigned at gcc dot gnu.org |rearnsha at gcc dot gnu.org
>From gcc-bugs-return-604400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:46:13 2018
Return-Path: <gcc-bugs-return-604400-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 47906 invoked by alias); 11 May 2018 08:46:13 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 47825 invoked by uid 48); 11 May 2018 08:46:07 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85742] sizeof allocatable arrays returning wrong value
Date: Fri, 11 May 2018 08:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
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: pault 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-85742-4-j9AYwRn54o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01295.txt.bz2
Content-length: 613
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85742
Paul Thomas <pault at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2018-05-11
Assignee|unassigned at gcc dot gnu.org |pault at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #1 from Paul Thomas <pault at gcc dot gnu.org> ---
Since it's my doing, I am on to it.
Thanks for the heads up
Paul
>From gcc-bugs-return-604401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:56:44 2018
Return-Path: <gcc-bugs-return-604401-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18702 invoked by alias); 11 May 2018 08:56: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 18640 invoked by uid 48); 11 May 2018 08:56:36 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50392] SIGSEGV in gfc_trans_label_assign
Date: Fri, 11 May 2018 08:56:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-50392-4-raYbfI61CV@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50392-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50392-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01296.txt.bz2
Content-length: 535
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50392
Jürgen Reuter <juergen.reuter at desy dot de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |juergen.reuter at desy dot de
--- Comment #15 from Jürgen Reuter <juergen.reuter at desy dot de> ---
This gives in ICE now with the current trunk, while it just shows an error
message for a "Deleted feature" when using -std=f95.
>From gcc-bugs-return-604402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 08:57:16 2018
Return-Path: <gcc-bugs-return-604402-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 19608 invoked by alias); 11 May 2018 08:57: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 19560 invoked by uid 48); 11 May 2018 08:57:10 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/85742] [8/9 Regression] sizeof allocatable arrays returning wrong value
Date: Fri, 11 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: 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: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: pault at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: keywords priority bug_status cf_known_to_work target_milestone short_desc cf_known_to_fail
Message-ID: <bug-85742-4-PVpi2HdilS@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85742-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85742-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01297.txt.bz2
Content-length: 908
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85742
Dominique d'Humieres <dominiq at lps dot ens.fr> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |wrong-code
Priority|P3 |P4
Status|NEW |ASSIGNED
Known to work| |7.3.0
Target Milestone|--- |8.2
Summary|sizeof allocatable arrays |[8/9 Regression] sizeof
|returning wrong value |allocatable arrays
| |returning wrong value
Known to fail| |8.1.0, 9.0
--- Comment #2 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
Caused by r257065. Marked as ASSIGNED.
>From gcc-bugs-return-604403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:01:51 2018
Return-Path: <gcc-bugs-return-604403-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25634 invoked by alias); 11 May 2018 09:01: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 25531 invoked by uid 48); 11 May 2018 09:01:47 -0000
From: "antoshkka at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] New: suboptimal code without constexpr
Date: Fri, 11 May 2018 09: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: antoshkka 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 keywords bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01298.txt.bz2
Content-length: 1523
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
Bug ID: 85747
Summary: suboptimal code without constexpr
Product: gcc
Version: 8.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: antoshkka at gmail dot com
Target Milestone: ---
Consider the following code snippet:
// Bubble-like sort. Anything complex enough will work
template <class It>
constexpr void sort(It first, It last) {
for (;first != last; ++first) {
auto it = first;
++it;
for (; it != last; ++it) {
if (*it < *first) {
auto tmp = *it;
*it = *first;
*first = tmp;
}
}
}
}
static int generate() {
int a[7] = {3, 7, 4, 2, 8, 0, 1};
sort(a + 0, a + 7);
return a[0] + a[6];
}
int no_constexpr() {
return generate();
}
Above code generates ~30 assembly instructions instead of just generating:
no_constexpr():
mov eax, 8
ret
But if we change `static` to `constexpr` then the compiler will optimize the
code correctly.
Could the compiler detect that `a[7]` holds values known at compile time and
force the constexpr on `sort(a + 0, a + 7);`? Could the compiler detect that
the function `generate()` is an `__attribute__((const))` function without
arguments and fully evaluate it's body?
>From gcc-bugs-return-604404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:04:36 2018
Return-Path: <gcc-bugs-return-604404-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 42414 invoked by alias); 11 May 2018 09:04: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 42317 invoked by uid 48); 11 May 2018 09:04:32 -0000
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50392] SIGSEGV in gfc_trans_label_assign
Date: Fri, 11 May 2018 09: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: 4.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: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50392-4-XMALKHG38D@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50392-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50392-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01299.txt.bz2
Content-length: 310
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50392
--- Comment #16 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
> This gives in ICE now with the current trunk, while it just shows
> an error message for a "Deleted feature" when using -std=f95.
Confirmed from at least 4.8 up to trunk (9.0).
>From gcc-bugs-return-604405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:06:16 2018
Return-Path: <gcc-bugs-return-604405-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 45452 invoked by alias); 11 May 2018 09:06: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 45370 invoked by uid 48); 11 May 2018 09:06:12 -0000
From: "juergen.reuter at desy dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/50392] SIGSEGV in gfc_trans_label_assign
Date: Fri, 11 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: fortran
X-Bugzilla-Version: 4.8.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: juergen.reuter at desy dot de
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-50392-4-HLF98qwnAE@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-50392-4@http.gcc.gnu.org/bugzilla/>
References: <bug-50392-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01300.txt.bz2
Content-length: 289
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=50392
--- Comment #17 from Jürgen Reuter <juergen.reuter at desy dot de> ---
Sorry, I don't want to generate unnecessary traffic, I'm just scrolling thru
old c.l.f. discussions and stumble over some old reports there from time to
time.
>From gcc-bugs-return-604406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:08:07 2018
Return-Path: <gcc-bugs-return-604406-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 48672 invoked by alias); 11 May 2018 09:08: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 48645 invoked by uid 48); 11 May 2018 09:08:03 -0000
From: "freddie_chopin at op dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85739] internal compiler error: in finish_member_declaration, at cp/semantics.c:3057
Date: Fri, 11 May 2018 09: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: needs-reduction
X-Bugzilla-Severity: normal
X-Bugzilla-Who: freddie_chopin at op dot 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: attachments.isobsolete attachments.created
Message-ID: <bug-85739-4-kn2laWZ2cL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85739-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01301.txt.bz2
Content-length: 1787
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85739
Freddie Chopin <freddie_chopin at op dot pl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Attachment #44111|0 |1
is obsolete| |
--- Comment #2 from Freddie Chopin <freddie_chopin at op dot pl> ---
Created attachment 44116
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44116&action=edit
reduced and generic test case for gcc 8.1.0
I attach reduced test case for gcc 8.1.0. Interestingly today I cannot
reproduce the error for previous versions of gcc, which means that either I
just got confused yesterday or the triggering code is a bit different. So for
now let's ignore previous versions and focus on gcc 8.1.0.
Using the test case:
-- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 --
$ g++ --version
g++ (GCC) 8.1.0
Copyright (C) 2018 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.
$ g++ -c Scheduler-8.cpp -std=c++14
$ g++ -c Scheduler-8.cpp -std=c++17
Scheduler-8.cpp: In instantiation of ‘class B<l, &l::f>’:
Scheduler-8.cpp:29:20: required from here
Scheduler-8.cpp:3:47: internal compiler error: in finish_member_declaration, at
cp/semantics.c:3057
template <typename a, const int a::*> class B { using e = ptrdiff_t; };
^
Please submit a full bug report,
with preprocessed source if appropriate.
See <https://bugs.archlinux.org/> for instructions.
-- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 -- >8 --
>From gcc-bugs-return-604407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:13:04 2018
Return-Path: <gcc-bugs-return-604407-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 56201 invoked by alias); 11 May 2018 09: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 56075 invoked by uid 48); 11 May 2018 09:12:59 -0000
From: "daffra.claudio at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85717] anonymous union in initializer list : do not handle the types correctly
Date: Fri, 11 May 2018 09: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: 5.3.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: daffra.claudio 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-85717-4-3Zvsm9pZJB@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85717-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85717-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01302.txt.bz2
Content-length: 1353
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85717
--- Comment #4 from claudio daffra <daffra.claudio at gmail dot com> ---
I expect that the compiler regardless of the location of the types
always gives me the same result, error message or warning
indeed :
# case integer before double :
union
{
uint64_t integer ;
double real;
} ;
gives me error, about narrowing conversion :
prova.cpp:32:5: error: narrowing conversion of '3.3999999999999999e+0' from
'double' to 'uint64_t {aka long long unsigned int}' inside { } [-Wnarrowing]
t1 = { 1 ,"a",3.4 } ;
^
# case double before integer, compile without warning or error me :
union
{
double real;
uint64_t integer ;
} ;
and about output gives me undefined behavior about integer
t1 = { 1 ,"a",3.4 } ;
std::cout << t1.real << "\n" ;
t1 = { 1 ,"a",2 } ;
std::cout << t1.integer << "\n" ;
C:\prj>x.exe
6.6
3
3.4
4611686018427387904
however if it is a normal behavior of c++ or compiler, close it.
>From gcc-bugs-return-604408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:14:35 2018
Return-Path: <gcc-bugs-return-604408-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 58215 invoked by alias); 11 May 2018 09:14: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 58116 invoked by uid 48); 11 May 2018 09:14:30 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/85740] Non-optimal determining maximum in a loop
Date: Fri, 11 May 2018 09:14:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: middle-end
X-Bugzilla-Version: unknown
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: marxin at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85740-4-LzMCobYU0p@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85740-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01303.txt.bz2
Content-length: 1025
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85740
--- Comment #8 from Martin Liška <marxin at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> Confirmed with a Haswell CPU as well. Without the __builtin_expect we
> rightfully predict the branch to be 50%/50% which means BB re-ordering will
> do either nothing to pre-existing order or apply some other magic. CFG
> construction makes the
> flow exactly as visible in the source.
>
> So not sure what you are asking here, but annotating the libgfortran routines
> or inline expansion from the FE with __builtin_expect is probably a good
> idea.
If the code is emitted in Fortran FE, that it's similar to specific predictors:
grep for 'PRED_FORTRAN_'. These are predictors emitted by the FE and can have
specific probability based on SPEC benchmarks.
Can you Thomas point me to code that emits the maxloc/minloc?
>
> At least I can't really see how to easily derive a new predictor that would
> match
> this case...
Agree.
>From gcc-bugs-return-604409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:28:49 2018
Return-Path: <gcc-bugs-return-604409-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 65049 invoked by alias); 11 May 2018 09:28: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 64957 invoked by uid 55); 11 May 2018 09:28:42 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85606] [8 regression] Assembly file generated for ARM Cortex-M0 should not specify `.arch armv6-m` at all or use `.arch armv6s-m`
Date: Fri, 11 May 2018 09:28:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85606-4-Ev8GNcW9tc@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01304.txt.bz2
Content-length: 1534
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85606
--- Comment #2 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Fri May 11 09:28:10 2018
New Revision: 260157
URL: https://gcc.gnu.org/viewcvs?rev=260157&root=gcc&view=rev
Log:
[arm] PR target/85606 prefer armv6s-m for armv6-m parts
When Arm introduced ARMv6-M there were two variants, ARMv6-M and
ARMv6S-M. The two differed only in support for the SVC instruction.
Later on SVC was then made a mandatory part of ARMv6-M and the
ARMv6S-M name was dropped. GCC and GAS, however still recognize both
names and at least some versions of GAS still distinguish between the
two.
To address this, this patch changes the architecture for the ARMv6-m
cortex parts (m0, m0plus, m1 and the variants will small multiply
units) to use the ARMv6S-M name in conjunction with the assembler.
This avoids problems with them rejecting code that was previously
accepted with older versions of GCC where we did not pass an explicit
architecture string through to the compiler when using -mcpu on the
command line.
PR target/85606
* config/arm/arm-cpus.in: Add comment that ARMv6-m and ARMv6S-m are now
equivalent.
(cortex-m0): Use armv6s-m isa.
(cortex-m0plus): Likewise.
(cortex-m1): Likewise.
(cortex-m0.small-multiply): Likewise.
(cortex-m0plus.small-multiply): Likewise.
(cortex-m1.small-multiply): Likewise.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/config/arm/arm-cpus.in
>From gcc-bugs-return-604410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:31:30 2018
Return-Path: <gcc-bugs-return-604410-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 69400 invoked by alias); 11 May 2018 09: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 69327 invoked by uid 55); 11 May 2018 09:31:26 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85606] [8 regression] Assembly file generated for ARM Cortex-M0 should not specify `.arch armv6-m` at all or use `.arch armv6s-m`
Date: Fri, 11 May 2018 09:31:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 8.0.1
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rearnsha at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 8.2
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85606-4-mpy3Tsrhch@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01305.txt.bz2
Content-length: 1566
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85606
--- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Author: rearnsha
Date: Fri May 11 09:30:49 2018
New Revision: 260158
URL: https://gcc.gnu.org/viewcvs?rev=260158&root=gcc&view=rev
Log:
[arm] PR target/85606 prefer armv6s-m for armv6-m parts
When Arm introduced ARMv6-M there were two variants, ARMv6-M and
ARMv6S-M. The two differed only in support for the SVC instruction.
Later on SVC was then made a mandatory part of ARMv6-M and the
ARMv6S-M name was dropped. GCC and GAS, however still recognize both
names and at least some versions of GAS still distinguish between the
two.
To address this, this patch changes the architecture for the ARMv6-m
cortex parts (m0, m0plus, m1 and the variants will small multiply
units) to use the ARMv6S-M name in conjunction with the assembler.
This avoids problems with them rejecting code that was previously
accepted with older versions of GCC where we did not pass an explicit
architecture string through to the compiler when using -mcpu on the
command line.
PR target/85606
* config/arm/arm-cpus.in: Add comment that ARMv6-m and ARMv6S-m are now
equivalent.
(cortex-m0): Use armv6s-m isa.
(cortex-m0plus): Likewise.
(cortex-m1): Likewise.
(cortex-m0.small-multiply): Likewise.
(cortex-m0plus.small-multiply): Likewise.
(cortex-m1.small-multiply): Likewise.
Modified:
branches/gcc-8-branch/gcc/ChangeLog
branches/gcc-8-branch/gcc/config/arm/arm-cpus.in
>From gcc-bugs-return-604411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:33:28 2018
Return-Path: <gcc-bugs-return-604411-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 95948 invoked by alias); 11 May 2018 09:33: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 95887 invoked by uid 48); 11 May 2018 09:33:24 -0000
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/85606] [8,9 regression] Assembly file generated for ARM Cortex-M0 should not specify `.arch armv6-m` at all or use `.arch armv6s-m`
Date: Fri, 11 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: target
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: 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: bug_status resolution short_desc
Message-ID: <bug-85606-4-9ZPiVgz1Rk@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85606-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85606-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01306.txt.bz2
Content-length: 805
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85606
Richard Earnshaw <rearnsha at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
Summary|[8 regression] Assembly |[8,9 regression] Assembly
|file generated for ARM |file generated for ARM
|Cortex-M0 should not |Cortex-M0 should not
|specify `.arch armv6-m` at |specify `.arch armv6-m` at
|all or use `.arch armv6s-m` |all or use `.arch armv6s-m`
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
Fixed.
>From gcc-bugs-return-604413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:36:32 2018
Return-Path: <gcc-bugs-return-604413-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102570 invoked by alias); 11 May 2018 09:36: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 102475 invoked by uid 55); 11 May 2018 09:36:27 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/68846] Pointer function as LValue doesn't work when the assignment regards a dummy argument.
Date: Fri, 11 May 2018 09: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: 6.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: 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-68846-4-IkHXYcF8DM@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-68846-4@http.gcc.gnu.org/bugzilla/>
References: <bug-68846-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01308.txt.bz2
Content-length: 1042
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68846
--- Comment #9 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Fri May 11 09:35:55 2018
New Revision: 260160
URL: https://gcc.gnu.org/viewcvs?rev=260160&root=gcc&view=rev
Log:
2018-05-11 Paul Thomas <pault@gcc.gnu.org>
PR fortran/68846
PR fortran/70864
backport from trunk
* resolve.c (get_temp_from_expr): The temporary must not have
dummy or intent attributes.
2018-05-11 Paul Thomas <pault@gcc.gnu.org>
PR fortran/68846
backport from trunk
* gfortran.dg/temporary_3.f90 : New test.
PR fortran/70864
backport from trunk
* gfortran.dg/temporary_2.f90 : New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/temporary_2.f90
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/temporary_3.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-604414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:36:32 2018
Return-Path: <gcc-bugs-return-604414-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 102578 invoked by alias); 11 May 2018 09:36: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 102478 invoked by uid 55); 11 May 2018 09:36:27 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/70864] internal compiler error: in gfc_get_symbol_decl, at fortran/trans-decl.c:1403
Date: Fri, 11 May 2018 09: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: 6.1.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: 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-70864-4-adiUut8iBP@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-70864-4@http.gcc.gnu.org/bugzilla/>
References: <bug-70864-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01309.txt.bz2
Content-length: 1042
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70864
--- Comment #7 from Paul Thomas <pault at gcc dot gnu.org> ---
Author: pault
Date: Fri May 11 09:35:55 2018
New Revision: 260160
URL: https://gcc.gnu.org/viewcvs?rev=260160&root=gcc&view=rev
Log:
2018-05-11 Paul Thomas <pault@gcc.gnu.org>
PR fortran/68846
PR fortran/70864
backport from trunk
* resolve.c (get_temp_from_expr): The temporary must not have
dummy or intent attributes.
2018-05-11 Paul Thomas <pault@gcc.gnu.org>
PR fortran/68846
backport from trunk
* gfortran.dg/temporary_3.f90 : New test.
PR fortran/70864
backport from trunk
* gfortran.dg/temporary_2.f90 : New test.
Added:
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/temporary_2.f90
branches/gcc-8-branch/gcc/testsuite/gfortran.dg/temporary_3.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-604412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:36:10 2018
Return-Path: <gcc-bugs-return-604412-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 101137 invoked by alias); 11 May 2018 09:36: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 101039 invoked by uid 55); 11 May 2018 09:36:04 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83687] [6 Regression] ARM NEON invalid optimisation for vabd/vabdl
Date: Fri, 11 May 2018 09:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: ASSIGNED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ktkachov at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-83687-4-V9hiKKpa7q@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01307.txt.bz2
Content-length: 965
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83687
--- Comment #6 from ktkachov at gcc dot gnu.org ---
Author: ktkachov
Date: Fri May 11 09:35:31 2018
New Revision: 260159
URL: https://gcc.gnu.org/viewcvs?rev=260159&root=gcc&view=rev
Log:
[arm] PR target/83687: Fix invalid combination of VSUB + VABS into VABD
PR target/83687
* config/arm/neon.md (neon_vabd<mode>_2): Use VCVTF mode iterator.
Remove integer-related logic from pattern.
(neon_vabd<mode>_3): Likewise.
* gcc.target/arm/neon-combine-sub-abs-into-vabd.c: Delete integer
tests.
* gcc.target/arm/pr83687.c: New test.
Added:
branches/gcc-6-branch/gcc/testsuite/gcc.target/arm/pr83687.c
Modified:
branches/gcc-6-branch/gcc/ChangeLog
branches/gcc-6-branch/gcc/config/arm/neon.md
branches/gcc-6-branch/gcc/testsuite/ChangeLog
branches/gcc-6-branch/gcc/testsuite/gcc.target/arm/neon-combine-sub-abs-into-vabd.c
>From gcc-bugs-return-604415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:43:17 2018
Return-Path: <gcc-bugs-return-604415-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 12704 invoked by alias); 11 May 2018 09:43: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 12664 invoked by uid 48); 11 May 2018 09:43:11 -0000
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] suboptimal code without constexpr
Date: Fri, 11 May 2018 09: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: rguenth at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-85747-4-EMYtotFOBC@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01310.txt.bz2
Content-length: 819
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rguenth at gcc dot gnu.org
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
Well. Besides of the C++ frontend the compiler has no facility to fully
evaluate a part of a program but for cases like this it would rely on
inlining then unrolling and then constant propagation. All this work has
limits and heuristics and there are just cases where the heuristics need
to give up...
What's the reason for writing the code as you pasted it?
Note that sort isn't a const function since it modifies global memory.
>From gcc-bugs-return-604416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:46:38 2018
Return-Path: <gcc-bugs-return-604416-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 17386 invoked by alias); 11 May 2018 09:46:38 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 17301 invoked by uid 48); 11 May 2018 09:46:33 -0000
From: "eberhard.franz@th-nuernberg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/85748] New: dbg, gfortran: Erroneous watch of matrix rows as formal arguments using assumed shape
Date: Fri, 11 May 2018 09:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: debug
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eberhard.franz@th-nuernberg.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-85748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01311.txt.bz2
Content-length: 1297
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85748
Bug ID: 85748
Summary: dbg, gfortran: Erroneous watch of matrix rows as
formal arguments using assumed shape
Product: gcc
Version: 8.1.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: debug
Assignee: unassigned at gcc dot gnu.org
Reporter: eberhard.franz@th-nuernberg.de
Target Milestone: ---
The newer versions of gdb have greatly simplified watching of Fortran arrays.
No longer *((real_8 *)y)@2 or similiar when one wants to watch arrays passed by
assumed shape to a subprogram. Just type the name of the array ... Thank you
very much for it!
But I believe there is a bug in watching arrays in a special case. This special
case occurs when you pass the row of a matrix (e.g. A(3, :)) to a subprogram
using assumed shape. The subprogram handles such vectors absolutely correctly,
but the vectors are displayed incorrectly using print in gdb. Obviously one
will see the first element of the row followed by wrong elements.
This error doesn't occur when one uses explict shape passing the matrix row.
I wrote a little sample program in order to demonstrate this behaviour and
attached it.
>From gcc-bugs-return-604418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:47:57 2018
Return-Path: <gcc-bugs-return-604418-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 41728 invoked by alias); 11 May 2018 09:47: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 39026 invoked by uid 48); 11 May 2018 09:47:52 -0000
From: "eberhard.franz@th-nuernberg.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug debug/85748] dbg, gfortran: Erroneous watch of matrix rows as formal arguments using assumed shape
Date: Fri, 11 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: debug
X-Bugzilla-Version: 8.1.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: eberhard.franz@th-nuernberg.de
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc attachments.created
Message-ID: <bug-85748-4-mVE0TBiJlg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85748-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85748-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01313.txt.bz2
Content-length: 570
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85748
Eberhard Franz <eberhard.franz@th-nuernberg.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |eberhard.franz@th-nuernberg
| |.de
--- Comment #1 from Eberhard Franz <eberhard.franz@th-nuernberg.de> ---
Created attachment 44117
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=44117&action=edit
Fortran sample program
>From gcc-bugs-return-604417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:47:27 2018
Return-Path: <gcc-bugs-return-604417-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 25520 invoked by alias); 11 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 22826 invoked by uid 48); 11 May 2018 09:47:22 -0000
From: "ktkachov at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/83687] [6 Regression] ARM NEON invalid optimisation for vabd/vabdl
Date: Fri, 11 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: target
X-Bugzilla-Version: 7.2.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ktkachov at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: ktkachov at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 6.5
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status resolution
Message-ID: <bug-83687-4-mCYQsg8f9o@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-83687-4@http.gcc.gnu.org/bugzilla/>
References: <bug-83687-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01312.txt.bz2
Content-length: 420
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83687
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |FIXED
--- Comment #7 from ktkachov at gcc dot gnu.org ---
Fixed on the active branches.
>From gcc-bugs-return-604419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 09:54:11 2018
Return-Path: <gcc-bugs-return-604419-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 67940 invoked by alias); 11 May 2018 09: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 67822 invoked by uid 48); 11 May 2018 09:54:07 -0000
From: "glisse at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/85747] suboptimal code without constexpr
Date: Fri, 11 May 2018 09: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.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: glisse at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85747-4-QeHPnmdLpg@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85747-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01314.txt.bz2
Content-length: 1054
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85747
--- Comment #2 from Marc Glisse <glisse at gcc dot gnu.org> ---
(In reply to Antony Polukhin from comment #0)
> Could the compiler detect that `a[7]` holds values known at compile time and
> force the constexpr on `sort(a + 0, a + 7);`?
There has to be a limit. If I write a program that computes the trillion's
decimal of pi, this is a constant, do you expect the compiler to evaluate the
whole program and compile it to just return cst? We are moving into a realm
where we would want to mix compilation and execution, sort of JIT.
For smaller functions, some heuristics could be used to try compile-time
evaluation, but sorting an array of size 7 already seems large to me.
> Could the compiler detect that
> the function `generate()` is an `__attribute__((const))` function without
> arguments and fully evaluate it's body?
If you call the function twice in a row, the compiler removes the second call
and reuses the result from the first, so at least it notices that generate is
pure.
>From gcc-bugs-return-604420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 10:12:17 2018
Return-Path: <gcc-bugs-return-604420-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 109826 invoked by alias); 11 May 2018 10:12: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 109778 invoked by uid 48); 11 May 2018 10:12:12 -0000
From: "schwab@linux-m68k.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/85725] strchr and strstr of a one-element array with a non-empty string can be assumed to return null
Date: Fri, 11 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: tree-optimization
X-Bugzilla-Version: 8.0
X-Bugzilla-Keywords: missed-optimization
X-Bugzilla-Severity: normal
X-Bugzilla-Who: schwab@linux-m68k.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-85725-4-x5QGFbwitR@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-85725-4@http.gcc.gnu.org/bugzilla/>
References: <bug-85725-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2018-05/txt/msg01315.txt.bz2
Content-length: 252
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=85725
--- Comment #2 from Andreas Schwab <schwab@linux-m68k.org> ---
The C standard defines a string as "a contiguous sequence of characters
terminated by and including the first null character" (7.1.1).
>From gcc-bugs-return-604421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 10:20:37 2018
Return-Path: <gcc-bugs-return-604421-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 44143 invoked by alias); 11 May 2018 10: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 44067 invoked by uid 48); 11 May 2018 10:20:31 -0000
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/82229] GCC7's LTO underperforms compared to GCC6
Date: Fri, 11 May 2018 10:20: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: marxin at gcc dot gnu.org
X-Bugzilla-Status: WAITING
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: assigned_to
Message-ID: <bug-82229-4-9eTXm8UzVY@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/msg01316.txt.bz2
Content-length: 544
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82229
Martin Liška <marxin at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|marxin at gcc dot gnu.org |unassigned at gcc dot gnu.org
--- Comment #27 from Martin Liška <marxin at gcc dot gnu.org> ---
I'm sorry for not having enough time. If GCC 7 and 8 is fine, then I won't
spend much time investigating version 6. Thanks for understanding.
>From gcc-bugs-return-604422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 11 11:03:30 2018
Return-Path: <gcc-bugs-return-604422-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 18710 invoked by alias); 11 May 2018 11: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 18693 invoked by uid 89); 11 May 2018 11:03:29 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=4.5 required=5.0 testsºYES_50,HTML_MESSAGE,MAILING_LIST_MULTI,PYZOR_CHECK,RCVD_IN_PBL,SPF_PASS autolearn=no version=3.3.2 spammy=wechat, motor, thickness, Wechat
X-HELO: mx1.mail.hawne.com
Received: from Unknown (HELO mx1.mail.hawne.com) (119.98.55.206) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 11 May 2018 11:03:26 +0000
Date: Fri, 11 May 2018 11:03:00 -0000
From: "EvenWall" <evenwall@hawne.com>
To: "gcc-bugs\@gcc.gnu.org" <gcc-bugs@gcc.gnu.org>
Reply-To: izysun@126.com
List: ewe
List-Owner: <evenwall@hawne.com>
Message-ID: <20180511170343.25983924@hawne.com>
MIME-Version: 1.0
Subject: Hollow Rotor - Lower Cost Rotor for Downhole PC Pump / Mud Motor
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
X-SW-Source: 2018-05/txt/msg01317.txt.bz2
Content-length: 902
__
Even Wall Thickness Hollow Rotor For Downhole PC Pump
* Well washing through hollow rotor;
* Steam injection into well through hollow sucker rod and hollow rotor;
  * use of same components of sucker rod pumping system for both pumping and injecting.
  * The system requires the drilling of only one well for injection.
  * The injected steam builds up a steam chamber that rises to the top of the reservoir.
  * While steam injection heats up the oil and improves the flow characteristic, hot oil drains  into the production well.
* Huge cost savings  because of material saving,price is 1/3 lower compared with solid rotor.
--
Subscription Reminder: You're Subscribed to, EvenWall
Using the address: gcc-bugs@gcc.gnu.org
From: evenwall@hawne.com
Wuhan EvenWall Machinery Co., Ltd.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-05-10 18:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-85732-4@http.gcc.gnu.org/bugzilla/>
2018-05-10 18:14 ` [Bug libstdc++/85732] use_facet<moneypunct<char, true>>(mylocale) retrieving wrong locale information gnu-org at bignm dot com
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).